[Bug 2040453] Re: Gnome 45 crash on restart in X11 session [Window manager error: Another compositing manager is already running on screen 0 on display “:0”]
I tested this with the very small patch indicated in #1 and it worked. I did "apt-src install mutter" applied the patch.txt file with "patch -p1 < patch.txt" "apt-src build mutter" it fails all the tests but apparently this is expected, so i just went into the obj directory and did "sudo ninja install" and it replaced all the versions from the original .deb package. I logged out and back in, and then I was able to restart gnome-shell (alt+f2 and r) while I still had windows open. Their discussions about this issue seem to have gotten bogged down in minutiae of what other bugs are related, does some other bigger patch fix those bugs, no one tested it, etc. So I think it might be a good idea to carry this small patch for now, and hopefully by the time it starts conflicting it will no longer be necessary because it will be fixed some other way. :) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2040453 Title: Gnome 45 crash on restart in X11 session [Window manager error: Another compositing manager is already running on screen 0 on display “:0”] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2040453/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2040453] Re: Gnome 45 crash on restart in X11 session [Window manager error: Another compositing manager is already running on screen 0 on display “:0”]
This bug is definitely important to me, being able to restart GNOME Shell after it locks up, crashes, or updating an extension, _without_ losing any of my work or having to restart a large amount of open programs, is one of the main reasons I still run it on X11. Luckily I was testing 23.10 in a VM while working on porting an extension and so haven't updated my main machine yet. But I won't be doing that until this is fixed. There is a patch on their gitlab but they have to test it? It's relatively simple so we could all test a PPA with the change. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2040453 Title: Gnome 45 crash on restart in X11 session [Window manager error: Another compositing manager is already running on screen 0 on display “:0”] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2040453/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011251] Re: When focus-mode=mouse is set, gnome-shell gets into state where clicking on window title bars doesn't raise them
It looks like the gnome bug does acknowledge it only works for 'click' mode (I use sloppy) so presumably when that gets fixed (and it looks like they're still thinking about it!) and released then both mine and yours will too. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2011251 Title: When focus-mode=mouse is set, gnome-shell gets into state where clicking on window title bars doesn't raise them To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2011251/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020277] Re: Update gnome-shell to 44.1
Hmm... unfortunately upgrading (both gnome-shell and mutter) to 44.1 did not fix the main annoying bug for me where clicking titlebar doesn't raise the window anymore (on X at least) - #2013216. Also hitting the weird black bar issue that I didn't see under 44.0 https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/5857 so I am going to revert to 44.0 and this should probably wait until that is fixed (I think it might require a new GTK to be released too?) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2020277 Title: Update gnome-shell to 44.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2020277/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2013216] Re: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions)
Argh, click to raise doesn't get fixed for me with this. Maybe because I have focus follows mouse also? I still have to click inside the window somewhere to raise it. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2013216 Title: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2013216/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2007742] Re: Can't update stage views actor (regarding MetaWindowGroup, MetaWindowActorX11, MetaSurfaceActorX11)
I've seen this in my logs too, QUITE a lot in fact sudo journalctl --no-hostname --since "30 days ago" | grep "update stage views actor" | wc -l gives me back: 221915 But as far as I can tell it doesn't have any effect (GNOME 44.0 certainly has its problems but I was getting it in 43.x too and even before that and it's not causing hangs or crashes). Intel i915 kernel driver and modesetting with X11. The message is coming from gnome-shell, so I assume if you won't get it if you run a different DE - but are other DEs also unstable or are they fine? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2007742 Title: Can't update stage views actor (regarding MetaWindowGroup, MetaWindowActorX11, MetaSurfaceActorX11) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2007742/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2013216] Re: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions)
this should be fixed when ubuntu upgrades to gnome 44.1 which will hopefully be soon! memory leak bugs that were fixed are also affecting me (as well as this very annoying bug) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2013216 Title: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2013216/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983794] Re: Evolution not deleting autosave files
Thanks, uninstalling libcanberra-gtk-3-0 helped with this. (I'd only installed it way back in the distant past to stop those stupid warnings on the command line!) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1983794 Title: Evolution not deleting autosave files To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1983794/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1844809] Re: clicking desktop notifications to bring up linked up works intermittently in 19.10?
If it is related to that - you should do gsettings set org.gnome.desktop.wm.preferences focus-new-windows 'strict' (see https://major.io/2015/07/06/allow-new-windows-to-steal-focus-in-gnome-3/ ) I'm here because I type in notification bubbles themselves, and since gnome 3.34 these notifications do not have focus when I bring them up, I have to explicitly click inside them (which doesn't always work). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1844809 Title: clicking desktop notifications to bring up linked up works intermittently in 19.10? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844809/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1731053] Re: Update gnome-shell to 3.26.2
please accept into artful-updates. i can't install the dbgsym files to get a good backtrace for a bug until the dbgsym matches the version i have installed (and i don't want to upgrade to proposed right now). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1731053 Title: Update gnome-shell to 3.26.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1731053/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1676573] Re: gnome-shell restarts every 20 minutes because of SEGFAULT
It seems that various extensions can cause the problem. It would be great if there were some way for extensions to not be able to crash gnome-shell. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1676573 Title: gnome-shell restarts every 20 minutes because of SEGFAULT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1676573/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1664060] Re: Can't see view message pane in Evolution after most recent apt-get upgrade
I don't have the GNOME 3 staging PPA, and Zesty which we're running includes GTK 3.22. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1664060 Title: Can't see view message pane in Evolution after most recent apt-get upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1664060/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1664060] Re: Can't see view message pane in Evolution after most recent apt-get upgrade
The latest batch of updates today (which included libwebkit2gtk updates) fixed the Evolution message pane display problem for me, yay! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1664060 Title: Can't see view message pane in Evolution after most recent apt-get upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1664060/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1664060] Re: Can't see view message pane in Evolution after most recent apt-get upgrade
Switching to Thunderbird is exactly what I did. :) But unlike the Arch thread I don't have HiDPI enabled (scaling is 1 in gnome-tweak-tool for both fonts and windows section). Epiphany works for me also. Do you have HiDPI enabled? Does epiphany work for you? Also, for me evolution seems to display a message or two (even HTML messages) and then hangs at "Retrieving" (and this is for both of the accounts I have, one Gmail and one Exchange). I just want to confirm if this is the same bug or not, if not I'll open up a new one. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1664060 Title: Can't see view message pane in Evolution after most recent apt-get upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1664060/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1639942] Re: Update evolution to 3.22.3
I upgraded to zesty before I saw movement on this, but I can confirm that 3.22.3 in zesty fixes the problem I was experiencing with inline images. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1639942 Title: Update evolution to 3.22.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1639942/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1639942] Re: Update evolution to 3.22.2
I'd really like this too. The git_fix-reply-with-inline-images.patch that is already included in .1 is not working for me - I'm still experiencing that crash. I'm really hoping that 3.22.2 will fix it but I'd rather not upgrade to zesty to find that out. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1639942 Title: Update evolution to 3.22.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1639942/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1292282] Re: background transparency is not working on gnome terminal
bug still occurs on gnome 3.16 w/ gnome-terminal 3.16 transparency can be enabled by editing the profile preferences and changing the slider a bit my preferred fix is ... use Konsole :) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1292282 Title: background transparency is not working on gnome terminal To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1292282/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1061195] Re: Can't create EWS or MAPI account
I was experiencing this exact same bug as well. Based on information I read in the corresponding RedHat report (https://bugzilla.redhat.com/show_bug.cgi?id=879773) I was able to get this to work by removing all the Evolution configuration directories (which did have some prior attempts at configuration from a long time ago) and killing and restarting Evolution: [Fri Aug 8 10:02:25 EDT 2014] mike at ossy in ~ ↪ rm -rf .config/evolution/ .cache/evolution/ .local/share/evolution/ [Fri Aug 8 10:02:40 EDT 2014] mike at ossy in ~ ↪ pkill evolution I went through the account wizard again, and after adding the password prompt showed up and I was able to type the password and add the account. ** Bug watch added: Red Hat Bugzilla #879773 https://bugzilla.redhat.com/show_bug.cgi?id=879773 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1061195 Title: Can't create EWS or MAPI account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1061195/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1034574] Re: nautilus crashed with SIGSEGV - searching and typing / in the box
*** This bug is a duplicate of bug 1034548 *** https://bugs.launchpad.net/bugs/1034548 When I click on that I get Bug 1034548 cannot be found -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1034574 Title: nautilus crashed with SIGSEGV - searching and typing / in the box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1034574/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 805894] Re: gnome-settings-daemon crashed with signal 5 in xkl_process_error()
Sebastien - I'm pretty sure I was able to glean the information from stuff on the internet, but doing xinput list and seeing it there certainly confirmed it. Finding error messages in xkl functions also helped. Others say this isn't their issue though. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/805894 Title: gnome-settings-daemon crashed with signal 5 in xkl_process_error() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/805894/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
RE: [Bug 805894] Re: gnome-settings-daemon crashed with signal 5 inxkl_process_error()
Unfortunately yes, at least for me. In my case it definitely has to do with the fact that I have a USB hard disk reporting itself as a keyboard, this is confusing xklavier and causing gsd to crash. I run the command xinput --set-prop Western Digital My Book Device Enabled 0 in my .xstartup and start gsd manually and this fixes it for me but I don’t think for other people. Gsd needs to handle errors better from xklavier apparently. Sincerely, Michael Russo, Systems Engineer PaperSolve, Inc. 268 Watchogue Road Staten Island, NY 10314 Randomly generated quote of the last 5 minutes: Swipple's Rule of Order: He who shouts the loudest has the floor. -Original Message- From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of Pedro Villavicencio Sent: Friday, October 07, 2011 9:51 AM To: Mike Russo Subject: [Bug 805894] Re: gnome-settings-daemon crashed with signal 5 inxkl_process_error() Is this still reproducible with g-s-d 3.2? There's no duplicates with that version . Thanks. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/805894 Title: gnome-settings-daemon crashed with signal 5 in xkl_process_error() Status in “gnome-settings-daemon” package in Ubuntu: Incomplete Bug description: Here's a note I included in a similar bug (797947) that may help to diagnose as this might be a timing issue: I'd like to add that I can never get gnome-settings-daemon to start and stay running for more than 5 seconds, UNLESS i take the following actions, in which case it applies the themes properly and responds to theme changes and generally works just fine: 1. start 'strace gnome-settings-daemon' in a window 2. wait until the terminal appears to hang in the middle of the output 3. switch to a virtual console (ALT+F1) and login 4. pkill -9 strace 5. switch back to X - everything is fine! This works about 95% of the time. This is a laptop that always gets this error on boot up and only has one screen, no docking station, so its not anything related to screen size I should think. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: gnome-settings-daemon 3.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.0-2.3-generic 3.0.0-rc4 Uname: Linux 3.0-2-generic i686 Architecture: i386 Date: Sun Jul 3 10:35:32 2011 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Alpha i386 (20100602.2) ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gnome-settings-daemon StacktraceTop: ?? () from /usr/lib/libgdk-3.so.0 ?? () from /usr/lib/libgdk-3.so.0 xkl_process_error () from /usr/lib/libxklavier.so.16 _XError () from /usr/lib/i386-linux-gnu/libX11.so.6 ?? () from /usr/lib/i386-linux-gnu/libX11.so.6 Title: gnome-settings-daemon crashed with signal 5 in xkl_process_error() UpgradeStatus: Upgraded to oneiric on 2011-06-05 (29 days ago) UserGroups: adm admin cdrom dialout games libvirtd lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/805894/+subscriptions -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/805894 Title: gnome-settings-daemon crashed with signal 5 in xkl_process_error() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/805894/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 805894] Re: gnome-settings-daemon crashed with signal 5 in xkl_process_error()
Besides just removing the device, I can also do xinput --set-prop Western Digital My Book Device Enabled 0 every time X comes up and then re-start gnome-settings-daemon. I just wish it could handle this error so I didn't have to! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/805894 Title: gnome-settings-daemon crashed with signal 5 in xkl_process_error() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/805894/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
RE: [Bug 805894] Re: gnome-settings-daemon crashed with signal 5 inxkl_process_error()
In my case, I can reproduce it and I included the backtrace above yesterday. I have found the issue is because an external USB hard disk (a western digital MyBook 1TB Mirror edition, although other WD MyBook devices also seem to have the same problem) is announcing itself not only as a hard disk but also as an input device, confusing xklavier and then this crashes gnome-settings-daemon. Jared -- do you have the same issue? If you do xinput list do you see any devices that are not really input devices in that list? Sincerely, Michael Russo, Systems Engineer PaperSolve, Inc. 268 Watchogue Road Staten Island, NY 10314 Randomly generated quote of the last 5 minutes: Dijkstra probably hates me. -- Linus Torvalds, in kernel/sched.c -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/805894 Title: gnome-settings-daemon crashed with signal 5 in xkl_process_error() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/805894/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 805894] Re: gnome-settings-daemon crashed with signal 5 in xkl_process_error()
After reading more of a related RedHat bug (https://bugzilla.redhat.com/show_bug.cgi?id=657726) it would seem that these crashes are in fact due to some bad messages coming back from xklavier or xinput, and gnome-settings-daemon not being able to handle them. Here is a recent stack trace: mike@hawty:~$ gdb gnome-settings-daemon GNU gdb (Ubuntu/Linaro 7.3-0ubuntu2) 7.3-2011.08 Copyright (C) 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i686-linux-gnu. For bug reporting instructions, please see: http://bugs.launchpad.net/gdb-linaro/... Reading symbols from /usr/bin/gnome-settings-daemon...(no debugging symbols found)...done. (gdb) run Starting program: /usr/bin/gnome-settings-daemon [Thread debugging using libthread_db enabled] [New Thread 0xb7ddbb70 (LWP 3131)] [New Thread 0xb75dab70 (LWP 3132)] [New Thread 0xb6bffb70 (LWP 3133)] ** (gnome-settings-daemon:3128): WARNING **: Ignoring unknown module 'org.gnome.settings-daemon.plugins.ubuntuone' [New Thread 0xb63feb70 (LWP 3134)] [Thread 0xb75dab70 (LWP 3132) exited] [1316688537,000,xklavier.c:xkl_engine_start_listen/]The backend does not require manual layout management - but it is provided by the application Gdk-ERROR **: The program 'gnome-settings-daemon' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 846 error_code 8 request_code 141 minor_code 22) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Program received signal SIGTRAP, Trace/breakpoint trap. 0x00810e69 in g_logv () from /lib/i386-linux-gnu/libglib-2.0.so.0 (gdb) bt #0 0x00810e69 in g_logv () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0x008111a3 in g_log () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0x00a79ec9 in ?? () from /usr/lib/libgdk-3.so.0 #3 0x00a87c28 in ?? () from /usr/lib/libgdk-3.so.0 #4 0x0163d99a in xkl_process_error () from /usr/lib/libxklavier.so.16 #5 0x00b06d3b in _XError () from /usr/lib/i386-linux-gnu/libX11.so.6 #6 0x00b0390d in ?? () from /usr/lib/i386-linux-gnu/libX11.so.6 #7 0x00b048f7 in _XReply () from /usr/lib/i386-linux-gnu/libX11.so.6 #8 0x00ea8f3b in XGetFeedbackControl () from /usr/lib/i386-linux-gnu/libXi.so.6 #9 0x01845fcb in ?? () from /usr/lib/gnome-settings-daemon-3.0/libmouse.so #10 0x01847a6c in ?? () from /usr/lib/gnome-settings-daemon-3.0/libmouse.so #11 0x01847d77 in ?? () from /usr/lib/gnome-settings-daemon-3.0/libmouse.so #12 0x008041a0 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #13 0x008082ef in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 #14 0x00808a20 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #15 0x0080902b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0 #16 0x002a1795 in gtk_main () from /usr/lib/libgtk-3.so.0 #17 0x0804ad11 in main () (gdb) quit A debugging session is active. Inferior 1 [process 3128] will be killed. Quit anyway? (y or n) y Now let's list what xinput devices I have connected to my computer: mike@hawty:~$ xinput list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ HP HP USB Laser Mouse id=10 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Power Button id=7[slave keyboard (3)] ↳ daskeyboard id=8[slave keyboard (3)] ↳ daskeyboard id=9[slave keyboard (3)] ↳ Western Digital My Book id=11 [slave keyboard (3)] What the hell? An external USB hard disk is reporting that it is a keyboard What happens if I disconnect it, then run gnome-settings-daemon again? root@hawty:~# umount /media/MyBook (unplugged it) root@hawty:~# xinput list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ HP HP USB Laser Mouse id=10 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard
[Bug 797947] Re: gnome-settings-daemon crashes frequently with X protocol error
Since this is another crash related to xkl_ functions (xklavier) please see my note in bug 805894 - its possible we are seeing the same issue with xinput. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/797947 Title: gnome-settings-daemon crashes frequently with X protocol error To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/797947/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 797947] Re: gnome-settings-daemon crashes frequently with X protocol error
I'd like to add that I can never get gnome-settings-daemon to start and stay running for more than 5 seconds, UNLESS i take the following actions, in which case it applies the themes properly and responds to theme changes and generally works just fine: 1. start 'strace gnome-settings-daemon' in a window 2. wait until the terminal appears to hang in the middle of the output 3. switch to a virtual console (ALT+F1) and login 4. pkill -9 strace 5. switch back to X - everything is fine! This works about 95% of the time. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/797947 Title: gnome-settings-daemon crashes frequently with X protocol error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/797947/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 735727] Re: Nautilus gets stuck in infinite loop on startup
Looks like this was corrected in the latest nautilus/nautilus-data update in the gnome3 ppa (2.91.94). yay! :) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/735727 Title: Nautilus gets stuck in infinite loop on startup -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
