[Bug 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically due to internal alsa-plugins pulse check
I'm reopening this bug because I'm running into this problem despite the fix dated 2008-12-03. Please let me know if opening a new one is more appropriate. I'm using the amd64 version of Xubuntu 9.0.4 (default install) on a Sony Vaio VGN-G2. The system stalls during reboot/halt. For reboot, it shows the following error message: nm-dispatcher.action: Caught signal 15, shutting down... acpid: exiting nm-system-settings: SCPlugin-Ifupdown: devices removed (udi: /org/freedesktop/Hal/devices/net_00_1a_80_d6_06_5a) nm-system-settings: SCPlugin-Ifupdown: devices removed (udi: /oorg/freedesktop/Hal/devices/net_00_1f_3c_85_77_4a) For halt, the message is just "acpi: exiting\n\n". The system is still responsive in the sense that the Enter key advances the cursor, and the laptop blanks the screen after inactivity. The problem goes away if I add the link K88NetworkManager to rc0.d and rc6.d. I got the number 88 from Debian's network-manager package. ** Changed in: network-manager Status: Invalid => New -- 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically due to internal alsa-plugins pulse check
Revert. I meant to change the status for network-manager (Ubuntu), not NetworkManager. ** Changed in: network-manager Status: New => Invalid -- 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically due to internal alsa-plugins pulse check
I'm reopening this bug because it reproduces with the latest release, which seems to have the fix released on 2008-12-03. I'm running a default install of Xubuntu 9.0.4 on a Sony Vaio VGN-G2. Problem: the system hangs during reboot or halt if there is an active wireless connection. During reboot, I get the following message * Stopping anac(h)ronistic cron anacron acpid: exiting nm-system-settings:SCPlugin-Ifupdown: devices removed (udi: /or/freedesktop/Hal/devices/net_00_1a_80_d6_06_5a) nm-system-settings:SCPlugin-Ifupdown: devices removed (udi: /org/freedesktop/Hal/devices/net_00_1f_3c_85_77_4a) nm-dispatcher.action: Caught signal 15, shutting down... The first line is sometimes different, but I can't seem to get the alternative message at the moment. The system makes no further progress. For halt, the message is just "acpid: exiting\n\n", or sometimes it's just blank. The system is not completely frozen; the Enter key advances the cursor and the console is blanked after inactivity (and lights up again in response to a keystroke). Ctrl+Alt+Delete seems to be registering---it doesn't cause the system to make progress but after repeatedly pressing the combination, I see "init: control-alt-delete respawning too fast, stopped". The reproducibility is not 100% although it's fairly high, well over 50% (subjectively; I didn't acutally count). The problem goes away if I link /etc/init.d/NetworkManager from rc0.d and rc6.d. I used the prefix K88 following Debian, but perhaps a different number is more appropriate for Ubuntu. ** Changed in: network-manager (Ubuntu) Status: Invalid => New -- 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 388291] [NEW] Computer hangs during reboot/halt
Public bug reported: Binary package hint: network-manager This bug is probably related to #274995 (which was closed on 2008-12-03), but I'm opening a new one following Michael Rooney's kind advice. I'm running a default install of Xubuntu 9.0.4 on a Sony Vaio VGN-G2. Problem: the system hangs during reboot or halt if there is an active wireless connection. During reboot, I get the following message * Stopping anac(h)ronistic cron anacron acpid: exiting nm-system-settings:SCPlugin-Ifupdown: devices removed (udi: /or/freedesktop/Hal/devices/net_00_1a_80_d6_06_5a) nm-system-settings:SCPlugin-Ifupdown: devices removed (udi: /org/freedesktop/Hal/devices/net_00_1f_3c_85_77_4a) nm-dispatcher.action: Caught signal 15, shutting down... The first line is sometimes different, but I can't seem to get the alternative message at the moment. The system makes no further progress. For halt, the message is just "acpid: exiting\n\n", or sometimes it's just blank. The system is not completely frozen; the Enter key advances the cursor and the console is blanked after inactivity (and lights up again in response to a keystroke). Ctrl+Alt+Delete seems to be registering---it doesn't cause the system to make progress but after repeatedly pressing the combination, I see "init: control-alt-delete respawning too fast, stopped". The reproducibility is not 100% although it's fairly high, well over 50% (subjectively; I didn't acutally count). The problem seems to go away if I link /etc/init.d/NetworkManager from rc0.d and rc6.d. (But please bare in mind this is a nondeterministic bug.) I used the prefix K88 immitating Debian, but perhaps a different number is more appropriate for Ubuntu. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- Computer hangs during reboot/halt https://bugs.launchpad.net/bugs/388291 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
Revert. I filed my report under #388291 following Michael Rooney's kind advice. ...Sorry to spam everyone with status changes. ** Changed in: network-manager (Ubuntu) Status: New => Invalid -- 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 1907944] [NEW] mpv can't play any videos, just eats up memory
Public bug reported: I can't seem to play any videos with mpv. When I invoke it like `mpv /path/to/file', it pops up a window but then eats up a ton of memory without showing anything. Eventually, the system becomes clogged up and I have to kill it with kill -9. Running it under ulimit -v $((4*1024*1024)) causes it to get killed, so it's at least occupying 4G of memory just to play a 640x360 file. I'm seeing similar behavior with vlc on the same system, if that might provide a clue. I've tried a few input files, the smallest being 640x360 m2v and asf files available here: https://filesamples.com/categories/video ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mpv 0.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Sun Dec 13 15:58:24 2020 InstallationDate: Installed on 2015-12-31 (1808 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: mpv UpgradeStatus: Upgraded to focal on 2020-06-15 (180 days ago) ** Affects: mpv (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907944 Title: mpv can't play any videos, just eats up memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpv/+bug/1907944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907944] Re: mpv can't play any videos, just eats up memory
Uhhh, actually the problem resolved itself after upgrading to 20.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907944 Title: mpv can't play any videos, just eats up memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpv/+bug/1907944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1595383] Re: Registration Timeout is Excessively Long
This patch changes the timeout to 5 seconds, which is probably too short for some slower media but reasonable for desktop installations. This is just a workaround as noted above; not meant for upstream. ** Patch added: "shorter-timeout.patch" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1595383/+attachment/4688851/+files/shorter-timeout.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1595383 Title: Registration Timeout is Excessively Long To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1595383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1595383] [NEW] Registration Timeout is Excessively Long
Public bug reported: I'm suffering from a problem where gnome-session pauses for a very long time (90 seconds) during login. I type in my password to lightdm, the screen switches to show my wallpaper, but nothing else, and for the next minute and a half, I can't do anything besides move the cursor. Clicks don't do anything, key combinations to start a terminal don't work. In /var/log/syslog, I see a message Jun 23 11:24:21 jun-MacBookAir gnome-session[1591]: gnome-session- binary[1591]: WARNING: Application 'at-spi-dbus-bus.desktop' failed to register before timeout which seems to be caused by a problem with at-spi-dbus-bus.desktop, but this bug report is not about that. The bug I'd like to report here is that gnome-session's timeout is *way* too long. At first I had no idea that the login was going to succeed at all, because it was frozen for so long, and I kept rebooting by pushing the power button. The 90-second wait seems to be hard-coded in the source, with a remark that waiting long enough is critical on slower media like CD-ROMs. While I can see how that's a concern, it makes no sense on a desktop installation booting from the SSD. The long wait interferes with debugging the problem (because every single thing I try takes at least 90 seconds), and will ensure that a problem in any of the components like at-spi-dbus-bus.desktop will show up as a serious inconvenience. I for one cannot stand a computer that takes minutes to boot, just because one component is acting erratically. Please make this timeout shorter if at all possible, or at least configurable. Better yet, please have this automatically configured by benchmarking the system upon installation. In the meantime, I'm attaching a patch for anyone who wants a quick work around to this nasty problem. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-session 3.18.1.2-1ubuntu1.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Jun 23 13:07:40 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-11-12 (223 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: Upgraded to xenial on 2016-05-28 (25 days ago) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1595383 Title: Registration Timeout is Excessively Long To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1595383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1166102] Re: Cannot mix incompatible Qt library
I'm affected by this as well. When I try to start any of okular, VirtualBox (the qt GUI), kmail, or AFAICT anything that uses qt4, I get $ kmail Cannot mix incompatible Qt library (version 0x40804) with this library (version 0x40801) zsh: abort (core dumped) kmail $ okular Cannot mix incompatible Qt library (version 0x40804) with this library (version 0x40801) KCrash: Application 'okular' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit sock_file=/home/jun/.kde/socket-jun-MacBookAir/kdeinit4__0 Warning: connect() failed: : No such file or directory KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi directly Cannot mix incompatible Qt library (version 0x40804) with this library (version 0x40801) $ anki Cannot mix incompatible Qt library (version 0x40804) with this library (version 0x40801) zsh: abort (core dumped) anki I've tried recompiling okular from the source package, but I got the same exact error. This has rendered many packages completely unusable for me. I think this bug deserves a high importance rating, unless it's rare (i.e. affecting few people), because AFAICT for those who are affected this bug is seriously crippling. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1166102 Title: Cannot mix incompatible Qt library To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1166102/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1068869] [NEW] Gnome with Xmonad starts without xmonad
Public bug reported: The "Gnome with Xmonad" session starts up normally, but doesn't automatically launch xmonad. The Gnome panel starts up without a window manager. When I start a terminal and manually boot up xmonad, it works fine. [Steps to Reproduce] At the log in prompt (I'm using lightdm), select "Gnome with Xmonad" and log in. [Expected Behavior] A Gnome session should start with windows managed by xmonad. [Actual Behavior] A Gnome session starts, but without a window manager. [Workaround] Add the line "xmonad&" as the second line of /usr/bin/gnome-session-xmonad, so that the file contains these three lines in total: #! /bin/sh xmonad& exec gnome-session --session xmonad "$@" A few insights: xmonad doesn't seem to be invoked at all. If I rename xmonad so that gnome-session can't find it, the session still starts up as if it didn't notice anything. OTOH, /usr/bin/gnome-session-xmonad *is* getting invoked. If I add a line in that file to start xmonad as described in the workaround above, then the session starts up with xmonad managing the windows. This could be a bug in gnome-session, but that utility works fine for all other purposes AFAICT, so I'll tentatively file this under xmonad. I just upgraded to quantal today, but I can't tell if that's a factor as I've been using xmonad with Unity 2D before the upgrade. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xmonad 0.10-4build2 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Fri Oct 19 23:34:22 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64+mac (20111012) SourcePackage: xmonad UpgradeStatus: Upgraded to quantal on 2012-10-19 (0 days ago) ** Affects: xmonad (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1068869 Title: Gnome with Xmonad starts without xmonad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xmonad/+bug/1068869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1068869] Re: Gnome with Xmonad starts without xmonad
Er... I just noticed my "workaround" above doesn't work completely. This is a separate, possibly unrelated issue, but if anyone has had the same problem and is hunting for a workaround, you should add xmonad through the Gnome GUI. Go to the main menu -> system tools -> settings -> autostart applications, and add xmonad. Do NOT modify /usr/bin /gnome-session-xmonad. I wrote that based on my Japanese settings, so the exact wording may be different. [The Problem] If you start xmonad before gnome-session like I suggested above, then dmenu doesn't seem to work at all. I bind mod-p to spawning "dmenu_run", but if I start xmonad before gnome-session and then press mod-p, the gnome panel blinks for a second and nothing happens. If I start up gnome-session without a window manager and then invoke xmonad, dmenu_run works fine. I didn't (and won't) have time to dig deeper into this dmenu issue, but I'll put this advice up here in case someone needs a quick fix. I'm attaching my xmonad.hs file. It's probably not related to the problem that xmonad doesn't start automatically, but it may well be related to the problem with dmenu_run not running. ** Attachment added: "xmonad.hs" https://bugs.launchpad.net/ubuntu/+source/xmonad/+bug/1068869/+attachment/3405057/+files/xmonad.hs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1068869 Title: Gnome with Xmonad starts without xmonad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xmonad/+bug/1068869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1010558] [NEW] Can't Disable Custom Keyboard Setting
Public bug reported:
I can't disable the default key binding for t ("Launch
Terminal") from gnome-control-center. (Note: I use Ubuntu's Japanese
edition, and I merely traslated the menu items into English. They might
be worded slightly differently on actual English-edition systems.)
Steps to reproduce:
0. mutter-common should be installed for these steps to exhibit the bug.
1. Type "gnome-control-center" on the command line.
2. Click on "Keyboard" -> "Shortcuts" -> "Custom Shortcuts".
There should be a binding for "Launch Terminal". I wanted to disable this
binding.
3. Click on the "Launch Terminal" line, and dismiss the dialog it pops up.
4. Now click on the "-" button. The binding will disappear from the list.
5. Close the control center and hit Ctrl-Alt-t in the app of your choice (I
used emacs).
Expected behavior: terminal should no longer start; the currently
focused application should get the keys. gnome-control-center should no
longer show the binding that I deleted.
Actual behavior: terminal starts; the application doesn't see the keys.
If you start gnome-control-center again, you will find that the "Launch
Terminal" shortcut has magically resurrected itself.
It is possible to change the keys bound to "Launch Terminal", and it is
possible to change the action taken when this shortcut is fired. Those
changes stick. But removal of the binding is always silently undone.
Possible cause: I don't know enough about gconf to say for sure, but it
seems like settings introduced in /usr/share/gconf/defaults/* are
treated as "permanent". This particular problem with "Launch Terminal"
is caused by the setting in /usr/share/gconf/defaults/10_mutter-common.
It does not seem to matter whether you use mutter or not; that file
hijacks the settings just by being there.
Workaround: Uninstall mutter-common. Or, set "Launch Terminal" to a key
that you'll never press, like Ctrl+Alt+Shift+F12.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gnome-control-center 1:3.4.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16
Uname: Linux 3.2.0-24-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Fri Jun 8 17:58:54 2012
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64+mac (20111012)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to precise on 2012-05-17 (22 days ago)
usr_lib_gnome-control-center:
activity-log-manager-control-center 0.9.4-0ubuntu3
deja-dup22.0-0ubuntu2
gnome-bluetooth 3.2.2-0ubuntu5
indicator-datetime 0.3.94-0ubuntu2
** Affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1010558
Title:
Can't Disable Custom Keyboard Setting
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1010558/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1010558] Re: Can't Disable Custom Keyboard Setting
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1010558 Title: Can't Disable Custom Keyboard Setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1010558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
