[Bug 900384] Re: usbipd requires usbip_common_mod.ko and usbip.ko kernel modules, which are not available in any package
Hi Leann, That's some very good news you are bringing to us. Just as a note to everyone who wants to use these modules. The usbip package has still to be upgraded though, in order to get the client side working as well. The current usbip package still expects the old modules. But that would be only a matter of building the client tools from source which is available in the linux-source package, package it up and release a new usbip package. Thanks for making my day. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/900384 Title: usbipd requires usbip_common_mod.ko and usbip.ko kernel modules, which are not available in any package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/900384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539878] Re: nouveau out of sync LVDS (basically card not supported)
The system with the relevant hardware in currently used in as a production machine. I will be able to test the upstream kernel, but I need some time to prepare another machine to take over the production role during the testing. Also I need to find some time to do the actual testing since it's a bit busy now. So it's possible it can take a few weeks before I can post the results of the test you describe. I'm glad someone is still looking at this bug though :) For the people who are looking for a workaround in the meantime: You can disable nouveau on the first boot after your Ubuntu is installed by applying the workaround in comment #19. When greeted with the desktop you can disable nouveau permanent by crafting the following file. $ cat /etc/modprobe.d/nouveau-kms.conf options nouveau modeset=0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/539878 Title: nouveau out of sync LVDS (basically card not supported) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/539878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 577416] Re: Bootchart doesn't get properly removed from init
The issue seems to be resolved. Unable to reproduce the issue with the following configuration: OS: Ubundu 11.04 DE: Xfce 4.8 bootchart: 0.90.2-8 pybootchartgui: 0+r141-0ubuntu3 I'm considering this as fixed. ** Changed in: bootchart (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/577416 Title: Bootchart doesn't get properly removed from init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bootchart/+bug/577416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 301052] Re: Nibbles: pressing arrowkeys down and right make you lose control
The issue seems to be resolved. Unable to reproduce the issue with the following configuration: OS: Ubundu 11.04 - Natty Narwhal DE: Xfce 4.8 gnibbles: 1:2.32.1-0ubuntu5 I'm considering this as fixed. ** Changed in: gnome-games (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/301052 Title: Nibbles: pressing arrowkeys down and right make you lose control To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-games/+bug/301052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539878] Re: nouveau out of sync LVDS (basically card not supported)
Tested iso: Ubuntu 11.04 (Natty Narwhal) Alpha 2 Still exactly the same issue. Although the fuzzy screen is a bit more gray then purple now, but still totally screwed up... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/539878 Title: nouveau out of sync LVDS (basically card not supported) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539878] Re: nouveau out of sync LVDS (basically card not supported)
** Description changed: - Binary package hint: plymouth - *** System *** Dell Vostro 1500 Intel T7500 Nvidia 8400M GS *** Affected ISO's *** (not limited to) Ubuntu Xubuntu - i386 amd64 * Lucid Pre Beta Beta 1 (201003xx) * Lucid Beta 2 (20100406) * Lucid RC (20100419) * Lucid Final Release * Maverick Alpha 3 (20100803) + * Natty Alpha 2 (20110201) *** Kernel type *** Ubuntu's versioning: 2.6.32-16.25 *** Actual behavior 1 *** 1. Booting (X)Ubuntu LiveCD 2. Choose the option Try without install with default boot-parameters 3. Screen has fuzzy colors and no text. *** Expected behavior 1 *** 1. Idem 2. Idem 3. A normal splash-screen and desktop. *** Actual behavior 2 *** 1. Booting (X)Ubuntu LiveCD 2. Choose the option Try without install without the quiet splash option 3. Console with output looking like dmesg 4. After 5 seconds screen switches to graphics and only fuzzy colors and no text. *** Expected behavior 2 *** 1. Idem 2. Idem 3. Idem 4. A normal desktop. *** Actual behavior 3 *** 1. Booting (X)Ubuntu LiveCD 2. Choose the option Check CD with default boot-parameters 3. Screen has fuzzy colors and no text. *** Expected behavior 3 *** 1. Idem 2. Idem 3. A normal screen with progress information. *** Additional info *** Runs correctly and without any problem in VMWare. MD5sum of the downloaded iso's were correct. The fuzzy colors are always the same, not random. - The Ubuntu-version has purple-brown colors. - The Xubuntu-version has green-blue colors. - The Check-CD (both ubuntu/xubuntu) has gray colors. + The colors seems to depend on the release. + The Ubuntu-version had purple-brown colors. + The Xubuntu-version had green-blue colors. + The Check-CD (both ubuntu/xubuntu) had gray colors. I'm not entirely sure if it's a plymouth issue, but since I don't see any form of splash-screen this was my best guess. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/539878 Title: nouveau out of sync LVDS (basically card not supported) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 506884] Re: Wakes processor way to often than needed
I can not reproduce the bug anymore in an fully updated Lucid installation. Neither could I find something in the source code of the plug-in that would explain the described behavior of this bug. So bug closed, also from my point of view. ** Tags removed: iso-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/506884 Title: Wakes processor way to often than needed -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595063] Re: kernel trace of wireless core failure
It seems that the culprit was on the hardware of the wireless card itself, a Intel Corporation PRO/Wireless 3945ABG. After replacing the card the described behavior didn't occur anymore. So I'm closing this since I can't reproduce the described behavior with the replaced card. ** Changed in: linux (Ubuntu) Status: New = Invalid ** Tags removed: kj-triage -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/595063 Title: kernel trace of wireless core failure -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 584410] Re: nm-applet notifications show multiple Don't show this message again buttons
** Bug watch added: GNOME Bug Tracker #622972 https://bugzilla.gnome.org/show_bug.cgi?id=622972 ** Also affects: network-manager-applet via https://bugzilla.gnome.org/show_bug.cgi?id=622972 Importance: Unknown Status: Unknown -- nm-applet notifications show multiple Don't show this message again buttons https://bugs.launchpad.net/bugs/584410 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 584410] Re: nm-applet notifications show multiple Don't show this message again buttons
Confirming Robert Wall's observations, reproduction is more general then only suspendresume, even a plain connect-disconnect cycle introduces a new button every time. Found an upstream bug which describes the same problem and added it here so it can be tracked. If someone is capable of updating the remote bug or finding a better matching remote bug, please be my guest. -- nm-applet notifications show multiple Don't show this message again buttons https://bugs.launchpad.net/bugs/584410 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 539878] Re: nouveau out of sync LVDS (basically card not supported)
** Description changed: Binary package hint: plymouth *** System *** Dell Vostro 1500 Intel T7500 Nvidia 8400M GS - *** Affected ISO's *** - Ubuntu Xubuntu - i386 amd64 - Lucid Pre Beta Beta 1 (201003xx) - Ubuntu Xubuntu - i386 amd64 - Lucid Beta 2 (20100406) - Ubuntu Xubuntu - i386 amd64 - Lucid RC (20100419) + *** Affected ISO's *** (not limited to) + Ubuntu Xubuntu - i386 amd64 + * Lucid Pre Beta Beta 1 (201003xx) + * Lucid Beta 2 (20100406) + * Lucid RC (20100419) + * Lucid Final Release + * Maverick Alpha 3 (20100803) *** Kernel type *** Ubuntu's versioning: 2.6.32-16.25 *** Actual behavior 1 *** 1. Booting (X)Ubuntu LiveCD 2. Choose the option Try without install with default boot-parameters 3. Screen has fuzzy colors and no text. *** Expected behavior 1 *** 1. Idem 2. Idem 3. A normal splash-screen and desktop. *** Actual behavior 2 *** 1. Booting (X)Ubuntu LiveCD 2. Choose the option Try without install without the quiet splash option 3. Console with output looking like dmesg 4. After 5 seconds screen switches to graphics and only fuzzy colors and no text. *** Expected behavior 2 *** 1. Idem 2. Idem 3. Idem 4. A normal desktop. *** Actual behavior 3 *** 1. Booting (X)Ubuntu LiveCD 2. Choose the option Check CD with default boot-parameters 3. Screen has fuzzy colors and no text. *** Expected behavior 3 *** 1. Idem 2. Idem 3. A normal screen with progress information. *** Additional info *** Runs correctly and without any problem in VMWare. MD5sum of the downloaded iso's were correct. The fuzzy colors are always the same, not random. The Ubuntu-version has purple-brown colors. The Xubuntu-version has green-blue colors. The Check-CD (both ubuntu/xubuntu) has gray colors. I'm not entirely sure if it's a plymouth issue, but since I don't see any form of splash-screen this was my best guess. -- nouveau out of sync LVDS (basically card not supported) https://bugs.launchpad.net/bugs/539878 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 539878] Re: nouveau out of sync LVDS (basically card not supported)
Just ignore the previous comment, it was a configuration-issue (Nvidia and nouveau were both battling for the same card...) I made a separate partition and installed a fresh 10.04 on it. First I booted with the blacklist option (see comment #19) and did a complete update to 2.6.32-23. Upon reboot (without blacklist option) I can still reproduce the bug and had to use the hard-shutdown method to shutdown the system. Secondly I booted with the blacklist option (see comment #19) and tried to install the linux-backports-modules-nouveau but it seems that that package doesn't exist any more... So I did an update with what was available in the lucid-proposed-repo and the lucid-backports-repo, which resulted in the 2.6.32-24 kernel. Upon reboot (without blacklist option) I can still reproduce the bug and had to use the hard-shutdown method to shutdown the system. Finally you asked for a apport-collect, but my system becomes completely unresponsive with the bug is reproduced (Mouse isn't drawn on the screen and it doesn't respond to the shortcut keys to switch VT's Ctrl+Alt+F[1-7]) so I can't create a working terminal while producing the bug to issue the apport-collect command. Since I provided all the info I could provide (more questions are of- course more then welcome :) ) i'm reverting the status to it's previous state. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- nouveau out of sync LVDS (basically card not supported) https://bugs.launchpad.net/bugs/539878 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 539878] Re: nouveau out of sync LVDS (basically card not supported)
Sure, no problem. I'm running a complete up to date 10.04 with kernel 2.6.32-23-generic. I re-installed the required nouveau-packages (libdrm-nouveau1 and xserver-xorg-video-nouveau), removed my X.org-config file so it would load the closed-nvidia driver and rebooted. I'm now capable of booting and X.org tries to load nouveau, but it seems that the drmOpenDevice fails, resulting in a fallback to vesa. (See attached X.org-log file) Was the drmOpenDevice-failure expected, or is this configuration- issue? ** Attachment added: Xorg.0.log http://launchpadlibrarian.net/51881407/Xorg.0.log -- nouveau out of sync LVDS (basically card not supported) https://bugs.launchpad.net/bugs/539878 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 501095] Re: SSH-agent not used when using sftp
On a Xubuntu 10.04 LTS using gigolo-0.4.0-1 I get still prompted. I have changed status back since the info implied by the Incomplete is delivered. ** Changed in: gvfs (Ubuntu) Status: Incomplete = New -- SSH-agent not used when using sftp https://bugs.launchpad.net/bugs/501095 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 595063] [NEW] kernel trace of wireless core failure
Public bug reported: *** System *** Hardware: Dell Vostro 1500 OS: Ubuntu 10.04 - Lucid Lynx - Linux kernel 2.6.32 DE: Xfce 4.6 *** Expected behavior *** Wireless doesn't fail (seemingly) at random *** Actual behavior *** Wireless does fail (seemingly) at random with seemingly different causes (Microcode HW errors detected, Microcode SW errors detected, BSM uCode verification failures, AP reply timeout, ...) The attached dmesg contains a kernel trace of one of the failures. Relevant actions during that period # 0s Booted with hardware-kill-switch (on) = wifi off # 66s deactived hardware-kill-switch (off) = wifi on, but fails # 309s activated kill-switch (on) = wifi off ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- kernel trace of wireless core failure https://bugs.launchpad.net/bugs/595063 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 595063] Re: kernel trace of wireless core failure
** Attachment added: dmesg.log http://launchpadlibrarian.net/50428734/dmesg.log -- kernel trace of wireless core failure https://bugs.launchpad.net/bugs/595063 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 595063] Re: kernel trace of wireless core failure
** Attachment added: uname-a.log http://launchpadlibrarian.net/50428741/uname-a.log -- kernel trace of wireless core failure https://bugs.launchpad.net/bugs/595063 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 595063] Re: kernel trace of wireless core failure
** Attachment added: version.log http://launchpadlibrarian.net/50428742/version.log -- kernel trace of wireless core failure https://bugs.launchpad.net/bugs/595063 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 595063] Re: kernel trace of wireless core failure
** Attachment added: lspci-vnvn.log http://launchpadlibrarian.net/50428763/lspci-vnvn.log -- kernel trace of wireless core failure https://bugs.launchpad.net/bugs/595063 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 592336] Re: Removal of aptitude from base installation
It should remain included in the base install, since aptitude has the value when things go wrong. If your system gets broken beyond just fixing a configuration file, when you loose your comfy graphical X-server, ... then aptitude's value is needed. And you (as a user for who fixing a broken system isn't trivial, or as the person who needs to fix it for someone else) can actually use it since it's already present. -- Removal of aptitude from base installation https://bugs.launchpad.net/bugs/592336 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 577416] [NEW] Bootchart doesn't get properly removed from init
Public bug reported: Binary package hint: bootchart *** System-info *** HW: Dell Vostro 1500 OS: Ubuntu 10.04 LTS DE: Xfce 4.6 *** Package-info *** bootchart: 0.90.2-7 pybootchartgui: 0+r139-2 *** Expected Behavior *** Step. 0: bootchart is installed Step. 1: bootchart is removed by using a package-manager Step. 2: init has no references to bootchart anymore since bootchart is removed *** Actual Behavior *** Step. 0 - 1: idem Step. 2: init still reports bootchart-processes in the boot.log *** Reproduction *** Step. 1: $ sudo aptitude install bootchart pybootchartgui Step. 2: reboot a few times and for each reboot wait a minute or two for all capturing and png-generation processes to complete. Step. 3: $ sudo aptitude remove bootchart pybootchartgui Step. 4: $ cat /var/log/boot.log | grep -i bootchart Step. 5: Notice that init still reports bootchart messages. ** Affects: bootchart (Ubuntu) Importance: Undecided Status: New -- Bootchart doesn't get properly removed from init https://bugs.launchpad.net/bugs/577416 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 577416] Re: Bootchart doesn't get properly removed from init
Boot output after removing the bootchart-package. ** Tags added: ubuntu-boot-experience ** Attachment added: boot.log http://launchpadlibrarian.net/48055159/boot.log -- Bootchart doesn't get properly removed from init https://bugs.launchpad.net/bugs/577416 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 577416] Re: Bootchart doesn't get properly removed from init
Apparently it does: $ ls -l /etc/init/bootchart.conf -rw-r--r-- 1 root root 2018 2010-03-22 19:13 /etc/init/bootchart.conf -- Bootchart doesn't get properly removed from init https://bugs.launchpad.net/bugs/577416 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 539878] Re: nouveau out of sync LVDS (basically card not supported)
Just finished testing the latest ISO QA (20100427) and this bug is still standing. Since Lucid will be released in a few hours, here is my workaround to get it booting: Update your boot-options to the following (F6 in the menu of your live-CD or e in your grub2 installation or add it in /etc/default/grub) Original: quiet splash Updated: quiet nouveau.blacklist=true This will give you a nice and stable black screen with only some basic output during booting and as soon as you reach you login-manager or desktop you have a complete, and correct graphical interface. From that point on you can choose to install the proprietary drivers or continue without using all the features of your graphical card. -- nouveau out of sync LVDS (basically card not supported) https://bugs.launchpad.net/bugs/539878 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 539878] Re: nouveau out of sync LVDS (basically card not supported)
The Release Candidate (20100419) has broken the nomodeset-workaround. Laptop is crashing again with flickering diagnostic leds. This bug won't be solved before the release of Lucid, will it? ** Description changed: Binary package hint: plymouth *** System *** Dell Vostro 1500 Intel T7500 Nvidia 8400M GS *** Affected ISO's *** Ubuntu Xubuntu - i386 amd64 - Lucid Pre Beta Beta 1 (201003xx) Ubuntu Xubuntu - i386 amd64 - Lucid Beta 2 (20100406) + Ubuntu Xubuntu - i386 amd64 - Lucid RC (20100419) *** Kernel type *** Ubuntu's versioning: 2.6.32-16.25 *** Actual behavior 1 *** 1. Booting (X)Ubuntu LiveCD 2. Choose the option Try without install with default boot-parameters 3. Screen has fuzzy colors and no text. *** Expected behavior 1 *** 1. Idem 2. Idem 3. A normal splash-screen and desktop. *** Actual behavior 2 *** 1. Booting (X)Ubuntu LiveCD 2. Choose the option Try without install without the quiet splash option 3. Console with output looking like dmesg 4. After 5 seconds screen switches to graphics and only fuzzy colors and no text. *** Expected behavior 2 *** 1. Idem 2. Idem 3. Idem 4. A normal desktop. *** Actual behavior 3 *** 1. Booting (X)Ubuntu LiveCD 2. Choose the option Check CD with default boot-parameters 3. Screen has fuzzy colors and no text. *** Expected behavior 3 *** 1. Idem 2. Idem 3. A normal screen with progress information. *** Additional info *** Runs correctly and without any problem in VMWare. MD5sum of the downloaded iso's were correct. The fuzzy colors are always the same, not random. The Ubuntu-version has purple-brown colors. The Xubuntu-version has green-blue colors. The Check-CD (both ubuntu/xubuntu) has gray colors. I'm not entirely sure if it's a plymouth issue, but since I don't see any form of splash-screen this was my best guess. -- nouveau out of sync LVDS (basically card not supported) https://bugs.launchpad.net/bugs/539878 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 539878] Re: nouveau out of sync LVDS (basically card not supported)
I tried your proposed workarounds in order to reproduce your case, with a liveCD that was already burned, Lubuntu Lucid Beta 2: Booting with nomodeset - usable screen (This wasn't the case during beta1, so \o/ ) Booting with nouveau.modeset=0 - usable screen (same as above) Booting with nouveau.noaccel=1 - didn't help, fuzzy screen, unusable. Not completely the same, but thanks for pointing out the fixed nomodeset. -- nouveau out of sync LVDS (basically card not supported) https://bugs.launchpad.net/bugs/539878 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 539878] Re: nouveau out of sync LVDS (basically card not supported)
** Description changed: Binary package hint: plymouth *** System *** Dell Vostro 1500 Intel T7500 Nvidia 8400M GS *** Affected ISO's *** - Ubuntu Desktop 20100316 - i386 - Ubuntu Desktop 20100316 - amd64 - Xubuntu Desktop 20100316.1 - i386 - Xubuntu Desktop 20100316.1 - amd64 + Ubuntu Xubuntu - i386 amd64 - Lucid Pre Beta Beta 1 (201003xx) + Ubuntu Xubuntu - i386 amd64 - Lucid Beta 2 (20100406) *** Kernel type *** Ubuntu's versioning: 2.6.32-16.25 *** Actual behavior 1 *** 1. Booting (X)Ubuntu LiveCD 2. Choose the option Try without install with default boot-parameters 3. Screen has fuzzy colors and no text. *** Expected behavior 1 *** 1. Idem 2. Idem 3. A normal splash-screen and desktop. *** Actual behavior 2 *** 1. Booting (X)Ubuntu LiveCD 2. Choose the option Try without install without the quiet splash option 3. Console with output looking like dmesg 4. After 5 seconds screen switches to graphics and only fuzzy colors and no text. *** Expected behavior 2 *** 1. Idem 2. Idem 3. Idem 4. A normal desktop. *** Actual behavior 3 *** 1. Booting (X)Ubuntu LiveCD 2. Choose the option Check CD with default boot-parameters 3. Screen has fuzzy colors and no text. *** Expected behavior 3 *** 1. Idem 2. Idem 3. A normal screen with progress information. *** Additional info *** Runs correctly and without any problem in VMWare. MD5sum of the downloaded iso's were correct. The fuzzy colors are always the same, not random. The Ubuntu-version has purple-brown colors. The Xubuntu-version has green-blue colors. The Check-CD (both ubuntu/xubuntu) has gray colors. I'm not entirely sure if it's a plymouth issue, but since I don't see any form of splash-screen this was my best guess. -- nouveau out of sync LVDS (basically card not supported) https://bugs.launchpad.net/bugs/539878 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 545470] Re: Fuzzy startup screen lucid LiveCD Beta 1
The error you mention isn't really an error...That's a normal exit state for ureadahead-other, but it's init / upstart fault you're seeing that error. See following bugs: Bug #484677 (where there is explained that it's normal behavior) Bug #522197 (where there is a bug running against upstart for displaying it faulty) So basically your system boots correctly and without errors if use the work-around of adding nomodeset as boot-option. So the issue is that you have to apply the work-around to get your system running. How and why, I don't know, that's for someone else with more knowledge. :) -- Fuzzy startup screen lucid LiveCD Beta 1 https://bugs.launchpad.net/bugs/545470 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 539878] Re: nouveau out of sync LVDS (basically card not supported)
@GerryFerdinandus: Since we suspect that this bug-report is about an issue with nouveau (an open-source driver for Nvidia cards) and your system has an ATI-card, I think it's better to report a new bug about the issue you're experiencing . Feel free to link this bug in your new bug-report-description if you think it's relevant. Have you tried booting with 'nomodeset'? -- nouveau out of sync LVDS (basically card not supported) https://bugs.launchpad.net/bugs/539878 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 539878] Re: nouveau out of sync LVDS (basically card not supported)
Done some more testing on the latest liveCD, didn't really solve the problem though: The breakpoint: break=top produced a type-able terminal to put commands in. If I only would know which command I need to type to continue the execution... All the other breakpoints, like modules,premount,mount,bottom and init resulted in either a static gray-screen with no VT's to type in, or they had no effect and the liveCD booted the same fuzzy colored-screen with probably should be the desktop... Probably because the breakpoints break after nouveau has been loaded. Boot-option vesa video=vesafb didn't had any effect. Boot-option rdblacklist=nouveau didn't had any effect. Boot-option xforcevesa is the first things that had a visual effect after the console is gone. It resulted in a totally different, but still corrupted screen, but I saw the same artifacts as some others on the ubuntu-forums have posted (small red signs in the top 20 pixel-lines) Anyone having some instructions on how to produce useful debugging info so that the developers can fix it? -- nouveau out of sync LVDS (basically card not supported) https://bugs.launchpad.net/bugs/539878 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 539878] Re: nouveau out of sync LVDS (basically card not supported)
Ehm, booting with only nomodeset results in the same crash as I mentioned in Comment 6 (when booting with vga=normal nomodeset), system crashes during loading and the diagnostics leds are flickering as if the are saying Please don't do that again :) So I can't get to console nor desktop to install the nvidia-glx drivers... Another thing I have found was that if I let it boot with default options, it seems to get to the desktop (don't know for sure since I can't read the screen, see screenshots ;) ). When my CD isn't active any more I can get the system to reboot if I press the key-combination (for Xubuntu): Alt+F4; Right-arrow; Enter, which results in my screen fading out and ejection of my CD, which if followed by an Enter-key- stroke, the system will reboot. Also if I do the key combo: Alt+F4; 2x Right-arrow; Enter I get the expected behavior of a shutdown. And a final thing I found was that if I let it boot with default options till there is no activity for my CD-drive, and I press any of the Ctrl+Alt+F[1-9] key-combinations, it has no effect. So I can't drop down to the console with Ctrl+Alt+F1 to have a look at any logs... So if there is anything I can help with, just provide the instructions or the relevant questions. More than happy to help out here :) -- nouveau out of sync LVDS (basically card not supported) https://bugs.launchpad.net/bugs/539878 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 484677] Re: init: ureadahead-other main process terminated with status 4
*** This bug is a duplicate of bug 522197 *** https://bugs.launchpad.net/bugs/522197 ** This bug has been marked a duplicate of bug 522197 init: shouldn't log a warning/error when a job fails with a status in normal exit -- init: ureadahead-other main process terminated with status 4 https://bugs.launchpad.net/bugs/484677 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 539878] Re: nouveau out of sync LVDS (basically card not supported)
** Tags added: lucid ** Tags removed: kernel-series-unknown ** Description changed: Binary package hint: plymouth *** System *** Dell Vostro 1500 Intel T7500 Nvidia 8400M GS *** Affected ISO's *** Ubuntu Desktop 20100316 - i386 Ubuntu Desktop 20100316 - amd64 Xubuntu Desktop 20100316.1 - i386 Xubuntu Desktop 20100316.1 - amd64 + + *** Kernel type *** + Ubuntu's versioning: 2.6.32-16.25 *** Actual behavior 1 *** 1. Booting (X)Ubuntu LiveCD 2. Choose the option Try without install with default boot-parameters 3. Screen has fuzzy colors and no text. *** Expected behavior 1 *** 1. Idem 2. Idem 3. A normal splash-screen and desktop. *** Actual behavior 2 *** 1. Booting (X)Ubuntu LiveCD 2. Choose the option Try without install without the quiet splash option 3. Console with output looking like dmesg 4. After 5 seconds screen switches to graphics and only fuzzy colors and no text. *** Expected behavior 2 *** 1. Idem 2. Idem 3. Idem 4. A normal desktop. *** Actual behavior 3 *** 1. Booting (X)Ubuntu LiveCD 2. Choose the option Check CD with default boot-parameters 3. Screen has fuzzy colors and no text. *** Expected behavior 3 *** 1. Idem 2. Idem 3. A normal screen with progress information. *** Additional info *** Runs correctly and without any problem in VMWare. MD5sum of the downloaded iso's were correct. The fuzzy colors are always the same, not random. The Ubuntu-version has purple-brown colors. The Xubuntu-version has green-blue colors. The Check-CD (both ubuntu/xubuntu) has gray colors. I'm not entirely sure if it's a plymouth issue, but since I don't see any form of splash-screen this was my best guess. -- nouveau out of sync LVDS (basically card not supported) https://bugs.launchpad.net/bugs/539878 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 539878] Re: nouveau out of sync LVDS (basically card not supported)
\o/ Somebody how actually knows what's going wrong, great. I'm willing to provide you all the information you need, but since I don't have much experience in these kind of things (I know that if I install jockey-gtk, I can play movies on my screen) I will need some advice on what I need to do... I have found what a mmiotrace is: http://nouveau.freedesktop.org/wiki/MmioTrace, but I have no idea how to retrieve the trace from the running liveCD, because I always end up with and unusable screen. So my questions are: 1) If I'm running the liveCD and it let it screw up my screen, how can I drop down to the terminal to copy the file to my USB-stick? 2) In the documentation of the kernel (/ Documentation / trace / mmiotrace.txt) I read that Tracing is disabled by default, so how do I enable it on the liveCD? 3) I have found that nouveau is part of the libdrm. So why is it that if I'm in the menu option of the liveCD and I choose the bootoption nodrm I still get the issue? 4) You say you have exact same issue. Does this mean that the status of the bug should move to Confirmed? 5) You said that you are working with upstream, but this bug isn't linked to a remote bug-tracker. Is there somewhere I can follow the discussion upstream in some sort of forum-thread / bug-tracker / IRC? 6) Is there any change this will be resolved before the launch of Lucid Beta 1? Because this will spook quite a lot of people if they just want to launch up the beta to see how thing are going. -- nouveau out of sync LVDS (basically card not supported) https://bugs.launchpad.net/bugs/539878 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 539878] Re: nouveau out of sync LVDS (basically card not supported)
I was able to get a bit further by supplying the following boot-option: vga=normal nomodeset. But my system crashes completely within the 2 minutes and a bunch of diagnostics leds are flickering indicating something went wrong. -- nouveau out of sync LVDS (basically card not supported) https://bugs.launchpad.net/bugs/539878 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 516834] Re: bad default swappiness for desktop systems
From the Ubuntu Documenatation: https://help.ubuntu.com/community/Installation/SystemRequirements#Desktop%20installation [quote]Recommended minimum requirements Ubuntu should run reasonably well on a computer with the following minimum hardware specification. However, features such as visual effects may not run smoothly. * 700 MHz x86 processor * 384 MB of system memory (RAM) [...] [/quote] If we can't meet those requirements due to a bad swappiness-value, someone (I'm not saying who, since I don't have a clue how those things work) needs to fix it in time before the LTS is released. Just my 2 cents. -- bad default swappiness for desktop systems https://bugs.launchpad.net/bugs/516834 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 539878] [NEW] Fuzzy screen without text
Public bug reported: Binary package hint: plymouth *** System *** Dell Vostro 1500 Intel T7500 Nvidia 8400M GS *** Affected ISO's *** Ubuntu Desktop 20100316 - i386 Ubuntu Desktop 20100316 - amd64 Xubuntu Desktop 20100316.1 - i386 Xubuntu Desktop 20100316.1 - amd64 *** Actual behavior 1 *** 1. Booting (X)Ubuntu LiveCD 2. Choose the option Try without install with default boot-parameters 3. Screen has fuzzy colors and no text. *** Expected behavior 1 *** 1. Idem 2. Idem 3. A normal splash-screen and desktop. *** Actual behavior 2 *** 1. Booting (X)Ubuntu LiveCD 2. Choose the option Try without install without the quiet splash option 3. Console with output looking like dmesg 4. After 5 seconds screen switches to graphics and only fuzzy colors and no text. *** Expected behavior 2 *** 1. Idem 2. Idem 3. Idem 4. A normal desktop. *** Actual behavior 3 *** 1. Booting (X)Ubuntu LiveCD 2. Choose the option Check CD with default boot-parameters 3. Screen has fuzzy colors and no text. *** Expected behavior 3 *** 1. Idem 2. Idem 3. A normal screen with progress information. *** Additional info *** Runs correctly and without any problem in VMWare. MD5sum of the downloaded iso's were correct. The fuzzy colors are always the same, not random. The Ubuntu-version has purple-brown colors. The Xubuntu-version has green-blue colors. The Check-CD (both ubuntu/xubuntu) has gray colors. I'm not entirely sure if it's a plymouth issue, but since I don't see any form of splash-screen this was my best guess. ** Affects: plymouth (Ubuntu) Importance: Undecided Status: New -- Fuzzy screen without text https://bugs.launchpad.net/bugs/539878 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 539878] Re: Fuzzy screen without text
** Attachment added: Picture of the fuzzy Xubuntu screen http://launchpadlibrarian.net/41056828/Xubuntu-Fuzzy.jpg ** Description changed: Binary package hint: plymouth *** System *** Dell Vostro 1500 Intel T7500 Nvidia 8400M GS *** Affected ISO's *** Ubuntu Desktop 20100316 - i386 Ubuntu Desktop 20100316 - amd64 Xubuntu Desktop 20100316.1 - i386 Xubuntu Desktop 20100316.1 - amd64 *** Actual behavior 1 *** 1. Booting (X)Ubuntu LiveCD 2. Choose the option Try without install with default boot-parameters 3. Screen has fuzzy colors and no text. *** Expected behavior 1 *** 1. Idem 2. Idem 3. A normal splash-screen and desktop. *** Actual behavior 2 *** 1. Booting (X)Ubuntu LiveCD 2. Choose the option Try without install without the quiet splash option 3. Console with output looking like dmesg 4. After 5 seconds screen switches to graphics and only fuzzy colors and no text. *** Expected behavior 2 *** 1. Idem 2. Idem 3. Idem 4. A normal desktop. + *** Actual behavior 3 *** + 1. Booting (X)Ubuntu LiveCD + 2. Choose the option Check CD with default boot-parameters + 3. Screen has fuzzy colors and no text. + + *** Expected behavior 3 *** + 1. Idem + 2. Idem + 3. A normal screen with progress information. + *** Additional info *** Runs correctly and without any problem in VMWare. MD5sum of the downloaded iso's were correct. The fuzzy colors are always the same, not random. The Ubuntu-version has purple-brown colors. The Xubuntu-version has green-blue colors. + The Check-CD (both ubuntu/xubuntu) has gray colors. I'm not entirely sure if it's a plymouth issue, but since I don't see any form of splash-screen this was my best guess. -- Fuzzy screen without text https://bugs.launchpad.net/bugs/539878 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 539878] Re: Fuzzy screen without text
** Attachment added: Picture of the fuzzy Ubuntu screen http://launchpadlibrarian.net/41056753/Ubuntu-Fuzzy.jpg -- Fuzzy screen without text https://bugs.launchpad.net/bugs/539878 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 506618] Re: Jockey failed to install nvidia current drivers
And why do I get the same error when trying to install the old 173-version? ** Attachment added: jockey.log http://launchpadlibrarian.net/37893327/jockey.log -- Jockey failed to install nvidia current drivers https://bugs.launchpad.net/bugs/506618 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 502587] Re: Please remove xfce4-governor-plugin (universe) from the archive
I also disagree to the statement of useless. I use it almost every day, and it never crashed or disappeared from my panel... From switching it from on-demand when being mobile to performance when I'm flash-gaming and I don't want any stutters or when I'm running simulations for my studies and need all the process-power my system with all my cores running at top-speed. Xfce4-power-manager doesn't have an option where you can choose between those setting. Removing the possibility to set that with an easy GUI would definitely be a step back! -- Please remove xfce4-governor-plugin (universe) from the archive https://bugs.launchpad.net/bugs/502587 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 506884] [NEW] Wakes processor way to often than needed
Public bug reported: Binary package hint: xfce4-systemload-plugin Ubuntu has set the goal for mobile devices to last longer on a single battery charge. This can be done by several things, of which keeping the amount of wakening the processor to a minimum. Tickless-kernels was a great move forward and now they advice to have around 50 interrupts per second for a fully but idle desktop. xfce4-systemload-plugin 1:0.4.2-1ubuntu3, which has been released for hardy and intrepid, did 4 interrupts per second. This gives the user every 250 milliseconds an update of the systems load. This is a reasonable value for something that has to present non-crucial and more or less real-time info. xfce4-systemload-plugin 1:0.4.2-3ubuntu1, which has been released for karmic and lucid, is doing 12 interrupts per second. This makes it almost the second top-cause for wakening the processor after the kernels function itself. It also takes as much as a quarter of the allowed 50 interrupts. Giving this non-crucial info every 85 milliseconds is not reasonable since the user will not gain any informative info. If you program gets stuck and your processor goes up to 100% load, you'll notice this in the same way on a 250 millisecond update as on a 85 millisecond update. I think this is just unnecessary usage of processor- cycles and power. Possible solutions: 1) Set the value back to a 4Hz update, like it has been. 2) Provide a simple option to let the user chose the update frequency, like already done in the xfce4-sensors-plugin. ** Affects: xfce4-systemload-plugin Importance: Undecided Status: New ** Affects: xfce4-systemload-plugin (Ubuntu) Importance: Undecided Status: New ** Also affects: xfce4-systemload-plugin Importance: Undecided Status: New ** Summary changed: - Wakes processor why to often than needed + Wakes processor way to often than needed -- Wakes processor way to often than needed https://bugs.launchpad.net/bugs/506884 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 503555] Re: Deprecate use of HAL
I can also confirm this during live-session of Xubuntu Lucid Alpha 2 - 2010-01-12.2 Dmesg output: [ 98.535728] CPUFREQ: Per core ondemand sysfs interface is deprecated - up_threshold -- Deprecate use of HAL https://bugs.launchpad.net/bugs/503555 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 500198] Re: opening pipe: no such file or directory
*** System *** Hardware: Dell Vostro 1500. Xubuntu Lucid Alpha 2 - 2010-1-12.2 I don't get the Opening pipe...-message and it seems that the disk does get checked, there is only no interaction with the user. If I run the checker with default boot options, I get a black-screen, and it starts to check my disk for 4m30s. After that my CD spins-down due the checking-process is complete. But it doesn't respond to any keystroke to reboot the system. I have to use Ctrl+Alt+Del (Alt+SysReq+B, doesn't seem to work). If I compare this with the behavior of the 9.04 release, I got an visual progress-bar, and it starts to check my disk for 4m30s (did 2 stopwatch tests, both for 9.04 and 10.04). After that my CD spins-down due to the checking-process is complete. Response to a keystroke and system rebooted. If I run the checker without the options quiet splash, I see that the console-output gets interrupted around the line: ACPI: Video Device [VID] ..., bright flash, cleared screen, and continuation of output on Console: switching to colour frame buffer ... Maybe this is related to having no visual feedback with the splash option? I didn't had that small interruption on the 9.04. Aside from that output seems similar to 9.04 aside from usual differences (squashfs 4.0 vs. squashfs 3.3, ...). So my guess is that the checking of the CD still works, but the visualization and keyboard-listing is somehow broken... -- opening pipe: no such file or directory https://bugs.launchpad.net/bugs/500198 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 238183] Re: Useless memory consumption
Ah, now I see. By first time, I meant, indeed, as long as you didn't install any packages as requested, since the install of the OS, and close the application. Basically doing nothing from the point of view of the shares-admin command. You can be right about counting memory usage. I don't now very much about it and I didn't take the shared memory into account. So I won't disagree that, while the issue is still present, it can be less then 90MB, that's perfectly possible. Starting only the modules you use, and preventing unnecessarily load to the system, would be my chose of preference as well. Unless this form of pre-loading has some tremendous performance benefits. But I doubt that. -- Useless memory consumption https://bugs.launchpad.net/bugs/238183 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 238183] Re: Useless memory consumption
I don't think I completely understand you. Forgive me, English is not my native language... You say that due to package installation there is an increase of 90MB in memory usage. But 1) I decline the request to install any packages upon request, by clicking on the close button. (see Step 2) 2) I never typed in any administration password and I didn't invoke the command while being root. So there aren't any packages being installed, ergo it can't be the cause of the increased memory usage. Correct? Thanks for looking into this issue and your quick reply. Happy holidays! -- Useless memory consumption https://bugs.launchpad.net/bugs/238183 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 238183] Re: Useless memory consumption
This is still present in Jaunty_Jackalope 9.04. Added the GST-project (gnome-system-tools) since this bug occurs when invoking the shares-admin-command. So maybe there's an issue with the front-end (shares-admin, part of gnome-system-tools) instead of a problem with the back-end (system-tools-backends). Also updated the bug description with newer info. ** Also affects: gst Importance: Undecided Status: New ** Description changed: Binary package hint: system-tools-backends *** Platform *** Xubuntu Hardy 8.04 system-tools-backend 2.6.0-0ubuntu7 - When you use the Shared Folders menu-entry for the first time and do - nothing but hit every close button you see, your memory usage will be - increased for about 3 minutes by 90 MiB, and for 10 MiB untill the next - reboot. + Xubuntu Jaunty 9.04 + gnome-system-tools 2.22.2-0ubuntu4 + system-tools-backend 2.6.0-2ubuntu8 + + + When you use the Shared Folders menu-entry for the first time and do nothing but hit every close button you see, your memory usage will be increased for about 3 minutes by 90 MiB, and for 10 MiB untill the next reboot. *** Reproduction Problem 1*** - Step 1. Open Shared Folders through the drop-down menu Applications. + Step 1. Open Shared Folders through the drop-down menu Applications, or run the shares-admin-command in terminal. Step 2. You get a pop-up window where you are asked to Install Services, click on the Close-button. Step 3. Then you see the remaining window titled Shared Folders. Click on the Close-button. Step 4. Your memory has now increased with around 90 MiB. Details: 8x SystemToolsBack 10MiB ~ 13 MiB SystemToolsBack: /usr/bin/perl /usr/share//system-tools-backends-2.0/scripts/SystemToolsBackends.pl -m AllWithDifferentOptions Step 5. After a while, around 3 minutes, they all are all cleared, expect 1 SystemToolsBack remains (/usr/bin/perl /usr/share//system-tools-backends-2.0/scripts/SystemToolsBackends.pl -m Platform) This SystemToolsBack -m Platfrom also survives a log-out / log-in. You have to reboot before it's cleared. *** Expected behavior *** Step 1 through step 3 the same. Step 4. Immediate clearance of memory usage. Step 5. Immediate clearance of memory usage. *** Additional note *** I have found bug #64560 describing the problem for Step 5. Nevertheless, this bug isn't a duplicate of bug #64560 because the bug described here puts bug #64560 in a bigger picture and the origin of problem for Step 4 can easily be totally different for bug #64560. I shall also reopen bug #64560 since it happened again and will add a reference to this bug. ** Description changed: Binary package hint: system-tools-backends *** Platform *** Xubuntu Hardy 8.04 system-tools-backend 2.6.0-0ubuntu7 Xubuntu Jaunty 9.04 gnome-system-tools 2.22.2-0ubuntu4 system-tools-backend 2.6.0-2ubuntu8 - + *** Description Problem *** When you use the Shared Folders menu-entry for the first time and do nothing but hit every close button you see, your memory usage will be increased for about 3 minutes by 90 MiB, and for 10 MiB untill the next reboot. - *** Reproduction Problem 1*** + *** Reproduction Problem *** Step 1. Open Shared Folders through the drop-down menu Applications, or run the shares-admin-command in terminal. Step 2. You get a pop-up window where you are asked to Install Services, click on the Close-button. Step 3. Then you see the remaining window titled Shared Folders. Click on the Close-button. Step 4. Your memory has now increased with around 90 MiB. Details: 8x SystemToolsBack 10MiB ~ 13 MiB SystemToolsBack: /usr/bin/perl /usr/share//system-tools-backends-2.0/scripts/SystemToolsBackends.pl -m AllWithDifferentOptions Step 5. After a while, around 3 minutes, they all are all cleared, expect 1 SystemToolsBack remains (/usr/bin/perl /usr/share//system-tools-backends-2.0/scripts/SystemToolsBackends.pl -m Platform) This SystemToolsBack -m Platfrom also survives a log-out / log-in. You have to reboot before it's cleared. *** Expected behavior *** Step 1 through step 3 the same. Step 4. Immediate clearance of memory usage. Step 5. Immediate clearance of memory usage. *** Additional note *** I have found bug #64560 describing the problem for Step 5. Nevertheless, this bug isn't a duplicate of bug #64560 because the bug described here puts bug #64560 in a bigger picture and the origin of problem for Step 4 can easily be totally different for bug #64560. I shall also reopen bug #64560 since it happened again and will add a reference to this bug. -- Useless memory consumption https://bugs.launchpad.net/bugs/238183 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 501095] [NEW] SSH-agent not used when using sftp
Public bug reported: Binary package hint: gigolo System: Xubuntu 9.04 Package: gigolo-0.3.0 Preliminary steps: 0.1) The ssh-agent gets started upon boot. 0.2) User adds his private keys to ssh-agent with ssh-add Expected behavior: 1) User starts gigolo and chooses to connect with sftp 2) The connection is made without prompting the user for a passphrase Actual behavior: 1) User starts gigolo and chooses to connect with sftp 2) The user is unnecessarily prompted for a passphrase ** Affects: gigolo (Ubuntu) Importance: Undecided Status: New -- SSH-agent not used when using sftp https://bugs.launchpad.net/bugs/501095 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 348904] Re: Showing no tooltip
I suppose that the fix will we ported to Jaunty aswell? -- Showing no tooltip https://bugs.launchpad.net/bugs/348904 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 348904] [NEW] Showing no tooltip
Public bug reported: Binary package hint: xfce4-systemload-plugin Release: Xubuntu Jaunty 9.04 - Alpha 6 - Live CD Package: xfce4-systemload-plugin: 1:0.4.2-1ubuntu3 Expected behavior: 1) Moving your mouse over one of the plugin's bars 2) A tooltip appear with more information. Actual behavior: 1) Moving your mouse over one of the plugin's bars 2) No tooltip This used to work under Intrepid. Package: xfce4-systemload-plugin: 1:0.4.2-1ubuntu3 This bug relates to Bug #134461, but since about one and a half years later, I though it was best to file a new bug. ** Affects: xfce4-systemload-plugin (Ubuntu) Importance: Undecided Status: New ** Tags: regression ** Tags added: regression -- Showing no tooltip https://bugs.launchpad.net/bugs/348904 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 236257] Re: kubuntu-live and kubuntu-kde4-live listed with same description
Upgraded from intrepid-proposed: tasksel (2.73ubuntu11.1) tasksel-data (2.73ubuntu11.1) I can confirm the success of the fix. Tasksel now lists two different entries: [ ] Kubuntu KDE 4 live CD [ ] Kubuntu live CD (I don't have a Hardy installation nearby now. But over three days I'm back home, where there is a running Hardy.) -- kubuntu-live and kubuntu-kde4-live listed with same description https://bugs.launchpad.net/bugs/236257 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 344196] Re: Songbird hangs on song change
I can confirm this, I'm experiencing exactly the same problem. I shall try to provide some additional info: * Platform on which I preformed some tests * (X)ubuntu 8.10 (32-bit) - original fresh CD-install * Packages I tested * Songbird 1.0.0 - installed from getdeb.net (Exactly the same problem occurs) Songbird 1.1.1 - installed from getdeb.net (Exactly the same problem occurs) * When launching Songbird, the relevant processes, with there waiting channels are: * Process: /bin/sh ./songbird Waiting-channel: do_wait Process: /bin/sh /usr/bin/songbird Waiting-channel: do_wait Process: ././songbird-bin Waiting-channel: do_poll * When Songbird hangs as described by bug description: * Process: /bin/sh ./songbird Waiting-channel: do_wait Process: /bin/sh /usr/bin/songbird Waiting-channel: do_wait Process: ././songbird-bin Waiting-channel: futex_wait * Library size * Only tested with a size 100. * File-system * Only tested on a EXT3 of 9 GiB. * Notes * I can only reproduce this bug when playing .flac files. I can play (replay, skip, ...) .mp3 files without any problem. I have tested all .flac files with the flac -t-command and they were all oké. Also it seems that the bug happens on random (.flac) songs, and the amount of successfull played song before it crashes varies too. Mine amount ranged between 1 and 7 songs. -- Songbird hangs on song change https://bugs.launchpad.net/bugs/344196 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 335422] [NEW] Xfce 4.6 for Jaunty
Public bug reported: Binary package hint: xfce4 On about to include xfce v4.6.0 for Jaunty ? It has so many improvements... and testers still have enough time for the release is there. Changelog: http://www.xfce.org/documentation/changelogs/ ** Affects: xfce4 (Ubuntu) Importance: Undecided Status: New -- Xfce 4.6 for Jaunty https://bugs.launchpad.net/bugs/335422 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 335422] Re: Xfce 4.6 for Jaunty
@Pasi Lallinaho: I think only the assignee can change the Importance... @Charlie Kravetz: I see :-) That's good news, so it will be certain that Jaunty will ship with Xfce 4.6.0. (which is released this morning, but you'll knew that already I assume :-) ) Than it is now waiting till the final reaches the Jaunty-alpha's. -- Xfce 4.6 for Jaunty https://bugs.launchpad.net/bugs/335422 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 239123] Re: Challange one: mismatch description vs. goals
System version: Xubuntu 8.10 - Intrepid Package version: extremetuxracer: 0.4-1ubuntu1 This fix still hasn't made it to extremetuxracer (Ubuntu). ** Changed in: extremetuxracer (Ubuntu) Status: New = Confirmed -- Challange one: mismatch description vs. goals https://bugs.launchpad.net/bugs/239123 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 229518] Re: crash looking for map in wrong directory
System version: Xubuntu 8.10 - Intrepid Package version: extremetuxracer: 0.4-1ubuntu1 This fix still hasn't made it to extremetuxracer (Ubuntu). ** Also affects: extremetuxracer (Ubuntu) Importance: Undecided Status: New ** Changed in: extremetuxracer (Ubuntu) Status: New = Confirmed -- crash looking for map in wrong directory https://bugs.launchpad.net/bugs/229518 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 177725] Re: pnpacpi: exceeded the max number of mem/IO resources
System version: Xubuntu 8.10 - Intrepid Package version: 2.6.27-7 The warnings aren't displayed anymore during boot. -- pnpacpi: exceeded the max number of mem/IO resources https://bugs.launchpad.net/bugs/177725 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 292778] Re: Revision of hald-addon-dell-backlight needed
** Changed in: hal (Ubuntu) Status: Confirmed = Invalid -- Revision of hald-addon-dell-backlight needed https://bugs.launchpad.net/bugs/292778 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 301052] [NEW] Nibbles: pressing arrowkeys down and right make you lose control
Public bug reported: Binary package hint: gnome-games System-version: Xubuntu 8.10 - Intrepid Software-version: gnome-games 1:2.24.1.1-0ubuntu1 Reproduction: 0. I'm assuming you have installed the Gnome game Nibbles which comes by default with ubuntu. 1. Launch Nibbles 2. Chose in the menu-bar Game - New 3. Point your worm horizontally to right 4. Press the right-arrow key and keep it pressed 5. Press the down-arrow key and keep it pressed 6. Notice that your worm has gone crazy 6.1 It's making a shape like an staircase 6.2 You have no control over the worm and have to wait until it crashes into something. 7. Notice that when you revive you have regained full control and you can start reproducing again from step 3. Expected: Step 0 to 5 the same. Step 6. The worm doesn't go crazy. It just goes down. Note: I have tested some more combinations, and these were my results: Crazy == Pointing upwards + pressing up + pressing left Normal == Pointing upwards + pressing up + pressing right Crazy == Pointing to the right + pressing right + pressing down Normal == Pointing to the right + pressing right + pressing up Normal == Pointing downwards + pressing down + pressing left Normal == Pointing downwards + pressing down + pressing right Normal == Pointing to the left + pressing left + pressing down Normal == Pointing to the left + pressing left + pressing up ** Affects: gnome-games Importance: Undecided Status: New ** Affects: gnome-games (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-games Importance: Undecided Status: New -- Nibbles: pressing arrowkeys down and right make you lose control https://bugs.launchpad.net/bugs/301052 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 292778] Re: Revision of hald-addon-dell-backlight needed
Oké, now I understand your point. Please close this bug, like you proposed in your first comment. Thanks for clearing this out for me. -- Revision of hald-addon-dell-backlight needed https://bugs.launchpad.net/bugs/292778 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 292778] Re: Revision of hald-addon-dell-backlight needed
Do I understand this correctly, if I say there are more then 1 listeners for the FN-keys? One listener is hald-addon-dell-backlight and if you kill it, hitting FN-keys will still work because another listener will capture the event. That would explain why killing hald-addon-dell-backlight keeps it working. A second thing why I thought revision was needed, is the fact that hitting the FN-keys once makes the brightness changes several levels. There are numerous bug reports about this like bug #207473, in my personal case it changes with steps of 4 levels. A small test reveals that if I kill hald-addon-dell-backlight process it still changes by 4 levels. So hald-addon-dell-backlight can't have anything to do with this, right? But this makes me question: if hitting FN-keys are properly handled without hald-addon-dell-backlight, why does it still exists? (Without it would save us resources and it would be a process less that needed to be started upon boot-time.) -- Revision of hald-addon-dell-backlight needed https://bugs.launchpad.net/bugs/292778 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 292778] Re: Revision of hald-addon-dell-backlight needed
Oh, and another question: there have been reports of hald-addon- backlight consumes up to 100% of CPU. (Reference: bug #285323, comments 56 57). Shouldn't that be a reason too to revise the hald-addon- backlight? -- Revision of hald-addon-dell-backlight needed https://bugs.launchpad.net/bugs/292778 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 292778] Re: Revision of hald-addon-dell-backlight needed
Sorry for the double post :S ... -- Revision of hald-addon-dell-backlight needed https://bugs.launchpad.net/bugs/292778 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 292778] Re: Revision of hald-addon-dell-backlight needed
Oh, and another question: there have been reports of hald-addon- backlight consumes up to 100% of CPU. (Reference: bug #285323, comments 56 57). Shouldn't that be a reason too to revise the hald-addon- backlight. -- Revision of hald-addon-dell-backlight needed https://bugs.launchpad.net/bugs/292778 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 292778] Re: Revision of hald-addon-dell-backlight needed
Changed status to confirmed since: Hinrik Örn Sigurðsson reported the same problem in bug #277954. ** Changed in: hal (Ubuntu) Status: New = Confirmed -- Revision of hald-addon-dell-backlight needed https://bugs.launchpad.net/bugs/292778 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 292778] [NEW] Revision of hald-addon-dell-backlight needed
Public bug reported: Binary package hint: hal Personally I think it's needed to revise hald-addon-dell-backlight. I have a Dell Vostro 1500, that shipped with Vista. I'm now running it in dual boot with Xubuntu 8.04. Now, on my (X)ubuntu I'm able to change the brightness of my LCD-pannel with the FN-keys. In my process-list I see this process:hald-addon-dell-backlight. But I think it does nothing... Because when I kill hald-addon-dell-backlight, I can still change the brightness of my LCD-pannel. ** Affects: hal (Ubuntu) Importance: Undecided Status: Confirmed -- Revision of hald-addon-dell-backlight needed https://bugs.launchpad.net/bugs/292778 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 277954] Re: Adjusting Dell backlight steals X keyboard focus and uses 100% CPU
*** This bug is a duplicate of bug 285323 *** https://bugs.launchpad.net/bugs/285323 ** This bug has been marked a duplicate of bug 285323 Losing keyboard and mouse control when changing screen brightness with fn + arrow under intrepid -- Adjusting Dell backlight steals X keyboard focus and uses 100% CPU https://bugs.launchpad.net/bugs/277954 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 277954] Re: Adjusting Dell backlight steals X keyboard focus and uses 100% CPU
*** This bug is a duplicate of bug 285323 *** https://bugs.launchpad.net/bugs/285323 To make things easier, I splitted this bug report up in 2 separated reports. Bug #292778 takes care of the regardless of whether 'hald-addon-dell-backlight' is running. Bug #285323 takes care of the rest you reported. -- Adjusting Dell backlight steals X keyboard focus and uses 100% CPU https://bugs.launchpad.net/bugs/277954 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 251950] Re: Please update filezilla to 3.1.0.1
Filezilla release 3.1.0.1 should also be available in hardy as well, since it's a LTS (and people will be using it a long time) and this is a security advisory! Therefor I have set the status back to Confirmed. If there is (are) good argument(s) to not update the hardy-version then you can set it back to Fix Released. ** Changed in: filezilla (Ubuntu) Status: Fix Released = Confirmed -- Please update filezilla to 3.1.0.1 https://bugs.launchpad.net/bugs/251950 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 220543] Re: Halt entry doesn't shutdown pc
@Charlie Kravetz: From the GNU GRUB Manual 0.97: (http://www.gnu.org/software/grub/manual/grub.html#halt) [quote] Command: halt --no-apm The command halts the computer. If the --no-apm option is specified, no APM BIOS call is performed. Otherwise, the computer is shut down using APM. [/quote] It clearly states [...]computer is shut down[...]. -- Halt entry doesn't shutdown pc https://bugs.launchpad.net/bugs/220543 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 275410] Re: firefox wrapper script breaks sensible-browser, gnome-www-browser, and firefox-3.0
** Tags added: qa-intrepid-platform -- firefox wrapper script breaks sensible-browser, gnome-www-browser, and firefox-3.0 https://bugs.launchpad.net/bugs/275410 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 186167] Re: dmesg: Driver 'sd' needs updating - please use bus_type methods
** Tags added: qa-intrepid-platform -- dmesg: Driver 'sd' needs updating - please use bus_type methods https://bugs.launchpad.net/bugs/186167 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 277543] Re: MurrinaStormCloud has some confusing characteristics
** Tags added: qa-intrepid-platform -- MurrinaStormCloud has some confusing characteristics https://bugs.launchpad.net/bugs/277543 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 277536] Re: Selecting a theme other than MurrinaStormCloud results in the default gtk theme being used instead of the actual theme.
** Tags added: qa-intrepid-platform -- Selecting a theme other than MurrinaStormCloud results in the default gtk theme being used instead of the actual theme. https://bugs.launchpad.net/bugs/277536 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 277521] Re: Kernel panic on 8.10 beta
** Tags added: qa-intrepid-platform -- Kernel panic on 8.10 beta https://bugs.launchpad.net/bugs/277521 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 276979] Re: Set sane defaults for preferred applications
** Tags added: qa-intrepid-platform -- Set sane defaults for preferred applications https://bugs.launchpad.net/bugs/276979 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 276657] Re: Main menu is still in English after installation from LiveCD
** Tags added: qa-intrepid-platform -- Main menu is still in English after installation from LiveCD https://bugs.launchpad.net/bugs/276657 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 197802] Re: Can not eject
Using a fully updated 8.04.1 Hardy release and using the latest flash- firmware for my CD/DVD burner, I couldn't reproduce this bug anymore while burning the Intrepid Alpha 5 liveCD. Therefor I have set the status to Fix Released. If anyone is still able to reproduce, feel free to reopen the bug and describe the reproduction process along with the used Ubuntu release. ** Changed in: brasero (Ubuntu) Status: Incomplete = Fix Released -- Can not eject https://bugs.launchpad.net/bugs/197802 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 199005] Re: Unmount is not possible on floppy drives
Personally I don't think Bug 200936 is the same as this one, because: 1. The error message isn't the same, so the trigger for the error message can be different and so can be the cause for the error. 2. This bug receives an corresponding entry in /etc/mtab, while Bug 200936 receives an error stating it has no corresponding entry in /etc/mtab. Personally I don't think Bug 204261 is the same as this one, because: 1. It's basically 2 reports in one: a request for an umount-option and a report of an error upon eject. 2. No-one confirmed the Bug 204261, no-one was able to reproduce the bug and the bug reporter considers it as fixed. -- Unmount is not possible on floppy drives https://bugs.launchpad.net/bugs/199005 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 200936] Re: [Hardy A6] remote HDD: Thunar's eject failes, Terminal works
Personally I think that having more than one filesystem on the external HDD, with one of them NTFS, is the source of the problem. I have read posts on ubuntuforums.org which are stating just the same problem. And Bug 199005 gives an different error message than this one, so the trigger for the error message can be different and so can be the cause for the error. ** Also affects: thunar-volman (Ubuntu) Importance: Undecided Status: New ** Changed in: thunar-volman (Ubuntu) Status: New = Confirmed -- [Hardy A6] remote HDD: Thunar's eject failes, Terminal works https://bugs.launchpad.net/bugs/200936 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 200936] Re: [Hardy A6] remote HDD: Thunar's eject failes, Terminal works
My apologies for the lack of information. Let me give another shot at it: To start, I shall give some information about my external HDD (see Bug attachments: fdisk on external HDD) In brief, a 300 GB disk, with a primary partition of 150 GB in NTFS and 150 GB in FAT32. First I place my laptop on the table and next to it I place my external HDD. Then I connect my laptop with the external HDD through a USB-cable. After that I fire up my external HDD, and when the external HDD is spinning at operation speed, I fire up my laptop. My laptop then boots Xubuntu 8.04.1 (Linux Druif 2.6.24-18-generic #1 SMP Wed May 28 20:27:26 UTC 2008 i686 GNU/Linux) and I login with my user name and password. On my desktop I see both partitions, of my external HDD, with there corresponding labels. When I right click on one of those partitions, I see that the option mount as well as eject are active. (Like in Bug attachment: Both options with partition #). If I left click twice on one of those partitions, I get a thunar-window with a list of the files and folders of the chosen partition, just as you would expect and the partition is mounted. If I then return to my desktop and right click on the partition icon, and chose the eject option I get what's described in my bug description at Step 4: a pop-up window Eject Failed - Unable to eject BACKUP : An unknown error occured (where BACKUP is the label of one of my partitions) and thunar-windows of every partition of my external HDD. So I have done some additional testing and I have come up with following results: * Mounting a partition of my external HDD Via left clicking twice on icon on desktop: works Via right clicking on icon on desktop and choosing mount: works Via terminal command sudo mount /dev/sdb1: fails - Error message mount: can't find /dev/sdb1 in /etc/fstab or /etc/mtab * Unmounting a partition of my external HDD Via terminal command sudo umount /dev/sdb1: works * Ejecting my external HDD Via right clicking on icon on desktop and choosing eject: fails - Error window Eject Failed - Unable to eject ' ': An unknown error occured (with partition's label between the ' ') - all partitions are of my external HDD are mounted. - thunar-windows of every partition of my external HDD. Via terminal command sudo eject /dev/sdb: fails - No error message - all partitions are of my external HDD are mounted. - thunar-windows of every partition of my external HDD. Via terminal command gksu thunar and right click eject: fails - Error window Eject Failed - Unable to eject ' ': An unknown error occured (with partition's label between the ' ') - all partitions are of my external HDD are mounted. - thunar-windows as user of every partition of my external HDD and thunar-windows as root of every partition of my external HDD And the answer to your question who owns the drive/partition: See Bug attachments ls -l of drive and partitions. In brief: the root owns the drive and partitions. I hope I have the information you asked for, and if you need anything else, just ask ;) ** Attachment added: fdisk on external HDD http://launchpadlibrarian.net/16228102/fdisk_External_HDD.txt -- [Hardy A6] remote HDD: Thunar's eject failes, Terminal works https://bugs.launchpad.net/bugs/200936 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 200936] Re: [Hardy A6] remote HDD: Thunar's eject failes, Terminal works
** Attachment added: ls -l of drive and partitions http://launchpadlibrarian.net/16228154/ls_of_external_HDD.txt -- [Hardy A6] remote HDD: Thunar's eject failes, Terminal works https://bugs.launchpad.net/bugs/200936 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 200936] Re: [Hardy A6] remote HDD: Thunar's eject failes, Terminal works
** Changed in: thunar (Ubuntu) Status: Incomplete = Confirmed -- [Hardy A6] remote HDD: Thunar's eject failes, Terminal works https://bugs.launchpad.net/bugs/200936 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 239121] Re: Challange one crashes to desktop
I'm capable to run Challenge One in practice mode without any problems... Also I have noticed that if I want to play Challenge One in campaign mode, the little preview image is a yellow question mark... Instead of the preview image in practice mode... -- Challange one crashes to desktop https://bugs.launchpad.net/bugs/239121 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 239121] Re: Challange one crashes to desktop
** Attachment added: Terminal Output when trying to run Challenge One in campaign mode http://launchpadlibrarian.net/15674279/Terminal%20Output.txt -- Challange one crashes to desktop https://bugs.launchpad.net/bugs/239121 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 239123] Re: Challange one: mismatch description vs. goals
After a few hours and knowing the course by heart I managed to make 2:37.21 and 63 herrings. But If this is Challenge One, I don't wanna know what the other challenges will bring... -- Challange one: mismatch description vs. goals https://bugs.launchpad.net/bugs/239123 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 239123] Re: Challange one: mismatch description vs. goals
I have the feeling there about 70 to collect if you chose the right path every time. So 50 would allow to miss a few, sound oké. And three minutes is challenging enough since you can't effort a lot of mistakes. So, green light from me. -- Challange one: mismatch description vs. goals https://bugs.launchpad.net/bugs/239123 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 129280] Re: KeepassX is not associated with .kbd files
** Also affects: xubuntu-default-settings (Ubuntu) Importance: Undecided Status: New ** Also affects: kubuntu-default-settings (Ubuntu) Importance: Undecided Status: New -- KeepassX is not associated with .kbd files https://bugs.launchpad.net/bugs/129280 You received this bug notification because you are a member of Kubuntu Team, which is subscribed to kubuntu-default-settings in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 235499] Re: keepass doesn't start
Try to run keepassx instead of keepass in your terminal. -- keepass doesn't start https://bugs.launchpad.net/bugs/235499 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 239121] [NEW] Challange one crashes to desktop
Public bug reported: Binary package hint: extremetuxracer *** Platform *** Xubuntu Hardy 8.04 extremetuxracer 0.4-0ubuntu1 *** Current behavior *** Step 1. Game untill you have unlocked the following: Campaign: The Niehoff Expierence Cup: The Final Challange Race: Challange One Step 2. Navigate through the menu's to the above and click on race. Step 3. Notice that Extreme Tux Racer crashes to desktop *** Expected behavior *** Step 1. The same Step 2. The same Step 3. The game starts *** Reproducibility *** Always *** Note *** If someone needs additional info, please provide the commands I should execute, and just ask ahead ;) ** Affects: etracer Importance: Undecided Status: New ** Affects: extremetuxracer (Ubuntu) Importance: Undecided Status: New ** Also affects: etracer Importance: Undecided Status: New -- Challange one crashes to desktop https://bugs.launchpad.net/bugs/239121 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 239123] [NEW] Challange one: mismatch description vs. goals
Public bug reported: Binary package hint: extremetuxracer *** Platform *** Xubuntu Hardy 8.04 extremetuxracer 0.4-0ubuntu1 *** Issue description *** Campaign: The Niehoff Expierence Cup: The Final Challange Race: Challange One Race description says: [...]Try to catch more then 60 hearings[...] Goal description says: Hearing: 5 *** Note 1 *** I haven't been able to test if 60 hearings is even possible, since I'm affected with bug #239121. I haven't been able to test if 5 hearings is a realistic goal, since I'm affected with bug #239121. *** Note 2 *** If someone needs additional info, please provide the commands I should execute, and just ask ahead ;) ** Affects: etracer Importance: Undecided Status: New ** Affects: extremetuxracer (Ubuntu) Importance: Undecided Status: New ** Also affects: etracer Importance: Undecided Status: New -- Challange one: mismatch description vs. goals https://bugs.launchpad.net/bugs/239123 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 238183] [NEW] Useless memory consumption
Public bug reported: Binary package hint: system-tools-backends *** Platform *** Xubuntu Hardy 8.04 system-tools-backend 2.6.0-0ubuntu7 When you use the Shared Folders menu-entry for the first time and do nothing but hit every close button you see, your memory usage will be increased for about 3 minutes by 90 MiB, and for 10 MiB untill the next reboot. *** Reproduction Problem 1*** Step 1. Open Shared Folders through the drop-down menu Applications. Step 2. You get a pop-up window where you are asked to Install Services, click on the Close-button. Step 3. Then you see the remaining window titled Shared Folders. Click on the Close-button. Step 4. Your memory has now increased with around 90 MiB. Details: 8x SystemToolsBack 10MiB ~ 13 MiB SystemToolsBack: /usr/bin/perl /usr/share//system-tools-backends-2.0/scripts/SystemToolsBackends.pl -m AllWithDifferentOptions Step 5. After a while, around 3 minutes, they all are all cleared, expect 1 SystemToolsBack remains (/usr/bin/perl /usr/share//system-tools-backends-2.0/scripts/SystemToolsBackends.pl -m Platform) This SystemToolsBack -m Platfrom also survives a log-out / log-in. You have to reboot before it's cleared. *** Expected behavior *** Step 1 through step 3 the same. Step 4. Immediate clearance of memory usage. Step 5. Immediate clearance of memory usage. *** Additional note *** I have found bug #64560 describing the problem for Step 5. Nevertheless, this bug isn't a duplicate of bug #64560 because the bug described here puts bug #64560 in a bigger picture and the origin of problem for Step 4 can easily be totally different for bug #64560. I shall also reopen bug #64560 since it happened again and will add a reference to this bug. ** Affects: system-tools-backends (Ubuntu) Importance: Undecided Status: New -- Useless memory consumption https://bugs.launchpad.net/bugs/238183 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 64560] Re: System Tools Backends uses 9 mb of writable memory
I'm reopening this bug since I suffer from this bug with version 2.6.0-0ubuntu7 on a Xubuntu Hardy 8.04. I also found even more memory issues, as I have described in bug #238183, but those don't have to be related to this bug. ** Changed in: system-tools-backends (Ubuntu) Status: Fix Released = Confirmed -- System Tools Backends uses 9 mb of writable memory https://bugs.launchpad.net/bugs/64560 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 236257] [NEW] Dubble entry Kubuntu liveCD
Public bug reported: Binary package hint: tasksel Platfrom: Xubuntu Hardy 8.04 Tasksel lists two times Kubuntu live CD at the end of the list, so the user doesn't know which one to choose. Scenario 1: One of the entries is Kubuntu with KDE 3.5 and the other is with KDE 4.0 Suggested solution: rename the entries with Kubuntu live CD (KDE 3.5) and Kubuntu live CD (KDE 4.0) Scenario 2: Both entries do the same thing. Suggested solution: remove one of them :P Other scenario's are possible, but I can't think of any other. ;) ** Affects: tasksel (Ubuntu) Importance: Undecided Status: New -- Dubble entry Kubuntu liveCD https://bugs.launchpad.net/bugs/236257 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 184440] Re: [nvidia] Blue hue in all videos
I have read a report today, that if you uninstall totem/GStreamer, and install totem/Xine, it should prevent from blueing your video. Maybe the people here can give it a shot? -- [nvidia] Blue hue in all videos https://bugs.launchpad.net/bugs/184440 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 190414] Re: Clocksource tsc unstable add 10 seconds to the boot time.
Oké, thanks for confirming, it doesn't solve it for me either... @nappsoft: Sorry, I have read over that one... -- Clocksource tsc unstable add 10 seconds to the boot time. https://bugs.launchpad.net/bugs/190414 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 193970] Re: iwl3945 | iwl4965: Wireless can't be activated after disabling kill switch
@Pihhan: So if I understand correctly: If you install hardy with the 2.6.24 kernel without adding anything (like mine), there is no problem. But if you install hardy with 2.6.25 you do have the problem? So we are speaking of regression from the 2.6.24 to the 2.6.25? -- iwl3945 | iwl4965: Wireless can't be activated after disabling kill switch https://bugs.launchpad.net/bugs/193970 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 58386] Re: ACPI: Looking for DSDT ... not found! (message during boot)
Still there in Hardy ** Also affects: linux-source-2.6.24 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Sourcepackagename: linux-source-2.6.24 = linux Assignee: (unassigned) = Ubuntu Kernel ACPI Team (ubuntu-kernel-acpi) -- ACPI: Looking for DSDT ... not found! (message during boot) https://bugs.launchpad.net/bugs/58386 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 131106] Re: KeePassX crashes when deleting a group contaning entries
Installing keepassx - 0.3.1-0ubuntu1 from the PPA of Felix Geyer (KeePassX Developer) solves indeed the described problem. Thanks Ian Stride for pointing that out :) ** Changed in: keepassx (Ubuntu) Status: Confirmed = Fix Released -- KeePassX crashes when deleting a group contaning entries https://bugs.launchpad.net/bugs/131106 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 215944] Re: Please sync keepassx 0.3.1-1 from debian unstable
Keepassx 0.3.1-1 is released in Intrepid: https://launchpad.net/ubuntu/+source/keepassx/ ** Changed in: keepassx (Ubuntu) Status: New = Fix Released -- Please sync keepassx 0.3.1-1 from debian unstable https://bugs.launchpad.net/bugs/215944 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
