@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
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
@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.
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
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
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
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
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
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.
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
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
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
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,
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
*** 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
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
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
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
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
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
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
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
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
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
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
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
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
** 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
** 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.
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
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
(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
(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
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.
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-
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
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
(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
(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
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
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.
(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
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
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
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
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
46 matches
Mail list logo
