[Bug 66483] Re: Sound crackles snaps when SDL volume not set at 100%
The alsa/sdl crackling issues were fixed in libsdl 1.2.14, which is in lucid, so I will close this bug. If you are still experiencing crackling issues with lucid, you are probably experiencing a new bug and should consider filing a new one. ** Changed in: sdl-mixer1.2 (Ubuntu) Status: Confirmed = Invalid ** Package changed: sdl-mixer1.2 (Ubuntu) = libsdl1.2 (Ubuntu) ** Changed in: libsdl1.2 (Ubuntu) Status: Invalid = Fix Released -- Sound crackles snaps when SDL volume not set at 100% https://bugs.launchpad.net/bugs/66483 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 538648] Re: [Intel GM45] Irregular sync flashes on 8086:2a42 (Needs i915.powersave quirk)
Andy, I have been using the kernel in comment 88 for about 6 hours now without flickering. -- [Intel GM45] Irregular sync flashes on 8086:2a42 (Needs i915.powersave quirk) https://bugs.launchpad.net/bugs/538648 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 538648] Re: [Intel GM45] Irregular sync flashes on 8086:2a42 (Needs i915.powersave quirk)
Robert, I have been using the latest maverick kernel for about 24 hours now: $ uname -r 2.6.34-2-generic I have an Inspiron 1545 and the Intel GM45: $ lspci | grep -i graphics 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) I was previously using the i915.powersave workaround. To test the newer kernel, I installed it, and disabled the i915.powersave workaround. To ensure that it was disabled, I rebooted into the lucid kernel again, and the flickering returned--about every few minutes, like before. Now I've been booted into the latest maverick kernel for about 24 hours now without seeing any flickering. Given how frequently I saw the flickering before, I think that it is likely that the maverick kernel has resolved the issue. However, given the flickering's nondeterministic nature, I will continue using the maverick kernel and post back if the flickering returns. Let me know if there is anything else I can do, short of using git- bisect, to help you track this down. -- [Intel GM45] Irregular sync flashes on 8086:2a42 (Needs i915.powersave quirk) https://bugs.launchpad.net/bugs/538648 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 538648] Re: [Intel GM45] Irregular sync flashes on 8086:2a42 (Needs i915.powersave quirk)
According to comment 5, we already know why the -15 kernel had no flicker issues: it had i915.powersave=0 by default. -- [Intel GM45] Irregular sync flashes on 8086:2a42 (Needs i915.powersave quirk) https://bugs.launchpad.net/bugs/538648 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 459437] Re: Firefox core dump after installation of Firebug extension
*** This bug is a duplicate of bug 449744 *** https://bugs.launchpad.net/bugs/449744 ** Bug watch added: Mozilla Bugzilla #510040 https://bugzilla.mozilla.org/show_bug.cgi?id=510040 ** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=510040 Importance: Unknown Status: Unknown -- Firefox core dump after installation of Firebug extension https://bugs.launchpad.net/bugs/459437 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 264196] Re: [intrepid] keyboard Repeat Keys is failing to adjust
Yes, here's the GUI instructions: Select the package in synaptic In menu, go to Package - Force version... Then select the version you want to downgrade to. Apply this downgrade, restart X or your computer, and you should be back to using intrepid's version. -- [intrepid] keyboard Repeat Keys is failing to adjust https://bugs.launchpad.net/bugs/264196 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 264196] Re: [intrepid] keyboard Repeat Keys is failing to adjust
The bug for inclusion of the patch into jaunty is bug 345397. It also has summarized mostly what you're looking for, including steps to reproduce, a theory of the problem, and a patch that you can test. Future discussion of one's experience with the jaunty patch should go there. Other discussion, including how to install the jaunty patch, and so on can go here: http://ubuntuforums.org/showthread.php?t=1101190 -- [intrepid] keyboard Repeat Keys is failing to adjust https://bugs.launchpad.net/bugs/264196 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 264196] Re: [intrepid] keyboard Repeat Keys is failing to adjust
Hi, I've put a patched version of xserver-xorg-input-evdev into my ppa using the patch that Ricardo Pérez López linked to. My ppa is here: https://launchpad.net/~jeff250/+archive/ppa It seems to have fixed the problem for me. If this works for others, and there are no side effects, perhaps we could coerce an Ubuntu dev to include the patch in the jaunty release. Note that if you want to test it, first undo any previous workaround that you may have use before, and then reboot to make sure that the problem comes back. Then install the new package (version 2.1.1-1ubuntu4~ppa1.1) from my ppa and reboot again (or just restart X if you are comfortable doing this). Then play around with the keyboard rate settings and see if they work. Also note any problems that you might have with the new package that you didn't have before. -- [intrepid] keyboard Repeat Keys is failing to adjust https://bugs.launchpad.net/bugs/264196 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 345397] Re: Please include this fix for jaunty
Hi, I've attached a first attempt at a proposed debdiff. As original poster indicates, this debdiff essentially includes this upstream patch: http://cgit.freedesktop.org/xorg/driver/xf86-input-evdev/patch/?id=ece72ce9e97adae23b1932dc1334f63669196d56 ** Attachment added: First attempt at debdiff for proposed patch http://launchpadlibrarian.net/24120350/xserver-xorg-input-evdev.diff -- Please include this fix for jaunty https://bugs.launchpad.net/bugs/345397 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 345397] Re: Please include this fix for jaunty
Steps to reproduce: 1. Use evdev for X keyboard input (on Intrepid, Jaunty should be default, i.e. if you have no xorg.conf file) 2. In gnome keyboard preferences, move repeat delay slider all the way to 'Long' 3. Move repeat rate slider all the way to 'Fast' 4. Test repeat rate at bottom of dialog Expected results: Very fast repeat rate Actual results: Normal repeat rate My understanding of the problem: It appears that the hardware repeat rate is tripping up Xorg's internal software repeat rate. If we set the software delay to be very long, i.e. such that it is longer than the hardware's delay, then the hardware's repeat will be triggered first. Once the hardware begins repeating key events, then the software's delay wait gets perpetually reset, so the software repeat rate will never be triggered. Some regression discussion: After patching evdev to ignore hardware repeat events, the hardware rate will be overridden by Xorg's software rate. E.g., before using this patch, you could use kbdrate in an rxvt to set the keyboard rate inside of X. After this patch, doing this has no effect. But I believe that this is OK and expected behavior. Any thoughts other concerns from any X gurus? Some further justification: This could close at least the following bugs: bug 264196 bug 289951 bug 290050 bug 290674 -- Please include this fix for jaunty https://bugs.launchpad.net/bugs/345397 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 264196] Re: [intrepid] keyboard Repeat Keys is failing to adjust
It seems to work just as well in intrepid. I've now uploaded intrepid packages to the ppa. Just make sure you use intrepid on the deb/deb-src lines, not jaunty. -- [intrepid] keyboard Repeat Keys is failing to adjust https://bugs.launchpad.net/bugs/264196 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 264196] Re: [intrepid] keyboard Repeat Keys is failing to adjust
I just tested that, and I can confirm the same regression on intrepid. Since you, Daniel Hollocher, and I can confirm the left/down arrow regression on intrepid when we use the patched evdev packages, we should probably let go of intrepid and focus on jaunty, since both Daniel and I cannot reproduce this regression on jaunty when using the patched evdev packages. I believe that the left/down regression was fixed somewhere in between intrepid and jaunty's xserver, since, when I cherry-picked the latest jaunty xserver packages onto my intrepid box, the regression was not present, even when using my patched evdev package. (Note that cherry picking packages, in general, is a risky idea in terms of overall stability, and I've since reverted the xserver packages on my intrepid box to the intrepid versions, but doing it can be useful for experiments like this.) I will leave the intrepid evdev packages in my ppa anyways, in case someone wants to still play around with them, but I don't advise using them, and it's too late for any fix like this to appear in intrepid anyways, whereas at least the chance for this fix to appear in jaunty is nonzero. And since jaunty thus far has *not* been shown to be affected by the left/down arrow regression, this is why we still need more testers for the ppa package in jaunty. As an aside, I also tested evdev-2.2.0 (a much newer version of the evdev in jaunty) on my jaunty box. I won't put it in my ppa, but it automatically reflects the patch for the repeat bug that I used to patch the package in my ppa archive. Like we would expect, I also tested it to solve repeat bug. So, if we cannot patch jaunty's evdev package to include the fix, the good news is that the first ubuntu version (likely jaunty+1) to use evdev-2.2.0 or greater will get this fix for free. -- [intrepid] keyboard Repeat Keys is failing to adjust https://bugs.launchpad.net/bugs/264196 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 345397] Re: Please include this fix for jaunty
Some more regression discussion: We tried backporting this patch to intrepid, but we found that this produced a regression: some keys such as the left/down arrow keys no longer repeated. The good news is that no one has produced this regression yet using the patched evdev packages in jaunty, but it is something to look out for. I think I'm going to try to see if I can get some more testers for this by posting some pleading in the Ubuntu Jaunty development forums, since we really need more than just a few people testing this. -- Please include this fix for jaunty https://bugs.launchpad.net/bugs/345397 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 278146] Re: [i915] [intrepid ] screen flickers while loading X, running xrandr or playing a video (i915)
unggnu, I can also confirm your workaround. With intrepid, I had been using the outdated version 2.3.2 of the intel xorg drivers to get around this issue. However, now that I've upgraded to jaunty and am now using the latest jaunty version, I can confirm that your workaround works with the latest intel drivers. -- [i915] [intrepid ] screen flickers while loading X, running xrandr or playing a video (i915) https://bugs.launchpad.net/bugs/278146 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 285795] Re: Intrepid - Changing laptop brightness makes gnome unresponsive
I believe that this is a duplicate of #261721. -- Intrepid - Changing laptop brightness makes gnome unresponsive https://bugs.launchpad.net/bugs/285795 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 280506] Re: I/O error booting when using Intrepid kernel
Gah, this appears to be an hpa issue. This is a Dell laptop that used to have one of those MediaDirect partitions once upon a time. With the hardy kernel, /sys/module/libata/parameters/ignore_hpa is 1. But with the intrepid kernel, /sys/module/libata/parameters/ignore_hpa is 0, so apparently handling of hpa has changed here. (This was originally a Breezy install, so ignoring hpa must go a long way back...) I used a tool called MHDD (ran it in FreeDOS) to remove the hpa from the drive. For posterity, once you're in the program, select the disk giving you issues. Then type the nhpa command. Although I've fixed this in my personal circumstance, my solution may be considered cheating, so I will let someone more knowledgeable decide whether to close this bug or not. -- I/O error booting when using Intrepid kernel https://bugs.launchpad.net/bugs/280506 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 280506] [NEW] I/O error booting when using Intrepid kernel
Public bug reported: I dist-upgraded to Intrepid from Hardy, but now I cannot boot using the Intrepid kernel (2.6.27-6-generic). Reiserfs reports an unreadable block and kicks me to a root shell. Dmesg reports errors of the following kind (full file attached): [ 23.807828] Buffer I/O error on device sda5, logical block 67360508 [ 23.807892] attempt to access beyond end of device [ 23.807895] sda: rw=0, want=156296315, limit=153774180 . . . The block that reiserfs reports is bad is block 16840127, and indeed running the following command fails and produces more dmesg errors: dd if=/dev/sda5 of=/root/block bs=4096 count=1 skip=16840127 But the above command (as well as booting in general) works fine using the Hardy kernels. Here is fdisk -l output: Disk /dev/sda: 78.7 GB, 78732380160 bytes 255 heads, 63 sectors/track, 9572 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0xe686f016 Device Boot Start End Blocks Id System /dev/sda1 11216 9767488+ 83 Linux /dev/sda21281972967866592+ f W95 Ext'd (LBA) /dev/sda4 *12171280 514080b W95 FAT32 /dev/sda51344972967360545 83 Linux /dev/sda612811343 505984+ 82 Linux swap / Solaris And here is my fstab file: # /etc/fstab: static file system information. # # file system mount point type options dump pass proc/proc procdefaults0 0 # /dev/sda1 UUID=3415ef48-c558-4546-8779-95d03f4a9e82 / reiserfs notail,noatime 0 1 # /dev/sda4 UUID=4464-0805 /dosvfatdefaults,utf8,umask=007,gid=46 0 1 # /dev/sda5 UUID=aa668c2e-2439-41b3-89f7-cf7069b51970 /home reiserfs defaults,noatime 0 2 # /dev/sda6 UUID=9b024922-9749-40b2-8a74-c9348639e8da none swap sw 0 0 /dev/scd0 /media/cdrom0 iso9660,udf user,noauto 0 0 #none /debug debugfs defaults 0 0 And the dmesg log will be attached. I will also momentarily post the reiser fsck log. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- I/O error booting when using Intrepid kernel https://bugs.launchpad.net/bugs/280506 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 280506] Re: I/O error booting when using Intrepid kernel
** Attachment added: dmesg log http://launchpadlibrarian.net/18356898/dmesglog -- I/O error booting when using Intrepid kernel https://bugs.launchpad.net/bugs/280506 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 280506] Re: I/O error booting when using Intrepid kernel
** Attachment added: Shows fsck.reiserfs error on device /dev/sda5 http://launchpadlibrarian.net/18357007/checkfslog -- I/O error booting when using Intrepid kernel https://bugs.launchpad.net/bugs/280506 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 156027] Re: Rhythmbox displays error, crashes using monoscope visualization
Not necessary--I can no longer reproduce this in hardy. Feel free to change bug status to reflect this. -- Rhythmbox displays error, crashes using monoscope visualization https://bugs.launchpad.net/bugs/156027 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 191508] Re: Compiz doesn't show shadows on Hardy
No shadows with my Geforce 8600 GT with a fresh 64-bit hardy install. Other effects seem to be working just fine. -- Compiz doesn't show shadows on Hardy https://bugs.launchpad.net/bugs/191508 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 156027] Re: Rhythmbox displays error, crashes using monoscope visualization
OK, I've attached that. ** Attachment added: Backtrace with gstreamer debug symbols http://launchpadlibrarian.net/10788613/gdb-rhythmbox.txt -- Rhythmbox displays error, crashes using monoscope visualization https://bugs.launchpad.net/bugs/156027 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 156027] Re: Rhythmbox displays error, crashes using monoscope visualization
I have an i915 video adapter. I can reproduce it with compiz both on and off. I noticed that I cannot reproduce it on my other computer, which has a Geforce 7600GT using the nVidia binary driver blob fwiw. I've attached a backtrace. I noticed that I originally used the word crash, but this was probably poor word choice--the program stops responding. I got the attached backtrace by doing the following: 1. Switch to non-monoscope visualization. 2. Switch back to monoscope visualization. 3. Acknowledge error message described in original bug report by pressing OK. 4. Quit rhythmbox. At this point, rhythmbox stops responding, so I sent it a STOP signal and got the backtrace. I'm hoping that getting the backtrace like this is just as good as anything, but let me know if that's not the case. ** Attachment added: Backtrace of where rhythmbox stops responding http://launchpadlibrarian.net/10146872/gdb-rhythmbox.txt -- Rhythmbox displays error, crashes using monoscope visualization https://bugs.launchpad.net/bugs/156027 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 156027] Re: Rhythmbox displays error, crashes using monoscope visualization
This also seems to be reproducible using both xv and non-xv video output fwiw. -- Rhythmbox displays error, crashes using monoscope visualization https://bugs.launchpad.net/bugs/156027 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 156027] Rhythmbox displays error, crashes using monoscope visualization
Public bug reported: Binary package hint: rhythmbox Rhythmbox displays the following error when selecting the monoscope visualization after another visualization is already used: Unable to start visualization Failed to link new visual effect into the Gstreamer pipeline This tends to leave Rhythmbox in a bad state where trying to do anything afterwards will lead to a crash. However, when restarting Rhythmbox after such a crash, then the monoscope visualization is already selected and works fine. However, selecting a different visualization and then the monoscope visualization again brings back the error, which will create a bad state that will ultimately lead to a crash again. Totem does not have this issue with the monoscope visualization. ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- Rhythmbox displays error, crashes using monoscope visualization https://bugs.launchpad.net/bugs/156027 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 127101] Re: laptop hangs when switching video mode
To reiterate more of what has already been said, I've been using the xserver-xorg-video-intel_2.1.1-0ubuntu9~pcjc2_i386.deb package for a few days, and I cannot reproduce the crash any longer. I also haven't noticed any regressions. -- laptop hangs when switching video mode https://bugs.launchpad.net/bugs/127101 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 127101] Re: laptop hangs when switching video mode
Hi, I tried the git xserver-xorg-video-intel package, and I can also confirm that DRI is not working with this package. Here is the error: libGL error: drmMap of framebuffer failed (Invalid argument) libGL error: reverting to (slow) indirect rendering Perhaps Ubuntu's libdrm or drm kernel modules aren't recent enough for the git package? I also tried the xserver-xorg-core package with patch 120 dropped. The rectangle crash is still reproducible using this package using Juan's steps. (Also, the problem that patch 120 fixes is reintroduced.) -- laptop hangs when switching video mode https://bugs.launchpad.net/bugs/127101 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 127101] Re: laptop hangs when switching video mode
For Gutsy users, the newer gdm always restarts X. The following report has information on that: http://bugzilla.gnome.org/show_bug.cgi?id=326771 But this can be reproduced without any logging out though anyways (see Juan's three steps for reproduction). -- laptop hangs when switching video mode https://bugs.launchpad.net/bugs/127101 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 127101] Re: laptop hangs when switching video mode
I can reproduce this using Juan's steps, even running -12ubuntu8. I've attached a Xorg.0.log for one of the crashes I reproduced, but there doesn't appear to be any relevant errors. Let me know if there's anything else I can do to help debug this. ** Attachment added: Xorg.0.log for crash http://launchpadlibrarian.net/9613338/Xorg.0.log -- laptop hangs when switching video mode https://bugs.launchpad.net/bugs/127101 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 141593] Re: Gnome-panel fails to load applets after re-login
Yes, when I kill those processes before logging in again, I cannot reproduce the bug. -- Gnome-panel fails to load applets after re-login https://bugs.launchpad.net/bugs/141593 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 141593] Re: Gnome-panel fails to load applets after re-login
Accidentally assigned to wrong package. ** Changed in: gnome-panel (Ubuntu) Sourcepackagename: gnome-applets = gnome-panel -- Gnome-panel fails to load applets after re-login https://bugs.launchpad.net/bugs/141593 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 141593] Gnome-panel fails to load applets after re-login
Public bug reported: Binary package hint: gnome-applets After logging in, then logging out, and then logging back in again (or logging in, pressing ctrl-alt-backspace, and logging back in again), gnome-panel fails to load some applets with errors such as the following: The panel encountered a problem while loading 'OAFIID:GNOME_GWeatherApplet'. Do you want to delete the applet from your configuration? When I run gnome-panel from the terminal, it outputs: ** (gnome-panel:6140): WARNING **: panel-applet-frame.c:1278: failed to load applet OAFIID:GNOME_GWeatherApplet: Failed to resolve, or extend '!prefs_key=/apps/panel/applets/applet_1/prefs;background=none:;orient=up;size=x-small;locked_down=false ** (gnome-panel:6140): WARNING **: panel-applet-frame.c:1278: failed to load applet OAFIID:GNOME_MixerApplet: Failed to resolve, or extend '!prefs_key=/apps/panel/applets/applet_0/prefs;background=none:;orient=up;size=x-small;locked_down=false Deleting and re-adding the applets does not seem to help. I can only get them back by doing a full reboot. I can reproduce this on two gutsy machines that are all up-to-date. I'm running gnome-panel 2.20.0.1. ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: New -- Gnome-panel fails to load applets after re-login https://bugs.launchpad.net/bugs/141593 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 141593] Re: Gnome-panel fails to load applets after re-login
** Attachment added: Example of the gnome-panel error http://launchpadlibrarian.net/9445789/Screenshot-Error.png -- Gnome-panel fails to load applets after re-login https://bugs.launchpad.net/bugs/141593 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 66483] Re: Sound crackles snaps when SDL volume not set at 100%
Jacob: re: supertux Yes, I believe you are correct concerning supertux's lack of use of sdl-mixer. I was under the impression that it did because it used to, as the 0.1.x (stable) version uses sdl-mixer. However, it appears that supertux 0.3 (preview) no longer does. -- Sound crackles snaps when SDL volume not set at 100% https://bugs.launchpad.net/bugs/66483 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 122937] Re: Rhythmbox desktop launcher icon appears too small
I use tango. However, I can reproduce this from a fresh Tribe-4 live cd boot-up, so human as well. In fact, I've been playing around, and I've found some other icons that do this too. I've attached a screenshot that shows all of the icons of the default ones in the menus that have this problem for me (on the left) and a portion of the ones that don't have this issue (on the right). ** Attachment added: Screenshot, small icons on the left, regular icons on the right http://launchpadlibrarian.net/8766257/Screenshot.png -- Rhythmbox desktop launcher icon appears too small https://bugs.launchpad.net/bugs/122937 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 66483] Re: Sound crackles snaps when SDL volume not set at 100%
Here are my results: $ SDL_AUDIODRIVER=assdf ./test-sdl-audio SDL_OpenAudio() failed: No available audio device $ SDL_AUDIODRIVER=alsa ./test-sdl-audio desired: 16 bit signed audio (stereo) at 44100 Hz obtained: 16 bit signed audio (stereo) at 44100 Hz $ SDL_AUDIODRIVER=oss ./test-sdl-audio SDL_OpenAudio() failed: No available audio device $ SDL_AUDIODRIVER=dsp ./test-sdl-audio desired: 16 bit signed audio (stereo) at 44100 Hz obtained: 16 bit signed audio (stereo) at 44100 Hz 'SDL_AUDIODRIVER=dsafd supertux' had sound, so I'm going to disregard this game for the moment, at least for this bug report and as long as we are focusing in on sdl-mixer. I downloaded neverball so that we can compare apples to apples here, and I ended up with similar results as Jacob. 'SDL_AUDIODRIVER=dsp neverball' results in crystal clear sound; however, 'SDL_AUDIODRIVER=alsa neverball' results with the static problem. The static problem consists in music playing staticy when not at 100% in- game volume; it plays crystal clear at 100% volume. Also, sound was slightly staticy at ANY volume. It is less staticy than the music is though. It was more obvious after I turned off the music and cranked up my speaker volume. Again, there is no static at all with oss/dsp. -- Sound crackles snaps when SDL volume not set at 100% https://bugs.launchpad.net/bugs/66483 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83210] Re: [Feisty] PNG desktop image dimensions displayed divided by 10
Using gutsy, I was still experiencing this until I did a... rm -r ~/.thumbnails It looks like the bad wallpaper metadata was saved in my thumbnail cache. -- [Feisty] PNG desktop image dimensions displayed divided by 10 https://bugs.launchpad.net/bugs/83210 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 66483] Re: Sound crackles snaps when SDL volume not set at 100%
I was looking at the alsa code this evening and noticed that putting the following line into ~/.asoundrc should be a workaround for my issue: defaults.pcm.dmix_max_periods -1 It seems to have solved the problem without any side effects, but only for some applications. Without this option, supertux is staticy, yet with it, it isn't. However, rott is just as staticy with this option as without. I don't really understand the alsa code enough to truly grok this option's implications. If you find that it resolves some issues, such as with supertux, it might be worth posting in the alsa bug thread that I started. -- Sound crackles snaps when SDL volume not set at 100% https://bugs.launchpad.net/bugs/66483 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 66483] Re: Sound crackles snaps when SDL volume not set at 100%
I have this problem for both feisty and gutsy with snd-hda-intel. Here's the output of alsa-info.sh: http://pastebin.ca/630434 Adding slowptr 1 doesn't help, but it wasn't expected to since this is supposed to already be enabled on gutsy's version of alsa. -- Sound crackles snaps when SDL volume not set at 100% https://bugs.launchpad.net/bugs/66483 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 66483] Re: Sound crackles snaps when SDL volume not set at 100%
I've narrowed my issue down to a commit and detailed it here in the following Alsa bug report: https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3253 I don't think that everyone here has the exact same bug as I do, but you might be interested in following the report nonetheless. -- Sound crackles snaps when SDL volume not set at 100% https://bugs.launchpad.net/bugs/66483 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 122937] Rhythmbox desktop launcher icon appears too small
Public bug reported: Binary package hint: rhythmbox After the gutsy update to Rhythmbox 0.11.1, when creating a desktop icon for Rhythmbox, the icon appears way too small. To reproduce, go to Applications - Sound Video - Right click on Rhythmbox - Add this launcher to desktop. This issue was not present prior the update to Rhythmbox 0.11.1. ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- Rhythmbox desktop launcher icon appears too small https://bugs.launchpad.net/bugs/122937 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 122937] Re: Rhythmbox desktop launcher icon appears too small
** Attachment added: Screenshot of issue. http://launchpadlibrarian.net/8229171/rhythmbox-icon.png -- Rhythmbox desktop launcher icon appears too small https://bugs.launchpad.net/bugs/122937 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 111257] Re: totem crashes with 'BadAlloc (insufficient resources for operation)' when using compiz and xserver-xorg-video-intel driver
Setting the video output plugin to X Window System ( No XV ) means that you won't be getting xv video acceleration. This puts more strain on the CPU during video playback, and higher resolution videos can play jerkily. -- totem crashes with 'BadAlloc (insufficient resources for operation)' when using compiz and xserver-xorg-video-intel driver https://bugs.launchpad.net/bugs/111257 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83210] Re: [Feisty] PNG desktop image dimensions displayed divided by 10
Will the fix be released in Ubuntu in time for Feisty? -- [Feisty] PNG desktop image dimensions displayed divided by 10 https://bugs.launchpad.net/bugs/83210 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 103177] Re: boot-time race condition initializing md
In the grub menu, select the kernel you want to boot with and then press 'e'. Then select the kernel line and press 'e'. Add a space and 'break=mount' to the end of the line and press enter. Press b to boot. You'll get thrown to busybox. Wait a few seconds, and then press ctrl+d. Alternatively, the way to update the kernel would be to find an old live cd that you know works with the array (I used an old Dapper cd). Then mount your root partition to a directory with a command similar to 'sudo mount /dev/md0 /mnt'. Then 'sudo chroot /mnt'. Your shell will now behave as if your mounted partition is now the root directory until you type exit, so you can wget the new initramfs-tools or the new kernel package or whatever you need and dpkg -i it. -- boot-time race condition initializing md https://bugs.launchpad.net/bugs/103177 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 103177] Re: boot-time race condition initializing md
I should also add that if you're trying to update the kernel because of the bug in the -14.23 kernel, the break=mount fix won't help get around that bug. It just gets around the initramfs bug that this bug report is about. To get around the -14.23 kernel bug, you're going to either have to chroot like I mentioned in my last comment, or boot using an older kernel, like a -13. -- boot-time race condition initializing md https://bugs.launchpad.net/bugs/103177 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 103177] Re: boot-time race condition initializing md
The newer initramfs-tools package has resolved this issue for me. Jose, your bug may be related to the bug in kernel 2.6.20-14.23. If so, try updating to 2.6.20-15, which should fix it. -- boot-time race condition initializing md https://bugs.launchpad.net/bugs/103177 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 103177] Re: boot-time race condition initializing md
I can't speak for Johan, but when I do 1) and 2), /dev/md0 is created after a couple of seconds when the sd? devices are created and before pressing ctrl+d. -- boot-time race condition initializing md https://bugs.launchpad.net/bugs/103177 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 96870] Re: 2.6.20-13 breaks internal SD card reader and suspend to memory
The SD reader problem is fixed for me with today's kernel update (2.6.20-14.23). -- 2.6.20-13 breaks internal SD card reader and suspend to memory https://bugs.launchpad.net/bugs/96870 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 96870] Re: 2.6.20-13 breaks internal SD card reader and suspend to memory
I recently experienced the same regression with my Ricoh card reader. I should add that the device is being created successfully. It's just not being mounted automatically. 'sudo mount /dev/mmcblk0p1 /mnt' allows me to access my data on my SD card. [EMAIL PROTECTED]:~$ id uid=1000(jeffrey) gid=1000(jeffrey) groups=4(adm),20(dialout),24(cdrom),25(floppy),29(audio),30(dip),44(video),46(plugdev),106(lpadmin),110(scanner),112(admin),1000(jeffrey) [EMAIL PROTECTED]:~$ id hal id: hal: No such user [EMAIL PROTECTED]:~$ id haldaemon uid=108(haldaemon) gid=108(haldaemon) groups=108(haldaemon),24(cdrom),25(floppy),46(plugdev),120(powerdev) [EMAIL PROTECTED]:~$ uname -a Linux jeff-laptop 2.6.20-14-generic #2 SMP Mon Apr 2 20:37:49 UTC 2007 i686 GNU/Linux [EMAIL PROTECTED]:~$ lspci | grep -i ricoh 02:01.0 FireWire (IEEE 1394): Ricoh Co Ltd Unknown device 0832 02:01.1 Generic system peripheral [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19) 02:01.2 System peripheral: Ricoh Co Ltd Unknown device 0843 (rev 01) 02:01.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 0a) 02:01.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 05) ** Attachment added: As per https://wiki.ubuntu.com/DebuggingRemovableDevices; http://librarian.launchpad.net/7258841/gvm.log -- 2.6.20-13 breaks internal SD card reader and suspend to memory https://bugs.launchpad.net/bugs/96870 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 96870] Re: 2.6.20-13 breaks internal SD card reader and suspend to memory
** Attachment added: As per https://wiki.ubuntu.com/DebuggingRemovableDevices; http://librarian.launchpad.net/7258844/lshal.txt -- 2.6.20-13 breaks internal SD card reader and suspend to memory https://bugs.launchpad.net/bugs/96870 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 96870] Re: 2.6.20-13 breaks internal SD card reader and suspend to memory
** Attachment added: dmesg.txt as per https://wiki.ubuntu.com/DebuggingRemovableDevices; http://librarian.launchpad.net/7258856/dmesg.txt -- 2.6.20-13 breaks internal SD card reader and suspend to memory https://bugs.launchpad.net/bugs/96870 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 96870] Re: 2.6.20-13 breaks internal SD card reader and suspend to memory
** Attachment added: udev.log as per https://wiki.ubuntu.com/DebuggingRemovableDevices; http://librarian.launchpad.net/7258857/udev.log -- 2.6.20-13 breaks internal SD card reader and suspend to memory https://bugs.launchpad.net/bugs/96870 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 103177] Re: boot-time race condition initializing md
Just to reiterate what I said in my other bug report, my /dev/sd* drives aren't ever created when I'm thrown to busybox unless I boot with break=mount. Then they magically appear without having to do anything, and /dev/md0 is created successfully too. I've attached a picture of my display after being thrown to busybox. (It looks almost identical to Jeff Balderson's.) ** Attachment added: Picture of my display after being thrown to busybox http://librarian.launchpad.net/7221042/busybox.jpg -- boot-time race condition initializing md https://bugs.launchpad.net/bugs/103177 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75681] Re: boot-time race condition initializing md
I suspect that this is the issue I'm experiencing with my desktop. My root partition is /dev/md0, but after upgrading to feisty, my system is no longer boots and throws me to busybox. I noticed in busybox that my sata drives are missing from /dev, which explains why the array isn't being mounted. One workaround that seems to work so far (although I have not thoroughly tested it) is booting the kernel with the option 'break=mount'. This seems to somehow fix everything, as by the time I get thrown to busybox, my drives are already in /dev, as well as my raid array, so I just press ctrl+d to continue booting. -- boot-time race condition initializing md https://launchpad.net/bugs/75681 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 103177] Re: boot-time race condition initializing md
Since my bug was marked a duplicate of this one, is there any more information that I can provide? (Gah, this might get confusing with two Jeff's!) -- boot-time race condition initializing md https://bugs.launchpad.net/bugs/103177 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 102933] Re: /dev/md0 fails to mount on boot
udev108-0ubuntu3 volumeid108-0ubuntu3 libvolume-id0 108-0ubuntu3 mdadm 2.5.6-7ubuntu5 No packages found matching evms. No packages found matching lvm2. No packages found matching lvm-common. dmsetup 2:1.02.08-1ubuntu10 libdevmapper1.022:1.02.08-1ubuntu10 -- /dev/md0 fails to mount on boot https://bugs.launchpad.net/bugs/102933 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83231] Re: linux software RAID not working after herd 3 installation..
Thanks Quikee. I tried your latest, most elegant workaround, and it worked great here. I don't think that this is an lvm problem, especially since me and a lot of the others here aren't using lvm. I am going to add udev to affected packages, since upgrading to udev-105 from debian unstable also fixed this bug. (However, this had other understandable side-effects.) ** Also affects: udev (Ubuntu) Importance: Undecided Status: Unconfirmed -- linux software RAID not working after herd 3 installation.. https://bugs.launchpad.net/bugs/83231 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 102933] /dev/md0 fails to mount on boot
Public bug reported: Binary package hint: udev Since upgrading from edgy to feisty beta1, my system gets thrown to busybox when booting. In busybox, /dev/md0 is missing, as well as the /dev/sd? drives that would normally constitute the array. This issue remains present with udev 108-0ubuntu2 and initramfs-tools 0.85eubuntu8. I do not use lvm. Known workarounds: (1) Boot with break=mount. Wait a couple of seconds, cd to /dev, and ensure that /dev/sd? and /dev/md0 are now there. Ctrl+d to continue booting normally. Or (2) install udev 0.105-4 from debian unstable. (This is undesirable for other reasons.) Or (3) Apply the workaround mentioned here involving adding an attached udevSettle script to /usr/share/initramfs-tools/scripts/init-premount/: https://launchpad.net/ubuntu/+source/initramfs-tools/+bug/83231 ** Affects: udev (Ubuntu) Importance: Undecided Status: Unconfirmed -- /dev/md0 fails to mount on boot https://bugs.launchpad.net/bugs/102933 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 102933] Re: /dev/md0 fails to mount on boot
** Description changed: Binary package hint: udev Since upgrading from edgy to feisty beta1, my system gets thrown to busybox when booting. In busybox, /dev/md0 is missing, as well as the /dev/sd? drives that would normally constitute the array. This issue remains present with udev 108-0ubuntu2 and initramfs-tools 0.85eubuntu8. I do not use lvm. Known workarounds: (1) Boot with break=mount. Wait a couple of seconds, cd to /dev, and ensure that /dev/sd? and /dev/md0 are now there. Ctrl+d to continue booting normally. Or (2) install udev 0.105-4 from debian unstable. (This is undesirable for other reasons.) Or (3) Apply the workaround mentioned here involving adding an attached udevSettle script to /usr/share/initramfs-tools/scripts/init-premount/: - https://launchpad.net/ubuntu/+source/initramfs-tools/+bug/83231 + https://launchpad.net/ubuntu/+source/initramfs-tools/+bug/83231/comments/19 ** Description changed: Binary package hint: udev Since upgrading from edgy to feisty beta1, my system gets thrown to busybox when booting. In busybox, /dev/md0 is missing, as well as the /dev/sd? drives that would normally constitute the array. This issue remains present with udev 108-0ubuntu2 and initramfs-tools 0.85eubuntu8. I do not use lvm. Known workarounds: (1) Boot with break=mount. Wait a couple of seconds, cd to /dev, and ensure that /dev/sd? and /dev/md0 are now there. Ctrl+d to continue booting normally. - Or (2) install udev 0.105-4 from debian unstable. (This is undesirable for other reasons.) + Or (2) Install udev 0.105-4 from debian unstable. (This is undesirable for other reasons.) Or (3) Apply the workaround mentioned here involving adding an attached udevSettle script to /usr/share/initramfs-tools/scripts/init-premount/: https://launchpad.net/ubuntu/+source/initramfs-tools/+bug/83231/comments/19 -- /dev/md0 fails to mount on boot https://bugs.launchpad.net/bugs/102933 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75681] Re: boot-time race condition initializing md
Reinhard, I tried your Ubuntu deb (105-4), and it brought the bug back for me consistently. Then I reverted to debian unstable's version (0.105-4), and now I'm booting consistently correctly again. This is interesting. Clearly what is causing my bug must be in the Ubuntu packaging? I've already tried gouging out the Ubuntu patches in debian/patches of the Ubuntu package that you gave me (and hacking debian/rules to accommodate) and then repackaging and reinstalling it then, but still no go. This as far as I have time to play around with this tonight, but before I try again in the near future, does anyone have any ideas? -- boot-time race condition initializing md https://launchpad.net/bugs/75681 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75681] Re: boot-time race condition initializing md
Reinhard Tartler, am I correct in assuming that you forgot to upload udev_105.orig.tar.gz? Otherwise, where are we expected to get it? Thanks. To mirror others' sentiments, I do suspect that there are a plurality of bugs with similar symptoms being voiced here. -- boot-time race condition initializing md https://launchpad.net/bugs/75681 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75681] Re: boot-time race condition initializing md
I tried upgrading to 0.105-3 from debian unstable, and it fixed this bug for me (I used prevu to accomplish this). Devices for my drives are now created correctly, and /dev/md0 is now created and mounted correctly at boot-up. Unfortunately, as a side-effect, network-manager is no longer seeing my wireless card now (gah!). I'll have to investigate this, but I wasn't anticipating upgrading to debian unstable's version to be painless. -- boot-time race condition initializing md https://launchpad.net/bugs/75681 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75681] Re: boot-time race condition initializing md
I doubt that this is the ideal place to say this, but in case anyone else goes down this path, getting my wireless working again involved copying /lib/udev/firmware-helper from the old feisty udev package to the same location once the new udev from debian unstable is installed. Apparently the debian udev package does not include this file. This goes to show that ubuntu's udev package is indeed very tricked out. ;-) -- boot-time race condition initializing md https://launchpad.net/bugs/75681 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 80666] Re: Azureus crashed when starting a new torrent
There's a workaround here that worked well for me: http://ubuntuforums.org/showthread.php?t=370473 -- Azureus crashed when starting a new torrent https://launchpad.net/bugs/80666 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 86434] Re: Azureus won't start in Feisty Herd 4
I suspect that this is a duplicate of #80666. -- Azureus won't start in Feisty Herd 4 https://launchpad.net/bugs/86434 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 30146] Re: gnome-panel doesn't show all menu items
This bug seems fixed for the primary menu (the one with Accessories, Games, Graphics, etc., a la the attachment on comment1), but not for its sub-menus (see attachment of this comment). I'm using 2.17.92-0ubuntu4. ** Attachment added: Screenshot of bug. http://librarian.launchpad.net/6725395/panel2.png -- gnome-panel doesn't show all menu items https://launchpad.net/bugs/30146 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 30146] Re: gnome-panel doesn't show all menu items
I think I've figured out why the package manager seems to trip it up. It presents a unique case, where both the contents of /usr/share/pixmaps and /usr/share/applications change at the same time, or at least in between menu browsing. Here's an example that I've found to rigorously reproduce this bug: 0. (Gnome ,menu must be on bottom panel.) 1. Browse menu until bug no longer is present. 2. sudo cp /usr/share/applications/totem.desktop /usr/share/applications/test.desktop 3. sudo touch /usr/share/pixmaps/test.png 4. Browse menu and notice that the bug appears The important thing is that you don't browse the menu in between steps 1 and 4, because just doing either step 2 or step 3 does not seem to produce the bug. Just when both happen in between menu browsing does it occur. Also, steps 2 and 3 can be performed in reverse order, i.e. step 3 then step 2. And also, it seems that to reproduce this, it needs a real .desktop file in the applications directory, whereas a phony touch'ed png file will suffice (although so will a real image) in triggering the bug. And, of course, to reproduce it again: 1. Browse menu until bug is no longer present 2. sudo rm /usr/share/applications/test.desktop 3. sudo rm /usr/share/pixmaps/test.png 4. Browse menu and notice that the bug appears -- gnome-panel doesn't show all menu items https://launchpad.net/bugs/30146 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 30146] Re: gnome-panel doesn't show all menu items
Right, I think so--I've been speaking about the bug where the menus or sub-menus from the gnome menu bar are sometimes displayed too short and have arrows on the top and bottom as if they haven't enough screen height to display (even though they do) when the gnome menu bar is on a panel on the bottom of the screen. -- gnome-panel doesn't show all menu items https://launchpad.net/bugs/30146 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76670] Tilp2 - New upstream release
Public bug reported: Binary package hint: tilp Tilp2 was released in Sept. 06 and is available here: http://lpg.ticalc.org/prj_tilp/linux.html Tilp2 supercedes Tilp1, and Tilp1 is no longer maintained. ** Affects: tilp (Ubuntu) Importance: Undecided Status: Unconfirmed -- Tilp2 - New upstream release https://launchpad.net/bugs/76670 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 49251] Re: tilp doesn't work out of the box with the TI-GRAPH LINK USB cable
I've recently run into the same wall. I tried installing the usb cable driver myself, and got similar results--shows up in lsusb, but doesn't actually work with tilp. It would be neat if I could transfer to and from my calculator with Ubuntu. -- tilp doesn't work out of the box with the TI-GRAPH LINK USB cable https://launchpad.net/bugs/49251 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 30146] Re: gnome-panel doesn't show all menu items
Yeah, I don't believe that this bug has anything to do with restarting the system. It's fairly reproducible by installing packages that affect the gnome menu. Take the game atomix for example. It puts a menu entry under Games. So to reproduce, insure that your menu is working correctly beforehand. Then install atomix and atomix-data in Synaptic. Now the menu will behave buggily. Then look at all of the sub-menus until they display correctly again. Then you can reproduce this bug again by uninstalling atomix and atomix-data! This might not be a bug so much with gnome-panel as it is one with how Ubuntu's packaging system messes with the menu. -- gnome-panel doesn't show all menu items https://launchpad.net/bugs/30146 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 30146] Re: gnome-panel doesn't show all menu items
I think that in any case gnome-panel's behavior year is buggy, but what leans me toward the packaging system being part at fault too is that I can change, add, and remove menu contents using alacarte all day long without this bug appearing. Of course, this is in userland, but I can do the same with system menu entries. For example, cp /usr/share/applications/totem.desktop /usr/share/applications/totem2.desktop . Now there are two entries for totem under Sound Video without the bug appearing. Now edit totem2.desktop and where it says Categories=, change AudioVideo to say Utility. Now totem appears under accessories. Now delete totem2.desktop, and totem's phantom menu entry disappears, all of this without the bug appearing. -- gnome-panel doesn't show all menu items https://launchpad.net/bugs/30146 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 30146] Re: gnome-panel doesn't show all menu items
In my previous comment, year-here. -- gnome-panel doesn't show all menu items https://launchpad.net/bugs/30146 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59138] Re: [SRU: EDGY] amule crashes when I close a tab
I just went by the aMule page, and apparently this bug is fixed in wxWidgets 2.8.0, which was released on December 12th. Of course, 2.8.0 didn't make the edgy repos, but surely it will make feisty's. Once it does, this patch is supposed to fix aMule to work with 2.8.0: http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES/aMule-wx.patch?rev=1.2 -- [SRU: EDGY] amule crashes when I close a tab https://launchpad.net/bugs/59138 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68932] Re: Shuffle + repeat + two-track playlist results in buggy behavior
I've been using this patch for a while, and it seems to work greatly. -- Shuffle + repeat + two-track playlist results in buggy behavior https://launchpad.net/bugs/68932 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69968] Re: Play Disk 'X' doesn't work
Yes, I see this as well. -- Play Disk 'X' doesn't work https://launchpad.net/bugs/69968 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 62723] Re: Totem doesn't auto-resize
This seems fixed when I upgraded to Feisty's totem. Well, at least mostly. It automatically resizes when opening a movie, and the '0' and '1' keyboard shortcuts work, but '2' seems to still not work. -- Totem doesn't auto-resize https://launchpad.net/bugs/62723 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69444] Re: Ubuntu's Firefox DOM Inspector is incompatible with Ubuntu's Firefox
I had this issue. Reinstalling it in Synaptic didn't seem to help, but a complete remove all then install fixed it. -- Ubuntu's Firefox DOM Inspector is incompatible with Ubuntu's Firefox https://launchpad.net/bugs/69444 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68932] Re: Shuffle + repeat + two-track playlist results in buggy behavior
Fully updated Ubuntu 6.10 with Rhythmbox 0.9.6. I noticed this happening on my brother's computer too, which has the same version. This is my first time using Rhythmbox, so I can't speak to older versions. -- Shuffle + repeat + two-track playlist results in buggy behavior https://launchpad.net/bugs/68932 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68932] Shuffle + repeat + two-track playlist results in buggy behavior
Public bug reported: Bug: When there are only two tracks in a playlist and both shuffle and random are enabled, Rhythmbox can have buggy behavior when the next button is pressed. If I am playing track A and press next, sometimes Rhythmbox will highlight track B, replace track A's name at the top with track B's, but Rhythmbox will play track A again instead. I suspect that Rhythmbox's random song chooser allows for the possibility of a song playing twice in a row, which is fine, but this bug deals with Rhythmbox visually looking like it's playing one track when it's audibly playing another. To reproduce, turn on shuffle and repeat in the options menu. Then open a playlist with two tracks (or use the browser to narrow a playlist to two tracks). Play a song in that playlist, and then press next until the bug occurs. (The bug seems to randomly occur, but it's often enough that it should occur without too many tries.) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: Unconfirmed -- Shuffle + repeat + two-track playlist results in buggy behavior https://launchpad.net/bugs/68932 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68932] Re: Shuffle + repeat + two-track playlist results in buggy behavior
I just noticed this happening with a three-track playlist too, except much more rarely, so I tried it with a six-track playlist, and it happened more rarely yet. Maybe Rhythmbox _is_ supposed to have some safe-guard to prevent a song from being played twice in a row, except it isn't working quite right? If so, it looks like it manages to select a different song and display its text at the top, but then it just plays the previous song again anyways. -- Shuffle + repeat + two-track playlist results in buggy behavior https://launchpad.net/bugs/68932 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 31286] Re: Displays repeated keyring dialogs on resume from suspend and login
I've found a fix for my version of this bug. I have an ipw2200, and I used to get two simultaneous keyring prompts after logging in when nm- applet tries to automatically connect to a preferred, secure network. I installed the network-manager and network-manager-gnome 0.6.4 packages from debian unstable, and they seem to have fixed the problem. -- Displays repeated keyring dialogs on resume from suspend and login https://launchpad.net/bugs/31286 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 31286] Re: Displays repeated keyring dialogs on resume from suspend and login
I can also confirm this bug. I always get simultaneously prompted twice for my keyring password at log-in. My wireless chipset is an ipw2200. -- Displays repeated keyring dialogs on resume from suspend and login https://launchpad.net/bugs/31286 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63795] Re: nm-applet asks for keyring password twice
I have the same issue. Also worked correctly with Dapper but not with Edgy. My wireless chipset is an ipw2200, and my secure network is a WPA2-TKIP. -- nm-applet asks for keyring password twice https://launchpad.net/bugs/63795 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 48711] Re: nm-applet leaves 5x5 pixel grey artifact on the screen near the panel
I see this one all the time as well. killall nm-applet nm-applet ...seems to be a crude workaround. -- nm-applet leaves 5x5 pixel grey artifact on the screen near the panel https://launchpad.net/bugs/48711 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54396] Re: Eclipse installation has broken dependencies, wants mozilla-browser
jvm crash is unrelated to this bug. Assuming you're having the same jvm problem I did, add '/usr/lib/jvm/java-1.5.0-sun' to /etc/eclipse/java_home, probably at the top. By default, eclipse doesn't seem to search in Ubuntu's directory for Sun Java 5.0. -- Eclipse installation has broken dependencies, wants mozilla-browser https://launchpad.net/bugs/54396 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 48244] Re: eclipse does not locate java-1.5.0-sun
Yes, I see no reason not to fix this considering it already looks in two places other than Ubuntu's directory for Sun Java 1.5.0. Somebody just needs to put in the right one too. -- eclipse does not locate java-1.5.0-sun https://launchpad.net/bugs/48244 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57636] Re: amarok_libvisual helper executable missing from Amarok package
Looks fixed in 1.4.2-0ubuntu2. -- amarok_libvisual helper executable missing from Amarok package https://launchpad.net/bugs/57636 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 57636] amarok_libvisual helper executable missing from Amarok package
Public bug reported: For working libvisual support, Amarok compiles a helper executable called 'amarok_libvisual', which is supposed to go in /usr/lib/amarok/. This file is currently compiled but is not included in the amarok deb. Before this file will be included in the deb, the source package needs to be changed to reflect the addition of it by modifying debian/amarok.install to include the line: debian/tmp/usr/bin/amarok_libvisual /usr/lib/amarok ...or so that worked for me anyways. ** Affects: amarok (Ubuntu) Importance: Untriaged Status: Unconfirmed -- amarok_libvisual helper executable missing from Amarok package https://launchpad.net/bugs/57636 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 52405] Re: gnome-panel eats 50% cpu for half an hour and flickers
To clarify on comment 17, /etc/xdg/menu/debian-menu.menu is the broken symlink that needs deleting, not: /etc/xdg/debian-menu.menu, which doesn't exist. But excellent workaround. -- gnome-panel eats 50% cpu for half an hour and flickers https://launchpad.net/bugs/52405 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 46656] Re: Nautilus FTP vfs doesn't follow redirects
Same issue here. -- Nautilus FTP vfs doesn't follow redirects https://launchpad.net/bugs/46656 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 32963] Re: Xv movies on 810/i945 gives horrible color, Gamma
Ditto Carlos (the post above). -- Xv movies on 810/i945 gives horrible color, Gamma https://launchpad.net/bugs/32963 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
