[Desktop-packages] [Bug 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
From bug 1947739 comment #53: > test mutter 3.36.0-0ubuntu0.20.04.2 from the focal-proposed channel on > the target machine for 10 times, can't reproduce this issue. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. Status in Mutter: Unknown Status in OEM Priority Project: In Progress Status in mutter package in Ubuntu: In Progress Status in mutter source package in Focal: Fix Committed Status in mutter source package in Hirsute: Fix Committed Status in mutter source package in Impish: Fix Committed Bug description: [Impact] * Gdm crashed and user need to be an expert to know how to work around, or need to reboot to fix. * OEM projects got certain SKU that can reliably reproduce this issue. * A merged patch in upstream fix the race condition. [Test Plan] * Use the SKU that can reliably reproduce this issue. * Do a cold boot, and wait for 5 mins. The monitor should turned-black but showing the Machine Vendor logo that was previously displayed by plythmouth. * Try to dog-food the deb from the proposed channel and make sure all input events still properly propagate. [Where problems could occur] * If the patch is not properly working as expected, per the file this patch touch, the user desktop session could stop responding to mouse, keyboard, and touch screen input. [Other Info] * Can't think of any for now. This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. (also observed that the touchscreen USB device drop of a USB bus on the target machine) Note: this bug seems to be timing sensitive. I got an OEM project machine that can reproduce this issue (reproducible on several machines with the same HW design). The machine is using ADL CPU, which needs a patched 5.14 kernel. So I can't reproduce this on impish. With the backported mutter, I verified an upstream patch seems to fix this issue. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #10 0x7f447c3cf3a8 in wl_closure_invoke (closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=, target@entry=0x56437639f000, opcode=opcode@entry=0, data=) at ../src/connection.c:1018 #11 0x7f447c3cbc48 in dispatch_event (display=display@entry=0x56437639f000, queue=) at ../src/wayland-client.c:1445 #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, display=0x56437639f000) at ../src/wayland-client.c:1584 #13 wl_display_dispatch_queue_pending (display=0x56437639f000, queue=0x56437639f0d0) at ../src/wayland-client.c:1833 #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896 #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at ../../../../../hw/xwayland/xwayland.c:957 #16 0x564374401c61 in ospoll_wait (ospoll=0x56437638f4a0, timeout=) at ../../../../os/ospoll.c:657 #17 0x5643743faa23 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:208 #18 0x5643743ca4a7 in Dispatch () at ../../../../include/list.h:220 #19 0x5643743ce794 in dix_main (argc=16,
[Desktop-packages] [Bug 1845362] Re: gnome-font-viewer crashed with signal 5 in _XEventsQueued()
I know that it was set to rls-ii-notfixing but I just want to tell that it appears in Jammy as well (build 20211104). I'm including this bug in my test result with the "Passed" flag. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/1845362 Title: gnome-font-viewer crashed with signal 5 in _XEventsQueued() Status in gnome-font-viewer package in Ubuntu: Confirmed Status in gnome-font-viewer package in Debian: New Bug description: Reproducible crash (tested on Ubuntu and Xubuntu) or freezing of application during ISO testing of a live-session. Application will crash if there is an attempt to close it or scroll through fonts. On one occasion my laptop was rendered unusable when Firefox was launched while trying to report the crash to Launchpad. After the bug report has been sent gnome-font-viewer will freeze when automatically restarted. No fonts are displayed. Work around --- gnome-font-viewer appears to start correctly when started from the command line of my Ubuntu 20.04 installation. Then subsequent attempts to start the program succeed when started from the dock or the Application Overview. I have found that this work around wasn't necessary when using Xubuntu 20.04. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-font-viewer 3.34.0-1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.416 CurrentDesktop: XFCE Date: Wed Sep 25 17:34:17 2019 ExecutablePath: /usr/bin/gnome-font-viewer LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190925) ProcCmdline: gnome-font-viewer ProcEnviron: LANGUAGE=en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gnome-font-viewer StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6 XPending () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-font-viewer crashed with signal 5 in _XEventsQueued() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1845362/+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 1939732] Re: report availability of Ubuntu Advantage ESM services on unattached machines
** Also affects: software-properties (Ubuntu Bionic) Importance: Undecided Status: New -- 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/1939732 Title: report availability of Ubuntu Advantage ESM services on unattached machines Status in software-properties package in Ubuntu: Fix Committed Status in software-properties source package in Bionic: New Status in software-properties source package in Focal: Fix Committed Status in software-properties source package in Hirsute: Fix Committed Status in software-properties source package in Impish: Fix Committed Bug description: [Impact] * Error messages emitted to software-properties-gtk console "[Errno 2] No such file or directory: '/var/lib/ubuntu-advantage/status.json'" due to incorrect expectation that status.json file is written when non-root runs `ua status` * This logic results in multiple `ua status` calls which each result in a network-egress to https://contracts.canonical.com on unattached machines which could result in delays in rendering the GTK dialogs while awaiting a response. [Test Case] 1. Install latest version of software-properties-gtk from -proposed cat > setup_proposed.sh
[Desktop-packages] [Bug 1761382] Re: Unable to connect to ibus: Could not connect: Connection refused
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1761382 Title: Unable to connect to ibus: Could not connect: Connection refused Status in gnome-shell package in Ubuntu: Expired Status in ibus package in Ubuntu: Expired Bug description: Get this logged: oem@ubuntu:~$ journalctl -b | grep ibus dbus-daemon[1074]: [session uid=120 pid=1074] Activating service name='org.freedesktop.portal.IBus' requested by ':1.18' (uid=120 pid=1135 comm="ibus-daemon --xim --panel disable " label="unconfined") gnome-shell[1084]: Unable to connect to ibus: Could not connect: Connection refused /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment: setting QT_IM_MODULE=ibus /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment: setting XMODIFIERS=@im=ibus /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment: setting GTK_IM_MODULE=ibus dbus-daemon[1293]: [session uid=1000 pid=1293] Activating service name='org.freedesktop.portal.IBus' requested by ':1.27' (uid=1000 pid=1458 comm="ibus-daemon --xim --panel disable " label="unconfined") gnome-shell[1435]: Unable to connect to ibus: Could not connect: Connection refused ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 5 07:43:59 2018 DisplayManager: gdm3 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1761382/+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 1761382] Re: Unable to connect to ibus: Could not connect: Connection refused
[Expired for ibus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ibus (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1761382 Title: Unable to connect to ibus: Could not connect: Connection refused Status in gnome-shell package in Ubuntu: Expired Status in ibus package in Ubuntu: Expired Bug description: Get this logged: oem@ubuntu:~$ journalctl -b | grep ibus dbus-daemon[1074]: [session uid=120 pid=1074] Activating service name='org.freedesktop.portal.IBus' requested by ':1.18' (uid=120 pid=1135 comm="ibus-daemon --xim --panel disable " label="unconfined") gnome-shell[1084]: Unable to connect to ibus: Could not connect: Connection refused /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment: setting QT_IM_MODULE=ibus /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment: setting XMODIFIERS=@im=ibus /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment: setting GTK_IM_MODULE=ibus dbus-daemon[1293]: [session uid=1000 pid=1293] Activating service name='org.freedesktop.portal.IBus' requested by ':1.27' (uid=1000 pid=1458 comm="ibus-daemon --xim --panel disable " label="unconfined") gnome-shell[1435]: Unable to connect to ibus: Could not connect: Connection refused ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 5 07:43:59 2018 DisplayManager: gdm3 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1761382/+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 1949845] Re: Toggle enable/disable dock autohide gives glitches
If the autohide setting is causing the gnome-control-center window to move or resize (and then "glitch") then this could be bug 1947149. -- 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/1949845 Title: Toggle enable/disable dock autohide gives glitches Status in gnome-control-center package in Ubuntu: New Bug description: Ubuntu 22.04 development branch @ 4/11/2021 with kernel 5.13.0-19-generic (wayland) When opening gnome-control-center and toggle enable/disable the dock to autohide a few times, the gnome-control-center window gives glitches/flashes this is not on random, it can be reproduced ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:40.0-1ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Nov 4 16:47:34 2021 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1949845/+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 1949924] Re: yelp crashes in wayland session
Downgrading yelp and libyelp0 to the impish version does not help, so it may well be a bug in some other package. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1949924 Title: yelp crashes in wayland session Status in yelp package in Ubuntu: New Bug description: $ yelp yelp: ../src/wayland-thread.c:87: wlExternalApiLock: Assertion `!"failed to lock pthread mutex"' failed. Aborted (core dumped) This does not happen in Debian testing, and it also works as expected in an Ubuntu on Xorg session. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: yelp 41.1-1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Nov 5 02:51:43 2021 InstallationDate: Installed on 2019-11-10 (725 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: yelp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1949924/+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 1947149] Re: Dock auto-hide off but hidden on screen unlock
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: In Progress => Fix Committed ** Also affects: gnome-shell-extension-dashtodock (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-dashtodock (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: gnome-shell-extension-dashtodock (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell-extension-dashtodock (Ubuntu) Status: New => Fix Committed ** Tags added: fixed-in-72 fixed-upstream -- 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/1947149 Title: Dock auto-hide off but hidden on screen unlock Status in gnome-shell-extension-dashtodock package in Ubuntu: Fix Committed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Committed Bug description: When the dock is set to "Auto-hide the Dock" = Off, the dock will un- hide when logging on. Both on boot and after locking the user. This causes any open full-screen windows to move and resize as needed. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 21.10 Release: 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center gnome-shell-extension-ubuntu-dock: Installed: 70~ubuntu3 Candidate: 70~ubuntu3 Version table: *** 70~ubuntu3 500 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish/main i386 Packages 100 /var/lib/dpkg/status 3) What you expected to happen The dock to start displayed (un-hidden) as per the settings. And not move. 4) What happened instead The dock appears from the left, as if hidden. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1947149/+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 1949924] [NEW] yelp crashes in wayland session
Public bug reported: $ yelp yelp: ../src/wayland-thread.c:87: wlExternalApiLock: Assertion `!"failed to lock pthread mutex"' failed. Aborted (core dumped) This does not happen in Debian testing, and it also works as expected in an Ubuntu on Xorg session. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: yelp 41.1-1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Nov 5 02:51:43 2021 InstallationDate: Installed on 2019-11-10 (725 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: yelp UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: yelp (Ubuntu) Importance: High Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1949924 Title: yelp crashes in wayland session Status in yelp package in Ubuntu: New Bug description: $ yelp yelp: ../src/wayland-thread.c:87: wlExternalApiLock: Assertion `!"failed to lock pthread mutex"' failed. Aborted (core dumped) This does not happen in Debian testing, and it also works as expected in an Ubuntu on Xorg session. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: yelp 41.1-1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Nov 5 02:51:43 2021 InstallationDate: Installed on 2019-11-10 (725 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: yelp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1949924/+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 1821415] Re: pkexec fails in a non-graphical environment
I am still having this bug. apport-cli --version 2.20.11 pkexec --version pkexec version 0.105 user2@computer:~/cm$ pkexec bash AUTHENTICATING FOR org.freedesktop.policykit.exec === Authentication is needed to run `/usr/bin/bash' as the super user Multiple identities can be used for authentication: 1. Administrator,,, (admin) 2. ,,, (user1) 3. ,,, (user2) Choose identity to authenticate as (1-3): 3 Password: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie AUTHENTICATION FAILED === Error executing command as another user: Not authorized This incident has been reported. user2@computer:~/cm$ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1821415 Title: pkexec fails in a non-graphical environment Status in PolicyKit: New Status in apport package in Ubuntu: Fix Released Status in policykit-1 package in Ubuntu: Won't Fix Status in apport source package in Focal: Fix Released Status in policykit-1 source package in Focal: Won't Fix Status in apport source package in Groovy: Fix Released Status in policykit-1 source package in Groovy: Won't Fix Bug description: [Impact] The plymouth apport source package hooks wants to gather log files as the root user and apport provides a policy kit policy for collecting that information. This works fine in a graphical environment but not in a non-graphical one. [Test Case] 1) ssh into an Ubuntu Desktop install of Ubuntu 20.04 LTS or Ubuntu 20.10 2) sudo touch /var/log/plymouth-debug.log 3) ubuntu@disco:~$ ubuntu-bug plymouth *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .. AUTHENTICATING FOR com.ubuntu.apport.root-info === Authentication is required to collect system information for this problem report Authenticating as: Ubuntu (ubuntu) Password: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie AUTHENTICATION FAILED === Error executing command as another user: Not authorized This incident has been reported. With the version of apport from -proposed you will not see the "AUTHENTICATION FAILED" error and the plymouth-debug.log file will be collected. [Where Problems Could Occur] It's possible that the spawned pkttyagent process does not get cleaned up properly and could be left running. When testing the SRU we should confirm it is not still running. To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1821415/+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 1949909] [NEW] bluetooth crashes on resume from suspend
Public bug reported: Crash on resume from suspend. The following messages appear and the computer stops responding: ``` [ 26.227264] Bluetooth: hci0: Reading supported features failed (-16) [ 26.228275] Bluetooth: hci0: Setting Intel telemetry ddc write event mask failed (-95) ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez (not installed) ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 4 22:50:23 2021 InstallationDate: Installed on 2021-09-16 (49 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1949909 Title: bluetooth crashes on resume from suspend Status in bluez package in Ubuntu: New Bug description: Crash on resume from suspend. The following messages appear and the computer stops responding: ``` [ 26.227264] Bluetooth: hci0: Reading supported features failed (-16) [ 26.228275] Bluetooth: hci0: Setting Intel telemetry ddc write event mask failed (-95) ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez (not installed) ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 4 22:50:23 2021 InstallationDate: Installed on 2021-09-16 (49 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1949909/+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 1946042] Re: Ubuntu Dock changes look/breaks in High Contrast
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => Won't Fix -- 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/1946042 Title: Ubuntu Dock changes look/breaks in High Contrast Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Won't Fix Status in yaru-theme package in Ubuntu: Fix Committed Bug description: When switching to High Contrast on Ubuntu Impish, the Ubuntu Dock detaches from the margin, changes look and expands. The expansion pushes the "Show Applications" button half-way outside the shell/display. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu1 Uname: Linux 5.14.9-xanmod2 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 5 01:49:19 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-04-03 (184 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210402) RelatedPackageVersions: mutter-common 40.5-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1946042/+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 1947445] Re: Click actions "previews" and "minimize-or-previews" are broken
Sorry Pepijn, the code of the dock is managed via github at https://github.com/micheleg/dash-to-dock/tree/ubuntu-dock Should do a PR there, but I will handle it in next upload. Thanks! -- 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/1947445 Title: Click actions "previews" and "minimize-or-previews" are broken Status in Dash to dock: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Committed Bug description: Since upgrading to Ubuntu 21.10 the "previews" and "minimize-or- previews" options no longer work as expected. For "previews": No previews are shown when clicking on the app icon. For "minimize-or-previews": When multiple windows of the same application are open and I click on the app icon, no previews are shown anymore. Schema: org.gnome.shell.extensions.dash-to-dock Name: click-action Value: "minimize-or-previews" Value: "previews" Description: Ubuntu 21.10 Release: 21.10 gnome-shell-extension-ubuntu-dock: Installed: 70~ubuntu3 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 16 11:32:51 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-21 (1090 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to impish on 2021-10-14 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1947445/+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 1887235] Re: System hangs, syslog filled with: Object St.BoxLayout (...), has been already deallocated - impossible to access it. Called from ubuntu-d...@ubuntu.com/docking.js:
vanvugt:fix-lp1947149 -- 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/1887235 Title: System hangs, syslog filled with: Object St.BoxLayout (...), has been already deallocated - impossible to access it. Called from ubuntu- d...@ubuntu.com/docking.js:184 from tweener.js:322 Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Description: Ubuntu 18.04.4 LTS Release: 18.04 I have been having incidents where the system suddenly hangs and nothing except a restart works. The only thing that I can see in logs are the following: Syslog filled up with repeats of: ``` Jul 11 20:27:18 gnome-shell[3317]: Object St.BoxLayout (0x55b1d8322450), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: == Stack trace for context 0x55b1d37ee320 == Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #0 0x7fff7db4aa50 b /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:184 (0x7f523f3bfab0 @ 35) Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #1 0x7fff7db4b480 b resource:///org/gnome/gjs/modules/tweener/tweener.js:322 (0x7f52845d2bc0 @ 1462) Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #2 0x7fff7db4b530 b resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7f52845d2c48 @ 100) Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #3 0x7fff7db4b5c0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7f52845d2cd0 @ 10) Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #4 0x7fff7db4b6b0 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f52845d2230 @ 386) Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #5 0x7fff7db4b760 b resource:///org/gnome/shell/ui/tweener.js:244 (0x7f52845cf808 @ 159) Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #6 0x7fff7db4b7c0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f52845b5de0 @ 71) Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #7 0x7fff7db4b860 b resource:///org/gnome/shell/ui/tweener.js:219 (0x7f52845cf780 @ 15) Jul 11 20:27:18 gnome-shell[3317]: clutter_actor_queue_relayout: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 11 20:27:18 gnome-shell[3317]: Object St.BoxLayout (0x55b1d8322450), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: == Stack trace for context 0x55b1d37ee320 == Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #0 0x7fff7db4aa50 b /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:184 (0x7f523f3bfab0 @ 35) Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #1 0x7fff7db4b480 b resource:///org/gnome/gjs/modules/tweener/tweener.js:322 (0x7f52845d2bc0 @ 1462) Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #2 0x7fff7db4b530 b resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7f52845d2c48 @ 100) Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #3 0x7fff7db4b5c0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7f52845d2cd0 @ 10) Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #4 0x7fff7db4b6b0 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f52845d2230 @ 386) Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #5 0x7fff7db4b760 b resource:///org/gnome/shell/ui/tweener.js:244 (0x7f52845cf808 @ 159) Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #6 0x7fff7db4b7c0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f52845b5de0 @ 71) Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #7 0x7fff7db4b860 b resource:///org/gnome/shell/ui/tweener.js:219 (0x7f52845cf780 @ 15) Jul 11 20:27:18 gnome-shell[3317]: clutter_actor_queue_relayout: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 11 20:27:18 gnome-shell[3317]: Object St.BoxLayout (0x55b1d8322450), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 11 20:27:18 gnome-shell[3317]: clutter_actor_queue_relayout: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: == Stack trace for context 0x55b1d37ee320 == Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #0 0x7fff7db4aa50 b /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:184 (0x7f523f3bfab0 @ 35) Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #1 0x7fff7db4b480 b resource:///org/gnome/gjs/modules/tweener/tweener.js:322 (0x7f52845d2bc0 @ 1462) Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #2 0x7fff7db4b530 b
[Desktop-packages] [Bug 1914806] Re: (EE) client bug: timer event3 debounce short: scheduled expiry is in the past (-28ms), your system is too slow
*** This bug is a duplicate of bug 1870597 *** https://bugs.launchpad.net/bugs/1870597 I'm use KDE and obtain the bug. "[635.832] (EE) client bug: timer event17 debounce: scheduled expiry is in the past (-8ms), your system is too slow [823.399] (EE) client bug: timer event17 debounce short: scheduled expiry is in the past (-16ms), your system is too slow" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1914806 Title: (EE) client bug: timer event3 debounce short: scheduled expiry is in the past (-28ms), your system is too slow Status in libinput package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Bug description: Feb 5 13:17:35 H61N-USB3 /usr/lib/gdm3/gdm-x-session[4812]: (EE) client bug: timer event3 debounce: scheduled expiry is in the past (-15ms), your system is too slow Feb 5 13:17:35 H61N-USB3 /usr/lib/gdm3/gdm-x-session[4812]: (EE) client bug: timer event3 debounce short: scheduled expiry is in the past (-28ms), your system is too slow Feb 5 13:17:46 H61N-USB3 /usr/lib/gdm3/gdm-x-session[4812]: (EE) client bug: timer event3 debounce short: scheduled expiry is in the past (-4ms), your system is too slow ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.7+git20201123-0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Feb 5 13:19:11 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-26 (2355 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: Upgraded to focal on 2020-09-30 (128 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1914806/+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 1574341] Re: [Asus T300 CHI] Synaptics Touch Digitizer V04 - no multitouch
** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1574341/+attachment/5538304/+files/Xorg.0.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xinput in Ubuntu. https://bugs.launchpad.net/bugs/1574341 Title: [Asus T300 CHI] Synaptics Touch Digitizer V04 - no multitouch Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in xinput package in Ubuntu: Triaged Bug description: This is a related but separate issue to bug #1480673 "Asus T300 CHI bluetooth Touchpad is recognized incorrectly". Affecting this digitizer is also bug #1574028 "Asus T300 CHI: touchscreen digitiser missing at boot". Using 16.04 amd64 Ubuntu (unity). In this case the USB-attached "Synaptics Touch Digitizer V04" fails to provide any multitouch functionality. 'evtest' shows multitouch events happening. $ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 06cb:11ef Synaptics, Inc. Bus 001 Device 005: ID 04f2:b3d5 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ~$ xinput --list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ASUS T300CHI DOCKING id=9[slave pointer (2)] ⎜ ↳ SYNAPTICS Synaptics Touch Digitizer V04 id=11 [slave pointer (2)] ⎜ ↳ SYNAPTICS Synaptics Touch Digitizer V04 Pen id=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Sleep Button id=8[slave keyboard (3)] ↳ USB2.0 HD UVC WebCam id=10 [slave keyboard (3)] ↳ Asus WMI hotkeys id=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)] ↳ ASUS T300CHI DOCKING id=15 [slave keyboard (3)] $ ll /sys/bus/hid/drivers/hid-multitouch/ total 0 drwxr-xr-x 2 root root0 Apr 24 18:12 ./ drwxr-xr-x 4 root root0 Apr 24 18:12 ../ lrwxrwxrwx 1 root root0 Apr 24 18:12 0003:06CB:11EF.0003 -> ../../../../devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/0003:06CB:11EF.0003/ --w--- 1 root root 4096 Apr 24 18:12 bind lrwxrwxrwx 1 root root0 Apr 24 18:12 module -> ../../../../module/hid_multitouch/ --w--- 1 root root 4096 Apr 24 18:12 new_id --w--- 1 root root 4096 Apr 24 18:12 uevent --w--- 1 root root 4096 Apr 24 18:12 unbind To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1574341/+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 1574341] Re: [Asus T300 CHI] Synaptics Touch Digitizer V04 - no multitouch
Although most other issues are solved there is still no multitouch for
this device with kernel v5.15 and xserver-xorg 1.20.13-1ubuntu1 using
Kubuntu 21.10.
# xinput
⎡ Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)]
⎜ ↳ Asus TouchPad id=10 [slave pointer (2)]
⎜ ↳ SYNAPTICS Synaptics Touch Digitizer V04 Mouse id=15 [slave pointer
(2)]
⎜ ↳ SYNAPTICS Synaptics Touch Digitizer V04 id=16 [slave pointer (2)]
⎜ ↳ BT5.0 Mouse id=20 [slave pointer (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave keyboard (3)]
↳ Power Button id=6[slave keyboard (3)]
↳ Asus Wireless Radio Control id=7[slave keyboard (3)]
↳ Video Bus id=8[slave keyboard (3)]
↳ Sleep Button id=9[slave keyboard (3)]
↳ ASUS T300CHI DOCKING id=11 [slave keyboard (3)]
↳ ASUS T300CHI DOCKING id=12 [slave keyboard (3)]
↳ ASUS T300CHI DOCKING id=13 [slave keyboard (3)]
↳ USB2.0 HD UVC WebCam: USB2.0 HD id=14 [slave keyboard (3)]
↳ SYNAPTICS Synaptics Touch Digitizer V04 Stylusid=17 [slave
keyboard (3)]
↳ Asus WMI hotkeys id=18 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=19 [slave keyboard (3)]
# for id in {15..17}; do xinput --list $id; done
SYNAPTICS Synaptics Touch Digitizer V04 Mouse id=15 [slave pointer (2)]
Reporting 7 classes:
Class originated from: 15. Type: XIButtonClass
Buttons supported: 7
Button labels: "Button Left" "Button Middle" "Button Right"
"Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz
Wheel Right"
Button state:
Class originated from: 15. Type: XIValuatorClass
Detail for Valuator 0:
Label: Rel X
Range: -1.00 - -1.00
Resolution: 0 units/m
Mode: relative
Class originated from: 15. Type: XIValuatorClass
Detail for Valuator 1:
Label: Rel Y
Range: -1.00 - -1.00
Resolution: 0 units/m
Mode: relative
Class originated from: 15. Type: XIValuatorClass
Detail for Valuator 2:
Label: Rel Horiz Scroll
Range: -1.00 - -1.00
Resolution: 0 units/m
Mode: relative
Class originated from: 15. Type: XIValuatorClass
Detail for Valuator 3:
Label: Rel Vert Scroll
Range: -1.00 - -1.00
Resolution: 0 units/m
Mode: relative
Class originated from: 15. Type: XIScrollClass
Scroll info for Valuator 2
type: 2 (horizontal)
increment: 15.00
flags: 0x0
Class originated from: 15. Type: XIScrollClass
Scroll info for Valuator 3
type: 1 (vertical)
increment: 15.00
flags: 0x0
SYNAPTICS Synaptics Touch Digitizer V04 id=16 [slave pointer (2)]
Reporting 6 classes:
Class originated from: 16. Type: XIButtonClass
Buttons supported: 7
Button labels: "Button Left" "Button Middle" "Button Right"
"Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz
Wheel Right"
Button state:
Class originated from: 16. Type: XIValuatorClass
Detail for Valuator 0:
Label: Abs MT Position X
Range: 0.00 - 65535.00
Resolution: 0 units/m
Mode: absolute
Current value: 44291.812165
Class originated from: 16. Type: XIValuatorClass
Detail for Valuator 1:
Label: Abs MT Position Y
Range: 0.00 - 65535.00
Resolution: 0 units/m
Mode: absolute
Current value: 39378.849306
Class originated from: 16. Type: XIValuatorClass
Detail for Valuator 2:
Label: Rel Horiz Scroll
Range: -1.00 - -1.00
Resolution: 0 units/m
Mode: relative
Class originated from: 16. Type: XIValuatorClass
Detail for Valuator 3:
[Desktop-packages] [Bug 1948933] Re: [SRU] libreoffice 7.1.7 for hirsute
Hello Rico, or anyone else affected, Accepted libreoffice into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libreoffice/1:7.1.7-0ubuntu0.21.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libreoffice (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-hirsute -- 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/1948933 Title: [SRU] libreoffice 7.1.7 for hirsute Status in libreoffice package in Ubuntu: Triaged Status in libreoffice source package in Hirsute: Fix Committed Bug description: [Impact] * LibreOffice 7.1.7 is in its seventh bugfix release of the 7.1 line: https://wiki.documentfoundation.org/ReleasePlan/7.1#7.1.7_release * Version 7.1.6 is currently released in hirsute. For a list of fixed bugs compared to 7.1.6 see the list of bugs fixed in the release candidates of 7.1.7 (that's a total of 27 bugs): https://wiki.documentfoundation.org/Releases/7.1.7/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.1.7/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_71/1460/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-ricotz-ppa/hirsute/amd64/libr/libreoffice/20211028_194503_1ee54@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-ricotz-ppa/hirsute/arm64/libr/libreoffice/20211028_113740_b763e@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-ricotz-ppa/hirsute/armhf/libr/libreoffice/20211029_170024_1bc17@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-ricotz-ppa/hirsute/ppc64el/libr/libreoffice/20211028_225613_de9da@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-ricotz-ppa/hirsute/s390x/libr/libreoffice/20211028_104330_62f27@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 27 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1948933/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net
[Desktop-packages] [Bug 1949605] Re: Backport Thunderbird 91 to 20.04 LTS and 18.04 LTS
Ubuntu packages do things a bit differently: - cbindgen is vendored in the source tarball (currently at version 0.19) - builds and uses the bundled nspr, not the system one - builds and uses the bundled nss, not the system one - the nodejs requirement is 10.23.1; a newer version was backported to bionic and focal under the name nodejs-mozilla -- 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/1949605 Title: Backport Thunderbird 91 to 20.04 LTS and 18.04 LTS Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Bionic: Confirmed Status in thunderbird source package in Focal: Confirmed Status in thunderbird source package in Hirsute: Confirmed Bug description: Similarly to bug #1895643, which was about upgrading thunderbird from 68 to 78 in all supported Ubuntu releases, this bug is to track the update from thunderbird 78 to 91 in hirsute, focal and bionic. The rationale is that series 78 will soon be out of support (the last release, 78.14.0, was made public on September 7, 2021). Thunderbird follows the Firefox ESR release cycle, and the next/current series is 91 (already available in impish and jammy). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1949605/+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 1949845] Re: Toggle enable/disable dock autohide gives glitches
Journal logs when toggle enable/disable autohide: nov 04 16:41:07 R00TB00K systemd[914]: Started Application launched by gnome-shell. nov 04 16:41:23 R00TB00K gnome-shell[2532]: DING: GNOME nautilus 40.2 nov 04 16:41:24 R00TB00K dbus-daemon[2444]: [session uid=1000 pid=2444] Activating service name='org.gnome.ArchiveManager1' requested by ':1.337' (uid=1000 pid=1693505 comm="gjs /usr/share/gnome-shell/extensions/ding@rasters" label="unconfined") nov 04 16:41:24 R00TB00K dbus-daemon[2444]: [session uid=1000 pid=2444] Successfully activated service 'org.gnome.ArchiveManager1' nov 04 16:41:25 R00TB00K gnome-shell[2532]: DING: GNOME nautilus 40.2 nov 04 16:41:26 R00TB00K gnome-shell[2532]: DING: GNOME nautilus 40.2 nov 04 16:41:27 R00TB00K gnome-shell[2532]: DING: GNOME nautilus 40.2 nov 04 16:41:30 R00TB00K gnome-shell[2532]: DING: GNOME nautilus 40.2 nov 04 16:41:32 R00TB00K gnome-shell[2532]: DING: GNOME nautilus 40.2 nov 04 16:41:40 R00TB00K gnome-shell[2532]: DING: GNOME nautilus 40.2 nov 04 16:41:40 R00TB00K dbus-daemon[2444]: [session uid=1000 pid=2444] Activating service name='org.gnome.ArchiveManager1' requested by ':1.360' (uid=1000 pid=1694302 comm="gjs /usr/share/gnome-shell/extensions/ding@rasters" label="unconfined") nov 04 16:41:40 R00TB00K dbus-daemon[2444]: [session uid=1000 pid=2444] Successfully activated service 'org.gnome.ArchiveManager1' nov 04 16:41:41 R00TB00K gnome-shell[2532]: DING: GNOME nautilus 40.2 nov 04 16:41:43 R00TB00K gnome-shell[2532]: DING: GNOME nautilus 40.2 nov 04 16:41:44 R00TB00K gnome-shell[2532]: DING: GNOME nautilus 40.2 nov 04 16:42:04 R00TB00K gnome-shell[2532]: DING: GNOME nautilus 40.2 nov 04 16:42:05 R00TB00K dbus-daemon[2444]: [session uid=1000 pid=2444] Activating service name='org.gnome.ArchiveManager1' requested by ':1.374' (uid=1000 pid=1695027 comm="gjs /usr/share/gnome-shell/extensions/ding@rasters" label="unconfined") nov 04 16:42:05 R00TB00K dbus-daemon[2444]: [session uid=1000 pid=2444] Successfully activated service 'org.gnome.ArchiveManager1' nov 04 16:42:06 R00TB00K gnome-shell[2532]: DING: GNOME nautilus 40.2 -- 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/1949845 Title: Toggle enable/disable dock autohide gives glitches Status in gnome-control-center package in Ubuntu: New Bug description: Ubuntu 22.04 development branch @ 4/11/2021 with kernel 5.13.0-19-generic (wayland) When opening gnome-control-center and toggle enable/disable the dock to autohide a few times, the gnome-control-center window gives glitches/flashes this is not on random, it can be reproduced ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:40.0-1ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Nov 4 16:47:34 2021 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1949845/+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 1949845] [NEW] Toggle enable/disable dock autohide gives glitches
Public bug reported: Ubuntu 22.04 development branch @ 4/11/2021 with kernel 5.13.0-19-generic (wayland) When opening gnome-control-center and toggle enable/disable the dock to autohide a few times, the gnome-control-center window gives glitches/flashes this is not on random, it can be reproduced ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:40.0-1ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Nov 4 16:47:34 2021 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/1949845 Title: Toggle enable/disable dock autohide gives glitches Status in gnome-control-center package in Ubuntu: New Bug description: Ubuntu 22.04 development branch @ 4/11/2021 with kernel 5.13.0-19-generic (wayland) When opening gnome-control-center and toggle enable/disable the dock to autohide a few times, the gnome-control-center window gives glitches/flashes this is not on random, it can be reproduced ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:40.0-1ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Nov 4 16:47:34 2021 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1949845/+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 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
Hello Yuan-Chen, or anyone else affected, Accepted mutter into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.38.4-1ubuntu2.21.04.01 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mutter (Ubuntu Hirsute) Status: New => Fix Committed ** Tags added: verification-needed-hirsute -- 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/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. Status in Mutter: Unknown Status in OEM Priority Project: In Progress Status in mutter package in Ubuntu: In Progress Status in mutter source package in Focal: Fix Committed Status in mutter source package in Hirsute: Fix Committed Status in mutter source package in Impish: Fix Committed Bug description: [Impact] * Gdm crashed and user need to be an expert to know how to work around, or need to reboot to fix. * OEM projects got certain SKU that can reliably reproduce this issue. * A merged patch in upstream fix the race condition. [Test Plan] * Use the SKU that can reliably reproduce this issue. * Do a cold boot, and wait for 5 mins. The monitor should turned-black but showing the Machine Vendor logo that was previously displayed by plythmouth. * Try to dog-food the deb from the proposed channel and make sure all input events still properly propagate. [Where problems could occur] * If the patch is not properly working as expected, per the file this patch touch, the user desktop session could stop responding to mouse, keyboard, and touch screen input. [Other Info] * Can't think of any for now. This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. (also observed that the touchscreen USB device drop of a USB bus on the target machine) Note: this bug seems to be timing sensitive. I got an OEM project machine that can reproduce this issue (reproducible on several machines with the same HW design). The machine is using ADL CPU, which needs a patched 5.14 kernel. So I can't reproduce this on impish. With the backported mutter, I verified an upstream patch seems to fix this issue. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #9 0x7f447b7c040a in ?? () from
[Desktop-packages] [Bug 1948933] Re: [SRU] libreoffice 7.1.7 for hirsute
** Changed in: libreoffice (Ubuntu Hirsute) Status: Triaged => In Progress -- 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/1948933 Title: [SRU] libreoffice 7.1.7 for hirsute Status in libreoffice package in Ubuntu: Triaged Status in libreoffice source package in Hirsute: In Progress Bug description: [Impact] * LibreOffice 7.1.7 is in its seventh bugfix release of the 7.1 line: https://wiki.documentfoundation.org/ReleasePlan/7.1#7.1.7_release * Version 7.1.6 is currently released in hirsute. For a list of fixed bugs compared to 7.1.6 see the list of bugs fixed in the release candidates of 7.1.7 (that's a total of 27 bugs): https://wiki.documentfoundation.org/Releases/7.1.7/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.1.7/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_71/1460/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-ricotz-ppa/hirsute/amd64/libr/libreoffice/20211028_194503_1ee54@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-ricotz-ppa/hirsute/arm64/libr/libreoffice/20211028_113740_b763e@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-ricotz-ppa/hirsute/armhf/libr/libreoffice/20211029_170024_1bc17@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-ricotz-ppa/hirsute/ppc64el/libr/libreoffice/20211028_225613_de9da@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-ricotz-ppa/hirsute/s390x/libr/libreoffice/20211028_104330_62f27@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 27 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1948933/+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 1949605] Re: Backport Thunderbird 91 to 20.04 LTS and 18.04 LTS
As far as I can see nspr does not require any special version, so could be upgraded easily, at least from 4.25 to 4.32. -- 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/1949605 Title: Backport Thunderbird 91 to 20.04 LTS and 18.04 LTS Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Bionic: Confirmed Status in thunderbird source package in Focal: Confirmed Status in thunderbird source package in Hirsute: Confirmed Bug description: Similarly to bug #1895643, which was about upgrading thunderbird from 68 to 78 in all supported Ubuntu releases, this bug is to track the update from thunderbird 78 to 91 in hirsute, focal and bionic. The rationale is that series 78 will soon be out of support (the last release, 78.14.0, was made public on September 7, 2021). Thunderbird follows the Firefox ESR release cycle, and the next/current series is 91 (already available in impish and jammy). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1949605/+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 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
Ok, I've uploaded hirsute too, we normally don't have much resources to handle also such versions, but this was easy enough. -- 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/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. Status in Mutter: Unknown Status in OEM Priority Project: In Progress Status in mutter package in Ubuntu: In Progress Status in mutter source package in Focal: Fix Committed Status in mutter source package in Impish: Fix Committed Bug description: [Impact] * Gdm crashed and user need to be an expert to know how to work around, or need to reboot to fix. * OEM projects got certain SKU that can reliably reproduce this issue. * A merged patch in upstream fix the race condition. [Test Plan] * Use the SKU that can reliably reproduce this issue. * Do a cold boot, and wait for 5 mins. The monitor should turned-black but showing the Machine Vendor logo that was previously displayed by plythmouth. * Try to dog-food the deb from the proposed channel and make sure all input events still properly propagate. [Where problems could occur] * If the patch is not properly working as expected, per the file this patch touch, the user desktop session could stop responding to mouse, keyboard, and touch screen input. [Other Info] * Can't think of any for now. This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. (also observed that the touchscreen USB device drop of a USB bus on the target machine) Note: this bug seems to be timing sensitive. I got an OEM project machine that can reproduce this issue (reproducible on several machines with the same HW design). The machine is using ADL CPU, which needs a patched 5.14 kernel. So I can't reproduce this on impish. With the backported mutter, I verified an upstream patch seems to fix this issue. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #10 0x7f447c3cf3a8 in wl_closure_invoke (closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=, target@entry=0x56437639f000, opcode=opcode@entry=0, data=) at ../src/connection.c:1018 #11 0x7f447c3cbc48 in dispatch_event (display=display@entry=0x56437639f000, queue=) at ../src/wayland-client.c:1445 #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, display=0x56437639f000) at ../src/wayland-client.c:1584 #13 wl_display_dispatch_queue_pending (display=0x56437639f000, queue=0x56437639f0d0) at ../src/wayland-client.c:1833 #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896 #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at ../../../../../hw/xwayland/xwayland.c:957 #16 0x564374401c61 in ospoll_wait (ospoll=0x56437638f4a0, timeout=) at ../../../../os/ospoll.c:657 #17 0x5643743faa23 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:208 #18 0x5643743ca4a7 in Dispatch () at ../../../../include/list.h:220 #19 0x5643743ce794 in dix_main (argc=16, argv=0x7ffc44d49298, envp=) at ../../../../dix/main.c:276 #20 0x7f447b8c90b3 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #21 0x56437429c60e in _start
[Desktop-packages] [Bug 1949605] Re: Backport Thunderbird 91 to 20.04 LTS and 18.04 LTS
For what its' worth, the Focal system's provided packages do not meet the following build-deps of the *debian* Thunderbird 91.3.0 package;- cbindgen (>= 0.19) debhelper-compat (= 13) libnspr4-dev (>= 2:4.32~) libnss3-dev (>= 2:3.68~) nodejs (>= 10.19.0) Merely overriding the version dependencies in debian control file [which can just automatically referring to latest version needlessly] is not sufficient, an internal check *actually* requires e.g. nspr >=4.32 . These packages may need backporting or whatever, or the ubuntu packages may work differently to get around these limitations for building (in any case build-deps and runtime-deps may be another matter...). -- 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/1949605 Title: Backport Thunderbird 91 to 20.04 LTS and 18.04 LTS Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Bionic: Confirmed Status in thunderbird source package in Focal: Confirmed Status in thunderbird source package in Hirsute: Confirmed Bug description: Similarly to bug #1895643, which was about upgrading thunderbird from 68 to 78 in all supported Ubuntu releases, this bug is to track the update from thunderbird 78 to 91 in hirsute, focal and bionic. The rationale is that series 78 will soon be out of support (the last release, 78.14.0, was made public on September 7, 2021). Thunderbird follows the Firefox ESR release cycle, and the next/current series is 91 (already available in impish and jammy). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1949605/+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 1916586] Re: Adding word to dictionary doesn't update subject
This still happens on Thunderbird 91, so have reported it upstream:
https://bugzilla.mozilla.org/show_bug.cgi?id=1739405
** Bug watch added: Mozilla Bugzilla #1739405
https://bugzilla.mozilla.org/show_bug.cgi?id=1739405
--
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/1916586
Title:
Adding word to dictionary doesn't update subject
Status in thunderbird package in Ubuntu:
New
Bug description:
When composing a new email, if you type a word that's not in the
dictionary into the email subject, then type the same word in the
email body, then right click on the word in the email body and select
"Add to dictionary", the wavy red warning line disappears from the
word in the email body, but not from the same word in the email
subject.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: thunderbird 1:78.7.1+build1-0ubuntu0.20.10.4
ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
Uname: Linux 5.8.0-43-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: alistair 1735 F pulseaudio
/dev/snd/pcmC0D0p: alistair 1735 F...m pulseaudio
BuildID: 20210203182138
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: Unity:Unity7:ubuntu
Date: Tue Feb 23 10:37:30 2021
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d
IncompatibleExtensions:
Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2020-07-14 (223 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
IpRoute:
default via 172.16.0.1 dev wlp0s20f3 proto dhcp metric 600
10.0.0.0/24 dev wg0 proto kernel scope link src 10.0.0.2
169.254.0.0/16 dev wg0 scope link metric 1000
172.16.0.0/16 dev wlp0s20f3 proto kernel scope link src 172.16.69.217 metric
600
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/thunderbird/omni.ja:greprefs.js:732
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=78.7.1/20210203182138 (In use)
RunningIncompatibleAddons: True
SourcePackage: thunderbird
UpgradeStatus: Upgraded to groovy on 2020-10-05 (141 days ago)
dmi.bios.date: 12/07/2020
dmi.bios.release: 1.15
dmi.bios.vendor: LENOVO
dmi.bios.version: N2WET25W (1.15 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20U9CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.8
dmi.modalias:
dmi:bvnLENOVO:bvrN2WET25W(1.15):bd12/07/2020:br1.15:efr1.8:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon Gen 8
dmi.product.name: 20U9CTO1WW
dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
dmi.product.version: ThinkPad X1 Carbon Gen 8
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1916586/+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 1949605] Re: Backport Thunderbird 91 to 20.04 LTS and 18.04 LTS
This is now a security issue. As the vulnerability CVE-2021-38503 is currently actively exploited and will not be fixed in 1.78 series, which is EOL (see https://www.mozilla.org/en-US/security/advisories/mfsa2021-50/) The latest version available in focal and focal-updates repositories is 1.78.13 (even not the latest available version of the 1.78 series). This is a show stopper for an LTS edition; please fix rapidly! ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-38503 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-38504 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-38506 -- 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/1949605 Title: Backport Thunderbird 91 to 20.04 LTS and 18.04 LTS Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Bionic: Confirmed Status in thunderbird source package in Focal: Confirmed Status in thunderbird source package in Hirsute: Confirmed Bug description: Similarly to bug #1895643, which was about upgrading thunderbird from 68 to 78 in all supported Ubuntu releases, this bug is to track the update from thunderbird 78 to 91 in hirsute, focal and bionic. The rationale is that series 78 will soon be out of support (the last release, 78.14.0, was made public on September 7, 2021). Thunderbird follows the Firefox ESR release cycle, and the next/current series is 91 (already available in impish and jammy). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1949605/+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 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
Accepted both focal and impish, but I don't see anyone sponsoring the hirsute version - could we get that uploaded as well? I know it's not the latest series, but hirsute will still be supported for a while and we shouldn't forget about users of 21.04, at least not yet. Not everyone upgraded yet. Can someone sponsor hirsute before we go live with these updates? Thanks. -- 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/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. Status in Mutter: Unknown Status in OEM Priority Project: In Progress Status in mutter package in Ubuntu: In Progress Status in mutter source package in Focal: Fix Committed Status in mutter source package in Impish: Fix Committed Bug description: [Impact] * Gdm crashed and user need to be an expert to know how to work around, or need to reboot to fix. * OEM projects got certain SKU that can reliably reproduce this issue. * A merged patch in upstream fix the race condition. [Test Plan] * Use the SKU that can reliably reproduce this issue. * Do a cold boot, and wait for 5 mins. The monitor should turned-black but showing the Machine Vendor logo that was previously displayed by plythmouth. * Try to dog-food the deb from the proposed channel and make sure all input events still properly propagate. [Where problems could occur] * If the patch is not properly working as expected, per the file this patch touch, the user desktop session could stop responding to mouse, keyboard, and touch screen input. [Other Info] * Can't think of any for now. This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. (also observed that the touchscreen USB device drop of a USB bus on the target machine) Note: this bug seems to be timing sensitive. I got an OEM project machine that can reproduce this issue (reproducible on several machines with the same HW design). The machine is using ADL CPU, which needs a patched 5.14 kernel. So I can't reproduce this on impish. With the backported mutter, I verified an upstream patch seems to fix this issue. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #10 0x7f447c3cf3a8 in wl_closure_invoke (closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=, target@entry=0x56437639f000, opcode=opcode@entry=0, data=) at ../src/connection.c:1018 #11 0x7f447c3cbc48 in dispatch_event (display=display@entry=0x56437639f000, queue=) at ../src/wayland-client.c:1445 #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, display=0x56437639f000) at ../src/wayland-client.c:1584 #13 wl_display_dispatch_queue_pending (display=0x56437639f000, queue=0x56437639f0d0) at ../src/wayland-client.c:1833 #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896 #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at ../../../../../hw/xwayland/xwayland.c:957 #16 0x564374401c61 in ospoll_wait (ospoll=0x56437638f4a0, timeout=) at ../../../../os/ospoll.c:657 #17 0x5643743faa23 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:208 #18 0x5643743ca4a7 in Dispatch () at
[Desktop-packages] [Bug 1948894] Please test proposed package
Hello Yuan-Chen, or anyone else affected, Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.9-0ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. Status in Mutter: Unknown Status in OEM Priority Project: In Progress Status in mutter package in Ubuntu: In Progress Status in mutter source package in Focal: Fix Committed Status in mutter source package in Impish: Fix Committed Bug description: [Impact] * Gdm crashed and user need to be an expert to know how to work around, or need to reboot to fix. * OEM projects got certain SKU that can reliably reproduce this issue. * A merged patch in upstream fix the race condition. [Test Plan] * Use the SKU that can reliably reproduce this issue. * Do a cold boot, and wait for 5 mins. The monitor should turned-black but showing the Machine Vendor logo that was previously displayed by plythmouth. * Try to dog-food the deb from the proposed channel and make sure all input events still properly propagate. [Where problems could occur] * If the patch is not properly working as expected, per the file this patch touch, the user desktop session could stop responding to mouse, keyboard, and touch screen input. [Other Info] * Can't think of any for now. This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. (also observed that the touchscreen USB device drop of a USB bus on the target machine) Note: this bug seems to be timing sensitive. I got an OEM project machine that can reproduce this issue (reproducible on several machines with the same HW design). The machine is using ADL CPU, which needs a patched 5.14 kernel. So I can't reproduce this on impish. With the backported mutter, I verified an upstream patch seems to fix this issue. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #10 0x7f447c3cf3a8 in wl_closure_invoke (closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=, target@entry=0x56437639f000,
[Desktop-packages] [Bug 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
Hello Yuan-Chen, or anyone else affected, Accepted mutter into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/40.5-1ubuntu3~21.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mutter (Ubuntu Impish) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-impish ** Changed in: mutter (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- 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/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. Status in Mutter: Unknown Status in OEM Priority Project: In Progress Status in mutter package in Ubuntu: In Progress Status in mutter source package in Focal: Fix Committed Status in mutter source package in Impish: Fix Committed Bug description: [Impact] * Gdm crashed and user need to be an expert to know how to work around, or need to reboot to fix. * OEM projects got certain SKU that can reliably reproduce this issue. * A merged patch in upstream fix the race condition. [Test Plan] * Use the SKU that can reliably reproduce this issue. * Do a cold boot, and wait for 5 mins. The monitor should turned-black but showing the Machine Vendor logo that was previously displayed by plythmouth. * Try to dog-food the deb from the proposed channel and make sure all input events still properly propagate. [Where problems could occur] * If the patch is not properly working as expected, per the file this patch touch, the user desktop session could stop responding to mouse, keyboard, and touch screen input. [Other Info] * Can't think of any for now. This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. (also observed that the touchscreen USB device drop of a USB bus on the target machine) Note: this bug seems to be timing sensitive. I got an OEM project machine that can reproduce this issue (reproducible on several machines with the same HW design). The machine is using ADL CPU, which needs a patched 5.14 kernel. So I can't reproduce this on impish. With the backported mutter, I verified an upstream patch seems to fix this issue. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in
[Desktop-packages] [Bug 1949352] Re: Removable drives are not auto-mounted after screen lock/unlock
** Changed in: gnome-shell-extension-dashtodock (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Triaged ** Changed in: gnome-shell-extension-ubuntu-dock (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 gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1949352 Title: Removable drives are not auto-mounted after screen lock/unlock Status in gnome-shell-extension-dashtodock package in Ubuntu: In Progress Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Bug description: If I lock and then unlock the screen, and then connect a removable drive, it is not recognized by the GNOME shell. The kernel logs show the drive, I can mount it manually, but it is not mounted automatically. The logged errors are attached. I could fix the issue by modifying the source code as given in the attached patch. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-11-01 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell 40.5-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Tags: wayland-session impish Uname: Linux 5.13.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1949352/+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 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
[Where problems could occur] is updated ** Description changed: [Impact] The modem certification requires that different modem firmware is used for different network carrier. This needs the firmware upgrading capability during the modem certification process. The modem manufacture vendors (Foxconn and Quectel) provided utilities to do modem's firmware upgrading manually.(LP#1943774, LP#1943780) These utilities are verified to be working when the recent versions(> v 1.18.2) of ModemManager are used with. To support manual firmware upgrading on the current Focal release which is using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2. The requested upstream patches are listed as below: * for Quectel EM160 4G ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2 * for Foxconn T99W175 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9 **https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154 The firmware upgrading was verified using the patched ModemManager v 1.16.6 with the following 2 modems: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Prepare the modem’s firmware and install the firmware upgrading application provided by Foxconn and Quectel 4. Using the firmware upgrading application to upgrade the modem’s firmware 5. Verify if the modem’s firmware upgrading is successful 6. Reboot 7. Verify if the upgraded modem firmware is still working [Where problems could occur] - The requested upstream patches are for these 2 specific modems. - This should not affect existing generic functions and other modems. + The requested update has 2 parts: + + 1. Informative +1.1 Provide more information about modems whose drivers use WWAN subsystem in kernel 5.13 +1.2 Modem manufacture's private utilities can use this information to do modem's FW upgrading manually + + 2. Changes are specific to Foxconn and Quectel modems +2.1 Modified code are only used by Foxconn and Quectel modems during their FW upgrading. (matched by vendor_id and product_id) + + In current Ubuntu's certification records for modem: + * No other modem uses WWAN subsystem in kernel 5.13 + * Modem's FW update is not supported via ModemManager ( < v1.18 ) + + There is no certificated modems can do the firmware upgrading flow for the regression test. + This update should not affect existing modems. [Other Info] The firmware and the upgrading utilities can be downloaded from the following link: * LP#1943774 for Quectel modems * LP#1943780 for Foxconn modems -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. Status in OEM Priority Project: In Progress Status in modemmanager package in Ubuntu: New Bug description: [Impact] The modem certification requires that different modem firmware is used for different network carrier. This needs the firmware upgrading capability during the modem certification process. The modem manufacture vendors (Foxconn and Quectel) provided utilities to do modem's firmware upgrading manually.(LP#1943774, LP#1943780) These utilities are verified to be working when the recent versions(> v 1.18.2) of ModemManager are used with. To support manual firmware upgrading on the current Focal release which is using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2. The requested upstream patches are listed as below: * for Quectel EM160 4G ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2 * for Foxconn T99W175 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9 **https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a **
[Desktop-packages] [Bug 1949621] Re: libmbim cannot make use of Quectel EM120
Please note the libmbim 1.24 branch is not actively maintained any more in upstream. If you want to keep on using that release, you're fully on your own. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1949621 Title: libmbim cannot make use of Quectel EM120 Status in libmbim package in Ubuntu: New Bug description: As reported on https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/issues/402, this modem (shipped in many new Lenovo ThinkPad laptops) requires some specific handling as others new modems to performs FCC unlock procedure. A fix has been merged upstream: https://gitlab.freedesktop.org/mobile- broadband/libmbim/-/merge_requests/125/diffs Can we expect to see that merged in the current Ubuntu 21.10 ? I understand it might require a backport, since they merged it against 1.26 and it does not seems to apply cleanly on 1.24. I also suspect upgrading libmbim to 1.26 is not acceptable for impish release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1949621/+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 1100326]
I do have a Geoclue2 geolocation provider for gecko-dev right now and have been using it in Firefox for a few weeks now. This provider is purely (G)D-Bus based, so it doesn't need any additional external library as a dependency. I envision it as a system-wide geolocation source, much like the ones that Firefox already uses on Windows, Mac OS or Android platforms. Unfortunately, it's unlikely that I will be able to find enough time to go through a formal review process with this patch before this year winter holiday break. -- 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/1100326 Title: Location requested by websites should be able to use GPS/mobile positioning Status in Chromium Browser: Fix Committed Status in Mozilla Firefox: Unknown Status in GeoClue: Won't Fix Status in WebKit: Fix Released Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in geoclue-2.0 package in Ubuntu: Fix Released Status in geoclue-providers package in Ubuntu: Invalid Bug description: It would be nice if location requested by websites could use location found from GPS or GSM/CDMA positioning. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1100326/+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 1065126]
(In reply to Anje from comment #203) > there are going to be an increase in Thunderbird users I can't comment on Thunderbird, and recommend you contact the Thunderbird devs through non-bugzilla channels (matrix or email is probably best). I believe that bug 1690395 was reopened and tracks the TB issue. I'm hopeful that the Firefox changes will help TB devs fix this, but TB is different enough that other/more work may be necessary. You should discuss that with the TB folks. > If someone is already working on this, it would be helpful to communicate this I did communicate this, in comment #201, which you quoted and therefore must have read. I don't know why you didn't take my word for it. If you don't trust my bugzilla comments, then no other change I could make to this bug would convince you that work is ongoing, and the issue is with the lack of trust, not with whatever work we are doing. I did not assign someone to this bug or set a release date because the fix for this bug is part of a bigger project. Although we have hopes about which release that change will ship in, we can't promise anything right now - it depends how long it takes to stabilize the changes in question. Downloads are complex and have a lot of edgecases. We're currently testing out these fixes on the Firefox nightly channel. In barely a week, nightly users have already found 10 or so new issues with it which will need addressing. As a result, I also did not (and still do not) want to write down a version or release here, because inevitably that information may get outdated or superseded, and then users will just be more upset. (I have been reluctant to share the other bug links because quite frankly, 200 comments on those bugs is not something that is going to help anyone, either. I've added one now, **please** do not deluge that one with comments instead; it won't help.) > outsider users are being polite in trying to explain how important this bug is Being polite is necessary, but not sufficient reason for commenting on a bug. This is a bug tracker, in which developers track work, and it isn't a user complaints forum. Being asked several times a week "when is this going to be fixed", no matter how politely, only delays a release date for the actual fix. I restricted comments for exactly this reason. We're sorry this hasn't been fixed yet, we know this is important to users, and that is why we are working on it. No further comments stating how important it is or how terrible it is that this hasn't yet been fixed are necessary, nor indeed helpful, at this point. -- 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/1065126 Title: "Always do this from now on" does not work Status in Mozilla Firefox: Confirmed Status in One Hundred Papercuts: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Downloading an unknown file type in Firefox displays a dialog for choosing which application to use for opening the file. The dialog contains a check box labelled "Always do this action from now on". Checking this option does not work: When I download a file of the same type next time, the same dialog is displayed again. This feature is broken for as long as I can remember (> 10 years). It's time it was fixed (or removed). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: firefox 15.0.1+build1-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 NonfreeKernelModules: nvidia AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ruediger 2536 F pulseaudio BuildID: 20120907231657 Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfe22 irq 49' Mixer name : 'Analog Devices AD1984' Components : 'HDA:11d41984,17aa20bb,00100400' Controls : 32 Simple ctrls : 20 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 7KHT24WW-1.08' Mixer name : 'ThinkPad EC 7KHT24WW-1.08' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Channel: Unavailable Date: Wed Oct 10 18:17:44 2012 EcryptfsInUse: Yes ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
[Desktop-packages] [Bug 1065126]
(In reply to :Gijs (he/him) from comment #201) > We are actively working on a fix, but as several comments here have already > pointed out, it isn't trivial and will come with some side-effects to 20-odd > year old ways that Firefox has done downloads. The root cause of this issue > is outlined in comment #22: avoiding dataloss when applications don't provide > the user with control over the resulting file, while the file is stored > ephemerally (ie in the temp folder) and gets deleted later. We'll update this > bug when we're confident about those changes making their way to release. You mention 'we are actively working on a fix' but to anyone following this bug and at this moment and there are going to be an increase in Thunderbird users, we notice this bug is marked as 'New' and it looks like no one has been assigned to fix it and there is nothing about when a fix is expected as a target. This implies no developer is working on it at this moment and there is no action - whether that is true or not is not the point. That is what is perceived by the lack of documentation. This bug is also where users get information on progress, but are seeing nothing and after 13 years you cannot blame users for wondering what is going on and why this bug still exists. If someone is already working on this, it would be helpful to communicate this and let people know this bug did have someone assigned to work on it and what version the planned fix will be expected for release. There have been comments suggesting no one should ask for a 'please fix' as it may stop developers working on it, but outsider users are being polite in trying to explain how important this bug is when it comes to work throughput for individuals and businesses alike. I would be appalled if developers were actually choosing to deliberately not work on a bug just because there has been so many desperate users wondering why something as important as this bug appears to still be new and no one assigned etc. This issue is a real problem in Thunderbird where opening of a variety of email attachments is extremely common. Emails by their nature are a means of conveying and communicating documention in various formats. This bug has also started to see more recent reports since TB version 91*. This is a polite request for information and update. -- 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/1065126 Title: "Always do this from now on" does not work Status in Mozilla Firefox: Confirmed Status in One Hundred Papercuts: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Downloading an unknown file type in Firefox displays a dialog for choosing which application to use for opening the file. The dialog contains a check box labelled "Always do this action from now on". Checking this option does not work: When I download a file of the same type next time, the same dialog is displayed again. This feature is broken for as long as I can remember (> 10 years). It's time it was fixed (or removed). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: firefox 15.0.1+build1-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 NonfreeKernelModules: nvidia AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ruediger 2536 F pulseaudio BuildID: 20120907231657 Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfe22 irq 49' Mixer name : 'Analog Devices AD1984' Components : 'HDA:11d41984,17aa20bb,00100400' Controls : 32 Simple ctrls : 20 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 7KHT24WW-1.08' Mixer name : 'ThinkPad EC 7KHT24WW-1.08' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Channel: Unavailable Date: Wed Oct 10 18:17:44 2012 EcryptfsInUse: Yes ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) IpRoute: default via 172.31.0.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 172.31.0.0/20 dev wlan0 proto kernel scope link src 172.31.9.26 metric 2 MostRecentCrashID:
[Desktop-packages] [Bug 1065126]
*** Bug 1736804 has been marked as a duplicate of this bug. *** -- 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/1065126 Title: "Always do this from now on" does not work Status in Mozilla Firefox: Confirmed Status in One Hundred Papercuts: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Downloading an unknown file type in Firefox displays a dialog for choosing which application to use for opening the file. The dialog contains a check box labelled "Always do this action from now on". Checking this option does not work: When I download a file of the same type next time, the same dialog is displayed again. This feature is broken for as long as I can remember (> 10 years). It's time it was fixed (or removed). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: firefox 15.0.1+build1-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 NonfreeKernelModules: nvidia AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ruediger 2536 F pulseaudio BuildID: 20120907231657 Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfe22 irq 49' Mixer name : 'Analog Devices AD1984' Components : 'HDA:11d41984,17aa20bb,00100400' Controls : 32 Simple ctrls : 20 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 7KHT24WW-1.08' Mixer name : 'ThinkPad EC 7KHT24WW-1.08' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Channel: Unavailable Date: Wed Oct 10 18:17:44 2012 EcryptfsInUse: Yes ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) IpRoute: default via 172.31.0.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 172.31.0.0/20 dev wlan0 proto kernel scope link src 172.31.9.26 metric 2 MostRecentCrashID: bp-7716491c-74b4-4213-bbf0-37b512110505 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=15.0.1/20120907231657 (In use) RelatedPackageVersions: rhythmbox-mozilla 2.96-0ubuntu4.2 totem-mozilla 3.0.1-0ubuntu21.1 icedtea-6-plugin 1.2-2ubuntu1.2 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to precise on 2012-04-28 (165 days ago) dmi.bios.date: 03/18/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETC9WW (2.29 ) dmi.board.name: 6457BBG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7LETC9WW(2.29):bd03/18/2011:svnLENOVO:pn6457BBG:pvrThinkPadT61:rvnLENOVO:rn6457BBG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 6457BBG dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1065126/+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 1949703] Re: Opening a link fails to bring browser to foreground
bot asked to select a package and nautilus was the closest I could think of for the issue... I might be wrong... ** Package changed: ubuntu => nautilus (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1949703 Title: Opening a link fails to bring browser to foreground Status in nautilus package in Ubuntu: New Bug description: Steps to reporduce: 1) Open a browser (e.g. Chrome) 2) Open any other application and make sure it's in the foreground. 3) Open a terminal and run: xdg-open "https://google.com; Expected: Your browser should be brought to foreground with the Google website open Actual: Your browser stays in the background with the Google website open. The browser icon in the Launcher Bar will animate (indicating that some trigger has been made). Only after actively clicking on the browser icon in the Launcher Bar will the browser move to foreground. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1949703/+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 1949703] [NEW] Opening a link fails to bring browser to foreground
You have been subscribed to a public bug: Steps to reporduce: 1) Open a browser (e.g. Chrome) 2) Open any other application and make sure it's in the foreground. 3) Open a terminal and run: xdg-open "https://google.com; Expected: Your browser should be brought to foreground with the Google website open Actual: Your browser stays in the background with the Google website open. The browser icon in the Launcher Bar will animate (indicating that some trigger has been made). Only after actively clicking on the browser icon in the Launcher Bar will the browser move to foreground. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Opening a link fails to bring browser to foreground https://bugs.launchpad.net/bugs/1949703 You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. -- 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 1949654] Re: Weird UI behavior when addprint off LAN using 21.10
Please 1. run apport-collect 1949654 2. report to https://github.com/OpenPrinting/system-config-printer/issues and share a link here. ** Also affects: system-config-printer (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1949654 Title: Weird UI behavior when addprint off LAN using 21.10 Status in Ubuntu MATE: New Status in system-config-printer package in Ubuntu: New Bug description: When using a fully patched 21.10 system and adding a LAN printer via it's IP, the response is very weird. See enclosed picture. PS: I believe this problem has been happening since AT LEAST 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1949654/+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 1811724] Re: libbd_mdraid.so.2: cannot open shared object file
I encountered something very similar to this issue (maybe even this issue?) when my docker containers could not start (using snap on Ubuntu 20.04.3 LTS under VirtualBox with a Windows 10 host). Similar to others, `sudo apt install libblockdev-mdraid2` seems to have fixed it. In case these log lines are useful context, they came from `sudo grep fail /var/log/syslog` (just trying to filter out some of the noise and I suspect that the devmapper/containerd/cni bits are not directly related): Nov 4 05:22:48 docker kernel: [0.305507] acpi PNP0A03:00: fail to add MMCONFIG information, can't access extended PCI configuration space under this bridge. Nov 4 05:22:48 docker systemd[1]: Starting GRUB failed boot detection... Nov 4 05:22:48 docker systemd[1]: Finished GRUB failed boot detection. Nov 4 05:22:48 docker udisksd[731]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory Nov 4 05:22:48 docker containerd[733]: time="2021-11-04T05:22:48.627329367Z" level=warning msg="failed to load plugin io.containerd.snapshotter.v1.devmapper" error="devmapper not configured" Nov 4 05:22:48 docker containerd[733]: time="2021-11-04T05:22:48.635107136Z" level=error msg="failed to load cni during init, please check CRI plugin status before setting up network for pods" error="cni config load failed: no network config found in /etc/cni/net.d: cni plugin not initialized: failed to load cni config" Nov 4 05:22:49 docker docker.dockerd[719]: snap-update-ns failed with code 1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1811724 Title: libbd_mdraid.so.2: cannot open shared object file Status in udisks2 package in Ubuntu: Confirmed Bug description: Had some (probably unrelated?) trouble typing input into login console, and went looking through /var/log/syslog : found Jan 14 21:10:21 vps39184 udisksd[611]: udisks daemon version 2.8.1 starting Jan 14 21:10:22 vps39184 udisksd[611]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory Jan 14 21:10:22 vps39184 udisksd[611]: Failed to load the 'mdraid' libblockdev plugin Seems to give this warning every time I boot. udisks2: Installed: 2.8.1-3 Candidate: 2.8.1-3 ubuntu: 19.04 disco ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: udisks2 2.8.1-3 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu18 Architecture: amd64 CustomUdevRuleFiles: 80-net-setup-link.rules Date: Mon Jan 14 21:31:52 2019 Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Red Hat KVM ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: root=/dev/vda1 ro vga16fb.modeset=0 quiet splash SourcePackage: udisks2 UpgradeStatus: Upgraded to disco on 2018-11-23 (52 days ago) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Seabios dmi.bios.version: 0.5.1 dmi.chassis.type: 1 dmi.chassis.vendor: Red Hat dmi.modalias: dmi:bvnSeabios:bvr0.5.1:bd01/01/2007:svnRedHat:pnKVM:pvrRHEL6.6.0PC:cvnRedHat:ct1:cvr: dmi.product.family: Red Hat Enterprise Linux dmi.product.name: KVM dmi.product.version: RHEL 6.6.0 PC dmi.sys.vendor: Red Hat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1811724/+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 1946098] Re: Update to 91.2.0 in impish
thunderbird 1:91.2.1+build1-0ubuntu0.21.10.1 is now available in impish (updates and security pockets) ** Changed in: thunderbird (Ubuntu) Status: New => Fix Released -- 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/1946098 Title: Update to 91.2.0 in impish Status in thunderbird package in Ubuntu: Fix Released Bug description: impish currently has thunderbird 1:91.1.2+build1-0ubuntu1, which at the time of filing this bug is the latest stable release (so all is good). There is a new release candidate, 91.2.0+build1 (https://ftp.mozilla.org/pub/thunderbird/candidates/91.2.0-candidates/build1/) which, if everything goes fine, will become a release before impish is released. I intend to upload that RC to impish-proposed, so I'm filing this bug for the release team to decide whether it's worth accepting in the release, or leaving it out as a 0-day SRU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1946098/+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
