[Desktop-packages] [Bug 1292041] Re: Lockscreen doesn't turn off the screen
I have also been hit by this bug. Extremely irritating. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292041 Title: Lockscreen doesn't turn off the screen Status in OEM Priority Project: Fix Released Status in OEM Priority Project trusty series: Fix Released Status in Unity: Fix Released Status in gnome-screensaver package in Ubuntu: Invalid Status in unity package in Ubuntu: Fix Released Bug description: [ATTENTION] This bug report is strictly for lockscreen. When user activates lockscreen with Ctrl+Alt+L or Super+L shortcut or from indicator-session the screen should blank off after a couple seconds. The new Unity lock screen doesn't turn off the monitor screen. I can wait as long as 10 minutes after activating the lock screen and the monitor still doesn't turn off. Then when I unlock the screen and don't use mouse or keyboard monitor will turn off (it's about 5 seconds after unlocking). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1292041/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1507764] Re: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout
I was just hit again with it today, with metacity 1:3.18.7-0ubuntu0.3 on 16.04. Here is the crash dump. ** Attachment added: "_usr_bin_metacity.1000.crash" https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+attachment/5189891/+files/_usr_bin_metacity.1000.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1507764 Title: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout Status in metacity package in Ubuntu: Expired Bug description: This bug seemed to occur already since earlier versions of Ubuntu, and usually would just end up leaving me with undecorated windows, from which recovery was as easy as restarting metacity by hand, but in this release of Ubuntu (15.04), it seems gnome-session tries to restart it too many times in a too short span, and then decides arbitrarily that it failed so bad it has to kill the whole session. So, while the metacity bug is really a thing, my real problem actually might be a gnome-session-bin bug. I expect metacity crashing would not bring down the whole session, as is the case currently. At any rate, this is extremely annoying, I am hitting this bug about every two days, and because of it and the regression in crash handling, I end up losing all my windows and running programs. (In all fairness, I am suspecting a hardware issue, but the problem remains that a sub process dying should not cause the parent process to die like this) ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: metacity 1:3.14.3-1ubuntu7 ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Flashback:Unity Date: Tue Oct 20 05:19:37 2015 ExecutablePath: /usr/bin/metacity InstallationDate: Installed on 2010-01-30 (2088 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1) ProcCmdline: metacity ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh Signal: 5 SourcePackage: metacity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XGetRequest () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XFixesCopyRegion () from /usr/lib/x86_64-linux-gnu/libXfixes.so.3 Title: metacity crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to vivid on 2015-09-05 (44 days ago) UserGroups: adm admin audio cdrom dialout libvirtd lpadmin plugdev pulse pulse-access sambashare vboxusers video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 771272] Re: gnome-keyring doesn't support ecdsa or ed25519 keys
Used the workaround in #12, but it is still a major annoyance that gnome-keyring-daemon does not handle this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/771272 Title: gnome-keyring doesn't support ecdsa or ed25519 keys Status in GNOME Keyring: Confirmed Status in gnome-keyring package in Ubuntu: Triaged Status in gnome-keyring package in Debian: Confirmed Bug description: Binary package hint: gnome-keyring I'm not sure I have described it correctly in the summary, but this is what happens: I run ssh-add in a new terminal and enter my passphrase, which is the same for my DSA and ECDSA key: the DSA identity is added, but the ECDSA gets the "Error reading response length from authentication socket. Could not add identity: /home/claudio/.ssh/id_ecdsa" error. I run ssh-agent, copy and paste the output in the terminal and re-run ssh-add. Both identities are correctly added: claudio@Chuck:~$ ssh-add Enter passphrase for /home/claudio/.ssh/id_dsa: Identity added: /home/claudio/.ssh/id_dsa (/home/claudio/.ssh/id_dsa) Error reading response length from authentication socket. Could not add identity: /home/claudio/.ssh/id_ecdsa claudio@Chuck:~$ ssh-agent SSH_AUTH_SOCK=/tmp/ssh-szGWMUbE3916/agent.3916; export SSH_AUTH_SOCK; SSH_AGENT_PID=3917; export SSH_AGENT_PID; echo Agent pid 3917; claudio@Chuck:~$ SSH_AUTH_SOCK=/tmp/ssh-szGWMUbE3916/agent.3916; export SSH_AUTH_SOCK; claudio@Chuck:~$ SSH_AGENT_PID=3917; export SSH_AGENT_PID; claudio@Chuck:~$ echo Agent pid 3917; Agent pid 3917 claudio@Chuck:~$ ssh-add Enter passphrase for /home/claudio/.ssh/id_dsa: Identity added: /home/claudio/.ssh/id_dsa (/home/claudio/.ssh/id_dsa) Identity added: /home/claudio/.ssh/id_ecdsa (/home/claudio/.ssh/id_ecdsa) Here is the content of my ~/.ssh/ claudio@Chuck:~$ ls -l .ssh total 32 -rw-r--r-- 1 claudio claudio 726 2011-04-15 23:34 config -r 1 claudio claudio 751 2011-04-05 10:35 id_dsa -rw-r--r-- 1 claudio claudio 603 2011-04-05 10:34 id_dsa.pub -r 1 claudio claudio 444 2011-04-05 10:29 id_ecdsa -rw-r--r-- 1 claudio claudio 267 2011-04-05 10:23 id_ecdsa.pub -rw--- 1 claudio claudio 6402 2011-04-19 18:04 known_hosts -rw-r--r-- 1 claudio claudio 2760 2011-04-06 17:05 known_hosts.old ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-keyring 2.92.92.is.2.32.1-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Tue Apr 26 16:27:02 2011 ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-keyring UpgradeStatus: Upgraded to natty on 2011-04-03 (23 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/771272/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637855] [NEW] Composite characters or Japanese input gets sometimes sent to the wrong terminal window
Public bug reported: At times (I have not found the trigger to reproduce it at will), one terminal window out of many will refuse to receive complex input sequences (such as the French composite accented character "ê" (which is typed with "^ + e" on a french keyboard), or IBus/Anthy Japanese input), and only these characters will be redirected to another terminal window. This means that for two terminals, typing in terminal 1 : "Verbe être" results in this : Terminal 1 : "Verbe tre" Terminal 2 : "ê" When this happens, the following workarounds work to put things in order : - close the affected terminal window - spawn a new one and close it I am not sure whether this is an IBus problem, or a Gnome Terminal problem at its core. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gnome-terminal 3.16.2-1ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Mon Oct 31 01:51:06 2016 InstallationDate: Installed on 2010-01-30 (2465 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to wily on 2016-04-16 (197 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages wily -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1637855 Title: Composite characters or Japanese input gets sometimes sent to the wrong terminal window Status in gnome-terminal package in Ubuntu: New Bug description: At times (I have not found the trigger to reproduce it at will), one terminal window out of many will refuse to receive complex input sequences (such as the French composite accented character "ê" (which is typed with "^ + e" on a french keyboard), or IBus/Anthy Japanese input), and only these characters will be redirected to another terminal window. This means that for two terminals, typing in terminal 1 : "Verbe être" results in this : Terminal 1 : "Verbe tre" Terminal 2 : "ê" When this happens, the following workarounds work to put things in order : - close the affected terminal window - spawn a new one and close it I am not sure whether this is an IBus problem, or a Gnome Terminal problem at its core. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gnome-terminal 3.16.2-1ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Mon Oct 31 01:51:06 2016 InstallationDate: Installed on 2010-01-30 (2465 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to wily on 2016-04-16 (197 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1637855/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637823] [NEW] keyboard input is not processed in the right order during high CPU load times
Public bug reported: I have noticed several issues with keyboard input processing, that can all seemingly be tied to high CPU usage. For context, I am using a french keyboard, and also need to type Japanese, which has me using IBus and Anthy. I think at some point in Ubuntu, the way input was handled changed drastically, and ever since I have been dealing with the following issues : - Composite keys such as ^ (^ + e => ê) used in French for accents are processed in a weird way : Suppose I type "Le verbe être est", I sometimes end up with "Le verbe treê est" actually appearing when typing under high CPU load. (Hinting at the fact that the ^ key stroke processing happens asynchronously, and without accounting for the proper and expected order of strokes, which is extremely annoying) (I mainly see this specific problem in applications such as Chrome, Skype for Linux Alpha, Discord, Slack.) Before I found a suggestion to set IBUS_ENABLE_SYNC_MODE=1 in my session environment, keyboard input order would end up completely shuffled. Enforcing sync mode nearly fixed everything except for composite keys. - When switching between French and Japanese, I have defined a specific shortcut to do the switching for me, and I am used to the switching taking time. The problem is that switching does not lock any input after that, so that it would be processed AFTER the switch was complete. When typing "tesuto" I expect the following to be input : てすと But I get the following : teすと This one, I am thinking is caused by asynchronous input processing for the shortcut keys, and the Anthy process taking time to get called back from swap memory. I would be perfectly fine with the previous behavior, and waiting three seconds, as long as input would be processed all at once, in the order I typed it. The above two problems mean I have to actually watch at what times I am going to need to use accented characters, or to type Japanese, and WAIT for the computer to finish switching before resuming typing. These literally halve my typing speed because I can't rely on muscle memory anymore when typing any language other than English. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ibus 1.5.10-1ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Sun Oct 30 20:45:04 2016 InstallationDate: Installed on 2010-01-30 (2464 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1) SourcePackage: ibus UpgradeStatus: Upgraded to wily on 2016-04-16 (196 days ago) ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages wily -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1637823 Title: keyboard input is not processed in the right order during high CPU load times Status in ibus package in Ubuntu: New Bug description: I have noticed several issues with keyboard input processing, that can all seemingly be tied to high CPU usage. For context, I am using a french keyboard, and also need to type Japanese, which has me using IBus and Anthy. I think at some point in Ubuntu, the way input was handled changed drastically, and ever since I have been dealing with the following issues : - Composite keys such as ^ (^ + e => ê) used in French for accents are processed in a weird way : Suppose I type "Le verbe être est", I sometimes end up with "Le verbe treê est" actually appearing when typing under high CPU load. (Hinting at the fact that the ^ key stroke processing happens asynchronously, and without accounting for the proper and expected order of strokes, which is extremely annoying) (I mainly see this specific problem in applications such as Chrome, Skype for Linux Alpha, Discord, Slack.) Before I found a suggestion to set IBUS_ENABLE_SYNC_MODE=1 in my session environment, keyboard input order would end up completely shuffled. Enforcing sync mode nearly fixed everything except for composite keys. - When switching between French and Japanese, I have defined a specific shortcut to do the switching for me, and I am used to the switching taking time. The problem is that switching does not lock any input after that, so that it would be processed AFTER the switch was complete. When typing "tesuto" I expect the following to be input : てすと But I get the following : teすと This one, I am thinking is caused by asynchronous input processing for the shortcut keys, and the Anthy process taking time to get called back from swap memory. I would be perfectly fine with the previous behavior, and waiting three seconds, as long as input would be processed all at once, in the order I typed it. The above two problems
[Desktop-packages] [Bug 1637822] [NEW] autosave freezes editor and loses keystrokes
Public bug reported: The very useful autosave feature that runs every five minutes locks up the editor when it runs, and when it happens, any keystrokes typed during the interval are lost. Such that when typing the following (for example) : abcdefghijklmnopqrstuvwxyz If autosave runs during that interval, here is an example of what ends up being processed : abcdefghpqrstuvwxyz As is obvious, keystrokes for "ijklmno" are lost. This happens every time. I am not sure if this is specific to gedit, or to the input framework I am using (IBus, and at times Anthy for Japanese input) This is quite annoying as it forces me to re-read absolutely everything I typed to make sure gedit did not miss anything. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gedit 3.10.4-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Sun Oct 30 20:37:04 2016 InstallationDate: Installed on 2010-01-30 (2464 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1) SourcePackage: gedit UpgradeStatus: Upgraded to wily on 2016-04-16 (196 days ago) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages wily -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1637822 Title: autosave freezes editor and loses keystrokes Status in gedit package in Ubuntu: New Bug description: The very useful autosave feature that runs every five minutes locks up the editor when it runs, and when it happens, any keystrokes typed during the interval are lost. Such that when typing the following (for example) : abcdefghijklmnopqrstuvwxyz If autosave runs during that interval, here is an example of what ends up being processed : abcdefghpqrstuvwxyz As is obvious, keystrokes for "ijklmno" are lost. This happens every time. I am not sure if this is specific to gedit, or to the input framework I am using (IBus, and at times Anthy for Japanese input) This is quite annoying as it forces me to re-read absolutely everything I typed to make sure gedit did not miss anything. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gedit 3.10.4-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Sun Oct 30 20:37:04 2016 InstallationDate: Installed on 2010-01-30 (2464 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1) SourcePackage: gedit UpgradeStatus: Upgraded to wily on 2016-04-16 (196 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1637822/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1507764] Re: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout
I upgraded to older version 3.18.1-1ubuntu3, and relaunched metacity using "metacity --replace", and now I have metacity crashes, but they don't log me out. Just wondering if the fact I "replaced" metacity while logged in untied it from gnome-session. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1507764 Title: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout Status in metacity package in Ubuntu: Confirmed Bug description: This bug seemed to occur already since earlier versions of Ubuntu, and usually would just end up leaving me with undecorated windows, from which recovery was as easy as restarting metacity by hand, but in this release of Ubuntu (15.04), it seems gnome-session tries to restart it too many times in a too short span, and then decides arbitrarily that it failed so bad it has to kill the whole session. So, while the metacity bug is really a thing, my real problem actually might be a gnome-session-bin bug. I expect metacity crashing would not bring down the whole session, as is the case currently. At any rate, this is extremely annoying, I am hitting this bug about every two days, and because of it and the regression in crash handling, I end up losing all my windows and running programs. (In all fairness, I am suspecting a hardware issue, but the problem remains that a sub process dying should not cause the parent process to die like this) ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: metacity 1:3.14.3-1ubuntu7 ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Flashback:Unity Date: Tue Oct 20 05:19:37 2015 ExecutablePath: /usr/bin/metacity InstallationDate: Installed on 2010-01-30 (2088 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1) ProcCmdline: metacity ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh Signal: 5 SourcePackage: metacity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XGetRequest () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XFixesCopyRegion () from /usr/lib/x86_64-linux-gnu/libXfixes.so.3 Title: metacity crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to vivid on 2015-09-05 (44 days ago) UserGroups: adm admin audio cdrom dialout libvirtd lpadmin plugdev pulse pulse-access sambashare vboxusers video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1507764] Re: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout
Initially, I thought the crash was linked to what was implementing the window switching (with the Compiz configuration tool, one can select several ways to switch windows, including the Static Application Switcher, which only shows icons of the application instead of the contents of the window ; which I thought might take a toll on graphics function). As for the steps, I am sorry I can't provide any better information : the only thing I can say is, it looks like something is accumulating like a leak. At one point I will start seeing artifacts when switching windows, seeing window redraw problems, and ultimately the last straw will make stuff blow up. Thanks for the packages, I will try that right away. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1507764 Title: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout Status in metacity package in Ubuntu: New Bug description: This bug seemed to occur already since earlier versions of Ubuntu, and usually would just end up leaving me with undecorated windows, from which recovery was as easy as restarting metacity by hand, but in this release of Ubuntu (15.04), it seems gnome-session tries to restart it too many times in a too short span, and then decides arbitrarily that it failed so bad it has to kill the whole session. So, while the metacity bug is really a thing, my real problem actually might be a gnome-session-bin bug. I expect metacity crashing would not bring down the whole session, as is the case currently. At any rate, this is extremely annoying, I am hitting this bug about every two days, and because of it and the regression in crash handling, I end up losing all my windows and running programs. (In all fairness, I am suspecting a hardware issue, but the problem remains that a sub process dying should not cause the parent process to die like this) ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: metacity 1:3.14.3-1ubuntu7 ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Flashback:Unity Date: Tue Oct 20 05:19:37 2015 ExecutablePath: /usr/bin/metacity InstallationDate: Installed on 2010-01-30 (2088 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1) ProcCmdline: metacity ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh Signal: 5 SourcePackage: metacity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XGetRequest () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XFixesCopyRegion () from /usr/lib/x86_64-linux-gnu/libXfixes.so.3 Title: metacity crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to vivid on 2015-09-05 (44 days ago) UserGroups: adm admin audio cdrom dialout libvirtd lpadmin plugdev pulse pulse-access sambashare vboxusers video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1507764] Re: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout
About the packages, I am still using 15.04 Vivid (which means metacity 3.14), and it seems metacity and gtk+-3.0 will require a ton of dependencies (glib, pango, atk, etc...), so I can't test these right away. Here is what I get : $ gsettings get org.gnome.metacity alt-tab-thumbnails No such key 'alt-tab-thumbnails' As for configuration, it seems I am still relying on CCSM (CompizConfig Settings Manager), which offers : - Application Switcher - Static Application Switcher (the one I use, which pops up with only icons) Also, I don't think this is related but it feels like at times the application switch is not instant (meaning, I need to wait a little bit to be sure that it did switch, otherwise the keys I hit right after Alt+Tab get processed by the previous application, which is kind of annoying) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1507764 Title: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout Status in metacity package in Ubuntu: New Bug description: This bug seemed to occur already since earlier versions of Ubuntu, and usually would just end up leaving me with undecorated windows, from which recovery was as easy as restarting metacity by hand, but in this release of Ubuntu (15.04), it seems gnome-session tries to restart it too many times in a too short span, and then decides arbitrarily that it failed so bad it has to kill the whole session. So, while the metacity bug is really a thing, my real problem actually might be a gnome-session-bin bug. I expect metacity crashing would not bring down the whole session, as is the case currently. At any rate, this is extremely annoying, I am hitting this bug about every two days, and because of it and the regression in crash handling, I end up losing all my windows and running programs. (In all fairness, I am suspecting a hardware issue, but the problem remains that a sub process dying should not cause the parent process to die like this) ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: metacity 1:3.14.3-1ubuntu7 ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Flashback:Unity Date: Tue Oct 20 05:19:37 2015 ExecutablePath: /usr/bin/metacity InstallationDate: Installed on 2010-01-30 (2088 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1) ProcCmdline: metacity ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh Signal: 5 SourcePackage: metacity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XGetRequest () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XFixesCopyRegion () from /usr/lib/x86_64-linux-gnu/libXfixes.so.3 Title: metacity crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to vivid on 2015-09-05 (44 days ago) UserGroups: adm admin audio cdrom dialout libvirtd lpadmin plugdev pulse pulse-access sambashare vboxusers video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1507764] Re: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout
I just had again the same crash. : Dec 30 23:49:59 archer gnome-session[28277]: Window manager warning: Log level 6: The program 'metacity' received an X Window System error. Dec 30 23:49:59 archer gnome-session[28277]: This probably reflects a bug in the program. Dec 30 23:49:59 archer gnome-session[28277]: The error was 'BadRegion (invalid Region parameter)'. Dec 30 23:49:59 archer gnome-session[28277]: (Details: serial 1686054464 error_code 140 request_code 138 (XFIXES) minor_code 12) Dec 30 23:49:59 archer gnome-session[28277]: (Note to programmers: normally, X errors are reported asynchronously; Dec 30 23:49:59 archer gnome-session[28277]: that is, you will receive the error a while after causing it. Dec 30 23:49:59 archer gnome-session[28277]: To debug your program, run it with the GDK_SYNCHRONIZE environment Dec 30 23:49:59 archer gnome-session[28277]: variable to change this behavior. You can then get a meaningful Dec 30 23:49:59 archer gnome-session[28277]: backtrace from your debugger if you break on the gdk_x_error() function.) which led once apport was done writing the crash report : Dec 30 23:54:51 archer gnome-session[28277]: gnome-session[28277]: WARNING: Application 'metacity.desktop' killed by signal 5 Dec 30 23:54:51 archer gnome-session[28277]: WARNING: Application 'metacity.desktop' killed by signal 5 Dec 30 23:54:51 archer gnome-session[28277]: gnome-session[28277]: WARNING: App 'metacity.desktop' respawning too quickly Dec 30 23:54:51 archer gnome-session[28277]: WARNING: App 'metacity.desktop' respawning too quickly Dec 30 23:54:51 archer gnome-session[28277]: Unrecoverable failure in required component metacity.desktop Dec 30 23:54:51 archer gnome-session[28277]: gnome-session[28277]: CRITICAL: We failed, but the fail whale is dead. Sorry Dec 30 23:54:51 archer gnome-session[28277]: CRITICAL: We failed, but the fail whale is dead. Sorry >From what I tried, it seems like trying to run "metacity --replace" before apport finishes killing the old instance does not work : once it freezes and apport is writing its stuff, the whole session will go down. Seriously, this regression is infuriating and makes Ubuntu barely usable for me. I nearly stopped using Alt+Tab out of fear of losing work when switching between gedit and evince. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1507764 Title: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout Status in metacity package in Ubuntu: New Bug description: This bug seemed to occur already since earlier versions of Ubuntu, and usually would just end up leaving me with undecorated windows, from which recovery was as easy as restarting metacity by hand, but in this release of Ubuntu (15.04), it seems gnome-session tries to restart it too many times in a too short span, and then decides arbitrarily that it failed so bad it has to kill the whole session. So, while the metacity bug is really a thing, my real problem actually might be a gnome-session-bin bug. I expect metacity crashing would not bring down the whole session, as is the case currently. At any rate, this is extremely annoying, I am hitting this bug about every two days, and because of it and the regression in crash handling, I end up losing all my windows and running programs. (In all fairness, I am suspecting a hardware issue, but the problem remains that a sub process dying should not cause the parent process to die like this) ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: metacity 1:3.14.3-1ubuntu7 ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Flashback:Unity Date: Tue Oct 20 05:19:37 2015 ExecutablePath: /usr/bin/metacity InstallationDate: Installed on 2010-01-30 (2088 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1) ProcCmdline: metacity ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh Signal: 5 SourcePackage: metacity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XGetRequest () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XFixesCopyRegion () from /usr/lib/x86_64-linux-gnu/libXfixes.so.3 Title: metacity crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to vivid on 2015-09-05 (44 days ago) UserGroups: adm admin audio cdrom dialout libvirtd lpadmin plugdev pulse pulse-access sambashare vboxusers video To manage notifications about this bug go to:
[Desktop-packages] [Bug 1455916] Re: Xorg unexpectedly crashed
I just had again the same crash. : Dec 30 23:49:59 archer gnome-session[28277]: Window manager warning: Log level 6: The program 'metacity' received an X Window System error. Dec 30 23:49:59 archer gnome-session[28277]: This probably reflects a bug in the program. Dec 30 23:49:59 archer gnome-session[28277]: The error was 'BadRegion (invalid Region parameter)'. Dec 30 23:49:59 archer gnome-session[28277]: (Details: serial 1686054464 error_code 140 request_code 138 (XFIXES) minor_code 12) Dec 30 23:49:59 archer gnome-session[28277]: (Note to programmers: normally, X errors are reported asynchronously; Dec 30 23:49:59 archer gnome-session[28277]: that is, you will receive the error a while after causing it. Dec 30 23:49:59 archer gnome-session[28277]: To debug your program, run it with the GDK_SYNCHRONIZE environment Dec 30 23:49:59 archer gnome-session[28277]: variable to change this behavior. You can then get a meaningful Dec 30 23:49:59 archer gnome-session[28277]: backtrace from your debugger if you break on the gdk_x_error() function.) which led once apport was done writing the crash report : Dec 30 23:54:51 archer gnome-session[28277]: gnome-session[28277]: WARNING: Application 'metacity.desktop' killed by signal 5 Dec 30 23:54:51 archer gnome-session[28277]: WARNING: Application 'metacity.desktop' killed by signal 5 Dec 30 23:54:51 archer gnome-session[28277]: gnome-session[28277]: WARNING: App 'metacity.desktop' respawning too quickly Dec 30 23:54:51 archer gnome-session[28277]: WARNING: App 'metacity.desktop' respawning too quickly Dec 30 23:54:51 archer gnome-session[28277]: Unrecoverable failure in required component metacity.desktop Dec 30 23:54:51 archer gnome-session[28277]: gnome-session[28277]: CRITICAL: We failed, but the fail whale is dead. Sorry Dec 30 23:54:51 archer gnome-session[28277]: CRITICAL: We failed, but the fail whale is dead. Sorry >From what I tried, it seems like trying to run "metacity --replace" before apport finishes killing the old instance does not work : once it freezes and apport is writing its stuff, the whole session will go down. Seriously, this regression is infuriating and makes Ubuntu barely usable for me. I nearly stopped using Alt+Tab out of fear of losing work when switching between gedit and evince. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1455916 Title: Xorg unexpectedly crashed Status in xorg package in Ubuntu: Incomplete Bug description: Xorg unexpectedly crashed bringing down down metacity and gnome-flashback too. This is the relevant section from the system logs: May 17 15:09:05 ultra-d gnome-session[1514]: Window manager warning: Log level 6: The program 'metacity' received an X Window System error. May 17 15:09:05 ultra-d gnome-session[1514]: This probably reflects a bug in the program. May 17 15:09:05 ultra-d gnome-session[1514]: The error was 'BadRegion (invalid Region parameter)'. May 17 15:09:05 ultra-d gnome-session[1514]: (Details: serial 508727326 error_code 140 request_code 138 (XFIXES) minor_code 12) May 17 15:09:05 ultra-d gnome-session[1514]: (Note to programmers: normally, X errors are reported asynchronously; May 17 15:09:05 ultra-d gnome-session[1514]: that is, you will receive the error a while after causing it. May 17 15:09:05 ultra-d gnome-session[1514]: To debug your program, run it with the GDK_SYNCHRONIZE environment May 17 15:09:05 ultra-d gnome-session[1514]: variable to change this behavior. You can then get a meaningful May 17 15:09:05 ultra-d gnome-session[1514]: backtrace from your debugger if you break on the gdk_x_error() function.) May 17 15:09:05 ultra-d kernel: [276368.790571] traps: metacity[1688] trap int3 ip:7fb31d5d9d00 sp:7ffc0f98c740 error:0 May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: WARNING: Child process 1688 was already dead. May 17 15:09:19 ultra-d gnome-session[1514]: WARNING: Child process 1688 was already dead. May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: WARNING: Application 'metacity.desktop' killed by signal 5 May 17 15:09:19 ultra-d gnome-session[1514]: WARNING: Application 'metacity.desktop' killed by signal 5 May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: WARNING: App 'metacity.desktop' respawning too quickly May 17 15:09:19 ultra-d gnome-session[1514]: WARNING: App 'metacity.desktop' respawning too quickly May 17 15:09:19 ultra-d gnome-session[1514]: Unrecoverable failure in required component metacity.desktop May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: CRITICAL: We failed, but the fail whale is dead. Sorry May 17 15:09:19 ultra-d gnome-session[1514]: CRITICAL: We failed, but the fail whale is dead. Sorry May 17 15:09:20 ultra-d gnome-session[1514]: ICE default IO error handler doing an exit(), pid
[Desktop-packages] [Bug 1528896] [NEW] metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout (#1507764 duplicate)
Public bug reported: This is a duplicate of bug 1507764, but the bug reporting system would not let me find it for further addition. I am posting this in hopes that by crossing this trace and the previous one this might help developers find what is going on. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: metacity 1:3.14.3-1ubuntu7 ProcVersionSignature: Ubuntu 3.19.0-42.48-generic 3.19.8-ckt10 Uname: Linux 3.19.0-42-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Flashback:Unity Date: Thu Dec 24 01:49:05 2015 ExecutablePath: /usr/bin/metacity InstallationDate: Installed on 2010-01-30 (2153 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1) ProcCmdline: metacity ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh Signal: 5 SourcePackage: metacity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XGetRequest () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XFixesCopyRegion () from /usr/lib/x86_64-linux-gnu/libXfixes.so.3 Title: metacity crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to vivid on 2015-09-05 (109 days ago) UserGroups: adm admin audio cdrom dialout libvirtd lpadmin plugdev pulse pulse-access sambashare vboxusers video ** Affects: metacity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace third-party-packages vivid ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1528896 Title: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout (#1507764 duplicate) Status in metacity package in Ubuntu: New Bug description: This is a duplicate of bug 1507764, but the bug reporting system would not let me find it for further addition. I am posting this in hopes that by crossing this trace and the previous one this might help developers find what is going on. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: metacity 1:3.14.3-1ubuntu7 ProcVersionSignature: Ubuntu 3.19.0-42.48-generic 3.19.8-ckt10 Uname: Linux 3.19.0-42-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Flashback:Unity Date: Thu Dec 24 01:49:05 2015 ExecutablePath: /usr/bin/metacity InstallationDate: Installed on 2010-01-30 (2153 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1) ProcCmdline: metacity ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh Signal: 5 SourcePackage: metacity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XGetRequest () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XFixesCopyRegion () from /usr/lib/x86_64-linux-gnu/libXfixes.so.3 Title: metacity crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to vivid on 2015-09-05 (109 days ago) UserGroups: adm admin audio cdrom dialout libvirtd lpadmin plugdev pulse pulse-access sambashare vboxusers video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1528896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1455916] Re: Xorg unexpectedly crashed
Maybe a duplicate of https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764 (or at least related ?) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1455916 Title: Xorg unexpectedly crashed Status in xorg package in Ubuntu: Confirmed Bug description: Xorg unexpectedly crashed bringing down down metacity and gnome-flashback too. This is the relevant section from the system logs: May 17 15:09:05 ultra-d gnome-session[1514]: Window manager warning: Log level 6: The program 'metacity' received an X Window System error. May 17 15:09:05 ultra-d gnome-session[1514]: This probably reflects a bug in the program. May 17 15:09:05 ultra-d gnome-session[1514]: The error was 'BadRegion (invalid Region parameter)'. May 17 15:09:05 ultra-d gnome-session[1514]: (Details: serial 508727326 error_code 140 request_code 138 (XFIXES) minor_code 12) May 17 15:09:05 ultra-d gnome-session[1514]: (Note to programmers: normally, X errors are reported asynchronously; May 17 15:09:05 ultra-d gnome-session[1514]: that is, you will receive the error a while after causing it. May 17 15:09:05 ultra-d gnome-session[1514]: To debug your program, run it with the GDK_SYNCHRONIZE environment May 17 15:09:05 ultra-d gnome-session[1514]: variable to change this behavior. You can then get a meaningful May 17 15:09:05 ultra-d gnome-session[1514]: backtrace from your debugger if you break on the gdk_x_error() function.) May 17 15:09:05 ultra-d kernel: [276368.790571] traps: metacity[1688] trap int3 ip:7fb31d5d9d00 sp:7ffc0f98c740 error:0 May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: WARNING: Child process 1688 was already dead. May 17 15:09:19 ultra-d gnome-session[1514]: WARNING: Child process 1688 was already dead. May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: WARNING: Application 'metacity.desktop' killed by signal 5 May 17 15:09:19 ultra-d gnome-session[1514]: WARNING: Application 'metacity.desktop' killed by signal 5 May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: WARNING: App 'metacity.desktop' respawning too quickly May 17 15:09:19 ultra-d gnome-session[1514]: WARNING: App 'metacity.desktop' respawning too quickly May 17 15:09:19 ultra-d gnome-session[1514]: Unrecoverable failure in required component metacity.desktop May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: CRITICAL: We failed, but the fail whale is dead. Sorry May 17 15:09:19 ultra-d gnome-session[1514]: CRITICAL: We failed, but the fail whale is dead. Sorry May 17 15:09:20 ultra-d gnome-session[1514]: ICE default IO error handler doing an exit(), pid = 17669, errno = 11 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity Date: Sun May 17 15:56:28 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.26, 3.19.0-15-generic, x86_64: installed virtualbox, 4.3.26, 3.19.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04ca] Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (rev ff) (prog-if ff) MachineType: Dell Inc. Inspiron N5110 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=/dev/mapper/system_vg-root_lv ro cryptdevice=/dev/sda2:system_crypt quiet splash vt.handoff=7 SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0FTJWD dmi.board.vendor: Dell Inc. dmi.board.version: A11 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/03/2012:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn0FTJWD:rvrA11:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron N5110 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core:
[Desktop-packages] [Bug 1507764] Re: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout
The crash is still happening no matter what I update. The fact it comes after somewhat intensive use (one week, two weeks of not rebooting) and when doing Alt+Tab repeatedly in succession hints maybe at memory leaks? Again, right before the crashes, artifacts of the application switcher windows remain, and application windows redraw gets flaky. Also, this looks strangely alike to : https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1455916 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1507764 Title: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout Status in metacity package in Ubuntu: New Bug description: This bug seemed to occur already since earlier versions of Ubuntu, and usually would just end up leaving me with undecorated windows, from which recovery was as easy as restarting metacity by hand, but in this release of Ubuntu (15.04), it seems gnome-session tries to restart it too many times in a too short span, and then decides arbitrarily that it failed so bad it has to kill the whole session. So, while the metacity bug is really a thing, my real problem actually might be a gnome-session-bin bug. I expect metacity crashing would not bring down the whole session, as is the case currently. At any rate, this is extremely annoying, I am hitting this bug about every two days, and because of it and the regression in crash handling, I end up losing all my windows and running programs. (In all fairness, I am suspecting a hardware issue, but the problem remains that a sub process dying should not cause the parent process to die like this) ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: metacity 1:3.14.3-1ubuntu7 ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Flashback:Unity Date: Tue Oct 20 05:19:37 2015 ExecutablePath: /usr/bin/metacity InstallationDate: Installed on 2010-01-30 (2088 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1) ProcCmdline: metacity ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh Signal: 5 SourcePackage: metacity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XGetRequest () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XFixesCopyRegion () from /usr/lib/x86_64-linux-gnu/libXfixes.so.3 Title: metacity crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to vivid on 2015-09-05 (44 days ago) UserGroups: adm admin audio cdrom dialout libvirtd lpadmin plugdev pulse pulse-access sambashare vboxusers video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1507764] Re: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout
It seems to crash when I switch windows (alt+tab ; even falling back to the static application switcher does not alleviate the bug). For reference, I do a lot of translation work, which requires me to have gedit, mplayer, evince running at the same time and heavily switching between these. (Especially mplayer/evince probably take a lot of memory). When metacity crashes, everything freezes while apport runs and writes its files, during which only the audio players and non graphical stuff keep running (if I am lucky I can SSH and force gedit to save my work), and once apport finishes, in a split second, every window just loses its decorations, and I am forced back to the login screen. Logs indeed indicate this : /var/log/syslog.1:Oct 20 05:22:14 archer gnome-session[29421]: WARNING: App 'metacity.desktop' respawning too quickly /var/log/syslog.1:Oct 20 05:22:14 archer gnome-session[29421]: gnome-session[29421]: WARNING: App 'metacity.desktop' respawning too quickly But I can't confirm with the bare eye that it tries to reload anything, or what the respawn threshold is. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1507764 Title: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout Status in metacity package in Ubuntu: New Bug description: This bug seemed to occur already since earlier versions of Ubuntu, and usually would just end up leaving me with undecorated windows, from which recovery was as easy as restarting metacity by hand, but in this release of Ubuntu (15.04), it seems gnome-session tries to restart it too many times in a too short span, and then decides arbitrarily that it failed so bad it has to kill the whole session. So, while the metacity bug is really a thing, my real problem actually might be a gnome-session-bin bug. I expect metacity crashing would not bring down the whole session, as is the case currently. At any rate, this is extremely annoying, I am hitting this bug about every two days, and because of it and the regression in crash handling, I end up losing all my windows and running programs. (In all fairness, I am suspecting a hardware issue, but the problem remains that a sub process dying should not cause the parent process to die like this) ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: metacity 1:3.14.3-1ubuntu7 ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Flashback:Unity Date: Tue Oct 20 05:19:37 2015 ExecutablePath: /usr/bin/metacity InstallationDate: Installed on 2010-01-30 (2088 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1) ProcCmdline: metacity ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh Signal: 5 SourcePackage: metacity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XGetRequest () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XFixesCopyRegion () from /usr/lib/x86_64-linux-gnu/libXfixes.so.3 Title: metacity crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to vivid on 2015-09-05 (44 days ago) UserGroups: adm admin audio cdrom dialout libvirtd lpadmin plugdev pulse pulse-access sambashare vboxusers video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1507764] Re: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout
Sorry, forgot to specify this : the Alt+Tab crash is indeed seemingly random. At one point after one day or two of running, Alt+Tab will start leaving refresh artifacts (parts of another window that I was browsing while switching) and eventually just outright freeze and crash. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1507764 Title: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout Status in metacity package in Ubuntu: New Bug description: This bug seemed to occur already since earlier versions of Ubuntu, and usually would just end up leaving me with undecorated windows, from which recovery was as easy as restarting metacity by hand, but in this release of Ubuntu (15.04), it seems gnome-session tries to restart it too many times in a too short span, and then decides arbitrarily that it failed so bad it has to kill the whole session. So, while the metacity bug is really a thing, my real problem actually might be a gnome-session-bin bug. I expect metacity crashing would not bring down the whole session, as is the case currently. At any rate, this is extremely annoying, I am hitting this bug about every two days, and because of it and the regression in crash handling, I end up losing all my windows and running programs. (In all fairness, I am suspecting a hardware issue, but the problem remains that a sub process dying should not cause the parent process to die like this) ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: metacity 1:3.14.3-1ubuntu7 ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Flashback:Unity Date: Tue Oct 20 05:19:37 2015 ExecutablePath: /usr/bin/metacity InstallationDate: Installed on 2010-01-30 (2088 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1) ProcCmdline: metacity ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh Signal: 5 SourcePackage: metacity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XGetRequest () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XFixesCopyRegion () from /usr/lib/x86_64-linux-gnu/libXfixes.so.3 Title: metacity crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to vivid on 2015-09-05 (44 days ago) UserGroups: adm admin audio cdrom dialout libvirtd lpadmin plugdev pulse pulse-access sambashare vboxusers video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1507764] Re: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1507764 Title: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout Status in metacity package in Ubuntu: New Bug description: This bug seemed to occur already since earlier versions of Ubuntu, and usually would just end up leaving me with undecorated windows, from which recovery was as easy as restarting metacity by hand, but in this release of Ubuntu (15.04), it seems gnome-session tries to restart it too many times in a too short span, and then decides arbitrarily that it failed so bad it has to kill the whole session. So, while the metacity bug is really a thing, my real problem actually might be a gnome-session-bin bug. I expect metacity crashing would not bring down the whole session, as is the case currently. At any rate, this is extremely annoying, I am hitting this bug about every two days, and because of it and the regression in crash handling, I end up losing all my windows and running programs. (In all fairness, I am suspecting a hardware issue, but the problem remains that a sub process dying should not cause the parent process to die like this) ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: metacity 1:3.14.3-1ubuntu7 ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Flashback:Unity Date: Tue Oct 20 05:19:37 2015 ExecutablePath: /usr/bin/metacity InstallationDate: Installed on 2010-01-30 (2088 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1) ProcCmdline: metacity ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh Signal: 5 SourcePackage: metacity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XGetRequest () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XFixesCopyRegion () from /usr/lib/x86_64-linux-gnu/libXfixes.so.3 Title: metacity crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to vivid on 2015-09-05 (44 days ago) UserGroups: adm admin audio cdrom dialout libvirtd lpadmin plugdev pulse pulse-access sambashare vboxusers video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1455916] Re: Xorg unexpectedly crashed
I also have confirmed the bug, it just happened right now, and here is the crash dump for metacity. It feels like gnome-session is trying to restart metacity too fast, when waiting a few seconds before respawning it would avoid this problem... ** Attachment added: "_usr_bin_metacity.1000.crash" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1455916/+attachment/4492163/+files/_usr_bin_metacity.1000.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1455916 Title: Xorg unexpectedly crashed Status in xorg package in Ubuntu: Confirmed Bug description: Xorg unexpectedly crashed bringing down down metacity and gnome-flashback too. This is the relevant section from the system logs: May 17 15:09:05 ultra-d gnome-session[1514]: Window manager warning: Log level 6: The program 'metacity' received an X Window System error. May 17 15:09:05 ultra-d gnome-session[1514]: This probably reflects a bug in the program. May 17 15:09:05 ultra-d gnome-session[1514]: The error was 'BadRegion (invalid Region parameter)'. May 17 15:09:05 ultra-d gnome-session[1514]: (Details: serial 508727326 error_code 140 request_code 138 (XFIXES) minor_code 12) May 17 15:09:05 ultra-d gnome-session[1514]: (Note to programmers: normally, X errors are reported asynchronously; May 17 15:09:05 ultra-d gnome-session[1514]: that is, you will receive the error a while after causing it. May 17 15:09:05 ultra-d gnome-session[1514]: To debug your program, run it with the GDK_SYNCHRONIZE environment May 17 15:09:05 ultra-d gnome-session[1514]: variable to change this behavior. You can then get a meaningful May 17 15:09:05 ultra-d gnome-session[1514]: backtrace from your debugger if you break on the gdk_x_error() function.) May 17 15:09:05 ultra-d kernel: [276368.790571] traps: metacity[1688] trap int3 ip:7fb31d5d9d00 sp:7ffc0f98c740 error:0 May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: WARNING: Child process 1688 was already dead. May 17 15:09:19 ultra-d gnome-session[1514]: WARNING: Child process 1688 was already dead. May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: WARNING: Application 'metacity.desktop' killed by signal 5 May 17 15:09:19 ultra-d gnome-session[1514]: WARNING: Application 'metacity.desktop' killed by signal 5 May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: WARNING: App 'metacity.desktop' respawning too quickly May 17 15:09:19 ultra-d gnome-session[1514]: WARNING: App 'metacity.desktop' respawning too quickly May 17 15:09:19 ultra-d gnome-session[1514]: Unrecoverable failure in required component metacity.desktop May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: CRITICAL: We failed, but the fail whale is dead. Sorry May 17 15:09:19 ultra-d gnome-session[1514]: CRITICAL: We failed, but the fail whale is dead. Sorry May 17 15:09:20 ultra-d gnome-session[1514]: ICE default IO error handler doing an exit(), pid = 17669, errno = 11 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity Date: Sun May 17 15:56:28 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.26, 3.19.0-15-generic, x86_64: installed virtualbox, 4.3.26, 3.19.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04ca] Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (rev ff) (prog-if ff) MachineType: Dell Inc. Inspiron N5110 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=/dev/mapper/system_vg-root_lv ro cryptdevice=/dev/sda2:system_crypt quiet splash vt.handoff=7 SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0FTJWD dmi.board.vendor: Dell Inc. dmi.board.version: A11 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/03/2012:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn0FTJWD:rvrA11:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron N5110 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz
