[Desktop-packages] [Bug 1841382] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice 0.6.55-0ubuntu5/6
** Changed in: accountsservice (Ubuntu) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- 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/1841382 Title: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice 0.6.55-0ubuntu5/6 Status in accountsservice package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781 https://errors.ubuntu.com/problem/0075340d0f484f9b5d37821d3023970cc12d I do not know what triggered the crash. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 25 20:45:09 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-08-24 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0 ?? () ?? () Title: gnome-shell crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1841382/+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 1841382] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice 0.6.55-0ubuntu5/6
If anyone experiences this crash repeatedly then please help us to debug it by downgrading to the last known non-crashing version: https://launchpad.net/ubuntu/+source/accountsservice/0.6.55-0ubuntu4 (click amd64) and tell us if that avoids the crash. If that still crashes then try: https://launchpad.net/ubuntu/+source/accountsservice/0.6.55-0ubuntu3 and so on. ** Tags added: rls-ee-incoming ** Tags removed: regression-release -- 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/1841382 Title: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice 0.6.55-0ubuntu5/6 Status in accountsservice package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781 https://errors.ubuntu.com/problem/0075340d0f484f9b5d37821d3023970cc12d I do not know what triggered the crash. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 25 20:45:09 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-08-24 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0 ?? () ?? () Title: gnome-shell crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1841382/+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 1842574] [NEW] Doesn't work mouse wheel A4tech Model: RFWOP-49
Public bug reported: After OS update doesn't work mouse wheel A4tech Model: RFWOP-49. Start-Date: 2019-09-04 09:09:24 Commandline: aptdaemon role='role-commit-packages' sender=':1.78' Install: linux-headers-4.4.0-161-generic:amd64 (4.4.0-161.189, automatic), linux-headers-4.4.0-161:amd64 (4.4.0-161.189, automatic), linux-modules-extra-4.15.0-60-generic:amd64 (4.15.0-60.67~16.04.1, automatic), linux-image-4.4.0-161-generic:amd64 (4.4.0-161.189, automatic), linux-headers-4.15.0-60:amd64 (4.15.0-60.67~16.04.1, automatic), linux-modules-4.15.0-60-generic:amd64 (4.15.0-60.67~16.04.1, automatic), linux-headers-4.15.0-60-generic:amd64 (4.15.0-60.67~16.04.1, automatic), linux-image-4.15.0-60-generic:amd64 (4.15.0-60.67~16.04.1, automatic), linux-modules-extra-4.4.0-161-generic:amd64 (4.4.0-161.189, automatic), linux-modules-4.4.0-161-generic:amd64 (4.4.0-161.189, automatic) Upgrade: linux-headers-generic:amd64 (4.4.0.159.167, 4.4.0.161.169), linux-libc-dev:amd64 (4.4.0-159.187, 4.4.0-161.189), libldap-2.4-2:amd64 (2.4.42+dfsg-2ubuntu3.6, 2.4.42+dfsg-2ubuntu3.7), linux-image-generic-hwe-16.04:amd64 (4.15.0.58.79, 4.15.0.60.81), linux-image-generic:amd64 (4.4.0.159.167, 4.4.0.161.169), linux-generic-hwe-16.04:amd64 (4.15.0.58.79, 4.15.0.60.81), linux-headers-generic-hwe-16.04:amd64 (4.15.0.58.79, 4.15.0.60.81), libsnapd-glib1:amd64 (1.47-0ubuntu0.16.04.0, 1.49-0ubuntu0.16.04.0), linux-generic:amd64 (4.4.0.159.167, 4.4.0.161.169), teamviewer:amd64 (14.4.2669, 14.5.5819) Remove: linux-image-4.4.0-159-generic:amd64 (4.4.0-159.187), linux-headers-4.4.0-159:amd64 (4.4.0-159.187), linux-modules-4.4.0-159-generic:amd64 (4.4.0-159.187), linux-headers-4.4.0-159-generic:amd64 (4.4.0-159.187), linux-modules-extra-4.4.0-159-generic:amd64 (4.4.0-159.187) End-Date: 2019-09-04 09:14:06 Start-Date: 2019-09-04 09:36:01 Commandline: aptdaemon role='role-upgrade-system' sender=':1.66' Upgrade: libdns-export162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.14, 1:9.10.3.dfsg.P4-8ubuntu1.15), libisccfg140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.14, 1:9.10.3.dfsg.P4-8ubuntu1.15), snapd:amd64 (2.39.2ubuntu0.2, 2.40), bind9-host:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.14, 1:9.10.3.dfsg.P4-8ubuntu1.15), dnsutils:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.14, 1:9.10.3.dfsg.P4-8ubuntu1.15), libisc160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.14, 1:9.10.3.dfsg.P4-8ubuntu1.15), libisc-export160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.14, 1:9.10.3.dfsg.P4-8ubuntu1.15), liblwres141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.14, 1:9.10.3.dfsg.P4-8ubuntu1.15), ubuntu-core-launcher:amd64 (2.39.2ubuntu0.2, 2.40), libdns162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.14, 1:9.10.3.dfsg.P4-8ubuntu1.15), libisccc140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.14, 1:9.10.3.dfsg.P4-8ubuntu1.15), libbind9-140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.14, 1:9.10.3.dfsg.P4-8ubuntu1.15) End-Date: 2019-09-04 09:36:08 Start-Date: 2019-09-04 10:17:53 Commandline: aptdaemon role='role-install-packages' sender=':1.66' Install: unity-tweak-tool:amd64 (0.0.7ubuntu2) End-Date: 2019-09-04 10:17:55 Start-Date: 2019-09-04 11:03:58 Commandline: apt-get install xserver-xorg-input-mouse-lts-vivid Requested-By: maxim (1000) Install: xserver-xorg-input-mouse-lts-vivid:amd64 (3:13) End-Date: 2019-09-04 11:03:59 Start-Date: 2019-09-04 11:04:20 Commandline: apt-get install xserver-xorg-input-mouse-lts-* Requested-By: maxim (1000) Install: xserver-xorg-input-mouse-lts-wily:amd64 (3:13), xserver-xorg-input-mouse-lts-utopic:amd64 (3:13) End-Date: 2019-09-04 11:04:21 Start-Date: 2019-09-04 11:06:05 Commandline: apt-get remove xserver-xorg-input-mouse-lts-* Requested-By: maxim (1000) Remove: xserver-xorg-input-mouse-lts-vivid:amd64 (3:13), xserver-xorg-input-mouse-lts-wily:amd64 (3:13), xserver-xorg-input-mouse-lts-utopic:amd64 (3:13) End-Date: 2019-09-04 11:06:06 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evince 3.18.2-1ubuntu4.6 ProcVersionSignature: Ubuntu 4.15.0-60.67~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-60-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 4 11:15:15 2019 InstallationDate: Installed on 2018-05-14 (477 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1842574 Title: Doesn't work mouse wheel A4tech Model: RFWOP-49 Status in evince package in Ubuntu: New Bug description: After OS update doesn't work mouse wheel A4tech Model: RFWOP-49. Start-Date: 2019-09-04 09:09:24 Commandline: aptdaemon role='role-commit-packages' sender=':1.78' Install:
[Desktop-packages] [Bug 1842538] Re: /usr/bin/gnome-shell:6:__GI_raise:__GI_abort:wl_abort:wl_closure_marshal:handle_array
*** This bug is a duplicate of bug 1842442 *** https://bugs.launchpad.net/bugs/1842442 ** This bug has been marked a duplicate of private bug 1842442 -- 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/1842538 Title: /usr/bin/gnome- shell:6:__GI_raise:__GI_abort:wl_abort:wl_closure_marshal:handle_array Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.33.91-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/2dbf01057d5a6583bb2cc7899ab6b33d10d6bbd6 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/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1842538/+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 1842538] [NEW] /usr/bin/gnome-shell:6:__GI_raise:__GI_abort:wl_abort:wl_closure_marshal:handle_array
*** This bug is a duplicate of bug 1842442 *** https://bugs.launchpad.net/bugs/1842442 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.33.91-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/2dbf01057d5a6583bb2cc7899ab6b33d10d6bbd6 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-shell (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic eoan kylin-18.04 -- 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/1842538 Title: /usr/bin/gnome- shell:6:__GI_raise:__GI_abort:wl_abort:wl_closure_marshal:handle_array Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.33.91-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/2dbf01057d5a6583bb2cc7899ab6b33d10d6bbd6 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/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1842538/+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 1842442] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from wl_abort() from wl_closure_marshal() from handle_array()
Tracking in: https://errors.ubuntu.com/problem/2dbf01057d5a6583bb2cc7899ab6b33d10d6bbd6 ** Description changed: + https://errors.ubuntu.com/problem/2dbf01057d5a6583bb2cc7899ab6b33d10d6bbd6 + Session suddenly stopped and came back to login screen, all opened windows lost. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 3 16:19:55 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-06-16 (443 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180611) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: - LANG=fr_FR.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: - __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 - __GI_abort () at abort.c:79 - ?? () - ?? () from /usr/lib/x86_64-linux-gnu/libwayland-server.so.0 - ?? () from /usr/lib/x86_64-linux-gnu/libwayland-server.so.0 + __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 + __GI_abort () at abort.c:79 + ?? () + ?? () from /usr/lib/x86_64-linux-gnu/libwayland-server.so.0 + ?? () from /usr/lib/x86_64-linux-gnu/libwayland-server.so.0 Title: gnome-shell crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to eoan on 2019-06-10 (84 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** Information type changed from Private to Public -- 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/1842442 Title: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from wl_abort() from wl_closure_marshal() from handle_array() Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/2dbf01057d5a6583bb2cc7899ab6b33d10d6bbd6 Session suddenly stopped and came back to login screen, all opened windows lost. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 3 16:19:55 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-06-16 (443 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180611) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () ?? () from /usr/lib/x86_64-linux-gnu/libwayland-server.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libwayland-server.so.0 Title: gnome-shell crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to eoan on 2019-06-10 (84 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1842442/+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 1841382] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice
Also tracking in: https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f ** Summary changed: - Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() from g_hash_table_lookup() from console_kit_session_default_init() with accountsservice 0.6.55-0ubuntu5 + Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice ** Description changed: + https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f + I do not know what triggered the crash. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 25 20:45:09 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-08-24 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=de_DE.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: - g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 - ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0 - ?? () - ?? () + g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 + ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0 + ?? () + ?? () Title: gnome-shell crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** Description changed: https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f + https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781 I do not know what triggered the crash. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 25 20:45:09 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-08-24 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0 ?? () ?? () Title: gnome-shell crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: -- 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/1841382 Title: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice 0.6.55-0ubuntu5/6 Status in accountsservice package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781 https://errors.ubuntu.com/problem/0075340d0f484f9b5d37821d3023970cc12d I do not know what triggered the crash. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 25 20:45:09 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-08-24 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from
[Desktop-packages] [Bug 1841382] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice
And by the looks of it: https://errors.ubuntu.com/problem/0075340d0f484f9b5d37821d3023970cc12d ** Description changed: https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781 + https://errors.ubuntu.com/problem/0075340d0f484f9b5d37821d3023970cc12d I do not know what triggered the crash. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 25 20:45:09 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-08-24 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0 ?? () ?? () Title: gnome-shell crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** Changed in: accountsservice (Ubuntu) Importance: Medium => High ** Tags added: regression-release ** Summary changed: - Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice + Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice 0.6.55-0ubuntu5 ** Summary changed: - Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice 0.6.55-0ubuntu5 + Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice 0.6.55-0ubuntu5/6 -- 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/1841382 Title: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice 0.6.55-0ubuntu5/6 Status in accountsservice package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781 https://errors.ubuntu.com/problem/0075340d0f484f9b5d37821d3023970cc12d I do not know what triggered the crash. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 25 20:45:09 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-08-24 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0 ?? () ?? () Title: gnome-shell crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1841382/+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 1842534] [NEW] /usr/bin/gnome-shell:11:g_str_hash:g_hash_table_lookup:update_user:on_user_changed:on_user_changed
*** This bug is a duplicate of bug 1841382 *** https://bugs.launchpad.net/bugs/1841382 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.33.91-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f 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-shell (Ubuntu) Importance: Undecided Status: New ** Tags: eoan -- 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/1842534 Title: /usr/bin/gnome- shell:11:g_str_hash:g_hash_table_lookup:update_user:on_user_changed:on_user_changed Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.33.91-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f 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/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1842534/+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 1842414] Re: gnome-shell crashed with SIGSEGV in g_str_hash()
*** This bug is a duplicate of bug 1841382 *** https://bugs.launchpad.net/bugs/1841382 This crash looks suspiciously similar to bug 1841382. ** Information type changed from Private to Public ** Summary changed: - gnome-shell crashed with SIGSEGV in g_str_hash() + gnome-shell crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user() ** Also affects: accountsservice (Ubuntu) Importance: Undecided Status: New ** Changed in: accountsservice (Ubuntu) Status: New => Confirmed ** Changed in: accountsservice (Ubuntu) Importance: Undecided => Medium ** Summary changed: - gnome-shell crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user() + gnome-shell crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user() from on_user_changed() ** Description changed: + https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f + Laptop was asleep (Dell XPS13 9370). I plugged it into a thunderbolt 3 dock (Caldigit TS3+). Keyboard rattling had no apparent effect at waking it up. Opened lid to see lock screen, keyboard still non-responsive. Unlocked using laptop's own keyboard. Logged in to see this and some other crashes being reported currently. As description is what i was doing and it was the same for all crashes, am copy-pasting that part from first bug #1842412 then adding notes. In this case, it seems to have relaunched as session is continuing and gnome-shell is running. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 2 23:31:05 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-09-11 (356 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: - LANG=en_GB.UTF-8 - LANGUAGE=en_GB:en - PATH=(custom, user) - SHELL=/usr/bin/zsh - XDG_RUNTIME_DIR= + LANG=en_GB.UTF-8 + LANGUAGE=en_GB:en + PATH=(custom, user) + SHELL=/usr/bin/zsh + XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: - __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 - () - () at /lib/x86_64-linux-gnu/libc.so.6 - g_str_hash () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_hash_table_lookup () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 + () + () at /lib/x86_64-linux-gnu/libc.so.6 + g_str_hash () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_hash_table_lookup () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in __GI_raise() UpgradeStatus: Upgraded to eoan on 2019-07-16 (48 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: -- 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/1842414 Title: gnome-shell crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user() from on_user_changed() Status in accountsservice package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f Laptop was asleep (Dell XPS13 9370). I plugged it into a thunderbolt 3 dock (Caldigit TS3+). Keyboard rattling had no apparent effect at waking it up. Opened lid to see lock screen, keyboard still non- responsive. Unlocked using laptop's own keyboard. Logged in to see this and some other crashes being reported currently. As description is what i was doing and it was the same for all crashes, am copy-pasting that part from first bug #1842412 then adding notes. In this case, it seems to have relaunched as session is continuing and gnome-shell is running. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 2 23:31:05 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-09-11 (356 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, user) SHELL=/usr/bin/zsh XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 Signal: 11 SourcePackage: gnome-shell
[Desktop-packages] [Bug 1842534] Re: /usr/bin/gnome-shell:11:g_str_hash:g_hash_table_lookup:update_user:on_user_changed:on_user_changed
*** This bug is a duplicate of bug 1841382 *** https://bugs.launchpad.net/bugs/1841382 ** This bug has been marked a duplicate of bug 1842414 gnome-shell crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user() from on_user_changed() ** This bug is no longer a duplicate of bug 1842414 gnome-shell crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user() from on_user_changed() ** This bug has been marked a duplicate of bug 1841382 Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice -- 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/1842534 Title: /usr/bin/gnome- shell:11:g_str_hash:g_hash_table_lookup:update_user:on_user_changed:on_user_changed Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.33.91-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f 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/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1842534/+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 1842414] Re: gnome-shell crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user() from on_user_changed()
*** This bug is a duplicate of bug 1841382 *** https://bugs.launchpad.net/bugs/1841382 Also tracking in: https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f ** This bug has been marked a duplicate of bug 1841382 Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice -- 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/1842414 Title: gnome-shell crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user() from on_user_changed() Status in accountsservice package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f Laptop was asleep (Dell XPS13 9370). I plugged it into a thunderbolt 3 dock (Caldigit TS3+). Keyboard rattling had no apparent effect at waking it up. Opened lid to see lock screen, keyboard still non- responsive. Unlocked using laptop's own keyboard. Logged in to see this and some other crashes being reported currently. As description is what i was doing and it was the same for all crashes, am copy-pasting that part from first bug #1842412 then adding notes. In this case, it seems to have relaunched as session is continuing and gnome-shell is running. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 2 23:31:05 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-09-11 (356 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, user) SHELL=/usr/bin/zsh XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 () () at /lib/x86_64-linux-gnu/libc.so.6 g_str_hash () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in __GI_raise() UpgradeStatus: Upgraded to eoan on 2019-07-16 (48 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1842414/+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 1842535] [NEW] /usr/lib/gdm3/gdm-session-worker:11:g_str_hash:g_hash_table_lookup:update_user:on_user_changed:on_user_changed
*** This bug is a duplicate of bug 1841382 *** https://bugs.launchpad.net/bugs/1841382 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gdm3. This problem was most recently seen with package version 3.33.90-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781 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: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: disco eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1842535 Title: /usr/lib/gdm3/gdm-session- worker:11:g_str_hash:g_hash_table_lookup:update_user:on_user_changed:on_user_changed Status in gdm3 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gdm3. This problem was most recently seen with package version 3.33.90-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781 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/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1842535/+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 1841894] Re: Wayland: Image of mouse cursor left on screen after unlock
** Changed in: mutter (Ubuntu) Status: Incomplete => New ** Tags added: cursor -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1841894 Title: Wayland: Image of mouse cursor left on screen after unlock Status in mutter package in Ubuntu: New Bug description: Gnome 3 desktop Multi-monitor setup with one screen rotated right into portrait mode *Experimental* fractional scaling on Wayland with different scaling on each monitor. Configured using: ~~~ gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']" ~~~ After wake from screen lock I often observe an "image" of an enlarged rotated mouse pointer on the second (rotated) monitor which doesn't move and doesn't appear on a screenshot. It overlays all other screen in formation and cannot be erased by moving the mouse over the area. Depending on where the mouse cursor was when sleeping it seems to appear in one of two places, either towards the bottom left or top right. After some time a block around the cursor image gets "corrupted". This behaviour is not observed if logging in to a X11 session Because this doesn't show up on a screenshot I have included a photo, which also shows the monitor setup. Description: Ubuntu 19.04 Release: 19.04 mutter: Installed: 3.32.2+git20190711-2ubuntu1~19.04.1 Candidate: 3.32.2+git20190711-2ubuntu1~19.04.1 Version table: *** 3.32.2+git20190711-2ubuntu1~19.04.1 500 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.32.0+git20190410-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-03-08 (178 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: mutter 3.32.2+git20190711-2ubuntu1~19.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Tags: wayland-session disco Uname: Linux 5.0.0-27-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-04-21 (134 days ago) UserGroups: adbusers adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1841894/+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 1683383]
very good post. http://www.winmilliongame.com http://www.gtagame100.com http://www.subway-game.com http://www.zumagame100.com -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1683383 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen) Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Confirmed Status in xorg package in Debian: New Bug description: From duplicate bug 1720364 report. Steps to reproduce: 1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 17.10 or 18.04 LTS. 2. Set-up two keyboard layouts - English and Russian 3. Set as keyboard layout switcher in mate-control-center 4. Try to use shortcuts starting from : 4.1. Open Firefox, open new tab, go to some site in it, close tab, try to click to restore closed tab. 4.2. Open mate-terminal, try to open new tab with , or copy (), or paste (). 4.3. Open pluma, write some text, try to navigate in it with . Expected results: switches keyboard layout, shortcuts starting from work normally. Actual results: switches keyboard layout, shortcuts starting from do not work. Notes: 1. Ubuntu 16.04 LTS (Xorg 1.18.4) with Marco and Compton work normally with keyboard layout switcher. 2. This problem was discovered before on 13.10, 14.04 and other modern versions with GNOME desktop (Metacity and Compiz) - see bug 1245473. --- Original description below: This is a reopen of bug #36812, which has reappeared in Kubuntu 17.04 Zesty Zapus. This is a bug about shortcuts mapped to combinations which include each other. For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to open a new terminal), then we are practically unable to use the second shortcut; this is what happens: Ctrl press (nothing happens) Shift press (keyboard layout change) N (a simple N appears, since a shortcut has already fired) The expected behavior is to fire shortcuts on the release (not on press) of the special keys (ctrl,shift,alt, etc) which is also how Windows behave. This is a serious problem for bilingual layouts, typically using Alt+Shift or Ctrl+Shift for keyboard layout change. Apparently, the bug has reappeared after the patch that used to fix the problem (208_switch_on_release.diff) has been removed from X.Org 1.19 packages. There is an updated patch in the upstream ticket https://bugs.freedesktop.org/show_bug.cgi?id=865 (link to the attachment: https://bugs.freedesktop.org/attachment.cgi?id=129861). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xserver-xorg-core 2:1.19.3-1ubuntu1 Uname: Linux 4.9.0-22.1-liquorix-amd64 x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 17 17:46:35 2017 InstallationDate: Installed on 2015-05-01 (716 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: xorg-server UpgradeStatus: Upgraded to zesty on 2017-04-16 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1683383/+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 1817537] Update Released
The verification of the Stable Release Update for libsoup2.4 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 Desktop Packages, which is subscribed to libsoup2.4 in Ubuntu. https://bugs.launchpad.net/bugs/1817537 Title: libsoup should support ntlmv2 Status in libsoup2.4 package in Ubuntu: Fix Released Status in libsoup2.4 source package in Bionic: Fix Released Bug description: * Impact Without NTLMv2 support evolution-ews can't connect to some exchange servers * Test case Try connecting from evolution-ews to an exchange server which enforces NTLMV2 * Regression potential The change adds extra cases in the ntlm handling support, it should impact existing feature but check out for any potential regression in libsoup user (check at least evolution and epiphany-browser). Note that the patch include additional code tests --- Our Exchange admins recently made NTLMv2 obligatory. Since then interaction with Exchange through Evolution isn't possible anymore. In newer versions of libsoup that has been implemented, see https://gitlab.gnome.org/GNOME/evolution-ews/issues/38 Could that be backported to Ubuntu 18.04? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsoup2.4-1 2.62.1-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Feb 25 12:10:26 2019 SourcePackage: libsoup2.4 UpgradeStatus: Upgraded to bionic on 2018-09-27 (150 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1817537/+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 1817537] Re: libsoup should support ntlmv2
This bug was fixed in the package libsoup2.4 - 2.62.1-1ubuntu0.3 --- libsoup2.4 (2.62.1-1ubuntu0.3) bionic; urgency=medium * debian/patches/git_ntlmv2_support.patch: - update with an extra upstream tweak libsoup2.4 (2.62.1-1ubuntu0.2) bionic; urgency=medium * debian/patches/git_ntlmv2_support.patch, debian/patches/git_ntlmv2_test.patch: - include upstream changes for NTLMv2 responses support, that's required for evolution-ews to be able to connect some exchange servers, also include corresponding code tests (lp: #1817537) -- Sebastien Bacher Tue, 16 Jul 2019 20:36:23 +0200 ** Changed in: libsoup2.4 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsoup2.4 in Ubuntu. https://bugs.launchpad.net/bugs/1817537 Title: libsoup should support ntlmv2 Status in libsoup2.4 package in Ubuntu: Fix Released Status in libsoup2.4 source package in Bionic: Fix Released Bug description: * Impact Without NTLMv2 support evolution-ews can't connect to some exchange servers * Test case Try connecting from evolution-ews to an exchange server which enforces NTLMV2 * Regression potential The change adds extra cases in the ntlm handling support, it should impact existing feature but check out for any potential regression in libsoup user (check at least evolution and epiphany-browser). Note that the patch include additional code tests --- Our Exchange admins recently made NTLMv2 obligatory. Since then interaction with Exchange through Evolution isn't possible anymore. In newer versions of libsoup that has been implemented, see https://gitlab.gnome.org/GNOME/evolution-ews/issues/38 Could that be backported to Ubuntu 18.04? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsoup2.4-1 2.62.1-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Feb 25 12:10:26 2019 SourcePackage: libsoup2.4 UpgradeStatus: Upgraded to bionic on 2018-09-27 (150 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1817537/+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 1766495] Re: "your libfreerdp does not support h264"
la solucion esta aqui, https://theoscaargomes.wordpress.com/2018/05/04/solucionando-erro- remmina-linux-ubuntu-18-04/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1766495 Title: "your libfreerdp does not support h264" Status in remmina package in Ubuntu: Confirmed Bug description: When I try to connect via RDP, Remmina gives this error: "You requested an h264 GFX mode for server , but your libfreerdp does not support h264. Please check color depth settings." However, (1) I don't see any color depth settings in Remmina GUI, and (2) ubuntu-restricted-extras is installed. I have libx264-152 version 2:0.152.2854+gite9a5903-2. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: remmina 1.2.0-rcgit.29+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: KDE Date: Tue Apr 24 09:29:44 2018 InstallationDate: Installed on 2018-03-23 (31 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) SourcePackage: remmina UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1766495/+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 1842519] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1841794 *** https://bugs.launchpad.net/bugs/1841794 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1841794, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1842519/+attachment/5286578/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1842519/+attachment/5286580/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1842519/+attachment/5286584/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1842519/+attachment/5286585/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1842519/+attachment/5286586/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1842519/+attachment/5286588/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1842519/+attachment/5286589/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1841794 gnome-shell crashed with SIGTRAP in g_log_default_handler() ... from ObjectInstance::~ObjectInstance() [usually logging "Finalizing wrapper for an already freed object of type: Clutter.PropertyTransition"] ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1842519 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 19.10 Clean Install Gnome 3.33.91 Intel® HD Graphics 520 (Skylake GT2) / NV118 Nouveau Clean ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 3 16:26:38 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-09-03 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190903) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1842519/+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 1842260] Re: lock screen does not fill screen when two monitors are in use
I just tried Ubuntu Budgie 18.04.3 and while it does use entire primary display on the lock screen, it struggles to use the secondary display at all while a live system. I would install it next to my Xubuntu installation and give it a shot to see if I could get I could get it working properly but I would rather not risk breaking it since I have a knack for borking things. I honestly think the live system issue is down to it using nouveau instead of the proprietary Nvidia Drivers. But that's besides the point. I'll try installing the Budgie desktop on my Xubuntu installation to see if that helps anything. I don't have very high hopes but it's worth a shot, unless someone can provide me with an alternative approach. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1842260 Title: lock screen does not fill screen when two monitors are in use Status in gnome-screensaver package in Ubuntu: New Bug description: Problem occurs with all kernels tried (4.15, 5.0, 5.1, and 5.2), and no matter what the resolution of the second monitor is set to. When system is locked, the lock screen takes up less than 1/4 of the primary monitor's area. It is expected the lock screen at least fill the entire primary display. output of lsb_release -rd: Description: Ubuntu 18.04.3 LTS Release: 18.04 Package version: 0.9.6.1 No log files where found in /tmp to indicate any problems occurred. Attached is the seat0-greeter.log file found in /var/log/lightdm. You can see in the log file on lines 44 and 45 that it knows the main monitor is 1920x1080, and it sets the MainWindow to this same resolution during start up. However, on lines 125-127 that it gets 720x480 to use for the MainWindow. I have no idea where it got this resolution since Monitor :0 is 1920x1080 and Monitor :1 is 1360x768, and I get the same results when I set both monitors to 1920x1080 (you can see this on lines 206-208). Please note that I plugged in the secondary monitor after I logged in. This was done to work around an unrelated problem with Xfce font scaling. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: budgie-lightdm-theme 0.9.6.1 Uname: Linux 5.2.0-11.1-liquorix-amd64 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Sep 1 19:45:28 2019 InstallationDate: Installed on 2019-06-30 (63 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: budgie-artwork UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1842260/+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 1842497] [NEW] /usr/bin/pkttyagent:5:on_request:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist:g_signal_emit_by_name
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding policykit-1. This problem was most recently seen with package version 0.105-21ubuntu0.4, the problem page at https://errors.ubuntu.com/problem/4f940970302056098474b4823b71ee9602e24c84 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: policykit-1 (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic cosmic wily xenial yakkety zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1842497 Title: /usr/bin/pkttyagent:5:on_request:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist:g_signal_emit_by_name Status in policykit-1 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding policykit-1. This problem was most recently seen with package version 0.105-21ubuntu0.4, the problem page at https://errors.ubuntu.com/problem/4f940970302056098474b4823b71ee9602e24c84 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/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1842497/+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 1842491] Re: Xorg crashed with SIGSEGV
*** This bug is a duplicate of bug 1681084 *** https://bugs.launchpad.net/bugs/1681084 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1681084, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1842491/+attachment/5286525/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1842491/+attachment/5286528/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1842491/+attachment/5286535/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1842491/+attachment/5286537/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1842491/+attachment/5286538/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1842491/+attachment/5286539/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1842491/+attachment/5286540/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1681084 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1842491 Title: Xorg crashed with SIGSEGV Status in xorg-server package in Ubuntu: New Bug description: Apps being used at the time: Jupyter Lab through mozilla, mendeley desktop ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu4.3 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Sep 3 23:41:17 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.67, 4.15.0-55-generic, x86_64: installed nvidia, 390.67, 4.15.0-58-generic, x86_64: installed DpkgLog: ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 530 [17aa:3802] Subsystem: Lenovo GM107M [GeForce GTX 960M] [17aa:3802] InstallationDate: Installed on 2018-05-09 (482 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 174f:14e8 Syntek Bus 001 Device 008: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80NV ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=afcac55f-fa7b-4d00-8aa7-989d032de3eb ro scsi_mod.scan=sync quiet splash vt.handoff=1 SegvAnalysis: Segfault happened at: 0x5606e572f0b0:mov0x40(%rbx),%rax PC (0x5606e572f0b0) ok source "0x40(%rbx)" (0x0020) not located in a known VMA region (needed readable region)! destination "%rax" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: xorg-server StacktraceTop: () miPointerSetPosition () () () GetPointerEvents () Title: Xorg crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 01/11/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN28WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 5A dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-15ISK dmi.modalias:
[Desktop-packages] [Bug 1745799] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler() from wl_log() ["wl_registry@2: error 0: invalid global wl_ou
** Tags added: eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1745799 Title: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler() from wl_log() ["wl_registry@2: error 0: invalid global wl_output (20)\n"] Status in xorg-server package in Ubuntu: Confirmed Bug description: Crashes when plugging in Dell WD15 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.5-0ubuntu2 Uname: Linux 4.15.0-rc8+ x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CompositorRunning: None CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 27 22:12:41 2018 DistUpgraded: 2018-01-26 09:36:11,455 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Device [8086:591e] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:077a] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:5690 Realtek Semiconductor Corp. Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9365 ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -core -listen 4 -listen 5 -displayfd 6 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-rc8+ root=UUID=fe08dba8-d746-4a04-82c9-cac962e9321c ro quiet splash wmi.debug_dump_wdg=1 vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0 Title: Xwayland crashed with SIGABRT in OsAbort() UpgradeStatus: Upgraded to bionic on 2018-01-26 (1 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo dmi.bios.date: 12/05/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.21 dmi.board.name: 0DVT6M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.21:bd12/05/2017:svnDellInc.:pnXPS139365:pvr:rvnDellInc.:rn0DVT6M:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9365 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1 version.libdrm2: libdrm2 2.4.89-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1745799/+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 1842490] Re: Xwayland crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1745799 *** https://bugs.launchpad.net/bugs/1745799 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1745799, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1842490/+attachment/5286503/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1842490/+attachment/5286506/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1842490/+attachment/5286514/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1842490/+attachment/5286516/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1842490/+attachment/5286517/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1842490/+attachment/5286518/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1842490/+attachment/5286519/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1745799 Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler() from wl_log() ["wl_registry@2: error 0: invalid global wl_output (20)\n"] ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1842490 Title: Xwayland crashed with SIGABRT in OsAbort() Status in xorg-server package in Ubuntu: New Bug description: Session crashed suddenly and came back to login screen. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: xwayland 2:1.20.5+git20190820-0ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 3 20:00:10 2019 DistUpgraded: 2019-06-10 22:54:14,861 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « ./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8)) DistroCodename: eoan DistroVariant: ubuntu ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1002:683d] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [174b:e244] InstallationDate: Installed on 2018-06-16 (443 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180611) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcCmdline: /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1000/.mutter-Xwaylandauth.BAEE7Z -listen 4 -listen 5 -displayfd 6 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-15-generic root=UUID=fc4f0329-57f3-4a60-8566-ce094d6324bb ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0 Title: Xwayland crashed with SIGABRT in OsAbort() UpgradeStatus: Upgraded to eoan on 2019-06-10 (84 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 02/06/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FEi dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-D3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFEi:bd02/06/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled
[Desktop-packages] [Bug 1721248] Re: "Totem could not get a screenshot of the video. This is not supposed to happen; please file a bug report."
** Changed in: mutter Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1721248 Title: "Totem could not get a screenshot of the video. This is not supposed to happen; please file a bug report." Status in Mutter: Fix Released Status in mutter package in Ubuntu: Confirmed Bug description: https://gitlab.gnome.org/GNOME/mutter/issues/146 --- I try to get a screenshot from my video and totem shows a message saying it could not get a screenshot of the video and suggesting to open a bug. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: totem 3.25.90.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 4 14:54:16 2017 InstallationDate: Installed on 2017-09-29 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1721248/+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
Re: [Desktop-packages] [Bug 1831369] Re: Gnome Shell pauses and stutters while waiting (several seconds) for web browsers to launch on a Celeron N3350.
I use my weak laptop carefully. I make such stress tests only for Ubuntu check to make it better. пн, 2 сент. 2019 г. в 05:15, Daniel van Vugt : > In the meantime I recommend only using one web browser at a time on this > machine, and keeping the number of open tabs to a minimum. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1831369 > > Title: > Gnome Shell pauses and stutters while waiting (several seconds) for > web browsers to launch on a Celeron N3350. > > Status in gnome-shell package in Ubuntu: > New > > Bug description: > My laptop: HP 250 G6, Intel Celeron N3350, integrated video card, 4 GB > RAM, Ubuntu 19.04 > Details in my video: https://photos.app.goo.gl/ERUaSS6Qc8jFhHnn9 > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: gnome-shell 3.32.0+git20190410-1ubuntu1 > ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 > Uname: Linux 5.0.0-15-generic x86_64 > ApportVersion: 2.20.10-0ubuntu27 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Sun Jun 2 14:32:17 2019 > DisplayManager: gdm3 > GsettingsChanges: >b'org.gnome.shell' b'app-picker-view' b'uint32 1' >b'org.gnome.shell' b'command-history' redacted by apport >b'org.gnome.shell' b'favorite-apps' redacted by apport >b'org.gnome.shell' b'enabled-extensions' b"['desktop-icons@csoriano']" >b'org.gnome.desktop.interface' b'gtk-im-module' > b"'gtk-im-context-simple'" > InstallationDate: Installed on 2019-05-31 (1 days ago) > InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) > ProcEnviron: >LANGUAGE=ru_UA:ru >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=ru_UA.UTF-8 >SHELL=/bin/bash > SourcePackage: gnome-shell > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1831369/+subscriptions > -- 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/1831369 Title: Gnome Shell pauses and stutters when other programs like Firefox are using significant CPU on a Celeron N3350 Status in gnome-shell package in Ubuntu: New Bug description: My laptop: HP 250 G6, Intel Celeron N3350, integrated video card, 4 GB RAM, Ubuntu 19.04 Details in my video: https://photos.app.goo.gl/ERUaSS6Qc8jFhHnn9 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 2 14:32:17 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'enabled-extensions' b"['desktop-icons@csoriano']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-05-31 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1831369/+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
Re: [Desktop-packages] [Bug 1831369] Re: Gnome Shell pauses and stutters while waiting (several seconds) for programs to launch
Yes, After 20.04 release I will agitate people to switch to Ubuntu. If anyone fan of dead Windows 7 or Ubuntu Unity (until 17.10 release) want to find a great alternative, he should take attention to our new stable smooth and fast Ubuntu. пн, 2 сент. 2019 г. в 05:15, Daniel van Vugt : > Thanks. > > It looks to be very CPU-busy, mostly in the gnome-shell process. We are > working to reduce the CPU load and increase the performance of gnome- > shell but it will take some time. You will see a definite improvement in > 19.10 and I hope another big improvement next year in 20.04. > > ** Summary changed: > > - Gnome Shell pauses and stutters while waiting (several seconds) for > programs to launch > + Gnome Shell pauses and stutters while waiting (several seconds) for web > browsers to launch on a Celeron N3350. > > ** Changed in: gnome-shell (Ubuntu) >Importance: Low => Medium > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1831369 > > Title: > Gnome Shell pauses and stutters while waiting (several seconds) for > web browsers to launch on a Celeron N3350. > > Status in gnome-shell package in Ubuntu: > New > > Bug description: > My laptop: HP 250 G6, Intel Celeron N3350, integrated video card, 4 GB > RAM, Ubuntu 19.04 > Details in my video: https://photos.app.goo.gl/ERUaSS6Qc8jFhHnn9 > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: gnome-shell 3.32.0+git20190410-1ubuntu1 > ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 > Uname: Linux 5.0.0-15-generic x86_64 > ApportVersion: 2.20.10-0ubuntu27 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Sun Jun 2 14:32:17 2019 > DisplayManager: gdm3 > GsettingsChanges: >b'org.gnome.shell' b'app-picker-view' b'uint32 1' >b'org.gnome.shell' b'command-history' redacted by apport >b'org.gnome.shell' b'favorite-apps' redacted by apport >b'org.gnome.shell' b'enabled-extensions' b"['desktop-icons@csoriano']" >b'org.gnome.desktop.interface' b'gtk-im-module' > b"'gtk-im-context-simple'" > InstallationDate: Installed on 2019-05-31 (1 days ago) > InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) > ProcEnviron: >LANGUAGE=ru_UA:ru >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=ru_UA.UTF-8 >SHELL=/bin/bash > SourcePackage: gnome-shell > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1831369/+subscriptions > -- 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/1831369 Title: Gnome Shell pauses and stutters when other programs like Firefox are using significant CPU on a Celeron N3350 Status in gnome-shell package in Ubuntu: New Bug description: My laptop: HP 250 G6, Intel Celeron N3350, integrated video card, 4 GB RAM, Ubuntu 19.04 Details in my video: https://photos.app.goo.gl/ERUaSS6Qc8jFhHnn9 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 2 14:32:17 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'enabled-extensions' b"['desktop-icons@csoriano']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-05-31 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1831369/+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 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
** Changed in: software-properties (Ubuntu Bionic) Assignee: (unassigned) => Sebastien Bacher (seb128) -- 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/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab Status in gnome-shell package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in gnome-shell source package in Bionic: New Status in software-properties source package in Bionic: New Bug description: On the "Other Software" tab, I am unable to select "Canonical Partners". Similarly, the other checkboxes on the "Other Software" can not be clicked. Clicking on a checkbox has no effect, and a dialog requesting the admin password is not presented. However, activating or deactivating checkboxes on other tabs causes an authorization dialog to be presented to the user. I experience this bug in an an Xorg session. sources.list and sources.list.d have the following permissions: -rw-r--r-- 1 root root 2897 Oct 26 22:35 sources.list drwxr-xr-x 2 root root 4096 Oct 26 21:29 sources.list.d All files in sources.list.d have the following permissions as this example: -rw-r--r-- 1 root root 189 Oct 25 21:50 google-chrome.list $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.96.24.17 Candidate: 0.96.24.17 Version table: *** 0.96.24.17 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 26 22:45:09 2017 InstallationDate: Installed on 2017-10-26 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+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 1842324] Re: Port schemas from gnome-settings-daemon-common to com.canonical.unity.settings-daemon
** Merge proposal linked: https://code.launchpad.net/~khurshid-alam/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/372202 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1842324 Title: Port schemas from gnome-settings-daemon-common to com.canonical.unity .settings-daemon Status in unity package in Ubuntu: Confirmed Status in unity-control-center package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Confirmed Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: Unity-settings-daemon still depends on gnome-settings-daemon schemas. It is undesired as it requires to modify code in all unity related components when upstream drops some gsettings schemas. gnome-settings-daemon > 3.33 drops/modify media-keys schemas in an undesired way that it can't easily be reverted. Keyboard & mouse schemas are modified and unity-settings-daemon is crashing. So it's better unity uses it's own schema as suggested by Laney. https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/6dff93a0dfa80db3f481eed5d6ed689bf469aa1b https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/44f53c64c5a2514d2c022bcb1596a9e46f1df51c https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/121a6f89917898b8d05db2e1933dd0ad59c26768 Since this is a huge task it can be achieved gradually. 1) Ubuntu 19.10 - Port media keys to use com.canonical.unity.settings-daemon - u-s-d will still use org.gnome.settings-daemon name in dbus - u-s-d will still respects activation toggle in org.gnome.settings- daemon - everything else remains the same 2) Ubuntu 20.04 - Port rest of plugins to use com.canonical.unity.settings-daemon - u-s-d will still use org.gnome.settings-daemon name in dbus - Activation toggle key will now use com.canonical.unity.settings- daemon - u-s-d will keep using org.gnome.session - Everything else will remain the same To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1842324/+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 1841915] Re: black screen, unresponsive, after logout from gnome Wayland session
My point regarding gnome-session-wayland.target is that if we're seeing different filenames for that file (assuming they're functionally the same) and mine definitely comes from gnome-session-bin, does that suggest we're running different gnome-session-bin versions? And seeing as you're not reproducing an issue i'm seeing regarding the ending of a gnome session... does that difference in what file you're expecting me to have there and the file i *assure* you is actually there... signify anything? -- 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/1841915 Title: black screen, unresponsive, after logout from gnome Wayland session Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: on logout the screen is black, the system is unresponsive and has to be restarted. (Untested by me yet, but I expect ssh-ing in and restarting gdm would work.) I believe this may be already reported upstream here: https://bugzilla.redhat.com/show_bug.cgi?id=1745554 That's why I've reported this against gdm3 even though I honestly don't know if it might be a gnome-shell, gnome-session or mutter based error. (FWIW without the upstream bug to link to I'd maybe suspect gnome-shell first.) NB: This machine's conf has AutomaticLogin enabled, but another machine also on 19.10 does not, and it's showing the same thing. On *this* machine I found that the *first* time I logged out, it was OK, but not the second time. On the other machine, it fails first time too. It's as if the gdm login screen can appear exactly once. That (and being on gnome 3.33) is why I don't think this is a dupe of #1824588. Nothing appears in /var/crash as a result of this. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.33.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:51:22 2019 InstallationDate: Installed on 2018-09-11 (351 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gdm3 UpgradeStatus: Upgraded to eoan on 2019-07-16 (43 days ago) mtime.conffile..etc.gdm3.custom.conf: 2019-07-17T00:07:04.528641 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+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 1834671] Re: TLSv1.3 client certificate authentication with renegotiation unsupported in browsers
** Changed in: firefox (Ubuntu Eoan)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: firefox (Ubuntu Disco)
Assignee: (unassigned) => Olivier Tilloy (osomon)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1834671
Title:
TLSv1.3 client certificate authentication with renegotiation
unsupported in browsers
Status in apache2 package in Ubuntu:
Invalid
Status in chromium package in Ubuntu:
New
Status in firefox package in Ubuntu:
New
Status in apache2 source package in Disco:
Invalid
Status in chromium source package in Disco:
New
Status in firefox source package in Disco:
New
Status in apache2 source package in Eoan:
Invalid
Status in chromium source package in Eoan:
New
Status in firefox source package in Eoan:
New
Bug description:
This is mostly a place holder bug, as more information becomes
available.
What is known so far is that a certain configuration of client
certificate authentication using TLSv1.3 is not working with most (all
at this point?) browsers, resulting in the server returning this error
message:
Forbidden
You don't have permission to access / on this server.
Reason: Cannot perform Post-Handshake Authentication.
Apache/2.4.38 (Ubuntu) Server at disco-apache-client-cert.lxd Port 443
It also logs it to error.log:
[Fri Jun 28 16:59:24.596425 2019] [ssl:error] [pid 1391:tid 139642783385344]
[client 10.0.100.1:41452] AH10129: verify client post handshake
[Fri Jun 28 16:59:24.596493 2019] [ssl:error] [pid 1391:tid 139642783385344]
[client 10.0.100.1:41452] AH10158: cannot perform post-handshake authentication
[Fri Jun 28 16:59:24.596513 2019] [ssl:error] [pid 1391:tid 139642783385344]
SSL Library Error: error:14268117:SSL
routines:SSL_verify_client_post_handshake:extension not received
These are upstream bugs about it:
Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1511989
Chromium: https://bugs.chromium.org/p/chromium/issues/detail?id=911653
Apache2 (invalid): https://bz.apache.org/bugzilla/show_bug.cgi?id=62975
One server workaround is to disable TLSv1.3. Something like this:
SSLProtocol all -SSLv3 -TLSv1.3
("-TLSv1.3" is what was added to that default config)
Sample server config to show the problem (minus the SSL certificate
parameters):
SSLVerifyClient require
Require ssl-verify-client
Another workaround is to move the SSLVerifyClient config to the vhost
level. It it applied to the whole vhost, and there are no exceptions
in specific blocks, then a re-negotiation isn't triggered and the
problem doesn't happen.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1834671/+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 1841718] Re: [radeon] Rendering of combo boxes and tooltips is broken
** Changed in: xserver-xorg-video-ati (Ubuntu) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: New => Triaged ** Also affects: xserver-xorg-video-ati (Ubuntu Eoan) Importance: Undecided Assignee: Timo Aaltonen (tjaalton) Status: Triaged ** Also affects: mutter (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: gtk+3.0 (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: xserver-xorg-video-ati (Ubuntu Eoan) Importance: Undecided => Medium ** Tags removed: rls-ee-incoming ** Changed in: mutter (Ubuntu Eoan) Status: New => Invalid ** Changed in: gtk+3.0 (Ubuntu Eoan) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1841718 Title: [radeon] Rendering of combo boxes and tooltips is broken Status in gtk+3.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Triaged Status in mutter package in Ubuntu: Invalid Status in gtk+3.0 source package in Eoan: Invalid Status in mesa source package in Eoan: Triaged Status in mutter source package in Eoan: Invalid Bug description: Combo boxes are broken (cf screenshot) Tested in gnome-control-center and gtk3-demo. Tooltips are also garbage. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 28 07:08:33 2019 DisplayManager: gdm3 InstallationDate: Installed on 2014-07-15 (1869 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2018-03-24 (521 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1841718/+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 1841718] Re: [radeon] Rendering of combo boxes and tooltips is broken
** Package changed: xserver-xorg-video-ati (Ubuntu Eoan) => mesa (Ubuntu Eoan) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1841718 Title: [radeon] Rendering of combo boxes and tooltips is broken Status in gtk+3.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Triaged Status in mutter package in Ubuntu: Invalid Status in gtk+3.0 source package in Eoan: Invalid Status in mesa source package in Eoan: Triaged Status in mutter source package in Eoan: Invalid Bug description: Combo boxes are broken (cf screenshot) Tested in gnome-control-center and gtk3-demo. Tooltips are also garbage. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 28 07:08:33 2019 DisplayManager: gdm3 InstallationDate: Installed on 2014-07-15 (1869 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2018-03-24 (521 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1841718/+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 1841915] Re: black screen, unresponsive, after logout from gnome Wayland session
** Tags removed: rls-ee-incoming -- 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/1841915 Title: black screen, unresponsive, after logout from gnome Wayland session Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: on logout the screen is black, the system is unresponsive and has to be restarted. (Untested by me yet, but I expect ssh-ing in and restarting gdm would work.) I believe this may be already reported upstream here: https://bugzilla.redhat.com/show_bug.cgi?id=1745554 That's why I've reported this against gdm3 even though I honestly don't know if it might be a gnome-shell, gnome-session or mutter based error. (FWIW without the upstream bug to link to I'd maybe suspect gnome-shell first.) NB: This machine's conf has AutomaticLogin enabled, but another machine also on 19.10 does not, and it's showing the same thing. On *this* machine I found that the *first* time I logged out, it was OK, but not the second time. On the other machine, it fails first time too. It's as if the gdm login screen can appear exactly once. That (and being on gnome 3.33) is why I don't think this is a dupe of #1824588. Nothing appears in /var/crash as a result of this. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.33.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:51:22 2019 InstallationDate: Installed on 2018-09-11 (351 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gdm3 UpgradeStatus: Upgraded to eoan on 2019-07-16 (43 days ago) mtime.conffile..etc.gdm3.custom.conf: 2019-07-17T00:07:04.528641 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+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 1841794] Re: gnome-shell crashed with SIGTRAP in g_log_default_handler() ... from ObjectInstance::~ObjectInstance() [usually logging "Finalizing wrapper for an already freed ob
** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Also affects: gnome-shell (Ubuntu Eoan) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Confirmed ** Tags removed: rls-ee-incoming -- 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/1841794 Title: gnome-shell crashed with SIGTRAP in g_log_default_handler() ... from ObjectInstance::~ObjectInstance() [usually logging "Finalizing wrapper for an already freed object of type: Clutter.PropertyTransition"] Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell source package in Eoan: Confirmed Bug description: https://errors.ubuntu.com/problem/10051642bda6e2a9a27fe0b0d5f84f8b1f29438f ubuntu-bug crash report for bug reported in LP: #1841680 On Eoan, gnome-shell (3.33.91-1ubuntu1) crashes and restarts when opening up applications from the dock. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 27 10:42:41 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-02-19 (554 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: Upgraded to eoan on 2019-08-27 (0 days ago) UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841794/+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
Re: [Desktop-packages] [Bug 1841915] Re: black screen, unresponsive, after logout from gnome Wayland session
On Tue, Sep 03, 2019 at 01:28:08PM -, Rachel Greenham wrote: > It is definitely /usr/lib/systemd/user-gnome-session-wayland.target. > dpkg -S on that file gives gnome-session-bin which is on version > 3.33.90-2ubuntu2. dpkg -S on the .service file gives no match. If it happens when you remove --systemd, then it cannot be to do with the systemd stuff. -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] -- 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/1841915 Title: black screen, unresponsive, after logout from gnome Wayland session Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: on logout the screen is black, the system is unresponsive and has to be restarted. (Untested by me yet, but I expect ssh-ing in and restarting gdm would work.) I believe this may be already reported upstream here: https://bugzilla.redhat.com/show_bug.cgi?id=1745554 That's why I've reported this against gdm3 even though I honestly don't know if it might be a gnome-shell, gnome-session or mutter based error. (FWIW without the upstream bug to link to I'd maybe suspect gnome-shell first.) NB: This machine's conf has AutomaticLogin enabled, but another machine also on 19.10 does not, and it's showing the same thing. On *this* machine I found that the *first* time I logged out, it was OK, but not the second time. On the other machine, it fails first time too. It's as if the gdm login screen can appear exactly once. That (and being on gnome 3.33) is why I don't think this is a dupe of #1824588. Nothing appears in /var/crash as a result of this. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.33.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:51:22 2019 InstallationDate: Installed on 2018-09-11 (351 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gdm3 UpgradeStatus: Upgraded to eoan on 2019-07-16 (43 days ago) mtime.conffile..etc.gdm3.custom.conf: 2019-07-17T00:07:04.528641 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+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 1841915] Re: black screen, unresponsive, after logout from gnome Wayland session
minor contextual note: It took me a little while to get the other machine, ssh in (offending ssh key to resolve), call up this page to remind me of the exact commands. The point of which is to say, these weren't taken *immediately* after the logout, but at least a minute later, certainly beyond that timeout discussed earlier. Also therefore that that ssh session started *after* the hang event, didn't log in in advance. -- 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/1841915 Title: black screen, unresponsive, after logout from gnome Wayland session Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: on logout the screen is black, the system is unresponsive and has to be restarted. (Untested by me yet, but I expect ssh-ing in and restarting gdm would work.) I believe this may be already reported upstream here: https://bugzilla.redhat.com/show_bug.cgi?id=1745554 That's why I've reported this against gdm3 even though I honestly don't know if it might be a gnome-shell, gnome-session or mutter based error. (FWIW without the upstream bug to link to I'd maybe suspect gnome-shell first.) NB: This machine's conf has AutomaticLogin enabled, but another machine also on 19.10 does not, and it's showing the same thing. On *this* machine I found that the *first* time I logged out, it was OK, but not the second time. On the other machine, it fails first time too. It's as if the gdm login screen can appear exactly once. That (and being on gnome 3.33) is why I don't think this is a dupe of #1824588. Nothing appears in /var/crash as a result of this. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.33.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:51:22 2019 InstallationDate: Installed on 2018-09-11 (351 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gdm3 UpgradeStatus: Upgraded to eoan on 2019-07-16 (43 days ago) mtime.conffile..etc.gdm3.custom.conf: 2019-07-17T00:07:04.528641 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+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 1731459] Re: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10+, 18.04 LTS and 18.10 Cosmic cuttlefish
As regards the autopkgtest regression reports in comment #75 and #76:
colord has passed autopkgtest for bionic/armhf several times, the latest
at 2019-08-23.
Likewise, libkf5sane has passed autopkgtest for disco/armhf several
times, the latest at 2019-07-01.
Seems like simply re-running the tests might help. Can somebody in the
SRU team please do that?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1731459
Title:
genesys_gl847 scanners produce a black band in scanned images on
Ubuntu 17.10+, 18.04 LTS and 18.10 Cosmic cuttlefish
Status in sane-backends:
Fix Released
Status in sane-backends package in Ubuntu:
Fix Released
Status in sane-backends source package in Bionic:
Fix Committed
Status in sane-backends source package in Disco:
Fix Committed
Status in sane-backends package in Debian:
Confirmed
Bug description:
[Impact]
When using a Genesys GL847 scanner, the documents get disfigured by a
discolored bar. The proposed uploads should fix the issue. They are
available in this PPA:
https://launchpad.net/~gunnarhj/+archive/ubuntu/sane-backends
[Test case]
1. Install the libsane (libsane1 in bionic), libsane-common
and sane-utils packages from {bionic,disco]-proposed.
2. Use an affected device to scan, and find that the issue is
no longer present.
[Regression risk]
Upstream commit, focused bug fix => low regression risk
[Original description]
On Windows it works but on my Ubuntu 17.10, 18.04 and 18.10 I see a
black band on scanned image. The scanner is Canon CanoScan LIDE100.
Libsane version is 1.0.27-1~experimental2ubuntu1
To manage notifications about this bug go to:
https://bugs.launchpad.net/sane-backends/+bug/1731459/+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 1841915] Re: black screen, unresponsive, after logout from gnome Wayland session
journalctl -b output as attached loginctl as below: rachel in ~ at rainbow ➜ loginctl SESSION UID USER SEAT TTY 1 1000 rachel seat0 tty2 3 1000 rachel pts/0 2 sessions listed. rachel in ~ at rainbow ➜ loginctl show-session 1 Id=1 User=1000 Name=rachel Timestamp=Tue 2019-09-03 14:30:40 BST TimestampMonotonic=20750725 VTNr=2 Seat=seat0 TTY=tty2 Remote=no Service=gdm-autologin Scope=session-1.scope Leader=5228 Audit=1 Type=wayland Class=user Active=yes State=closing IdleHint=no IdleSinceHint=0 IdleSinceHintMonotonic=0 LockedHint=no rachel in ~ at rainbow ➜ loginctl show-session 3 Id=3 User=1000 Name=rachel Timestamp=Tue 2019-09-03 14:31:47 BST TimestampMonotonic=87793987 VTNr=0 TTY=pts/0 Remote=yes RemoteHost=192.168.1.109 Service=sshd Scope=session-3.scope Leader=7048 Audit=3 Type=tty Class=user Active=yes State=active IdleHint=no IdleSinceHint=1567517624629274 IdleSinceHintMonotonic=205041051 LockedHint=no ** Attachment added: "jctl.log" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+attachment/5286446/+files/jctl.log -- 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/1841915 Title: black screen, unresponsive, after logout from gnome Wayland session Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: on logout the screen is black, the system is unresponsive and has to be restarted. (Untested by me yet, but I expect ssh-ing in and restarting gdm would work.) I believe this may be already reported upstream here: https://bugzilla.redhat.com/show_bug.cgi?id=1745554 That's why I've reported this against gdm3 even though I honestly don't know if it might be a gnome-shell, gnome-session or mutter based error. (FWIW without the upstream bug to link to I'd maybe suspect gnome-shell first.) NB: This machine's conf has AutomaticLogin enabled, but another machine also on 19.10 does not, and it's showing the same thing. On *this* machine I found that the *first* time I logged out, it was OK, but not the second time. On the other machine, it fails first time too. It's as if the gdm login screen can appear exactly once. That (and being on gnome 3.33) is why I don't think this is a dupe of #1824588. Nothing appears in /var/crash as a result of this. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.33.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:51:22 2019 InstallationDate: Installed on 2018-09-11 (351 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gdm3 UpgradeStatus: Upgraded to eoan on 2019-07-16 (43 days ago) mtime.conffile..etc.gdm3.custom.conf: 2019-07-17T00:07:04.528641 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+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 1841929] Re: Volume up/down repeat keys don't work on Xorg
** Tags removed: rls-ee-incoming ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Also affects: mutter (Ubuntu Eoan) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Confirmed ** Also affects: gnome-shell (Ubuntu Eoan) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Confirmed -- 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/1841929 Title: Volume up/down repeat keys don't work on Xorg Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in gnome-shell source package in Eoan: Confirmed Status in mutter source package in Eoan: Confirmed Bug description: GNOME Shell & mutter on 3.33.91 When pressing volume up or down on Xorg and keeping it pressed, only the first key event is sent, so the volume only goes up or down once, and doesn't scale up/down as long as you keep the button pressed. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 13:45:27 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-24 (461 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-01-08 (232 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1841929/+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 1842256] Re: ~/.pam_environment overridden by /etc/default/locale
** Changed in: gdm3 (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: gdm3 (Ubuntu) Status: New => Triaged ** Tags removed: rls-ee-incoming ** Also affects: gdm3 (Ubuntu Eoan) Importance: High Assignee: Olivier Tilloy (osomon) Status: Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1842256 Title: ~/.pam_environment overridden by /etc/default/locale Status in gdm3 package in Ubuntu: Triaged Status in gdm3 source package in Eoan: Triaged Bug description: Bug #1662031 has resurrected. The patch dont_set_language_env.patch, which fixed it last time, is still there, but it seems not to be sufficient in 3.33.90. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1842256/+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 1841915] Re: black screen, unresponsive, after logout from gnome Wayland session
It is definitely /usr/lib/systemd/user-gnome-session-wayland.target. dpkg -S on that file gives gnome-session-bin which is on version 3.33.90-2ubuntu2. dpkg -S on the .service file gives no match. This problem didn't start on upgrade to the 5.2 kernels, which happened a few weeks(?) earlier, but immediately when gnome 3.33 dropped. will get the gdm debugging stuff... (had to spend some time in windows doing that for which i'm paid ;-) -- 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/1841915 Title: black screen, unresponsive, after logout from gnome Wayland session Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: on logout the screen is black, the system is unresponsive and has to be restarted. (Untested by me yet, but I expect ssh-ing in and restarting gdm would work.) I believe this may be already reported upstream here: https://bugzilla.redhat.com/show_bug.cgi?id=1745554 That's why I've reported this against gdm3 even though I honestly don't know if it might be a gnome-shell, gnome-session or mutter based error. (FWIW without the upstream bug to link to I'd maybe suspect gnome-shell first.) NB: This machine's conf has AutomaticLogin enabled, but another machine also on 19.10 does not, and it's showing the same thing. On *this* machine I found that the *first* time I logged out, it was OK, but not the second time. On the other machine, it fails first time too. It's as if the gdm login screen can appear exactly once. That (and being on gnome 3.33) is why I don't think this is a dupe of #1824588. Nothing appears in /var/crash as a result of this. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.33.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:51:22 2019 InstallationDate: Installed on 2018-09-11 (351 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gdm3 UpgradeStatus: Upgraded to eoan on 2019-07-16 (43 days ago) mtime.conffile..etc.gdm3.custom.conf: 2019-07-17T00:07:04.528641 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+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 1815172] Re: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa
There's a follow up fix for bionic/linux which needs to be applied: https://lists.ubuntu.com/archives/kernel-team/2019-August/103175.html So I'm going to reset the task. ** Changed in: linux (Ubuntu Bionic) Status: Fix Released => In Progress ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa Status in Mesa: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in linux source package in Cosmic: Won't Fix Status in mesa source package in Cosmic: Fix Released Bug description: [Impact] Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument This is caused by mesa assuming that soft-pinning on GEN8+ is working since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT sizes/pin flags, but that's left for future. [Test case] install fixed mesa or kernel, check that the regression is fixed [Regression potential] mesa: shouldn't be any, it just reverts the change to always soft-pin (TODO kernel: adds commits from upstream stable, which have been well tested upstream by now) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+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 1842324] Re: Port schemas from gnome-settings-daemon-common to com.canonical.unity.settings-daemon
** Description changed: Unity-settings-daemon still depends on gnome-settings-daemon schemas. It is undesired as it requires to modify code in all unity related components when upstream drops some gsettings schemas. gnome-settings-daemon > 3.33 drops/modify media-keys schemas in an undesired way that it can't easily be reverted. Keyboard & mouse schemas are modified and unity-settings-daemon is crashing. So it's better unity uses it's own schema as suggested by Laney. https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/6dff93a0dfa80db3f481eed5d6ed689bf469aa1b https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/44f53c64c5a2514d2c022bcb1596a9e46f1df51c https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/121a6f89917898b8d05db2e1933dd0ad59c26768 Since this is a huge task it can be achieved gradually. 1) Ubuntu 19.10 - Port media keys to use com.canonical.unity.settings-daemon - u-s-d will still use org.gnome.settings-daemon name in dbus - u-s-d will still respects activation toggle in org.gnome.settings- daemon - everything else remains the same 2) Ubuntu 20.04 - Port rest of plugins to use com.canonical.unity.settings-daemon - - u-s-d registers as com.canonical.unity.settings-daemon + - u-s-d will still use org.gnome.settings-daemon name in dbus - Activation toggle key will now use com.canonical.unity.settings-daemon - u-s-d will keep using org.gnome.session - Everything else will remain the same -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1842324 Title: Port schemas from gnome-settings-daemon-common to com.canonical.unity .settings-daemon Status in unity package in Ubuntu: Confirmed Status in unity-control-center package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Confirmed Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: Unity-settings-daemon still depends on gnome-settings-daemon schemas. It is undesired as it requires to modify code in all unity related components when upstream drops some gsettings schemas. gnome-settings-daemon > 3.33 drops/modify media-keys schemas in an undesired way that it can't easily be reverted. Keyboard & mouse schemas are modified and unity-settings-daemon is crashing. So it's better unity uses it's own schema as suggested by Laney. https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/6dff93a0dfa80db3f481eed5d6ed689bf469aa1b https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/44f53c64c5a2514d2c022bcb1596a9e46f1df51c https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/121a6f89917898b8d05db2e1933dd0ad59c26768 Since this is a huge task it can be achieved gradually. 1) Ubuntu 19.10 - Port media keys to use com.canonical.unity.settings-daemon - u-s-d will still use org.gnome.settings-daemon name in dbus - u-s-d will still respects activation toggle in org.gnome.settings- daemon - everything else remains the same 2) Ubuntu 20.04 - Port rest of plugins to use com.canonical.unity.settings-daemon - u-s-d will still use org.gnome.settings-daemon name in dbus - Activation toggle key will now use com.canonical.unity.settings- daemon - u-s-d will keep using org.gnome.session - Everything else will remain the same To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1842324/+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 1842426] [NEW] xenial's chromium-browser test failure
Public bug reported: As requested by SRU verification team: https://bugs.launchpad.net/ubuntu/+source/util- linux/+bug/1589289/comments/33 As for xenial's chromium-browser test failures - could you please file a bug about the failing architectures? I would then include the bug number in the hint. This way we won't forget about the test issues. # pending SRU report: Regression in autopkgtest for chromium-browser (arm64): test log http://autopkgtest.ubuntu.com/packages/c/chromium-browser/xenial/arm64 Regression in autopkgtest for chromium-browser (i386): test log http://autopkgtest.ubuntu.com/packages/c/chromium-browser/xenial/i386 Regression in autopkgtest for chromium-browser (amd64): test log http://autopkgtest.ubuntu.com/packages/c/chromium-browser/xenial/amd64 The above are recurrent pattern of autopkgtest failures. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: chromium-browser (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: chromium-browser (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: chromium-browser (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1842426 Title: xenial's chromium-browser test failure Status in chromium-browser package in Ubuntu: Fix Released Status in chromium-browser source package in Xenial: New Bug description: As requested by SRU verification team: https://bugs.launchpad.net/ubuntu/+source/util- linux/+bug/1589289/comments/33 As for xenial's chromium-browser test failures - could you please file a bug about the failing architectures? I would then include the bug number in the hint. This way we won't forget about the test issues. # pending SRU report: Regression in autopkgtest for chromium-browser (arm64): test log http://autopkgtest.ubuntu.com/packages/c/chromium-browser/xenial/arm64 Regression in autopkgtest for chromium-browser (i386): test log http://autopkgtest.ubuntu.com/packages/c/chromium-browser/xenial/i386 Regression in autopkgtest for chromium-browser (amd64): test log http://autopkgtest.ubuntu.com/packages/c/chromium-browser/xenial/amd64 The above are recurrent pattern of autopkgtest failures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1842426/+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
Re: [Desktop-packages] [Bug 1841915] Re: black screen, unresponsive, after logout from gnome Wayland session
On Tue, Sep 03, 2019 at 11:42:51AM -, Rachel Greenham wrote: > With --systemd removed as directed I still ended up stuck on a black > screen, except this time it had a flashing white text cursor in the top > left. OK, please enable GDM debugging as outlined previously, reproduce the problem, SSH into your machine and then attach the output of `journalctl -b`. Perhaps the next step is to try an older kernel (e.g. the one that is in 19.04/disco's archive). Cheers, -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] -- 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/1841915 Title: black screen, unresponsive, after logout from gnome Wayland session Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: on logout the screen is black, the system is unresponsive and has to be restarted. (Untested by me yet, but I expect ssh-ing in and restarting gdm would work.) I believe this may be already reported upstream here: https://bugzilla.redhat.com/show_bug.cgi?id=1745554 That's why I've reported this against gdm3 even though I honestly don't know if it might be a gnome-shell, gnome-session or mutter based error. (FWIW without the upstream bug to link to I'd maybe suspect gnome-shell first.) NB: This machine's conf has AutomaticLogin enabled, but another machine also on 19.10 does not, and it's showing the same thing. On *this* machine I found that the *first* time I logged out, it was OK, but not the second time. On the other machine, it fails first time too. It's as if the gdm login screen can appear exactly once. That (and being on gnome 3.33) is why I don't think this is a dupe of #1824588. Nothing appears in /var/crash as a result of this. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.33.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:51:22 2019 InstallationDate: Installed on 2018-09-11 (351 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gdm3 UpgradeStatus: Upgraded to eoan on 2019-07-16 (43 days ago) mtime.conffile..etc.gdm3.custom.conf: 2019-07-17T00:07:04.528641 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+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
Re: [Desktop-packages] [Bug 1841915] Re: black screen, unresponsive, after logout from gnome Wayland session
On Tue, Sep 03, 2019 at 11:34:10AM -, Rachel Greenham wrote: > There is no /usr/lib/systemd/user/gnome-session-wayland.service file on > this system. There is a .target file though which is presumably the one. > As the presumably-default timeout didn't seem to be honoured here there > didn't seem a lot of point in adding a shorter one so I left the file > alone. I'll try the change to /usr/share/wayland-sessions/ubuntu- > wayland.desktop (the only file in that directory) and report back in the > next comment... That should be gnome-shell-wayland.service. But if you didn't see it return after the 30 second timeout then I doubt that lowering the default will help you. I was following this line of inquiry due to Daniel's comment. -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] -- 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/1841915 Title: black screen, unresponsive, after logout from gnome Wayland session Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: on logout the screen is black, the system is unresponsive and has to be restarted. (Untested by me yet, but I expect ssh-ing in and restarting gdm would work.) I believe this may be already reported upstream here: https://bugzilla.redhat.com/show_bug.cgi?id=1745554 That's why I've reported this against gdm3 even though I honestly don't know if it might be a gnome-shell, gnome-session or mutter based error. (FWIW without the upstream bug to link to I'd maybe suspect gnome-shell first.) NB: This machine's conf has AutomaticLogin enabled, but another machine also on 19.10 does not, and it's showing the same thing. On *this* machine I found that the *first* time I logged out, it was OK, but not the second time. On the other machine, it fails first time too. It's as if the gdm login screen can appear exactly once. That (and being on gnome 3.33) is why I don't think this is a dupe of #1824588. Nothing appears in /var/crash as a result of this. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.33.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:51:22 2019 InstallationDate: Installed on 2018-09-11 (351 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gdm3 UpgradeStatus: Upgraded to eoan on 2019-07-16 (43 days ago) mtime.conffile..etc.gdm3.custom.conf: 2019-07-17T00:07:04.528641 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+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 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE
So to summarize you found the newline issue, but that proved to not be related to the error message you get, even if fixing it may be necessary as a partial solution. If I modify the test script by commenting the newline fix I get: File "/lib/modules/5.0.0-25-generic /kernel/drivers/net/usb/cdc_mbim.ko" not found. I.e. no error message. So we are kind of stuck. There is a working TCL version in the first PPA, but I'm not permitted to propose it for upload. @Mathieu, @Steve: Are the reasons for carrying the dispatcher as an Ubuntu specific C program still strong enough? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1800794 Title: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE Status in usb-modeswitch package in Ubuntu: In Progress Bug description: Please refer to post of usb-modeswitch developer http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4=2827 for complete issue description. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+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 1841915] Re: black screen, unresponsive, after logout from gnome Wayland session
With --systemd removed as directed I still ended up stuck on a black screen, except this time it had a flashing white text cursor in the top left. (BTW reboots occurred between each test, somewhat perforce...) -- 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/1841915 Title: black screen, unresponsive, after logout from gnome Wayland session Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: on logout the screen is black, the system is unresponsive and has to be restarted. (Untested by me yet, but I expect ssh-ing in and restarting gdm would work.) I believe this may be already reported upstream here: https://bugzilla.redhat.com/show_bug.cgi?id=1745554 That's why I've reported this against gdm3 even though I honestly don't know if it might be a gnome-shell, gnome-session or mutter based error. (FWIW without the upstream bug to link to I'd maybe suspect gnome-shell first.) NB: This machine's conf has AutomaticLogin enabled, but another machine also on 19.10 does not, and it's showing the same thing. On *this* machine I found that the *first* time I logged out, it was OK, but not the second time. On the other machine, it fails first time too. It's as if the gdm login screen can appear exactly once. That (and being on gnome 3.33) is why I don't think this is a dupe of #1824588. Nothing appears in /var/crash as a result of this. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.33.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:51:22 2019 InstallationDate: Installed on 2018-09-11 (351 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gdm3 UpgradeStatus: Upgraded to eoan on 2019-07-16 (43 days ago) mtime.conffile..etc.gdm3.custom.conf: 2019-07-17T00:07:04.528641 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+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 1841915] Re: black screen, unresponsive, after logout from gnome Wayland session
I tried (just now) deliberately leaving it longer than 30 seconds to come back after a logout. In fact left it longer than 60 seconds. Nothing happening. I wasn't logged in via ssh as well at the time (I hadn't thought the systemd --user instance was related to the ssh session before so presumably might be confusing matters) so there's nothing more to report than that the screen remained resolutely black. There is no /usr/lib/systemd/user/gnome-session-wayland.service file on this system. There is a .target file though which is presumably the one. As the presumably-default timeout didn't seem to be honoured here there didn't seem a lot of point in adding a shorter one so I left the file alone. I'll try the change to /usr/share/wayland-sessions/ubuntu- wayland.desktop (the only file in that directory) and report back in the next comment... -- 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/1841915 Title: black screen, unresponsive, after logout from gnome Wayland session Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: on logout the screen is black, the system is unresponsive and has to be restarted. (Untested by me yet, but I expect ssh-ing in and restarting gdm would work.) I believe this may be already reported upstream here: https://bugzilla.redhat.com/show_bug.cgi?id=1745554 That's why I've reported this against gdm3 even though I honestly don't know if it might be a gnome-shell, gnome-session or mutter based error. (FWIW without the upstream bug to link to I'd maybe suspect gnome-shell first.) NB: This machine's conf has AutomaticLogin enabled, but another machine also on 19.10 does not, and it's showing the same thing. On *this* machine I found that the *first* time I logged out, it was OK, but not the second time. On the other machine, it fails first time too. It's as if the gdm login screen can appear exactly once. That (and being on gnome 3.33) is why I don't think this is a dupe of #1824588. Nothing appears in /var/crash as a result of this. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.33.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:51:22 2019 InstallationDate: Installed on 2018-09-11 (351 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gdm3 UpgradeStatus: Upgraded to eoan on 2019-07-16 (43 days ago) mtime.conffile..etc.gdm3.custom.conf: 2019-07-17T00:07:04.528641 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+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 1841915] Re: black screen, unresponsive, after logout from gnome Wayland session
I have tried to reproduce this but I can't, not in a VM or on my real system (i915). I tried with and without automatic login, with the vanilla GNOME session and with the Ubuntu session, with and without the same user logged in over SSH (to keep the systemd --user instance alive), and every log in/out cycle worked. Sorry :/ I'll note that VT switching works for me on all machines, and I see no lingering processes after logging out. One thing I did manage to reproduce, using the attached program (a daemon which doesn't quit when SIGTERMed, which I was trying to use to recreate your situation. Run it from xterm *not* gnome-terminal), is a 30 second *delay* on logout. Did you wait longer than that? If I edit `/usr/lib/systemd/user/gnome-session-wayland.service` and add TimeoutStopSec=5 at the end (then reboot), then the delay reduces to 5 seconds. I'll ask upstream about whether that's a good idea but this might not be your problem. If you go to `/usr/share/wayland-sessions/`, you can remove `--systemd` from the `Exec=` line of the session you're using, to revert to the previous method of launching the session. If that fixes it, then (in the broken situation), please enable GDM debug output (/etc/gdm3/custom.conf), and while the system is hanging fetch the output of 'loginctl', then for each session listed there, 'loginctl show-session ' and 'loginctl session-status ', as well as 'journalctl -b' and attach them here. Thanks. ** Attachment added: "daemon.c" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+attachment/5286400/+files/daemon.c -- 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/1841915 Title: black screen, unresponsive, after logout from gnome Wayland session Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: on logout the screen is black, the system is unresponsive and has to be restarted. (Untested by me yet, but I expect ssh-ing in and restarting gdm would work.) I believe this may be already reported upstream here: https://bugzilla.redhat.com/show_bug.cgi?id=1745554 That's why I've reported this against gdm3 even though I honestly don't know if it might be a gnome-shell, gnome-session or mutter based error. (FWIW without the upstream bug to link to I'd maybe suspect gnome-shell first.) NB: This machine's conf has AutomaticLogin enabled, but another machine also on 19.10 does not, and it's showing the same thing. On *this* machine I found that the *first* time I logged out, it was OK, but not the second time. On the other machine, it fails first time too. It's as if the gdm login screen can appear exactly once. That (and being on gnome 3.33) is why I don't think this is a dupe of #1824588. Nothing appears in /var/crash as a result of this. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.33.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:51:22 2019 InstallationDate: Installed on 2018-09-11 (351 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gdm3 UpgradeStatus: Upgraded to eoan on 2019-07-16 (43 days ago) mtime.conffile..etc.gdm3.custom.conf: 2019-07-17T00:07:04.528641 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+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 1842324] Re: Port schemas from gnome-settings-daemon-common to com.canonical.unity.settings-daemon
** Branch linked: lp:~khurshid-alam/unity-greeter/use-usd-schemas -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1842324 Title: Port schemas from gnome-settings-daemon-common to com.canonical.unity .settings-daemon Status in unity package in Ubuntu: Confirmed Status in unity-control-center package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Confirmed Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: Unity-settings-daemon still depends on gnome-settings-daemon schemas. It is undesired as it requires to modify code in all unity related components when upstream drops some gsettings schemas. gnome-settings-daemon > 3.33 drops/modify media-keys schemas in an undesired way that it can't easily be reverted. Keyboard & mouse schemas are modified and unity-settings-daemon is crashing. So it's better unity uses it's own schema as suggested by Laney. https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/6dff93a0dfa80db3f481eed5d6ed689bf469aa1b https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/44f53c64c5a2514d2c022bcb1596a9e46f1df51c https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/121a6f89917898b8d05db2e1933dd0ad59c26768 Since this is a huge task it can be achieved gradually. 1) Ubuntu 19.10 - Port media keys to use com.canonical.unity.settings-daemon - u-s-d will still use org.gnome.settings-daemon name in dbus - u-s-d will still respects activation toggle in org.gnome.settings- daemon - everything else remains the same 2) Ubuntu 20.04 - Port rest of plugins to use com.canonical.unity.settings-daemon - u-s-d registers as com.canonical.unity.settings-daemon - Activation toggle key will now use com.canonical.unity.settings- daemon - u-s-d will keep using org.gnome.session - Everything else will remain the same To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1842324/+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 1325931] Re: Can't select non-standard paper sizes for Printing
If the users have this similar issues to select the required paper size to make a valid print process. They should need a suggestion regarding this https://www.printererrorrepair.com/blog/how-to-fix-epson-printer- error-code-0xe5/ printing query to recover these errors. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1325931 Title: Can't select non-standard paper sizes for Printing Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: Problem description: I was trying to print a small compliments slip on a card that was 140mm x 100mm. I set the page size under Format -> Page -> Size to user defined, and then entered the width of 14.00cm and height of 10.00cm correctly. However, when I came to try to print it, it would not print correctly. The print dialog box showed the dimensions of A6 (140mm x 105mm) and I couldn't find any way to change this. I tried to print it anyway, but it came out wrong. To prove that the problem is in LibreOffice and probably not related to the driver, I exported the file to a PDF, and was able to print it by setting up a Custom Paper size in the printer settings dialog - an option which LibreOffice doesn't seem to have. Steps to reproduce: 1. Create a new Document 2. From the menu, do Format -> Page 3. From the Format dropdown, select User 4. Enter a size that is not a standard paper size 5. Click OK 6. Attempt to print the document Current behavior: No matter what combinations of options I tried, I was unable to change the Printer paper size to the correct size. If I go ahead and click Print, the output is wrong (output not aligned correctly on the page). Expected behavior: Paper size could be set by the selected Page size, or provide some way to change the printer paper size. Operating System: Ubuntu Version: 4.2.3.3 release ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libreoffice 1:4.2.3~rc3-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jun 3 12:04:40 2014 SourcePackage: libreoffice UpgradeStatus: Upgraded to trusty on 2014-05-07 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1325931/+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 1841894] Re: Wayland: Image of mouse cursor left on screen after unlock
apport information ** Tags added: apport-collected wayland-session ** Description changed: Gnome 3 desktop Multi-monitor setup with one screen rotated right into portrait mode *Experimental* fractional scaling on Wayland with different scaling on each monitor. Configured using: ~~~ gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']" ~~~ After wake from screen lock I often observe an "image" of an enlarged rotated mouse pointer on the second (rotated) monitor which doesn't move and doesn't appear on a screenshot. It overlays all other screen in formation and cannot be erased by moving the mouse over the area. Depending on where the mouse cursor was when sleeping it seems to appear in one of two places, either towards the bottom left or top right. After some time a block around the cursor image gets "corrupted". This behaviour is not observed if logging in to a X11 session Because this doesn't show up on a screenshot I have included a photo, which also shows the monitor setup. Description: Ubuntu 19.04 Release: 19.04 mutter: Installed: 3.32.2+git20190711-2ubuntu1~19.04.1 Candidate: 3.32.2+git20190711-2ubuntu1~19.04.1 Version table: *** 3.32.2+git20190711-2ubuntu1~19.04.1 500 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.32.0+git20190410-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu27.1 + Architecture: amd64 + CurrentDesktop: GNOME + DistroRelease: Ubuntu 19.04 + InstallationDate: Installed on 2019-03-08 (178 days ago) + InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) + Package: mutter 3.32.2+git20190711-2ubuntu1~19.04.1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 + Tags: wayland-session disco + Uname: Linux 5.0.0-27-generic x86_64 + UpgradeStatus: Upgraded to disco on 2019-04-21 (134 days ago) + UserGroups: adbusers adm cdrom dialout dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1841894/+attachment/5286323/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1841894 Title: Wayland: Image of mouse cursor left on screen after unlock Status in mutter package in Ubuntu: Incomplete Bug description: Gnome 3 desktop Multi-monitor setup with one screen rotated right into portrait mode *Experimental* fractional scaling on Wayland with different scaling on each monitor. Configured using: ~~~ gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']" ~~~ After wake from screen lock I often observe an "image" of an enlarged rotated mouse pointer on the second (rotated) monitor which doesn't move and doesn't appear on a screenshot. It overlays all other screen in formation and cannot be erased by moving the mouse over the area. Depending on where the mouse cursor was when sleeping it seems to appear in one of two places, either towards the bottom left or top right. After some time a block around the cursor image gets "corrupted". This behaviour is not observed if logging in to a X11 session Because this doesn't show up on a screenshot I have included a photo, which also shows the monitor setup. Description: Ubuntu 19.04 Release: 19.04 mutter: Installed: 3.32.2+git20190711-2ubuntu1~19.04.1 Candidate: 3.32.2+git20190711-2ubuntu1~19.04.1 Version table: *** 3.32.2+git20190711-2ubuntu1~19.04.1 500 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.32.0+git20190410-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-03-08 (178 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: mutter 3.32.2+git20190711-2ubuntu1~19.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Tags: wayland-session disco Uname: Linux 5.0.0-27-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-04-21 (134 days ago) UserGroups: adbusers adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1841894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1841894] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1841894/+attachment/5286324/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1841894 Title: Wayland: Image of mouse cursor left on screen after unlock Status in mutter package in Ubuntu: Incomplete Bug description: Gnome 3 desktop Multi-monitor setup with one screen rotated right into portrait mode *Experimental* fractional scaling on Wayland with different scaling on each monitor. Configured using: ~~~ gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']" ~~~ After wake from screen lock I often observe an "image" of an enlarged rotated mouse pointer on the second (rotated) monitor which doesn't move and doesn't appear on a screenshot. It overlays all other screen in formation and cannot be erased by moving the mouse over the area. Depending on where the mouse cursor was when sleeping it seems to appear in one of two places, either towards the bottom left or top right. After some time a block around the cursor image gets "corrupted". This behaviour is not observed if logging in to a X11 session Because this doesn't show up on a screenshot I have included a photo, which also shows the monitor setup. Description: Ubuntu 19.04 Release: 19.04 mutter: Installed: 3.32.2+git20190711-2ubuntu1~19.04.1 Candidate: 3.32.2+git20190711-2ubuntu1~19.04.1 Version table: *** 3.32.2+git20190711-2ubuntu1~19.04.1 500 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.32.0+git20190410-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-03-08 (178 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: mutter 3.32.2+git20190711-2ubuntu1~19.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Tags: wayland-session disco Uname: Linux 5.0.0-27-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-04-21 (134 days ago) UserGroups: adbusers adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1841894/+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 1841894] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1841894/+attachment/5286325/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1841894 Title: Wayland: Image of mouse cursor left on screen after unlock Status in mutter package in Ubuntu: Incomplete Bug description: Gnome 3 desktop Multi-monitor setup with one screen rotated right into portrait mode *Experimental* fractional scaling on Wayland with different scaling on each monitor. Configured using: ~~~ gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']" ~~~ After wake from screen lock I often observe an "image" of an enlarged rotated mouse pointer on the second (rotated) monitor which doesn't move and doesn't appear on a screenshot. It overlays all other screen in formation and cannot be erased by moving the mouse over the area. Depending on where the mouse cursor was when sleeping it seems to appear in one of two places, either towards the bottom left or top right. After some time a block around the cursor image gets "corrupted". This behaviour is not observed if logging in to a X11 session Because this doesn't show up on a screenshot I have included a photo, which also shows the monitor setup. Description: Ubuntu 19.04 Release: 19.04 mutter: Installed: 3.32.2+git20190711-2ubuntu1~19.04.1 Candidate: 3.32.2+git20190711-2ubuntu1~19.04.1 Version table: *** 3.32.2+git20190711-2ubuntu1~19.04.1 500 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.32.0+git20190410-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-03-08 (178 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: mutter 3.32.2+git20190711-2ubuntu1~19.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Tags: wayland-session disco Uname: Linux 5.0.0-27-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-04-21 (134 days ago) UserGroups: adbusers adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1841894/+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 1841897] Re: Cursor missing from slider
I filed a merge request upstream ** Tags removed: rls-ee-incoming ** Also affects: gnome-control-center (Ubuntu Eoan) Importance: Low Status: Confirmed ** Changed in: gnome-control-center (Ubuntu Eoan) Assignee: (unassigned) => Iain Lane (laney) ** Changed in: gnome-control-center (Ubuntu Eoan) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1841897 Title: Cursor missing from slider Status in gnome-control-center: New Status in gnome-control-center package in Ubuntu: In Progress Status in gnome-control-center source package in Eoan: In Progress Bug description: There is no cursor on the slider in gnome-control-center (cf screenshot) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.33.90-1ubuntu2 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 09:59:11 2019 InstallationDate: Installed on 2014-07-15 (1870 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2018-03-24 (522 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1841897/+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 1841762] Re: package nvidia-dkms-430 430.40-0ubuntu2 failed to install/upgrade: installed nvidia-dkms-430 package post-installation script subprocess returned error exit status
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-430 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1841762 Title: package nvidia-dkms-430 430.40-0ubuntu2 failed to install/upgrade: installed nvidia-dkms-430 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Bug description: Error window popped up without any intervention from me. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: nvidia-dkms-430 430.40-0ubuntu2 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Wed Aug 28 11:10:40 2019 ErrorMessage: installed nvidia-dkms-430 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2019-08-26 (1 days ago) InstallationMedia: Ubuntu-Server 19.04 "Disco Dingo" - Release amd64 (20190416.2) Python3Details: /usr/bin/python3.7, Python 3.7.4, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.7ubuntu1 apt 1.9.3 SourcePackage: nvidia-graphics-drivers-430 Title: package nvidia-dkms-430 430.40-0ubuntu2 failed to install/upgrade: installed nvidia-dkms-430 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to eoan on 2019-08-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1841762/+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 1841551] Re: Update to 0.20.1
** Changed in: gettext (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1841551 Title: Update to 0.20.1 Status in gettext package in Ubuntu: Triaged Status in gettext package in Debian: New Bug description: Requested to Debian as well on https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=934738 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/1841551/+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 1768539] Re: Conflicts between / and /usr
** Changed in: molly-guard (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1768539 Title: Conflicts between / and /usr Status in molly-guard package in Ubuntu: New Status in neutron-vpnaas package in Ubuntu: Fix Released Status in pm-utils package in Ubuntu: Fix Committed Status in safe-rm package in Ubuntu: Fix Released Status in molly-guard package in Debian: Fix Released Status in pm-utils package in Debian: Fix Released Status in safe-rm package in Debian: Fix Released Bug description: bin/rm and usr/bin/rm conflict between coreutils and safe-rm --- Not a conflict, but these just look weird: neutron-vpnaas ships these in python-neutron-vpnaas etc/neutron/rootwrap.d/vpnaas.filters usr/etc/neutron/rootwrap.d/vpnaas.filters --- pm-utils and molly-guard conflict on: sbin/pm-hibernate usr/sbin/pm-hibernate sbin/pm-suspend usr/sbin/pm-suspend sbin/pm-suspend-hybrid usr/sbin/pm-suspend-hybrid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/molly-guard/+bug/1768539/+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
