[Bug 1785174] [NEW] nvidia driver - does not resume from suspend
Public bug reported: The same as always: System gets to sleep (systemctl suspend), when pressing a key to resume from sleep, the system will power up (fans and hard disk can be heard), but screens remain dark. Not even terminals can be accessed (ctrl-alt-F2...6). No problem with nouveau driver this time... ubuntu GNOME 18.04, clean install Fujitsu-Siemens Celsius WT-380 nvidia GT 630 two monitors - MY GUESS IS THAT THIS IS IS AN IMPORTANT ASPECT Tried nvidia340, 390 and 396 - all the same result. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Description changed: The same as always: System gets to sleep (hibernate), when pressing a key to resume from sleep, the system will power up (fans and hard disk can be heard), but screens remain dark. Not even terminals can be accessed (ctrl-alt-F2...6). No problem with nouveau driver this time... ubuntu GNOME 18.04, clean install Fujitsu-Siemens Celsius WT-380 nvidia GT 630 + two monitors - MY GUESS IS THAT THIS IS IS AN IMPORTANT ASPECT Tried nvidia340, 390 and 396 - all the same result. ** Summary changed: - nvidia driver - does not resume from hibernate + nvidia driver - does not resume from suspend ** Description changed: The same as always: - System gets to sleep (hibernate), when pressing a key to resume from sleep, the system will power up (fans and hard disk can be heard), but screens remain dark. Not even terminals can be accessed (ctrl-alt-F2...6). + System gets to sleep (systemctl suspend), when pressing a key to resume from sleep, the system will power up (fans and hard disk can be heard), but screens remain dark. Not even terminals can be accessed (ctrl-alt-F2...6). No problem with nouveau driver this time... ubuntu GNOME 18.04, clean install Fujitsu-Siemens Celsius WT-380 nvidia GT 630 two monitors - MY GUESS IS THAT THIS IS IS AN IMPORTANT ASPECT Tried nvidia340, 390 and 396 - all the same result. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1785174 Title: nvidia driver - does not resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1785174/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1687864] Re: auto-login and "privacy -> auto screen lock -> disable" do not work
After a clean install of bionic, the system behaved as expected for some days. Now, I get autologin after system boot, but have to type my password after resume from sleep again. It happens with nvidia and nouveau driver. ** Changed in: gnome-control-center (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1687864 Title: auto-login and "privacy -> auto screen lock -> disable" do not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1687864/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774784] Re: tras escribir la constraseña de usuario, gnome-shell, no arranca usando el perfil Community Theme.
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1774784 Title: tras escribir la constraseña de usuario, gnome-shell, no arranca usando el perfil Community Theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1774784/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1422253] Re: gnome-shell crashed with SIGABRT in g_assertion_message("assertion failed: (window->display->focus_window != window)") from g_assertion_message_expr() from meta_window_unmanage() fro
** Also affects: gnome-shell (Ubuntu Bionic)
Importance: Undecided
Status: New
--
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/1422253
Title:
gnome-shell crashed with SIGABRT in g_assertion_message("assertion
failed: (window->display->focus_window != window)") from
g_assertion_message_expr() from meta_window_unmanage() from
handle_other_xevent()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1422253/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754949] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame()
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Bionic) Importance: Undecided Status: New -- 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/1754949 Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754949/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767956] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_new() from meta_monitor_manager_kms_initable_init() from g_initable_new_valist() from g_initable_new() from meta_backend_create_monit
** Also affects: gnome-shell (Ubuntu Bionic) Importance: Undecided Status: New -- 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/1767956 Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_new() from meta_monitor_manager_kms_initable_init() from g_initable_new_valist() from g_initable_new() from meta_backend_create_monitor_manager() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767956/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1723615] Re: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()
** Also affects: mutter (Ubuntu Bionic) Importance: Undecided Status: New -- 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/1723615 Title: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1723615/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1772831] Re: gnome-control-center does not respond after we set the resolution 320x180
** Also affects: gnome-control-center (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1772831 Title: gnome-control-center does not respond after we set the resolution 320x180 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1772831/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784398] Re: Changing monitor settings crashes on meta_window_wayland_move_resize_internal
** Also affects: gnome-shell (Ubuntu Bionic) Importance: Undecided Status: New -- 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/1784398 Title: Changing monitor settings crashes on meta_window_wayland_move_resize_internal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1784398/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1782152] Re: GDM blocks SIGUSR1 used in PAM scripts
Did Alberto release the fix there and just forget to document it? -- 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/1782152 Title: GDM blocks SIGUSR1 used in PAM scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782152/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1782152] Re: GDM blocks SIGUSR1 used in PAM scripts
Yes. The fix for this bug is in 3.28.2-3ubuntu4 -- 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/1782152 Title: GDM blocks SIGUSR1 used in PAM scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782152/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
jMyles, does your keyboard also stop responding to everything, including the Windows key? If so then that sounds like your shell is frozen, which is a different bug. In that case please open a new bug by running: ubuntu-bug gnome-shell on the machine. -- 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/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784065] Re: upgrade from 14.04 to 16.04 fails due to `interest-await' in trigger
Confirming that with new glib2.0 - 2.48.2-0ubuntu4 in updates repository, I could now easily do the 14.04 to 16.04 upgrade. Thanks to all who made this fix happen quickly! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1784065 Title: upgrade from 14.04 to 16.04 fails due to `interest-await' in trigger To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1784065/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767817] Re: Full text search does not work
Hi ! I have the same issue as I stated here : https://askubuntu.com/questions/1061855/ubuntu-18-04-and-tracker-files- properly-indexed-but-not-searchable-in-gs-naut 1. I installed tracker 2. I indexed all my data (as indicated on the command line by "tracker status" / "tracker daemon") 3. I checked whether everything was properly indexed by making some queries on the command line based on the content of some text files : the command line "tracker search" command did yield the right results 4. I made the same searches from Nautilus : they yielded no result : Nautilus (and thus the shell) only seem to use the "mlocate" database and not the tracker one. Hypothesis : the fact Ubuntu makes use of Nautilus 3.26 while the rest of the Gnome stack is 3.28 ? Actually, did anyone manage to get Nautilus 3.26 (and thus Gnome Shell with the nautilus search provider) from Ubuntu 18.04 to use the result of the tracker indexing ? I checked all possible settings in dconf- editor and found no relevant option. Cheers :-) -- 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/1767817 Title: Full text search does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1785144] [NEW] /usr/lib/gnome-terminal/gnome-terminal-server:11:gtk_widget_get_toplevel:gtk_main_do_event:gdk_event_source_dispatch:g_main_dispatch:g_main_context_dispatch
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-terminal. This problem was most recently seen with package version 3.18.3-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/533baf10eb4eebaf140d791f6b612b140c44b36d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: xenial yakkety -- 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/1785144 Title: /usr/lib/gnome-terminal/gnome-terminal- server:11:gtk_widget_get_toplevel:gtk_main_do_event:gdk_event_source_dispatch:g_main_dispatch:g_main_context_dispatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1785144/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1785122] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1785122/+attachment/5170927/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1785122/+attachment/5170914/+files/CoreDump.gz ** Changed in: nautilus (Ubuntu) Importance: Undecided => Medium ** Tags removed: need-amd64-retrace -- 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/1785122 Title: nautilus crashed with SIGSEGV in _int_malloc() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1785122/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1785122] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1785122/+attachment/5170926/+files/StacktraceSource.txt -- 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/1785122 Title: nautilus crashed with SIGSEGV in _int_malloc() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1785122/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1785122] nautilus crashed with SIGSEGV in _int_malloc()
StacktraceTop: _int_malloc (av=av@entry=0x7f33dc20, bytes=bytes@entry=33) at malloc.c:3612 _int_realloc (av=av@entry=0x7f33dc20, oldp=oldp@entry=0x7f33dc042890, oldsize=oldsize@entry=32, nb=nb@entry=48) at malloc.c:4570 __GI___libc_realloc (oldmem=0x7f33dc0428a0, bytes=bytes@entry=32) at malloc.c:3230 g_realloc (mem=, n_bytes=32) at ../../../../glib/gmem.c:164 g_array_maybe_expand (array=0x7f33ec019840, len=len@entry=1) at ../../../../glib/garray.c:794 -- 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/1785122 Title: nautilus crashed with SIGSEGV in _int_malloc() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1785122/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1785122] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1785122/+attachment/5170925/+files/Stacktrace.txt -- 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/1785122 Title: nautilus crashed with SIGSEGV in _int_malloc() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1785122/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1785122] [NEW] nautilus crashed with SIGSEGV in _int_malloc()
Public bug reported: The nautilus closed all of a sudden ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 2 23:16:25 2018 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'196' b'org.gnome.nautilus.window-state' b'geometry' b"'960x1011+960+27'" b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'" ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x7f34073e43c1 <_int_malloc+241>:mov 0x10(%rsi),%r9 PC (0x7f34073e43c1) ok source "0x10(%rsi)" (0x7f33dc01cb0010) not located in a known VMA region (needed readable region)! destination "%r9" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: _int_malloc (av=av@entry=0x7f33dc20, bytes=bytes@entry=33) at malloc.c:3612 _int_realloc (av=av@entry=0x7f33dc20, oldp=oldp@entry=0x7f33dc042890, oldsize=oldsize@entry=32, nb=nb@entry=48) at malloc.c:4570 __GI___libc_realloc (oldmem=0x7f33dc0428a0, bytes=32) at malloc.c:3230 g_realloc () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: nautilus crashed with SIGSEGV in _int_malloc() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-crash bionic ** Information type changed from Private to Public -- 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/1785122 Title: nautilus crashed with SIGSEGV in _int_malloc() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1785122/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1723615] Re: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()
FWIW I can't reproduce this any more either; since 18.04 in fact I've had no problems with gnome-shell crashing. The monitor very nearly always does wake up when it's supposed to now (some difference in the dpms signal being sent? Previously it would always wake for windows and just had a hard time with Linux), and on the few occasions it hasn't, I haven't lost my session and I just needed to powercycle the monitor properly. So I was under the impression this was all fixed. :-) Possibly by not-obviously-related changes elsewhere. -- 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/1723615 Title: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1723615/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1422253] Re: gnome-shell crashed with SIGABRT in g_assertion_message("assertion failed: (window->display->focus_window != window)") from g_assertion_message_expr() from meta_window_unmanage() fro
** Description changed:
https://errors.ubuntu.com/problem/868da6d40640c1199f496b7af7e37e54871ed8d7
https://errors.ubuntu.com/problem/9b0e145ca11443bc44b35a2050317dd51f5ab5c5
Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/15
- ---
+ [ Description ]
Was running 3 programs at time of crash, PROGRAM 1. Nautilus with no
tabs open, PROGRAM 2. Firefox v.34.0 with 3 tabs open (1.
https://twitter.com/ - 2.
http://www.scons.org/wiki/FrequentlyAskedQuestions#What_is_SCons.3F -
PROGRAM 3. http://scons.org/download.php) Synaptic Package Manager ver
0.81.3 installing Scons & Scons-doc - crash happened while synaptic was
in process of installing programs (downloads were complete & actual
install was in progress)
- -
+ [ Test case ]
+
+ 1. Run one of the reproducer test (python or gjs version) available at:
+https://gitlab.gnome.org/GNOME/mutter/issues/15
+ 2. when that close, g-s should not crash
+
+ [ Regression potential ]
+
+ Possible break for windows that have the grab but are not the active
+ ones.
+
+
+
ProblemType: CrashDistroRelease: Ubuntu 15.04
Package: gnome-shell 3.14.3-0ubuntu2
ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
Uname: Linux 3.18.0-13-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Mon Feb 16 01:20:05 2015
DisplayManager: gdm
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
b'org.gnome.desktop.interface' b'clock-show-date' b'true'
InstallationDate: Installed on 2015-01-26 (21 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Alpha amd64
(20150120.1)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
- SHELL=/bin/bash
- Signal: 6SourcePackage: gnome-shell
+ SHELL=/bin/bashSignal: 6SourcePackage: gnome-shell
StacktraceTop:
g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
meta_window_unmanage () from /usr/lib/libmutter.so.0
?? () from /usr/lib/libmutter.so.0
?? () from /usr/lib/libmutter.so.0
Title: gnome-shell crashed with SIGABRT in g_assertion_message()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
--
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/1422253
Title:
gnome-shell crashed with SIGABRT in g_assertion_message("assertion
failed: (window->display->focus_window != window)") from
g_assertion_message_expr() from meta_window_unmanage() from
handle_other_xevent()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1422253/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1723615] Re: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()
** Description changed: https://gitlab.gnome.org/GNOME/mutter/issues/130 https://errors.ubuntu.com/problem/84e05b052e88b79520a684d6113084e9be8bc339 --- + + [ Description ] This happened while I was away from the computer. By the timing it should have been well after the time it should have gone *into* displaysleep, and was also about 45min before I returned, so certainly wasn't the wake-up process either. What I observed when I did return: My 4K monitor didn't wake up (that's a known problem with this monitor, Dell P2715Q), the second monitor (Dell U2711) did wake up, showing the login screen. So although I've considered my Dell 4K problem a problem with waking up, I wonder if it might be actually a problem with it apparently going away completely after a longer displaysleep (it's usually fine if I just do a short sleep of a minute or two). Another possibility is the cat stepped on the keyboard and thus triggered an attempted display-wake. But that would actually be out of character (for the cat). Either way is a bug because the session should survive monitor shenanigans... :-) - ProblemType: Crash - DistroRelease: Ubuntu 17.10 + In some not known conditions, g-s might crash while computing global + resolution for monitors. + + [ Test case ] + + There's really no test case for this bug, a part that g-s should not + crash with this stacktrace. Unforuntaltey this is quite hard to + reproduce, it might happen while resetting the crtc when setting up a + (new) monitor or at wake up, but so far nobody has reported a way for + reproducing this. + + [ Regression potential ] + + Global scale for attached monitors could not be properly computed, and + thus if attaching an HiDPI device, the UI could not be scaled properly + + --- + + ProblemType: CrashDistroRelease: 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 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Oct 14 15:39:50 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-07-30 (75 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7fae20ab44a0 : mov0x8(%rdi),%eax PC (0x7fae20ab44a0) ok source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA - Signal: 11 - SourcePackage: gnome-shell + Signal: 11SourcePackage: gnome-shell StacktraceTop: meta_monitor_mode_get_resolution () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_monitor_calculate_mode_scale () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_monitor_manager_update_logical_state_derived () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_monitor_manager_rebuild_derived () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_monitor_manager_xrandr_handle_xevent () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 Title: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution() UpgradeStatus: Upgraded to artful on 2017-08-22 (53 days ago) UserGroups: -- 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/1723615 Title: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1723615/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1772831] Re: gnome-control-center does not respond after we set the resolution 320x180
This will be fixed in mutter (3.29.90-1) ** Description changed: + [ Description ] + gnome-control-center does not respond after we set the resolution 320x180 + + + [ Test case ] + + Open gnome-control-center -> Displays + Low resolutions (such as 320x180) should not be listed. + + Trying to set the lowst listed resolution, should just apply without + breaking gnome-control-center. + + [ Regression potential ] + + No alternative resolutions are shown in g-c-c + + --- Expected results: shows the countdown dialog Actual results: the countdown dialog doesn't show. Only mouse cursor can move. All of the buttons/icons don't respond. Note1: When I executed "gnome-settings-daemon -o -v | tee gcc.log", the count-down dialog shows up! - Notebook: Dell XPS 13 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1772831 Title: gnome-control-center does not respond after we set the resolution 320x180 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1772831/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1568852] Re: missing title bar for some applications
I've not seen it yet on bionic (which uses 3.28), but it's still not fixed on xenial's 3.18. Even though I encounter this quite frequently there, I couldn't find a way to reproduce it in a consistent manner. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1568852 Title: missing title bar for some applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1568852/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767956] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_new() from meta_monitor_manager_kms_initable_init() from g_initable_new_valist() from g_initable_new() from meta_backend_create_monit
** Description changed: + [ Description ] + + GNome shell crashes after Xorg logging + + [ Test case ] + + From GDM login in a GNOME Ubuntu session (so Xorg). + It should start with no issues + + [ Regression potential ] + + Nothing know, this is a safe NULL check, so no crash will happen. + It's not granted that the session will work properly aftewards though. + + -- + The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.1-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/ceb319b41dc72ad98263c386ee6891b05fca8623 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium -- 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/1767956 Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_new() from meta_monitor_manager_kms_initable_init() from g_initable_new_valist() from g_initable_new() from meta_backend_create_monitor_manager() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767956/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754949] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame()
** Description changed: + [ Description ] + + GNome shell crashes after Xorg loggin + + [ Test case ] + + From GDM login in a GNOME Ubuntu session (so Xorg). + It should start with no issues + + [ Regression potential ] + + We were deferencing a NULL pointer while outputting an error. + This is pretty safe. Although the session might still not run properly as per a driver issue to be addressed in linux package. + + --- + https://gitlab.gnome.org/GNOME/mutter/issues/70 https://errors.ubuntu.com/problem/16426125ad8d92ae4dc9ce9e89450153b0a8b665 https://salsa.debian.org/gnome-team/mutter/merge_requests/6 --- The crash was reported after booting and logging in to an X.Org session. $ lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 $ apt-cache policy gnome-shell gnome-shell: Instalovaná verze: 3.27.92-0ubuntu1 Kandidát: 3.27.92-0ubuntu1 Tabulka verzí: *** 3.27.92-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: CrashDistroRelease: Ubuntu 18.04 Package: gnome-shell 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Mar 11 11:08:00 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-12-19 (81 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=cs_CZ PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f3fee5d2f17 : mov0x20(%rax),%rcx PC (0x7f3fee5d2f17) ok source "0x20(%rax)" (0x0020) not located in a known VMA region (needed readable region)! destination "%rcx" ok - SegvReason: reading NULL VMA - Signal: 11SourcePackage: gnome-shell + SegvReason: reading NULL VMASignal: 11SourcePackage: gnome-shell StacktraceTop: meta_gpu_kms_apply_crtc_mode () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 meta_renderer_native_finish_frame () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() UpgradeStatus: Upgraded to bionic on 2018-03-05 (5 days ago) UserGroups: -- 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/1754949 Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754949/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784398] Re: Changing monitor settings crashes on meta_window_wayland_move_resize_internal
** Description changed: - Under wayland: + [ Description ] + + Under wayland adding a monitor in cloned mode might crash g-s + + See upstream bug: https://gitlab.gnome.org/GNOME/mutter/issues/248 + + [ Test case ] + + Open an Ubuntu session on Wayland: 1. Attach another monitor 2. Mark as cloned display 3. Gnome-shell should not crash - See upstream bug: https://gitlab.gnome.org/GNOME/mutter/issues/248 + [ Regression potential ] + + Global scale for attached monitors could not be properly computed, and + thus if attaching an HiDPI device, the UI could not be scaled properly -- 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/1784398 Title: Changing monitor settings crashes on meta_window_wayland_move_resize_internal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1784398/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1542519] Re: Double menu bar
^ this solution doesn't work anymore -- 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/1542519 Title: Double menu bar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1542519/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784671] Re: Keeping Alt+Space pressed shows the window menu and then minimizes the window
** Description changed: To reproduce: - Open a couple of windows Press Alt+Space and keep it pressed - Expected results: - The window menu opens and nothing else happens - Current behavior: - The window menu opens The window is minimized The window menu of the following window is open The window is minized ... + + [ Description ] + + Pressing Alt+Space and keeping it pressed causes a window to be + minimized + + [ Test case ] + + 1. Press Alt+Space and keep it pressed + 2. The menu should stay open without any action being performed automatically + + [ Regression potential ] + + Key-actions happening with popups open when keybindings use modifiers + might be broken afterwards. No case that I know. ** Description changed: + + [ Description ] + + Pressing Alt+Space and keeping it pressed causes a window to be + minimized + + [ Test case ] + + 1. Press Alt+Space and keep it pressed + 2. The menu should stay open without any action being performed automatically + + [ Regression potential ] + + Key-actions happening with popups open when keybindings use modifiers + might be broken afterwards. No case that I know. + + --- + To reproduce: Open a couple of windows Press Alt+Space and keep it pressed Expected results: The window menu opens and nothing else happens Current behavior: The window menu opens The window is minimized The window menu of the following window is open The window is minized - ... - - [ Description ] - - Pressing Alt+Space and keeping it pressed causes a window to be - minimized - - [ Test case ] - - 1. Press Alt+Space and keep it pressed - 2. The menu should stay open without any action being performed automatically - - [ Regression potential ] - - Key-actions happening with popups open when keybindings use modifiers - might be broken afterwards. No case that I know. -- 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/1784671 Title: Keeping Alt+Space pressed shows the window menu and then minimizes the window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1784671/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767564] Re: Ubuntu 18.04 Workspaces only change on primary monitor
Thank 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/1767564 Title: Ubuntu 18.04 Workspaces only change on primary monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767564/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
This bug was fixed in the package gdm3 - 3.28.2-3ubuntu4 --- gdm3 (3.28.2-3ubuntu4) cosmic; urgency=medium * ubuntu_nvidia_prime.patch: - Run scripts for Prime before and after Gdm sessions (LP: #1778011). -- Alberto Milone Mon, 30 Jul 2018 18:31:17 +0200 ** Changed in: gdm3 (Ubuntu) Status: Fix Committed => Fix Released -- 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/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1782152] Re: GDM blocks SIGUSR1 used in PAM scripts
This bug was fixed in the package gdm3 - 3.28.2-3ubuntu4 --- gdm3 (3.28.2-3ubuntu4) cosmic; urgency=medium * ubuntu_nvidia_prime.patch: - Run scripts for Prime before and after Gdm sessions (LP: #1778011). -- Alberto Milone Mon, 30 Jul 2018 18:31:17 +0200 ** Changed in: gdm3 (Ubuntu Cosmic) Status: In Progress => Fix Released -- 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/1782152 Title: GDM blocks SIGUSR1 used in PAM scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782152/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
I am experiencing this issue and it's just totally crippling. I can't keep a session going for more than a few minutes without suddenly losing the ability to interact with applications. The specifics of my experience more closely match bug #1730229 - although that is marked as a duplicate of this one. Specifically, unlike this issue (but like bug #1730229), I am unable to use alt-f2 once the issue manifests itself. Other mentioned workarounds in this thread do not work for me, including switching-to-tty-and-back, logging-out-and-back-in, and alt-tab. I have also disabled gnome-shell extensions altogether and set the number of workspaces to 1. Any other ideas for a temporary workaround? -- 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/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1568852] Re: missing title bar for some applications
3.18 is very old release, does this happens with 3.28? Is there any way to reproduce this bug always? Bug description says that it does not happen always... :( -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1568852 Title: missing title bar for some applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1568852/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1568852] Re: missing title bar for some applications
I am also having this problem. Additional notes: This happens even on the most primitive X11 applications. Even applications like the Rosetta Code X11 xlib application. This happens regardless of if you use XCreate window or XCreateSimpleWindow. Additionally, even if you change the window title, the window title in bar does not appear. This bug does not seem to happen with Xt, Gnome, KDE and similar applications. This bug is VERY annoying. Hopefully this helps move things along. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1568852 Title: missing title bar for some applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1568852/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
This bug was fixed in the package ubuntu-drivers-common - 1:0.5.3 --- ubuntu-drivers-common (1:0.5.3) cosmic; urgency=medium * gpu-manager.(c|py): - Set automatic pci power management when the dGPU is disabled (LP: #1778011). - Load the nvidia modules when switching to performance mode. - Do not skip unbound devices. - Make remove_prime_outputclass() void. - Report failures in enable_power_management(). - Look for blacklisted modules in /lib/modprobe.d too. - Report failure when the nvidia modules cannot be unloaded, kill the main display session created by gdm3, and try unloading the nvidia modules once again. * gpu-manager.service: - Start before oem-config.service. -- Alberto Milone Thu, 02 Aug 2018 15:45:42 +0200 ** Changed in: ubuntu-drivers-common (Ubuntu) Status: In Progress => Fix Released -- 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/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784065] Re: upgrade from 14.04 to 16.04 fails due to `interest-await' in trigger
** Changed in: glib2.0 (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1784065 Title: upgrade from 14.04 to 16.04 fails due to `interest-await' in trigger To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1784065/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
** Changed in: gdm3 (Ubuntu) Status: In Progress => Fix Committed -- 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/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1782152] Re: GDM blocks SIGUSR1 used in PAM scripts
** Changed in: gdm3 (Debian) Status: Unknown => New -- 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/1782152 Title: GDM blocks SIGUSR1 used in PAM scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782152/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1712661] Re: gnome-shell crash using ubuntu-dock with dual monitors
This bug was fixed in the package gnome-shell-extension-ubuntu-dock - 63ubuntu1 --- gnome-shell-extension-ubuntu-dock (63ubuntu1) cosmic; urgency=medium * Merged with latest master - Fix crash connecting/disconnecting monitors (LP: #1712661) - showApps button label position (LP: #1784920) - Add wrapper to properly run in both gnome-shell 3.28 and 3.29.90 - Update translations, fixed settings typos * Updated versioning to match with extensions.gnome.org * debian/gbp.conf: - updated branches and tags settings accordingly -- Marco Trevisan (Treviño) Thu, 02 Aug 2018 13:29:47 +0200 ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: In Progress => Fix Released -- 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/1712661 Title: gnome-shell crash using ubuntu-dock with dual monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1712661/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784920] Re: "Show applications" label is shown in the right in every dock orientation
This bug was fixed in the package gnome-shell-extension-ubuntu-dock - 63ubuntu1 --- gnome-shell-extension-ubuntu-dock (63ubuntu1) cosmic; urgency=medium * Merged with latest master - Fix crash connecting/disconnecting monitors (LP: #1712661) - showApps button label position (LP: #1784920) - Add wrapper to properly run in both gnome-shell 3.28 and 3.29.90 - Update translations, fixed settings typos * Updated versioning to match with extensions.gnome.org * debian/gbp.conf: - updated branches and tags settings accordingly -- Marco Trevisan (Treviño) Thu, 02 Aug 2018 13:29:47 +0200 ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: In Progress => Fix Released -- 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/1784920 Title: "Show applications" label is shown in the right in every dock orientation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1784920/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767564] Re: Ubuntu 18.04 Workspaces only change on primary monitor
Just to follow up on this issue. I just realized that if you install gnome-tweak tool [sudo apt install gnome-tweak-tool] you can actually choose between coherent or independent behavior of your multiple monitors across workspaces. Once installed, launch tweak and then click on workspaces. then choose " Workspaces span displays" (instead of the default choice "Workspaces on primary display only" !) -- 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/1767564 Title: Ubuntu 18.04 Workspaces only change on primary monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767564/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784065] Update Released
The verification of the Stable Release Update for glib2.0 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1784065 Title: upgrade from 14.04 to 16.04 fails due to `interest-await' in trigger To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1784065/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784065] Re: upgrade from 14.04 to 16.04 fails due to `interest-await' in trigger
This bug was fixed in the package glib2.0 - 2.48.2-0ubuntu4 --- glib2.0 (2.48.2-0ubuntu4) xenial; urgency=medium * Add a versioned Pre-Depends for dpkg because the libglib2.0-0 -await trigger requires a newer dpkg than the one in Ubuntu 14.04. (LP: #1784065) -- Brian Murray Mon, 30 Jul 2018 08:29:26 -0700 ** Changed in: glib2.0 (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1784065 Title: upgrade from 14.04 to 16.04 fails due to `interest-await' in trigger To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1784065/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767564] Re: Ubuntu 18.04 Workspaces only change on primary monitor
Totally agree with Bruce! I have two monitors. Let say I use LibreOffice on the left (primary) monitor and a reference manager on the right monitor. When I switch workspace (let say to do some programming) I don' t expect that the reference manager keeps appearing? This should be fixed. Or at least the possibility to have a coherence behavior of multiple monitors be an option. Please . Otherwise, Ubuntu is great (I just switch from OpenSUSE in which, by the way, multiple monitors switch coherently across workspaces) !! -- 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/1767564 Title: Ubuntu 18.04 Workspaces only change on primary monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767564/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780996] Re: Convert triggers to noawait
** Changed in: libreoffice (Ubuntu Xenial) Assignee: (unassigned) => Olivier Tilloy (osomon) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1780996/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1782152] Re: GDM blocks SIGUSR1 used in PAM scripts
Although I originally shared Daniel's doubt, I reported it to Debian and shared the patch (bug linked above). ** Bug watch added: Debian Bug tracker #905277 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905277 ** Also affects: gdm3 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905277 Importance: Unknown Status: Unknown -- 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/1782152 Title: GDM blocks SIGUSR1 used in PAM scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782152/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1785060] [NEW] Evince cannot open cbr-files based on rar v5
Public bug reported: Trying to open a cbr-Archive based on rar v5 leads to "Der Dateityp RAR-Archiv (application/vnd.rar) wird nicht unterstützt." CBR-Files based on other rar-Types, e.g. rarv4 works fine. ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1785060 Title: Evince cannot open cbr-files based on rar v5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1785060/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1775226] Re: [SRU] Gnome Software offers installation of updates on shutdown independently from update-manager and unattended-upgrades
** Summary changed: - Gnome Software offers installation of updates on shutdown independently from update-manager and unattended-upgrades + [SRU] Gnome Software offers installation of updates on shutdown independently from update-manager and unattended-upgrades ** Description changed: + [Original Description] + In Ubuntu the GUI for upgrading packages is update-manager allowing debconf questions to be answered when needed and Ubuntu also offers unattended-upgrades for upgrading packages in the background and it keeps back packages from upgrading when configuration-file changes would need user interaction during the upgrade. Unattended-upgrades can be configured to perform upgrades during system shutdown. Gnome Software in Bionic started offering performing upgrades during shutdown using PackageKit independently from update-manager and unattended-upgrades without offering all of the features of either one. Unless there is a decision to fully switch to Gnome Software I suggest disabling the "Install pending software updates" on the shutdown screen to avoid confusing users. + + + [Impact] + + As stated in the original description, users may be confused by the + checkbox on the shutdown dialog offering to install updates, considering + that all updates in Ubuntu are currently handled by a separate GUI + (update-manager). + + This is fixed in cosmic (3.29.1-0ubuntu6) by disabling offline updates + in the packagekit refresh plugin. + + The fix is trivial and complements an existing patch that was already + disabling updates in gnome-software. + + + [Test Case] + + 0) Prerequisite: a bionic system not fully up-to-date (if yours is fully up-to-date, downgrade a package) + 1) Verify that the following file doesn't exist (if it does, remove it): /var/lib/PackageKit/prepared-update + 2) Open gnome-software + 3) Click on the "Updates" tab, and click the refresh button in the top-left corner + 4) Wait for the refresh operation to be complete (gnome-software might incorrectly report that there are no updates available, this is a separate issue, bug #1709725) + 5) Wait a minute or two to ensure there are no pending packagekit async tasks + 6) Verify that /var/lib/PackageKit/prepared-update still doesn't exist, and consequently, when requesting to shut down the computer, the shutdown dialog doesn't offer a "Install pending software updates" checkbox + + + [Regression Potential] + + gnome-software is not used to install updates (from the archive) on + Ubuntu. However firmware updates and updates from other packaging + systems (such as flatpak) should still appear in the updates tab, when + available. + + + [Other Info] + + The updates tab in gnome-software may claim that there are no updates + available, when in fact there are. This is also confusing, but is a + separate issue (bug #1709725) and will be addressed separately. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1775226 Title: [SRU] Gnome Software offers installation of updates on shutdown independently from update-manager and unattended-upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1775226/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1775226] Re: Gnome Software offers installation of updates on shutdown independently from update-manager and unattended-upgrades
** Also affects: gnome-software (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: gnome-software (Ubuntu Bionic) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: gnome-software (Ubuntu Bionic) Status: New => In Progress ** Changed in: gnome-software (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1775226 Title: Gnome Software offers installation of updates on shutdown independently from update-manager and unattended-upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1775226/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: PRIME Power Saving mode draws too much power
** Description changed: Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. - Solving the problem in systemd (LP: #1777099), and adding code in gpu- - manager and in nvidia-prime to unload the nvidia modules, and to allow - the PCI device to sleep, dramatically decreases power consumption. + Furthermore, if the main X/Xwayland session was started by Gdm when the + nvidia driver was loaded, the session will keep the nvidia module + loaded, and prevent the system from switching off the dGPU. Also, the + nouveau driver will be loaded, if nvidia is not, and this can cause + problems to unsupported NVIDIA GPUs. + + The solution involves the following changes: + + 1) Solving the problem in systemd (LP: #1777099) + + 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia + modules, and to allow the PCI device to sleep. + + 3) Making a slight change to the current patch in Gdm, used to call the + PRIME scripts before and after a Gdm session (so that gpu-manager gets + actually called on log out) + + 4) Adding code in gpu-manager to kill the main X/Xwayland session on log + out, if the session is preventing us from unloading the nvidia driver. A + new X/Xwayland session will be created after unload the module. + + 5) Removing the systemd service that loads nouveau from the nvidia + packages. ** Also affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Fix Released ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Description changed: - Relying on the nouveau driver and on the vga switcheroo (to get around a - change in systemd LP: #1777099) caused increased power consumption, and - slowed down the switching process. + SRU Request: + + [Impact] + Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. + + + [Test Case] + 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 + + 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): + sudo prime-select nvidia + + 3) Restart your computer and attach your /var/log/gpu-manager.log. see + if the system boots correctly. If unsure, please attach your /var/log + /gpu-manager.log and /var/log/Xorg.0.log + + 4) Select power saving mode: + sudo prime-select intel + + 5) Log out and log back in + + 6) Check if the nvidia driver is still loaded: + lsmod | grep nvidia + + + [Regression Potential] + Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. ** Summary changed: - PRIME Power Saving mode draws too much power + SRU: PRIME Power Saving mode draws too much power -- 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/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com
[Bug 1783571] Re: Set Yaru as default
This bug was fixed in the package yaru-theme - 18.10.1 --- yaru-theme (18.10.1) cosmic; urgency=medium [ Didier Roche ] * debian/yaru-theme-gnome-shell.postinst: - bump priority for Yaru gdm css to 15, higher than current ubuntu unthemed default. (LP: #1783571) [ Marco Trevisan (Treviño) ] * Theme updated to support gnome-shell 3.29.90 * debian/gbp.conf: - add build-package configuration -- Marco Trevisan (Treviño) Wed, 01 Aug 2018 16:32:46 +0200 ** Changed in: yaru-theme (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1783571 Title: Set Yaru as default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1783571/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries (stack traces ending in osdWindow.js:206/207)
I am facing this issue too. Is there a workaround as I have very limited disk space and this is killing it! Aug 2 09:09:03 Bantam1 org.gnome.Shell.desktop[1532]: == Stack trace for context 0x55c6d5f34330 == Aug 2 09:09:03 Bantam1 org.gnome.Shell.desktop[1532]: #0 0x7ffc8ee86540 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f44101c96f8 @ 231) Aug 2 09:09:03 Bantam1 org.gnome.Shell.desktop[1532]: #1 0x7ffc8ee865b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f44103b5de0 @ 71) Aug 2 09:09:03 Bantam1 org.gnome.Shell.desktop[1532]: #2 0x7ffc8ee865b0 I self-hosted:915 (0x7f44103f12b8 @ 367) Aug 2 09:09:03 Bantam1 org.gnome.Shell.desktop[1532]: #3 0x7ffc8ee86650 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f44103d3230 @ 386) Aug 2 09:09:03 Bantam1 org.gnome.Shell.desktop[1532]: #4 0x55c6d62daa10 i resource:///org/gnome/shell/ui/layout.js:531 (0x7f44101042b8 @ 127) Aug 2 09:09:03 Bantam1 org.gnome.Shell.desktop[1532]: #5 0x7ffc8ee87240 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f44103b5de0 @ 71) Aug 2 09:09:03 Bantam1 org.gnome.Shell.desktop[1532]: #6 0x7ffc8ee87240 I self-hosted:915 (0x7f44103f12b8 @ 367) -- 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/1772677 Title: gnome-shell filling up syslog with thousands of entries (stack traces ending in osdWindow.js:206/207) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1772677/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1785015] [NEW] Nvidia GPU shows zero usage all the time
Public bug reported: I have the nvidia-smi package installed and it shows GPU info correctly. The monitor though shows zero usage in the graph. For a short while I was able to get it showing GPU usage, by setting lower refresh rate, but then it stopped working again and now I can't get it working. martin@martin-thinkpad-p50s:~$ nvidia-smi Thu Aug 2 09:46:45 2018 +-+ | NVIDIA-SMI 390.77 Driver Version: 390.77| |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | |===+==+==| | 0 Quadro M500MOff | :06:00.0 Off | N/A | | N/A 50CP0N/A / N/A |421MiB / 2004MiB | 6% Default | +---+--+--+ +-+ | Processes: GPU Memory | | GPU PID Type Process name Usage | |=| |0 1292 G /usr/lib/xorg/Xorg 225MiB | |0 1795 G /usr/bin/gnome-shell 121MiB | |0 4302 G ...-token=9E7DB48B8BFB5171728EA8BCAA76548472MiB | +-+ ** Affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1785015 Title: Nvidia GPU shows zero usage all the time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1785015/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1781647] Re: gnome-shell crashed with SIGABRT in __GI___poll() from g_main_context_poll() from g_main_context_iterate() from g_main_loop_run() from g_dbus_connection_send_message_with_reply_sync(
Thanks. Though we don't need to wait for the result of further testing to believe the bug is not in gnome-shell. If you find the bug is in an extension that is offered by the Ubuntu archive then we should reopen it as a task against that extension. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid -- 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/1781647 Title: gnome-shell crashed with SIGABRT in __GI___poll() from g_main_context_poll() from g_main_context_iterate() from g_main_loop_run() from g_dbus_connection_send_message_with_reply_sync() from g_dbus_connection_call_sync_internal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1781647/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
