from:"experimancer"

[Desktop-packages] [Bug 1903382] Re: unable to add online account for google, flickr, microsoft, facebook

2022-08-03 Thread experimancer

Issue still present in Ubuntu 22.04 (Gnome 42.2): google-control-center
fails when adding account (Google etc) with following console error log:


Gdk-ERROR **: 20:44:19.527: The program 'WebKitWebProcess' received an X Window 
System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 202 error_code 2 request_code 151 (GLX) minor_code 34)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)


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

Title:
  unable to add online account for google, flickr, microsoft, facebook

Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of groovy. When I try to add Google, Flickr or Microsoft
  account, the loading window stays grey forever. When trying Facebook,
  i can see the loaded page for a second then switches to grey also.

  gnome-online-accounts:
Telepítve: 3.37.90-1ubuntu1
Jelölt:3.37.90-1ubuntu1

  
  I see these messages in journal:
  10:03:14 kernel: traps: WebKitWebProces[14044] trap int3 ip:7f510e1933cb 
sp:7ffd7c266ba0 error:0 in libglib-2.0.so.0.6600.1[7f510e153000+8b000]
  10:03:14 WebKitWebProces:backtrace from your debugger if you break on the 
gdk_x_error() function.)
  10:03:14 WebKitWebProces:backtrace from your debugger if you break on the 
gdk_x_error() function.)
  10:03:14 WebKitWebProces:variable to change this behavior. You can then 
get a meaningful
  10:03:14 WebKitWebProces:To debug your program, run it with the 
GDK_SYNCHRONIZE environment
  10:03:14 WebKitWebProces:that is, you will receive the error a while 
after causing it.
  10:03:14 WebKitWebProces:   (Note to programmers: normally, X errors are 
reported asynchronously;
  10:03:14 WebKitWebProces:   (Details: serial 221 error_code 2 request_code 
152 (GLX) minor_code 34)
  10:03:14 WebKitWebProces: The error was 'BadValue (integer parameter out of 
range for operation)'.
  10:03:14 WebKitWebProces: This probably reflects a bug in the program.
  10:03:14 WebKitWebProces: (WebKitWebProcess:2): Gdk-ERROR **: 10:03:14.587: 
The program 'WebKitWebProcess' received an X Window System error.
  10:03:14 WebKitWebProces: libGL error: failed to load driver: swrast
  10:03:14 WebKitWebProces: libGL error: MESA-LOADER: failed to open swrast 
(search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
  10:03:14 WebKitWebProces: libGL error: failed to load driver: radeonsi
  10:03:14 WebKitWebProces: libGL error: MESA-LOADER: failed to open radeonsi 
(search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
  10:03:14 WebKitWebProces: libGL error: failed to load driver: radeonsi
  10:03:14 WebKitWebProces: libGL error: MESA-LOADER: failed to open radeonsi 
(search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
  10:03:02 kernel: traps: eadedCompositor[14032] trap int3 ip:7f38f64183cb 
sp:7f387c5fde10 error:0 in libglib-2.0.so.0.6600.1[7f38f63d8000+8b000]
  10:03:02 WebKitWebProces:backtrace from your debugger if you break on the 
gdk_x_error() function.)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)

2019-01-09 Thread experimancer

Thanks @vanvugt for telling us that in which gnome-shell versions the
bug will be fixed.

However, this doesn't help us running Ubuntu 18.04 or 18.10 in
production now, both systems are unusable cause after about 15 to 60
minutes minutes of inactivity during which the lock-screen kicks in the
systems root disk will be 50 GB+ big which usually means that root file
system is full and host becomes unresponsive or crashes and/or
shutdowns.

The bug has been fixed in Gnome upstream 2 months, but still it hasn't
been backported or released in Gnome-shell version thats in use in
Ubuntu 18.04 LTS and 18.10. This is unacceptable.

I agree with many above (@jihunterwu etc,) that at the minimum
Ubuntu/Canonical should release a workaround for Ubuntu 18.04 LTS and
18.10 because this bug is so critical and affects *all* 18.04 and 18.10
installations making their daily use impossible!

If anyone has found a way to make existing 18.04 or 18.10 installations
usable, could you please post your workarounds or local fixes here,
thanks.

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

Title:
  gnome-shell filling up syslog with thousands of entries with stack
  traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224
  in cosmic)

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/602

  ---

  I'm seeing a several gigs (more than 70GB) a day of the following
  entries on syslog:

  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==

[Desktop-packages] [Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)

2018-12-24 Thread experimancer

Hi all,

In Ubuntu 18.10 this bug is still here, my /var/log/syslog went to 38 GB
in two hours.

$ uname -a
Linux plutot 4.18.0-13-generic #14-Ubuntu SMP Wed Dec 5 09:04:24 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

$ dpkg -l |grep gnome-shell
ii chrome-gnome-shell 10.1-1 all GNOME Shell extensions integration for web 
browsers
ii gnome-shell 3.30.1-2ubuntu1.18.10.1 amd64 graphical shell for the GNOME 
desktop
ii gnome-shell-common 3.30.1-2ubuntu1.18.10.1 all common files for the GNOME 
shell
ii gnome-shell-extension-appindicator  22-1  all 
AppIndicator/KStatusNotifierItem support for GNOME Shell
ii gnome-shell-extension-ubuntu-dock 63ubuntu1 all  Ubuntu Dock for GNOME Shell
ii  yaru-theme-gnome-shell 18.10.6 all Yaru GNOME Shell desktop theme from the 
Ubuntu Community

$ cat /var/log/syslog
... [millions of similar lines ]

Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #6   556ac620a830 i   
self-hosted:977 (7f36100f0280 @ 413)
Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: == Stack trace for context 
0x556ac2a75260 ==
Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #0   7fff170d96b0 b   
resource:///org/gnome/shell/ui/osdWindow.js:224 (7f35c7ac79d0 @ 273)
Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #1   7fff170d9780 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (7f36100b0b80 @ 71)
Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #2   7fff170d9840 b   
self-hosted:977 (7f36100f0280 @ 413)
Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #3   7fff170d9930 b   
resource:///org/gnome/gjs/modules/signals.js:128 (7f36100c18b0 @ 386)
Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #4   556ac620a998 i   
resource:///org/gnome/shell/ui/layout.js:538 (7f35c7a043a0 @ 127)
Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #5   556ac620a8f0 i   
resource:///org/gnome/gjs/modules/_legacy.js:82 (7f36100b0b80 @ 71)
Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #6   556ac620a830 i   
self-hosted:977 (7f36100f0280 @ 413)
Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: == Stack trace for context 
0x556ac2a75260 ==
Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #0   7fff170d96b0 b   
resource:///org/gnome/shell/ui/osdWindow.js:223 (7f35c7ac79d0 @ 231)
Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #1   7fff170d9780 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (7f36100b0b80 @ 71)
Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #2   7fff170d9840 b   
self-hosted:977 (7f36100f0280 @ 413)
Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #3   7fff170d9930 b   
resource:///org/gnome/gjs/modules/signals.js:128 (7f36100c18b0 @ 386)
Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #4   556ac620a998 i   
resource:///org/gnome/shell/ui/layout.js:538 (7f35c7a043a0 @ 127)
Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #5   556ac620a8f0 i   
resource:///org/gnome/gjs/modules/_legacy.js:82 (7f36100b0b80 @ 71)
Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #6   556ac620a830 i   
self-hosted:977 (7f36100f0280 @ 413)
Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: == Stack trace for context 
0x556ac2a75260 ==
Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #0   7fff170d96b0 b   
resource:///org/gnome/shell/ui/osdWindow.js:224 (7f35c7ac79d0 @ 273)
Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #1   7fff170d9780 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (7f36100b0b80 @ 71)
Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #2   7fff170d9840 b   
self-hosted:977 (7f36100f0280 @ 413)
Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #3   7fff170d9930 b   
resource:///org/gnome/gjs/modules/signals.js:128 (7f36100c18b0 @ 386)
Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #4   556ac620a998 i   
resource:///org/gnome/shell/ui/layout.js:538 (7f35c7a043a0 @ 127)
Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #5   556ac620a8f0 i   
resource:///org/gnome/gjs/modules/_legacy.js:82 (7f36100b0b80 @ 71)
Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #6   556ac620a830 i   
self-hosted:977 (7f36100f0280 @ 413)
Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: == Stack trace for context 
0x556ac2a75260 ==
...
...
..

I saw above that this has been fixed upstream, what is the ETA to have
the fix in 18.04 and 18.10?

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

Title:
  gnome-shell filling up syslog with thousands of entries with stack
  traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224
  in cosmic)

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/602

  ---

  I'm seeing a several gigs (more than 70GB) a day of the following
  entries on syslog:

  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042

[Desktop-packages] [Bug 1003950] Re: launcher does not show minimized update manager while clicked

2017-03-22 Thread experimancer

Might be related to this (the orig bug reappearing in Xenial/Unity
7.4.0): https://bugs.launchpad.net/update-notifier/+bug/1671540

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1003950

Title:
  launcher does not show minimized update manager while clicked

Status in Compiz:
  New
Status in Nouveau Xorg driver:
  New
Status in Unity:
  Fix Released
Status in Unity 5.0 series:
  Fix Released
Status in Unity 6.0 series:
  Fix Released
Status in Xenial Backports:
  New
Status in binary-driver-fglrx package in Ubuntu:
  New
Status in intel-linux-graphics-installer package in Ubuntu:
  New
Status in unity package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New
Status in binary-driver-fglrx source package in Precise:
  New
Status in intel-linux-graphics-installer source package in Precise:
  New
Status in unity source package in Precise:
  Fix Released
Status in update-manager source package in Precise:
  Confirmed
Status in xserver-xorg-video-nouveau source package in Precise:
  New
Status in binary-driver-fglrx source package in Quantal:
  Invalid
Status in intel-linux-graphics-installer source package in Quantal:
  Invalid
Status in unity source package in Quantal:
  Fix Released
Status in update-manager source package in Quantal:
  Won't Fix
