[Bug 1916701] Re: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered)

2021-02-23 Thread Sebastien Bacher
** Tags added: block-proposed

-- 
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/1916701

Title:
  [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed,
  eventually comes up without Wayland support (only Xorg sessions
  offered)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1916701/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1916701] Re: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered)

2021-02-23 Thread Daniel van Vugt
It looks like this glib error always comes first:

Feb 24 15:24:48 kab gnome-shell[1013]: invalid (NULL) pointer instance
Feb 24 15:24:48 kab gnome-shell[1013]: g_signal_connect_data: assertion 
'G_TYPE_CHECK_INSTANCE (instance)' failed
...
Feb 24 15:25:39 kab gnome-shell[1013]: JS ERROR: Gio.IOErrorEnum: Error calling 
StartServiceByName for org.gnome.SessionManager: Timeout was reached

-- 
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/1916701

Title:
  [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed,
  eventually comes up without Wayland support (only Xorg sessions
  offered)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1916701/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1916701] Re: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered)

2021-02-23 Thread Daniel van Vugt
When the login screen does finally come up (without Wayland support),
the first log message is:

Feb 24 15:25:39 kab gnome-shell[1013]: JS ERROR: Gio.IOErrorEnum: Error calling 
StartServiceByName for org.gnome.SessionManager: Timeout was reached
   
_injectToMethod/klass[method]@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:290:25
   
_makeProxyWrapper/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:267:17
   
SessionManager@resource:///org/gnome/shell/misc/gnomeSession.js:36:12
   
_init@resource:///org/gnome/shell/misc/systemActions.js:140:25
   
getDefault@resource:///org/gnome/shell/misc/systemActions.js:28:22
   
_init@resource:///org/gnome/shell/ui/status/system.js:18:31
   
_init@resource:///org/gnome/shell/ui/panel.js:743:24
   
_ensureIndicator@resource:///org/gnome/shell/ui/panel.js:1070:25
   
_updateBox@resource:///org/gnome/shell/ui/panel.js:1081:34
   
_updatePanel@resource:///org/gnome/shell/ui/panel.js:1027:14
   
_init@resource:///org/gnome/shell/ui/panel.js:836:14
   
_initializeUI@resource:///org/gnome/shell/ui/main.js:221:13
   
start@resource:///org/gnome/shell/ui/main.js:162:5
   @:1:47
Feb 24 15:25:39 kab gnome-shell[1013]: Execution of main.js threw exception: 
Script  threw an exception

-- 
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/1916701

Title:
  [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed,
  eventually comes up without Wayland support (only Xorg sessions
  offered)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1916701/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1916705] [NEW] glib2.0 >=2.67.3 breaks include from an extern C context

2021-02-23 Thread Christian Ehrhardt 
Public bug reported:

