[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292041 Title: Lockscreen doesn't turn off the screen To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1292041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507764 Title: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/771272 Title: gnome-keyring doesn't support ecdsa or ed25519 keys To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/771272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637855 Title: Composite characters or Japanese input gets sometimes sent to the wrong terminal window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1637855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637823 Title: keyboard input is not processed in the right order during high CPU load times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1637823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637822 Title: autosave freezes editor and loses keystrokes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1637822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507764 Title: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1507764] Re: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout
It's hard to reproduce "at will". I personally run Firefox, Thunderbird, Chrome, gedit, gjiten, skype, pidgin, Gnome Terminal, and always have something like 20 windows open at a time on my main workspace. Of note : - When alt tabbing between windows, sometimes surfaces flash to black for one instant before redraw happens. This might indicate that the core problem with metacity crashing in the first place is linked to Xorg or the nvidia driver ? - Also, with previous versions of Ubuntu, I did have metacity crash on me at times, but the session would keep on running, so I could relaunch metacity from an open terminal (or via console using : DISPLAY=:0.0 metacity ) ; The crash itself is not a problem, gnome-sessions's extremely poor handling of it is. The easiest way for me to produce this crash is to edit text in gedit, open a PDF in evince, and spend my time alt tabbing between them (which happens quite a lot as I am doing translation work). At one point, I'll start seeing redrawing artifacts (to explain : even though I switched applications, the display still shows a black surface, or the application which was on top of gedit at that time, and I have to interact with the application for redraw to occur. When I see this symptom, I know that within the next 50~100 window switchings, I will crash. The crash can even be triggered by clicking the window tab on the application bar. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507764 Title: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507764 Title: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507764 Title: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507764 Title: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1455916 Title: Xorg unexpectedly crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1455916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1528896 Title: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout (#1507764 duplicate) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1528896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1455916 Title: Xorg unexpectedly crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1455916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507764 Title: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507764 Title: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507764 Title: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507764 Title: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1455916 Title: Xorg unexpectedly crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1455916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 364101] Re: network-manager-openvpn does not support all options supported by openvpn
I would like to propose the following patch to handle the options in the configuration file (just tested it right now, and it does the job) [vpn] ... ping=10 ping-restart=60 As one can see, the process spawned has the proper arguments : $ ps auxw | grep vpn root 3752 0.0 0.0 28444 2728 ?S22:16 0:00 /usr/sbin/openvpn --remote ... --nobind --dev tun --proto udp --port 1194 --auth-nocache --ping-restart 60 --ping 10 --syslog nm-openvpn --script-security 2 --up /usr/lib/NetworkManager/nm-openvpn-service-openvpn-helper --up-restart --persist-key --persist-tun --management 127.0.0.1 1194 --management-query-passwords --route-noexec --ifconfig-noexec --secret ... --ifconfig 192.168.100.2 192.168.100.1 This alone of course won't fix the UI, but it's a start. ** Attachment added: Adds --ping and --ping-restart https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/364101/+attachment/4435168/+files/support-ping-options -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/364101 Title: network-manager-openvpn does not support all options supported by openvpn To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-openvpn/+bug/364101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 250549] Re: Wrong interface speed from snmpd running as snmp user
Also confirming this problem. This is really ANNOYING with a full network of Ubuntu machines, there is no proper way of monitoring the network interface information, screwing up about every NMS you can find in the book. Any further input, help, or attention would be much appreciated. -- Wrong interface speed from snmpd running as snmp user https://bugs.launchpad.net/bugs/250549 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to net-snmp in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 250549] Re: Wrong interface speed from snmpd running as snmp user
Also confirming this problem. This is really ANNOYING with a full network of Ubuntu machines, there is no proper way of monitoring the network interface information, screwing up about every NMS you can find in the book. Any further input, help, or attention would be much appreciated. -- Wrong interface speed from snmpd running as snmp user https://bugs.launchpad.net/bugs/250549 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 353396] [NEW] hald crashes on startup upon checking md device
Public bug reported: Binary package hint: hal In Jaunty Jackalope, hald crashed at boot time (and other daemons depending on hald didn't start). Following the instructions from man hald, running a gdb hald with options --daemon=no --verbose=yes has hald crash at this point : 04:34:26.151 [I] blockdev.c:904: block_add: sysfs_path=/sys/devices/virtual/block/md0/md0p1 dev=/dev/md0p1 is_part=1, parent=0x 04:34:26.152 [I] blockdev.c:916: Handling /dev/md0p1 as MD device Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7ff13ab036f0 (LWP 4921)] 0x00435845 in ?? () (gdb) bt #0 0x00435845 in ?? () #1 0x00425aa2 in ?? () #2 0x00425ef8 in hotplug_event_process_queue () #3 0x00426908 in ?? () #4 0x0042704e in ?? () #5 0x004234e5 in ?? () #6 0x0040b727 in ?? () #7 0x0040bbe4 in ?? () #8 0x7ff139faca6a in ?? () from /lib/libdbus-1.so.3 #9 0x7ff139fad671 in dbus_connection_dispatch () from /lib/libdbus-1.so.3 #10 0x7ff13a6f0b55 in ?? () from /usr/lib/libdbus-glib-1.so.2 #11 0x7ff13a2160ca in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #12 0x7ff13a2197a0 in ?? () from /usr/lib/libglib-2.0.so.0 #13 0x7ff13a219c6d in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #14 0x00413e95 in ?? () #15 0x7ff1397ad5a6 in __libc_start_main () from /lib/libc.so.6 #16 0x00408129 in ?? () #17 0x7fff42b27428 in ?? () #18 0x001c in ?? () #19 0x0003 in ?? () #20 0x7fff42b28b49 in ?? () #21 0x7fff42b28b58 in ?? () #22 0x7fff42b28b64 in ?? () #23 0x in ?? () There are also messages for other pids killed in the process. A normal run also pops lots of these messages : error: libhal_ctx_init_direct md0 is a RAID mirror device using two whole disks, and with partitions inside it. It seems that it can't get the parent device record, md0 and that it is bailing out because of that. This doesn't sound like normal behaviour to me... hal not working is quite problematic for me as I need to use pcscd which depends on hal. Is there a way to prevent it from polling MD devices ? Below are the package versions I use : dpkg -l | grep hal ii hal0.5.12~rc1+git20090204-0ubuntu4 Hardware Abstraction Layer ii hal-info 20090324-0ubuntu1 Hardware Abstraction Layer - fdi files ii libhal-storage10.5.12~rc1+git20090204-0ubuntu4 Hardware Abstraction Layer - shared library ii libhal10.5.12~rc1+git20090204-0ubuntu4 Hardware Abstraction Layer - shared library hal: Installed: 0.5.12~rc1+git20090204-0ubuntu4 Candidate: 0.5.12~rc1+git20090204-0ubuntu4 Version table: *** 0.5.12~rc1+git20090204-0ubuntu4 0 500 http://jp.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status hal-info: Installed: 20090324-0ubuntu1 Candidate: 20090324-0ubuntu1 Version table: *** 20090324-0ubuntu1 0 500 http://jp.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status libhal1: Installed: 0.5.12~rc1+git20090204-0ubuntu4 Candidate: 0.5.12~rc1+git20090204-0ubuntu4 Version table: *** 0.5.12~rc1+git20090204-0ubuntu4 0 500 http://jp.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status libhal-storage1: Installed: 0.5.12~rc1+git20090204-0ubuntu4 Candidate: 0.5.12~rc1+git20090204-0ubuntu4 Version table: *** 0.5.12~rc1+git20090204-0ubuntu4 0 500 http://jp.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status ** Affects: hal (Ubuntu) Importance: Undecided Status: New ** Description changed: Binary package hint: hal In Jaunty Jackalope, hald crashed at boot time (and other daemons depending on hald didn't start). Following the instructions from man hald, running a gdb hald with options --daemon=no --verbose=yes has hald crash at this point : 04:34:26.151 [I] blockdev.c:904: block_add: sysfs_path=/sys/devices/virtual/block/md0/md0p1 dev=/dev/md0p1 is_part=1, parent=0x 04:34:26.152 [I] blockdev.c:916: Handling /dev/md0p1 as MD device Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7ff13ab036f0 (LWP 4921)] 0x00435845 in ?? () (gdb) bt #0 0x00435845 in ?? () #1 0x00425aa2 in ?? () #2 0x00425ef8 in hotplug_event_process_queue () #3 0x00426908 in ?? () #4 0x0042704e in ?? () #5 0x004234e5 in ?? () #6 0x0040b727 in ?? () #7 0x0040bbe4 in ?? () #8 0x7ff139faca6a in ?? () from /lib/libdbus-1.so.3 #9 0x7ff139fad671 in dbus_connection_dispatch () from /lib/libdbus-1.so.3 #10 0x7ff13a6f0b55 in ?? () from /usr/lib/libdbus-glib-1.so.2 #11
[Bug 237443] Re: Crash during playback with CPU time limit error
Also occurs for me even on Ubuntu Intrepid. pulseaudio is 0.9.10-2ubuntu9, alsa is 1.0.17.dfsg-2ubuntu1, running on kernel 2.6.27-7-generic on a x86_64 machine. It seems to occur when I have a paused amarok, and a paused mplayer and pops randomly. I keep a running terminal with the command pulseaudio --log- target=syslog and only get : Soft CPU time limit exhausted, terminating. Hard CPU time limit exhausted, terminating forcibly. -- Crash during playback with CPU time limit error https://bugs.launchpad.net/bugs/237443 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