Status in xserver-xorg-video-nouveau source package in Quantal:
  Invalid

Bug description:
  Found an easy way to reproduce it during brussels sprint:
  1. start deja-dup or update-manager
  2. kill -9 compiz; metacity
  3. compiz --replace

  
  ===

  Update manager is showing up in the dock but I can click on the icon
  all day and nothing happens. Similarly if I do Super-S or Super-W it
  doesn't show up anywhere.

  Even if I alt-tab to the application nothing shows up. This happens
  only when update manager runs on its own. If I kill it and then launch
  it myself it comes to the foreground just fine.

  I'm not 100% sure whether this is a unity, compiz, or update-manager
  bug but so far my bet is on unity.

  =Original Report=
  Bug #877444 is showing again in latest updates, please re-open it. This is 
the exact same problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1003950/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1003950] Re: launcher does not show minimized update manager while clicked

2017-03-22 Thread experimancer

The bug is still as described above in Ubuntu 16.04 Xenial in Zbook-
laptop with nvidia-4375 drivers in Unity 7.4.0.

** Also affects: xenial-backports
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1003950

Title:
  launcher does not show minimized update manager while clicked

Status in Compiz:
  New
Status in Nouveau Xorg driver:
  New
Status in Unity:
  Fix Released
Status in Unity 5.0 series:
  Fix Released
Status in Unity 6.0 series:
  Fix Released
Status in Xenial Backports:
  New
Status in binary-driver-fglrx package in Ubuntu:
  New
Status in intel-linux-graphics-installer package in Ubuntu:
  New
Status in unity package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New
Status in binary-driver-fglrx source package in Precise:
  New
Status in intel-linux-graphics-installer source package in Precise:
  New
Status in unity source package in Precise:
  Fix Released
Status in update-manager source package in Precise:
  Confirmed
Status in xserver-xorg-video-nouveau source package in Precise:
  New
Status in binary-driver-fglrx source package in Quantal:
  Invalid
Status in intel-linux-graphics-installer source package in Quantal:
  Invalid
Status in unity source package in Quantal:
  Fix Released
Status in update-manager source package in Quantal:
  Won't Fix
Status in xserver-xorg-video-nouveau source package in Quantal:
  Invalid

Bug description:
  Found an easy way to reproduce it during brussels sprint:
  1. start deja-dup or update-manager
  2. kill -9 compiz; metacity
  3. compiz --replace

  
  ===

  Update manager is showing up in the dock but I can click on the icon
  all day and nothing happens. Similarly if I do Super-S or Super-W it
  doesn't show up anywhere.

  Even if I alt-tab to the application nothing shows up. This happens
  only when update manager runs on its own. If I kill it and then launch
  it myself it comes to the foreground just fine.

  I'm not 100% sure whether this is a unity, compiz, or update-manager
  bug but so far my bet is on unity.

  =Original Report=
  Bug #877444 is showing again in latest updates, please re-open it. This is 
the exact same problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1003950/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1577049] Re: Switch user feature has disappeared from GNOME Shell since upgrade from 15.10 to 16.04

2016-10-28 Thread experimancer

** Tags removed: xenial

** Tags removed: verification-done yakkety
** Tags added: verification-failed xenial

** Tags added: verification-done yakkety

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

Title:
  Switch user feature has disappeared from GNOME Shell since upgrade
  from 15.10 to 16.04

Status in accountsservice:
  Unknown
Status in Ubuntu GNOME:
  Fix Released
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Xenial:
  Fix Released
Status in accountsservice package in Debian:
  Fix Released

Bug description:
  Impact
  ==
  Ubuntu 16.04's accountsservice was built without systemd support because 
systemd dropped libsystemd-login because that functionality was merged into 
libsystemd.

  At a minimum, this broke GNOME Shell's "Switch User" feature.

  Test Case
  =
  1. From Ubuntu GNOME 16.04.1, install the updated accountsservice packages.
  2. Add a user if necessary to ensure you have at least 2 user accounts 
configured.
  3. Reload gnome-shell. You can do this with Alt+F2 and entering the lower 
case letter r. Or you can log out of all user accounts and log back in.
  4. Click the system status area in the top right of GNOME Shell.
  5. Click your user name. "Switch User" should appear in the list.

  Regression Potential
  
  None.
  The one-line change to accountsservice's configure check was made in Debian's 
accountsservice 0.6.40-3 a year ago(!). The patch is upstreamed and was 
included in accountsservice 0.6.42 released in June.

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/1577049/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1903382] Re: unable to add online account for google, flickr, microsoft, facebook

[Desktop-packages] [Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)

[Desktop-packages] [Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)

[Desktop-packages] [Bug 1003950] Re: launcher does not show minimized update manager while clicked

[Desktop-packages] [Bug 1003950] Re: launcher does not show minimized update manager while clicked

[Desktop-packages] [Bug 1577049] Re: Switch user feature has disappeared from GNOME Shell since upgrade from 15.10 to 16.04

6 matches

Site Navigation

Mail list logo

Footer information