[Bug 157777] Re: gutsy amd64 freeze crash lockup
I'm not sure if I should post this info here as if I use kernel 2.6.24-19 now, but maybe it is usefull for older kernels too... Or for you kernel developers ;-) Found some things worth testing on the Linux NVidea forum: http://www.nvnews.net/vbulletin/showthread.php?t=46678 and http://www.nvnews.net/vbulletin/showthread.php?t=58498 I am testing right now Kernel command line: root=UUID=----x976d1bc ro nmi_watchdog=0 quiet splash idle=poll maxcpus=1 where I manually added "idle=poll maxcpus=1". Last 2,5 hours no screenflashing and short freezes, so maybe worth testing for you too... This is of course not a real solution, why using 1 CPU when I have 2! test Configuration: AMD Turion 64 X2 mobile TL-56 2 GB memory nVidia Corporation GeForce Go 7200 rev 161 256 MB (shared) Original clean Ubuntu 8.04 installation, fully updated. Linux version 2.6.24-19-generic ([EMAIL PROTECTED]) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Wed Jun 4 16:35:01 UTC 2008 (Ubuntu 2.6.24-19.33-generic) NVIDIA UNIX x86 Kernel Module 169.12 Thu Feb 14 17:53:07 PST 2008 -- gutsy amd64 freeze crash lockup https://bugs.launchpad.net/bugs/15 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
Re: [Bug 157777] Re: gutsy amd64 freeze crash lockup
After having lots of problems with short freezes (as discribed earlier) I did a fresh install of Ubuntu 8.04 (Hardy) on a brand new harddisk in my HP Pavilion dv6361eu. This did the trick for me, my problems are gone. The Hardy cd installed driver NVidea version 169.12 just out of the box. Best of it is maybe that CPU scaling is installed right out the box too! maybee you should give it try too! -- gutsy amd64 freeze crash lockup https://bugs.launchpad.net/bugs/15 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 157777] Re: gutsy amd64 freeze crash lockup
It's sad, I've had the same short freezes again in kernel, but less, less frequent: Linux version 2.6.24-16-generic ([EMAIL PROTECTED]) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Thu Apr 10 13:23:42 UTC 2008 (Ubuntu 2.6.24-16.30-generic) and Linux version 2.6.24-18-generic ([EMAIL PROTECTED]) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Wed May 28 20:27:26 UTC 2008 (Ubuntu 2.6.24-18.32-generic) -- gutsy amd64 freeze crash lockup https://bugs.launchpad.net/bugs/15 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 157777] Re: gutsy amd64 freeze crash lockup
Maybe I have something usefull... I found these messages for the second time in dmesg just after/on/before the short freezes I experience: "[ 6797.155790] NVRM: Xid (0005:00): 6, PE 0280 1400 fc3c 00ff [ 6797.171010] NVRM: Xid (0005:00): 36, L1 -> L0 " found NVRM on another place in dmesg: "[ 39.932136] NVRM: loading NVIDIA UNIX x86 Kernel Module 169.12 Thu Feb 14 17:53:07 PST 2008" I have short lockups of the screen (x-server). I can move the mouse but no reaction on mouseclicks. No response from hitting keyboard (e.g. caps lock). I only have SHORT lockups (I guess 10 seconds). I have seen them most in Firefox where I do a lot of mousescrolling (USB mouse). This is my configuration, if you need more info, feel free to ask for it, I wrote some more info to textfiles! Hardware: laptop HP Pavilion dv6361eu CPU: AMD Turion(tm) 64 X2 Mobile Technology TL-56 stepping 02 Linux version 2.6.24-18-generic ([EMAIL PROTECTED]) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Wed May 28 20:27:26 UTC 2008 (Ubuntu 2.6.24-18.32-generic) Kernel command line: root=UUID=baa5188b-677c--aa72- ro nmi_watchdog=0 quiet splash (II) NVIDIA GLX Module 169.12 Thu Feb 14 18:45:56 PST 2008 -- gutsy amd64 freeze crash lockup https://bugs.launchpad.net/bugs/15 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 307106] [NEW] only 1 out of 3 emailboxes visable, and home-box does not appear. Restarting or setting changes don't solve the problem
Public bug reported: Binary package hint: thunderbird After startup of Thunderbird , the left pane is not visible where I normally would find all of my 3 email boxes and the 'home box'. Now, only 1 emailbox is visible, while the machine asks me for the passwords of all 3 mailboxes (which is OK). After submitting these passwords nothing changes however. Thunderbird 2.0.0.18 Ubuntu 2.6.24-22-generic There might be a correlation with a problems and programm use shorty before this failure (?) Yesterday I encountered a problem in Audacity 1.3.4 beta: Audacity refused to cancel an exportation order (MP3 to MP3) that was pursuing. Nothing moved in the font. Next I couldn't redo or do anything, and the programm wouldn't quit. Everything was fixed and nothing would move. So I enforced a quit by unplugging the electricity to the computer. After a restart I removed Audacity from Ubuntu, and, after a new restart, downloaded and installed Audacity again. After starting it up, Audacity told me that continuing would cause a sever problem because the Temporary files were filled up (it could even lead to the crashing of my computer...). Next I couldn't stop Audacity and even the Ubuntu log off button disappeared when I wanted to stop the computer! After several restarts and working with different programmas, to my surprise Audacity started up well again. This problem of Audacity not reacting to the cancel button (when exporting) I experenced more often, but then I always could quit Audacity afterwards. It didn't work out that way now. If relevant in any way (?): Just before this new Audacity problem occurred I worked with the Bit Torrent programm (for the first time) letting this run for long hours to download some files. ProblemType: Bug Architecture: i386 Date: Thu Dec 11 10:49:52 2008 Dependencies: DistroRelease: Ubuntu 8.04 Package: mozilla-thunderbird None [modified: /var/lib/dpkg/info/mozilla-thunderbird.list] PackageArchitecture: all ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: thunderbird Uname: Linux 2.6.24-22-generic i686 ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- only 1 out of 3 emailboxes visable, and home-box does not appear. Restarting or setting changes don't solve the problem https://bugs.launchpad.net/bugs/307106 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 115969] Re: drag to queue causes crash
** Attachment added: "Dependencies.txt" http://librarian.launchpad.net/7725445/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://librarian.launchpad.net/7725446/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://librarian.launchpad.net/7725447/ProcStatus.txt -- drag to queue causes crash https://bugs.launchpad.net/bugs/115969 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 115969] Re: drag to queue causes crash
Further research suggests that the problem is not caused by the act of dragging to file to the play queue. Rather, after doing that, I then attempted to move the newly added item, by dragging it upwards, to a higher position in the queue. On releasing the mouse button, all the existing queue items disappear and are replaced by the tracks from yesterday. At this point rbox is in a fairly fragile state, any/some further queue operations cause it to crash/exit... -- drag to queue causes crash https://bugs.launchpad.net/bugs/115969 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 115969] Re: drag to queue causes crash
** Attachment added: "output from gdb session ..." http://librarian.launchpad.net/7726011/gdb-session-rhythmbox.txt -- drag to queue causes crash https://bugs.launchpad.net/bugs/115969 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 115969] Re: drag to queue causes crash
Oh right, the output from the tee (much the same - sorry) ... ** Attachment added: "gdb rhythmbox 2>&1 | tee gdb-rhythmbox.txt" http://librarian.launchpad.net/7726013/gdb-rhythmbox.txt -- drag to queue causes crash https://bugs.launchpad.net/bugs/115969 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 195982] Re: Shift key (and caps lock) stop working when using VMWare
Do you experience any reliability issues in the Ubuntu host when VmWare tools is installed in the VPS? I, and some others, have major stability issues, especially on opening new applications or dialog boxes. I have NOT tested this with the latest xorg updates released in the last week so maybe that part has been fixed. -- Shift key (and caps lock) stop working when using VMWare https://bugs.launchpad.net/bugs/195982 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 195982] Re: Shift key (and caps lock) stop working when using VMWare
Your logs may well show some xorg or general segfault errors in this case. Makes the system kind of hard to use! An exit out of xorg is all that is needed to recovery (a reboot does not seem to be required). OK, at least we have more data. Not sure how that helps given I can't do much more than test. At least the problem seems to be associated to the vmware-tools within the client VPS. For now I just don't use vmware- tools. I suspect an update from VmWare will be the final solution. -- Shift key (and caps lock) stop working when using VMWare https://bugs.launchpad.net/bugs/195982 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 195982] Re: Shift key (and caps lock) stop working when using VMWare
Removing vmware tools from the client system also has proven reliable for me. I have had an occasional (every 3 days or so) full system lockup but have not been able to track it down to VmWare at this time. -- Shift key (and caps lock) stop working when using VMWare https://bugs.launchpad.net/bugs/195982 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 195982] Re: Shift key (and caps lock) stop working when using VMWare
Just had the problem again and this time with the normal NV driver. I never switched to full screen VMware (always ran windowed). So I have reproduced the problem under similar circumstances others have reported. I still feel there is some interaction with the xorg as the nvidia driver consistently fails much sooner than the nv driver. Once a failure occurs dialog boxes become highly unreliable and crashes (outside of VMware) become common. I am now going back to the nvidia driver and disabling the vmware tools just to see if that might be an issue. Hopefully going back to nvidia driver will accelerate any issues I have. Any suggestions for further testing are encouraged. Of course a VMware solution would be rather handy -- Shift key (and caps lock) stop working when using VMWare https://bugs.launchpad.net/bugs/195982 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 195982] Re: Shift key (and caps lock) stop working when using VMWare
Since my last post on 4/6 I have NOT had the issue occur. I removed the vmware-tools from the virtual server and now use ctrl-alt to switch. I am running in a window mode. I agree that this appears to be a vmware issue, although it would be nice to have xorg a tad more robust and not crashing dialog boxes on us when the error occurs. -- Shift key (and caps lock) stop working when using VMWare https://bugs.launchpad.net/bugs/195982 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 117133] Re: FEISTY (final): remove usb disk : fail to eject
I can confirm this problem on complete up-to-date Ubuntu Feisty (gcc (GCC) 4.1.2 (Ubuntu 4.1.2-0ubuntu4)) kernel ( 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux) with portable USB 2 harddisk. With a 2GB Sandisk USB stick and with USB 1.1 connected digital camera confirmed too. It doesn't matter if files are only red or read/write is used. Haven't used terminal commands for manipulating data on disk, only Nautilus copy/paste actions as user and in a different Nautilus screen as root. It doesn't matter if Nautilus is open or closed when unmounting. Looks like USB software "finds" directly after unmount new USB hardware and opens Nautilus to show the contents. It should only react if hardware is plugged in and not when hardware was already plugged in. Command 'sudo eject /media/disk' in terminal helps to unmount for me, thanks! -- FEISTY (final): remove usb disk : fail to eject https://bugs.launchpad.net/bugs/117133 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 195982] [NEW] Shift key (and caps lock) stop working
Public bug reported: After a day or so of running the shift key mysteriously stops working as does the cap lock. In other words I cannot enter shifted characters of any kind. The keyboard is connected to a KVM and all other systems respond to it properly. In additional any VMWare sessions I have open respond correctly. So I have the condition where all non-vmware applications in Ubuntu Hardy (all updates applied as of 2008-02-26 at 12:43 UTC) fail to recognize the shift key BUT applications within an active (a paused/restarted session also works) VMWare sessions running DO recognize the key. When this condition occurs ALL applications (except those within a VMWare session) are also unstable and will usually crash within a few keystrokes.If I continue to operate in this mode. I cannot pinpoint what, if any, application triggers this. It has always happened while working within terminal/browser/vmware sessions and NOT when opening a new application. It could be related to the KVM switch, but none of my other systems (2 Mandriva, 1 Windows) are affected by this. This bug has been present on my system for a number of days across daily updates and reboots (if the update requested it) and I think since I installed Hardy Alpha 1. A work around: log off and back on. A reboot/restart does not appear to be needed. Error logs show some unusual activity. --- MARK ... ... kernel ... rtc lost 7 interrupts ... --- MARK --- Plus some segfaults indicating which application crashed as I tried to type into it (mouse works fine). System: HP dv9743cl (which otherwise works lovely) Ubuntu: Hardy 8.04 (from lsb-release) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: keyboard -- Shift key (and caps lock) stop working https://bugs.launchpad.net/bugs/195982 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 117133] Re: FEISTY (final): remove usb disk : fail to eject
Has anyone confirmed the problem in 7.10? -- FEISTY (final): remove usb disk : fail to eject https://bugs.launchpad.net/bugs/117133 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 157777] Re: gutsy amd64 freeze crash lockup
Some additional info. Today it is CPU1 using 100% capacity when locking, CPU2 almost no activity. Till now always 1 Core that is 100% while locked. Surfing launchpad I found a refference to bug: https://bugs.launchpad.net/bugs/109643 Difference is that I can work after some time of waiting (when the lockup is over). But I have those messages to: ~$ dmesg | tail [ 159.756000] Disabling IRQ #7 [ 164.86] NVRM: Xid (0005:00): 6, PE 0f28 ff83b9ec d1f8 ffc5e0fa [ 229.12] NVRM: Xid (0005:00): 26, Ch 01ff M 1ffc D intr [ 229.12] NVRM: Xid (0005:00): 1, Ch 01ff M 1ffc D intr [ 229.12] NVRM: Xid (0005:00): 7, Ch 01ff M 1ffc D intr [ 229.128000] NVRM: Xid (0005:00): 6, PE 0bd8 00ff f85c 00ff 00ff [ 895.464000] NVRM: Xid (0005:00): 6, PE 0fb0 00ff fc50 00ff 00ff [ 896.024000] NVRM: Xid (0005:00): 6, PE 0fb0 fdbc 00ff 00ff [ 896.068000] NVRM: Xid (0005:00): 6, PE 0fb0 00ff ec70 00ff 00ff [ 4967.664000] spurious 8259A interrupt: IRQ15. ~$ dpkg -l nvidia-\* | grep ii ii nvidia-glx-new 100.14.19+2.6.22.4-14.10 NVIDIA binary XFree86 4.x/X.Org 'new' driver ii nvidia-kernel-common 20051028+1ubuntu7NVIDIA binary kernel module common files I don't know if it has anything to do with it but I can't use sudo cpufreq-set -g ondemand anymore, not error or something but processorspeed can't be changed after the upgrade, while it worked fine in Feisty. The same for the nice program: ~$ sudo /usr/sbin/laptop-mode start sudo: /usr/sbin/laptop-mode: command not found There was a suggestion to disable powernowd in the URL above. I'll test that tomorrow. ** Attachment added: "lsmod.txt" http://launchpadlibrarian.net/11009493/lsmod.txt -- gutsy amd64 freeze crash lockup https://bugs.launchpad.net/bugs/15 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 157777] Re: gutsy amd64 freeze crash lockup
Found some links that migh't be helpfull for some of us. Please report your solutions here! http://ubuntuforums.org/showthread.php?t=585714(thread with 144 replies!) http://ubuntuforums.org/showthread.php?t=412125(thread with 820 replies!) Ooh see, we're not alone :-( -- gutsy amd64 freeze crash lockup https://bugs.launchpad.net/bugs/15 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 157777] Re: gutsy amd64 freeze crash lockup
update: I followed one of the links from the forums I gave before: http://ubuntuforums.org/showthread.php?t=512059 I installed Envy as helper software to install the most recent NVidia driver for my videocard (version 169.07). And good news I had only one Freeze in 6-8 hours yesterday! And today no freeze till now! So my problem seems to be a driver problem in combination with Gutsy. Developers: thanx -- gutsy amd64 freeze crash lockup https://bugs.launchpad.net/bugs/15 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 117133] Re: FEISTY (final): remove usb disk : fail to eject
Upgrading to Gutsy (7.10) solved this issue for me too. Good work! -- FEISTY (final): remove usb disk : fail to eject https://bugs.launchpad.net/bugs/117133 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 157777] Re: gutsy amd64 freeze crash lockup
I upgraded from 7.04 to 7.10 on laptop HP. Didn't have problems in 7.04 but have some now. I have short lockups of the screen (x-server). I can move the mouse but no reaction on mouseclicks. No response from hitting keyboard (caps lock). The magic SysRq works, did not test because I only have SHORT lockups (I guess 10 seconds). I have seen them most in Firefox where I do a lot of mousescrolling. Addition: sometimes the mousecursor stops moving. Resizing of a window (systemmonitor) resulted in a lockup too. Sometimes... Page down with keyboard in Firefox did not result in visible lockup till now... When screen locks up and I look at the Systemmonitor I always find cpu2 using 100% capacity (today), no memory increase. CPU goes back to normal 5% when lockup stops after some time. Scrolling in a webpage in Firefox costs about 40% CPU (for each CPU's simultanously). Sometimes I reach 60%, and then the screen seems to freeze, CPU2 is 100% for some time and goes back again to 3% or so. I use a HP Pavilion dv6361eu: AMD Turion 64 X2 mobile TL-56 2 GB memory NVIDIA GeForce Go 7200 256 MB (shared) MCP51 Serial ATA Controller (Presario V6133CL) Hitachi HTS 54161160 GB HDD Microsoft Natural Ergonomic Keyboard 4000 (yes, M$ works together with Ubuntu LOL) USB Typhoon 3 button mouse USB VideoDriver: NVidea 100.14.19 ([EMAIL PROTECTED] TFT) kernel parameters (kernel 2.6.22-14-generic): acpi=force noapic apci=routeirq pnpbios=off pci=routeirq Hint: stop scrolling, clicking or typing or whatever directly after a lockup, more clicks cost more time to recover. Hope this helps... -- gutsy amd64 freeze crash lockup https://bugs.launchpad.net/bugs/15 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 115969] drag to queue causes crash
Public bug reported: Binary package hint: rhythmbox When I dragged a mp3 file from the file browser to the rbox play queue area, suddenly the existing items in the queue were replaced by previously played/removed items from the previous day (really). Attempting to remove one of these items (click right -> remove) crashed rbox. (This is an Ubuntu 704 system, was upgraded from ubu 606, to 610, to 704) ProblemType: Bug Architecture: i386 Date: Mon May 21 14:23:58 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/rhythmbox Package: rhythmbox 0.10.0-0ubuntu2 PackageArchitecture: i386 ProcCmdline: rhythmbox ProcCwd: /space/home/robb ProcEnviron: LANGUAGE=en_GB:en PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox Uname: Linux isar 2.6.20-15-386 #2 Sun Apr 15 07:34:00 UTC 2007 i686 GNU/Linux ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: Unconfirmed -- drag to queue causes crash https://bugs.launchpad.net/bugs/115969 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 195982] Re: Shift key (and caps lock) stop working when using VMWare
I am slowly working out when this happens. So far I have the following data points 1. I reinstalled Ubuntu, from scratch using the BETA download 2. I had NO problems with or without VmWare using the nv driver 3. I finally figured out how to enable Nvidia proprietary driver 4. Problems began anew within a day or so 5. Once the problem begins Ubuntu is HIGHLY unstable with crashes in all range of applications. The VMwre session is unaffected (which makes sense). Recover is log on/off. I realize this is not very scientific and possibly of minimal value. I have now disabled the proprietary Nvidia drivers (gads video is slow now) to see if that helps. I run in VMware extensively as I am using it for development, but I suspect VMware is a red herring. I think the problem is with the proprietary Nvidia drivers on my HP Laptop (8600 m). My hypothesis is that disabling Nvidia proprietary drivers (the reason I went with Ubuntu in the first place) will resolve the keyboard and stability issues. PS: Disabling the Nvidia driver required an edit to my xorg, un-checking the box in the Hardware Drivers was ineffective, even with a reboot. -- Shift key (and caps lock) stop working when using VMWare https://bugs.launchpad.net/bugs/195982 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 195982] Re: Shift key (and caps lock) stop working when using VMWare
There may be more to this bug than just VMware or just Nvidia. I think until it can be isolated it is best to leave this bug as is. I don't see a reason to spawn another bug report based on a hypothesis used to isolate this one. Once more data is accumulated a new more specific bug can be filed if appropriate. I find it curious you only encounter this bug when running VMware. Out of curiosity are you using the VMware tools in the client? I am, and maybe that interaction is contributing to this problem. And just to add more confusion lets say it is an Xorg issue and some drivers are more susceptible than others. Just guessing, but some ideas to track down. So may variables that are hard to isolate since the bug does not, at least for me, happen instantly. 1. Xorg? 1.a. Video Driver contributing? 2. VMware? 2.a. VMware tools in client? -- Shift key (and caps lock) stop working when using VMWare https://bugs.launchpad.net/bugs/195982 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 195982] Re: Shift key (and caps lock) stop working when using VMWare
It's been 24 hours or so, longer than any prior good result with Nvidia drivers, and my system is stable using the "nv" driver. VMware works fine as do all other applications so far. Also resolved is the odd auto- repeat for the keyboard. Using the 'Nvidia' driver I get weird keyboard auto-repeat timeouts in VMware (long pauses to start and then VERY fast repeat). With the "nv" driver the repeats work as expected. Unfortunately the nv driver is rather slow, especially for scrolling, so it is not a good long term solution for me. I am still not sure if this is an issue with VMware,VMware tools or NVidia drivers on my system. Any suggestions on what I can do to help resolve this bug are appreciated. -- Shift key (and caps lock) stop working when using VMWare https://bugs.launchpad.net/bugs/195982 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 195982] Re: Shift key (and caps lock) stop working when using VMWare
Yes, that mirrors my case. I have found that many dialog boxes will cause the specific application to crash. Starting Thunderbird, entering the package manager, etc. Existing applications work OK but without the SHIFT/ALT/CTR. Opening a new window often causes an application crash. Have you tried switching to the to basic NV video driver and see if this is more stable? -- Shift key (and caps lock) stop working when using VMWare https://bugs.launchpad.net/bugs/195982 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 195982] Re: Shift key (and caps lock) stop working
So far no crashes in the last 24 hours (running 2.6.24-11). Plus a reboot issue (where the system locked with a LCD white screen - never reported) has also been resolved. I will continue to monitor and on any errors post the requested data. The segfaults have, usually, been submitted as a different bug. I will also attach them here if I can. As an aside, having worked with many distributions of 10 years, Ubuntu's community, dedication and ability to just make things works is very impressive. Nice work. -- Shift key (and caps lock) stop working https://bugs.launchpad.net/bugs/195982 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 109604] adept_manager db cache unopened
Public bug reported: Binary package hint: adept-manager Popup message:The APT Database could not be opened! This may be caused by incorrect APT configuration or some similar problem. Try running apt-setup and apt-get update in terminal and see if it helps to resolve the problem. System: VMware player upgraded from dapper => edgy => fiesty Kubuntu Konsole: [EMAIL PROTECTED]:/etc/apt$ sudo adept_manager X Error: BadDevice, invalid or uninitialized input device 167 Major opcode: 145 Minor opcode: 3 Resource id: 0x0 Failed to open device X Error: BadDevice, invalid or uninitialized input device 167 Major opcode: 145 Minor opcode: 3 Resource id: 0x0 Failed to open device kapture::PkgSystem::PkgSystem() [EMAIL PROTECTED]:/etc/apt$ Other: no apt-setup on my system, apt-get update runs OK ** Affects: adept (Ubuntu) Importance: Undecided Status: Unconfirmed -- adept_manager db cache unopened https://bugs.launchpad.net/bugs/109604 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for adept in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 575031] [NEW] a few bugs while and after upgrading to Ubuntu 10_04 LTS
Public bug reported: Binary package hint: software-center a few bugs while and after upgrading to Ubuntu 10_04 LTS from 8_04 : 1. Desktop-Applet problem (automatic bugreporting wasn't possible): System: Linux 2.6.31-21-generic #59-Ubuntu SMP Wed Mar 24 07:28:56 UTC 2010 i686 X Vendor: The X.Org Foundation X Vendor Release: 10604000 Selinux: No Accessibility: Disabled GTK+ Theme: Ambiance Icon Theme: ubuntu-mono-dark GTK+ Modules: canberra-gtk-module Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Traceback (most recent call last): File "/usr/lib/pymodules/python2.6/deskbar/ui/DeskbarApplet.py", line 197, in on_allocate File "/usr/lib/pymodules/python2.6/deskbar/ui/DeskbarApplet.py", line 203, in _set_image File "/usr/lib/pymodules/python2.6/deskbar/ui/AbstractCuemiacDeskbarIcon.py", line 102, in get_deskbar_icon File "/usr/lib/pymodules/python2.6/deskbar/core/Utils.py", line 126, in load_icon_from_icon_theme GError: Icon 'deskbar-applet' not present in theme --- .xsession-errors (1301 sec old) - ** (update-notifier:1579): WARNING **: log file empty (logrotate?) /var/log/apt/term.log 1569 PID TTY TIME CMD 1498 ?00:00:00 pulseaudio (firefox:1771): GLib-WARNING **: g_set_prgname() called multiple times (firefox:1829): GLib-WARNING **: g_set_prgname() called multiple times Window manager warning: Window 0x1801423 (update-man) sets an MWM hint indicating it isn't resizable, but sets min size 175 x 141 and max size 2147483647 x 2147483647; this doesn't make much sense. Window manager warning: Window 0x1801423 (update-man) sets an MWM hint indicating it isn't resizable, but sets min size 175 x 141 and max size 2147483647 x 2147483647; this doesn't make much sense. tar: Removing leading `/' from member names gnome-session[1445]: WARNING: Detected that screensaver has left the bus ** (nm-applet:1576): WARNING **: Icon nm-active-device missing: Unable to load image-loading module: /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-png.so: /lib/tls/i686/cmov/libc.so.6: version `GLIB -- 2. While upgrading, this report came up: "Could not install 'nvidia-kernel-common' "subprocess stalled pre-removal script returned error exist status 127" Normal bugreporting wasn't possible, because "not supported" 3. Error during commit: 'installArchives() failed' 4. [After upgrading and restart:] Problem while loading "OAFIIF Desktop-Applet" (and choice: either or not delete from configuration (I didn't)) 5. Unresponsive script at restart of Firefox after a update of NoScript: chrome://bp/content/bp.js:881 (and choice: either or not stop script (I did stop it)) This bug appearde a few times. Later fe. ending in bp.js:996) ** Affects: software-center (Ubuntu) Importance: Undecided Status: New -- a few bugs while and after upgrading to Ubuntu 10_04 LTS https://bugs.launchpad.net/bugs/575031 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 470293] Re: gnome-volume-control crashed with SIGFPE in g_closure_invoke()
Thank you for taking a look at this "bug". I installed all necessary software, ready to do a backtrace. But... I'm more or less happy to tell you this crash happened only once till now. Just after the first restart after the update from 8.04 to 9.04. Did some short testing with changing all buttons, volumes, sounds and so on. The output is this: -- (gdb) run gnome-volume-control Starting program: /usr/bin/gnome-volume-control gnome-volume-control [Thread debugging using libthread_db enabled] [New Thread 0xaf4dfb70 (LWP 24423)] [Thread 0xaf4dfb70 (LWP 24423) exited] Program exited normally. (gdb) quit -- Nothing went wrong... Is there anything else I can do? -- gnome-volume-control crashed with SIGFPE in g_closure_invoke() https://bugs.launchpad.net/bugs/470293 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 1724639] Re: Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen
Like jojo said in #49 GRUB_GFXPAYLOAD_LINUX=text solves the problem. some more info: This bug affects me after a fresh installation of lubuntu-17.10-desktop-i386 on a HP Mini 5101. installation uses kernel 4.13.0-16-generic. lspci: 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller rev 0 Kernel 4.11.0-041100_4.11.0-041100.201705041534 works fine. grub option GRUB_GFXPAYLOAD_LINUX=keep does not work, same problem comes back GRUB_GFXPAYLOAD_LINUX=text solves the problem for me! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724639 Title: Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1457616] [NEW] package ecryptfs-utils 107-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
Public bug reported: >From clean install - one of a number of failed packages to install. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: ecryptfs-utils 107-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 Date: Thu May 21 19:20:06 2015 DuplicateSignature: package:ecryptfs-utils:107-0ubuntu1.1:subprocess installed post-installation script returned error exit status 128 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2015-05-20 (2 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: ecryptfs-utils Title: package ecryptfs-utils 107-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ecryptfs-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1457616 Title: package ecryptfs-utils 107-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1457616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file"
Download 340.76 driver from http://www.nvidia.com/object/unix.html, which corrected this unnecessary glitch. On 15-01-31 01:33 PM, awol wrote: > i switched to Debian weeks ago because of THIS problem. it works well. > > > On Sun, Feb 1, 2015 at 4:03 AM, Luc Bruninx <1268...@bugs.launchpad.net> > wrote: > >> Same problem during update of the kernel 3.16.0-30 with NVIDIA driver - >> version 331.113 (nvidia 331.113-0ubuntu0.1). >> But after reboot, everything seems to be properly updated. >> >> -- >> You received this bug notification because you are subscribed to a >> duplicate bug report (1395929). >> https://bugs.launchpad.net/bugs/1268257 >> >> Title: >> nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module >> failed to build, with only error: "objdump: '... .tmp_nv.o': No such >> file" >> >> Status in nvidia-graphics-drivers-331 package in Ubuntu: >> Triaged >> Status in nvidia-graphics-drivers-331-updates package in Ubuntu: >> Triaged >> >> Bug description: >> **WARNING:** This bug has been widely reported and has *many* >> automatic subscribers. Please be considerate. >> >> **If you need help:** try searching and asking on >> http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a >> nearby user group (see http://loco.ubuntu.com or search for "LUG" in >> your area). Link back to this bug for clarity. >> >> **If you want to unsubscribe:** see >> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- >> drivers-331-updates/+bug/1268257/+subscribe. You can also change your >> settings so you don't get comments but do get notified when the bug is >> solved - see https://askubuntu.com/questions/576523 for details. >> >> **If you want to comment:** Please consider if you have something >> meaningful to contribute to the 2500+ people who will get an email. >> >> **If you are an Ubuntu developer:** thanks for looking into this! :D >> >> >> >> Nvidia kernel module failed to build on kernel 3.13.0-2 >> Yesterday when the new kernel was pushed, the dkms process failed. >> >> ProblemType: Package >> DistroRelease: Ubuntu 14.04 >> Package: nvidia-331-updates 331.20-0ubuntu9 >> ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 >> Uname: Linux 3.12.0-7-generic x86_64 >> ApportVersion: 2.13.1-0ubuntu1 >> Architecture: amd64 >> DKMSKernelVersion: 3.13.0-2-generic >> Date: Sun Jan 12 01:28:35 2014 >> InstallationDate: Installed on 2013-11-03 (69 days ago) >> InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 >> (20131016.1) >> PackageVersion: 331.20-0ubuntu9 >> SourcePackage: nvidia-graphics-drivers-331-updates >> Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel >> module failed to build >> UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) >> >> To manage notifications about this bug go to: >> >> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1268257/+subscriptions >> > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1268257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396103] [NEW] nvidia-331-updates-uvm 331.38-0ubuntu7.1: nvidia-331-updates-uvm kernel module failed to build
Public bug reported: System reported issue ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates-uvm 331.38-0ubuntu7.1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 DKMSKernelVersion: 3.13.0-40-generic Date: Tue Nov 25 03:43:35 2014 InstallationDate: Installed on 2014-09-10 (75 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723) PackageVersion: 331.38-0ubuntu7.1 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates-uvm 331.38-0ubuntu7.1: nvidia-331-updates-uvm kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396103 Title: nvidia-331-updates-uvm 331.38-0ubuntu7.1: nvidia-331-updates-uvm kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1396103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 888633] Re: picture from webcam has no color and some artifacts
The PPA libv4l fixes this problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/888633 Title: picture from webcam has no color and some artifacts To manage notifications about this bug go to: https://bugs.launchpad.net/cheese/+bug/888633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 847467] [NEW] package software-center 4.1.22 failed to install/upgrade: corrupted filesystem tarfile - corrupted package archive
Public bug reported: happened on boot after apt-get dist-upgrade ProblemType: Package DistroRelease: Ubuntu 11.10 Package: software-center 4.1.22 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 Uname: Linux 3.0.0-10-generic i686 ApportVersion: 1.22.1-0ubuntu2 Architecture: i386 Date: Mon Sep 12 00:38:25 2011 DpkgTerminalLog: Preparing to replace software-center 4.1.21 (using .../software-center_4.1.22_all.deb) ... Unpacking replacement software-center ... dpkg: error processing /var/cache/apt/archives/software-center_4.1.22_all.deb (--unpack): corrupted filesystem tarfile - corrupted package archive DuplicateSignature: Unpacking replacement software-center ... dpkg: error processing /var/cache/apt/archives/software-center_4.1.22_all.deb (--unpack): corrupted filesystem tarfile - corrupted package archive ErrorMessage: corrupted filesystem tarfile - corrupted package archive InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110803.1) PackageArchitecture: all SourcePackage: software-center Title: package software-center 4.1.22 failed to install/upgrade: corrupted filesystem tarfile - corrupted package archive UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-center (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 oneiric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/847467 Title: package software-center 4.1.22 failed to install/upgrade: corrupted filesystem tarfile - corrupted package archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/847467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 847467] Re: package software-center 4.1.22 failed to install/upgrade: corrupted filesystem tarfile - corrupted package archive
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/847467 Title: package software-center 4.1.22 failed to install/upgrade: corrupted filesystem tarfile - corrupted package archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/847467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 886538] [NEW] Webcam Image Distortion
Public bug reported: Since the install of 11.10, my ID 046d:08d7 Logitech, Inc. QuickCam Communicate STX webcam does not provide a proper image. The image is mostly black and white with graphic distortions. Programs such as MPlayer and VLC utilize the webcam without a problem, but programs such as Cheese that use gstreamer produce the distorted image. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: cheese 3.2.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Sat Nov 5 05:45:52 2011 EcryptfsInUse: Yes MachineType: Acer Aspire M1200/3200/5200 RelatedPackageVersions: cheese3.2.0-0ubuntu2 cheese-common 3.2.0-0ubuntu2 SourcePackage: linux UpgradeStatus: Upgraded to oneiric on 2011-09-26 (39 days ago) dmi.bios.date: 08/21/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R03-B1 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: RS740DVF dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR03-B1:bd08/21/2008:svnAcer:pnAspireM1200/3200/5200:pvr:rvnAcer:rnRS740DVF:rvr:cvnAcer:ct3:cvr1.0: dmi.product.name: Aspire M1200/3200/5200 dmi.sys.vendor: Acer ** Affects: cheese (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug gstreamer-error oneiric running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/886538 Title: Webcam Image Distortion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/886538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 886538] Re: Webcam Image Distortion
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/886538 Title: Webcam Image Distortion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/886538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 888633] Re: picture from webcam has no color and some artifacts
Tried the lower resolution, but had not success. Colors and artifacts are still present. Mplayer, VLC , and v4lucp, which uses Mplayer to preview, have no difficulties. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/888633 Title: picture from webcam has no color and some artifacts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/888633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 661685] [NEW] package bcmwl-kernel-source 5.60.48.36 bdcom-0ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: crash after auto update. First start of Ubuntu netbook 10.10 from 16GB USB stick on COmpac mini 110C 111DCD ProblemType: Package DistroRelease: Ubuntu 10.10 Package: bcmwl-kernel-source 5.60.48.36+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 Architecture: i386 Date: Sat Oct 16 11:12:01 2010 ErrorMessage: subprocess installed post-installation script returned error exit status 1 LiveMediaBuild: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 (20101007) SourcePackage: bcmwl Title: package bcmwl-kernel-source 5.60.48.36+bdcom-0ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 maverick ubuntu-une -- package bcmwl-kernel-source 5.60.48.36 bdcom-0ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/661685 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 661685] Re: package bcmwl-kernel-source 5.60.48.36 bdcom-0ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
-- package bcmwl-kernel-source 5.60.48.36 bdcom-0ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/661685 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 192152] Re: ubuntu studio color theme results in unreadable urls on dropdown bar w/ FF3
ubuntustudio-theme (v0.28)
firefox-3.0 (3.0+nobinonly-0ubuntu0.8.04.1)
firefox-3.0-gnome-support (3.0+nobinonly-0ubuntu0.8.04.1)
firefox-gnome-support (3.0+nobinonly-0ubuntu0.8.04.1)
Still true for Hardy, though now the default appears to be dark gray on
gray.
A workaround can be applied per Firefox profile. For a white description
and bright green URL (and white/white when hovered over), add the
following lines to
/home/{username}/.mozilla/{profile}/chrome/userChrome.css:
.ac-comment {color: #FF !important; }
.ac-comment[selected='true'] { color: #FF !important; }
.ac-url-text {color: #33FF33 !important; }
.ac-url-text[selected='true'] { color: #FF !important; }
--
ubuntu studio color theme results in unreadable urls on dropdown bar w/ FF3
https://bugs.launchpad.net/bugs/192152
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 207454] Re: Firefox is VERY slow rendering pragprog.com; becomes almost unusable
I see the same, but top shows the spike in Xorg, not in Firefox. Disabling the screen (and therefore the shared and high) stylesheet makes things snappy again. Dell Precision 670 (dual Xeon 3.0) Ubuntu 8.10 2.6.24-19-generic Firefox 3.0.1 nVidia NV45GL also using the restricted "nvidia" driver -- Firefox is VERY slow rendering pragprog.com; becomes almost unusable https://bugs.launchpad.net/bugs/207454 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 207454] Re: Firefox is VERY slow rendering pragprog.com; becomes almost unusable
Correction: I'm running Ubuntu 8.04. (Got Ibex on my mind.) -- Firefox is VERY slow rendering pragprog.com; becomes almost unusable https://bugs.launchpad.net/bugs/207454 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 207454] Re: Firefox is VERY slow rendering pragprog.com; becomes almost unusable
According to my browser history, I visited PragProg.com on 7-9-08 and I recall *not* seeing this problem then. Dave Thomas said in an email yesterday that PragProg has made no code changes to the site since then. Looking in my problem host's APT log, I see that the following suspect packages (nvidia restricted and firefox) have changed since then: 7-2: nvidia-glx-new 169.12+2.6.24.13-19.42 -> nvidia-glx-new_169.12+2.6.24.13-19.44 7-14: nvidia-glx-new 169.12+2.6.24.13-19.44 -> 169.12+2.6.24.13-19.45 7-25: xulrunner 1.9+nobinonly-0ubuntu0.8.04.1 -> 1.9_1.9.0.1+build1+nobinonly-0ubuntu0.8.04.2 7-25: firefox 3.0+nobinonly-0ubuntu0.8.04.1 -> 3.0.1+build1+nobinonly-0ubuntu0.8.04.2 7-29: xulrunner 1.9.0.1+build1+nobinonly-0ubuntu0.8.04.2 -> 1.9.0.1+build1+nobinonly-0ubuntu0.8.04.3 7-29: firefox 3.0+nobinonly-0ubuntu0.8.04.2 -> 3.0.1+build1+nobinonly-0ubuntu0.8.04.3 Rolled back firefox and the problem still exists: + nvidia-glx-new 169.12+2.6.24.13-19.45 - firefox 3.0+nobinonly-0ubuntu0.8.04.1 - xulrunner 1.9+nobinonly-0ubuntu0.8.04.1 Brought firefox up-to-date and rolled back nvidia-glx-new, problem still exists: - nvidia-glx-new 169.12+2.6.24.13-19.42 + firefox 3.0.1+build1+nobinonly-0ubuntu0.8.04.3 + xulrunner 1.9.0.1+build1+nobinonly-0ubuntu0.8.04.3 So, color me confused. -- Firefox is VERY slow rendering pragprog.com; becomes almost unusable https://bugs.launchpad.net/bugs/207454 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 301430] Re: ipv6 /etc/hosts missing localhost hostname
question answered, several examples provided ** Changed in: netcfg (Ubuntu) Status: Incomplete => Confirmed -- ipv6 /etc/hosts missing localhost hostname https://bugs.launchpad.net/bugs/301430 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 301430] Re: ipv6 /etc/hosts missing localhost hostname
I think this bug lives in ubuntu-installer/ubiquity/
currently line 1525 /scripts/install.py (revision 2954)
1515hosts = open(os.path.join(self.target, 'etc/hosts'),
'w')
1516997 print >>hosts, "127.0.0.1\tlocalhost"
15171772if domain:
1518print >>hosts, "127.0.1.1\t%s.%s\t%s" % (hostname,
domain,
1519 hostname)
1520else:
1521print >>hosts, "127.0.1.1\t%s" % hostname
1522997 print >>hosts, textwrap.dedent("""\
1523996
1524997 # The following lines are desirable for IPv6
capable hosts
1525::1 ip6-localhost ip6-loopback
1526fe00::0 ip6-localnet
1527ff00::0 ip6-mcastprefix
1528ff02::1 ip6-allnodes
1529ff02::2 ip6-allrouters
1530ff02::3 ip6-allhosts""")
1531996 hosts.close()
** Also affects: ubiquity
Importance: Undecided
Status: New
--
ipv6 /etc/hosts missing localhost hostname
https://bugs.launchpad.net/bugs/301430
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 306567] [NEW] package snort 2.7.0-19ubuntu1 failed to be uninstalled: subprocess pre-removal script returned error exit status 123
Public bug reported: Binary package hint: snort package snort 2.7.0-19ubuntu1 failed to be uninstalled: subprocess pre- removal script returned error exit status 123 This report was initiated by the crash-reporting process. I am adding the following information manually. Used Synaptic Package Manager to install snort and, after dependencies, 5 packages were selected. After install, I ran snort a couple of times (it didn't seem to start, gave me the message "you've got to tell me to do something" (both without sudo and with, and I don't know what I'm doing so my command line arguments were probably incomplete). After looking over the options, I decided it probably wasn't what I was looking for and I selected the 5 packages for removal (not Complete Removal). Today's dpkg.log 2008-12-09 07:28:22 startup archives unpack 2008-12-09 07:28:35 install libprelude2 0.9.17.2-1ubuntu1 2008-12-09 07:28:35 status half-installed libprelude2 0.9.17.2-1ubuntu1 2008-12-09 07:28:35 status triggers-pending man-db 2.5.2-2 2008-12-09 07:28:36 status half-installed libprelude2 0.9.17.2-1ubuntu1 2008-12-09 07:28:36 status unpacked libprelude2 0.9.17.2-1ubuntu1 2008-12-09 07:28:36 status unpacked libprelude2 0.9.17.2-1ubuntu1 2008-12-09 07:28:36 install snort-common-libraries 2.7.0-19ubuntu1 2008-12-09 07:28:36 status half-installed snort-common-libraries 2.7.0-19ubuntu1 2008-12-09 07:28:36 status unpacked snort-common-libraries 2.7.0-19ubuntu1 2008-12-09 07:28:36 status unpacked snort-common-libraries 2.7.0-19ubuntu1 2008-12-09 07:28:36 install snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:36 status half-installed snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:36 status unpacked snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:36 status unpacked snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:36 install snort-common 2.7.0-19ubuntu1 2008-12-09 07:28:36 status half-installed snort-common 2.7.0-19ubuntu1 2008-12-09 07:28:36 status half-installed snort-common 2.7.0-19ubuntu1 2008-12-09 07:28:36 status unpacked snort-common 2.7.0-19ubuntu1 2008-12-09 07:28:36 status unpacked snort-common 2.7.0-19ubuntu1 2008-12-09 07:28:36 install snort 2.7.0-19ubuntu1 2008-12-09 07:28:36 status half-installed snort 2.7.0-19ubuntu1 2008-12-09 07:28:37 status half-installed snort 2.7.0-19ubuntu1 2008-12-09 07:28:37 status unpacked snort 2.7.0-19ubuntu1 2008-12-09 07:28:37 status unpacked snort 2.7.0-19ubuntu1 2008-12-09 07:28:37 install oinkmaster 2.0-2 2008-12-09 07:28:37 status half-installed oinkmaster 2.0-2 2008-12-09 07:28:37 status half-installed oinkmaster 2.0-2 2008-12-09 07:28:37 status unpacked oinkmaster 2.0-2 2008-12-09 07:28:37 status unpacked oinkmaster 2.0-2 2008-12-09 07:28:38 trigproc man-db 2.5.2-2 2.5.2-2 2008-12-09 07:28:38 status half-configured man-db 2.5.2-2 2008-12-09 07:28:39 status installed man-db 2.5.2-2 2008-12-09 07:28:40 startup packages configure 2008-12-09 07:28:40 configure libprelude2 0.9.17.2-1ubuntu1 0.9.17.2-1ubuntu1 2008-12-09 07:28:40 status unpacked libprelude2 0.9.17.2-1ubuntu1 2008-12-09 07:28:40 status unpacked libprelude2 0.9.17.2-1ubuntu1 2008-12-09 07:28:40 status unpacked libprelude2 0.9.17.2-1ubuntu1 2008-12-09 07:28:40 status unpacked libprelude2 0.9.17.2-1ubuntu1 2008-12-09 07:28:40 status unpacked libprelude2 0.9.17.2-1ubuntu1 2008-12-09 07:28:40 status half-configured libprelude2 0.9.17.2-1ubuntu1 2008-12-09 07:28:40 status installed libprelude2 0.9.17.2-1ubuntu1 2008-12-09 07:28:40 status triggers-pending libc6 2.8~20080505-0ubuntu7 2008-12-09 07:28:40 configure snort-common-libraries 2.7.0-19ubuntu1 2.7.0-19ubuntu1 2008-12-09 07:28:40 status unpacked snort-common-libraries 2.7.0-19ubuntu1 2008-12-09 07:28:40 status half-configured snort-common-libraries 2.7.0-19ubuntu1 2008-12-09 07:28:40 status installed snort-common-libraries 2.7.0-19ubuntu1 2008-12-09 07:28:40 configure snort-rules-default 2.7.0-19ubuntu1 2.7.0-19ubuntu1 2008-12-09 07:28:40 status unpacked snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:40 status unpacked snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:40 status unpacked snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:40 status unpacked snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:40 status unpacked snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:40 status unpacked snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:40 status unpacked snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:40 status unpacked snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:40 status unpacked snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:40 status unpacked snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:40 status unpacked snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:40 status unpacked snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:40 status unpacked snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:40 status unpacked snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:40 status unpacked snort-rules
[Bug 306567] Re: package snort 2.7.0-19ubuntu1 failed to be uninstalled: subprocess pre-removal script returned error exit status 123
** Attachment added: "Screenshot - Synaptic Package Manager console window following error message" http://launchpadlibrarian.net/20323448/Screenshot-Changes%20applied.png ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/20323455/Dependencies.txt ** Attachment added: "DpkgTerminalLog.txt" http://launchpadlibrarian.net/20323459/DpkgTerminalLog.txt -- package snort 2.7.0-19ubuntu1 failed to be uninstalled: subprocess pre-removal script returned error exit status 123 https://bugs.launchpad.net/bugs/306567 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 306567] Re: package snort 2.7.0-19ubuntu1 failed to be uninstalled: subprocess pre-removal script returned error exit status 123
I am attaching a second "Screenshot - Synaptic Package Manager console
window following error message" which is the scrolled-down view. I also
notice that there seems to be some DpkgTerminalLog.txt info from a
previous session, but today's information also appears toward the bottom
of that log.
SEVERITY/PRIORITY SUGGESTION - Unless further investigations see deeper
impacts than are apparent to me, I suggest that this is not a critical-
priority bug as the exception appears to be detected, and when coupled
with Synaptic Package Manager, it is logically handled following rather
intuitive steps (simply try again). However, it is also not "Low" as
the error messages are neither user-friendly ("Error 123") and appear
"scary" (big-red "Stop" indicator, Crash Detector appears in Gnome).
HTH & good luck!
** Attachment added: "Screenshot - Synaptic Package Manager console window
following error message -- scrolled down"
http://launchpadlibrarian.net/20323674/synaptic-console2.png
--
package snort 2.7.0-19ubuntu1 failed to be uninstalled: subprocess pre-removal
script returned error exit status 123
https://bugs.launchpad.net/bugs/306567
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 301430] Re: ipv6 /etc/hosts missing localhost hostname
Proposed change for ubiquity/scripts/install.py -- I am not on the dev
team so someone needs to review/sponsor this change. This would solve
the issue for future new installs. This does not solve the issue for
the currently installed base.
=== modified file 'scripts/install.py'
--- scripts/install.py 2008-10-30 17:34:58 +
+++ scripts/install.py 2008-12-09 16:58:04 +
@@ -1522,7 +1522,7 @@
print >>hosts, textwrap.dedent("""\
# The following lines are desirable for IPv6 capable hosts
-::1 ip6-localhost ip6-loopback
+::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
--
ipv6 /etc/hosts missing localhost hostname
https://bugs.launchpad.net/bugs/301430
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 288863] Re: Intrepid Ibex hangs when shutting down or restarting...
*** This bug is a duplicate of bug 274995 *** https://bugs.launchpad.net/bugs/274995 ** This bug has been marked a duplicate of bug 274995 MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up -- Intrepid Ibex hangs when shutting down or restarting... https://bugs.launchpad.net/bugs/288863 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up
Just a couple of notes on this. 1. For those with working ALSA sounds, but ALSA hangs on shutdowns lasting about 2.5 minutes, I believe our bug fix is mentioned http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.27.5 -- released November 7th. (I don't know how soon we will see it through normal channels -- can anyone advise?) commit a858c06703057cfdd142184e536c3ba36c45000e Author: Takashi Iwai <[EMAIL PROTECTED]> Date: Thu Oct 30 19:10:15 2008 + ALSA: hda - Add reboot notifier commit 0cbf00980f0fc4cc064a15ab3dfce19b5fae9130 upstream The current snd-hda-intel driver seems blocking the power-off on some devices like eeepc. Although this is likely a BIOS problem, we can add a workaround by disabling IRQ lines before power-off operation. This patch adds the reboot notifier to achieve it. The detailed problem description is found in bug#11889: http://bugme.linux-foundation.org/show_bug.cgi?id=11889 Tested-by: Luiz Fernando N. Capitulino <[EMAIL PROTECTED]> Signed-off-by: Takashi Iwai <[EMAIL PROTECTED]> Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]> 2. It's possible that this bug report is a duplicate of bug#126140. I'm not sure. That would make this a very old bug. That reporter noted that doing an rmmod of snd_hda_intel prior to shutdown avoided the hang. A similar solution posted at http://bugzilla.kernel.org/show_bug.cgi?id=7195#c3 (status NEW for over 2 years) describes putting similar entries in a shutdown script. Another commenter at https://bugs.launchpad.net/ubuntu/+source/linux- source-2.6.22/+bug/126140/comments/38 says that using aggressive power saving mentioned http://www.thinkwiki.org/wiki/How_to_enable_AC97_power_saving#HDA_audio_subsystem softens the problem. More recently, many are reporting, especially on ubuntuforum, that doing an ifdown on their active network avoids this ALSA hang on shutdown -- https://bugs.launchpad.net/ubuntu/+source/alsa- utils/+bug/274995/comments/25 mentions it as well. That the workarounds are different makes me wonder whether these actually are duplicates. Good luck, all! -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up https://bugs.launchpad.net/bugs/274995 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 286285] Re: kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x00000100
Jakub, What was the date/time when the system locked up? You'll want to check your logs matching up those times to help figure out why the kernel panicked. As to the printout you provided, those look like routine firewall logs. To get help with turning that off, see http://www.ubuntu.com/support/communitysupport for different ways to get help. If I had that logging problem and couldn't find the answer by searching, I might go to http://ubuntuforums.org/forumdisplay.php?f=336 and ask. -- kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x0100 https://bugs.launchpad.net/bugs/286285 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 288863] Re: Intrepid Ibex hangs when shutting down or restarting...
*** This bug is a duplicate of bug 274995 *** https://bugs.launchpad.net/bugs/274995 I concur that this is not a duplicate, FWIW. My read of this (288863) bug is that the failure mode is that the computer fails to shut down, the last thing displayed is "acpid exiting." The "hang" in 274995 isn't a hang but a long delay (about 2.5 minutes). The hang in the reports involving "acpid exiting" seems endless. -- Intrepid Ibex hangs when shutting down or restarting... https://bugs.launchpad.net/bugs/288863 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 295136] Re: amixer timeout when muting sound card
*** This bug is a duplicate of bug 274995 *** https://bugs.launchpad.net/bugs/274995 ** This bug has been marked a duplicate of bug 274995 MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up -- amixer timeout when muting sound card https://bugs.launchpad.net/bugs/295136 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up
This was tipped by aschuring in bug 295136 with Flagman's explanation -- here's another workaround: STEP A. sudo gedit /etc/hosts STEP B. Change the first line in the IPv6 section from # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback to # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback Wallah! No more hang at shutdown or reboot or when otherwise using amixer when no user is logged in. -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up https://bugs.launchpad.net/bugs/274995 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up
@aschuring, > can anyone confirm whether they have a "search ..." statement in > /etc/resolv.conf, > and whether removing that statement fixes the delays? I did not have a search statement there, but I can see where having one could lengthen the situation. -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up https://bugs.launchpad.net/bugs/274995 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up
Even though they have a lot in common, I'm convinced these issues have two different root causes, but I'm also hopeful that the change for bug 126140 will also avoid ours (bug 274995). Bug 126140 is about certain PCs that remain powered up at the end of their shutdown sequence. Anyone remember the Windows "It is now safe to turn off your computer" screen? That's essentially the behavior of bug 126140, minus the cheery-souding Microsoft comforting. Both that problem and ours ... can be avoided by rmmod -f snd_hda_intel (the sound driver) ... generally involved Alsa ... interrupted normal shutdown But ... 274995 is not actually a hang ... 126140 actually is a hang ... 274995 has a networking workaround ... 126140 seems to have a power-management workaround The "fix" for bug 126140 isn't r-e-a-l-l-y a fix because it doesn't address the root cause (which certainly could be a BIOS oddness), but it does avoid it. Before the hang, the code will now respond to a system reboot signal by releasing the interrupts. It was tested against the problem in 126140. If the net effect of releasing the interrupts is the same as "rmmod -f snd_hda_intel" then it should also avoid our problem as well. We should test it. If it does, we should also make sure that nothing else broke in the process -- for example, does the shutdown in /etc/init.d/alsa-tools still save and zero mixer settings like it was written to do? My suggestion is that we don't call these duplicate bugs until such testing is complete, even though we are hopeful that this one change avoids both issues. -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up https://bugs.launchpad.net/bugs/274995 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically due to internal alsa-plugins pulse check
@Jens -- whatever DNS server you are using while connected to VPN probably doesn't quickly return an answer for a query for "localhost," while your non-VPN DNS does. alsa-utils 1.0.17-0ubuntu3 should avoid it in all cases. Also, see below. @kungmidas -- when I change my DNS to some bogus address, I see this delay. When I use good DNS servers, the delay is gone. alsa-utils 1.0.17-0ubuntu3 should avoid it in all cases. Also, see below. @all, please see https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/274995/comments/273 -- if you were seeing a delay -- even if it is fixed now, you probably also have or had that separate network configuration bug 301430 that allows DNS queries for localhost -- however generated -- to escape your local machine and network. -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically due to internal alsa-plugins pulse check https://bugs.launchpad.net/bugs/274995 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 286285] Re: kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x00000100
+ ***Important summary for those experiencing this bug*** + Kernel versions where this bug is fixed: + 1) 2.6.27-10 from intrepid-proposed CORRECT + Kernel versions where this bug is NOT fixed (if you are running one of these, please upgrade to known working kernel): + 1) 2.6.27-7 from intrepid + 2) 2.6.27-9 from intrepid-updates and intrepid-security CORRECT + If you are experiencing this bug, please remove the linux-backports- + modules packages too, as they don't contain a fix I have read that here, but I can't vouch for it as I'm not running backports. -- kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x0100 https://bugs.launchpad.net/bugs/286285 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up
Thanks for agreeing with me, aschuring. :-) However, the change for 126140 certainly won't benefit you so my previous advice of "wait and hope" no longer makes sense for some. This is a cascade of bugs and behaviors. In bug 295136, FlagMan said, "If pulseaudio is the default sound sink and you are NOT logged into X, amixer will search the pulseaudio server but there is none running on the local machine. Therefore, the network will be searched for a pulseaudio server. Most likely there is none on the local network either, and network timeouts are set to high values, so this may take some time and is the symptom we are seeing." MY THEORY (and I'm not too strong on my capture of linux sound, so beware): I think the root cause is in that first sentence -- the user is no longer logged into X, the pulseaudio daemon has been terminated when the user session ended, but pulseaudio is still sought by alsa tools. So amixer, searches fruitlessly for the daemon and it has to wait for a network timeout every time its called, and it is called numerous times in /etc/init.d/alsa-tools as the script zeros and mutes channels. (After the user logs out of gnome, I have also noticed a delay between the time that "gdm" appears ready for input and /usr/share/sounds/question.wav plays, which is played by gdmplay which is simply a script that calls aplay, another alsa tool trying to do something after pulseaudio has ended.) Finally, gdm.conf has this text, ---Quote--- # Program used to play sounds. Should not require any 'daemon' or anything # like that as it will be run when no one is logged in yet. SoundProgram=/usr/lib/gdmplay" ---EndQuote--- This points the finger at alsa-tools OR, and I think this more likely, the ubuntu user-session implementation of pulseaudio, and here's where my lack of knowledge about these ends my usefulness -- I don't know the implications of default sinks and whether the closing gnome session can and ought to switch audio defaults back and forth. It should be noted that pulse's xsmp module is installed to load upon login, and never does. That might have everything to do with this. It is probably not a bug that the alsa tools looks for pulseaudio using network calls. This is not only very common, it works fine when the network isn't searching DNS for the localhost hostname. Even though many workarounds involve killing the network, or nfs, or uninstalling pulseaudio -- these are avoiding the symptom. There might be a bug related to whether alsa tools seeks the network correctly, and how to do that in IPv4/IPv6 LAN has been the topic of much disagreement (see below). SECONDARY ISSUES: It was found that listing localhost to :::1 in the IPv6 section of /etc/hosts avoided the long delay mentioned in this report. Some distributions, including Debian, include (or have included) that entry in /etc/hosts by default while others have not (including Ubuntu, apparently, starting with Hardy (bug 211537). However, and this is important no matter which way this goes, several VERY POPULAR network applications that have bug reports indicating that they fail or misbehave when localhost is listed twice in /etc/hosts (these reports are older and are probably fixed). How to handle localhost in lookups as everyone transitions to IPv6 has been the source of questions http://lists.debian.org/debian-ipv6/2008/07/msg0.html and heated (and infamous) discussions http://sources.redhat.com/bugzilla/show_bug.cgi?id=4980 and contradiction http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=427067 (seems to indicate that localhost ought to be listed in the IPv6 section, even though it means that localhost is listed twice). I have researched this question for days and can't find which answer is right. However, as a result of this bug, and as observed by aschuring, my system ends up sending DNS lookups for localhost to the WAN. However, even though localhost lookups for IPv6 might be a bug, fixing it only hides the fact that pulseaudio is not running when the alsa tools need to find it (the root cause bug). It seems like when the user logs out and the pulseaudio daemon is not running, alsa tools should stop trying to find it. -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up https://bugs.launchpad.net/bugs/274995 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 288863] Re: Intrepid Ibex hangs when shutting down or restarting...
** This bug is no longer a duplicate of bug 274995 MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up -- Intrepid Ibex hangs when shutting down or restarting... https://bugs.launchpad.net/bugs/288863 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 295262] Re: acpi seems to delay shutdown
*** This bug is a duplicate of bug 274995 *** https://bugs.launchpad.net/bugs/274995 ** This bug has been marked a duplicate of bug 274995 MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up -- acpi seems to delay shutdown https://bugs.launchpad.net/bugs/295262 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 288863] Re: Intrepid Ibex hangs when shutting down or restarting...
*** This bug is a duplicate of bug 274995 *** https://bugs.launchpad.net/bugs/274995 This bug 288863 as originally reported is probably a duplicate of bug 274995. However, the symptom of having to shut down using the power button even after waiting 5+ more minutes is NOT a symptom of 274995. (The hang in 274995 is usually 2-3 minutes). @Brion,Kill0u since the original of this bug is a duplicate, I'm thinking your comments (involving the never-ending hang at acpid) is different. You should search for or open a specific report. You may want to consider Bug 126140, which is a failure to shut-down, (but it is specific to Intel HDA sound). But if that's not your bug, then please open one. ** This bug has been marked a duplicate of bug 274995 MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up -- Intrepid Ibex hangs when shutting down or restarting... https://bugs.launchpad.net/bugs/288863 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up
Please reevaluate -- see comment 226 ** Changed in: pulseaudio (Ubuntu) Status: Invalid => New -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up https://bugs.launchpad.net/bugs/274995 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up
Please reevaluate -- see comment 226 ** Changed in: alsa-utils (Ubuntu) Status: Invalid => New -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up https://bugs.launchpad.net/bugs/274995 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up
I am going to try and change the "invalid" status for pulseaudio and alsa-tools. alsa-tools, pulseaudio -- please re-evaluate. The primary issue seems to be that the alsa-tools are trying to find a pulseaudio daemon that is no longer running after the user has chosen to shutdown or reboot. It seems to me that amixer or aplay ought not try to access a pulseaudio process that doesn't exist. (The hang which is avoided by shutting down the network helps illuminate the issue, but it isn't the cause.) -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up https://bugs.launchpad.net/bugs/274995 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up
@Dove, It's probable that everyone who uses pulseaudio as installed by Intrepid will experience this bug. The question is whether or not they'll experience the long hang that helps us notice it -- and that is determined by the networking configuration. It appears to me that users who once had an IPV4-only system and upgraded will avoid the wait for timeout caused by the bug (the alsa- tools still look for the pulseaudio server, but fails to find it much faster). This is because the upgrade script notices the ipv6 section is missing in /etc/hosts and installs one including the "localhost" name in the ::1 line. Users who manually add the "localhost" hostname to the ::1 line in /etc/hosts also avoid this wait. My guess is that users who disable IPV6 after installing will also avoid this wait for timeout. Robb Topolski -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up https://bugs.launchpad.net/bugs/274995 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up
Hi Dov, I'm glad you posted. It seems I've made the bug Gods angry -- it won't show itself on my system tonight, and I can't figure out why. I hate when that happens. > I tried killing pulseaudio while logged in to an X session, and it still hung while shutting down. Right. Killing pulseaudio while logged in should show the same problem when the gnome user hits reboot or shutdown. The pulseaudio daemon gets killed then the alsa utility tries to contact it. That is the crux of the issue -- should alsa be trying to contact the pulseaudio server after its killed? Or, should something in the sound configuration revert before pulseaudio gets killed so that the alsa tools don't try to contact the pulseaudio server? I don't understand the architecture well enough to know for certain. The freeze (~ 15 seconds each for 7-10 times that amixer is called to zero and mute the mixer in /etc/init.d/alsa-tools stop) occurs as amixer waits for a DNS query to time out. If the pulseaudio server is alive, the DNS query doesn't happen. If the pulseaudio server is unexpectedly gone, then amixer searches localhost for it. Since it's not found on ipv4 and ipv6 doesn't have localhost in /etc/hosts, the query goes to the WAN and things pause for 15 seconds while amixer waits for a reply. -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up https://bugs.launchpad.net/bugs/274995 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up
I'll buy the beer if this is a BIOS bug. Bug 295136 (aschuring) is the most succinct test case I've seen on this. That bug is a duplicate but shows what is going on. It should not be ignored. Key observations: ---Quote--- After dist-upgrading to intrepid, Ubuntu appears to hang when shutting down. I have traced this down to the ALSA shutdown script taking more than a minute (!) to save sound card state. More specifically: [EMAIL PROTECTED]:~$ time amixer -c0 -q set Mic 0% mute real 0m8.061s user 0m0.003s sys 0m0.012s This is reproducable only in single-user mode. When I run the amixer command when logged in into X (I can even run the command from a console, as long as X is running), the same command takes only a few milliseconds as it should. I will attach an strace log from above call. Of interest is the following line: 4.013297 ioctl(5, FIONREAD, [37]) = 0 which occurs twice in the script. It seems to be expecting data from a network socket, but I can't figure out why. ---endQuote--- - commenting out everything in /usr/share/alsa/pulse.conf: amixer responds fast (The description of this file is, "PulseAudio alsa plugin configuration file to set the pulseaudio plugin as default output for applications using alsa when pulseaudio is running." However, pulseaudio is not running, wasn't running, so why does Aschuring's commenting out of lines change anything? /usr/share/alsa/pulse.conf calls its config from /usr/share/alsa/pulse-alsa.conf which appears to set pulse as the default sound device. Aschuring's tests at the single-user root prompt create a similar situation to what all these users are reporting where when the user session is ended, X and pulse are no longer running, and the alsa configuration is to use pulse.) - removing dns in /etc/nsswitch.conf or adding localhost to ipv6 ::1 in /etc/hosts amixer responds fast (This addresses the networking delay, but not whether alsa should be looking for pulse at all when the server is not running. Removing dns from nsswitch.conf is not desirable.) It's a shame that bug 295136 isn't the primary bug, because the best information is there. I don't know if launchpad etiquette allows that to happen -- but developers investigating this bug ought to be paying attention. -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up https://bugs.launchpad.net/bugs/274995 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up
@Luke, My quick test -- There was the same hang with your new file as written (without the variable being exported). THERE WAS NO HANG with export PULSE_INTERNAL=0 but there was a hang if the variable was not exported. -- Robb PS: (reproducing tip for developers and experienced users -- do not try this if you don't understand it -- If your nameserver handles queries correctly, then you may not see the delay users are seeing that is caused by the failed DNS query for localhost. Edit /etc/resolv.conf and change your working nameserver line to one with an unoccupied IP before shutting down and rebooting, for example 192.168.0.177, and the DNS query being generated will go to a address that will timeout instead of to your nameserver. I just figured this out tonight and perhaps that is why this bug is so hit and miss -- some users have nameservers that are answering NXDOMAIN (and thus no delay) and some users have nameservers that aren't answering the query.) -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up https://bugs.launchpad.net/bugs/274995 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up
@Daniel Chen, Hi Daniel, you're over my head a little bit. Can you tell me in easier terms what you'd like me to try and I'll be happy to try it. @Any, What does the PULSE_INTERNAL variable do? Was that a potential fix or just a diagnostic test? -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up https://bugs.launchpad.net/bugs/274995 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 294160] Re: ALSA hangs on shutdown - Intrepid Ibex on Dell Inspiron 1525
*** This bug is a duplicate of bug 274995 *** https://bugs.launchpad.net/bugs/274995 @bugmenot, I suggest a new bug report. Bug 274995 is narrowing to an issue commonly seen during shutdown where 2-3 minute delays also sometimes occur. The crackling quality is usually not a symptom. Any fix for 274995 is unlikely to fix the crackling issue. Also, 274995 is a huge mess and introducing one more side issue to it would likely cause more harm than good. You can certainly mention in a new bug report that you also suffered from the effects of 274995, but if you do, I suggest that you also mention that it is a different issue near resolution and the crackling sound is not fixed by it. Thanks! Robb Topolski -- ALSA hangs on shutdown - Intrepid Ibex on Dell Inspiron 1525 https://bugs.launchpad.net/bugs/294160 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 302237] [NEW] undocumented logaudit facility, how to log unknown facilities
Public bug reported: Binary package hint: sysklogd Ubuntu 8.10 sysklogd 1.5-2ubuntu6 >From syslog.conf MAN page Quote The facility is one of the following keywords: auth, authpriv, cron, daemon, ftp, kern, lpr, mail, mark, news, security (same as auth), sys‐ log, user, uucp and local0 through local7. endQuote My silly D-Link DIR-655 router puts its syslog on the Log Audit facility 13 (which is 104 in the 32-bit PRI). It took me quite a bit of reverse engineering to figure that out. I'll make the following proposal based on that finding, but it would be even better if someone could find a copy of syslog.h (mentioned in the MAN page) and extract all of the supported facility names. (I did review the source and couldn't find it myself, it's probably in some global header or config file for making inet-tools.) Proposed Change The facility is one of the following keywords: auth, authpriv, cron, daemon, ftp, kern, logaudit, lpr, mail, mark, news, security (same as auth), sys‐ log, user, uucp and local0 through local7. end I also found something else in the meantime, close and related and easy to fix... Quote ... Both parts are case insensitive and can also be specified as decimal numbers corresponding to the definitions in . endQuote This is probably incorrect, as I was able to find an old Berkeley syslog.h and it turns out that you have to multiply the decimal number by 8. So logaudit (13) becomes 104 and both logaudit.info and 104.info works correctly in syslog.conf while 13.info does not. Here is my suggestion Quote ... Both parts are case insensitive and can also be specified as decimal numbers corresponding to the numerical code being used in the PRI part of the RFC 3164 message from the logging device. (Note: the facility's numerical code is multiplied by 8 before being used in the PRI part, and syslog.conf requires this too. For example, network news facilities have a facility identifier of 7, therefore news.local and 56.local are equivalent in syslog.conf.) endQuote Thanks Robb Topolski ** Affects: sysklogd (Ubuntu) Importance: Undecided Status: New -- undocumented logaudit facility, how to log unknown facilities https://bugs.launchpad.net/bugs/302237 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 291467] Re: Delayed Intrepid Login
ATM, I'm able to avoid the delay by going to System - Preferences - Sessions and clearing the checkbox next to Gnome Login Sound. -- Delayed Intrepid Login https://bugs.launchpad.net/bugs/291467 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 291467] Re: Delayed Intrepid Login
Accepted -- it must be something else that I did. Sorry for the false alarm. -- Delayed Intrepid Login https://bugs.launchpad.net/bugs/291467 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 286285] Re: kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x00000100
@aldebx re https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/103 What is your failure symptom after the suspend or hibernation? -- kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x0100 https://bugs.launchpad.net/bugs/286285 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up
Okay, that helps explain why the rc.0 one alone did nothing for me -- I'm usually rebooting! ;-/ So the workaround is to do both -- sudo ln -s /etc/init.d/NetworkManager /etc/rc0.d/K40NetworkManager sudo ln -s /etc/init.d/NetworkManager /etc/rc6.d/K40NetworkManager Great job! That's a temporary work-around, and work-arounds are very good -- but when a request to test a patch or a fix comes out, you'll want to return to the previous state and delete those symlinks so you can cleanly test. sudo rm /etc/init.d/NetworkManager /etc/rc0.d/K40NetworkManager sudo rm /etc/init.d/NetworkManager /etc/rc6.d/K40NetworkManager For those who'd rather not edit, another work-around is to disconnect network cables, disable networking in nm-applet, or hit the Wi-Fi kill switch either before or during shutdown. If done before choosing shut- down or reboot, the hang is avoided. If done during the hang, then the remaining shutdown hang at the alsa step is shortened from over 2 minutes to under 15 seconds. @Daniel T. Chen -- are you still asking for help or information on this? -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up https://bugs.launchpad.net/bugs/274995 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up
IMPORTANT CORRECTION -- please ignore my prior message, it contained a major mistake -- this is the corrected version Okay, that helps explain why the rc.0 one alone did nothing for me -- I'm usually rebooting! ;-/ So the workaround is to do both -- sudo ln -s /etc/init.d/NetworkManager /etc/rc0.d/K40NetworkManager sudo ln -s /etc/init.d/NetworkManager /etc/rc6.d/K40NetworkManager Great job! That's a temporary work-around, and work-arounds are very good -- but when a request to test a patch or a fix comes out, you'll want to return to the previous state and delete those symlinks so you can cleanly test. sudo rm /etc/rc0.d/K40NetworkManager sudo rm /etc/rc6.d/K40NetworkManager For those who'd rather not edit, another work-around is to disconnect network cables, disable networking in nm-applet, or hit the Wi-Fi kill switch either before or during shutdown. If done before choosing shut- down or reboot, the hang is avoided. If done during the hang, then the remaining shutdown hang at the alsa step is shortened from over 2 minutes to under 15 seconds. @Daniel T. Chen -- are you still asking for help or information on this? -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up https://bugs.launchpad.net/bugs/274995 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 286285] Re: kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x00000100
Looks like the -9 security update fixed a number of concerning-looking issues. Is that why our fix wasn't in it? I tried reapplying the patch from comment 52 into the (-9 directories instead of -7) and wound up with a system with no wireless devices. (Fortunately that process left me with .ko~ backup files I could restore. Nice!) Okay, (whew!) 1. so what do I do now to prevent kernel panics from burning up the computer or filling the disk? 2. when can I expect to trust system updates again? Thanks, Robb -- kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x0100 https://bugs.launchpad.net/bugs/286285 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 276990] Re: iwlagn causes kernel panic on 802.11n wifi
They're ba-ack. With a patch at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/52 and later a 2.6.27-8 kernel update in backports (mentioned later in bug 286285), I was avoiding kernel panics on 802.11n networks. Now with 2.6.27-9, the panics are back. I am able to work around them by turning off the 802.11n capabilities of my router. -- iwlagn causes kernel panic on 802.11n wifi https://bugs.launchpad.net/bugs/276990 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 301430] Re: ipv6 /etc/hosts missing localhost hostname
Hi Steve, I'm glad you identified the right package. It was difficult for me to figure out what actually initially creates /etc/hosts! > What was in your /etc/hosts, if not this? Exactly what you posted, except for the localhost entry in the ::1 line. This condition is common across two fresh installs here at home. 127.0.0.1 localhost 127.0.1.1 topol015 # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts Also, hopefully helpful ... - My installs were from the Live CD Gnome desktop Live User environment (I did not install from the CD without booting up the Gnome session first). - My installs were on a SOHO LAN with an IPv4 router that was also the DNS server and was not responding to IPv6 DNS queries (in case netcfg or some other tool makes choices based on IPv6 reachability) However, - Dovel mentioned in https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/274995/comments/230 that neither his upgraded installation contained the correct /etc/hosts line, nor did his installation direct from CD. (His upgraded installation may have had a different audio configuration or some other factor, it did not experience the delay in 274995.) (If I understand it correctly,) The bug in 274995 (a condition with a delay noticed by a large number of users) involves attempts to reach a user-session Pulseaudio daemon during /etc/init.d/alsa-tools stop. Of course, the daemon had shut down with the end of the user session, but the alsa-tools seemed oblivious to that and still treated them as part of the default audio system. To experience the delay, there had to be no IPv6 localhost in /etc/hosts AND ALSO no timely response to the resulting DNS queries for localhost. This is an indicator that the number of users without localhost for ipv6 in /etc/hosts may be quite high. -- ipv6 /etc/hosts missing localhost hostname https://bugs.launchpad.net/bugs/301430 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically due to internal alsa-plugins pulse check
All, If you are or were experiencing this delay, there is a related bug report -- bug 301430 -- concerning the omission of localhost in the ipv6 part of /etc/hosts. While bug 274995 is fixed by the update to alsa- tools, the delay uncovered by bug 274995 was only experienced by those of us who had bug 301430 as well. Bug 301430 is marked as "incomplete" and will expire unfixed without confirmation that it affects others. I suspect that everyone who noticed a delay during shutdown owing to 274995 also has an IPv6 misconfiguration in the /etc/hosts file, even if they're not using IPv6 and even if the delay is now fixed. Please help out, check, and advise. WHAT YOU SHOULD DO: 1. Even if the latest alsa-tools update fixed your problem, please check your /etc/hosts and verify whether or not it was set up correctly. A CORRECTLY configured file originally had (or has) this line (the whitespace-separated word localhost is included among the hostnames in the ipv6 section of /etc/hosts): ::1 localhost ip6-localhost ip6-loopback An INCORRECTLY configured file had or has this line (the whitespace-separated word localhost is NOT included among the hostnames): ::1 ip6-localhost ip6-loopback 2. If your system was or is INCORRECTLY configured, please visit bug 301430 and indicate so via a comment. The /etc/hosts file is created as part of the network installation and configuration. It would be interesting to know whether your install was an upgrade or fresh install. Look for any other developer questions you might be able to answer or add your other relevant insights or observations. Please consider subscribing to the bug by clicking "E-mail me about changes to this bug report) and indicating that the bug affects you (see the links toward the top of the report). Thanks for your help and congrats on getting bug 274995 fixed! Robb Topolski -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically due to internal alsa-plugins pulse check https://bugs.launchpad.net/bugs/274995 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 301430] Re: ipv6 /etc/hosts missing localhost hostname
Laurent, I replied https://bugs.launchpad.net/ubuntu/+source/alsa- utils/+bug/274995/comments/275 on the alsa-utils issue. -- ipv6 /etc/hosts missing localhost hostname https://bugs.launchpad.net/bugs/301430 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically due to internal alsa-plugins pulse check
Hi Laurent, That's odd that the 274995 proposed fix doesn't solve the issue. Do you have more than 2 machines? Did you follow the steps mentioned in https://wiki.ubuntu.com/Testing/EnableProposed to upgrade? Did alsa- utils update to 1.0.17-0ubuntu3 (the proposed fix) or are you using alsa-utils 1.0.17-0ubuntu2 (the previous version)? In /etc/init.d/alsa- utils, do you find the following line?: export PULSE_INTERNAL=0 (Adding localhost to the ipv6 line doesn't actually fix the alsa-utils problem, it just masks it. The omission mentioned in bug 301430 along with the bug in 274995 causes enough delay to uncover the alsa-utils issue.) -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically due to internal alsa-plugins pulse check https://bugs.launchpad.net/bugs/274995 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 286285] Re: kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x00000100
Tom, if I use apt-get to remove backports and then try the patch, is that a clean test? -- kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x0100 https://bugs.launchpad.net/bugs/286285 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 286285] Re: kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x00000100
I removed backports, rebooted, then installed the patch per Tom's instructions, rebooted, and now I've rebooted several times. I cannot reproduce the original problem. However, I can't shut down without hitting the wifi killswitch. 18:45 Shut down from Gnome 18:46 Hanging... hanging... (and will continue to hang) 18:47 Flip the Wi-Fi switch 18:48 Shutdown completes /var/log/kern.log Nov 3 18:42:30 topol015 kernel: [ 158.992820] type=1503 audit(1225766550.341:14): operation="socket_create" family="x25" sock_type="seqpacket" protocol=0 pid=6230 profile="/usr/sbin/cupsd" Nov 3 18:45:44 topol015 kernel: [ 352.808577] apm: BIOS not found. Nov 3 18:45:46 topol015 kernel: [ 355.263861] ip6_tables: (C) 2000-2006 Netfilter Core Team Nov 3 18:47:15 topol015 kernel: [ 444.087373] iwlagn: Radio Frequency Kill Switch is On: Nov 3 18:47:15 topol015 kernel: [ 444.087378] Kill switch must be turned off for wireless networking to work. Nov 3 18:47:20 topol015 kernel: [ 449.308039] wlan0: No ProbeResp from current AP 00:1e:58:f3:26:e5 - assume out of range Nov 3 18:47:20 topol015 kernel: [ 449.310549] iwlagn: Error sending REPLY_ADD_STA: enqueue_hcmd failed: -5 Nov 3 18:47:20 topol015 kernel: [ 449.310727] mac80211-phy0: failed to remove key (0, 00:1e:58:f3:26:e5) from hardware (-5) Nov 3 18:47:20 topol015 kernel: [ 449.317281] iwlagn: Error sending REPLY_ADD_STA: enqueue_hcmd failed: -5 Nov 3 18:47:20 topol015 kernel: [ 449.317438] mac80211-phy0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-5) Nov 3 18:48:31 topol015 kernel: Inspecting /boot/System.map-2.6.27-7-generic Nov 3 18:48:31 topol015 kernel: Cannot find map file. Nov 3 18:48:31 topol015 kernel: Loaded 70488 symbols from 101 modules. Nov 3 18:48:31 topol015 kernel: [0.00] Initializing cgroup subsys cpuset Nov 3 18:48:31 topol015 kernel: [0.00] Initializing cgroup subsys cpu Nov 3 18:48:31 topol015 kernel: [0.00] Linux version 2.6.27-7-generic ([EMAIL PROTECTED]) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu11) ) #1 SMP Thu Oct 30 04:18:38 UTC 2008 (Ubuntu 2.6.27-7.15-generic) /var/log/messages Nov 3 18:42:30 topol015 kernel: [ 158.992815] type=1503 audit(1225766550.341:13): operation="socket_create" family="ash" sock_type="dgram" protocol=0 pid=6230 profile="/usr/sbin/cupsd" Nov 3 18:42:30 topol015 kernel: [ 158.992820] type=1503 audit(1225766550.341:14): operation="socket_create" family="x25" sock_type="seqpacket" protocol=0 pid=6230 profile="/usr/sbin/cupsd" Nov 3 18:45:40 topol015 bonobo-activation-server (robb-6323): could not associate with desktop session: Failed to connect to socket /tmp/dbus-8pCCuzghiS: Connection refused Nov 3 18:45:44 topol015 kernel: [ 352.808577] apm: BIOS not found. Nov 3 18:45:46 topol015 kernel: [ 355.263861] ip6_tables: (C) 2000-2006 Netfilter Core Team Nov 3 18:47:15 topol015 kernel: [ 444.087373] iwlagn: Radio Frequency Kill Switch is On: Nov 3 18:47:15 topol015 kernel: [ 444.087378] Kill switch must be turned off for wireless networking to work. Nov 3 18:47:38 topol015 exiting on signal 15 Nov 3 18:48:31 topol015 syslogd 1.5.0#2ubuntu6: restart. Nov 3 18:48:31 topol015 kernel: Inspecting /boot/System.map-2.6.27-7-generic Nov 3 18:48:31 topol015 kernel: Cannot find map file. Nov 3 18:48:31 topol015 kernel: Loaded 70488 symbols from 101 modules. Nov 3 18:48:31 topol015 kernel: [0.00] Initializing cgroup subsys cpuset Nov 3 18:48:31 topol015 kernel: [0.00] Initializing cgroup subsys cpu Nov 3 18:48:31 topol015 kernel: [0.00] Linux version 2.6.27-7-generic ([EMAIL PROTECTED]) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu11) ) #1 SMP Thu Oct 30 04:18:38 UTC 2008 (Ubuntu 2.6.27-7.15-generic) Nov 3 18:48:31 topol015 kernel: [0.00] BIOS-provided physical RAM map: /var/log/syslog Nov 3 18:40:19 topol015 kernel: [ 27.695965] Registered led device: iwl-phy0:radio Nov 3 18:40:19 topol015 kernel: [ 27.696243] Registered led device: iwl-phy0:assoc Nov 3 18:40:19 topol015 kernel: [ 27.697753] Registered led device: iwl-phy0:RX Nov 3 18:40:19 topol015 kernel: [ 27.699182] Registered led device: iwl-phy0:TX Nov 3 18:40:19 topol015 kernel: [ 27.708662] ADDRCONF(NETDEV_UP): wlan0: link is not ready Nov 3 18:40:19 topol015 NetworkManager: (wlan0): preparing device. Nov 3 18:40:19 topol015 NetworkManager: (wlan0): deactivating device (reason: 2). Nov 3 18:40:19 topol015 NetworkManager: (eth0): carrier now ON (device state 2) Nov 3 18:40:19 topol015 NetworkManager: (eth0): device state change: 2 -> 3 Nov 3 18:40:19 topol015 NetworkManager: (eth0): carrier now OFF (device state 3) Nov 3 18:40:19 topol015 NetworkManager: (eth0): device state change: 3 -> 2 Nov 3 18:40:19 topol015 NetworkManager: (eth0): deactivating de
[Bug 286285] Re: kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x00000100
Thank you Antonio. That helps assure me that the results I'm seeing apply to the patch. As also reported above, I now can't shutdown cleanly without hitting the wifi switch. I'm not certain whether this is a new behavior or heightened awareness of an existing issue. for clarity's sake, 11 hours ago, I removed... linux-backports-modules-intrepid linux-backports-modules-intrepid-generic linux-backports-modules-2.6.27-7-generic ...and followed that with a reboot. Then I patched and rebooted again. Then I rebooted several times and haven't seen the "scheduling" bug. Currently synaptic shows no backports packages installed. $ ls -lc --full-time Desktop/bug286285 total 4020 -rw-r--r-- 1 robb robb 1057703 2008-11-03 18:31:30.0 -0800 iwl3945.ko -rw-r--r-- 1 robb robb 1076975 2008-11-03 18:31:30.0 -0800 iwlagn.ko -rw-r--r-- 1 robb robb 1964712 2008-11-03 18:31:30.0 -0800 iwlcore.ko $ ls -lc --full-time /lib/modules/2.6.27-7-generic/kernel/drivers/net/wireless/iwlwifi/ total 4396 -rw-r--r-- 1 root root 1057703 2008-11-03 18:31:35.0 -0800 iwl3945.ko -rw-r--r-- 1 root root 125004 2008-11-03 18:31:35.0 -0800 iwl3945.ko~ -rw-r--r-- 1 root root 1076975 2008-11-03 18:31:35.0 -0800 iwlagn.ko -rw-r--r-- 1 root root 129776 2008-11-03 18:31:35.0 -0800 iwlagn.ko~ -rw-r--r-- 1 root root 1964712 2008-11-03 18:31:35.0 -0800 iwlcore.ko -rw-r--r-- 1 root root 111220 2008-11-03 18:31:35.0 -0800 iwlcore.ko~ $ modprobe --list | grep "iwlwifi" /lib/modules/2.6.27-7-generic/kernel/drivers/net/wireless/iwlwifi/iwlagn.ko /lib/modules/2.6.27-7-generic/kernel/drivers/net/wireless/iwlwifi/iwl3945.ko /lib/modules/2.6.27-7-generic/kernel/drivers/net/wireless/iwlwifi/iwlcore.ko $ lsmod | grep "iwl" iwlagn 99844 0 iwlcore91972 1 iwlagn rfkill 17176 2 iwlcore led_class 12164 1 iwlcore mac80211 216820 2 iwlagn,iwlcore cfg80211 32392 3 iwlagn,iwlcore,mac80211 HTH & thanks everyone! -- kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x0100 https://bugs.launchpad.net/bugs/286285 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 286285] Re: kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x00000100
Tom, I got the kern.log entry mentioned at https://bugs.launchpad.net/ubuntu/intrepid/+source/linux/+bug/276990/comments/92 which is the patched (comment 85) behavior of that bug. The news is that I didn't use that patch, I used the patch from comment 52 in this bug. The patch at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/52 has eased both problems, the scheduling report churning into kern.log and turns the wrong command queue hang into a log event. The entry that I received is Nov 4 12:13:33 topol015 kernel: [20559.634756] [ cut here ] Nov 4 12:13:33 topol015 kernel: [20559.634774] WARNING: at drivers/net/wireless/iwlwifi/iwl-tx.c:1196 iwl_tx_cmd_complete+0x2c9/0x2d0 [iwlcore]() Nov 4 12:13:33 topol015 kernel: [20559.634781] wrong command queue 63, command id 0x0 Nov 4 12:13:33 topol015 kernel: [20559.634786] Modules linked in: aes_i586 aes_generic af_packet binfmt_misc rfcomm bridge stp bnep sco l2cap bluetooth ipv6 ppdev acpi_cpufreq cpufreq_ondemand cpufreq_userspace cpufreq_conservative cpufreq_stats freq_table cpufreq_powersave container sbs pci_slot sbshc iptable_filter ip_tables x_tables coretemp sbp2 parport_pc lp parport joydev snd_hda_intel arc4 ecb crypto_blkcipher snd_pcm_oss snd_mixer_oss snd_pcm iwlagn snd_seq_dummy iwlcore snd_seq_oss uvcvideo rfkill snd_seq_midi compat_ioctl32 led_class videodev snd_rawmidi psmouse mac80211 v4l1_compat snd_seq_midi_event serio_raw pcspkr evdev nvidia(P) snd_seq cfg80211 i2c_core snd_timer snd_seq_device sdhci_pci snd sdhci video output ricoh_mmc mmc_core battery wmi soundcore ac button iTCO_wdt iTCO_vendor_support intel_agp agpgart snd_page_alloc shpchp pci_hotplug ext3 jbd mbcache sr_mod cdrom ata_generic sd_mod crc_t10dif sg ata_piix ahci ohci1394 pata_acpi ieee1394 libata scsi_mod dock r8169 ehci_hcd uhci_hcd usbcore t Nov 4 12:13:33 topol015 kernel: ermal processor fan fbcon tileblit font bitblit softcursor fuse Nov 4 12:13:33 topol015 kernel: [20559.635009] Pid: 5617, comm: Xorg Tainted: P 2.6.27-7-generic #1 Nov 4 12:13:33 topol015 kernel: [20559.635016] [] warn_slowpath+0x65/0x90 Nov 4 12:13:33 topol015 kernel: [20559.635035] [] ? apparmor_socket_recvmsg+0x15/0x20 Nov 4 12:13:33 topol015 kernel: [20559.635048] [] ? __sock_recvmsg+0x66/0x80 Nov 4 12:13:33 topol015 kernel: [20559.635059] [] ? sock_aio_read+0xdc/0x120 Nov 4 12:13:33 topol015 kernel: [20559.635069] [] iwl_tx_cmd_complete+0x2c9/0x2d0 [iwlcore] Nov 4 12:13:33 topol015 kernel: [20559.635094] [] ? do_sync_read+0xd9/0x120 Nov 4 12:13:33 topol015 kernel: [20559.635106] [] iwl_rx_handle+0xd9/0x260 [iwlagn] Nov 4 12:13:33 topol015 kernel: [20559.635125] [] iwl4965_irq_tasklet+0x1ad/0x2f0 [iwlagn] Nov 4 12:13:33 topol015 kernel: [20559.635140] [] ? inotify_inode_queue_event+0xe/0xe0 Nov 4 12:13:33 topol015 kernel: [20559.635152] [] tasklet_action+0x78/0x100 Nov 4 12:13:33 topol015 kernel: [20559.635161] [] __do_softirq+0x92/0x120 Nov 4 12:13:33 topol015 kernel: [20559.635169] [] do_softirq+0x5d/0x60 Nov 4 12:13:33 topol015 kernel: [20559.635176] [] irq_exit+0x55/0x90 Nov 4 12:13:33 topol015 kernel: [20559.635184] [] do_IRQ+0x4a/0x80 Nov 4 12:13:33 topol015 kernel: [20559.635193] [] ? sys_clock_gettime+0x57/0xb0 Nov 4 12:13:33 topol015 kernel: [20559.635205] [] common_interrupt+0x23/0x30 Nov 4 12:13:33 topol015 kernel: [20559.635214] === Nov 4 12:13:33 topol015 kernel: [20559.635219] ---[ end trace 44f093d96ce74abe ]--- It happend 57.5 minutes after reassociation to a rebooted DIR-655 802.11n WPA/WPA2 router. -- kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x0100 https://bugs.launchpad.net/bugs/286285 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 276990] Re: iwlagn causes kernel panic on 802.11n wifi
Tom (comment 93), Please see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/63 for some info. --Robb -- iwlagn causes kernel panic on 802.11n wifi https://bugs.launchpad.net/bugs/276990 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 260646] Re: Help-button in gnome-appearance-properties doesn't do anything
*** This bug is a duplicate of bug 136813 *** https://bugs.launchpad.net/bugs/136813 ** This bug has been marked a duplicate of bug 136813 (Gutsy) help button does not work in gnome-appearance-properties -- Help-button in gnome-appearance-properties doesn't do anything https://bugs.launchpad.net/bugs/260646 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 136813] Re: (Gutsy) help button does not work in gnome-appearance-properties
Not FIXED in 8.10/Gnome 2.24 see http://bugzilla.gnome.org/attachment.cgi?id=122030 in http://bugzilla.gnome.org/show_bug.cgi?id=473181 -- (Gutsy) help button does not work in gnome-appearance-properties https://bugs.launchpad.net/bugs/136813 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 286285] Re: kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x00000100
Hi Rocko, The problem you are describing is https://bugs.launchpad.net/ubuntu/intrepid/+source/linux/+bug/276990 and a patch was available for that problem. But it gets better. The patch at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/52 includes the patch from bug#276990 and so it eases both problems. My suggestion today is to use the patch mentioned https://bugs.launchpad.net/ubuntu/intrepid/+source/linux/+bug/276990 as testers who have tried today's "intrepid-proposed" fixed report that it is not helping. Robb -- kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x0100 https://bugs.launchpad.net/bugs/286285 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 259385] Re: Intrepid Compiz hangs on login for i830MG and i845 video cards
Okay, I think I'm reading that the 845G is blacklisted from compiz, thus dodging the bug(s) causing the hang. The status here, however, is "Fix Released." Is that right? Seems there is still an actual bug out there to be hunted. -- Intrepid Compiz hangs on login for i830MG and i845 video cards https://bugs.launchpad.net/bugs/259385 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 286285] Re: kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x00000100
Dylan, you've most probably got the correct bug report. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/52 has a patch that will ease the issue. There is an update forthcoming in the "proposed" repository, but so far nobody has reported on it (it was still missing as of my last check a few hours ago). Read about it https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/73 and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/80. -- kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x0100 https://bugs.launchpad.net/bugs/286285 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 286285] Re: kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x00000100
linux-image-2.6.27-8-generic is looking good. > Beware that this doesn't yet have linux-restricted-modules or > -backports-modules available, these will follow in a bit. Worth repeating. I tried to apply only linux-image-2.6.27-8-generic and Synaptic let me do so without complaint. I booted into a low-res gdm. Then I went to apply all the other proposed and still ended up with graphics-related error messages and a low-res gnome. Ultimately I went back to 2.6.27-7 to System-Administration-Hardware and turned off the Restricted Nvidia driver, I then uninstalled and reinstalled linux-image-2.6.27-8-generic which fixed whatever dependencies I broke. Now that I'm up, linux-image-2.6.27-8-generic is looking good. -- kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x0100 https://bugs.launchpad.net/bugs/286285 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 295781] Re: logs (syslog, messages, kern.log) flooded on new 8.10 installation - no wlan
*** This bug is a duplicate of bug 286285 *** https://bugs.launchpad.net/bugs/286285 Bug#295781 does not appear to be a duplicate of bug#286285, which had a root cause and is patched in wifi code. -- logs (syslog, messages, kern.log) flooded on new 8.10 installation - no wlan https://bugs.launchpad.net/bugs/295781 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
