[Bug 1823732] [NEW] jsonlint binary should be named "jsonlint", not "jsonlint-php"
Public bug reported: AFAICT the program has no connection to PHP, beyond being written in PHP, and there doesn't seem to be another command with a conflicting name. Or at least, typing "jsonlint" at the command line doesn't suggest installing any other packages. Debian seems to have changed the name to "jsonlint-php" for some reason. The upstream name is "jsonlint": https://github.com/Seldaek/jsonlint/tree/master/bin ** Affects: jsonlint (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823732 Title: jsonlint binary should be named "jsonlint", not "jsonlint-php" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jsonlint/+bug/1823732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1709684] [NEW] package libxfont-dev (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc/libxfont-dev/fontlib.html', which is also in package libxfont1-dev 1:1.5.1-1ubun
Public bug reported: $ sudo apt -f install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: linux-headers-4.10.0-27 linux-headers-4.10.0-27-generic linux-headers-4.8.0-36 linux-headers-4.8.0-36-generic linux-image-4.10.0-27-generic linux-image-4.8.0-36-generic linux-image-extra-4.10.0-27-generic linux-image-extra-4.8.0-36-generic linux-signed-image-4.10.0-27-generic snap-confine Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: libxfont-dev The following NEW packages will be installed: libxfont-dev 0 upgraded, 1 newly installed, 0 to remove and 3 not upgraded. 31 not fully installed or removed. Need to get 0 B/124 kB of archives. After this operation, 494 kB of additional disk space will be used. Do you want to continue? [Y/n] y (Reading database ... 305731 files and directories currently installed.) Preparing to unpack .../libxfont-dev_1%3a2.0.1-3~ubuntu16.04.1_amd64.deb ... Unpacking libxfont-dev (1:2.0.1-3~ubuntu16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/libxfont-dev_1%3a2.0.1-3~ubuntu16.04.1_amd64.deb (--unpack): trying to overwrite '/usr/share/doc/libxfont-dev/fontlib.html', which is also in package libxfont1-dev 1:1.5.1-1ubuntu0.16.04.1 Errors were encountered while processing: /var/cache/apt/archives/libxfont-dev_1%3a2.0.1-3~ubuntu16.04.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libxfont-dev (not installed) ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Wed Aug 9 20:45:28 2017 DuplicateSignature: package:libxfont-dev:(not installed) Unpacking libxfont-dev (1:2.0.1-3~ubuntu16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/libxfont-dev_1%3a2.0.1-3~ubuntu16.04.1_amd64.deb (--unpack): trying to overwrite '/usr/share/doc/libxfont-dev/fontlib.html', which is also in package libxfont1-dev 1:1.5.1-1ubuntu0.16.04.1 ErrorMessage: trying to overwrite '/usr/share/doc/libxfont-dev/fontlib.html', which is also in package libxfont1-dev 1:1.5.1-1ubuntu0.16.04.1 InstallationDate: Installed on 2017-07-26 (13 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: libxfont2 Title: package libxfont-dev (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc/libxfont-dev/fontlib.html', which is also in package libxfont1-dev 1:1.5.1-1ubuntu0.16.04.1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libxfont2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1709684 Title: package libxfont-dev (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc/libxfont-dev/fontlib.html', which is also in package libxfont1-dev 1:1.5.1-1ubuntu0.16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxfont2/+bug/1709684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 584632]
For those who want to see this in Thunderbird 38 -- I suggest talking to the Thunderbird people and asking them if they can cherry-pick the patch for Thunderbird without affecting Firefox. If it's really a huge improvement for them, maybe they'll be willing to accept it despite lack of testing. Perhaps file a bug against the Thunderbird product, or get on IRC/e-mail/etc. with the appropriate people. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/584632 Title: composer changes font mid email To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/584632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 584632]
(In reply to Jorg K from comment #110) Where in the mochitest.ini do I put my new test? I put it right at the front since I don't understand the syntax of skip-if. Does that skip the next line? Perhaps you can suggest a line where it should go. Or say: After such and such. Just add a line that says [test_bug756984.html] (assuming that's the file's name). Put it right before the next test line, like [test_bug784410.html] or whatever. The skip-if, support-files, etc. lines apply to the preceding test file, so don't put it before one of those lines. (This is confusing. I looked it up in the online docs: https://ci.mozilla.org/job/mozilla-central-docs/Tree_Documentation/build/buildsystem/test_manifests.html) In the test I use a span123/span to get offset 3 when clicking behind it. Without the span, I get offset 4, which I find surprising, or clicking at the front gives offset 1 instead of 0. FF 36 does the same, so I guess it's right, but I'd like to understand why 4 and not 3, or 1 and not 0. Why does the span make a difference? You have a newline at the beginning of the div. That's the first character in the text node (although it doesn't normally render). If you did div id='div1'123br456br/div all on one line, the offsets would be as you expected even without the span. Anyway, the tests are passed. Without my changes, the first test fails as expected. As I said in comment #106: There are already tests for hitting the end key and navigating with the arrow keys, so this test should be the only one we need additionally. Sounds great! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/584632 Title: composer changes font mid email To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/584632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 584632]
(In reply to Jorg K from comment #92) OK, but how do I send the patch to the try server? I have my level 1 access rights and I believe SSH is set up correctly. I tried hg push -f ssh://mozi...@jorgk.com@hg.mozilla.org/try/ *before* coming across the hg qnew command. It returned: No changes found or words to that extent. I haven't tried after the hg qnew. So what is the exact sequence of commands? BTW, I'm on Windows 7. 30 seconds of your time save me three hours of (very frustrating) research (since I want to focus on the problem and not the infrastructure). If you have some changes you want to commit, and no patches currently applied: hg qnew mypatchname # This saves your changes to an mq patch hg qnew -m try: -b do -p all -u all[x64] -t none try # Make a second patch with the try line hg push -f mc-try # Make sure you have Magnus' line in .hg/hgrc hg qdelete try # Delete the empty try patch Note: this will leave you with a patch in mq called mypatchname with your changes. If you make any new changes to the patch and want to submit to try again, do the same, except instead of the first line, do hg qref to refresh the existing patch instead of making a new one. To view your existing patches, try hg qser -s; to move around, you can use hg qpop and hg qpush and hg qgoto; for more help, try hg help mq or hg help commandname. If you see any weird changes that only appear on some platforms and don't look related to your changes, they're probably random (intermittent) failures that are unrelated to your changes. You can usually spot changes that you really caused because they'll show up on all platforms, and look related to your changes. If you're not sure, you can ask us, or ask on IRC for a quicker response. However, this stuff worries me (3x crashed, 1x time out) 965721 Intermittent test_bug409604.html, test_bug719533.html, test_richtext2.html, test_bug412567.html | application crashed [@ imgStatusTracker::RecordCancel()] 969526 Intermittent test_richtext.html,test_richtext2.html,test_bug436801.html | application crashed [@ KERNELBASE.dll + 0x89ae4] (ABORT: Should have mProgressTracker until we create mImage: 'mProgressTracker') 1129538 Intermittent test_draggableprop.html,test_richtext2.html | application crashed [@ mozalloc_abort(char const*)] after ABORT: Should have given mProgressTracker to mImage: '!mProgressTracker', file /image/src/imgRequest.cpp, line 149 1142900 Intermittent test_richtext2.html | application timed out after 330 seconds with no output Any comments on these crashes and time-outs? Don't worry about those. These tests fail sometimes at random -- it's not connected to your changes. P.S.: Would you be able to let me know your time-zone so I know when not to expect feedback ;-) I'm UTC+0200, and switching to UTC+0300 this Thursday night. Last I was aware, Ehsan lives in eastern Canada and so should be UTC-0400. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/584632 Title: composer changes font mid email To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/584632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 584632]
(In reply to Jorg K from comment #106) Pushed to try server (thanks guys for the support!): https://treeherder.mozilla.org/#/jobs?repo=tryrevision=9782fa678cd1 Treeherder isn't loading for me right now, but someone else who looked said it seemed fine. Just out of interest: Why build on all platforms and then just execute on Linux? I mean, why build it in the first place? Just to see that it compiles? If it already compiled once, and I only rerun tests, that doesn't make too much sense. Yes, to see that it compiles. Different platforms use different compilers, and maybe sometimes different compiler versions, and they treat different things as errors. Compiling the code on all platforms is usually a good resources-safety tradeoff. (Ideally all tests would be run on all platforms, but it overloads the try servers.) Further steps: If this try run goes well, the only thing missing is a test for the changes I made. Two scenarios are already covered by the existing tests which I had to change: the moving around with the left arrow and the jumping to the end of the line with a key stroke. What's missing is the clicking beyond the end of the line. The first try run in comment #71 was done with only the code to fix the clicking. No tests failed, so there wasn't a test for this, so it needs to be added now. Sounds good! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/584632 Title: composer changes font mid email To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/584632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 584632]
Try running the tests locally without your patches if you want to be sure (hg qpop -a will get rid of them if you're using mq). If they fail even without your patches, don't worry about it. In theory all tests should work on all supported platforms and configurations, but in practice some small fraction will break on some systems for various reasons, and in practice we only require that they work on the try servers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/584632 Title: composer changes font mid email To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/584632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 584632]
Okay, this caused some try failures. One of them is an unexpected pass in richtext2, which is good! It means you just have to update the test so it knows we're supposed to pass now. In the case of richtext2, you want to edit the file editor/libeditor/tests/browserscope/lib/richtext2/currentStatus.js and remove the appropriate lines (this is different from how most tests need to be updated). To check that it worked, run this (which may take a while and you have to keep the browser window focused): ./mach mochitest-plain editor/libeditor/tests/browserscope If you're on Linux, you should be able to install the appropriate package for the xvfb-run command and use this instead so it runs without creating a window you have to keep in focus: xvfb-run ./mach mochitest-plain editor/libeditor/tests/browserscope The other failure I see is layout/generic/test/test_movement_by_characters.html, which you need to look at. It could be your patch has a problem, or it could be the test needs to be updated. If you're having trouble, please feel free to ask for help! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/584632 Title: composer changes font mid email To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/584632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 584632]
A good try line to use by default for editor changes is: try: -b do -p all -u all[x64] -t none This will build on all platforms (to detect compile errors), and will run tests only on 64-bit Linux (to avoid wasting resources). If there might be platform-specific test failures, remove the [x64], but I don't think you need to do that here. For Mercurial -- if you're using mq (which you should), you don't ever want to do hg commit. The patch you've attached is exactly right. Here are the try results for you: https://treeherder.mozilla.org/#/jobs?repo=tryrevision=fd11f71e3daa -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/584632 Title: composer changes font mid email To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/584632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 584632]
The failure in editor/libeditor/tests/test_selection_move_commands.xul also needs looking at. Otherwise, looks good! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/584632 Title: composer changes font mid email To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/584632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 584632]
For the record, from black-box testing of WebKit a few years ago, it
looked like it normalized the selection after every change. Even if you
called .addRange(), it copied the range and then stuck the selection
endpoints inside a nearby text node if available, etc. I think it's
taking things too far to change script-specified selections, but the
right way to do this is probably to have some sort of helper method in
Selection like NormalizePoint(nsINode*, int32_t) and call it before
every user-initiated selection change. We might want to disallow other
types of user-created selections from occurring in the future, although
my brain is too rusty to supply any.
Do we want to allow a selection like bfoo/b{}ibar/i, with the
selection collapsed in between the b and i? IIRC, WebKit in my
testing forced this to be bfoo[]/bibar/i (always making it on
the previous text node). A ten-second test in WordPad suggests this is
the right thing to do.
I don't think any of this has to be in the scope of the current bug,
though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/584632
Title:
composer changes font mid email
To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/584632/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 584632]
Oops, I missed that part of comment #68 -- should have read more carefully. I don't know what more there is to do, since it passed a try run. But that's why Ehsan is in charge and not me. ;) In any event, you will need a test at the end of the day, so you could still go ahead and write it now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/584632 Title: composer changes font mid email To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/584632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 584632]
The try results look good to me, so you just need to include an automated regression test (mochitest) and you can ask a reviewer to approve it to be included in Firefox. You want to add a file patterned off something like this: https://dxr.mozilla.org/mozilla- central/source/layout/generic/test/test_bug970363.html You could base it off one of the tests you attached to this bug, but instead of asking the user to click, you have to synthesize a click using a function from EventUtils.js https://dxr.mozilla.org/mozilla- central/source/testing/mochitest/tests/SimpleTest/EventUtils.js, possibly synthesizeMouse. And instead of doing alert(), do something like is(myVariable, #text, selection should be in text node). You have to add your test's name to the file layout/generic/test/mochitest.ini, and then you can run it with ./mach mochitest-plain layout/generic/test/test_bug756984.html. It should fail before the patch is applied, and pass after the patch is applied. Thanks a ton for working on this! If you want feedback from me on if your test looks good before asking for review, please feel free to ask me via the feedback flag when uploading your patch. I'm probably less busy than the reviewers. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/584632 Title: composer changes font mid email To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/584632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 584632]
(In reply to Jorg K from comment #18) OK, when you say editor you mean composer. The component that allows the user to more or less WYSIWYG enter text (with fonts, colour, etc.) and pictures and creates HTML which is sent out. I mean the code under editor/ in the Gecko source tree, which handles the backend of editors for both Firefox and Thunderbird. Thunderbird's composer uses the Gecko editor for composing mail, but also has its own code that it puts on top, so the post you link to may be referring to that. This bug is in the editor itself, not the Thunderbird-specific code. The two bugs you mentioned are Thunderbird-specific and not related to the editor (note Product: Thunderbird, vs. this bug with Product: Core). That said, I actually haven't been paying much attention, and for all I know it could be someone has started working on editor again recently and I didn't notice. It doesn't seem so based on glancing at the log, but I didn't look at the commits in detail. If people are working on Thunderbird more, maybe they'll want to fix stuff in the editor too, since some high-profile Thunderbird bugs are really editor bugs. So we can still hope! :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/584632 Title: composer changes font mid email To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/584632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 584632]
(In reply to Jorg K from comment #12) This bug is still current at version 31.2.0 and 33 beta. Given that it's been carried over from bug 250539 created in 2004, it might be a good idea to one day do something about it ;-) Unfortunately, we have no one actively working on the editor component, so basically all editor bugs on indefinitely on hold. Occasionally one or two gets fixed here or there, but as things stand, I wouldn't count on it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/584632 Title: composer changes font mid email To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/584632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 888355] Re: users-admin should not allow creation of users with encrypted home who aren't asked for password on login
*** This bug is a duplicate of bug 577563 *** https://bugs.launchpad.net/bugs/577563 In 11.10, hitting the super/meta/whatever key and typing Users gets me Users and Groups (= users-admin) and also User Accounts (= gnome- control-center?). User Accounts is the one that shows up in System Settings... from the button in the upper right. If we're not supposed to use users-admin anymore, shouldn't it be removed? I upgraded from 11.04, if that helps. Should I file a separate bug? If it's no longer maintained, surely it should be uninstalled when the user upgrades. I can confirm that the new applet doesn't allow the same issue to arise, because it just doesn't allow you to do either of the two conflicting things. This seems like a, well, not really optimal solution to the problem, but I can't argue it's not a solution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/888355 Title: users-admin should not allow creation of users with encrypted home who aren't asked for password on login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/888355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 577563] Re: Automatic login fails and computer hangs (Lucid)
So does Ubuntu plan to switch to the new upstream applet in a future version? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/577563 Title: Automatic login fails and computer hangs (Lucid) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/577563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 888355] [NEW] users-admin should not allow creation of users with encrypted home who aren't asked for password on login
Public bug reported: Tested in Ubuntu 11.04 and 11.10. Steps to reproduce: 1) Go to Users and Groups (users-admin) 2) Click Add 3) Pick any name 4) Check Encrypt home folder to protect sensitive data 5) Click OK 6) Set any password 7) Check Don't ask for password on login 8) Click OK Expected result: An error is raised at some point, because the user will not be able to log in. Actual result: User is created normally. On login, the user is not prompted for their password, so the login fails. In Ubuntu 11.04, some cryptic error messages display and the GUI hangs; in Ubuntu 11.10, you're returned to the login screen. Since the user is not prompted for their password, the home directory cannot be decrypted, so login will fail. The two options are contradictory, and it should be impossible to select both. It might also be worthwhile if the program responsible for login (gdm?) detected this conflict and prompted the user for their password, ignoring the preference not to be prompted. However, the preferences are still logically contradictory, so the administrator should not be allowed to select both when creating a user. Bug #581303 and Bug #577563 are related, but were filed against gdm and eCryptfs. The problem should still be fixed in users-admin regardless of whether there's a workaround in gdm. ** Affects: gnome-system-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/888355 Title: users-admin should not allow creation of users with encrypted home who aren't asked for password on login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/888355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 577563] Re: Automatic login fails and computer hangs (Lucid)
In reply to comment #1: the bug is not invalid, and this is not a local issue. See bug #888355 for detailed steps to reproduce. The combination of these two preferences makes login impossible. The user administration tool should make such combinations impossible (bug #888355), but if they do occur somehow, gdm should ask for the password so that it can decrypt the home directory. At the very least, it should raise a clear error message. Currently it gives very cryptic errors and login hangs (on Ubuntu 11.04), or it gives no error message at all and just returns you to the login screen (on Ubuntu 11.10). There's definitely room for improvement here. ** Changed in: gdm (Ubuntu) Status: Invalid = Confirmed ** Changed in: gdm (Ubuntu) Status: Confirmed = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/577563 Title: Automatic login fails and computer hangs (Lucid) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/577563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 601380] Re: update-initramfs missing md root
I also hit this bug. We installed Ubuntu 10.04 fresh on LVM with no RAID, then I set up RAID and moved the root filesystem there using pvmove. Then when I tried running update-initramfs -u -k all, I got: $ sudo update-initramfs -k all -u update-initramfs: Generating /boot/initrd.img-2.6.32-25-server mkinitramfs: missing md root /dev/mapper/lvm_Boot-root /sys entry mkinitramfs: workaround is MODULES=most mkinitramfs: Error please report the bug update-initramfs: failed for /boot/initrd.img-2.6.32-25-server update-initramfs: Generating /boot/initrd.img-2.6.32-24-server mkinitramfs: missing md root /dev/mapper/lvm_Boot-root /sys entry mkinitramfs: workaround is MODULES=most mkinitramfs: Error please report the bug update-initramfs: failed for /boot/initrd.img-2.6.32-24-server update-initramfs: Generating /boot/initrd.img-2.6.32-22-server mkinitramfs: missing md root /dev/mapper/lvm_Boot-root /sys entry mkinitramfs: workaround is MODULES=most mkinitramfs: Error please report the bug update-initramfs: failed for /boot/initrd.img-2.6.32-22-server update-initramfs: Generating /boot/initrd.img-2.6.32-21-server mkinitramfs: missing md root /dev/mapper/lvm_Boot-root /sys entry mkinitramfs: workaround is MODULES=most mkinitramfs: Error please report the bug update-initramfs: failed for /boot/initrd.img-2.6.32-21-server MODULES=most is already set in initramfs.conf. I'm afraid to reboot now. -- update-initramfs missing md root https://bugs.launchpad.net/bugs/601380 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 601380] Re: update-initramfs missing md root
I deleted the file /etc/initramfs-tools/conf.d/driver-policy, which contained MODULES=dep, and the error messages went away. (The machine actually didn't boot in the end, but I think that was a GRUB problem, not an initramfs problem.) -- update-initramfs missing md root https://bugs.launchpad.net/bugs/601380 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 364089] Re: clock applet jumps in time when set to display seconds
I submitted a one-line patch to the upstream bug at https://bugzilla.gnome.org/show_bug.cgi?id=585668. Just change timeouttime = (G_USEC_PER_SEC - tv.tv_usec)/1000+1; to timeouttime = (G_USEC_PER_SEC - tv.tv_usec)/1000+20; in applets/clock/clock.c. Not such an elegant solution, but it works for me. -- clock applet jumps in time when set to display seconds https://bugs.launchpad.net/bugs/364089 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271706] Re: Toshiba Satellite U300 volume wheel sticking
If you're using 2.6.32 or later, you should be able to fidget with the contents of the force_release file in /sys to add the appropriate keycodes. The exact values can be found by experimentation, and you can add something to /etc/rc.local to set it on startup if you like (changes will not persist across startup). -- Toshiba Satellite U300 volume wheel sticking https://bugs.launchpad.net/bugs/271706 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 149042] Re: do-release-upgrade has no man page
** Also affects: server-papercuts Importance: Undecided Status: New -- do-release-upgrade has no man page https://bugs.launchpad.net/bugs/149042 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 289087] Re: Missing linux-image-debug packages and metapackages since Intrepid
** Also affects: server-papercuts Importance: Undecided Status: New -- Missing linux-image-debug packages and metapackages since Intrepid https://bugs.launchpad.net/bugs/289087 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271706] Re: Toshiba Satellite U300 volume wheel sticking
On 2.6.33-rc4 (presumably also 2.6.32), this mostly works: sudo bash -c 'echo 174,176,`cat /sys/devices/platform/i8042/serio0/force_release` /sys/devices/platform/i8042/serio0/force_release' (I figured out 174,176 by binary search. Protip: don't force_release anything in the range 0-127, since that will prevent keycodes like Ctrl- Alt-F1 from working . . . I had to hard-reset my computer.) The volume control no longer goes crazy when you turn the dial. But it's not a complete fix -- as noted, the dial sends three or four keypresses at once, so this results in the volume jumping instead of increasing smoothly. A quirk probably does need to be added to the kernel after all, which will cut out the duplicate keypresses. I'll look into writing that. -- Toshiba Satellite U300 volume wheel sticking https://bugs.launchpad.net/bugs/271706 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 498747] Re: Failed to build linux-image-2.6.33.rc1
I subscribed ubuntu-main-sponsors as described at: https://wiki.ubuntu.com/SyncRequestProcess. Sorry if this is incorrect. -- Failed to build linux-image-2.6.33.rc1 https://bugs.launchpad.net/bugs/498747 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271706] Re: Toshiba Satellite U300 volume wheel sticking
I took a stab at fixing the multiple keypresses thing, but eventually gave up. It doesn't seem worth it -- volume control works okay as-is, and I'm concerned that maybe in some cases it will start emitting only one keypress at a time and break any fix. We just need to wait for userspace support for this quirk detection, I guess? At any rate, now there's a very good workaround with 2.6.32+, it just needs to be applied automatically. -- Toshiba Satellite U300 volume wheel sticking https://bugs.launchpad.net/bugs/271706 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271706] Re: Toshiba Satellite U300 volume wheel sticking
Tomasz: I wrote the patch against 2.6.33-rc4, so I'm not surprised it doesn't apply to an older kernel. To clarify, are you still getting the user-visible symptoms even with the patch? When I tried it, I stopped getting the symptoms (volume indicator maxing out and flickering, keyboard freezing up, etc.). The volume wheel seemed sluggish/jittery, but it behaved much better. I did seem to still be getting similar codes from showkey -s, but I assumed those were somehow not relevant, since it mostly worked. I'll try out the sysfs thing when I get access to the machine again. Do you know where this sort of change would be added in HAL/DeviceKit? Are there any example patches? 2.6.32 means Lucid, so a quirk would still be needed if we wanted to fix it for Karmic, I guess (maybe not worth it). -- Toshiba Satellite U300 volume wheel sticking https://bugs.launchpad.net/bugs/271706 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271706] Re: Toshiba Satellite U300 volume wheel sticking
For anyone who's not clear how to test: compile a kernel using the instructions at https://wiki.ubuntu.com/KernelTeam/GitKernelBuild, with my patch applied. You'll have to work around bug 498747, for instance by doing git checkout v2.6.32 to use an older kernel so it compiles cleanly, or by applying the patch given there when (if) the compile process fails for 2.6.33. Compiling the kernel using those instructions took about two hours on my U305 (100 minutes to actually compile and then 20-30 minutes to make the .deb), so make sure you have something else to do. Say here whether or not it helps, and post the output of sudo dmidecode | grep -e Product -e Vendor. Also, whether or not you want to test, if anyone is affected by this but sudo dmidecode | grep Product does *not* output exactly either Satellite U305 or Satellite Pro U300, please say so so that your model can be included in the fix, since it won't be at present. Finally, thanks to everyone who posted critical info here, particularly jetdog, ktemkin, and the people who posted their DMI info -- I'm a PHP programmer and barely touch C code, so I was basically just copy-pasting to write the patch, and wouldn't have had a clue how to proceed without the exquisitely thorough explanations and pointers given earlier in the thread. -- Toshiba Satellite U300 volume wheel sticking https://bugs.launchpad.net/bugs/271706 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 498747] Re: Failed to build linux-image-2.6.33.rc1
Still happens with 2.6.33-rc4, on 9.10. -- Failed to build linux-image-2.6.33.rc1 https://bugs.launchpad.net/bugs/498747 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271706] Re: Toshiba Satellite U300 volume wheel sticking
The attached patch fixes the problem for my Satellite U305. I copy- pasted the same for Satellite Pro U300 on the assumption that will work too. ** Attachment added: diff http://launchpadlibrarian.net/37939758/diff -- Toshiba Satellite U300 volume wheel sticking https://bugs.launchpad.net/bugs/271706 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 398161] Re: pcspkr requires rmmod and modprobe to function
rmmod followed by modprobe seems to be the only way it works for me. I only reboot for distribution upgrades and (sometimes) hardware updates, so it's often a couple months since I rebooted and I forget to do this. So it's kind of a problem for me, because I use system beep for my alarm clock. I've now tried adding this to /etc/rc.local: rmmod pcspkr || true modprobe pcspkr || true rmmod pcspkr || true modprobe pcspkr || true (twice just in case that's necessary) and made sure it's executable. I guess I'll see if that works next time I reboot. -- pcspkr requires rmmod and modprobe to function https://bugs.launchpad.net/bugs/398161 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 388656] Re: Non-intuitive term Move to trash
The only reason to use Delete is because users are familiar with it from other platforms, IMO. I don't think Move to Trash is awkward, it's just that it will add to Windows users' confusion when using Linux for the first time, and right now that's a bad thing. Delete isn't lying, either, but it's misleading. Many users will expect that the file is gone forever. Move to Trash is a clear hint that the file isn't really gone. Cut is different because it has a conventional meaning that users are familiar with -- no one will mistake cut for delete forever. This isn't an issue of dictionary definitions, it's a matter of user expectations. So it's a tradeoff. I think the tradeoff right now tilts strongly in favor of usability for Windows users, and we should use Delete for now but reconsider the issue when our overall usability is good enough that we can sacrifice a few things like this (like Mac can). For now it's a very easy-to-implement usability fix that has only a minor downside. -- Non-intuitive term Move to trash https://bugs.launchpad.net/bugs/388656 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 491377] Re: mdadm uses one more spare that specified while creating a RAID5 array
From the man page: When creating a RAID5 array, mdadm will automatically create a degraded array with an extra spare drive. This is because building the spare into a degraded array is in general faster than resyncing the parity on a non-degraded, but not clean, array. This feature can be overridden with the --force option. I admit that I don't understand this at all (spotted this bug while looking for something else), but thought it might be helpful. -- mdadm uses one more spare that specified while creating a RAID5 array https://bugs.launchpad.net/bugs/491377 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 388656] Re: Non-intuitive term Move to trash
There are two obvious choices: 1) Use Move to Trash. This will confuse some users initially, and therefore cause a bad first impression. However, regular Ubuntu users will be more likely to understand what deletion actually does. 2) Use Delete. Users used to Windows will have an easier time, creating a better first impression. However, regular Ubuntu users will be more likely to assume that deletion from Nautilus is irreversible. Right now, IMO, we need to put top priority on first impressions. It's much better for a user to not know about the Trash, than to not use Ubuntu at all. Little things like this do add up and create an overall impression that Linux isn't as easy to use as Windows -- that's what Hundred Paper Cuts is all about. In the long run, Bug #1 should be fixed, and then we can switch back to correct terminology and educate users with nothing lost. Also, the concept of Trash should become obsolete in two or three years with a switch to btrfs and snapshotting. So I would suggest that we switch to Delete for the time being and see what happens. We can always switch back later with nothing lost. This is assuming we only have two options, though. What if we used Delete, but gave a strong visual cue that the file was going to the Trash? For instance, have the icon shrink and fly over to the Trash icon in the corner, like when a window minimizes in some setups? This would possibly be the best of both worlds, but might make it too hard to do to really be a paper cut. -- Non-intuitive term Move to trash https://bugs.launchpad.net/bugs/388656 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 495530] [NEW] update-manager is slow, obtrusive, and confusing
Public bug reported: Binary package hint: update-manager Here's a summary of the user experience when updates become available on Ubuntu: 1) Click on updates icon. 2) Wait five to ten seconds for the updates list to load. 3) The updates are confusing gibberish to the average user, frequently listing package names that the user stands no chance of recognizing. For instance, see http://www.computerworld.com/s/article/9126042/Living_free_with_Linux_2_weeks_without_Windows?taxonomyId=89pageNumber=4: Ubuntu's Update Manager . . . did tell me about numerous upgrades of other software I've never heard of, and certainly will never need. (If I ever needed xulrunner or Yelp, though, the Update Manager was here to help.) Of course, xulrunner is a critical component of Firefox, and Yelp is the GNOME help browser, so he probably used both. 4) Click Install Updates. 5) Wait five more seconds. 6) Type password. 7) Wait five or ten more seconds. 8) An Applying Changes window pops up, stealing focus (at least with my settings), and sits in the foreground until explicitly minimized. 9) Wait a while longer while everything works in the background. 10) Check back a while later to find that the updates are long since finished, but the window has been hanging around uselessly in the background for the entire time since then. By contrast, Windows Update goes more like this (from memory): 1) Click on updates icon. 2) Update dialog pops up almost instantly. It gives no confusing details by default. 3) When you confirm that you want to update, it minimizes to an icon again automatically, and tells you you can continue working. 4) When updates are finished, the icon just disappears (unless a reboot is required). Some key areas that should be improved: * The multisecond lag should be removed from multiple points. Maybe the update manager should create and populate the window in the background, and just un-hide it when the user clicks, or something. I don't know why there's a lag before it prompts you for your password. * When the user types in his password, the update manager should minimize immediately by default. Clicking it again could reopen it and keep it open for users who want to see the details. * If the update completes successfully and a reboot isn't required and the user hasn't explicitly reopened the update manager, it should exit automatically. Possibly this bug is too broad. This behavior is something that all desktop Ubuntu users will inevitably encounter multiple times per week, and at least one review of Ubuntu specifically pointed it out as a significant problem: The Ubuntu Update Manager had me longing for Windows Update. http://www.computerworld.com/s/article/9126042/Living_free_with_Linux_2_weeks_without_Windows?taxonomyId=89pageNumber=3 As such, I believe this would be a good candidate for a paper cut. The only issue is that it might not be trivial enough to fix -- however, I would think that at least some parts of it (e.g., minimizing it after Install Updates is clicked) could qualify as paper cuts by themselves, so I'll nominate this bug as a paper cut. ** Affects: hundredpapercuts Importance: Undecided Status: New ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Also affects: hundredpapercuts Importance: Undecided Status: New -- update-manager is slow, obtrusive, and confusing https://bugs.launchpad.net/bugs/495530 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 495530] Re: update-manager is slow, obtrusive, and confusing
1) Could you please explain why exactly this is not a small usability issue, in the default Ubuntu 9.10 install, that affects many people and is quick and easy to fix? It's a small usability issue, it's in the default Ubuntu 9.10 install, it affects all desktop users, and at least some parts are quick and easy to fix. Would it help if I broke it up into smaller pieces (e.g., update-manager should pop up immediately when icon is clicked)? 2) What makes this an idea and not a bug? Some examples of paper cuts that were fixed for Karmic: Downloads should go to ~/Downloads https://bugs.edge.launchpad.net/hundredpapercuts/+bug/204567 Default folders inside Home Folder (e.g. Documents, Music) should have special icons/emblems https://bugs.edge.launchpad.net/hundredpapercuts/+bug/126103 Ubuntu LiveCD Install icon confusing https://bugs.edge.launchpad.net/hundredpapercuts/+bug/154506 And many other things in the same vein. I identified several specific, concrete problems in an Ubuntu application, presented evidence that at least some are in fact problems, and suggested possible fixes. What about this is not really a bug, or less of a bug than the fixed paper cuts from Karmic I linked to? -- update-manager is slow, obtrusive, and confusing https://bugs.launchpad.net/bugs/495530 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 388656] Re: Non-intuitive term Move to trash
I have a friend who uses a Linux computer occasionally, and he complained it wasn't very usable. I asked him for an example, and he said that when he wanted to delete a file, he right-clicked and couldn't find any option to do it. He's not very computer-savvy and didn't think of trying other ways (like hitting the Delete key), so he blamed Linux. I'm glad to see someone else agrees that this is a problem. The problem is that people expect to see Delete and will look for it; they might not spot Move to Trash at all, or if they do, they might be unsure what it does. It makes it less clear that the file is easily recoverable, but that's not an advantage for users who can't find the option to begin with. The sort of user who doesn't know what the Recycling Bin/Trash is is exactly the sort of user who will probably get confused if standard options' names change. We have at least three anecdotal accounts of confusion over Move to Trash and even a usability study, so IMO the evidence is firmly on the side of using Delete. This could always be changed back later if it causes demonstrable problems; apparently they aren't significant enough for other OSes to change the terminology. (Konqueror (KDE) seems to use Move to Trash as well, FWIW, but Thunar (Xfce) uses Delete, and so does every version of Windows AFAIK. What does Mac do, out of curiosity? I'd bet Delete.) -- Non-intuitive term Move to trash https://bugs.launchpad.net/bugs/388656 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 478669] Re: beep doesn't beep
This affects me too. modprobe pcspkr resolves the issue. This might also affect other things that are really supposed to beep, like ping -a? (That doesn't seem to beep for me even with pcspkr loaded.) Either pcspkr should be enabled when beep is installed, or it should be enabled all the time and the programs that beep inappropriately should just be fixed. (FWIW, I use my PC as an alarm clock and overslept the day after upgrading because of this bug. :( ) -- beep doesn't beep https://bugs.launchpad.net/bugs/478669 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 317781] Re: Ext4 data loss
That looks like it removes the file before it does the rename, so it misses the special overwrite-by-rename workaround. This is slightly unsafe on any filesystem, since you might be left with no config file with the correct name if the system crashes in a small window, fsync() or no. Seemingly Python on Windows doesn't support an atomic rename operation at all. It might be simplest for it to only do the remove if rename throws an OSError, or only if the platform is Windows. Ideally it should call fsync() as well, of course. -- Ext4 data loss https://bugs.launchpad.net/bugs/317781 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 317781] Re: Ext4 data loss
The filesystem should be fixed to allocate blocks on *every* commit, not just ones overwriting existing files. alloc_on_commit mode has been added. Those who want to use it (and take the large associated performance hit) can use it. It's a tradeoff that is and should be in the hands of the individual system administrator. Personally, my machine almost never crashes, so I'd prefer the extra performance. What the application is doing in this case is broken anyway, and if it fixed that there would be no problem on ext4. As for the program -- fsync should *not* be inserted. (Though the unconditional os.remove() should be changed.) It's a bad thing to ritually fsync every file before the rename for a host of reasons described upthread. fsync() should preferably be used for config file updates, assuming those are reasonably rare, for a host of reasons described upthread. Otherwise, the user will click Save and then the preference change won't actually take effect if the system crashes shortly thereafter. This is true in any filesystem. On some filesystems (not just ext4: XFS certainly, maybe NFS?), you might also get some kind of other bad stuff happening. Explicit user saving of files/preferences/etc. should therefore invoke an fsync() in most cases: you want to make sure the change is committed to stable storage before giving confirmation to the user that it's saved. Text editors already do this, and no one seems to have complained. If Gaim updates its config file very often for some reason, though, they'd have to weigh the added reliability of fsync() against the performance hit (especially on filesystems like ext3). -- Ext4 data loss https://bugs.launchpad.net/bugs/317781 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 317781] Re: Ext4 data loss
If you accept that it makes sense to allocate on rename commits for overwrites of *existing* files, it follows that it makes sense to commit on *all* renames. Renaming a new file over an existing one carries the risk of destroying *old* data. If I create a new file and don't rename it to anything, it's possible I will lose *the new file only*, on any filesystem (unless I fsync()). This is universally considered an acceptable risk: losing up to a couple of minutes' work (but nothing earlier) in the event of a system crash. This is the exact risk carried by renaming a file to a name that doesn't exist -- unless you gratuitously delete the old file first, which is completely pointless on Unix and obviously destroys any hope of atomicity (if the system crashes/app dies/etc. between delete and rename). Only files for which atomicty matters are renamed that way -- which are precisely the files that would get the commit-on-rename treatment in other circumstances. Virtually all users of this atomicity technique appear to rename over the existing file, which is why almost all problems disappeared when users applied Ted's patches. Gaim only did otherwise as a flawed attempt to work around a quirk of the Windows API, in a way that wasn't atomic anyway, and that can be expected to be fixed in Gaim. -- Ext4 data loss https://bugs.launchpad.net/bugs/317781 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 317781] Re: Ext4 data loss
Guys, see comment 45 and comment 154. A workaround is going to be committed to 2.6.30 and has already been committed to Jaunty. The bug is fixed. There will be no data loss in these applications when using ext4, it will automatically fsync() in these cases (truncate then recreate, create new and rename over old). -- Ext4 data loss https://bugs.launchpad.net/bugs/317781 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 317781] Re: Ext4 data loss
@CowBoyTim Power failure during fsync() will result in a half-written file, but that's why the correct sequence is 1) Create new temp file 2) Write to new temp file 3) fsync() new temp file 4) rename() over old file If there's a power failure before or during step 3, the temp file will be partially written or not at all, but you'll still have the old data intact. A power failure during step 4 is no problem due to journaling. Therefore this really does give 100% assurance of durability, unless of course the hardware fails. But it's not perfect, therefore it's worthless is flawed logic anyway. -- Ext4 data loss https://bugs.launchpad.net/bugs/317781 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 317781] Re: Ext4 data loss
@Theodore, Well, that's not how I would describe it, although I admit in practice it has that effect. What's happening is that the journal is still being committed every 5 seconds, but dirty pages in the page cache do not get flushed out if they don't have a block allocation assigned to them. I think everyone understands why it's a bad idea to write data pages immediately (thanks for your detailed and clear explanations). But why can't the metadata writes be delayed as well? Why do they have to be written every five seconds instead of much later, whenever the data happens to get written? -- Ext4 data loss https://bugs.launchpad.net/bugs/317781 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
