[Bug 1803319] Re: GNOME Shell task bar menus not updated with external monitor primary and laptop screen fractionally scaled
Seemed to work when I tested it yesterday (I do not always have access to the test set-up). So assuming fixed. Thank you. -- 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/1803319 Title: GNOME Shell task bar menus not updated with external monitor primary and laptop screen fractionally scaled To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1803319/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1803319] Re: GNOME Shell task bar menus not updated with external monitor primary and laptop screen fractionally scaled
Sounds reasonable. Thanks for letting me know. -- 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/1803319 Title: GNOME Shell task bar menus not updated with external monitor primary and laptop screen fractionally scaled To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1803319/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1803319] Re: GNOME Shell task bar menus not updated with external monitor primary and laptop screen fractionally scaled
Please let me know when there Ubuntu packages I can test. I have upgraded to 19.04. -- 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/1803319 Title: GNOME Shell task bar menus not updated with external monitor primary and laptop screen fractionally scaled To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1803319/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1803319] [NEW] GNOME Shell task bar menus not updated with external monitor primary and laptop screen fractionally scaled
Public bug reported: My set-up: a laptop with an internal screen open and scaled to 150% and an external monitor at 100% set to act as the primary screen. When I open the menus in the GNOME Shell task bar (calendar or settings/log- out/etc menu) they are displayed but not updated when I mouse over them or click on them. I can still use them by blind clicking. When I set both screens to 100% I did not see this. I am using the Wayland session. With the internal screen at 125% I saw this too, but after changing the relative position of the two it went away. I think this was a fluke, but I was unable to do the same after going back to 150%. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CasperVersion: 1.399 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 14 11:23:54 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-06-12 (154 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-10-08 (37 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic third-party-packages wayland-session -- 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/1803319 Title: GNOME Shell task bar menus not updated with external monitor primary and laptop screen fractionally scaled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803319/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1723045] Re: GNOME Terminal does not get into GNOME Shell's frequently used list
After rebooting into 18.10 this morning this seemed to work. I will assume it is fixed, close the bug and re-open it if necessary. ** Changed in: gnome-shell (Ubuntu) Status: New => Fix Released -- 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/1723045 Title: GNOME Terminal does not get into GNOME Shell's frequently used list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723045/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792000] [NEW] VirtualBox icon does not show un dock until screen locks
Public bug reported: Quite simple: I start VirtualBox or a virtual machine straight from the build directory (without installing) and the icon in the dock is a red, crossed-out circle. After deliberately or due to a timeout locking the screen and unlocking it, the correct X11 property icon is shown. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 11 20:32:51 2018 InstallationDate: Installed on 2018-06-12 (91 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1792000 Title: VirtualBox icon does not show un dock until screen locks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1792000/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722725] Re: GNOME Shell disabling wrong screen when docking laptop
Even though 3.28 is due out after the Bionic feature freeze? What about X.Org 1.20, which is due out a few days later? -- 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/1722725 Title: GNOME Shell disabling wrong screen when docking laptop To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1722725/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722725] Re: GNOME Shell disabling wrong screen when docking laptop
Do you expect 3.26.3 to end up in Bionic? If not, would it be possible to back-port the fix? -- 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/1722725 Title: GNOME Shell disabling wrong screen when docking laptop To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1722725/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722725] Re: GNOME Shell disabling wrong screen when docking laptop
The patches are attached to gnome-bugs #788915. -- 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/1722725 Title: GNOME Shell disabling wrong screen when docking laptop To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1722725/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722725] Re: GNOME Shell disabling wrong screen when docking laptop
Would it be possible to apply the upstream patches to the version in Bionic? I am happy to install the updated packages before they hit the repositories. -- 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/1722725 Title: GNOME Shell disabling wrong screen when docking laptop To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1722725/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724259] Re: gnome-shell frozen and using 100% CPU after docking and display configuration change
I am currently running version 1.8.4-0ubuntu0.17.10.1 of both packages and have not seen this problem for a while. I have rebooted several times since installing the packages. Off-topic, but since yesterday (can't remember it happening earlier) I have started seeing mouse button freezes after suspend and resume, affecting clients. Most windows can still be dragged, and the dock responds to mouse buttons, but e.g. the terminal, Firefox and Thunderbird respond to keyboard but not mouse. I can raise the windows using the dock. Would you happen to know of any matching open bug for that, or anything else? -- 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/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1724259/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724259] Re: gnome-shell frozen and using 100% CPU after docking and display configuration change
I must admit that I have not seen this freeze for a while (unless I just missed it among all the swap-to-death freezes I have had recently), but I installed the packages. I did not enable proposed, I just manually installed libinput-bin and libinput10, versions 1.8.4. I probably can't give any meaningful feedback until after my next reboot though. -- 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/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1724259/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1505409] Re: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"]
At least in my case, I think that the sensible approach is to make wayland-server treat requests for deleted objects non-fatal, as suggested by Pekka Paalanan in the blog post linked to above. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1505409 Title: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1505409/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1505409] Re: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"]
Just for the sake of adding a comment too... I am getting this in the following situation. I hope the description is correct. 1) I change the display set-up on my laptop slightly too fast, e.g. close the lid, re-open, re-close (I did that quite a bit recently trying to work out bug patterns). 2) GNOME Shell creates a wl_output object for the internal screen, reports it to Xwayland, then removes it again because the screen is disabled again. 3) Xwayland asks GNOME Shell for more information about the no-longer-existing wl_output object and GNOME Shell (in the Wayland library code) terminates the connection because it considers asking about a non-existing object to be a bug. 4) Xwayland dutifully terminates and GNOME Shell panics and terminates too. See: https://phabricator.freedesktop.org/T7722 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1505409 Title: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1505409/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724259] Re: gnome-shell frozen and using 100% CPU after docking and display configuration change
Or a third hypothesis: systemd-logind triggers a suspend on lid close if there is no external monitor plugged in. Perhaps it looks for a while too long like there is no monitor, so that systemd-logind suspends the system and the GNOME Shell wayland output object disappears, causing the xwayland error. -- 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/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724259] Re: gnome-shell frozen and using 100% CPU after docking and display configuration change
Not succeeded in reproducing this again after rebuilding GNOME Shell with ASAN_OPTIONS=detect_leaks=0 CFLAGS="-fsanitize=address -fsanitize=return -fsanitize=bounds -fsanitize=object-size". I do now manage to trigger debian bug 823216 quite reliably now, with the difference that I can log on again immediately. It is usually the user GNOME Shell and XWayland which crash, but at least once the gdm ones crashed. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823216 I trigger this by opening a few applications (Firefox with a few windows seems to make it easier to reproduce) and repeatedly opening and closing the laptop lid. It seems that, as per systemd logind settings this should not trigger a suspend when docked, but occasionally it does. The xwayland termination happens just before this (as observed from an ssh session on my other laptop: I can see the results just before the session stops responding due to the suspension). ** Bug watch added: Debian Bug tracker #823216 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823216 -- 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/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724259] Re: gnome-shell frozen and using 100% CPU after docking and display configuration change
Thinking of it I might be confusing cause and effect here: the unexpected suspend might be caused somehow by the xwayland and gnome- shell crash. -- 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/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724259] Re: gnome-shell frozen and using 100% CPU after docking and display configuration change
>From the other bug (this is getting a bit tiring): I was able to trigger the crash pretty easily with the old library still in use by opening and closing the lid a few times in quick succession and then trying to type an update to this bug. After restarting I was not immediately able to trigger it, but instead brought gnome-shell down with an assertion (g_malloc failed to allocate 1.8x10^19 bytes). Working down the stack a few frames it looked like it was trying to use an invalid structure, presumably in memory which had already been freed. Which at least raises the possibility that gnome-shell has some memory use bug which triggers on suspend and resume and that libinput was collateral damage. I am thinking of rebuilding gnome-shell with memory debugging enabled. -- 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/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724259] Re: gnome-shell frozen and using 100% CPU after docking and display configuration change
I have rebuilt libinput10 with the patch in that freedesktop.org bug report and will see if that helps things before trying to submit anything to launchpad. -- 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/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724259] Re: gnome-shell frozen and using 100% CPU after docking and display configuration change
I installed debug symbols for libinput and had a look at the core file, and it looks very much like this: https://bugs.freedesktop.org/show_bug.cgi?id=103298 I am missing the top frame in that stack trace, but I am guessing that is just chance based on when I took the trace. The description of how to trigger it looks like it could apply too. In any case, here is my trace: (gdb) bt #0 0x7f6b37a2ccc7 in post_device_event (device=device@entry=0x56373d197e80, time=time@entry=1377003141, type=type@entry= LIBINPUT_EVENT_KEYBOARD_KEY, event=0x56373e972770) at libinput.c:2312 #1 0x7f6b37a2df5f in keyboard_notify_key (device=device@entry=0x56373d197e80, time=time@entry=1377003141, key=, state=) at libinput.c:2412 #2 0x7f6b37a30ab7 in fallback_keyboard_notify_key (device=device@entry=0x56373d197e80, time=time@entry=1377003141, key=, state=, dispatch=) at evdev.c:173 #3 0x7f6b37a339b3 in fallback_process_key (e=0x7ffe3b444aa0, e=0x7ffe3b444aa0, time=1377003141, device=0x56373d197e80, dispatch=) at evdev.c:969 #4 0x7f6b37a339b3 in fallback_process (evdev_dispatch=, device=0x56373d197e80, event=0x7ffe3b444aa0, time=1377003141) at evdev.c:1301 #5 0x7f6b37a31159 in evdev_process_event (e=0x7ffe3b444aa0, device=0x56373d197e80) at evdev.c:2052 #6 0x7f6b37a31159 in evdev_device_dispatch_one (ev=0x7ffe3b444aa0, device=0x56373d197e80) at evdev.c:2060 #7 0x7f6b37a31159 in evdev_device_dispatch (data=0x56373d197e80) at evdev.c:2119 #8 0x7f6b37a2cdaf in libinput_dispatch (libinput=0x56373d123d60) at libinput.c:2196 #9 0x7f6b4113be9c in () ---Type to continue, or q to quit--- at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.so #10 0x7f6b424c2fb7 in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7f6b424c31f0 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7f6b424c3502 in g_main_loop_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7f6b409f868c in meta_run () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 #14 0x56373c9ec2e7 in () #15 0x7f6b4038a1c1 in __libc_start_main (main= 0x56373c9ebef0, argc=1, argv=0x7ffe3b444f78, init=, fini=, rtld_fini=, stack_end=0x7ffe3b444f68) at ../csu/libc-start.c:308 #16 0x56373c9ec3fa in () I will not fiddle around trying to properly upload the apport report just now, but I will keep it around locally. ** Bug watch added: freedesktop.org Bugzilla #103298 https://bugs.freedesktop.org/show_bug.cgi?id=103298 -- 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/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724259] Re: gnome-shell frozen and using 100% CPU after docking and display configuration change
That won't fix the outdated packages (one of them was curl...) though, will it? And does disabled mean that Launchpad will refuse to accept the upload even if my system tries to send it? -- 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/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724259] Re: gnome-shell frozen and using 100% CPU after docking and display configuration change
I checked and it was the main thread which was using CPU. Uploading a crash report (Apport would not submit it due to a couple of outdated packages). Note that this is on a different system with a fresh Ubuntu 17.10 install (not upgraded; but the report should tell you all that). ** Attachment added: "crash.zip" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+attachment/4996103/+files/crash.zip -- 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/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724259] Re: gnome-shell frozen and using 100% CPU after docking and display configuration change
Thank you. I assume then that my failure to get a crash report was due to the GNOME Shell process and not to the underlying mechanism. I will just check the GNOME Shell/Mutter/whatever source next time beforehand. -- 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/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724259] Re: gnome-shell frozen and using 100% CPU after docking and display configuration change
I will do that next time I see this. A question: is there a signal I can send to the process (SEGV?) to trigger an Apport bug report in /var/crash? And would that make things easier for you? -- 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/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724259] Re: gnome-shell frozen and using 100% CPU after docking and display configuration change
Here is a gdb stacktrace. I tried sending signal 3 to the process in the hope that it would trigger an apport bug report, but it did not. ** Attachment added: "gdb.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+attachment/4991557/+files/gdb.txt -- 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/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722725] Re: GNOME Shell disabling wrong screen when docking laptop
I have definitely observed bug 1716160 as well, even after correcting the GNOME settings (though it happens less often then). However this does not match either of the two. I still do not have a good feeling for exactly when it happens, so if you do not mind I will just update the bug next time it triggers with an unstructured chronology of what happened before. It might be related to bug 1723025, but I can't say for sure. -- 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/1722725 Title: GNOME Shell disabling wrong screen when docking laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722725/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1726020] [NEW] apport will not process report in /var/crash
Public bug reported: I have an 11K crash report in /var/crash, which Apport refuses to process due to a lack of "free memory to automatically analyze the problem and send a report to the developers". So I am attaching it here in case it is of interest. At least the question of why Apport has so much trouble of it might be interesting. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: udev 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 60-vboxdrv.rules Date: Sun Oct 22 16:11:44 2017 InstallationDate: Installed on 2016-05-31 (509 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Latitude E6420 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-10-05 (17 days ago) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A21 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA21:bd11/14/2013:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1726020 Title: apport will not process report in /var/crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1726020/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724886] Re: gnome-shell assert failure: gnome-shell: libinput.c:2157: assertion failed: libinput_device_destroy: list_empty(>event_listeners)
** Summary changed: - gnome-shell assert failure: gnome-shell: libinput.c:2157: libinput_device_destroy: list_empty(>event_listeners) + gnome-shell assert failure: gnome-shell: libinput.c:2157: assertion failed: libinput_device_destroy: list_empty(>event_listeners) -- 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/1724886 Title: gnome-shell assert failure: gnome-shell: libinput.c:2157: assertion failed: libinput_device_destroy: list_empty(>event_listeners) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724259] Re: System freeze after docking and display configuration change
Looking at the journald error log, the problem happened after Okt 17 15:27:08. I hoped that apport would take a stack trace of the gnome- shell process, but I will probably have to do that myself when I get the chance. Can you retrace a stack trace if the debug packages are not installed? -- 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/1724259 Title: System freeze after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724259] [NEW] System freeze after docking and display configuration change
Public bug reported: I have been having regular system freezes after switching from using my laptop stand-alone to waking it up on a docking station with an external monitor. I have seen this using two identical docking station plus monitor combinations. I am still trying to find a pattern. I was able to ssh in and use apport to save this bug information. The gnome-shell process was hung at 100% CPU utilisation. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 15:56:34 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'command-history' b"['gnome-terminal']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (504 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-05 (12 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- 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/1724259 Title: System freeze after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1723045] [NEW] GNOME Terminal does not get into GNOME Shell's frequently used list
Public bug reported: I use GNOME Terminal frequently. I tend (at least since I upgraded) to start it from GNOME Shell's dash, using the "all applications" category. For some reason it never makes it to the frequently used list. If it is of interest: $ grep terminal .local/share/gnome-shell/application_state I wonder whether the fact that my desktop is mainly Russian localised (the main folder names are in English) is related, but my guess is that it is not. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 11:12:37 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (498 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-05 (7 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- 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/1723045 Title: GNOME Terminal does not get into GNOME Shell's frequently used list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723045/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722725] [NEW] GNOME Shell disabling wrong screen when docking laptop
Public bug reported: I often switch between working with a docking station, closed laptop and an external monitor, and an open laptop without docking station or monitor. I noticed since updating to 17.10 that GNOME Shell would not switch correctly from the setup where the laptop was being used open without a docking station to the other. When I opened the laptop in the docking station the external monitor would come on, and when I closed the laptop it went off again. I manually switched the primary screen to be the external one and that solved it for now, so I assume that GNOME Shell was disabling the external screen instead of the internal one (it is a bit hard to see, and I have not yet tried ssh-ing in). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 11 09:06:34 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (497 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-05 (6 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- 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/1722725 Title: GNOME Shell disabling wrong screen when docking laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722725/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721718] Re: Segmentation fault in meta_monitor_mode_get_resolution
Update: I see that there are files in /var/crash, but they are all from October 5. I will try deleting the GNOME Shell one and see if a new one is created if another crash happens. -- 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/1721718 Title: Segmentation fault in meta_monitor_mode_get_resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1721718/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721718] Re: Segmentation fault in meta_monitor_mode_get_resolution
I saw something similar again today. Hard to say how similar. For some reason Apport does not seem to be doing the automatic reporting, though it looked like it was set up at a quick glance. I will try catching it myself. -- 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/1721718 Title: Segmentation fault in meta_monitor_mode_get_resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1721718/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721718] Re: Segmentation fault in meta_monitor_mode_get_resolution
I overcame my laziness and restarted everything. I was just able to reconfigure monitors without a crash, so assume this is fixed. I can always re-open if really necessary. Thanks. ** Changed in: mutter (Ubuntu) Status: Incomplete => Fix Released -- 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/1721718 Title: Segmentation fault in meta_monitor_mode_get_resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1721718/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721718] Re: Segmentation fault in meta_monitor_mode_get_resolution
Gianfranco suggested off-Launchpad that I test the most recent version of libmutter (3.26.1), as it looks from the source as though this issue is fixed there. I will report back in a few days (I generally suspend and resume without restarting my session, so it will be a while until I start using the new library). Until then and unless I see otherwise let's assume that 3.26.1 fixes this. -- 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/1721718 Title: Segmentation fault in meta_monitor_mode_get_resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1721718/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721718] Re: Segmentation fault in meta_monitor_mode_get_resolution
Quick fix below. For reasons of time I have done no testing beyond that GNOME Shell no longer crashes with the patch below. I have not tested the effect on scaling settings. ** Patch added: "mutter.patch" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1721718/+attachment/4963800/+files/mutter.patch -- 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/1721718 Title: Segmentation fault in meta_monitor_mode_get_resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1721718/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721718] Re: Segmentation fault in meta_monitor_mode_get_resolution
Second try with debug symbols for glib2.0 and libmutter. Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault. meta_monitor_mode_get_resolution (monitor_mode=monitor_mode@entry=0x0, width=width@entry=0x7fff256d5ad8, height=height@entry=0x7fff256d5adc) at backends/meta-monitor.c:1582 1582backends/meta-monitor.c: Нет такого файла или каталога. (gdb) bt #0 0x7f3df4941f50 in meta_monitor_mode_get_resolution (monitor_mode=monitor_mode@entry=0x0, width=width@entry=0x7fff256d5ad8, height=height@entry=0x7fff256d5adc) at backends/meta-monitor.c:1582 #1 0x7f3df4941fd2 in calculate_scale (monitor_mode=0x0, monitor=0x55c462ebd040 [MetaMonitorNormal]) at backends/meta-monitor.c:1377 #2 0x7f3df4941fd2 in meta_monitor_calculate_mode_scale (monitor=monitor@entry=0x55c462ebd040 [MetaMonitorNormal], monitor_mode=0x0) at backends/meta-monitor.c:1439 #3 0x7f3df493e437 in meta_finish_monitors_config_migration (monitor_manager=monitor_manager@entry=0x55c462af81b0 [MetaMonitorManagerKms], config=config@entry=0x7f3dd0019750 [MetaMonitorsConfig], error=error@entry=0x7fff256d5b60) at backends/meta-monitor-config-migration.c:1177 #4 0x7f3df493b8fe in meta_monitor_config_manager_get_stored (config_manager=0x7f3dd0005f20 [MetaMonitorConfigManager]) at backends/meta-monitor-config-manager.c:385 #5 0x7f3df4943732 in meta_monitor_manager_ensure_configured (manager=0x55c462af81b0 [MetaMonitorManagerKms]) at backends/meta-monitor-manager.c:487 #9 0x7f3df6733f4f in (instance=instance@entry=0x7f3dd000cb70, signal_id=, detail=) at ../../../../gobject/gsignal.c:3447 #6 0x7f3df6717f9d in g_closure_invoke (closure=0x55c462ecde10, return_value=0x0, n_param_values=2, param_values=0x7fff256d5dc0, invocation_hint=0x7fff256d5d40) at ../../../../gobject/gclosure.c:804 ---Type to continue, or q to quit--- #7 0x7f3df672ad5e in signal_emit_unlocked_R (node=node@entry=0x55c462ae0060, detail=detail@entry=302, instance=instance@entry=0x7f3dd000cb70, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fff256d5dc0) at ../../../../gobject/gsignal.c:3635 #8 0x7f3df6733535 in g_signal_emit_valist (instance=0x7f3dd000cb70, signal_id=, detail=302, var_args=var_args@entry=0x7fff256d5f90) at ../../../../gobject/gsignal.c:3391 #10 0x7f3df671c464 in g_object_dispatch_properties_changed (object=0x7f3dd000cb70 [UpClient], n_pspecs=, pspecs=) at ../../../../gobject/gobject.c:1064 #11 0x7f3df671e8b9 in g_object_notify_by_spec_internal (pspec=0x55c462b1c830 [GParamBoolean], object=0x7f3dd000cb70 [UpClient]) at ../../../../gobject/gobject.c:1157 #12 0x7f3df671e8b9 in g_object_notify (object=0x7f3dd000cb70 [UpClient], property_name=0x55c462ad20ff "lid-is-closed") at ../../../../gobject/gobject.c:1205 #16 0x7f3df6733f4f in (instance=instance@entry=0x55c462ae9580, signal_id=, detail=) at ../../../../gobject/gsignal.c:3447 #13 0x7f3df6717f9d in g_closure_invoke (closure=0x55c462ecdbd0, return_value=0x0, n_param_values=2, param_values=0x7fff256d62a0, invocation_hint=0x7fff256d6220) at ../../../../gobject/gclosure.c:804 ---Type to continue, or q to quit--- #14 0x7f3df672ad5e in signal_emit_unlocked_R (node=node@entry=0x55c462ae0060, detail=detail@entry=302, instance=instance@entry=0x55c462ae9580, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fff256d62a0) at ../../../../gobject/gsignal.c:3635 #15 0x7f3df6733535 in g_signal_emit_valist (instance=0x55c462ae9580, signal_id=, detail=302, var_args=var_args@entry=0x7fff256d6470) at ../../../../gobject/gsignal.c:3391 #17 0x7f3df671c464 in g_object_dispatch_properties_changed (object=0x55c462ae9580 [UpExportedDaemonProxy], n_pspecs=, pspecs=) at ../../../../gobject/gobject.c:1064 #18 0x7f3df671e8b9 in g_object_notify_by_spec_internal (pspec=0x55c462b0fc40 [GParamOverride], object=0x55c462ae9580 [UpExportedDaemonProxy]) at ../../../../gobject/gobject.c:1157 #19 0x7f3df671e8b9 in g_object_notify (object=0x55c462ae9580 [UpExportedDaemonProxy], property_name=0x7f3deb10b5cd "lid-is-closed") at ../../../../gobject/gobject.c:1205 #20 0x7f3deb100bbc in () at /usr/lib/x86_64-linux-gnu/libupower-glib.so.3 #21 0x7f3df03a1e18 in ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #22 0x7f3df03a187a in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #27 0x7f3df6733f4f in (instance=instance@entry=0x55c462ae9580, signal_id=, detail=detail@entry=0) at ../../../../gobject/gsignal.c:3447 ---Type to continue, or q to quit--- #23 0x7f3df6718799 in g_cclosure_marshal_generic (closure=0x55c462ae73a0, return_gvalue=0x0, n_param_values=, param_values=, invocation_hint=, marshal_data=) at ../../../../gobject/gclosure.c:1490 #24 0x7f3df6717f9d in g_closure_invoke (closure=0x55c462ae73a0,
[Bug 1721718] [NEW] Segmentation fault in meta_monitor_mode_get_resolution
Public bug reported: When I change the monitor configuration on my newly updated Artful system I get a desktop crash. A quick reproduction with gdb attached to gnome-shell gave the following back-trace, unfortunately with symbols for gnome-shell but not for libmutter (I am still a bit of a new-comer to gnome-shell). Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault. 0x7f2b2d75bf50 in meta_monitor_mode_get_resolution () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 (gdb) bt #0 0x7f2b2d75bf50 in meta_monitor_mode_get_resolution () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 #1 0x7f2b2d75bfd2 in meta_monitor_calculate_mode_scale () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 #2 0x7f2b2d758437 in meta_finish_monitors_config_migration () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 #3 0x7f2b2d7558fe in meta_monitor_config_manager_get_stored () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 #4 0x7f2b2d75d732 in meta_monitor_manager_ensure_configured () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 #5 0x7f2b2f531f9d in g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #6 0x7f2b2f544d5e in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #7 0x7f2b2f54d535 in g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #8 0x7f2b2f54df4f in g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #9 0x7f2b2f536464 in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #10 0x7f2b2f5388b9 in g_object_notify () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #11 0x7f2b2f531f9d in g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #12 0x7f2b2f544d5e in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ---Type to continue, or q to quit--- #13 0x7f2b2f54d535 in g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #14 0x7f2b2f54df4f in g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #15 0x7f2b2f536464 in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #16 0x7f2b2f5388b9 in g_object_notify () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #17 0x7f2b23f1abbc in () at /usr/lib/x86_64-linux-gnu/libupower-glib.so.3 #18 0x7f2b291bbe18 in ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #19 0x7f2b291bb87a in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #20 0x7f2b2f532799 in g_cclosure_marshal_generic () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #21 0x7f2b2f531f9d in g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #22 0x7f2b2f5447d8 in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #23 0x7f2b2f54d535 in g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #24 0x7f2b2f54df4f in g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #25 0x7f2b2f83f311 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #26 0x7f2b2f82e804 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #27 0x7f2b2f258de5 in g_main_context_dispatch () ---Type to continue, or q to quit--- at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x7f2b2f2591b0 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x7f2b2f2594c2 in g_main_loop_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #30 0x7f2b2d79201c in meta_run () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 #31 0x56266c5ff307 in main (argc=, argv=) at ../src/main.c:462 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libmutter-1-0 3.26.0+20170925~ea214fb-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 10:03:09 2017 InstallationDate: Installed on 2016-05-31 (492 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: mutter UpgradeStatus: Upgraded to artful on 2017-10-05 (1 days ago) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- 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/1721718 Title: Segmentation fault in meta_monitor_mode_get_resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1721718/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1466368] Re: Middle click paste from touchpad sometimes stops working
Looks like a case of Problem between Keyboard and Chair. I notice that middle clicks work when I release the button very quickly. It is hard to say now of course, I think that that was not necessary previously, which is what mislead me. I will leave it up to others whether to keep this open or close it. -- 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/1466368 Title: Middle click paste from touchpad sometimes stops working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1466368/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1499747] Re: gedit crashed with SIGABRT in g_assertion_message()
Seems to be fixed here too. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1499747 Title: gedit crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1499747/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1499747] Re: gedit crashed with SIGABRT in g_assertion_message()
I can also reproduce this as described in comment 14, and get it whenever I start Pidgin and log in to my Jabber account: $ pidgin ** GLib-GIO:ERROR:/build/glib2.0-pRoDo9/glib2.0-2.46.0/./gio/gmenuexporter.c:256:g_menu_exporter_menu_items_changed: assertion failed: (position + removed <= g_sequence_get_length (menu->item_links)) Aborted (core dumped) $ gedit ** GLib-GIO:ERROR:/build/glib2.0-pRoDo9/glib2.0-2.46.0/./gio/gmenuexporter.c:256:g_menu_exporter_menu_items_changed: assertion failed: (position + removed <= g_sequence_get_length (menu->item_links)) Aborted (core dumped) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1499747 Title: gedit crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1499747/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1466368] Re: Middle click paste from touchpad sometimes stops working
Update: I noticed that I was unable to select and paste URLs and parts of URLs from Firefox to Pidgin this morning. I naively assume that it is the same issue. -- 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/1466368 Title: Middle click paste from touchpad sometimes stops working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1466368/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1466368] [NEW] Middle click paste from touchpad sometimes stops working
Public bug reported: Quite often (subjectively nearly always) when I am using my laptop - Dell Latitude E7440 - undocked with the internal touch pad, after a while middle click paste stops working in gnome-terminal. I can middle- click paste in e.g. Firefox, but neither from nor to gnome-terminal. I have not seen this while docked with an external mouse. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: gnome-terminal 3.14.2-0ubuntu3 Uname: Linux 4.0.0-04rc2-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 18 08:30:11 2015 InstallationDate: Installed on 2014-08-01 (321 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages vivid -- 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/1466368 Title: Middle click paste from touchpad sometimes stops working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1466368/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1430429] [NEW] jayatana prevents jdk1.6.0 from working
Public bug reported: Happens during a build of VirtualBox. I think that the make output describes the problem best: kBuild: Generating /home/michael/vbox/trunk/out/linux.amd64/debug/obj/vboxjws-gen/jwsgen/jwsglue.list /home/michael/vbox/trunk/tools/linux.x86/jdk1.6.0_27/bin/wsimport -Xnocompile -p org.virtualbox_4_4.jaxws -d /home/michael/vbox/trunk/out/linux.amd64/debug/obj/vboxjws-gen/jwsgen/java /home/michael/vbox/trunk/out/linux.amd64/debug/obj/webservice/vboxwebService.wsdl Picked up JAVA_TOOL_OPTIONS: -javaagent:/usr/share/java/jayatanaag.jar Error occurred during initialization of VM Could not find agent library instrument on the library path, with error: libinstrument.so: cannot open shared object file: No such file or directory kmk: *** [/home/michael/vbox/trunk/out/linux.amd64/debug/obj/vboxjws-gen/jwsgen/jwsglue.list.ts] Error 1 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: jayatana 2.7-0ubuntu3 Uname: Linux 4.0.0-04rc2-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 10 17:35:06 2015 InstallationDate: Installed on 2014-08-01 (221 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: jayatana UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: jayatana (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to jayatana in Ubuntu. https://bugs.launchpad.net/bugs/1430429 Title: jayatana prevents jdk1.6.0 from working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jayatana/+bug/1430429/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 146862] Re: Should not allow to paste in the Leave Message box
I would like to draw attention to this issue again. The fix which was created is somewhat problematic, as it causes clipboard content to be lost when the screensaver password screen is shown. Relevant to me is that when that screen is shown in an Ubuntu guest in VirtualBox using clipboard sharing it causes the host clipboard contents to be lost. The original problem which the fix solved no longer exists, since the leave a message functionality in gnome-screensaver is long gone, but the upstream GNOME developers do not seem interested in reverting the fix, as gnome-screensaver is only used by Ubuntu at this point and is deprecated upstream. Would it be possible then for you to make that change in Ubuntu? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/146862 Title: Should not allow to paste in the Leave Message box To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/146862/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 304889] Re: Does not use system proxy settings
Nice little workaround for IRC, and hence for idle (at least it does the job at a pinch): http://wiki.tcl.tk/3125 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/304889 Title: Does not use system proxy settings To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/304889/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 9441] Re: the locate pointer option breaks other keybindings
Kirill: I am commenting as the member of the VirtualBox development team in charge of keyboard handling in Linux. My guess is that the locate pointer tool places a passive grab [1] on the control key. What this means if it is correct is that as of the point when the grab is placed no other application can see the control key being pressed or released unless the tool explicitly allows it (I presume it doesn't); however they can still (usually) see combinations including the control key, such as Ctrl-Scroll in Frederik's example above. Certainly VirtualBox relies on being able to spot individual keypresses and releases and doesn't try to monitor key combinations to work around this sort of thing: we take the point of view that if the user wants to take keys away from us for other purposes they should know what they are doing, and we don't want to add complexity to deal with it and risk creating bugs for other people. If there were a nice way of spotting passive grabs by other applications we might warn the user, but I don't know of any way other than trying to grab every key ourselves to see which ones we can't get. [1] http://tronche.com/gui/x/xlib/input/XGrabKey.html -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/9441 Title: the locate pointer option breaks other keybindings To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/9441/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