qemu now breaks in Hirsute (it didn't 23h ago)
Broken:
https://launchpadlibrarian.net/524654684/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-6ubuntu1_BUILDING.txt.gz

Good before:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4471/+packages

Error:

../../disas/arm-a64.cc
In file included from /usr/include/glib-2.0/glib/gmacros.h:241,
 from /usr/lib/x86_64-linux-gnu/glib-2.0/include/glibconfig.h:9,
 from /usr/include/glib-2.0/glib/gtypes.h:32,
 from /usr/include/glib-2.0/glib/galloca.h:32,
 from /usr/include/glib-2.0/glib.h:30,
 from /<>/qemu-5.2+dfsg/include/glib-compat.h:32,
 from /<>/qemu-5.2+dfsg/include/qemu/osdep.h:126,
 from ../../disas/arm-a64.cc:21:
/usr/include/c++/10/type_traits:56:3: error: template with C linkage
   56 |   template
  |   ^~~~
../../disas/arm-a64.cc:20:1: note: ‘extern "C"’ linkage started here
   20 | extern "C" {
  | ^~

Also in disas/nanomips.cpp, ...

And indeed disas/arm-a64.cc has:
 20 extern "C" {
 21 #include "qemu/osdep.h"
 22 #include "disas/dis-asm.h"
 23 }

Through the chain of headers as reported above this gets to the templates
in /usr/include/c++/10/type_traits which fails due to that.

So C++ constructs within a C scope which is this bug.

Upstream qemu has not recently changed yet for this.
The code is the same since 2016 via commit e78490c44: "disas/arm-a64.cc:
Include osdep.h first" by Peter Maydell.

But what was different before to break it now?
To find that I was comparing Hirsute vs Hirsute-proposed ...

It is indeed failing in -proposed but working in hirsute-release.

10.2.1-20ubuntu1 : bad

repro in broken build:
$ cd /root/qemu-5.2+dfsg/b/qemu
$ c++ -Ilibcommon.fa.p -I. -I../.. -Iqapi -Itrace -Iui -Iui/shader 
-I/usr/include/pixman-1 -I/usr/include/virgl -I/usr/include/libpng16 
-I/usr/include/spice-server -I/usr/include/spice-1 -I/usr/include/libusb-1.0 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gio-unix-2.0 
-I/usr/include/cacard -I/usr/include/nss -I/usr/include/nspr 
-I/usr/include/PCSC -I/usr/include/slirp -fdiagnostics-color=auto -pipe -Wall 
-Winvalid-pch -Wnon-virtual-dtor -std=gnu++11 -O2 -g -D__STDC_LIMIT_MACROS 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -U_FORTIFY_SOURCE -m64 -mcx16 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wundef 
-Wwrite-strings -fno-strict-aliasing -fno-common -fwrapv -g -O2 
-ffile-prefix-map=/root/qemu-5.2+dfsg=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wtype-limits 
-Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body 
-Wendif-labels -Wexpansion-to-defined -Wno-missing-include-dirs 
-Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -isystem 
/root/qemu-5.2+dfsg/linux-headers -isystem linux-headers -iquote 
/root/qemu-5.2+dfsg/tcg/i386 -iquote . -iquote /root/qemu-5.2+dfsg -iquote 
/root/qemu-5.2+dfsg/accel/tcg -iquote /root/qemu-5.2+dfsg/include -iquote 
/root/qemu-5.2+dfsg/disas/libvixl -pthread -fPIE -DSTRUCT_IOVEC_DEFINED 
-D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DNCURSES_WIDECHAR -MD -MQ 
libcommon.fa.p/disas_nanomips.cpp.o -MF libcommon.fa.p/disas_nanomips.cpp.o.d 
-o libcommon.fa.p/disas_nanomips.cpp.o -c ../../disas/nanomips.cpp

With that I have a test env...

Doko asked me to test
https://launchpad.net/ubuntu/+source/gcc-10/10.2.1-19ubuntu1/+build/20995220/+files/g++-10_10.2.1-19ubuntu1_amd64.deb
That fails as well, but also good as well as bad case have 10.10.2.1-20ubuntu1
It must be something else.

The difference were ~340 packages I was upgrading them to spot what broke it.
I eventually found glib 2.66 -> 2.67 to break it.

libglib2.0-0/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
libglib2.0-bin/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
libglib2.0-data/hirsute-proposed 2.67.4-1 all [upgradable from: 2.66.4-1]
libglib2.0-dev-bin/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
libglib2.0-dev/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]

Old:
/*
 * We can only use __typeof__ on GCC >= 4.8, and not when compiling C++. Since
 * __typeof__ is used in a few places in GLib, provide a pre-processor symbol
 * to factor the check out from callers.
 *
 * This symbol is private.
 */
#undef g_has_typeof
#if defined(__GNUC__) && (__GNUC__ > 4 || (__GNUC__ == 4 && __GNUC_MINOR__ >= 
8)) && !defined(__cplusplus)
#define g_has_typeof
#endif

New:
/*
 * We can only use __typeof__ on GCC >= 4.8, and not when compiling C++. Since
 * __typeof__ is used in a few places in GLib, provide a pre-processor symbol
 * to factor the check out from callers.
 *
 * This symbol is private.
 */
