[Bug 414280] Re: pulseaudio killall does not prevent pulseaudio from restarting
Attempted to use a program which does raw IO to the sound device. "sudo alsa force-unload" finds pulseaudio, kills it, but it comes back before any unload could happen. I see it coming back from init, so I couldn't identify the reason it restarts. This means I'm not alone. As for the Wine part, for me Wine works correctly with pa. Could it be the "wineserver" process the one that restarts pa? :/ I'm talking about precise (12.04) here, so it still exists :| ** Changed in: pulseaudio (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/414280 Title: pulseaudio killall does not prevent pulseaudio from restarting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/414280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969359] Re: [keyboard]: gnome-settings-daemon consumes 100% cpu (and blinking numlock)
To me it happened once, after other bugs: 1. Used extensively (GPARTED=100%), crashed gnome-shell (wasn't answering, I guess the kernel or something else killed it) 2. Attempted to log back in (had to do SYSRQ+K to logout), got forced in gnome-classic (however having my icon theme) 3. Rebooted, nothing else, and 100%. This made me kill it, but... 4. Lost icon themes and etc. I tried to restart it and succeded after many attempts. And I guess it handles the keyboard too, since the LEDs weren't working as I configured them but rather had default behaviour... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969359 Title: [keyboard]: gnome-settings-daemon consumes 100% cpu (and blinking numlock) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/969359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 405120] Re: resume from suspend doesn't work (powers off instead) for Acer Aspire 3810T
In Precise this is solved (I risked). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/405120 Title: resume from suspend doesn't work (powers off instead) for Acer Aspire 3810T To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/405120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 405120] Re: resume from suspend doesn't work (powers off instead) for Acer Aspire 3810T
I am aware of the cause of the bug in all... When the computer enters suspend mode (at least in my case) the hard disk stops spinning and when I attempt resuming, I get a kernel panic. The solution is for the kernel to always try to spin at least the hard disk drive where the root file system sits... This doesn't affect computers having a solid-state drive [SSD] as their root disk. I will first attempt checking whether this was solved in Precise (I had it in Lucid) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/405120 Title: resume from suspend doesn't work (powers off instead) for Acer Aspire 3810T To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/405120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
