[Desktop-packages] [Bug 1933186] Re: gnome-shell crashed with SIGSEGV in meta_window_place() from place_window_if_needed() from meta_window_constrain() from meta_window_move_resize_internal() from met
** Summary changed: - /usr/bin/gnome-shell:11:meta_window_place:place_window_if_needed:meta_window_constrain:meta_window_move_resize_internal:meta_window_force_placement + gnome-shell crashed with SIGSEGV in meta_window_place() from place_window_if_needed() from meta_window_constrain() from meta_window_move_resize_internal() from meta_window_force_placement() ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #64 https://gitlab.gnome.org/GNOME/mutter/-/issues/64 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/64 Importance: Unknown Status: Unknown ** Changed in: mutter (Ubuntu) Status: New => Confirmed ** Tags removed: cosmic disco 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/1933186 Title: gnome-shell crashed with SIGSEGV in meta_window_place() from place_window_if_needed() from meta_window_constrain() from meta_window_move_resize_internal() from meta_window_force_placement() Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed 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.38.4-1ubuntu3, the problem page at https://errors.ubuntu.com/problem/7ae33f650c2de2c5580905f0c63e5b6c35fb46c6 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/mutter/+bug/1933186/+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 1933187] Re: gnome-shell-portal-helper crashed with SIGABRT in _dbus_abort() from _dbus_warn_check_failed() from _dbus_warn_return_if_fail() from dbus_message_new_method_call()
** Summary changed: - /usr/libexec/gnome-shell-portal-helper:6:_dbus_abort:_dbus_warn_check_failed:_dbus_warn_return_if_fail:dbus_message_new_method_call:socket_embed_hook + gnome-shell-portal-helper crashed with SIGABRT in _dbus_abort() from _dbus_warn_check_failed() from _dbus_warn_return_if_fail() from dbus_message_new_method_call() from socket_embed_hook() -- 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/1933187 Title: gnome-shell-portal-helper crashed with SIGABRT in _dbus_abort() from _dbus_warn_check_failed() from _dbus_warn_return_if_fail() from dbus_message_new_method_call() from socket_embed_hook() 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 40.1-0shemgpubuntu2, the problem page at https://errors.ubuntu.com/problem/bd34533f7e9069499d1fff35ad3ea274bdd877f3 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/1933187/+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 1933186] [NEW] gnome-shell crashed with SIGSEGV in meta_window_place() from place_window_if_needed() from meta_window_constrain() from meta_window_move_resize_internal() from m
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.38.4-1ubuntu3, the problem page at https://errors.ubuntu.com/problem/7ae33f650c2de2c5580905f0c63e5b6c35fb46c6 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: mutter Importance: Unknown Status: Unknown ** Affects: mutter (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: bionic focal groovy hirsute impish -- 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/1933186 Title: gnome-shell crashed with SIGSEGV in meta_window_place() from place_window_if_needed() from meta_window_constrain() from meta_window_move_resize_internal() from meta_window_force_placement() Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed 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.38.4-1ubuntu3, the problem page at https://errors.ubuntu.com/problem/7ae33f650c2de2c5580905f0c63e5b6c35fb46c6 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/mutter/+bug/1933186/+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 1933187] [NEW] gnome-shell-portal-helper crashed with SIGABRT in _dbus_abort() from _dbus_warn_check_failed() from _dbus_warn_return_if_fail() from dbus_message_new_method_call
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 40.1-0shemgpubuntu2, the problem page at https://errors.ubuntu.com/problem/bd34533f7e9069499d1fff35ad3ea274bdd877f3 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: hirsute -- 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/1933187 Title: gnome-shell-portal-helper crashed with SIGABRT in _dbus_abort() from _dbus_warn_check_failed() from _dbus_warn_return_if_fail() from dbus_message_new_method_call() from socket_embed_hook() 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 40.1-0shemgpubuntu2, the problem page at https://errors.ubuntu.com/problem/bd34533f7e9069499d1fff35ad3ea274bdd877f3 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/1933187/+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 1918855] Re: Xorg xserver got signal 6 to abort
I think it's another bug. The log from original bug report shows that
the system has 32G ram, so the abort() is less likely triggered by OOM.
--
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/1918855
Title:
Xorg xserver got signal 6 to abort
Status in Mesa:
Unknown
Status in OEM Priority Project:
In Progress
Status in Provider for Plainbox - Checkbox:
New
Status in mesa package in Ubuntu:
Fix Released
Status in mesa source package in Focal:
New
Status in mesa source package in Hirsute:
New
Bug description:
== SRU Justification ==
[Impact]
When the system is under memory pressure, the entire desktop session may
crash.
[Fix]
Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if
kernel can't allocate memory")
[Test]
Run memory stress and the session crashed in less than 5 minutes.
With the fix applied, run memory stress for 24 hours and the desktop session
is still alive.
[Where problems could occur]
Doing a reset might make the system even more sluggish when under memory
pressure.
== Original bug report ==
I run checkbox job com.canonical.certification::memory/memory_stress_ng on
focal, and the xserver stops unexpectedly with the following stacktrace:
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg
(OsLookupColor+0x13c) [0x5619f3a4d59c]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 1:
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6
(gsignal+0xcb) [0x7fae476a418b]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6
(abort+0x12b) [0x7fae47683859]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind
info found [-10]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 4:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 5:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec)
[0x7fae46529c9c]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 6:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 7:
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150)
[0x7fae47007480]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind
info found [-10]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 8:
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg
(BlockHandler+0xa5) [0x5619f38f0995]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg
(WaitForSomething+0x122) [0x5619f3a46c12]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg
(SendErrorToClient+0x117) [0x5619f38ebcf7]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg
(InitFonts+0x3b4) [0x5619f38effc4]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6
(__libc_start_main+0xf3) [0x7fae476850b3]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e)
[0x5619f38d9a2e]
More info:
I searched the Internet and got a bug with the same stacktrace:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859
To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1918855/+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 1933184] Re: /usr/libexec/gnome-shell-calendar-server:double free or corruption (fasttop)
*** This bug is a duplicate of bug 1915929 *** https://bugs.launchpad.net/bugs/1915929 ** This bug has been marked a duplicate of bug 1915929 gnome-shell-calendar-server assert failure on arm64: double free or corruption (fasttop) -- 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/1933184 Title: /usr/libexec/gnome-shell-calendar-server:double free or corruption (fasttop) 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.38.4-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/da135469ec9d609ad6c73389fe4aa648cc8eb9be 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/1933184/+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 1933184] [NEW] /usr/libexec/gnome-shell-calendar-server:double free or corruption (fasttop)
*** This bug is a duplicate of bug 1915929 *** https://bugs.launchpad.net/bugs/1915929 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.38.4-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/da135469ec9d609ad6c73389fe4aa648cc8eb9be 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: focal groovy hirsute kylin-20.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1933184 Title: /usr/libexec/gnome-shell-calendar-server:double free or corruption (fasttop) 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.38.4-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/da135469ec9d609ad6c73389fe4aa648cc8eb9be 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/1933184/+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 1497593] Re: [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed.
** Description changed: - webbrowser-app crashed with SIGABRT in __assert_fail_base() - - ProblemType: Crash - DistroRelease: Ubuntu 15.10 - Package: webbrowser-app 0.23+15.10.20150913-0ubuntu1 - ProcVersionSignature: Ubuntu 4.2.0-10.12-generic 4.2.0 - Uname: Linux 4.2.0-10-generic x86_64 - ApportVersion: 2.18.1-0ubuntu1 - Architecture: amd64 - CurrentDesktop: Unity - Date: Sat Sep 19 20:05:51 2015 - ExecutablePath: /usr/bin/webbrowser-app - InstallationDate: Installed on 2015-09-18 (1 days ago) - InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150918) - ProcCmdline: webbrowser-app - Signal: 6 - SourcePackage: webbrowser-app - StacktraceTop: - __assert_fail_base (fmt=0x7f1aba6fd028 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7f1aa469f879 "kref", file=file@entry=0x7f1aa469f85a "../../nouveau/pushbuf.c", line=line@entry=726, function=function@entry=0x7f1aa469f8a0 "nouveau_pushbuf_data") at assert.c:92 - __GI___assert_fail (assertion=0x7f1aa469f879 "kref", file=0x7f1aa469f85a "../../nouveau/pushbuf.c", line=726, function=0x7f1aa469f8a0 "nouveau_pushbuf_data") at assert.c:101 - nouveau_pushbuf_data () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 - nouveau_pushbuf_data () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 - ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 - Title: webbrowser-app crashed with SIGABRT in __assert_fail_base() - UpgradeStatus: No upgrade log present (probably fresh install) - UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' + failed. Because nouveau is not thread safe(?) -- 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/1497593 Title: [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. Status in Mesa: Unknown Status in libdrm package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. Because nouveau is not thread safe(?) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1497593/+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 1933181] Re: /usr/bin/gnome-shell:gnome-shell: ../nouveau/pushbuf.c:723\357\274\232nouveau_pushbuf_data: \345\201\207\350\256\276 \342\200\230kref\342\200\231 \345\244\261\350\
*** This bug is a duplicate of bug 1497593 *** https://bugs.launchpad.net/bugs/1497593 ** This bug has been marked a duplicate of bug 1497593 [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. -- 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/1933181 Title: /usr/bin/gnome-shell:gnome-shell: ../nouveau/pushbuf.c:723\357\274\232nouveau_pushbuf_data: \345\201\207\350\256\276 \342\200\230kref\342\200\231 \345\244\261\350\264\245\343\200\202 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.38.4-1ubuntu3~21.04.1, the problem page at https://errors.ubuntu.com/problem/45cbec119ded530df1a4f72ce263d765ed4fe3bd 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/1933181/+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 1933182] Re: /usr/bin/gnome-shell:gnome-shell: ../nouveau/pushbuf.c:723: nouveau_pushbuf_data: Zusicherung \302\273kref\302\253 nicht erf\303\274llt.
*** This bug is a duplicate of bug 1497593 *** https://bugs.launchpad.net/bugs/1497593 ** This bug has been marked a duplicate of bug 1497593 [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. -- 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/1933182 Title: /usr/bin/gnome-shell:gnome-shell: ../nouveau/pushbuf.c:723: nouveau_pushbuf_data: Zusicherung \302\273kref\302\253 nicht erf\303\274llt. 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.38.4-1ubuntu3~21.04.1, the problem page at https://errors.ubuntu.com/problem/0280bf08af71b648042f1e6ec027b1097fb7e1c0 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/1933182/+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 1933181] [NEW] /usr/bin/gnome-shell:gnome-shell: ../nouveau/pushbuf.c:723\357\274\232nouveau_pushbuf_data: \345\201\207\350\256\276 \342\200\230kref\342\200\231 \345\244\261\35
*** This bug is a duplicate of bug 1497593 *** https://bugs.launchpad.net/bugs/1497593 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.38.4-1ubuntu3~21.04.1, the problem page at https://errors.ubuntu.com/problem/45cbec119ded530df1a4f72ce263d765ed4fe3bd 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: focal groovy hirsute -- 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/1933181 Title: /usr/bin/gnome-shell:gnome-shell: ../nouveau/pushbuf.c:723\357\274\232nouveau_pushbuf_data: \345\201\207\350\256\276 \342\200\230kref\342\200\231 \345\244\261\350\264\245\343\200\202 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.38.4-1ubuntu3~21.04.1, the problem page at https://errors.ubuntu.com/problem/45cbec119ded530df1a4f72ce263d765ed4fe3bd 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/1933181/+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 1933182] [NEW] /usr/bin/gnome-shell:gnome-shell: ../nouveau/pushbuf.c:723: nouveau_pushbuf_data: Zusicherung \302\273kref\302\253 nicht erf\303\274llt.
*** This bug is a duplicate of bug 1497593 *** https://bugs.launchpad.net/bugs/1497593 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.38.4-1ubuntu3~21.04.1, the problem page at https://errors.ubuntu.com/problem/0280bf08af71b648042f1e6ec027b1097fb7e1c0 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 focal groovy hirsute -- 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/1933182 Title: /usr/bin/gnome-shell:gnome-shell: ../nouveau/pushbuf.c:723: nouveau_pushbuf_data: Zusicherung \302\273kref\302\253 nicht erf\303\274llt. 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.38.4-1ubuntu3~21.04.1, the problem page at https://errors.ubuntu.com/problem/0280bf08af71b648042f1e6ec027b1097fb7e1c0 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/1933182/+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 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()
Fixed in bug 1918855? -- 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/1871959 Title: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush() Status in Mesa: Unknown Status in mesa package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f --- nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:50:52 2020 DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56 DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2019-11-27 (134 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5500 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server 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/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago) UserGroups: dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1871959/+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 1918855] Re: Xorg xserver got signal 6 to abort
Is this the same issue as bug 1871959?
--
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/1918855
Title:
Xorg xserver got signal 6 to abort
Status in Mesa:
Unknown
Status in OEM Priority Project:
In Progress
Status in Provider for Plainbox - Checkbox:
New
Status in mesa package in Ubuntu:
Fix Released
Status in mesa source package in Focal:
New
Status in mesa source package in Hirsute:
New
Bug description:
== SRU Justification ==
[Impact]
When the system is under memory pressure, the entire desktop session may
crash.
[Fix]
Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if
kernel can't allocate memory")
[Test]
Run memory stress and the session crashed in less than 5 minutes.
With the fix applied, run memory stress for 24 hours and the desktop session
is still alive.
[Where problems could occur]
Doing a reset might make the system even more sluggish when under memory
pressure.
== Original bug report ==
I run checkbox job com.canonical.certification::memory/memory_stress_ng on
focal, and the xserver stops unexpectedly with the following stacktrace:
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg
(OsLookupColor+0x13c) [0x5619f3a4d59c]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 1:
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6
(gsignal+0xcb) [0x7fae476a418b]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6
(abort+0x12b) [0x7fae47683859]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind
info found [-10]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 4:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 5:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec)
[0x7fae46529c9c]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 6:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 7:
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150)
[0x7fae47007480]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind
info found [-10]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 8:
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg
(BlockHandler+0xa5) [0x5619f38f0995]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg
(WaitForSomething+0x122) [0x5619f3a46c12]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg
(SendErrorToClient+0x117) [0x5619f38ebcf7]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg
(InitFonts+0x3b4) [0x5619f38effc4]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6
(__libc_start_main+0xf3) [0x7fae476850b3]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e)
[0x5619f38d9a2e]
More info:
I searched the Internet and got a bug with the same stacktrace:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859
To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1918855/+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 1931701] Re: autopkgtests failures on armhf of 7.1.4
A better workaround was applied to the hirsute SRU https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?id=c832999071e9582ca7e4405cb7a7cfcbd656279d -- 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/1931701 Title: autopkgtests failures on armhf of 7.1.4 Status in gcc-9 package in Ubuntu: New Status in libreoffice package in Ubuntu: New Status in gcc-9 source package in Hirsute: New Status in libreoffice source package in Hirsute: New Status in gcc-9 source package in Impish: New Status in libreoffice source package in Impish: New Bug description: The autopkgtests for 7.1.4~rc2-0ubuntu1 on impish/armhf has started to fail reliably. https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/armhf/libr/libreoffice/20210610_121847_0ab56@/log.gz "/usr/lib/libreoffice/program/unopkg" add -f "/tmp/tmp.oOlP0i1pzN/out/sdk/LINUXexample.out/bin/SampleDialog.oxt" # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0xf47474b8, pid=35616, tid=35643 # # JRE version: OpenJDK Runtime Environment (11.0.12+4) (build 11.0.12-ea+4-Ubuntu-0ubuntu2) # Java VM: OpenJDK Server VM (11.0.12-ea+4-Ubuntu-0ubuntu2, mixed mode, g1 gc, linux-) # Problematic frame: # C [libbootstraplo.so+0x1c4b8] stoc_impreg::mergeKeys(com::sun::star::uno::Reference const&, com::sun::star::uno::Reference const&, std::vector >&)+0xb # # Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport %p %s %c %d %P %E" (or dumping to /usr/lib/libreoffice/sdk/examples/DevelopersGuide/BasicAndDialogs/CreatingDialogs/core.35616) # # An error report file with more information is saved as: # /tmp/hs_err_pid35616.log # # If you would like to submit a bug report, please visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-lts # ERROR: Exception occurred: Binary URP bridge disposed during call ./binaryurp/source/bridge.cxx:613 ERROR: unopkg failed. make[1]: Leaving directory '/usr/lib/libreoffice/sdk/examples/DevelopersGuide/BasicAndDialogs/CreatingDialogs' make[1]: *** [Makefile:112: /tmp/tmp.oOlP0i1pzN/out/sdk/LINUXexample.out/misc/devguide_basicanddialogs_creatingdialogs_register_component.flag] Error 1 make[1]: Target 'ALL' not remade because of errors. make: *** [/tmp/autopkgtest.U74TIg/build.myd/src/odk/CustomTarget_build-examples_java.mk:62: /tmp/autopkgtest.U74TIg/build.myd/src/workdir/CustomTarget/odk/build-examples_java.done] Error 2 make: Target 'CustomTarget_odk/build-examples_java' not remade because of errors. While a re-run of the test for 7.1.3-0ubuntu1 were successful it suggests it is binary problem. https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/armhf/libr/libreoffice/20210609_234830_1265b@/log.gz liberoffice is built with gcc-9/g++-9 on armhf to avoid https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/1891623 A significant difference in the used toolchain points to the update of gcc-9 7.1.3-0ubuntu1 was built with gcc 9.3.0-24ubuntu1 https://launchpadlibrarian.net/537628130/buildlog_ubuntu-impish-armhf.libreoffice_1%3A7.1.3-0ubuntu1_BUILDING.txt.gz 7.1.4~rc2-0ubuntu1 was built with gcc 9.4.0-1ubuntu1 https://launchpadlibrarian.net/542492348/buildlog_ubuntu-impish-armhf.libreoffice_1%3A7.1.4~rc2-0ubuntu1_BUILDING.txt.gz Regarding 21.04/Hirsute 1:7.1.4~rc2-0ubuntu0.21.04.1~lo1 built and successfully ran autopkgtests, see https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1931272 If was using the gcc-9 9.3.0-23ubuntu2 available at the time. The no-change rebuild against 9.4.0-1ubuntu1~21.04 results in the same failure now. https://launchpadlibrarian.net/543392061/buildlog_ubuntu-hirsute-armhf.libreoffice_1%3A7.1.4~rc2-0ubuntu0.21.04.1~lo1_BUILDING.txt.gz https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-experimental/hirsute/armhf/libr/libreoffice/20210612_113218_f7f69@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1931701/+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 1918855] Re: Xorg xserver got signal 6 to abort
** Also affects: mesa (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: mesa (Ubuntu Focal)
Importance: Undecided
Status: New
--
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/1918855
Title:
Xorg xserver got signal 6 to abort
Status in Mesa:
Unknown
Status in OEM Priority Project:
In Progress
Status in Provider for Plainbox - Checkbox:
New
Status in mesa package in Ubuntu:
Fix Released
Status in mesa source package in Focal:
New
Status in mesa source package in Hirsute:
New
Bug description:
== SRU Justification ==
[Impact]
When the system is under memory pressure, the entire desktop session may
crash.
[Fix]
Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if
kernel can't allocate memory")
[Test]
Run memory stress and the session crashed in less than 5 minutes.
With the fix applied, run memory stress for 24 hours and the desktop session
is still alive.
[Where problems could occur]
Doing a reset might make the system even more sluggish when under memory
pressure.
== Original bug report ==
I run checkbox job com.canonical.certification::memory/memory_stress_ng on
focal, and the xserver stops unexpectedly with the following stacktrace:
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg
(OsLookupColor+0x13c) [0x5619f3a4d59c]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 1:
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6
(gsignal+0xcb) [0x7fae476a418b]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6
(abort+0x12b) [0x7fae47683859]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind
info found [-10]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 4:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 5:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec)
[0x7fae46529c9c]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 6:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 7:
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150)
[0x7fae47007480]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind
info found [-10]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 8:
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg
(BlockHandler+0xa5) [0x5619f38f0995]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg
(WaitForSomething+0x122) [0x5619f3a46c12]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg
(SendErrorToClient+0x117) [0x5619f38ebcf7]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg
(InitFonts+0x3b4) [0x5619f38effc4]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6
(__libc_start_main+0xf3) [0x7fae476850b3]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e)
[0x5619f38d9a2e]
More info:
I searched the Internet and got a bug with the same stacktrace:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859
To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1918855/+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 1770587]
Does this still happen?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1770587
Title:
creation of new email account impossible in thunderbird
Status in Mozilla Thunderbird:
Confirmed
Status in thunderbird package in Ubuntu:
Confirmed
Bug description:
With Ubuntu 18.04, creation of new email account is not possible.
You have a first screen "Would you like a new email address?" and no button
is active
I have restarted with add-on disabled but same issue
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: thunderbird 1:52.7.0+build1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jmax 2698 F pulseaudio
BuildID: 20180416164209
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Fri May 11 10:07:03 2018
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
Français Language Pack - langpack...@thunderbird.mozilla.org
English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2016-01-31 (830 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
IpRoute:
default via 192.168.0.254 dev wlo1 proto dhcp metric 600
10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.32 metric 600
MostRecentCrashID: bp-da66c229-e498-447a-8233-47b610170721
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=52.7.0/20180416164209 (In use)
RunningIncompatibleAddons: True
SourcePackage: thunderbird
UpgradeStatus: Upgraded to bionic on 2018-04-28 (12 days ago)
dmi.bios.date: 07/20/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.1A
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3581
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 10.31
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnHewlett-Packard:bvrF.1A:bd07/20/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058F1124461620100:rvnHewlett-Packard:rn3581:rvr10.31:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
dmi.product.name: HP Pavilion dv6 Notebook PC
dmi.product.version: 058F1124461620100
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1770587/+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 1933168] Re: Show Applications button does not bring up application after setting show-favorites to false
** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1933168 Title: Show Applications button does not bring up application after setting show-favorites to false Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Description: When setting show-favorites to false by following command, log out/in or reboot, show applications button does not bring up applications: gsettings set org.gnome.shell.extensions.dash-to-dock show-favorites false Expect results: Show Applications button can bring up application Actual results: Show Applications button does not do anything, applications won't show up OS: Ubuntu 20.04.2 LTS Gnome-shell version: 3.36.7-0ubuntu0.20.04.1 gnome-shell-extension-ubuntu-dock version: 68ubuntu1~20.04.1 Error: gnome-shell[2110]: JS ERROR: TypeError: Main.overview.viewSelector._activePage is null _onShowAppsButtonToggled@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1912:25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1933168/+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 1933168] [NEW] Show Applications button does not bring up application after setting show-favorites to false
Public bug reported: Description: When setting show-favorites to false by following command, log out/in or reboot, show applications button does not bring up applications: gsettings set org.gnome.shell.extensions.dash-to-dock show-favorites false Expect results: Show Applications button can bring up application Actual results: Show Applications button does not do anything, applications won't show up OS: Ubuntu 20.04.2 LTS Gnome-shell version: 3.36.7-0ubuntu0.20.04.1 gnome-shell-extension-ubuntu-dock version: 68ubuntu1~20.04.1 Error: gnome-shell[2110]: JS ERROR: TypeError: Main.overview.viewSelector._activePage is null _onShowAppsButtonToggled@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1912:25 ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1933168 Title: Show Applications button does not bring up application after setting show-favorites to false Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Description: When setting show-favorites to false by following command, log out/in or reboot, show applications button does not bring up applications: gsettings set org.gnome.shell.extensions.dash-to-dock show-favorites false Expect results: Show Applications button can bring up application Actual results: Show Applications button does not do anything, applications won't show up OS: Ubuntu 20.04.2 LTS Gnome-shell version: 3.36.7-0ubuntu0.20.04.1 gnome-shell-extension-ubuntu-dock version: 68ubuntu1~20.04.1 Error: gnome-shell[2110]: JS ERROR: TypeError: Main.overview.viewSelector._activePage is null _onShowAppsButtonToggled@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1912:25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1933168/+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 1933118] Re: Screen freeze
Please also: * Check the 'Extensions' app to ensure you don't have any extensions other than the three Ubuntu extensions. Any others should be removed, then log in again. * Next time the problem happens, wait 10 seconds, reboot and then run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** Tags added: nvidia -- 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/1933118 Title: Screen freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: This bug appears to be a deadlock of some kind. It most often happens when I move the mouse (external USB mouse), but it has once happened when I left the computer logged in but idle and has sometimes happened in video conferences. When the problem occurs, the mouse cursor still moves and any audio continues being audible for a while, but the UI is frozen and unresponsive. The fan gets very loud as if the computer is doing a lot of work. If I try the 'REISUB' method of shutting down, it usually does not work. If I remote log in and do a shutdown, it takes several minutes to actually shut down - as if waiting for some process to time out. I haven't any obvious errors for this bug, and i don't know where to look for possible error messages. It is possible that if there is a deadlock, there is no error message, unless shutting down causes the process to generate an error message. The bug happens very often, sometimes several times a week. If you could tell me what commands to run when the problem occurs in order to gather more information, I can remote login and run those commands. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.143 Fri Mar 12 07:24:47 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 21 15:14:30 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.3, 5.8.0-53-generic, x86_64: installed v4l2loopback, 0.12.3, 5.8.0-55-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since before I upgraded GraphicsCard: NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GK107GLM [Quadro K1100M] [103c:2256] InstallationDate: Installed on 2021-01-11 (161 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP ZBook 17 G2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=62a0870e-1f83-43a4-a2ff-864901a24fb6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2015 dmi.bios.release: 1.12 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M70 Ver. 01.12 dmi.board.name: 2255 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 03.10 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 3.16 dmi.modalias: dmi:bvnHewlett-Packard:bvrM70Ver.01.12:bd09/23/2015:br1.12:efr3.16:svnHewlett-Packard:pnHPZBook17G2:pvrA3009DD10203:rvnHewlett-Packard:rn2255:rvrKBCVersion03.10:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP ZBook 17 G2 dmi.product.sku: G6Z41AV dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to:
[Desktop-packages] [Bug 1933118] Re: Xorg freeze
If the mouse cursor still moves then Xorg is still working. This usually means it's the gnome-shell process that has frozen or crashed, so please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Summary changed: - Xorg freeze + Screen freeze -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1933118 Title: Screen freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: This bug appears to be a deadlock of some kind. It most often happens when I move the mouse (external USB mouse), but it has once happened when I left the computer logged in but idle and has sometimes happened in video conferences. When the problem occurs, the mouse cursor still moves and any audio continues being audible for a while, but the UI is frozen and unresponsive. The fan gets very loud as if the computer is doing a lot of work. If I try the 'REISUB' method of shutting down, it usually does not work. If I remote log in and do a shutdown, it takes several minutes to actually shut down - as if waiting for some process to time out. I haven't any obvious errors for this bug, and i don't know where to look for possible error messages. It is possible that if there is a deadlock, there is no error message, unless shutting down causes the process to generate an error message. The bug happens very often, sometimes several times a week. If you could tell me what commands to run when the problem occurs in order to gather more information, I can remote login and run those commands. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.143 Fri Mar 12 07:24:47 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 21 15:14:30 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.3, 5.8.0-53-generic, x86_64: installed v4l2loopback, 0.12.3, 5.8.0-55-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since before I upgraded GraphicsCard: NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GK107GLM [Quadro K1100M] [103c:2256] InstallationDate: Installed on 2021-01-11 (161 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP ZBook 17 G2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=62a0870e-1f83-43a4-a2ff-864901a24fb6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2015 dmi.bios.release: 1.12 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M70 Ver. 01.12 dmi.board.name: 2255 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 03.10 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 3.16 dmi.modalias: dmi:bvnHewlett-Packard:bvrM70Ver.01.12:bd09/23/2015:br1.12:efr3.16:svnHewlett-Packard:pnHPZBook17G2:pvrA3009DD10203:rvnHewlett-Packard:rn2255:rvrKBCVersion03.10:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP ZBook 17 G2 dmi.product.sku: G6Z41AV dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
[Desktop-packages] [Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver
Timo, Do you have an ETA when this would be released to focal-update? -- 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/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver Status in OEM Priority Project: New Status in OEM Priority Project focal series: New Status in xorg-server package in Ubuntu: Fix Released Bug description: [Impact] The cursor bleeds because of the bug in xorg which does not refresh the sprite background. (LP: #1911479) The issue happens to Xilinx zcu102/104/106 boards (arm64, mali gpu). [Test Case] Check if cursor is still bleeding with the patched xorg-server [ Regression potential ] The new function, miDCSaveUnderCursor2, is only used by Xilinx armsoc driver. It won't impact other platforms. --- Xilinx is trying to upstream the patch. It's still under review. https://lists.x.org/archives/xorg-devel/2021-March/058672.html To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+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 1933022] Re: gnome control-center crashed with sigsegv in g_str_hash() whenever I try to add input sources
The stack trace is different but that's to be expected in cases like
this.
That upstream fix landed after version 40.0 so no it won't be included
in gnome-desktop3 version 40.0-1. And no release of Ubuntu has any
version newer than 3.38.5 yet.
** Also affects: gnome-desktop via
https://gitlab.gnome.org/GNOME/gnome-desktop/-/issues/190
Importance: Unknown
Status: Unknown
** Changed in: gnome-desktop3 (Ubuntu)
Status: Incomplete => New
** Changed in: gnome-desktop3 (Ubuntu)
Status: New => Fix Committed
** Tags added: fixed-in-40.2 fixed-upstream
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-desktop3 in Ubuntu.
https://bugs.launchpad.net/bugs/1933022
Title:
gnome control-center crashed with sigsegv in g_str_hash() whenever I
try to add input sources
Status in gnome-desktop:
Unknown
Status in gnome-desktop3 package in Ubuntu:
Fix Committed
Bug description:
I've been facing the problems for about 9 months now. Back then I
thought that maybe getting a new version would solve the problem, but
turns out it didn't. Whenever I try to add some Input Sources from it
just crashes.
Reproducing it is very easy: running gnome-control-center, then going
to Input Sources settings and clicking Add(+) would generate the
crash. But the weird thing is that I've been unable to reproduce it in
VM. And I also tried to reinstall most of the packages which, I think
if changed/misconfigured would cause this but it didn't help. I also
tried to use debsums to give some clues but didn't find any.
After enough digging, this is what I can retrieve from gdb:
#0 g_str_hash (v=0x506) at ../../../glib/ghash.c:2333
p = 0x506
h = 5381
#1 0x77c6e174 in g_hash_table_lookup_node (hash_return=, key=0x506, hash_table=0x563a6180 = {...}) at
../../../glib/ghash.c:472
node_hash =
hash_value =
have_tombstone = 0
step = 0
node_index =
first_tombstone = 0
node_hash =
__func__ = "g_hash_table_lookup_extended"
#2 g_hash_table_lookup_extended (hash_table=0x563a6180 = {...},
lookup_key=lookup_key@entry=0x506, orig_key=orig_key@entry=0x0,
value=value@entry=0x7fffcbb0) at ../../../glib/ghash.c:1548
node_hash =
__func__ = "g_hash_table_lookup_extended"
#3 0x76f03013 in gnome_xkb_info_get_layout_info (self=, id=id@entry=0x506 ,
display_name=display_name@entry=0x7fffcc10,
short_name=short_name@entry=0x0, xkb_layout=xkb_layout@entry=0x0,
xkb_variant=xkb_variant@entry=0x0) at ../libgnome-desktop/gnome-xkb-info.c:1042
priv = 0x56395600
layout = 0x76262ba0
__func__ = "gnome_xkb_info_get_layout_info"
#4 0x555fe467 in input_source_row_new
(self=self@entry=0x568d22b0, type=type@entry=0x556dcac3 "xkb",
id=id@entry=0x506 ) at
../panels/keyboard/cc-input-chooser.c:236
display_name = 0x0
row = 0x0
widget =
#5 0x555fe81d in add_rows_to_table (self=self@entry=0x568d22b0,
info=info@entry=0x56450320, list=0x55c82100 = {...},
list@entry=0x55c8bec0 = {...}, type=type@entry=0x556dcac3 "xkb",
default_id=0x0) at ../panels/keyboard/cc-input-chooser.c:723
table = 0x5677 = {[0x5657bb00 "cm+mmuock"] =
0x56ca91a0, [0x56506340 "us+3l"] = 0x56400920, [0x5656f6f0
"ph+capewell-dvorak"] = 0x56cb6f50, [0x5660caf0 "us+dvorak-l"] =
0x56ca9620, [0x5656cd40 "gb+mac_intl"] = 0x56cb6950,
[0x5650de80 "gh+gillbt"] = 0x56cb61d0, [0x56571540 "apl+aplx"] =
0x56ca94a0, [0x565063a0 "us+3l-cros"] = 0x56cb64d0, [0x565062b0
"us+carpalx-full-intl"] = 0x56400aa0, [0x56506070 "us+sun_type6"] =
0x56cb6350, [0x56505f50 "us+drix"] = 0x56ca9320, [0x56506b40
"cm+dvorak"] = 0x56cb6dd0, [0x564faaf0 "us+dvp"] = 0x56cb6650,
[0x564faa80 "us+dvorak-classic"] = 0x564004a0, [0x564fad30
"us+olpc2"] = 0x56400c20, [0x5656f2d0 "ml+us-intl"] = 0x56400620,
[0x564f9c70 "eu"] = 0x56400320, [0x56506310
"us+carpalx-full-altgr-intl"] = 0x564007a0, [0x5656c390 "gb+intl"] =
0x56ca97a0, [0x56506fc0 "ca+eng"] = 0x56cb67d0, [0x565714a0
"apl+aplplusII"] = 0x56400f20, [0x564fafb0 "us+norman"] =
0x56400da0, [0x5660ca90 "us+dvorak-intl"] = 0x56cb6ad0,
[0x56506140 "us+carpalx-intl"] = 0x56cb6c50}
row =
id = 0x506
#6 0x555ffb78 in get_locale_infos (self=0x568d22b0) at
../panels/keyboard/cc-input-chooser.c:950
country_code = 0x5680eb50 "BW"
simple_locale = 0x5680eb70 "en_BW.UTF-8"
tmp = 0x568acf70 "English (Botswana)"
type = 0x0
language_layouts = 0x55c8bec0
lang_code =
[Desktop-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- 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/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" Status in amd: New Status in linux-firmware package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Confirmed Bug description: After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and severe GPU instability. When this happens, I see this error in dmesg: [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 pid 1236) [20061.061103] amdgpu :03:00.0: amdgpu: in page starting at address 0x80401000 from client 27 [20061.061135] amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00101031 [20061.061147] amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [20061.061157] amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 [20061.061167] amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 [20061.061174] amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [20061.061183] amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 [20061.061189] amdgpu :03:00.0: amdgpu: RW: 0x0 I'll attach a couple of full dmesgs that I collected. Many of the times when this happens, the screen and keyboard freeze irreversibly (I tried waiting for more than 30 minutes, but it doesn't help). I can still log in via ssh though. When there's no freeze, I can continue using the computer normally, but the laptop fans keep running are always running and the battery depletes fast. There's probably something on a permanent loop either in the kernel or in the GPU. This bug happens several times a day, rendering the machine so unstable as to be almost unusable. It is a severe regression and I'm aghast that it passed AMD's Quality Assurance. After downgrading back to linux-firmware 1.190.5, the machine is back to the previous, mostly-reliable state. Which is to say, this bug is gone, I'm just left with the other amdgpu suspend bug I've learned to live with since I bought this computer. Please revert the amdgpu firmware in this package as soon as possible. This is unbearable. Relevant information: Ubuntu version: 21.04 Linux kernel: 5.11.0-17-generic x86_64 CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c1) Laptop model: Lenovo Ideapad S145 To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+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 1932981] Re: desktop mouse selection appears on secondary monitor
** Also affects: gnome-shell-extension-desktop-icons-ng via https://gitlab.com/rastersoft/desktop-icons-ng/-/issues/151 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons-ng in Ubuntu. https://bugs.launchpad.net/bugs/1932981 Title: desktop mouse selection appears on secondary monitor Status in Gnome Shell Extension Desktop Icons Ng: Unknown Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Triaged Bug description: With a secondary monitor on the left, a mouse highlight on the desktop creates a slight selection box on the primary one, after the Ubuntu dock. If this isn't clear, see the attached screenshot. Expected: Only see the selection *where I selected*. Actual: Selection appears slightly on the primary monitor Also tested with all shell extensions disabled. badboyhalocat@bbhc-laptop:~$ lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 badboyhalocat@bbhc-laptop:~$ apt-cache policy gnome-shell gnome-shell: Installed: 3.38.4-1ubuntu3~21.04.1 Candidate: 3.38.4-1ubuntu3~21.04.1 Version table: *** 3.38.4-1ubuntu3~21.04.1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu hirsute-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.38.4-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-20.21-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jun 18 17:28:26 2021 DisplayManager: gdm3 ProcEnviron: LANGUAGE=en.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-05-13 (36 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1932981/+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 1932979] Re: blank screen with cursor after login
Neither step 1 nor step 2 gave me anything unfortunately. I've commented out the the problem types field, so perhaps I'll get more useful data eventually. This is a rare occurrence. -- 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/1932979 Title: blank screen with cursor after login Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 on amd64. I came back to the machine after it was idle long enough for the screen to go blank. I can see the cursor move with the mouse, but nothing else. This is VT2. VT1 shows a login screen. I can get to console VTs as well and did so to file the report. I see the following in the system log that may be related: Jun 18 18:29:54 cerberus gnome-shell[4694]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed Jun 18 18:29:54 cerberus gnome-shell[4694]: Source ID 3568871 was not found when attempting to remove it Jun 18 18:29:54 cerberus gnome-shell[4694]: Source ID 3568998 was not found when attempting to remove it Jun 18 18:29:54 cerberus gnome-shell[4694]: Source ID 3569045 was not found when attempting to remove it Jun 18 18:29:54 cerberus gnome-shell[4694]: [System monitor] applet disable Jun 18 18:29:54 cerberus gnome-shell[4694]: g_dbus_connection_emit_signal: assertion 'G_IS_DBUS_CONNECTION (connection)' failed ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114 Uname: Linux 5.4.0-74-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 18 19:33:55 2021 DistUpgraded: 2020-11-04 10:03:47,100 DEBUG running doUpdate() (showErrors=True) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev c7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Radeon RX 480 [1043:04fb] InstallationDate: Installed on 2020-05-29 (385 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Supermicro X10DAi ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=linux XDG_RUNTIME_DIR= PATH=(custom, user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-74-generic root=/dev/mapper/ubuntu--vg-root ro amdgpu.dc=0 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-11-04 (226 days ago) dmi.bios.date: 12/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X10DAI dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.2:bd12/16/2019:svnSupermicro:pnX10DAi:pvr123456789:rvnSupermicro:rnX10DAI:rvr1.01:cvnTobefilledbyO.E.M.:ct3:cvrTobefilledbyO.E.M.: dmi.product.family: SMC X10 dmi.product.name: X10DAi dmi.product.sku: 083615D9 dmi.product.version: 123456789 dmi.sys.vendor: Supermicro version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1932979/+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 1922353] Re: Overview sometimes fails to appear or disappear in gnome-shell 3.38
Possibly Robert asked about version 3.38.4-1ubuntu3~21.04.1 of gnome- shell. In that case the answer is yes, it's available through the Software Updater. -- 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/1922353 Title: Overview sometimes fails to appear or disappear in gnome-shell 3.38 Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Hirsute: Fix Released Status in gnome-shell source package in Impish: Fix Released Bug description: [Impact] Shell overview gets stuck where it's permanently toggled but not visible. Only app windows appear in their overview state. Can't interact with applications anymore. [Test Plan] 1. Log into GNOME. 2. Press Super+A 3. Click on 'Files' and wait till it has launched. 4. Press the Super key. Expect: Can interact with the application window. [Where problems could occur] Since the patch affects some of the core gnome-shell layout logic, anything is possible. Risk has been mitigated by the patch being small. [Original description] When I press the "windows" or "options" or "super" key a list of running applications (like alt-tab) and a text window appears. I can choose from the running applications or write a command into the text window. After I chose an application or press ESC all this disappear and I can do my thing. Since trying 21.04 sometimes this 1. does not appear properly - there is no visible text window 2. does not disappear - despite what I click on or what keys do I press this never disappear so I can not use my running applications or start anything new even from the menu. I have to log out and in to break this. Disabling my gnome-shell extensions or using xorg instead of wayland does not helps. Since upgrading this morning this happens every time I press Super, not just occasionally, thus making my desktop unusable. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 14:07:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-19 (378 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1922353/+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 1923845] Re: Please compress packages with zstd by default
This bug was fixed in the package reprepro - 5.3.0-1.3
---
reprepro (5.3.0-1.3) experimental; urgency=medium
* Non-maintainer upload.
* Add support for Zstd compressed debs. (LP: #1923845)
-- Dimitri John Ledkov Mon, 21 Jun 2021 10:16:53
+0100
** Changed in: reprepro (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream-glib in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
Fix Released
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
Fix Released
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
New
Status in dpkg package in Ubuntu:
New
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in hello package in Ubuntu:
Fix Released
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
Fix Released
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
Fix Released
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz=1=1
https://codesearch.debian.net/search?q=control.tar.xz=1=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
libsolv - needs fix, ext/repo_deb.c
lintian - needs fix malformed-deb-archive
lutris - needs fix, lutris/util/extract.py
obs-build - needs fix Build/Deb.pm
osc - needs fix osc/util/debquery.py control.tar.zst only
python-apt - needs fix
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
radare2 - needs fix
reprepro- needs fix, debfile.c
vim-scripts - needs fix debPlugin/autoload/deb.vim
winetricks - needs fix when Debian switches src/winetricks
zeroinstall-injector - needs fix src/zeroinstall/archive.ml
acr - skip, does not _have to_ be fixed, just creates packages,
see dist/deb_hand.mak
alien - skip, uses dpkg-deb to extract .deb
ansible - not affected, just test data in dbdata.tar.xz
anthy - not affected, just changelog entry
apt - seems fixed already
ceph- not affected in Ubuntu's version
circlator - not affected, just test data
cowdancer - not affected, just documentation
eccodes - skip, just orig-data.tar.xz
eckit - skip, just ...orig-data.tar.xz
firefox - skip, profdata.tar.xz
firefox-esr - skip,
[Desktop-packages] [Bug 487720] Re: Restore fails with "Invalid data - SHA1 hash mismatch"
Still a problem in Ubuntu 20.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/487720 Title: Restore fails with "Invalid data - SHA1 hash mismatch" Status in Déjà Dup: Invalid Status in Duplicity: Fix Released Status in duplicity package in Ubuntu: Fix Released Status in duplicity source package in Lucid: Fix Released Status in duplicity source package in Maverick: Won't Fix Status in duplicity source package in Natty: Fix Released Bug description: When restoring a backup, one might see an error like: Invalid data - SHA1 hash mismatch: Calculated hash: 0b2bc4c2fb98b36f9891f9172f909d70ab5662e9 Manifest hash: 11cd330357618de52e4e5361a6e63b09ee951ae2 This can happen when a volume file was not completely written to the backend before duplicity was interrupted (say, shutting down the machine or whatever). When duplicity resumes the backup next run, it will start with the next volume. The half-complete volume file will sit on the backend and cause this error later when restoring. You can manually recover from this by either restoring from your older backup sets or by restoring individual files that don't happen to be in the corrupted volume. == To Reproduce == See attachment https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/487720/+attachment/2159465/+files/test.sh for a test script tor reproduce the problem. == Ubuntu SRU Justification == This is a serious data loss problem for users, which won't be noticed until they try to restore. With Ubuntu 11.10 including Deja Dup, some users may think to back up their data first then upgrade, and may accidentally create corrupted backups. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/487720/+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 1933022] Re: gnome control-center crashed with sigsegv in g_str_hash() whenever I try to add input sources
But seeing the version number seems like that I have the exact same
version(40.0-1) installed. So doesn't that mean the patch should be
applied already? But nonetheless I would want to try a candidate fix if
I get one.
And about the bug, I think this is somehow related to dconf database
because when I had tried to add a source with a newly created account on
the same machine, it did work, didn't crash (Exactly that's why I had
been unable to reproduce it in vm). And noticing that I tried resetting
few values to default on the dconf database related to ibus and input-
sources( and losing some input settings along the way) the bug vanished.
So yeah it's fixed for me but I would be following up and will try to
analyze exactly which key or keys triggers the bug and will let you know
if I find any.
Furthermore, I don't know where but I can faintly remember that I saw
something along the lines "Tried to access null vma" So that means it's
a null pointer related bug too.
** Tags added: dconf gio
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-desktop3 in Ubuntu.
https://bugs.launchpad.net/bugs/1933022
Title:
gnome control-center crashed with sigsegv in g_str_hash() whenever I
try to add input sources
Status in gnome-desktop3 package in Ubuntu:
Incomplete
Bug description:
I've been facing the problems for about 9 months now. Back then I
thought that maybe getting a new version would solve the problem, but
turns out it didn't. Whenever I try to add some Input Sources from it
just crashes.
Reproducing it is very easy: running gnome-control-center, then going
to Input Sources settings and clicking Add(+) would generate the
crash. But the weird thing is that I've been unable to reproduce it in
VM. And I also tried to reinstall most of the packages which, I think
if changed/misconfigured would cause this but it didn't help. I also
tried to use debsums to give some clues but didn't find any.
After enough digging, this is what I can retrieve from gdb:
#0 g_str_hash (v=0x506) at ../../../glib/ghash.c:2333
p = 0x506
h = 5381
#1 0x77c6e174 in g_hash_table_lookup_node (hash_return=, key=0x506, hash_table=0x563a6180 = {...}) at
../../../glib/ghash.c:472
node_hash =
hash_value =
have_tombstone = 0
step = 0
node_index =
first_tombstone = 0
node_hash =
__func__ = "g_hash_table_lookup_extended"
#2 g_hash_table_lookup_extended (hash_table=0x563a6180 = {...},
lookup_key=lookup_key@entry=0x506, orig_key=orig_key@entry=0x0,
value=value@entry=0x7fffcbb0) at ../../../glib/ghash.c:1548
node_hash =
__func__ = "g_hash_table_lookup_extended"
#3 0x76f03013 in gnome_xkb_info_get_layout_info (self=, id=id@entry=0x506 ,
display_name=display_name@entry=0x7fffcc10,
short_name=short_name@entry=0x0, xkb_layout=xkb_layout@entry=0x0,
xkb_variant=xkb_variant@entry=0x0) at ../libgnome-desktop/gnome-xkb-info.c:1042
priv = 0x56395600
layout = 0x76262ba0
__func__ = "gnome_xkb_info_get_layout_info"
#4 0x555fe467 in input_source_row_new
(self=self@entry=0x568d22b0, type=type@entry=0x556dcac3 "xkb",
id=id@entry=0x506 ) at
../panels/keyboard/cc-input-chooser.c:236
display_name = 0x0
row = 0x0
widget =
#5 0x555fe81d in add_rows_to_table (self=self@entry=0x568d22b0,
info=info@entry=0x56450320, list=0x55c82100 = {...},
list@entry=0x55c8bec0 = {...}, type=type@entry=0x556dcac3 "xkb",
default_id=0x0) at ../panels/keyboard/cc-input-chooser.c:723
table = 0x5677 = {[0x5657bb00 "cm+mmuock"] =
0x56ca91a0, [0x56506340 "us+3l"] = 0x56400920, [0x5656f6f0
"ph+capewell-dvorak"] = 0x56cb6f50, [0x5660caf0 "us+dvorak-l"] =
0x56ca9620, [0x5656cd40 "gb+mac_intl"] = 0x56cb6950,
[0x5650de80 "gh+gillbt"] = 0x56cb61d0, [0x56571540 "apl+aplx"] =
0x56ca94a0, [0x565063a0 "us+3l-cros"] = 0x56cb64d0, [0x565062b0
"us+carpalx-full-intl"] = 0x56400aa0, [0x56506070 "us+sun_type6"] =
0x56cb6350, [0x56505f50 "us+drix"] = 0x56ca9320, [0x56506b40
"cm+dvorak"] = 0x56cb6dd0, [0x564faaf0 "us+dvp"] = 0x56cb6650,
[0x564faa80 "us+dvorak-classic"] = 0x564004a0, [0x564fad30
"us+olpc2"] = 0x56400c20, [0x5656f2d0 "ml+us-intl"] = 0x56400620,
[0x564f9c70 "eu"] = 0x56400320, [0x56506310
"us+carpalx-full-altgr-intl"] = 0x564007a0, [0x5656c390 "gb+intl"] =
0x56ca97a0, [0x56506fc0 "ca+eng"] = 0x56cb67d0, [0x565714a0
"apl+aplplusII"] = 0x56400f20, [0x564fafb0 "us+norman"] =
0x56400da0, [0x5660ca90 "us+dvorak-intl"] = 0x56cb6ad0,
[0x56506140 "us+carpalx-intl"] = 0x56cb6c50}
[Desktop-packages] [Bug 1933027] Re: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled
So... GDM actually just launches special session instance that is actually a login screen? Now it's even more weird that gnome-shell doesn't ask for PIN on lock screen. -- 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/1933027 Title: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled Status in gdm3 package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: I use my Ubuntu PC with Yubikey almost always plugged in. It provides several security token interfaces, such as U2F, GPG smartcard, proprieritary Yubico interfaces (of which I mostly use TOTP codes), and also PIV smartcard. However, I haven't configured a PIV smartcard on it. Whenever I login into the system having Yubikey plugged in, I'm prompted for login name, and then for PIN for some smartcard while also being asked to plug in one. This is very misleading on several layers: 1. I have the device providing smartcard plugged id, 2. But it's not the smartcard GDM would think it is as it's not configured properly, 3. There are no local smartcard-authenticating users right now in the system, 3. There are no remote authentication systems configured on the system (so no ActiveDirectory-smartcard logins or such). If I unplug the token UX goes back on old good track. Given the circumstances above, I'd consider that GDM (and, on my bet, any PAM configuration it uses) shouldn't offer to login using smartcard if there is no way to actually do so. I feel something is off here, so I'm reporting a bug. It could be an upstream problem though; it also could be an upstream SSSD problem, or all combined. I believe there is a more clear user experience: 1. GDM should display users that can login into the system, as it always does (if configured). It may also provide entering other login name (also if configured). This is GDM usually does without smartcards altogether. 2. When user is chosen (from the list or manually typed in), check can this user even authenticate with smartcards (i.e. if any of available smartcards is actually recognised for this user). If so, then ask for PIN. Else, don't show anything about smartcards at all (this includes when SSSD is not configured for any AD or related and this user has no local smartcard configuration). This can switch there & back based on device events. I've seen other OS doing this. Ubuntu/Gnome session doesn't ask me for PIN for a smartcard on a lock screen, so I guess it doesn't support it at all or correctly finds out it can't be used. Even more, I couldn't find a way to actually add my smartcard as a local login method. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gdm3 3.38.2.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jun 20 14:02:02 2021 InstallationDate: Installed on 2017-03-05 (1567 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to hirsute on 2021-05-13 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1933027/+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 1931301] Re: NIC unavailable after suspend to RAM
i did a fresh install of 21.04, not an upgrade. the same problem. Doesn't seem to be upgrade related. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1931301 Title: NIC unavailable after suspend to RAM Status in network-manager package in Ubuntu: Confirmed Bug description: Upgraded to 21.04 (hirsute) and now the network card is unavailable after suspend to RAM (sleep state S3). It worked flawlessly up until 20.10. My workaround for now is unloading and reloading the kernel module, but that won't work for normal users, hence this report. NIC in its unavailable state: 2: enp4s0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether d0:50:99:27:02:11 brd ff:ff:ff:ff:ff:ff NIC (from lspci): 04:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 10) Trying to ifconfig it down/up results in: SIOCSIFFLAGS: No such device journalctl shows (right after recovering from suspend): NetworkManager[1911]: [1623181236.9371] manager: sleep: wake requested (sleeping: yes enabled: yes) NetworkManager[1911]: [1623181236.9372] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') NetworkManager[1911]: [1623181236.9382] manager: NetworkManager state is now CONNECTED_LOCAL ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Jun 8 21:59:15 2021 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-25 (1748 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to hirsute on 2021-06-04 (4 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1931301/+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 1931301] Re: NIC unavailable after suspend to RAM
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1931301 Title: NIC unavailable after suspend to RAM Status in network-manager package in Ubuntu: Confirmed Bug description: Upgraded to 21.04 (hirsute) and now the network card is unavailable after suspend to RAM (sleep state S3). It worked flawlessly up until 20.10. My workaround for now is unloading and reloading the kernel module, but that won't work for normal users, hence this report. NIC in its unavailable state: 2: enp4s0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether d0:50:99:27:02:11 brd ff:ff:ff:ff:ff:ff NIC (from lspci): 04:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 10) Trying to ifconfig it down/up results in: SIOCSIFFLAGS: No such device journalctl shows (right after recovering from suspend): NetworkManager[1911]: [1623181236.9371] manager: sleep: wake requested (sleeping: yes enabled: yes) NetworkManager[1911]: [1623181236.9372] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') NetworkManager[1911]: [1623181236.9382] manager: NetworkManager state is now CONNECTED_LOCAL ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Jun 8 21:59:15 2021 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-25 (1748 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to hirsute on 2021-06-04 (4 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1931301/+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 711305]
I hav a question on this case. Why does this "Already running" dialog even exist? In my opinion Thunderbird should all time automatic open the existing application. I do not know any other application with this nonsense Dialogs. What user would be interested in such a detail if the app already run or not. In all cases a normal user inter act with thunderbird I personally know no situation where this error shows a good information. * If the Thunderbird app already run do something in thunderbird. * If thunderbird do not run start it and than do something in tunderbird. * If there is a case that Thunderbird do not react on a call say something like: "Thunderbird do not answer. Should I kill it and start a new one. If you wish check yourself leaf this dialog open. It will disappear the moment thunderbird do answer." -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/711305 Title: Thunderbird is already running, but is not responding. To open a new window, you must first close the existing Thunderbird process, or restart your system. Error received when clicking a mailto link in firefox. Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Binary package hint: thunderbird This thunderbird error is given when clicking a mailto link. Instead of using the thunderbird that's already open it tries to open a new instance. Preferred Applications has Thunderbird select, but I have also tried Custom command "thunderbird %s". This has been tested on 10.04 and 10.10. Both result in this error if thunderbird is already running. Thunderbird is already running, but is not responding. To open a new window, you must first close the existing Thunderbird process, or restart your system. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: thunderbird 3.1.7+build3+nobinonly-0ubuntu0.10.10.1 ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10 Uname: Linux 2.6.35-25-generic i686 Architecture: i386 Date: Tue Feb 1 10:19:09 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) ProcEnviron: LANG=en_CA.utf8 SHELL=/bin/bash SourcePackage: thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/711305/+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 1682542] Re: Add support for top bars on all monitors to allow for multi-monitor support in primary extensions - apps-menu, places-menu, topbar, etc
** Changed in: gnome-shell Importance: Medium => Wishlist -- 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/1682542 Title: Add support for top bars on all monitors to allow for multi-monitor support in primary extensions - apps-menu, places-menu, topbar, etc Status in GNOME Shell: Incomplete Status in gnome-shell package in Ubuntu: Triaged Bug description: This issue will effectively be a regression in desktop usage once Ubuntu switches from Unity to Gnome Shell. Gnome Shell does not work well with multiple monitors unlike every other desktop environment except Budgie, which is switching away from GTK/Gnome to Qt with Budgie 11 due out in the next month or two. I reported it upstream last month but it does not appear to have much traction at the moment. https://bugzilla.gnome.org/show_bug.cgi?id=780078 " It would be nice if the primary included gnome-shell extensions, eg apps-menu and places-menu (and by extension the topbar) supported multi-monitor similar to how the bottom bar 'window-list' currently does. This was easy to achieve on Gnome 2 and now via MATE (out of the box) but there does not appear to be any way to do this with Gnome 3. This also leads to there not being a way to do this via 'Gnome Classic'. Even Windows finally (in W10) does this better out of the box than Gnome 3. BTW - Intel has supported IGP triple head since Ivy Bridge (2012) so it is very cheap to deploy a triple head system (~ $200 for 3 1080p monitors). AMD supports up to quad head in their IGPs. This has been blocking me from moving to Gnome 3 since its release and I finally decided to write a bug report about it. I have had all multi-monitor systems since prior to 2004. " And see comments #11 and #14 from Florian. " No, you don't want that in the extensions. Each extension is separate, so what you are asking for here is that apps-menu and places-menu *both* add top bars to non-primary monitors. We are definitely not going to add two or more stacked panels at the top. What you probably want instead is an option in gnome-shell to put top bars on non-primary monitors, and the aforementioned extensions to handle that case. " " Well, we've established what you want, but that doesn't necessarily mean that we'll implement it. So far the reasoning seems to be: - you really want the feature - GNOME 2 / Windows has it Unlike the case of the window list, nothing in the top bar (except for the app menu to some extent) is tied to a particular monitor, so there's a much weaker case here IMHO. (I'll also note that this wouldn't be a "cheap" option, but require work on lots of details throughout the stack - we'd need to figure out the overview (only include the activities button on the primary monitor? or allow an overview on any monitor?), get API to control the brightness of a particular monitor (rather than the built-in one), don't use "the monitor with the top bar" as indicator for the primary monitor in Settings, ...) " To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1682542/+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 1933022] Re: gnome control-center crashed with sigsegv in g_str_hash() whenever I try to add input sources
Checking upstream it sounds like it could be
https://gitlab.gnome.org/GNOME/gnome-desktop/-/issues/190 fixed by
https://gitlab.gnome.org/GNOME/gnome-desktop/-/commit/aa7e3440 ... would
you know how to rebuild a package with a patch or would you be able to
try a ppa with a candidate fix?
** Package changed: gnome-control-center (Ubuntu) => gnome-desktop3
(Ubuntu)
** Changed in: gnome-desktop3 (Ubuntu)
Importance: Undecided => High
** Changed in: gnome-desktop3 (Ubuntu)
Status: New => Incomplete
--
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/1933022
Title:
gnome control-center crashed with sigsegv in g_str_hash() whenever I
try to add input sources
Status in gnome-desktop3 package in Ubuntu:
Incomplete
Bug description:
I've been facing the problems for about 9 months now. Back then I
thought that maybe getting a new version would solve the problem, but
turns out it didn't. Whenever I try to add some Input Sources from it
just crashes.
Reproducing it is very easy: running gnome-control-center, then going
to Input Sources settings and clicking Add(+) would generate the
crash. But the weird thing is that I've been unable to reproduce it in
VM. And I also tried to reinstall most of the packages which, I think
if changed/misconfigured would cause this but it didn't help. I also
tried to use debsums to give some clues but didn't find any.
After enough digging, this is what I can retrieve from gdb:
#0 g_str_hash (v=0x506) at ../../../glib/ghash.c:2333
p = 0x506
h = 5381
#1 0x77c6e174 in g_hash_table_lookup_node (hash_return=, key=0x506, hash_table=0x563a6180 = {...}) at
../../../glib/ghash.c:472
node_hash =
hash_value =
have_tombstone = 0
step = 0
node_index =
first_tombstone = 0
node_hash =
__func__ = "g_hash_table_lookup_extended"
#2 g_hash_table_lookup_extended (hash_table=0x563a6180 = {...},
lookup_key=lookup_key@entry=0x506, orig_key=orig_key@entry=0x0,
value=value@entry=0x7fffcbb0) at ../../../glib/ghash.c:1548
node_hash =
__func__ = "g_hash_table_lookup_extended"
#3 0x76f03013 in gnome_xkb_info_get_layout_info (self=, id=id@entry=0x506 ,
display_name=display_name@entry=0x7fffcc10,
short_name=short_name@entry=0x0, xkb_layout=xkb_layout@entry=0x0,
xkb_variant=xkb_variant@entry=0x0) at ../libgnome-desktop/gnome-xkb-info.c:1042
priv = 0x56395600
layout = 0x76262ba0
__func__ = "gnome_xkb_info_get_layout_info"
#4 0x555fe467 in input_source_row_new
(self=self@entry=0x568d22b0, type=type@entry=0x556dcac3 "xkb",
id=id@entry=0x506 ) at
../panels/keyboard/cc-input-chooser.c:236
display_name = 0x0
row = 0x0
widget =
#5 0x555fe81d in add_rows_to_table (self=self@entry=0x568d22b0,
info=info@entry=0x56450320, list=0x55c82100 = {...},
list@entry=0x55c8bec0 = {...}, type=type@entry=0x556dcac3 "xkb",
default_id=0x0) at ../panels/keyboard/cc-input-chooser.c:723
table = 0x5677 = {[0x5657bb00 "cm+mmuock"] =
0x56ca91a0, [0x56506340 "us+3l"] = 0x56400920, [0x5656f6f0
"ph+capewell-dvorak"] = 0x56cb6f50, [0x5660caf0 "us+dvorak-l"] =
0x56ca9620, [0x5656cd40 "gb+mac_intl"] = 0x56cb6950,
[0x5650de80 "gh+gillbt"] = 0x56cb61d0, [0x56571540 "apl+aplx"] =
0x56ca94a0, [0x565063a0 "us+3l-cros"] = 0x56cb64d0, [0x565062b0
"us+carpalx-full-intl"] = 0x56400aa0, [0x56506070 "us+sun_type6"] =
0x56cb6350, [0x56505f50 "us+drix"] = 0x56ca9320, [0x56506b40
"cm+dvorak"] = 0x56cb6dd0, [0x564faaf0 "us+dvp"] = 0x56cb6650,
[0x564faa80 "us+dvorak-classic"] = 0x564004a0, [0x564fad30
"us+olpc2"] = 0x56400c20, [0x5656f2d0 "ml+us-intl"] = 0x56400620,
[0x564f9c70 "eu"] = 0x56400320, [0x56506310
"us+carpalx-full-altgr-intl"] = 0x564007a0, [0x5656c390 "gb+intl"] =
0x56ca97a0, [0x56506fc0 "ca+eng"] = 0x56cb67d0, [0x565714a0
"apl+aplplusII"] = 0x56400f20, [0x564fafb0 "us+norman"] =
0x56400da0, [0x5660ca90 "us+dvorak-intl"] = 0x56cb6ad0,
[0x56506140 "us+carpalx-intl"] = 0x56cb6c50}
row =
id = 0x506
#6 0x555ffb78 in get_locale_infos (self=0x568d22b0) at
../panels/keyboard/cc-input-chooser.c:950
country_code = 0x5680eb50 "BW"
simple_locale = 0x5680eb70 "en_BW.UTF-8"
tmp = 0x568acf70 "English (Botswana)"
type = 0x0
language_layouts = 0x55c8bec0
lang_code = 0x5680eb30 "en"
id = 0x0
layouts_with_locale = 0x56772e40
info =
[Desktop-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort
This bug was fixed in the package mesa - 21.1.2-1
---
mesa (21.1.2-1) experimental; urgency=medium
* New upstream release.
* iris-avoid-abort-if-enomem.diff: Don't abort when out of memory.
(LP: #1918855)
-- Timo Aaltonen Fri, 18 Jun 2021 14:33:09 +0300
** Changed in: mesa (Ubuntu)
Status: New => Fix Released
--
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/1918855
Title:
Xorg xserver got signal 6 to abort
Status in Mesa:
Unknown
Status in OEM Priority Project:
In Progress
Status in Provider for Plainbox - Checkbox:
New
Status in mesa package in Ubuntu:
Fix Released
Bug description:
== SRU Justification ==
[Impact]
When the system is under memory pressure, the entire desktop session may
crash.
[Fix]
Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if
kernel can't allocate memory")
[Test]
Run memory stress and the session crashed in less than 5 minutes.
With the fix applied, run memory stress for 24 hours and the desktop session
is still alive.
[Where problems could occur]
Doing a reset might make the system even more sluggish when under memory
pressure.
== Original bug report ==
I run checkbox job com.canonical.certification::memory/memory_stress_ng on
focal, and the xserver stops unexpectedly with the following stacktrace:
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg
(OsLookupColor+0x13c) [0x5619f3a4d59c]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 1:
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6
(gsignal+0xcb) [0x7fae476a418b]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6
(abort+0x12b) [0x7fae47683859]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind
info found [-10]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 4:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 5:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec)
[0x7fae46529c9c]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 6:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 7:
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150)
[0x7fae47007480]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind
info found [-10]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 8:
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg
(BlockHandler+0xa5) [0x5619f38f0995]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg
(WaitForSomething+0x122) [0x5619f3a46c12]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg
(SendErrorToClient+0x117) [0x5619f38ebcf7]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg
(InitFonts+0x3b4) [0x5619f38effc4]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6
(__libc_start_main+0xf3) [0x7fae476850b3]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e)
[0x5619f38d9a2e]
More info:
I searched the Internet and got a bug with the same stacktrace:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859
To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1918855/+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 1933022] Re: gnome control-center crashed with sigsegv in g_str_hash() whenever I try to add input sources
There was a mention of a segfault following the fix from bug #1925792 ,
sounds like that could be a gnome-desktop issue
** Bug watch added: gitlab.gnome.org/GNOME/gnome-desktop/-/issues #190
https://gitlab.gnome.org/GNOME/gnome-desktop/-/issues/190
--
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/1933022
Title:
gnome control-center crashed with sigsegv in g_str_hash() whenever I
try to add input sources
Status in gnome-desktop3 package in Ubuntu:
Incomplete
Bug description:
I've been facing the problems for about 9 months now. Back then I
thought that maybe getting a new version would solve the problem, but
turns out it didn't. Whenever I try to add some Input Sources from it
just crashes.
Reproducing it is very easy: running gnome-control-center, then going
to Input Sources settings and clicking Add(+) would generate the
crash. But the weird thing is that I've been unable to reproduce it in
VM. And I also tried to reinstall most of the packages which, I think
if changed/misconfigured would cause this but it didn't help. I also
tried to use debsums to give some clues but didn't find any.
After enough digging, this is what I can retrieve from gdb:
#0 g_str_hash (v=0x506) at ../../../glib/ghash.c:2333
p = 0x506
h = 5381
#1 0x77c6e174 in g_hash_table_lookup_node (hash_return=, key=0x506, hash_table=0x563a6180 = {...}) at
../../../glib/ghash.c:472
node_hash =
hash_value =
have_tombstone = 0
step = 0
node_index =
first_tombstone = 0
node_hash =
__func__ = "g_hash_table_lookup_extended"
#2 g_hash_table_lookup_extended (hash_table=0x563a6180 = {...},
lookup_key=lookup_key@entry=0x506, orig_key=orig_key@entry=0x0,
value=value@entry=0x7fffcbb0) at ../../../glib/ghash.c:1548
node_hash =
__func__ = "g_hash_table_lookup_extended"
#3 0x76f03013 in gnome_xkb_info_get_layout_info (self=, id=id@entry=0x506 ,
display_name=display_name@entry=0x7fffcc10,
short_name=short_name@entry=0x0, xkb_layout=xkb_layout@entry=0x0,
xkb_variant=xkb_variant@entry=0x0) at ../libgnome-desktop/gnome-xkb-info.c:1042
priv = 0x56395600
layout = 0x76262ba0
__func__ = "gnome_xkb_info_get_layout_info"
#4 0x555fe467 in input_source_row_new
(self=self@entry=0x568d22b0, type=type@entry=0x556dcac3 "xkb",
id=id@entry=0x506 ) at
../panels/keyboard/cc-input-chooser.c:236
display_name = 0x0
row = 0x0
widget =
#5 0x555fe81d in add_rows_to_table (self=self@entry=0x568d22b0,
info=info@entry=0x56450320, list=0x55c82100 = {...},
list@entry=0x55c8bec0 = {...}, type=type@entry=0x556dcac3 "xkb",
default_id=0x0) at ../panels/keyboard/cc-input-chooser.c:723
table = 0x5677 = {[0x5657bb00 "cm+mmuock"] =
0x56ca91a0, [0x56506340 "us+3l"] = 0x56400920, [0x5656f6f0
"ph+capewell-dvorak"] = 0x56cb6f50, [0x5660caf0 "us+dvorak-l"] =
0x56ca9620, [0x5656cd40 "gb+mac_intl"] = 0x56cb6950,
[0x5650de80 "gh+gillbt"] = 0x56cb61d0, [0x56571540 "apl+aplx"] =
0x56ca94a0, [0x565063a0 "us+3l-cros"] = 0x56cb64d0, [0x565062b0
"us+carpalx-full-intl"] = 0x56400aa0, [0x56506070 "us+sun_type6"] =
0x56cb6350, [0x56505f50 "us+drix"] = 0x56ca9320, [0x56506b40
"cm+dvorak"] = 0x56cb6dd0, [0x564faaf0 "us+dvp"] = 0x56cb6650,
[0x564faa80 "us+dvorak-classic"] = 0x564004a0, [0x564fad30
"us+olpc2"] = 0x56400c20, [0x5656f2d0 "ml+us-intl"] = 0x56400620,
[0x564f9c70 "eu"] = 0x56400320, [0x56506310
"us+carpalx-full-altgr-intl"] = 0x564007a0, [0x5656c390 "gb+intl"] =
0x56ca97a0, [0x56506fc0 "ca+eng"] = 0x56cb67d0, [0x565714a0
"apl+aplplusII"] = 0x56400f20, [0x564fafb0 "us+norman"] =
0x56400da0, [0x5660ca90 "us+dvorak-intl"] = 0x56cb6ad0,
[0x56506140 "us+carpalx-intl"] = 0x56cb6c50}
row =
id = 0x506
#6 0x555ffb78 in get_locale_infos (self=0x568d22b0) at
../panels/keyboard/cc-input-chooser.c:950
country_code = 0x5680eb50 "BW"
simple_locale = 0x5680eb70 "en_BW.UTF-8"
tmp = 0x568acf70 "English (Botswana)"
type = 0x0
language_layouts = 0x55c8bec0
lang_code = 0x5680eb30 "en"
id = 0x0
layouts_with_locale = 0x56772e40
info = 0x56450320
locale = 0x5680e950
all_layouts = 0x0
locale_ids = 0x5680e950
l =
self = 0x568d22b0
error = 0x0
#7 cc_input_chooser_new (is_login=, xkb_info=,
ibus_engines=) at
[Desktop-packages] [Bug 1932066] Re: PulseAudio Preferences searches for libraries in incorrect location
*** This bug is a duplicate of bug 1907882 ***
https://bugs.launchpad.net/bugs/1907882
** This bug has been marked a duplicate of bug 1907882
paprefs does not find modules
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1932066
Title:
PulseAudio Preferences searches for libraries in incorrect location
Status in pulseaudio package in Ubuntu:
New
Bug description:
PulseAudio Preferences (paprefs) appears to be searching for modules
in the wrong location.
Specifically, the "install" button appears when modules relevant
modules cannot be found by paprefs.
paprefs is searching for modules in the location:
/usr/lib/pulse-13.99/modules/
the modules are actually located in: /usr/lib/pulse-13.99.1/modules/
The specifics of this were determined via `strace paprefs`, which
(among a lot of other things), produces:
access("/usr/lib/pulse-13.99/modules/module-esound-protocol-tcp.so", F_OK) =
-1 ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-native-protocol-tcp.so", F_OK) =
-1 ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-zeroconf-publish.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-zeroconf-discover.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-raop-discover.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-rtp-recv.so", F_OK) = -1 ENOENT
(No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-rtp-send.so", F_OK) = -1 ENOENT
(No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-rygel-media-server.so", F_OK) =
-1 ENOENT (No such file or directory)
creating a symlink from /usr/lib/pulse-13.99.1 to /usr/lib/pulse-13.99
resolves the issue.
paprefs should perhaps be updated to match the version of the
pulseaudio package.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1932066/+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 1933118] [NEW] Xorg freeze
Public bug reported: This bug appears to be a deadlock of some kind. It most often happens when I move the mouse (external USB mouse), but it has once happened when I left the computer logged in but idle and has sometimes happened in video conferences. When the problem occurs, the mouse cursor still moves and any audio continues being audible for a while, but the UI is frozen and unresponsive. The fan gets very loud as if the computer is doing a lot of work. If I try the 'REISUB' method of shutting down, it usually does not work. If I remote log in and do a shutdown, it takes several minutes to actually shut down - as if waiting for some process to time out. I haven't any obvious errors for this bug, and i don't know where to look for possible error messages. It is possible that if there is a deadlock, there is no error message, unless shutting down causes the process to generate an error message. The bug happens very often, sometimes several times a week. If you could tell me what commands to run when the problem occurs in order to gather more information, I can remote login and run those commands. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.143 Fri Mar 12 07:24:47 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 21 15:14:30 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.3, 5.8.0-53-generic, x86_64: installed v4l2loopback, 0.12.3, 5.8.0-55-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since before I upgraded GraphicsCard: NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GK107GLM [Quadro K1100M] [103c:2256] InstallationDate: Installed on 2021-01-11 (161 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP ZBook 17 G2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=62a0870e-1f83-43a4-a2ff-864901a24fb6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2015 dmi.bios.release: 1.12 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M70 Ver. 01.12 dmi.board.name: 2255 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 03.10 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 3.16 dmi.modalias: dmi:bvnHewlett-Packard:bvrM70Ver.01.12:bd09/23/2015:br1.12:efr3.16:svnHewlett-Packard:pnHPZBook17G2:pvrA3009DD10203:rvnHewlett-Packard:rn2255:rvrKBCVersion03.10:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP ZBook 17 G2 dmi.product.sku: G6Z41AV dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze possible-manual-nvidia-install third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1933118 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: This bug appears to be a deadlock of some kind. It most often happens when I move the mouse (external USB mouse), but it has once happened when I left the computer logged in but idle and has sometimes happened in video conferences. When the problem occurs, the mouse cursor still moves and any audio continues being audible for a while, but the UI is frozen and unresponsive. The fan gets very loud as if the computer is doing a lot
[Desktop-packages] [Bug 1923845] Re: Please compress packages with zstd by default
This bug was fixed in the package hello - 2.10-2ubuntu3
---
hello (2.10-2ubuntu3) impish; urgency=medium
* Ubuntu Impish will be switching default dpkg compression format to
Zstd. This upload is the first canary to signal the archive format
change. dpkg in Ubuntu supports zstd in xenial and up. If any issues
are identified with this package, please report them at
https://pad.lv/1923845 LP: #1923845
-- Dimitri John Ledkov Fri, 18 Jun 2021 11:58:54
+0100
** Changed in: hello (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream-glib in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
Fix Released
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
Fix Released
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
New
Status in dpkg package in Ubuntu:
New
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in hello package in Ubuntu:
Fix Released
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
Fix Released
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
New
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz=1=1
https://codesearch.debian.net/search?q=control.tar.xz=1=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
libsolv - needs fix, ext/repo_deb.c
lintian - needs fix malformed-deb-archive
lutris - needs fix, lutris/util/extract.py
obs-build - needs fix Build/Deb.pm
osc - needs fix osc/util/debquery.py control.tar.zst only
python-apt - needs fix
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
radare2 - needs fix
reprepro- needs fix, debfile.c
vim-scripts - needs fix debPlugin/autoload/deb.vim
winetricks - needs fix when Debian switches src/winetricks
zeroinstall-injector - needs fix src/zeroinstall/archive.ml
acr - skip, does not _have to_ be fixed, just creates packages,
see dist/deb_hand.mak
alien - skip, uses dpkg-deb to extract .deb
ansible - not affected, just test data in dbdata.tar.xz
anthy - not affected, just changelog entry
apt - seems fixed already
ceph- not affected in Ubuntu's version
circlator - not affected, just test data
cowdancer
[Desktop-packages] [Bug 1931701] Re: autopkgtests failures on armhf of 7.1.4
Using a three year old compiler is not a fix, but a work around. Please start investigating this properly. https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/1891623/comments/8 suggests to do a proper debug build at least. This was filed ten months ago ... ** Changed in: libreoffice (Ubuntu Impish) Status: Fix Released => New ** Tags added: rls-ii-incoming -- 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/1931701 Title: autopkgtests failures on armhf of 7.1.4 Status in gcc-9 package in Ubuntu: New Status in libreoffice package in Ubuntu: New Status in gcc-9 source package in Hirsute: New Status in libreoffice source package in Hirsute: New Status in gcc-9 source package in Impish: New Status in libreoffice source package in Impish: New Bug description: The autopkgtests for 7.1.4~rc2-0ubuntu1 on impish/armhf has started to fail reliably. https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/armhf/libr/libreoffice/20210610_121847_0ab56@/log.gz "/usr/lib/libreoffice/program/unopkg" add -f "/tmp/tmp.oOlP0i1pzN/out/sdk/LINUXexample.out/bin/SampleDialog.oxt" # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0xf47474b8, pid=35616, tid=35643 # # JRE version: OpenJDK Runtime Environment (11.0.12+4) (build 11.0.12-ea+4-Ubuntu-0ubuntu2) # Java VM: OpenJDK Server VM (11.0.12-ea+4-Ubuntu-0ubuntu2, mixed mode, g1 gc, linux-) # Problematic frame: # C [libbootstraplo.so+0x1c4b8] stoc_impreg::mergeKeys(com::sun::star::uno::Reference const&, com::sun::star::uno::Reference const&, std::vector >&)+0xb # # Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport %p %s %c %d %P %E" (or dumping to /usr/lib/libreoffice/sdk/examples/DevelopersGuide/BasicAndDialogs/CreatingDialogs/core.35616) # # An error report file with more information is saved as: # /tmp/hs_err_pid35616.log # # If you would like to submit a bug report, please visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-lts # ERROR: Exception occurred: Binary URP bridge disposed during call ./binaryurp/source/bridge.cxx:613 ERROR: unopkg failed. make[1]: Leaving directory '/usr/lib/libreoffice/sdk/examples/DevelopersGuide/BasicAndDialogs/CreatingDialogs' make[1]: *** [Makefile:112: /tmp/tmp.oOlP0i1pzN/out/sdk/LINUXexample.out/misc/devguide_basicanddialogs_creatingdialogs_register_component.flag] Error 1 make[1]: Target 'ALL' not remade because of errors. make: *** [/tmp/autopkgtest.U74TIg/build.myd/src/odk/CustomTarget_build-examples_java.mk:62: /tmp/autopkgtest.U74TIg/build.myd/src/workdir/CustomTarget/odk/build-examples_java.done] Error 2 make: Target 'CustomTarget_odk/build-examples_java' not remade because of errors. While a re-run of the test for 7.1.3-0ubuntu1 were successful it suggests it is binary problem. https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/armhf/libr/libreoffice/20210609_234830_1265b@/log.gz liberoffice is built with gcc-9/g++-9 on armhf to avoid https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/1891623 A significant difference in the used toolchain points to the update of gcc-9 7.1.3-0ubuntu1 was built with gcc 9.3.0-24ubuntu1 https://launchpadlibrarian.net/537628130/buildlog_ubuntu-impish-armhf.libreoffice_1%3A7.1.3-0ubuntu1_BUILDING.txt.gz 7.1.4~rc2-0ubuntu1 was built with gcc 9.4.0-1ubuntu1 https://launchpadlibrarian.net/542492348/buildlog_ubuntu-impish-armhf.libreoffice_1%3A7.1.4~rc2-0ubuntu1_BUILDING.txt.gz Regarding 21.04/Hirsute 1:7.1.4~rc2-0ubuntu0.21.04.1~lo1 built and successfully ran autopkgtests, see https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1931272 If was using the gcc-9 9.3.0-23ubuntu2 available at the time. The no-change rebuild against 9.4.0-1ubuntu1~21.04 results in the same failure now. https://launchpadlibrarian.net/543392061/buildlog_ubuntu-hirsute-armhf.libreoffice_1%3A7.1.4~rc2-0ubuntu0.21.04.1~lo1_BUILDING.txt.gz https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-experimental/hirsute/armhf/libr/libreoffice/20210612_113218_f7f69@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1931701/+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 1925742] Re: Recent iCloud versions trigger an issue in IMAP x
Thank you Brian for following up on this! Is there any news regarding the fix in Hirsute yet? Two months of not being able to access iCloud mails in a core component of the current supported Ubuntu release is a really long time ... :( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1925742 Title: Recent iCloud versions trigger an issue in IMAP x Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Focal: Fix Released Status in evolution-data-server source package in Hirsute: Triaged Bug description: * Impact The Icloud service introduced changes that are confusing evolution- data-server which means evolution is now failing to connect to the email server * Test case Set up an iCloud account and try to use it for emails in evolution * Regression potential The change is in the imapx connection code, it could create problems with other type of servers so we should try to test on different providers. - The bug has been fixed yesterday by Evolution's developer: https://gitlab.gnome.org/GNOME/evolution/-/issues/1468 However, the package in Ubuntu (at least in Focal Fosa) still needs to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+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 1933085] Re: nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
I was informed by Alberto Milone that the 340 driver was discontinued and won't get updates to support the 5.11 kernels. ** Changed in: linux-hwe-5.11 (Ubuntu) Status: New => Invalid ** Changed in: linux-hwe-5.11 (Ubuntu Focal) Status: New => Invalid ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Won't Fix ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Focal) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1933085 Title: nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in linux-hwe-5.11 source package in Focal: Invalid Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Bug description: This is a scripted bug report about ADT failures while running nvidia- graphics-drivers-340 tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/n/nvidia-graphics-drivers-340/20210611_210127_38d90@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1933085/+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 1933085] Re: nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
** Attachment added: "make.log" https://bugs.launchpad.net/bugs/1933085/+attachment/5505995/+files/make.log ** Also affects: nvidia-graphics-drivers-340 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-hwe-5.11 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1933085 Title: nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in linux-hwe-5.11 source package in Focal: Invalid Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Bug description: This is a scripted bug report about ADT failures while running nvidia- graphics-drivers-340 tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/n/nvidia-graphics-drivers-340/20210611_210127_38d90@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1933085/+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 1933085] [NEW] nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
Public bug reported: This is a scripted bug report about ADT failures while running nvidia- graphics-drivers-340 tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/n/nvidia-graphics-drivers-340/20210611_210127_38d90@/log.gz ** Affects: linux-hwe-5.11 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: Won't Fix ** Affects: linux-hwe-5.11 (Ubuntu Focal) Importance: Undecided Status: Invalid ** Affects: nvidia-graphics-drivers-340 (Ubuntu Focal) Importance: Undecided Status: Won't Fix ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1933085 Title: nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in linux-hwe-5.11 source package in Focal: Invalid Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Bug description: This is a scripted bug report about ADT failures while running nvidia- graphics-drivers-340 tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/n/nvidia-graphics-drivers-340/20210611_210127_38d90@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1933085/+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 1930700] Re: Firefox 89 won't load pages due to many fonts
Launchpad has imported 13 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1694174. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2021-02-22T15:49:49+00:00 Jfkthame wrote: Currently gfx.e10s.font-list.shared is enabled by default on Nightly/early Beta, but disabled for release. To reduce content-process memory footprint and startup time, we should get this enabled all the way to the Release channel. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1930700/comments/0 On 2021-02-24T20:29:38+00:00 Cpeterson-3 wrote: How much memory does the shared font-list save per content process? Since Fission will have launch many more content processes than e10s, the shared font-list might be nice to have for Fission MVP. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1930700/comments/1 On 2021-03-01T20:08:21+00:00 Cpeterson-3 wrote: @ Jonathan, SearchAllFontsForChar crash bug 1667977 and src:local() bug 1694123 are blocking this bug. I see you already have a patch up to fix bug 1694123. Does bug 1667977 also need to be fixed before we can let the shared font-list ride the trains to late Beta and Release? Fission's current perf measurements are all from Nightly, so already include any perf and memory benefits from the shared font-list. Tracking for Fission M7 Beta milestone because we'd like to have the shared font- list in late Beta and when we ship to Release. kmag estimates the shared font-list might save about 500 KB in each content process. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1930700/comments/2 On 2021-03-02T09:13:58+00:00 Jfkthame wrote: Bug 1667977 currently means that on Windows there's a possibility of content processes crashing if the user installs/removes a bunch of fonts while the browser is running (so we get a flurry of notifications that trigger repeated, overlapping updates to our font list). This is probably not a common situation -- most users aren't installing and removing fonts frequently in the midst of a browser session -- but still, I'd be reluctant to ship something that is known to be crashy in such a scenario. So I'd definitely prefer to have bug 1667977 fixed before it rides to Release. I've been attempting to debug but it's proving difficult to track down the root cause at the moment. (Not having a tool equivalent to rr or pernosco on Windows hurts...) I'll try to spend some more time digging into it this week. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1930700/comments/3 On 2021-03-10T18:28:55+00:00 Cpeterson-3 wrote: (In reply to Jonathan Kew (:jfkthame) from comment #3) > So I'd definitely prefer to have bug 1667977 fixed before it rides to > Release. I've been attempting to debug but it's proving difficult to track > down the root cause at the moment. (Not having a tool equivalent to rr or > pernosco on Windows hurts...) I'll try to spend some more time digging into > it this week. A fix for SearchAllFontsForChar crash bug 1667977 probably won't be ready for 88 Beta, so I will move this bug from Fission milestone M7 to M8. btw, the reporter of bug 1667977 says the crash is also reproducible on Linux, so you may be able to catch the crash in rr on Linux. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1930700/comments/4 On 2021-04-10T11:18:58+00:00 Jfkthame wrote: This has been enabled on Nightly since 82, and also early Beta since 83. Now that a fix for bug 1667977 has landed, I think we should remove the early-beta condition and let this go all the way to release. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1930700/comments/5 On 2021-04-10T11:20:16+00:00 Jfkthame wrote: Created attachment 9214874 Bug 1694174 - Pref-on the shared font-list by default for all channels. r=#layout-reviewers Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1930700/comments/6 On 2021-04-10T22:06:18+00:00 Pulsebot wrote: Pushed by j...@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/622e8fe7e539 Pref-on the shared font-list by default for all channels. r=emilio Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1930700/comments/7
[Desktop-packages] [Bug 1923845] Re: Please compress packages with zstd by default
** Tags removed: block-proposed-impish
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream-glib in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
Fix Released
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
Fix Released
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
New
Status in dpkg package in Ubuntu:
New
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in hello package in Ubuntu:
New
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
Fix Released
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
New
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz=1=1
https://codesearch.debian.net/search?q=control.tar.xz=1=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
libsolv - needs fix, ext/repo_deb.c
lintian - needs fix malformed-deb-archive
lutris - needs fix, lutris/util/extract.py
obs-build - needs fix Build/Deb.pm
osc - needs fix osc/util/debquery.py control.tar.zst only
python-apt - needs fix
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
radare2 - needs fix
reprepro- needs fix, debfile.c
vim-scripts - needs fix debPlugin/autoload/deb.vim
winetricks - needs fix when Debian switches src/winetricks
zeroinstall-injector - needs fix src/zeroinstall/archive.ml
acr - skip, does not _have to_ be fixed, just creates packages,
see dist/deb_hand.mak
alien - skip, uses dpkg-deb to extract .deb
ansible - not affected, just test data in dbdata.tar.xz
anthy - not affected, just changelog entry
apt - seems fixed already
ceph- not affected in Ubuntu's version
circlator - not affected, just test data
cowdancer - not affected, just documentation
eccodes - skip, just orig-data.tar.xz
eckit - skip, just ...orig-data.tar.xz
firefox - skip, profdata.tar.xz
firefox-esr - skip, profdata.tar.xz
galculator - skip, just changelog
grads - skip, ...orig-data.tar.xz
gvmd- skip, just creates xz compressed .deb
insighttoolkit4 - skip, ...orig-data.tar.xz
jdeb- skip, just creates compressed .deb packages
jmol- skip, just local data archive
jq
[Desktop-packages] [Bug 1933080] [NEW] package bluez 5.53-0ubuntu3.2 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1
Public bug reported: . ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.2 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: bluez:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jun 21 11:08:56 2021 ErrorMessage: installed bluez package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-03-11 (101 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 004: ID 27c6:5385 Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=05af585d-21ef-4aab-a647-bf6f798a1ee1 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: bluez Title: package bluez 5.53-0ubuntu3.2 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2021 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.3 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.3:bd03/17/2021:br1.14:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: 9C:B6:D0:8D:7C:B4 ACL MTU: 1024:8 SCO MTU: 50:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:28400076 acl:327 sco:0 events:3488107 errors:0 TX bytes:2059958316 acl:3291744 sco:0 commands:27448 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933080 Title: package bluez 5.53-0ubuntu3.2 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 Status in bluez package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.2 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: bluez:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jun 21 11:08:56 2021 ErrorMessage: installed bluez package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-03-11 (101 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 004: ID 27c6:5385 Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=05af585d-21ef-4aab-a647-bf6f798a1ee1 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: bluez Title: package bluez 5.53-0ubuntu3.2 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2021 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.3 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.3:bd03/17/2021:br1.14:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc.
[Desktop-packages] [Bug 1933078] [NEW] BlueZ 5.59 release
Public bug reported: Release BlueZ 5.59 to impish. ** Affects: bluez (Ubuntu) Importance: Wishlist Assignee: Daniel van Vugt (vanvugt) Status: In Progress ** Tags: impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933078 Title: BlueZ 5.59 release Status in bluez package in Ubuntu: In Progress Bug description: Release BlueZ 5.59 to impish. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933078/+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 1916827] Re: Update libgweather to v40
** Changed in: libgweather (Ubuntu) Status: New => Fix Committed ** Changed in: libgweather (Ubuntu) Importance: Undecided => High ** Changed in: libgweather (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1916827 Title: Update libgweather to v40 Status in libgweather package in Ubuntu: Fix Committed Bug description: Without the latest gweather v40, gnome-shell 40 fails to start: (gnome-shell:14525): Gjs-CRITICAL **: 14:24:49.987: JS ERROR: Error: No property application_id on GWeatherInfo WeatherClient@resource:///org/gnome/shell/misc/weather.js:75:29 _init@resource:///org/gnome/shell/ui/dateMenu.js:478:31 _init@resource:///org/gnome/shell/ui/dateMenu.js:872:29 _ensureIndicator@resource:///org/gnome/shell/ui/panel.js:1012:25 _updateBox@resource:///org/gnome/shell/ui/panel.js:1023:34 _updatePanel@resource:///org/gnome/shell/ui/panel.js:968:14 _init@resource:///org/gnome/shell/ui/panel.js:778:14 _initializeUI@resource:///org/gnome/shell/ui/main.js:228:13 start@resource:///org/gnome/shell/ui/main.js:169:5 @:1:47 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/1916827/+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 1919134] Re: Please package gsettings-desktop-schemas >= 40.alpha
** Changed in: gsettings-desktop-schemas (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1919134 Title: Please package gsettings-desktop-schemas >= 40.alpha Status in gsettings-desktop-schemas package in Ubuntu: Fix Released Bug description: Please package gsettings-desktop-schemas >= 40.alpha as it is required to build mutter 40. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1919134/+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 1532264] Re: fprintd allows unauthorized root access
This bug was fixed in the package fprintd - 1.90.9-1~ubuntu20.04.1
---
fprintd (1.90.9-1~ubuntu20.04.1) focal; urgency=medium
* Backport to focal (LP: #1908119)
fprintd (1.90.9-1) unstable; urgency=medium
[ Marco Trevisan (Treviño) ]
* New upstream release:
- Fix multiple daemon lockup issues (#97)
- Fix print garbage collection to not delete used prints
- pam: Use the device with the most prints
* debian/control: Mark fprintd-doc as Multi-Arch: foreign
[ Helmut Grohne ]
* Fix nocheck FTFBS: Drop from non-optional dependencies.
(Closes: #977395)
fprintd (1.90.8-1~ubuntu20.04.1) focal; urgency=medium
* Backport to focal (LP: #1908119)
* debian/{control,gbp.conf}: Prepare for ubuntu focal branching
* debian/{control, rules}: Do not use debhelper 13 features
* debian/rules: Use meson test directly to handle timeouts
* debian/patches: Drop all the patches applied upstream
fprintd (1.90.8-1) unstable; urgency=medium
* New upstream release
- pam: Only listen to NameOwnerChanged after fprintd is known to run
- Place new ObjectManager DBus API at /net/reactivated/Fprint
* debian/patches: Remove all patches, applied upstream or not needed anymore
* debian/control: Depend on systemd 235, but only in linux
* debian/rules: Require systemd and set unit path only on linux
* debian/fprintd.install: Use dh-exec to filter linux-only files
fprintd (1.90.7-1) unstable; urgency=medium
* New upstream release
- Fix fprintd DBus configuration (Closes: #976990)
- Change details of what requires authorization
- Fix various race conditions in pam_fprintd
- Permit interactive authorization from fprintd utilities
- Do not allow deletion while another operation is ongoing
- pam: Guard strdup calls against NULL pointers
* debian/patches:
- Refresh
- Ignore NameOwnerChanged until fprintd is running
fprintd (1.90.5-2) unstable; urgency=medium
* debian/patches: Make tests run with actual required libfprint version
* debian/control: Remove test-only dependency on libfprint 1.90.4.
Tests are now working with older libfprint versions too
* debian/control: Add myself to Uploaders
* debian/gbp.conf: Include suggested settings by GNOME team.
Even if fprintd is not part of GNOME I think these settings are good
practice anyways.
fprintd (1.90.5-1) unstable; urgency=medium
* New upstream release:
- Permit building with polkit older than 0.114
- Fix possible issues with PAM test
- Fix incorrect DBus policy
- Fix build so that CFLAGS environment is correctly used
- Skip hotplug test with older libfprint (which times out otherwise)
* debian/patches: Drop patches applied upstream
fprintd (1.90.4-1) unstable; urgency=medium
* Team upload.
[ Marco Trevisan (Treviño) ]
* New upstream release:
- Use GDBus and async Polkit checks
- Authentication is now required to enroll a new print (LP: #1532264,
Closes: #719004)
- Add support for the libfprint early reporting mechanism
- Proper hotplug support together with libfprint 1.90.4
- Handle STATE_DIRECTORY containing multiple paths
- Various memory fixes (LP: #1888495)
* debian/control:
- Remove build dependency on dbus-glib (Closes: #955893)
- Mark as the packages required only for testing
- Use debhelper 13
- Bump libfprint-2 dependency on 1.90.4 on test case
* debian/rules:
- remove unneeded override to force --fail-missing (as per dh 13)
- Increase tests timeout multiplier
* debian/patches:
- Refresh
- Define auto-pointers functions if not defined:
Fixes a build failure with debian polkit version.
- Cleanup pam-wrapper temporary dir when running tests
- Fix dbus-policy file to address lintian
- Ensure we generate debug symbols in debian builds
[ Laurent Bigonville ]
* debian/control: Bump Standards-Version to 4.5.1 (no further changes)
fprintd (1.90.1-2) unstable; urgency=low
* Team upload.
* Simplify the installation of the pam-config, do not install one
configuration file per architecture
* debian/NEWS: Add an news entry explaining that the user will have to
re-enroll their fingerprints upon update to 1.90.1.
-- Marco Trevisan (Treviño) Mon, 22 Feb 2021
16:00:47 +0100
** Changed in: fprintd (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fprintd in Ubuntu.
https://bugs.launchpad.net/bugs/1532264
Title:
fprintd allows unauthorized root access
Status in fprintd:
Invalid
Status in fprintd package in Ubuntu:
Fix Released
Status in fprintd source package in Focal:
Fix Released
Status in fprintd source package in Groovy:
Fix Committed
Bug description:
For some reason, fprintd-enroll does not require any special authorization to
run.
This means that anyone coming across or stealing a
[Desktop-packages] [Bug 1888495] Re: fprintd-verify fails with an USB UPEK reader
This bug was fixed in the package fprintd - 1.90.9-1~ubuntu20.04.1
---
fprintd (1.90.9-1~ubuntu20.04.1) focal; urgency=medium
* Backport to focal (LP: #1908119)
fprintd (1.90.9-1) unstable; urgency=medium
[ Marco Trevisan (Treviño) ]
* New upstream release:
- Fix multiple daemon lockup issues (#97)
- Fix print garbage collection to not delete used prints
- pam: Use the device with the most prints
* debian/control: Mark fprintd-doc as Multi-Arch: foreign
[ Helmut Grohne ]
* Fix nocheck FTFBS: Drop from non-optional dependencies.
(Closes: #977395)
fprintd (1.90.8-1~ubuntu20.04.1) focal; urgency=medium
* Backport to focal (LP: #1908119)
* debian/{control,gbp.conf}: Prepare for ubuntu focal branching
* debian/{control, rules}: Do not use debhelper 13 features
* debian/rules: Use meson test directly to handle timeouts
* debian/patches: Drop all the patches applied upstream
fprintd (1.90.8-1) unstable; urgency=medium
* New upstream release
- pam: Only listen to NameOwnerChanged after fprintd is known to run
- Place new ObjectManager DBus API at /net/reactivated/Fprint
* debian/patches: Remove all patches, applied upstream or not needed anymore
* debian/control: Depend on systemd 235, but only in linux
* debian/rules: Require systemd and set unit path only on linux
* debian/fprintd.install: Use dh-exec to filter linux-only files
fprintd (1.90.7-1) unstable; urgency=medium
* New upstream release
- Fix fprintd DBus configuration (Closes: #976990)
- Change details of what requires authorization
- Fix various race conditions in pam_fprintd
- Permit interactive authorization from fprintd utilities
- Do not allow deletion while another operation is ongoing
- pam: Guard strdup calls against NULL pointers
* debian/patches:
- Refresh
- Ignore NameOwnerChanged until fprintd is running
fprintd (1.90.5-2) unstable; urgency=medium
* debian/patches: Make tests run with actual required libfprint version
* debian/control: Remove test-only dependency on libfprint 1.90.4.
Tests are now working with older libfprint versions too
* debian/control: Add myself to Uploaders
* debian/gbp.conf: Include suggested settings by GNOME team.
Even if fprintd is not part of GNOME I think these settings are good
practice anyways.
fprintd (1.90.5-1) unstable; urgency=medium
* New upstream release:
- Permit building with polkit older than 0.114
- Fix possible issues with PAM test
- Fix incorrect DBus policy
- Fix build so that CFLAGS environment is correctly used
- Skip hotplug test with older libfprint (which times out otherwise)
* debian/patches: Drop patches applied upstream
fprintd (1.90.4-1) unstable; urgency=medium
* Team upload.
[ Marco Trevisan (Treviño) ]
* New upstream release:
- Use GDBus and async Polkit checks
- Authentication is now required to enroll a new print (LP: #1532264,
Closes: #719004)
- Add support for the libfprint early reporting mechanism
- Proper hotplug support together with libfprint 1.90.4
- Handle STATE_DIRECTORY containing multiple paths
- Various memory fixes (LP: #1888495)
* debian/control:
- Remove build dependency on dbus-glib (Closes: #955893)
- Mark as the packages required only for testing
- Use debhelper 13
- Bump libfprint-2 dependency on 1.90.4 on test case
* debian/rules:
- remove unneeded override to force --fail-missing (as per dh 13)
- Increase tests timeout multiplier
* debian/patches:
- Refresh
- Define auto-pointers functions if not defined:
Fixes a build failure with debian polkit version.
- Cleanup pam-wrapper temporary dir when running tests
- Fix dbus-policy file to address lintian
- Ensure we generate debug symbols in debian builds
[ Laurent Bigonville ]
* debian/control: Bump Standards-Version to 4.5.1 (no further changes)
fprintd (1.90.1-2) unstable; urgency=low
* Team upload.
* Simplify the installation of the pam-config, do not install one
configuration file per architecture
* debian/NEWS: Add an news entry explaining that the user will have to
re-enroll their fingerprints upon update to 1.90.1.
-- Marco Trevisan (Treviño) Mon, 22 Feb 2021
16:00:47 +0100
** Changed in: fprintd (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fprintd in Ubuntu.
https://bugs.launchpad.net/bugs/1888495
Title:
fprintd-verify fails with an USB UPEK reader
Status in fprintd package in Ubuntu:
Fix Released
Status in libfprint package in Ubuntu:
Triaged
Status in fprintd source package in Focal:
Fix Released
Status in fprintd source package in Groovy:
Fix Committed
Bug description:
[ Impact ]
The fingerprint reader is an UPEK TCRE3C usb fingerprint reader. It
was working fine with ubuntu 16.04 and
[Desktop-packages] [Bug 1908119] Re: Update and SRU 1.90.9
This bug was fixed in the package fprintd - 1.90.9-1~ubuntu20.04.1
---
fprintd (1.90.9-1~ubuntu20.04.1) focal; urgency=medium
* Backport to focal (LP: #1908119)
fprintd (1.90.9-1) unstable; urgency=medium
[ Marco Trevisan (Treviño) ]
* New upstream release:
- Fix multiple daemon lockup issues (#97)
- Fix print garbage collection to not delete used prints
- pam: Use the device with the most prints
* debian/control: Mark fprintd-doc as Multi-Arch: foreign
[ Helmut Grohne ]
* Fix nocheck FTFBS: Drop from non-optional dependencies.
(Closes: #977395)
fprintd (1.90.8-1~ubuntu20.04.1) focal; urgency=medium
* Backport to focal (LP: #1908119)
* debian/{control,gbp.conf}: Prepare for ubuntu focal branching
* debian/{control, rules}: Do not use debhelper 13 features
* debian/rules: Use meson test directly to handle timeouts
* debian/patches: Drop all the patches applied upstream
fprintd (1.90.8-1) unstable; urgency=medium
* New upstream release
- pam: Only listen to NameOwnerChanged after fprintd is known to run
- Place new ObjectManager DBus API at /net/reactivated/Fprint
* debian/patches: Remove all patches, applied upstream or not needed anymore
* debian/control: Depend on systemd 235, but only in linux
* debian/rules: Require systemd and set unit path only on linux
* debian/fprintd.install: Use dh-exec to filter linux-only files
fprintd (1.90.7-1) unstable; urgency=medium
* New upstream release
- Fix fprintd DBus configuration (Closes: #976990)
- Change details of what requires authorization
- Fix various race conditions in pam_fprintd
- Permit interactive authorization from fprintd utilities
- Do not allow deletion while another operation is ongoing
- pam: Guard strdup calls against NULL pointers
* debian/patches:
- Refresh
- Ignore NameOwnerChanged until fprintd is running
fprintd (1.90.5-2) unstable; urgency=medium
* debian/patches: Make tests run with actual required libfprint version
* debian/control: Remove test-only dependency on libfprint 1.90.4.
Tests are now working with older libfprint versions too
* debian/control: Add myself to Uploaders
* debian/gbp.conf: Include suggested settings by GNOME team.
Even if fprintd is not part of GNOME I think these settings are good
practice anyways.
fprintd (1.90.5-1) unstable; urgency=medium
* New upstream release:
- Permit building with polkit older than 0.114
- Fix possible issues with PAM test
- Fix incorrect DBus policy
- Fix build so that CFLAGS environment is correctly used
- Skip hotplug test with older libfprint (which times out otherwise)
* debian/patches: Drop patches applied upstream
fprintd (1.90.4-1) unstable; urgency=medium
* Team upload.
[ Marco Trevisan (Treviño) ]
* New upstream release:
- Use GDBus and async Polkit checks
- Authentication is now required to enroll a new print (LP: #1532264,
Closes: #719004)
- Add support for the libfprint early reporting mechanism
- Proper hotplug support together with libfprint 1.90.4
- Handle STATE_DIRECTORY containing multiple paths
- Various memory fixes (LP: #1888495)
* debian/control:
- Remove build dependency on dbus-glib (Closes: #955893)
- Mark as the packages required only for testing
- Use debhelper 13
- Bump libfprint-2 dependency on 1.90.4 on test case
* debian/rules:
- remove unneeded override to force --fail-missing (as per dh 13)
- Increase tests timeout multiplier
* debian/patches:
- Refresh
- Define auto-pointers functions if not defined:
Fixes a build failure with debian polkit version.
- Cleanup pam-wrapper temporary dir when running tests
- Fix dbus-policy file to address lintian
- Ensure we generate debug symbols in debian builds
[ Laurent Bigonville ]
* debian/control: Bump Standards-Version to 4.5.1 (no further changes)
fprintd (1.90.1-2) unstable; urgency=low
* Team upload.
* Simplify the installation of the pam-config, do not install one
configuration file per architecture
* debian/NEWS: Add an news entry explaining that the user will have to
re-enroll their fingerprints upon update to 1.90.1.
-- Marco Trevisan (Treviño) Mon, 22 Feb 2021
16:00:47 +0100
** Changed in: fprintd (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fprintd in Ubuntu.
https://bugs.launchpad.net/bugs/1908119
Title:
Update and SRU 1.90.9
Status in fprintd package in Ubuntu:
Fix Released
Status in fprintd source package in Focal:
Fix Released
Status in fprintd source package in Groovy:
Fix Committed
Bug description:
[ Impact ]
Fprintd 1.90.7 is a new upstream version of fprintd that addresses many
issues that have been here for some years, including some security ones (such
as bug #1532264).
It was
[Desktop-packages] [Bug 1882291] Re: Gnome Shell clock is truncated/corrupt on the right side
** No longer affects: yaru -- 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/1882291 Title: Gnome Shell clock is truncated/corrupt on the right side Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: When clock changes value, it doesn't displaying time properly To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1882291/+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 1930550] Re: usb sound devices crackling
** Also affects: pulseaudio via https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1227 Importance: Unknown Status: Unknown ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1930550 Title: usb sound devices crackling Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: New Bug description: After upgrade from 20.04 to 21.04 all 3 my usb sound devices start crackling, i have xduoo05plus, audeze mobius, audient id4. I also tried to modify default-fragments = 5 default-fragment-size-msec = 2 to different sugested on stackoverflow articles setting Also this is in my config: high-priority = yes nice-level = -11 realtime-scheduling = yes realtime-priority = 5 I even tried to switch to pipewire, but it still the same. Possible issue in alsa kernel drivers for usb interface, submitting bug to pulse as it default in ubuntu. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: pulseaudio 1:14.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Jun 2 11:11:55 2021 InstallationDate: Installed on 2019-08-13 (658 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to hirsute on 2021-05-16 (16 days ago) dmi.bios.date: 08/12/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. 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.:bvrF11:bd08/12/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnB85-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85-HD3:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: B85-HD3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.system.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2021-05-18T13:33:15.787174 mtime.conffile..etc.pulse.system.pa: 2021-05-18T11:20:40.860787 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1930550/+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 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
This bug was fixed in the package alsa-ucm-conf - 1.2.2-1ubuntu0.8
---
alsa-ucm-conf (1.2.2-1ubuntu0.8) focal; urgency=medium
* d/p/0001-HDA-Intel-add-RearMic-JackControl.patch
Add "Rear Mic Jack" to make P520 rear mic works correctly. (LP: #1929371)
-- Jeremy Szu Tue, 25 May 2021 11:42:01
+
** Changed in: alsa-ucm-conf (Ubuntu Focal)
Status: Fix Committed => Fix Released
** Changed in: pulseaudio (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1929371
Title:
[SRU] there is always a "Rear Microphone - Built-in Audio" option on
the input device list even if the microphone is unplugged
Status in OEM Priority Project:
Triaged
Status in alsa-ucm-conf package in Ubuntu:
Fix Released
Status in pulseaudio package in Ubuntu:
Fix Released
Status in alsa-ucm-conf source package in Focal:
Fix Released
Status in pulseaudio source package in Focal:
Fix Released
Status in alsa-ucm-conf source package in Hirsute:
Fix Released
Status in pulseaudio source package in Hirsute:
Fix Released
Bug description:
[Impact]
In Lenovo P520, which using a codec for front panel, the other codec for rear
panel and both are on a same card.
In this case, the rear Mic will present on input devices of "Sound
Settings" even if attaching nothing to rear mic jack.
[Fix]
For alsa-ucm-conf part, the Mic 2 should use "Rear Mic Jack" as JackControl
because of
```
control.18 {
iface CARD
name 'Rear Mic Jack'
value true
comment {
access read
type BOOLEAN
count 1
}
}
```
After applying "Rear Mic Jack", the rear Mic will not always there anymore
but it's not there as well if hot-plugging audio device on rear mic. Thus, it
needs to change pulseaudio to handle if all devices are off cases.
For pulseaudio, if there is no any audio devices attached, then
attaching an input device on rear mic jack. The port will not be
selected automatically because the profiles is off. It needs patch
pulseaudio to check off profiles (for dual codec case).
[Test]
After applying these patches, the rear mic jack works good in all cases (boot
without mic and then attach mic, boot with mic and then hotplug it) and other
functions (line-in / line-out) work pretty well.
[Where problems could occur]
This change only apply the bonus on below cases:
```
if ((has_input_port && found_available_input_port && !has_output_port) ||
(has_output_port && found_available_output_port && !has_input_port) ||
(has_input_port && found_available_input_port && has_output_port &&
found_available_output_port))
```
and these cases have been tested.
If there are some complex codec design then it might cause problem but so far
we didn't see that.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1929371/+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 1882291] Re: Gnome Shell clock is truncated/corrupt on the right side
** Changed in: yaru Status: Unknown => Fix Released -- 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/1882291 Title: Gnome Shell clock is truncated/corrupt on the right side Status in GNOME Shell: Unknown Status in Yaru Theme: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Bug description: When clock changes value, it doesn't displaying time properly To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1882291/+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 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
This bug was fixed in the package pulseaudio - 1:13.99.1-1ubuntu3.11
---
pulseaudio (1:13.99.1-1ubuntu3.11) focal; urgency=medium
* d/p/0016-check_off_profile_when_switching_profile.patch
* d/p/0017-add_dynamic_priority_bonus_base_for_alsa_profiles.patch
Fix a "Rear Mic" always showing on input list when using dual codec.
(LP: #1929371)
[ Hui Wang ]
* d/p/0704-alsa-mixer-use-safe-dB-range-values-when-the-overrid.patch
* d/p/0705-alsa-mixer-add-support-up-8-mixer-channels.patch
- The linux kernel 5.11 starts supporting more than 2 channels for
the digital mic, we need to add the support of 8 channels for a
single alsa mixer, otherwise the PA can't change the hardware input
volume of the digital mic.
(LP: #1929817)
-- Jeremy Szu Tue, 25 May 2021 16:04:07
+
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1929371
Title:
[SRU] there is always a "Rear Microphone - Built-in Audio" option on
the input device list even if the microphone is unplugged
Status in OEM Priority Project:
Triaged
Status in alsa-ucm-conf package in Ubuntu:
Fix Released
Status in pulseaudio package in Ubuntu:
Fix Released
Status in alsa-ucm-conf source package in Focal:
Fix Released
Status in pulseaudio source package in Focal:
Fix Released
Status in alsa-ucm-conf source package in Hirsute:
Fix Released
Status in pulseaudio source package in Hirsute:
Fix Released
Bug description:
[Impact]
In Lenovo P520, which using a codec for front panel, the other codec for rear
panel and both are on a same card.
In this case, the rear Mic will present on input devices of "Sound
Settings" even if attaching nothing to rear mic jack.
[Fix]
For alsa-ucm-conf part, the Mic 2 should use "Rear Mic Jack" as JackControl
because of
```
control.18 {
iface CARD
name 'Rear Mic Jack'
value true
comment {
access read
type BOOLEAN
count 1
}
}
```
After applying "Rear Mic Jack", the rear Mic will not always there anymore
but it's not there as well if hot-plugging audio device on rear mic. Thus, it
needs to change pulseaudio to handle if all devices are off cases.
For pulseaudio, if there is no any audio devices attached, then
attaching an input device on rear mic jack. The port will not be
selected automatically because the profiles is off. It needs patch
pulseaudio to check off profiles (for dual codec case).
[Test]
After applying these patches, the rear mic jack works good in all cases (boot
without mic and then attach mic, boot with mic and then hotplug it) and other
functions (line-in / line-out) work pretty well.
[Where problems could occur]
This change only apply the bonus on below cases:
```
if ((has_input_port && found_available_input_port && !has_output_port) ||
(has_output_port && found_available_output_port && !has_input_port) ||
(has_input_port && found_available_input_port && has_output_port &&
found_available_output_port))
```
and these cases have been tested.
If there are some complex codec design then it might cause problem but so far
we didn't see that.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1929371/+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 1929817] Re: [SRU] pulseaudio: let a single alsa mixer support up to 8 channels (focal only)
This bug was fixed in the package pulseaudio - 1:13.99.1-1ubuntu3.11 --- pulseaudio (1:13.99.1-1ubuntu3.11) focal; urgency=medium * d/p/0016-check_off_profile_when_switching_profile.patch * d/p/0017-add_dynamic_priority_bonus_base_for_alsa_profiles.patch Fix a "Rear Mic" always showing on input list when using dual codec. (LP: #1929371) [ Hui Wang ] * d/p/0704-alsa-mixer-use-safe-dB-range-values-when-the-overrid.patch * d/p/0705-alsa-mixer-add-support-up-8-mixer-channels.patch - The linux kernel 5.11 starts supporting more than 2 channels for the digital mic, we need to add the support of 8 channels for a single alsa mixer, otherwise the PA can't change the hardware input volume of the digital mic. (LP: #1929817) -- Jeremy Szu Tue, 25 May 2021 16:04:07 + ** Changed in: pulseaudio (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1929817 Title: [SRU] pulseaudio: let a single alsa mixer support up to 8 channels (focal only) Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] Many Lenovo laptops have up to 4 microphones (microphone array), before the linux kernel 5.11, the alsa mixer for digital microphone is 2 channels, and the PA in the focal also supports up to 2 chanels for a single alsa mixer, so the PA in the focal works well with linux kernel 5.10 and lower on those Lenovo laptops. But we are going to install hirsute kernel (5.11) to the focal, the PA in the focal can't handle 4 channels of the digital mic, it will use pure software volume for digital mic, user can't adjust hardware volume of the digital mic anymore. [Fix] Backport 2 patches from PA-14.2, the PA in the hirsute (21.04) already have these 2 patches, so this SRU is for focal only. After applying these 2 patches, the PA could handle up to 8 channels for a single alsa mixer. [Test] Install patched PA on Lenovo laptops with 4 digital microphone, I could change the hardware input volume of digital mic through pulseaudio. I also installed patched PA to some old lenovo and Dell machines, all output and input devices worked as well as before, there is no regression observed. [Where problems could occur] This could introduce a regression on the output/input volume control, for example, the output or input volume only supports software volume in the PA, users can't adjust the hardware volume through pulseaudio anymore. But this regression possibility is very low, first the hirsute already has these 2 patches, second I already tested these 2 patches on different machines, all worked as well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1929817/+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 1930550] Re: usb sound devices crackling
created report https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1227 ** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #1227 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1227 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1930550 Title: usb sound devices crackling Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrade from 20.04 to 21.04 all 3 my usb sound devices start crackling, i have xduoo05plus, audeze mobius, audient id4. I also tried to modify default-fragments = 5 default-fragment-size-msec = 2 to different sugested on stackoverflow articles setting Also this is in my config: high-priority = yes nice-level = -11 realtime-scheduling = yes realtime-priority = 5 I even tried to switch to pipewire, but it still the same. Possible issue in alsa kernel drivers for usb interface, submitting bug to pulse as it default in ubuntu. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: pulseaudio 1:14.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Jun 2 11:11:55 2021 InstallationDate: Installed on 2019-08-13 (658 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to hirsute on 2021-05-16 (16 days ago) dmi.bios.date: 08/12/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. 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.:bvrF11:bd08/12/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnB85-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85-HD3:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: B85-HD3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.system.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2021-05-18T13:33:15.787174 mtime.conffile..etc.pulse.system.pa: 2021-05-18T11:20:40.860787 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1930550/+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 1929817] Update Released
The verification of the Stable Release Update for pulseaudio has completed successfully and the package is now being 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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1929817 Title: [SRU] pulseaudio: let a single alsa mixer support up to 8 channels (focal only) Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] Many Lenovo laptops have up to 4 microphones (microphone array), before the linux kernel 5.11, the alsa mixer for digital microphone is 2 channels, and the PA in the focal also supports up to 2 chanels for a single alsa mixer, so the PA in the focal works well with linux kernel 5.10 and lower on those Lenovo laptops. But we are going to install hirsute kernel (5.11) to the focal, the PA in the focal can't handle 4 channels of the digital mic, it will use pure software volume for digital mic, user can't adjust hardware volume of the digital mic anymore. [Fix] Backport 2 patches from PA-14.2, the PA in the hirsute (21.04) already have these 2 patches, so this SRU is for focal only. After applying these 2 patches, the PA could handle up to 8 channels for a single alsa mixer. [Test] Install patched PA on Lenovo laptops with 4 digital microphone, I could change the hardware input volume of digital mic through pulseaudio. I also installed patched PA to some old lenovo and Dell machines, all output and input devices worked as well as before, there is no regression observed. [Where problems could occur] This could introduce a regression on the output/input volume control, for example, the output or input volume only supports software volume in the PA, users can't adjust the hardware volume through pulseaudio anymore. But this regression possibility is very low, first the hirsute already has these 2 patches, second I already tested these 2 patches on different machines, all worked as well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1929817/+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 1930700] Re: Firefox 89 won't load pages due to many fonts
** Bug watch added: Mozilla Bugzilla #1694174 https://bugzilla.mozilla.org/show_bug.cgi?id=1694174 ** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=1694174 Importance: Unknown Status: Unknown -- 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/1930700 Title: Firefox 89 won't load pages due to many fonts Status in Mozilla Firefox: Unknown Status in firefox package in Ubuntu: Fix Released Bug description: Upgraded Firefox to 89 and it shows a crash tab every time because I have 22000+ fonts. In safe-mode it works, but refreshed firefox still has the bug. When starting firefox from the terminal it shows messages like: [Parent 42669, Main Thread] WARNING: Too many file descriptors for one message!: file /build/firefox- Sx7Sor/firefox-89.0+build2/ipc/chromium/src/chrome/common/ipc_message_utils.h:414 This only happens since Firefox 89 and not in 88. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 89.0+build2-0ubuntu0.21.04.1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: shemgp 5850 F pulseaudio /dev/snd/controlC0: shemgp 5850 F pulseaudio /dev/snd/controlC1: shemgp 5850 F pulseaudio BuildID: 20210527174632 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: GNOME Date: Thu Jun 3 19:36:30 2021 EcryptfsInUse: Yes Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2015-09-28 (2074 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:355 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=89.0/20210527174632 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to hirsute on 2021-02-16 (106 days ago) dmi.bios.date: 09/25/2019 dmi.bios.release: 2.75 dmi.bios.vendor: LENOVO dmi.bios.version: GCETB5WW (2.75 ) dmi.board.asset.tag: Not Available dmi.board.name: 34361A0 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.15 dmi.modalias: dmi:bvnLENOVO:bvrGCETB5WW(2.75):bd09/25/2019:br2.75:efr1.15:svnLENOVO:pn34361A0:pvrThinkPadX220:rvnLENOVO:rn34361A0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X220 dmi.product.name: 34361A0 dmi.product.sku: LENOVO_MT_3436 dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1930700/+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 1932021] Re: cannot find proper graphics drivers and cannot install (NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M])
Since the 'oibaf' PPA is likely the problem here I am going to close this bug. Please uninstall the PPA, reboot, and if the problem continues to occur then open a new bug. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Invalid ** Changed in: software-properties (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1932021 Title: cannot find proper graphics drivers and cannot install (NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M]) Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Status in software-properties package in Ubuntu: Invalid Bug description: in the additional driver, till the last update 20.10 i had option to choose the nvidia graphics diver. now after the upgrade to hippo i am unable to change the driver. also cannot install drivers from command line as well. while installing the latest or any other nvidia drivers had issues of mismatch packages and the install was broken every time i try. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 15 19:02:03 2021 DistUpgraded: 2021-06-15 01:56:42,836 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.18, 5.11.0-18-generic, x86_64: installed virtualbox, 6.1.18, 5.8.0-55-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3978] Subsystem: Lenovo GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [17aa:3817] InstallationDate: Installed on 2020-09-14 (274 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20404 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=5bdb42c7-4383-40ee-b1ba-ee63c9932b5f ro quiet splash i8042.nokbd vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-06-14 (0 days ago) dmi.bios.date: 05/21/2014 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: A0CN26WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Flex 2-14 dmi.board.vendor: LENOVO dmi.board.version: 31900059 Std dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Flex 2-14 dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnLENOVO:bvrA0CN26WW:bd05/21/2014:br1.9:efr1.3:svnLENOVO:pn20404:pvrLenovoFlex2-14:rvnLENOVO:rnLenovoFlex2-14:rvr31900059Std:cvnLENOVO:ct10:cvrLenovoFlex2-14: dmi.product.family: IDEAPAD dmi.product.name: 20404 dmi.product.sku: LENOVO_MT_20404_BU_idea_FM_Lenovo Flex 2-14 dmi.product.version: Lenovo Flex 2-14 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104+git2101240500.19f0a9~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 21.1~git2102070600.92f129~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx 21.1~git2102070600.92f129~oibaf~f version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1932021/+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 1932021] Re: cannot find proper graphics drivers and cannot install
Thanks for the bug report. It appears the correct driver for your Nvidia GPU is version 390.143 which does exist in hirsute. You can try installing it by: sudo apt install nvidia-driver-390 Also, you appear to have some unsupported graphics packages installed from the 'oidbaf' PPA, which is known to cause bugs. Please remove that PPA from your system. ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-390 (Ubuntu) ** Also affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Summary changed: - cannot find proper graphics drivers and cannot install + cannot find proper graphics drivers and cannot install (NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M]) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1932021 Title: cannot find proper graphics drivers and cannot install (NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M]) Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Status in software-properties package in Ubuntu: Invalid Bug description: in the additional driver, till the last update 20.10 i had option to choose the nvidia graphics diver. now after the upgrade to hippo i am unable to change the driver. also cannot install drivers from command line as well. while installing the latest or any other nvidia drivers had issues of mismatch packages and the install was broken every time i try. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 15 19:02:03 2021 DistUpgraded: 2021-06-15 01:56:42,836 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.18, 5.11.0-18-generic, x86_64: installed virtualbox, 6.1.18, 5.8.0-55-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3978] Subsystem: Lenovo GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [17aa:3817] InstallationDate: Installed on 2020-09-14 (274 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20404 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=5bdb42c7-4383-40ee-b1ba-ee63c9932b5f ro quiet splash i8042.nokbd vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-06-14 (0 days ago) dmi.bios.date: 05/21/2014 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: A0CN26WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Flex 2-14 dmi.board.vendor: LENOVO dmi.board.version: 31900059 Std dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Flex 2-14 dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnLENOVO:bvrA0CN26WW:bd05/21/2014:br1.9:efr1.3:svnLENOVO:pn20404:pvrLenovoFlex2-14:rvnLENOVO:rnLenovoFlex2-14:rvr31900059Std:cvnLENOVO:ct10:cvrLenovoFlex2-14: dmi.product.family: IDEAPAD dmi.product.name: 20404 dmi.product.sku: LENOVO_MT_20404_BU_idea_FM_Lenovo Flex 2-14 dmi.product.version: Lenovo Flex 2-14 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104+git2101240500.19f0a9~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 21.1~git2102070600.92f129~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx 21.1~git2102070600.92f129~oibaf~f version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1932021/+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 1931793] Re: two bluetooth icons
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) -- 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/1931793 Title: two bluetooth icons Status in gnome-shell package in Ubuntu: Incomplete Bug description: There two different bluetooth icons on my taskbar. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114 Uname: Linux 5.4.0-74-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 13 13:49:02 2021 DistUpgraded: 2020-05-22 21:25:58,624 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:81eb] InstallationDate: Installed on 2020-01-28 (501 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 003: ID 04f2:b56c Chicony Electronics Co., Ltd HP TrueVision HD Bus 001 Device 002: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-74-generic root=UUID=e8d9a762-01b7-4681-bf37-86327e77af4a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-22 (386 days ago) dmi.bios.date: 01/05/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EB dmi.board.vendor: HP dmi.board.version: 61.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd01/05/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EB:rvr61.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: 1DE70PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1931793/+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 1933064] Re: [Clevo NS50MU] Max screen brightness after suspend
** Summary changed: - Max screen brightness after suspend + [Clevo NS50MU] Max screen brightness after suspend ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Package changed: linux (Ubuntu) => linux-hwe-5.8 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1933064 Title: [Clevo NS50MU] Max screen brightness after suspend Status in linux-hwe-5.8 package in Ubuntu: New Bug description: When I suspend my laptop and start using it again, screen brightness is always at a maximum. When I then adjust the screen brightness, it all of a sudden remembers the state it was in before suspending (usually the lowest setting). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 21 08:49:49 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:51a1] InstallationDate: Installed on 2021-05-31 (20 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Notebook NS50MU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-55-generic root=/dev/mapper/vgubuntu-root ro quiet splash acpi_osi=! acpi_osi=Linux vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.6 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06LWL dmi.board.name: NS50MU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06LWL:bd09/07/2020:br7.6:efr7.2:svnNotebook:pnNS50MU:pvrNotApplicable:rvnNotebook:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NS50MU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1933064/+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 1933067] Re: Startup bios defective
Please explain in more detail what kind of problem you are experiencing. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1933067 Title: Startup bios defective Status in Ubuntu: Incomplete Bug description: Ubuntu updates prone to fail. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-119.120-generic 4.15.18 Uname: Linux 4.15.0-119-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Jun 21 00:12:50 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] InstallationDate: Installed on 2015-12-20 (2010 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP ProBook 4510s ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-119-generic root=UUID=a019a556-761b-432a-9ed2-c81051ae44fe ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PZI Ver. F.15 dmi.board.name: 3072 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 24.0E dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZIVer.F.15:bd02/23/2010:svnHewlett-Packard:pnHPProBook4510s:pvrF.15:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0E:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP ProBook 4510s dmi.product.version: F.15 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-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 xserver.bootTime: Mon Sep 17 01:04:12 2018 xserver.configfile: default xserver.errors: /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5504 vendor CMO xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1933067/+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 1933027] Re: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled
Assigning to gnome-shell (which implements the login GUI). ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/1933027 Title: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled Status in gdm3 package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: I use my Ubuntu PC with Yubikey almost always plugged in. It provides several security token interfaces, such as U2F, GPG smartcard, proprieritary Yubico interfaces (of which I mostly use TOTP codes), and also PIV smartcard. However, I haven't configured a PIV smartcard on it. Whenever I login into the system having Yubikey plugged in, I'm prompted for login name, and then for PIN for some smartcard while also being asked to plug in one. This is very misleading on several layers: 1. I have the device providing smartcard plugged id, 2. But it's not the smartcard GDM would think it is as it's not configured properly, 3. There are no local smartcard-authenticating users right now in the system, 3. There are no remote authentication systems configured on the system (so no ActiveDirectory-smartcard logins or such). If I unplug the token UX goes back on old good track. Given the circumstances above, I'd consider that GDM (and, on my bet, any PAM configuration it uses) shouldn't offer to login using smartcard if there is no way to actually do so. I feel something is off here, so I'm reporting a bug. It could be an upstream problem though; it also could be an upstream SSSD problem, or all combined. I believe there is a more clear user experience: 1. GDM should display users that can login into the system, as it always does (if configured). It may also provide entering other login name (also if configured). This is GDM usually does without smartcards altogether. 2. When user is chosen (from the list or manually typed in), check can this user even authenticate with smartcards (i.e. if any of available smartcards is actually recognised for this user). If so, then ask for PIN. Else, don't show anything about smartcards at all (this includes when SSSD is not configured for any AD or related and this user has no local smartcard configuration). This can switch there & back based on device events. I've seen other OS doing this. Ubuntu/Gnome session doesn't ask me for PIN for a smartcard on a lock screen, so I guess it doesn't support it at all or correctly finds out it can't be used. Even more, I couldn't find a way to actually add my smartcard as a local login method. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gdm3 3.38.2.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jun 20 14:02:02 2021 InstallationDate: Installed on 2017-03-05 (1567 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to hirsute on 2021-05-13 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1933027/+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 1933022] Re: gnome control-center crashed with sigsegv in g_str_hash() whenever I try to add input sources
I can't find any other reports of such a crash. Please report it to the
developers at https://gitlab.gnome.org/GNOME/gnome-control-
center/-/issues
** Tags added: impish
--
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/1933022
Title:
gnome control-center crashed with sigsegv in g_str_hash() whenever I
try to add input sources
Status in gnome-control-center package in Ubuntu:
New
Bug description:
I've been facing the problems for about 9 months now. Back then I
thought that maybe getting a new version would solve the problem, but
turns out it didn't. Whenever I try to add some Input Sources from it
just crashes.
Reproducing it is very easy: running gnome-control-center, then going
to Input Sources settings and clicking Add(+) would generate the
crash. But the weird thing is that I've been unable to reproduce it in
VM. And I also tried to reinstall most of the packages which, I think
if changed/misconfigured would cause this but it didn't help. I also
tried to use debsums to give some clues but didn't find any.
After enough digging, this is what I can retrieve from gdb:
#0 g_str_hash (v=0x506) at ../../../glib/ghash.c:2333
p = 0x506
h = 5381
#1 0x77c6e174 in g_hash_table_lookup_node (hash_return=, key=0x506, hash_table=0x563a6180 = {...}) at
../../../glib/ghash.c:472
node_hash =
hash_value =
have_tombstone = 0
step = 0
node_index =
first_tombstone = 0
node_hash =
__func__ = "g_hash_table_lookup_extended"
#2 g_hash_table_lookup_extended (hash_table=0x563a6180 = {...},
lookup_key=lookup_key@entry=0x506, orig_key=orig_key@entry=0x0,
value=value@entry=0x7fffcbb0) at ../../../glib/ghash.c:1548
node_hash =
__func__ = "g_hash_table_lookup_extended"
#3 0x76f03013 in gnome_xkb_info_get_layout_info (self=, id=id@entry=0x506 ,
display_name=display_name@entry=0x7fffcc10,
short_name=short_name@entry=0x0, xkb_layout=xkb_layout@entry=0x0,
xkb_variant=xkb_variant@entry=0x0) at ../libgnome-desktop/gnome-xkb-info.c:1042
priv = 0x56395600
layout = 0x76262ba0
__func__ = "gnome_xkb_info_get_layout_info"
#4 0x555fe467 in input_source_row_new
(self=self@entry=0x568d22b0, type=type@entry=0x556dcac3 "xkb",
id=id@entry=0x506 ) at
../panels/keyboard/cc-input-chooser.c:236
display_name = 0x0
row = 0x0
widget =
#5 0x555fe81d in add_rows_to_table (self=self@entry=0x568d22b0,
info=info@entry=0x56450320, list=0x55c82100 = {...},
list@entry=0x55c8bec0 = {...}, type=type@entry=0x556dcac3 "xkb",
default_id=0x0) at ../panels/keyboard/cc-input-chooser.c:723
table = 0x5677 = {[0x5657bb00 "cm+mmuock"] =
0x56ca91a0, [0x56506340 "us+3l"] = 0x56400920, [0x5656f6f0
"ph+capewell-dvorak"] = 0x56cb6f50, [0x5660caf0 "us+dvorak-l"] =
0x56ca9620, [0x5656cd40 "gb+mac_intl"] = 0x56cb6950,
[0x5650de80 "gh+gillbt"] = 0x56cb61d0, [0x56571540 "apl+aplx"] =
0x56ca94a0, [0x565063a0 "us+3l-cros"] = 0x56cb64d0, [0x565062b0
"us+carpalx-full-intl"] = 0x56400aa0, [0x56506070 "us+sun_type6"] =
0x56cb6350, [0x56505f50 "us+drix"] = 0x56ca9320, [0x56506b40
"cm+dvorak"] = 0x56cb6dd0, [0x564faaf0 "us+dvp"] = 0x56cb6650,
[0x564faa80 "us+dvorak-classic"] = 0x564004a0, [0x564fad30
"us+olpc2"] = 0x56400c20, [0x5656f2d0 "ml+us-intl"] = 0x56400620,
[0x564f9c70 "eu"] = 0x56400320, [0x56506310
"us+carpalx-full-altgr-intl"] = 0x564007a0, [0x5656c390 "gb+intl"] =
0x56ca97a0, [0x56506fc0 "ca+eng"] = 0x56cb67d0, [0x565714a0
"apl+aplplusII"] = 0x56400f20, [0x564fafb0 "us+norman"] =
0x56400da0, [0x5660ca90 "us+dvorak-intl"] = 0x56cb6ad0,
[0x56506140 "us+carpalx-intl"] = 0x56cb6c50}
row =
id = 0x506
#6 0x555ffb78 in get_locale_infos (self=0x568d22b0) at
../panels/keyboard/cc-input-chooser.c:950
country_code = 0x5680eb50 "BW"
simple_locale = 0x5680eb70 "en_BW.UTF-8"
tmp = 0x568acf70 "English (Botswana)"
type = 0x0
language_layouts = 0x55c8bec0
lang_code = 0x5680eb30 "en"
id = 0x0
layouts_with_locale = 0x56772e40
info = 0x56450320
locale = 0x5680e950
all_layouts = 0x0
locale_ids = 0x5680e950
l =
self = 0x568d22b0
error = 0x0
#7 cc_input_chooser_new (is_login=, xkb_info=,
ibus_engines=) at ../panels/keyboard/cc-input-chooser.c:1068
self = 0x568d22b0
error = 0x0
[Desktop-packages] [Bug 1933003] Re: left click on USB mouse stops working
Sounds like either a faulty mouse or a Xorg-specific bug (the login screen doesn't use Xorg). Please try either a new mouse, or selecting 'Ubuntu on Wayland' from the login screen. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/1933003 Title: left click on USB mouse stops working Status in xorg-server package in Ubuntu: Incomplete Bug description: ## Issue with mouse left-button click Issue with left-button (button 1) click. After login left mouse button click stops working. Within xev rectangle, it (button 1) does not show output first time. but after right button click it starts showing output in xen output as shown in xev-output.log file. After that, left button click works once or twice in other windows like chrome etc, but then stops working after that. full manufacturer and model of your mouse. - HP X1000 Wired Mouse - Connected via USB - Has 2-buttons and one middle scrooll wheel and has optical sensor ## Attachements (inside 'debug-attachments.zip' file_ - Recent apt updates are in apt-history.log file - xen output as shown in xev-output.log file - xmodmap -pp > ~/xmodmap-pp ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.119.03 Mon Mar 29 17:51:27 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 19 20:10:30 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 450.119.03, 5.8.0-53-generic, x86_64: installed nvidia, 450.119.03, 5.8.0-55-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83ba] Subsystem: Hewlett-Packard Company GP108M [GeForce MX150] [103c:83ba] InstallationDate: Installed on 2020-05-18 (396 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 003: ID 0408:5251 Quanta Computer, Inc. HP Wide Vision FHD Camera Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 15-ch0xx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=10b0a8d0-b11d-4604-a11a-0717ee06ce60 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2019 dmi.bios.release: 15.31 dmi.bios.vendor: AMI dmi.bios.version: F.31 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83BA dmi.board.vendor: HP dmi.board.version: 57.33 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 57.33 dmi.modalias: dmi:bvnAMI:bvrF.31:bd05/20/2019:br15.31:efr57.33:svnHP:pnHPSpectrex360Convertible15-ch0xx:pvr:rvnHP:rn83BA:rvr57.33:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-ch0xx dmi.product.sku: 2LV24UA#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1
[Desktop-packages] [Bug 1932979] Re: blank screen with cursor after login
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Tags added: amdgpu ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1932979 Title: blank screen with cursor after login Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 on amd64. I came back to the machine after it was idle long enough for the screen to go blank. I can see the cursor move with the mouse, but nothing else. This is VT2. VT1 shows a login screen. I can get to console VTs as well and did so to file the report. I see the following in the system log that may be related: Jun 18 18:29:54 cerberus gnome-shell[4694]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed Jun 18 18:29:54 cerberus gnome-shell[4694]: Source ID 3568871 was not found when attempting to remove it Jun 18 18:29:54 cerberus gnome-shell[4694]: Source ID 3568998 was not found when attempting to remove it Jun 18 18:29:54 cerberus gnome-shell[4694]: Source ID 3569045 was not found when attempting to remove it Jun 18 18:29:54 cerberus gnome-shell[4694]: [System monitor] applet disable Jun 18 18:29:54 cerberus gnome-shell[4694]: g_dbus_connection_emit_signal: assertion 'G_IS_DBUS_CONNECTION (connection)' failed ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114 Uname: Linux 5.4.0-74-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 18 19:33:55 2021 DistUpgraded: 2020-11-04 10:03:47,100 DEBUG running doUpdate() (showErrors=True) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev c7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Radeon RX 480 [1043:04fb] InstallationDate: Installed on 2020-05-29 (385 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Supermicro X10DAi ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=linux XDG_RUNTIME_DIR= PATH=(custom, user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-74-generic root=/dev/mapper/ubuntu--vg-root ro amdgpu.dc=0 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-11-04 (226 days ago) dmi.bios.date: 12/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X10DAI dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.2:bd12/16/2019:svnSupermicro:pnX10DAi:pvr123456789:rvnSupermicro:rnX10DAI:rvr1.01:cvnTobefilledbyO.E.M.:ct3:cvrTobefilledbyO.E.M.: dmi.product.family: SMC X10 dmi.product.name: X10DAi dmi.product.sku: 083615D9 dmi.product.version: 123456789 dmi.sys.vendor: Supermicro version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1932979/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1932357] Re: Mouse events not interpreted correctly
It sounds like some events (or Bluetooth packets) are going missing. Please try a wired mouse, or try avoiding 2.4GHz wifi networks that may interfere with Bluetooth (use 5GHz instead). ** Package changed: mutter (Ubuntu) => libinput (Ubuntu) ** Summary changed: - Mouse events not interpreted correctly + [Logitech MX Anywhere 2S] Mouse events not interpreted correctly ** Package changed: libinput (Ubuntu) => linux (Ubuntu) -- 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/1932357 Title: [Logitech MX Anywhere 2S] Mouse events not interpreted correctly Status in linux package in Ubuntu: New Bug description: This is a very weird bug that started occurring since I updated to 21.04. I am not sure mutter is the correct package. I have a bluetooth mouse that works perfectly (I'll clarify below why I'm sure it works). Sometimes, seemingly at random, scrolling stops working correctly, but not always in all applications (eg. scroll starts failing in Firefox, but works fine in Terminal). When this happens, moving the mouse around over a window causes it to scroll randomly up and down, while moving the mouse wheel also works randomly (sometimes it scrolls in the correct direction, sometimes in the opposite direction, sometimes not at all). This occurs only when I have my external monitor connected (dual, non mirrored displays). If I unplug the display, the problem disappears immediately. If I plug the display back in, that problem reappears immediately (if it was already occurring before). While the problem is "active", I can scroll without problem using the notebook's touchpad. It seems to affect only the mouse. I've seen messages like this in the log, but it does not seem strongly correlated with the occurrence of the problem: libinput error: event21 - MX Anywhere 2S Mouse: client bug: event processing lagging behind by 21ms, your system is too slow Also, rebooting the computer fixes the issue for a few hours/days, until it appears again. Also, the problem sometimes "solves itself" after a few minutes, or it intermittenly appears every few minutes. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mutter 3.38.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Jun 17 13:58:15 2021 InstallationDate: Installed on 2018-12-14 (916 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: mutter UpgradeStatus: Upgraded to hirsute on 2021-05-30 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932357/+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 1932548] Re: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless
It appears the offending kernel is indeed about two weeks old: https://launchpad.net/ubuntu/+source/linux-oem-5.10/5.10.0-1029.30 ** Summary changed: - Video conferences constantly freeze when I am on wireless + [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless ** Package changed: xorg (Ubuntu) => linux-oem-5.10 (Ubuntu) ** Tags added: regression-update -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1932548 Title: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless Status in linux-oem-5.10 package in Ubuntu: New Bug description: Whenever I am using a wireless connection, the image freezes roughly every two minutes. Sometimes, email cannot be retrieved / computer complains the connection was momentarily lost. - If I am on a wire, this problem does NOT occur. - This problems occurs on wireless independent of the platform used (behavior seen in both Google Hangout and Zoom) - This problem does NOT occur on Windows. I did a meeting where both my Linux and Windows machines were connected to the same meeting and using the same wifi router, and while the performance on Windows was flawless, unfortunately it was not so on the Ubuntu box. So I don't think my wifi router or network is to blame. - As far as I can recall, the problem used not to be there 2 weeks ago. So it may have been introduced by a recent update. - As communicated before, I am on a certified machine from Dell, recently purchased with Ubuntu already on board from factory (I assume the logs there were sent to you would contain the information). - I tried to generate a log on the wireless, but the process did not let me do this very easily. I am more than happy to send you additional information - but please let me know which package you want me to spy upon exactly, as I am not sure what would be helpful in this matter. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35 Uname: Linux 5.10.0-1029-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 18 09:47:58 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0991] InstallationDate: Installed on 2021-04-24 (54 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem root=UUID=28dc4511-d4dc-4dec-8abb-64e06b4e9d1e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2021 dmi.bios.release: 2.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.1 dmi.board.name: 08607K dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.1:bd03/25/2021:br2.1:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1932548/+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 1932289] Re: 'swipe finger' in login interface disappear and show up periodically
^^^ That's being tracked in bug 1933068, separate to this bug in case it's not the main issue here. ** No longer affects: gdm3 (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- 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/1932289 Title: 'swipe finger' in login interface disappear and show up periodically Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: New Bug description: After upgrade gnome-shell from 3.36.7-0ubuntu0.20.04.1 to 3.36.9-0ubuntu0.20.04.1, I met this issue. We took a short video for this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1932289/+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 1932289] Re: 'swipe finger' in login interface disappear and show up periodically
Oh yes, the message in comment #2: gdm-session-worker[1987]: free(): double free detected in tcache 2 matches: https://errors.ubuntu.com/problem/476b07edafb4eaa68c811cb00291075695ac7376 -- 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/1932289 Title: 'swipe finger' in login interface disappear and show up periodically Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: New Bug description: After upgrade gnome-shell from 3.36.7-0ubuntu0.20.04.1 to 3.36.9-0ubuntu0.20.04.1, I met this issue. We took a short video for this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1932289/+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 1932289] Re: 'swipe finger' in login interface disappear and show up periodically
I can't figure out which crash that is. Please upload the crash file using 'ubuntu-bug' or 'apport-cli'. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Also affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete ** Tags added: focal -- 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/1932289 Title: 'swipe finger' in login interface disappear and show up periodically Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: New Bug description: After upgrade gnome-shell from 3.36.7-0ubuntu0.20.04.1 to 3.36.9-0ubuntu0.20.04.1, I met this issue. We took a short video for this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1932289/+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 1933068] [NEW] /usr/lib/gdm3/gdm-session-worker:free(): double free detected in tcache 2
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.36.3-0ubuntu0.20.04.3, the problem page at https://errors.ubuntu.com/problem/476b07edafb4eaa68c811cb00291075695ac7376 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: focal groovy -- 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/1933068 Title: /usr/lib/gdm3/gdm-session-worker:free(): double free detected in tcache 2 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.36.3-0ubuntu0.20.04.3, the problem page at https://errors.ubuntu.com/problem/476b07edafb4eaa68c811cb00291075695ac7376 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/1933068/+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 1933067] [NEW] Startup bios defective
Public bug reported: Ubuntu updates prone to fail. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-119.120-generic 4.15.18 Uname: Linux 4.15.0-119-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Jun 21 00:12:50 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] InstallationDate: Installed on 2015-12-20 (2010 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP ProBook 4510s ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-119-generic root=UUID=a019a556-761b-432a-9ed2-c81051ae44fe ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PZI Ver. F.15 dmi.board.name: 3072 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 24.0E dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZIVer.F.15:bd02/23/2010:svnHewlett-Packard:pnHPProBook4510s:pvrF.15:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0E:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP ProBook 4510s dmi.product.version: F.15 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-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 xserver.bootTime: Mon Sep 17 01:04:12 2018 xserver.configfile: default xserver.errors: /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5504 vendor CMO xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1933067 Title: Startup bios defective Status in xorg package in Ubuntu: New Bug description: Ubuntu updates prone to fail. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-119.120-generic 4.15.18 Uname: Linux 4.15.0-119-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Jun 21 00:12:50 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] InstallationDate: Installed on 2015-12-20 (2010 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP ProBook 4510s ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-119-generic root=UUID=a019a556-761b-432a-9ed2-c81051ae44fe ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PZI Ver. F.15 dmi.board.name: 3072 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 24.0E
[Desktop-packages] [Bug 1932108] Re: bluetooth not starting also airplane mode is not working. laptop hp pavillion g6
Thanks for the bug report. The only log information I can find that might be relevant is: [ 30.453981] Bluetooth: hci0: command 0x1009 tx timeout which suggests a problem with the kernel driver, or the hardware. ** Summary changed: - bluetooth not starting also airplane mode is not working. laptop hp pavillion g6 + [USB 0a5c:21b4 Broadcom Corp. BCM2070 Bluetooth 2.1 + EDR] [HP Pavilion g6] Bluetooth not starting also airplane mode is not working. ** Package changed: bluez (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1932108 Title: [USB 0a5c:21b4 Broadcom Corp. BCM2070 Bluetooth 2.1 + EDR] Bluetooth not starting also airplane mode is not working. Status in linux package in Ubuntu: Confirmed Bug description: native bluetooth is not working.Sometimes disabling the wifi and bluetooth hardware and then enabling it again enables bluetooth. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jun 16 11:28:58 2021 InstallationDate: Installed on 2021-01-27 (140 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: bnep btusb bluetooth MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=35e14111-9084-42ac-baef-472ae96d2665 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-06-08 (7 days ago) dmi.bios.date: 02/11/2011 dmi.bios.release: 15.4 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.04 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1668 dmi.board.vendor: Hewlett-Packard dmi.board.version: 08.10 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.ec.firmware.release: 8.16 dmi.modalias: dmi:bvnHewlett-Packard:bvrF.04:bd02/11/2011:br15.4:efr8.16:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr059F100046100:rvnHewlett-Packard:rn1668:rvr08.10:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: LN246EA#A2N dmi.product.version: 059F100046100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:34 acl:0 sco:0 events:3 errors:0 TX bytes:12 acl:0 sco:0 commands:4 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932108/+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 1932377] Re: [HDA-Intel - HDA Intel MID, playback] No sound at all. bluetooth hedphones aren connected but in built speakers are used. to make bluetooth headphones to work i ne
*** This bug is a duplicate of bug 1932108 *** https://bugs.launchpad.net/bugs/1932108 ** This bug has been marked a duplicate of bug 1932108 [USB 0a5c:21b4 Broadcom Corp. BCM2070 Bluetooth 2.1 + EDR] Bluetooth not starting also airplane mode is not working. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1932377 Title: [HDA-Intel - HDA Intel MID, playback] No sound at all. bluetooth hedphones aren connected but in built speakers are used. to make bluetooth headphones to work i need to remove them from settings and addd them again. hp pavillion g6 Status in alsa-driver package in Ubuntu: New Bug description: firstly bluetooth services is somehow dead. to make it work we need to disable the hardware for some time so that in power settings both wifi and bluetooth is turned off and them enable it again for bluetooth to work. and after that if bluetooth is connected automatically then the audio input and output both works from laptop and after removing and adding again the bluetooth then only output is given from headphone. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: overlord 2136 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jun 18 09:26:55 2021 InstallationDate: Installed on 2021-01-27 (141 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed Symptom_Card: Built-in Audio - HDA Intel MID Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: overlord 2136 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel MID, playback] No sound at all UpgradeStatus: Upgraded to hirsute on 2021-06-08 (9 days ago) dmi.bios.date: 02/11/2011 dmi.bios.release: 15.4 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.04 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1668 dmi.board.vendor: Hewlett-Packard dmi.board.version: 08.10 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.ec.firmware.release: 8.16 dmi.modalias: dmi:bvnHewlett-Packard:bvrF.04:bd02/11/2011:br15.4:efr8.16:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr059F100046100:rvnHewlett-Packard:rn1668:rvr08.10:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: LN246EA#A2N dmi.product.version: 059F100046100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1932377/+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 1932066] Re: PulseAudio Preferences searches for libraries in incorrect location
** Tags added: focal
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1932066
Title:
PulseAudio Preferences searches for libraries in incorrect location
Status in pulseaudio package in Ubuntu:
New
Bug description:
PulseAudio Preferences (paprefs) appears to be searching for modules
in the wrong location.
Specifically, the "install" button appears when modules relevant
modules cannot be found by paprefs.
paprefs is searching for modules in the location:
/usr/lib/pulse-13.99/modules/
the modules are actually located in: /usr/lib/pulse-13.99.1/modules/
The specifics of this were determined via `strace paprefs`, which
(among a lot of other things), produces:
access("/usr/lib/pulse-13.99/modules/module-esound-protocol-tcp.so", F_OK) =
-1 ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-native-protocol-tcp.so", F_OK) =
-1 ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-zeroconf-publish.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-zeroconf-discover.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-raop-discover.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-rtp-recv.so", F_OK) = -1 ENOENT
(No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-rtp-send.so", F_OK) = -1 ENOENT
(No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-rygel-media-server.so", F_OK) =
-1 ENOENT (No such file or directory)
creating a symlink from /usr/lib/pulse-13.99.1 to /usr/lib/pulse-13.99
resolves the issue.
paprefs should perhaps be updated to match the version of the
pulseaudio package.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1932066/+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 1933064] [NEW] Max screen brightness after suspend
Public bug reported: When I suspend my laptop and start using it again, screen brightness is always at a maximum. When I then adjust the screen brightness, it all of a sudden remembers the state it was in before suspending (usually the lowest setting). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 21 08:49:49 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:51a1] InstallationDate: Installed on 2021-05-31 (20 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Notebook NS50MU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-55-generic root=/dev/mapper/vgubuntu-root ro quiet splash acpi_osi=! acpi_osi=Linux vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.6 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06LWL dmi.board.name: NS50MU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06LWL:bd09/07/2020:br7.6:efr7.2:svnNotebook:pnNS50MU:pvrNotApplicable:rvnNotebook:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NS50MU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1933064 Title: Max screen brightness after suspend Status in xorg package in Ubuntu: New Bug description: When I suspend my laptop and start using it again, screen brightness is always at a maximum. When I then adjust the screen brightness, it all of a sudden remembers the state it was in before suspending (usually the lowest setting). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 21 08:49:49 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:51a1] InstallationDate: Installed on 2021-05-31 (20 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Notebook NS50MU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-55-generic root=/dev/mapper/vgubuntu-root ro quiet splash acpi_osi=! acpi_osi=Linux vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.6 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06LWL dmi.board.name: NS50MU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06LWL:bd09/07/2020:br7.6:efr7.2:svnNotebook:pnNS50MU:pvrNotApplicable:rvnNotebook:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NS50MU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz
[Desktop-packages] [Bug 1932981] Re: desktop mouse selection appears on secondary monitor
** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension- desktop-icons-ng (Ubuntu) -- 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/1932981 Title: desktop mouse selection appears on secondary monitor Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Triaged Bug description: With a secondary monitor on the left, a mouse highlight on the desktop creates a slight selection box on the primary one, after the Ubuntu dock. If this isn't clear, see the attached screenshot. Expected: Only see the selection *where I selected*. Actual: Selection appears slightly on the primary monitor Also tested with all shell extensions disabled. badboyhalocat@bbhc-laptop:~$ lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 badboyhalocat@bbhc-laptop:~$ apt-cache policy gnome-shell gnome-shell: Installed: 3.38.4-1ubuntu3~21.04.1 Candidate: 3.38.4-1ubuntu3~21.04.1 Version table: *** 3.38.4-1ubuntu3~21.04.1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu hirsute-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.38.4-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-20.21-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jun 18 17:28:26 2021 DisplayManager: gdm3 ProcEnviron: LANGUAGE=en.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-05-13 (36 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1932981/+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 1931902] Re: [Asus PRIME B450-PLUS] Crackling sound on Pulseaudio for Ubuntu 21.04
** Summary changed: - Crackling sound on Pulseaudio for Ubuntu 21.04 + [Asus PRIME B450-PLUS] Crackling sound on Pulseaudio for Ubuntu 21.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1931902 Title: [Asus PRIME B450-PLUS] Crackling sound on Pulseaudio for Ubuntu 21.04 Status in pulseaudio package in Ubuntu: New Bug description: While playing back any sounds, a certain crackling sound (static) will play with a fixed delay of the sound being played. The amount and volume of the static will depend on the sound/music that is being played, and this only starts occurring after a somewhat long time (30 minutes or more). What is interesting to see is that while playing back music from Spotify (Snap) the static will only start after a second or so, but when playing YouTube videos on Firefox, it will be immediate and output that static while the video is playing. I've added two sound recordings, one while playing back a song from Spotify and the other while playing a song from YouTube. This issue goes away when restarting the PulseAudio service, but it comes back after a random amount of time. 1) Description: Ubuntu 21.04 Release: 21.04 2) pulseaudio: Installed: 1:14.2-1ubuntu1 Candidate: 1:14.2-1ubuntu1 Version table: 1:14.2-1ubuntu1.1 1 (phased 10%) 500 http://br.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages *** 1:14.2-1ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: pulseaudio 1:14.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: matheus 18662 F pulseaudio /dev/snd/controlC2: matheus 18662 F pulseaudio /dev/snd/controlC0: matheus 18662 F pulseaudio /dev/snd/pcmC0D8p: matheus 18662 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 14 16:58:43 2021 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2021-05-03 (41 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: LANG=pt_BR.UTF-8 LANGUAGE=pt_BR:pt:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: Default string dmi.board.name: PRIME B450-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd03/11/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1931902/+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 1931870] Re: System freezes several times per week, sometimes more than once per day
The open source 'nouveau' driver you are using is known to be unstable. Please use the 'Additional Drivers' app to install the official Nvidia driver. ** Tags added: nouveau ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - System freezes several times per week, sometimes more than once per day + [nouveau] System freezes several times per week, sometimes more than once per day -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1931870 Title: [nouveau] System freezes several times per week, sometimes more than once per day Status in linux package in Ubuntu: New Bug description: ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-55.62-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Mon Jun 14 15:18:03 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:2297] InstallationDate: Installed on 2021-01-15 (150 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20QQS0KL13 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-55-generic root=UUID=35cef147-e021-4bdd-b8db-31a3192c8a6a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2020 dmi.bios.release: 1.23 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET38W (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QQS0KL13 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: ZF211710 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN2NET38W(1.23):bd06/04/2020:br1.23:efr1.14:svnLENOVO:pn20QQS0KL13:pvrThinkPadP53:rvnLENOVO:rn20QQS0KL13:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P53 dmi.product.name: 20QQS0KL13 dmi.product.sku: LENOVO_MT_20QQ_BU_Think_FM_ThinkPad P53 dmi.product.version: ThinkPad P53 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931870/+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 1931807] Re: unable to install intel hd graphic on ubuntu
There is nothing to install. Intel drivers are built-in and yours appear to be working properly. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1931807 Title: unable to install intel hd graphic on ubuntu Status in Ubuntu: Invalid Bug description: kindly fix the issue ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 13 20:34:30 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics [8086:1606] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics [103c:80c1] InstallationDate: Installed on 2021-02-20 (112 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:57d6 Realtek Semiconductor Corp. HP Truevision HD Bus 001 Device 002: ID 0bda:b006 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=bf96a269-335b-44b8-ad20-bbdd984dd05b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.release: 15.38 dmi.bios.vendor: Insyde dmi.bios.version: F.26 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C1 dmi.board.vendor: HP dmi.board.version: 96.51 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 96.51 dmi.modalias: dmi:bvnInsyde:bvrF.26:bd03/06/2018:br15.38:efr96.51:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn80C1:rvr96.51:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: P4Y39PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1931807/+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 1931741] Re: Second Display Never Supports Proper Resolution
*** This bug is a duplicate of bug 1901470 *** https://bugs.launchpad.net/bugs/1901470 I've decoded your monitor's EDID data (see attached) and it only supports the detailed modes 3440x1440 or 2560x1080. Not "2560x1440", although you can fake it with xrandr as you say. So if that's the only issue then this bug is invalid. If you find 3440x1440 or 2560x1080 are missing by default however, then this is kernel bug 1901470. ** Attachment added: "edid-decoded.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1931741/+attachment/5505924/+files/edid-decoded.txt ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1931741 Title: Second Display Never Supports Proper Resolution Status in Ubuntu: New Bug description: I have tried cables, drivers, upgrades --no matter what I do I cannot get Ubuntu to recognize that my 32" UHD LG display supports 2560x1440. I can work around it with `cvt` and `xrandr` but this is tedious and is not saved across sessions, and xorg.conf is no longer a possibility (bricks the system). ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 11 12:06:05 2021 DistUpgraded: 2021-06-11 10:51:25,279 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc5] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09a4] InstallationDate: Installed on 2021-03-08 (95 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Dell Inc. OptiPlex 7080 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to hirsute on 2021-06-11 (0 days ago) dmi.bios.date: 12/24/2020 dmi.bios.release: 1.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0J37VM dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd12/24/2020:br1.3:svnDellInc.:pnOptiPlex7080:pvr:rvnDellInc.:rn0J37VM:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7080 dmi.product.sku: 09A4 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1931741/+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 1931704] Re: The settings show that bluetooth is turned off even after I turn it on
*** This bug is a duplicate of bug 1926062 *** https://bugs.launchpad.net/bugs/1926062 ** This bug has been marked a duplicate of bug 1926062 [hirsute/impish] Can't turn bluetooth on again after turning it off -- 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/1931704 Title: The settings show that bluetooth is turned off even after I turn it on Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Description: Ubuntu 21.04 Release: 21.04 $apt-cache policy bluetooth bluetooth: Installed: 5.56-0ubuntu4 Candidate: 5.56-0ubuntu4 Version table: *** 5.56-0ubuntu4 500 500 http://in.archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages 500 http://in.archive.ubuntu.com/ubuntu hirsute/universe i386 Packages 100 /var/lib/dpkg/status The settings show that the bluetooth is turned off even after I turn it on, and the devices are not detected. I am attaching a screenshot. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-control-center 1:3.38.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Budgie:GNOME Date: Fri Jun 11 17:24:20 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2021-04-24 (47 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to hirsute on 2021-06-06 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1931704/+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 1931756] Re: [XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem
So far the 20.04 uses 5.8.0-generic kernel, it is not easy to backport soundwire code to 5.8 kernel. And the 20.04 is going to replace 5.8 kernel with 5.11.0-generic kernel soon, when this happens, the LTS will support your machine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1931756 Title: [XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem Status in alsa-driver package in Ubuntu: Fix Released Bug description: I have tried modifications to DKMS, modprobe.d, pulseaudio and alsa but all were no sound. The modprobe,d modifications did result in the "dummy" message being replaced by a device. This was done 2 installs ago,sorry. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.10.0-051000-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pbea 1894 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Fri Jun 11 23:34:27 2021 InstallationDate: Installed on 2021-06-11 (0 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2021 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.2 dmi.board.name: 0P25F6 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.2:bd03/04/2021:br1.7:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0P25F6:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1931756/+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 1930359] Re: gdm fails to start in a VMware Horizon VDI environment with latest mutter 3.36.9-0ubuntu0.20.04.1 in focal-updates
** Summary changed: - gdm fails to start with latest mutter 3.36.9-0ubuntu0.20.04.1 in focal-updates + gdm fails to start in a VMware Horizon VDI environment with latest mutter 3.36.9-0ubuntu0.20.04.1 in focal-updates -- 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/1930359 Title: gdm fails to start in a VMware Horizon VDI environment with latest mutter 3.36.9-0ubuntu0.20.04.1 in focal-updates Status in mutter package in Ubuntu: New Status in mutter source package in Focal: In Progress Bug description: [Impact] gdm fails to start in a VMware Horizon VDI environment, with Nvidia GRID gpus passed into the VDIs. Downgrading mutter from 3.36.9-0ubuntu0.20.04.1 to 3.36.1-3ubuntu3 in -release fixes the issue, and the issue does not occur with 3.36.7+git20201123-0.20.04.1. Currently looking into what landed in bug 1919143 and bug 1905825. [Testcase] [Where problems can occur] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1930359/+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 1930550] Re: usb sound devices crackling
I'm not familiar with mpd. It sounds like maybe you should seek advice from the developers by opening an upstream issue at: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues or https://gitlab.freedesktop.org/pipewire/pipewire/-/issues -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1930550 Title: usb sound devices crackling Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrade from 20.04 to 21.04 all 3 my usb sound devices start crackling, i have xduoo05plus, audeze mobius, audient id4. I also tried to modify default-fragments = 5 default-fragment-size-msec = 2 to different sugested on stackoverflow articles setting Also this is in my config: high-priority = yes nice-level = -11 realtime-scheduling = yes realtime-priority = 5 I even tried to switch to pipewire, but it still the same. Possible issue in alsa kernel drivers for usb interface, submitting bug to pulse as it default in ubuntu. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: pulseaudio 1:14.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Jun 2 11:11:55 2021 InstallationDate: Installed on 2019-08-13 (658 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to hirsute on 2021-05-16 (16 days ago) dmi.bios.date: 08/12/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. 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.:bvrF11:bd08/12/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnB85-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85-HD3:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: B85-HD3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.system.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2021-05-18T13:33:15.787174 mtime.conffile..etc.pulse.system.pa: 2021-05-18T11:20:40.860787 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1930550/+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