#undef glib_typeof
#if !defined(__cplusplus) && \
 ((defined(__GNUC__) && (__GNUC__ > 4 || (__GNUC__ == 4 && __GNUC_MINOR__ 

[Bug 1916701] [NEW] [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered)

2021-02-23 Thread Daniel van Vugt
Public bug reported:

When I installed the glib2.0 2.67.4-1 packages I consistently
encountered a black screen on boot. The login screen was missing/delayed
but eventually comes up without Wayland support (only Xorg sessions
offered).

** Affects: glib2.0 (Ubuntu)
 Importance: Critical
 Status: New

** Affects: gnome-session (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: hirsute regression-proposed

** Also affects: gnome-session (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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/1916701

Title:
  [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed,
  eventually comes up without Wayland support (only Xorg sessions
  offered)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1916701/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1916463] Re: gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]

2021-02-23 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1915870 ***
https://bugs.launchpad.net/bugs/1915870

** Summary changed:

- gnome-session-check-accelerated-gl-helper crashed with SIGSEGV
+ gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in 
cso_destroy_context() [r300_dri.so]

** This bug has been marked a duplicate of bug 1915870
   gnome session not starting (segfault in r300_dri.so)

-- 
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/1916463

Title:
  gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in
  cso_destroy_context() [r300_dri.so]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1916463/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1723130] Re: totem crashed with SIGSEGV in wl_proxy_add_listener() from wl_buffer_add_listener() from dri2_wl_swap_buffers_with_damage() from eglSwapBuffers() from _cogl_winsys_onscreen_swap_buff

2021-02-23 Thread Daniel van Vugt
No crashes reported after 18.04 so consider it fixed.

** Changed in: wayland (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: totem (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: mesa (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1723130

Title:
  totem crashed with SIGSEGV in wl_proxy_add_listener() from
  wl_buffer_add_listener() from dri2_wl_swap_buffers_with_damage() from
  eglSwapBuffers() from _cogl_winsys_onscreen_swap_buffers_with_damage()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1723130/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1726497] Re: nautilus crashed with SIGABRT in wl_abort() from wl_proxy_marshal_array_constructor_versioned()

2021-02-23 Thread Daniel van Vugt
No crashes reported after 19.04 so consider it fixed.

** Changed in: wayland (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: nautilus (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: gtk+3.0 (Ubuntu)
   Status: Confirmed => Fix Released

-- 
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/1726497

Title:
  nautilus crashed with SIGABRT in wl_abort() from
  wl_proxy_marshal_array_constructor_versioned()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1726497/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1912246] Re: [nvidia] gnome-shell freezes randomly after upgrading to groovy

2021-02-23 Thread Daniel van Vugt
Also, that "common freezing problem that happens with the Nvidia driver"
is being tracked upstream in
https://gitlab.gnome.org/GNOME/mutter/-/issues/1516

-- 
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/1912246

Title:
  [nvidia] gnome-shell freezes randomly after upgrading to groovy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1912246/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1912246] Re: [nvidia] gnome-shell freezes randomly after upgrading to groovy

2021-02-23 Thread Daniel van Vugt
Thanks. That log shows gnome-shell (for the login screen?) died because
Xorg went away:

Feb 23 07:30:15 gnome-shell[3625]: gnome-shell: Fatal IO error 11
(Resource temporarily unavailable) on X server :0.

Also there is evidence of a common freezing problem that happens with
the Nvidia driver:

Feb 23 08:31:40 gnome-shell[8333]: Window manager warning: MetaSyncRing: Sync 
object is not ready -- were events handled properly?
Feb 23 08:31:40 gnome-shell[8333]: Window manager warning: MetaSyncRing: Sync 
object is not ready -- were events handled properly?

Next please follow the instructions in comments #5 and #11 and attach
the resulting text files here in full. Please also check for crashes
from the system using these instructions:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: New => Incomplete

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1516
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1516

-- 
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/1912246

Title:
  [nvidia] gnome-shell freezes randomly after upgrading to groovy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1912246/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking

2021-02-23 Thread Daniel van Vugt
This bug does not appear to be related to Xfce, yet. If it does happen
in Xubuntu then please add a new task at the top of the page.

-- 
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/1532508

Title:
  Screen contents revealed briefly on resume, before even unlocking

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1532508/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1720262] Re: gnome-screenshot Actions don't work in Wayland

2021-02-23 Thread Coeur Noir
Hi,

Ubuntu Budgie 20.04 here - so no wayland and no gnome-shell.

Desktop Actions are still broken in gnome-screenshot.

If re-enable

Actions=screen-shot;window-shot;area-shot

area-shot has then no effect.

Other two seem ok but I was unable to modify options ( -p -d or else )
as seen in gnome-screenshot --help

Seems like it always want to act as soon as clicked - hence maybe why
the area-shot can't work ?

New ( ? ) issue → https://bugs.launchpad.net/ubuntu/+source/gnome-
screenshot/+bug/191

-- 
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/1720262

Title:
  gnome-screenshot Actions don't work in Wayland

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1720262/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1916463] Re: gnome-session-check-accelerated-gl-helper crashed with SIGSEGV

2021-02-23 Thread Mark Muth
** 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 gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1916463

Title:
  gnome-session-check-accelerated-gl-helper crashed with SIGSEGV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1916463/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1910838] Re: stopped working after latest update

2021-02-23 Thread Ken VanDine
** Tags removed: rls-ff-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator
in Ubuntu.
https://bugs.launchpad.net/bugs/1910838

Title:
  stopped working after latest update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1910838/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1905370] Re: Qt-based tray icons not displayed on start-up

2021-02-23 Thread Ken VanDine
** Tags removed: rls-ff-incoming rls-gg-incoming

** Also affects: gnome-shell-extension-appindicator (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: gnome-shell-extension-appindicator (Ubuntu Hirsute)
   Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
   Status: Triaged

** Also affects: gnome-shell-extension-appindicator (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Changed in: gnome-shell-extension-appindicator (Ubuntu Groovy)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: gnome-shell-extension-appindicator (Ubuntu Groovy)
   Importance: Undecided => Medium

** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator
in Ubuntu.
https://bugs.launchpad.net/bugs/1905370

Title:
  Qt-based tray icons not displayed on start-up

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/1905370/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1912246] Re: [nvidia] gnome-shell freezes randomly after upgrading to groovy

2021-02-23 Thread Ian Johnson
So I disabled both ubuntu-dock and the desktop icons extensions and
still see the freezes, here's a log of gnome-shell:
https://pastebin.ubuntu.com/p/CXCfTVtkMJ/

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: Incomplete => New

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => 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/1912246

Title:
  [nvidia] gnome-shell freezes randomly after upgrading to groovy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1912246/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking

2021-02-23 Thread ^rooker
I can also confirm this (Xubuntu 20.04.2).
Hardware is a HP Probook 430 G6.

lspci says this about the graphics card:
"Intel Corporation UHD Graphics 620"

Thanks in advance!

-- 
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/1532508

Title:
  Screen contents revealed briefly on resume, before even unlocking

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1532508/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed

2021-02-23 Thread Bug Watch Updater
** 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/1865226

Title:
  gdm-smartcard pam config needs to be updated for Ubuntu and installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1865226/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs