[Desktop-packages] [Bug 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
Oops. That link suggests it's a Wayland server bug in mutter. Fixed in tag 41.0 ** Package changed: xorg-server (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: New => Fix Committed ** Tags added: fixed-in-41.0 fixed-upstream ** Bug watch added: Red Hat Bugzilla #1516859 https://bugzilla.redhat.com/show_bug.cgi?id=1516859 ** Also affects: mutter (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1516859 Importance: Unknown Status: Unknown ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1797 https://gitlab.gnome.org/GNOME/mutter/-/issues/1797 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/1797 Importance: Unknown Status: Unknown ** Also affects: xorg-server via https://gitlab.freedesktop.org/xorg/xserver/-/issues/1239 Importance: Unknown Status: Unknown ** Tags added: 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 X.Org X server: Unknown Status in mutter package in Ubuntu: Fix Committed Status in mutter package in Fedora: Unknown Bug description: 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. 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 ()``` To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+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.
This was from focal so Xwayland comes from the 'xorg-server' source package. In hirsute and later it changed to the 'xwayland' source package. ** Package changed: mutter (Ubuntu) => xorg-server (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. Status in OEM Priority Project: In Progress Status in mutter package in Ubuntu: Fix Committed Status in mutter package in Fedora: Unknown Bug description: 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. 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 ()``` To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1948894/+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.
upstream bug: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1239 ** Tags added: oem-priority originate-from-1947739 somerville -- 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 OEM Priority Project: In Progress Status in mutter package in Ubuntu: New Bug description: 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. 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 ()``` To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1948894/+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 1948829] Re: AppIndicator icon looks squashed in Ubuntu focal
** Description changed: Release of Ubuntu: Ubuntu 20.04 (focal) Version of gnome-shell: 3.36.9-0ubuntu0.20.04.2 + Version of gnome-shell-extension-appindicator: 33.1-0ubuntu0.20.04.2 I implemented a simple AppIndicator app using python which contains an icon and a label. The icon image is SVG file and image size is 300 x 200 in px. When running the AppIndicator app, the icon should be scaled based on AppIndicator bar height and keeps aspect ratio, but only image height is scaled and image width still keeps 300px so the icon looks squashed on AppIndicator bar. This issue was only happened if the icon image weight and height are different (eg. 300 x 200). I tried the icon image weight and height are the same (300 x 300), the issue was not reproduced. The same AppIndicator app works fine in Ubuntu 18.04 (bionic, gnome- shell version: 3.28.4-0ubuntu18.04.7), and both weight and height are scaled and keeps aspect ratio even if the icon image weight and height are different. So this issue is only happened in gnome-shell 3.36. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1948829 Title: AppIndicator icon looks squashed in Ubuntu focal Status in gnome-shell-extension-appindicator package in Ubuntu: New Bug description: Release of Ubuntu: Ubuntu 20.04 (focal) Version of gnome-shell: 3.36.9-0ubuntu0.20.04.2 Version of gnome-shell-extension-appindicator: 33.1-0ubuntu0.20.04.2 I implemented a simple AppIndicator app using python which contains an icon and a label. The icon image is SVG file and image size is 300 x 200 in px. When running the AppIndicator app, the icon should be scaled based on AppIndicator bar height and keeps aspect ratio, but only image height is scaled and image width still keeps 300px so the icon looks squashed on AppIndicator bar. This issue was only happened if the icon image weight and height are different (eg. 300 x 200). I tried the icon image weight and height are the same (300 x 300), the issue was not reproduced. The same AppIndicator app works fine in Ubuntu 18.04 (bionic, gnome- shell version: 3.28.4-0ubuntu18.04.7), and both weight and height are scaled and keeps aspect ratio even if the icon image weight and height are different. So this issue is only happened in gnome-shell 3.36. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1948829/+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] [NEW] Xwayland crash in gdm as screen off and touchscreen detach.
Public bug reported: 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. 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 ()``` ** Affects: oem-priority Importance: Critical Assignee: Yuan-Chen Cheng (ycheng-twn) Status: In Progress ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1947739 somerville ** Information type changed from Proprietary to Public ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1239 https://gitlab.freedesktop.org/xorg/xserver/-/issues/1239 -- 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 OEM Priority Project: In Progress Status in mutter package in Ubuntu: New Bug description: 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. 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
[Desktop-packages] [Bug 1948641] Re: can not change dock bar position
at last, i tried 'gnome-extensions enable ubuntu-d...@ubuntu.com' then i can change the position! but why the extension is not enabled, i totally can not figure out. -- 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/1948641 Title: can not change dock bar position Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: dock bar is fixed at the bottom. when u want to change the pisition, is is still fixed at the bottom. method: settings->appearence->dock->position ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Mon Oct 25 15:45:45 2021 DistUpgraded: 2021-10-22 13:55:14,850 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05ca] InstallationDate: Installed on 2018-04-28 (1276 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Latitude E7240 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=794fdd3e-74af-4db0-8e0a-ca94eb02e241 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2021-10-22 (3 days ago) dmi.bios.date: 02/01/2018 dmi.bios.release: 65.25 dmi.bios.vendor: Dell Inc. dmi.bios.version: A25 dmi.board.name: 08230Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA25:bd02/01/2018:br65.25:svnDellInc.:pnLatitudeE7240:pvr00:rvnDellInc.:rn08230Y:rvrA00:cvnDellInc.:ct9:cvr:sku05CA: dmi.product.name: Latitude E7240 dmi.product.sku: 05CA dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.1+21.10.20210501-0ubuntu1 version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1948641/+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 1948829] Re: AppIndicator icon looks squashed in Ubuntu focal
** Description changed: Release of Ubuntu: Ubuntu 20.04 (focal) Version of gnome-shell: 3.36.9-0ubuntu0.20.04.2 - I implemented a simple AppIndicator in python which contains an icon and - a label. The icon image is SVG file and image size is 300x200 in px. - When running the AppIndicator app, the icon should be scaled based on - AppIndicator bar height and keeps aspect ratio, but only image height is - scaled and image width still keeps 300px so the icon looks squashed on - AppIndicator bar. + I implemented a simple AppIndicator app using python which contains an + icon and a label. The icon image is SVG file and image size is 300 x 200 + in px. When running the AppIndicator app, the icon should be scaled + based on AppIndicator bar height and keeps aspect ratio, but only image + height is scaled and image width still keeps 300px so the icon looks + squashed on AppIndicator bar. + + This issue was only happened if the icon image weight and height are + different (eg. 300 x 200). I tried the icon image weight and height are + the same (300 x 300), the issue was not reproduced. The same AppIndicator app works fine in Ubuntu 18.04 (bionic, gnome- shell version: 3.28.4-0ubuntu18.04.7), and both weight and height are - scaled and keeps aspect ratio. So this issue is only happened in gnome- - shell 3.36. + scaled and keeps aspect ratio even if the icon image weight and height + are different. So this issue is only happened in gnome-shell 3.36. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1948829 Title: AppIndicator icon looks squashed in Ubuntu focal Status in gnome-shell-extension-appindicator package in Ubuntu: New Bug description: Release of Ubuntu: Ubuntu 20.04 (focal) Version of gnome-shell: 3.36.9-0ubuntu0.20.04.2 I implemented a simple AppIndicator app using python which contains an icon and a label. The icon image is SVG file and image size is 300 x 200 in px. When running the AppIndicator app, the icon should be scaled based on AppIndicator bar height and keeps aspect ratio, but only image height is scaled and image width still keeps 300px so the icon looks squashed on AppIndicator bar. This issue was only happened if the icon image weight and height are different (eg. 300 x 200). I tried the icon image weight and height are the same (300 x 300), the issue was not reproduced. The same AppIndicator app works fine in Ubuntu 18.04 (bionic, gnome- shell version: 3.28.4-0ubuntu18.04.7), and both weight and height are scaled and keeps aspect ratio even if the icon image weight and height are different. So this issue is only happened in gnome-shell 3.36. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1948829/+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 1948893] Re: Application grid fails to appear or disappear
** Description changed: - 3.38.4.1 + 3.38.4 What you expected to happen: gnome-shell application grid to behave normally What actually happened: Upon clicking the show applications button once and reopening overview, applications do not show up. When clicking the button twice to open/close the application view, the grid will briefly flash on second click, and after closing and reopening overview the grid will persist in the main overview behind open windows. This bug seems to be triggered by extensions such as dash-to-panel when configuring settings to use the default gnome-dash/applications button and disabling the button on the panel. Because this bug is very similar to https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922353 which was also triggered by the same extension for many users, it seems appropriate to report here. I've recreated this bug on ubuntu 21.04 with vanilla gnome as well as pop_os 21.04 and ubuntu 21.04 with default extensions disabled. Error log: value "nan" of type 'gfloat' is invalid or out of range for property 'translation-x' of type 'gfloat' value "nan" of type 'gfloat' is invalid or out of range for property 'translation-y' of type 'gfloat' value "-nan" of type 'gdouble' is invalid or out of range for property 'value' of type 'gdouble' Steps to recreate: 1) Disable any built-in extensions that modify gnome-shell 2) Install and enable dash-to-panel, toggle 'show applications button' off and 'activities button' on and enable 'keep original gnome-shell dash' 3) Restart shell and click show applications button on the dash screenshot of log: https://user-images.githubusercontent.com/89889704/134977896-7a4a2457-e4c4-4d30-9eb7-8eac60e4d524.png video of bug: https://user-images.githubusercontent.com/89889704/134979056-653976d3-ec83-44c5-948a-4ee8baac2fa7.mp4 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-38.42-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Tue Oct 26 19:10:25 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-10-26 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1948893 Title: Application grid fails to appear or disappear Status in gnome-shell package in Ubuntu: New Bug description: 3.38.4 What you expected to happen: gnome-shell application grid to behave normally What actually happened: Upon clicking the show applications button once and reopening overview, applications do not show up. When clicking the button twice to open/close the application view, the grid will briefly flash on second click, and after closing and reopening overview the grid will persist in the main overview behind open windows. This bug seems to be triggered by extensions such as dash-to-panel when configuring settings to use the default gnome-dash/applications button and disabling the button on the panel. Because this bug is very similar to https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1922353 which was also triggered by the same extension for many users, it seems appropriate to report here. I've recreated this bug on ubuntu 21.04 with vanilla gnome as well as pop_os 21.04 and ubuntu 21.04 with default extensions disabled. Error log: value "nan" of type 'gfloat' is invalid or out of range for property 'translation-x' of type 'gfloat' value "nan" of type 'gfloat' is invalid or out of range for property 'translation-y' of type 'gfloat' value "-nan" of type 'gdouble' is invalid or out of range for property 'value' of type 'gdouble' Steps to recreate: 1) Disable any built-in extensions that modify gnome-shell 2) Install and enable dash-to-panel, toggle 'show applications button' off and 'activities button' on and enable 'keep original gnome-shell dash' 3) Restart shell and click show applications button on the dash screenshot of log: https://user-images.githubusercontent.com/89889704/134977896-7a4a2457-e4c4-4d30-9eb7-8eac60e4d524.png video of bug: https://user-images.githubusercontent.com/89889704/134979056-653976d3-ec83-44c5-948a-4ee8baac2fa7.mp4 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package:
[Desktop-packages] [Bug 1948893] [NEW] Application grid fails to appear or disappear
Public bug reported: 3.38.4.1 What you expected to happen: gnome-shell application grid to behave normally What actually happened: Upon clicking the show applications button once and reopening overview, applications do not show up. When clicking the button twice to open/close the application view, the grid will briefly flash on second click, and after closing and reopening overview the grid will persist in the main overview behind open windows. This bug seems to be triggered by extensions such as dash-to-panel when configuring settings to use the default gnome-dash/applications button and disabling the button on the panel. Because this bug is very similar to https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922353 which was also triggered by the same extension for many users, it seems appropriate to report here. I've recreated this bug on ubuntu 21.04 with vanilla gnome as well as pop_os 21.04 and ubuntu 21.04 with default extensions disabled. Error log: value "nan" of type 'gfloat' is invalid or out of range for property 'translation-x' of type 'gfloat' value "nan" of type 'gfloat' is invalid or out of range for property 'translation-y' of type 'gfloat' value "-nan" of type 'gdouble' is invalid or out of range for property 'value' of type 'gdouble' Steps to recreate: 1) Disable any built-in extensions that modify gnome-shell 2) Install and enable dash-to-panel, toggle 'show applications button' off and 'activities button' on and enable 'keep original gnome-shell dash' 3) Restart shell and click show applications button on the dash screenshot of log: https://user-images.githubusercontent.com/89889704/134977896-7a4a2457-e4c4-4d30-9eb7-8eac60e4d524.png video of bug: https://user-images.githubusercontent.com/89889704/134979056-653976d3-ec83-44c5-948a-4ee8baac2fa7.mp4 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-38.42-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Tue Oct 26 19:10:25 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-10-26 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1948893 Title: Application grid fails to appear or disappear Status in gnome-shell package in Ubuntu: New Bug description: 3.38.4.1 What you expected to happen: gnome-shell application grid to behave normally What actually happened: Upon clicking the show applications button once and reopening overview, applications do not show up. When clicking the button twice to open/close the application view, the grid will briefly flash on second click, and after closing and reopening overview the grid will persist in the main overview behind open windows. This bug seems to be triggered by extensions such as dash-to-panel when configuring settings to use the default gnome-dash/applications button and disabling the button on the panel. Because this bug is very similar to https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1922353 which was also triggered by the same extension for many users, it seems appropriate to report here. I've recreated this bug on ubuntu 21.04 with vanilla gnome as well as pop_os 21.04 and ubuntu 21.04 with default extensions disabled. Error log: value "nan" of type 'gfloat' is invalid or out of range for property 'translation-x' of type 'gfloat' value "nan" of type 'gfloat' is invalid or out of range for property 'translation-y' of type 'gfloat' value "-nan" of type 'gdouble' is invalid or out of range for property 'value' of type 'gdouble' Steps to recreate: 1) Disable any built-in extensions that modify gnome-shell 2) Install and enable dash-to-panel, toggle 'show applications button' off and 'activities button' on and enable 'keep original gnome-shell dash' 3) Restart shell and click show applications button on the dash screenshot of log: https://user-images.githubusercontent.com/89889704/134977896-7a4a2457-e4c4-4d30-9eb7-8eac60e4d524.png video of bug: https://user-images.githubusercontent.com/89889704/134979056-653976d3-ec83-44c5-948a-4ee8baac2fa7.mp4 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-38.42-generic 5.11.22 Uname:
[Desktop-packages] [Bug 1948641] Re: can not change dock bar position
I've made a screencast. ** Attachment added: "change_posistion.webm" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1948641/+attachment/5536354/+files/change_posistion.webm -- 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/1948641 Title: can not change dock bar position Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: dock bar is fixed at the bottom. when u want to change the pisition, is is still fixed at the bottom. method: settings->appearence->dock->position ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Mon Oct 25 15:45:45 2021 DistUpgraded: 2021-10-22 13:55:14,850 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05ca] InstallationDate: Installed on 2018-04-28 (1276 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Latitude E7240 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=794fdd3e-74af-4db0-8e0a-ca94eb02e241 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2021-10-22 (3 days ago) dmi.bios.date: 02/01/2018 dmi.bios.release: 65.25 dmi.bios.vendor: Dell Inc. dmi.bios.version: A25 dmi.board.name: 08230Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA25:bd02/01/2018:br65.25:svnDellInc.:pnLatitudeE7240:pvr00:rvnDellInc.:rn08230Y:rvrA00:cvnDellInc.:ct9:cvr:sku05CA: dmi.product.name: Latitude E7240 dmi.product.sku: 05CA dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.1+21.10.20210501-0ubuntu1 version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1948641/+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.
Yes, (3) is not expected to change existing behavior. -- 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 ** 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. [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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+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 1781810] Re: Plank dock is not showing an indicator when a certain application is open anymore and when an application that is open is clicked on the dock, a new instance of it
Thank you for the information. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/1781810 Title: Plank dock is not showing an indicator when a certain application is open anymore and when an application that is open is clicked on the dock, a new instance of it is opened Status in BAMF: Expired Status in Plank: Expired Status in bamf package in Ubuntu: Expired Status in plank package in Ubuntu: Expired Bug description: Plank version: 0.11.4 Distribution: Ubuntu MATE 18.04 DE: MATE Desktop Window manager: Marco Video card: Intel HD Graphics 4000 Plank comes installed with the system by default When i used Ubuntu MATE 16.04 it didn't happen. I had an indicator that the application i was clicking on was open and when i clicked it, it would be restored if it was minimized and it will be minimized if it was maximized or just being shown on the screen but on this version, even if the application is minimized or maximized, when i click on its icon, first of all, i can't see that "application open" indicator below its icon anymore(Only below the Plank icon) and second of all, Plank will open a new instance of that same application. I recorded a video showing you what i am talking about. And also, sometimes when i click on the icons on the dock, i won't have that visual feedback, that "little jump" of the icon i click. That's very important as well otherwise, i think nothing happened. That's all. I really like Plank and it is a great application. Thanks for it. Best wishes To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1781810/+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.
Ok. For clarity, my understanding of these patches are that they do the following things: 1) Add a feature to ModemManager to support uploading firmware to these modems 2) Increase a timeout that was found to be insufficient when doing a firmware update 3) Add a bunch of mappings from SIM->Carrier And then in response to potential concerns: (1) is a straight feature addition, and the associated code will only be called if an external component connects to modemmanager requesting a firmware upload. This is not expected to change any existing behaviours. (2) is low-risk It's not clear to me whether (3) is expected to change existing behaviours at all. Is this understanding correct? Assuming (3) is not expected to change existing behaviour this looks like it would be acceptable under the hardware-enablement SRU policy. -- 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 ** 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. [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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+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 1948813] Re: cant connect to second monitor
Thanks for the bug report. The problem appears to be that the nvidia-470 kernel driver loaded and then quickly unloaded two seconds later. I don't know why that would happen... Maybe look in the 'Additional Drivers' app and uninstall the 470 driver, try 460 or 465 instead? ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-470 (Ubuntu) ** Summary changed: - cant connect to second monitor + Nvidia-470 kernel driver loads then unloads during boot on GTX 1050 Mobile. No driver loaded in the end. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1948813 Title: Nvidia-470 kernel driver loads then unloads during boot on GTX 1050 Mobile. No driver loaded in the end. Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: I lost projecting to my second monitor while updating in ubuntu 20 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 26 07:55:42 2021 DistUpgraded: 2021-10-15 08:30:35,667 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 5.4.0-89-generic, x86_64: installed nvidia, 470.74, 5.4.0-89-generic, x86_64: installed virtualbox, 6.1.26, 5.4.0-88-generic, x86_64: installed virtualbox, 6.1.26, 5.4.0-89-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics 630 (Mobile) [1025:1264] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev ff) (prog-if ff) InstallationDate: Installed on 2021-09-21 (34 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Acer Nitro AN515-52 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=c4de9279-4774-410d-be28-7e7083e0c939 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-10-15 (10 days ago) dmi.bios.date: 08/05/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.28 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Freed_CFS dmi.board.vendor: CFL dmi.board.version: V1.28 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.28 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.28:bd08/05/2019:svnAcer:pnNitroAN515-52:pvrV1.28:rvnCFL:rnFreed_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28: dmi.product.family: Acer Nitro 5 dmi.product.name: Nitro AN515-52 dmi.product.sku: dmi.product.version: V1.28 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1948813/+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 1948829] Re: AppIndicator icon looks squashed in Ubuntu focal
** Tags added: focal ** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension- appindicator (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1948829 Title: AppIndicator icon looks squashed in Ubuntu focal Status in gnome-shell-extension-appindicator package in Ubuntu: New Bug description: Release of Ubuntu: Ubuntu 20.04 (focal) Version of gnome-shell: 3.36.9-0ubuntu0.20.04.2 I implemented a simple AppIndicator in python which contains an icon and a label. The icon image is SVG file and image size is 300x200 in px. When running the AppIndicator app, the icon should be scaled based on AppIndicator bar height and keeps aspect ratio, but only image height is scaled and image width still keeps 300px so the icon looks squashed on AppIndicator bar. The same AppIndicator app works fine in Ubuntu 18.04 (bionic, gnome- shell version: 3.28.4-0ubuntu18.04.7), and both weight and height are scaled and keeps aspect ratio. So this issue is only happened in gnome-shell 3.36. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1948829/+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 1948778] Re: Random flashes in gnome-shell
Thanks. Please try these fixes separately so we can see which one if any avoids the problem: 1. Edit /etc/default/grub and change: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_psr=0" 2. Run: sudo update-grub 3. Reboot. 1. Edit /etc/environment and add a line: MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 2. Reboot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1948778 Title: Random flashes in gnome-shell Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 22.04 development branch up to date to latest @ 26/10/2021 kernel 5.13.0-19-generic While working around on the desktop i'm getting short screen flashes like a screenshot style i cant reproduce them, they seem to come on random like every few minutes journal logs dont record anything while they occur this only happens on wayland, tested a long session on xorg where they dont occur ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 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: Tue Oct 26 11:12:30 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2021-10-23T19:12:47.175230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948778/+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 1948647] Re: Screeen recording via Ctrl+Alt+Shift+R creates empty webm file, orange circle persists
** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4725 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1948647 Title: Screeen recording via Ctrl+Alt+Shift+R creates empty webm file, orange circle persists Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: Running 21.10 and Gnome 40.4 the screen recording no longer works with the Ctrl+Alt+Shift+R keystroke. A .webm file does appear in the Videos folder but it is empty. The orange circle does appear in the upper corner, but it will not go away. Further Ctrl+Alt+Shift+R strokes do not make a new .webm file or remove the orange circle. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 Uname: Linux 5.15.0-rc4-soffixes x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 25 11:11:13 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-10-12 (12 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 40.5-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2021-10-14 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1948647/+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 1781810] Re: Plank dock is not showing an indicator when a certain application is open anymore and when an application that is open is clicked on the dock, a new instance of it
> Well, is the bamf bug fixed, then? No, I still have this issue. Workaround: plank > /dev/null & sleep 1 systemctl --user restart bamfdaemon.service -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/1781810 Title: Plank dock is not showing an indicator when a certain application is open anymore and when an application that is open is clicked on the dock, a new instance of it is opened Status in BAMF: Expired Status in Plank: Expired Status in bamf package in Ubuntu: Expired Status in plank package in Ubuntu: Expired Bug description: Plank version: 0.11.4 Distribution: Ubuntu MATE 18.04 DE: MATE Desktop Window manager: Marco Video card: Intel HD Graphics 4000 Plank comes installed with the system by default When i used Ubuntu MATE 16.04 it didn't happen. I had an indicator that the application i was clicking on was open and when i clicked it, it would be restored if it was minimized and it will be minimized if it was maximized or just being shown on the screen but on this version, even if the application is minimized or maximized, when i click on its icon, first of all, i can't see that "application open" indicator below its icon anymore(Only below the Plank icon) and second of all, Plank will open a new instance of that same application. I recorded a video showing you what i am talking about. And also, sometimes when i click on the icons on the dock, i won't have that visual feedback, that "little jump" of the icon i click. That's very important as well otherwise, i think nothing happened. That's all. I really like Plank and it is a great application. Thanks for it. Best wishes To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1781810/+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 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy)
** Description changed: gir1.2-signon-1.0 from groovy gir1.2-signon-2.0 from hirsute above two packages ship the same file /usr/lib/python3/dist- packages/gi/overrides/Signon.py without specifying how to resolve the conflict. + + [Test Case] + This can be simply tested with a focal schroot: + 1) apt-get install vim libsignon-glib-dev + 2) edit /etc/apt/sources.list replacing focal with hirsute + 3) apt-get update + 4) apt-get install libsignon-glib-dev + + With the version of libsignon-glib-dev from -proposed you'll no longer + receive the 'dpkg: error' from below. Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 Errors were encountered while processing: /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Probably needs a conflicts/replaces dependency added to the newer hirsute package. + + [Regression Potential] + We are adding a replaces with gir1.2-signon-1.0 so anything that depends on that package would be broken but given that that package is no longer available after focal that seems fine. ** Also affects: libsignon-glib (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: libsignon-glib (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: libsignon-glib (Ubuntu Hirsute) Status: New => In Progress ** Changed in: libsignon-glib (Ubuntu Impish) Status: New => In Progress ** Changed in: libsignon-glib (Ubuntu Hirsute) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: libsignon-glib (Ubuntu Impish) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsignon-glib in Ubuntu. https://bugs.launchpad.net/bugs/1916250 Title: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy) Status in libsignon-glib package in Ubuntu: Fix Released Status in libsignon-glib source package in Hirsute: In Progress Status in libsignon-glib source package in Impish: In Progress Bug description: gir1.2-signon-1.0 from groovy gir1.2-signon-2.0 from hirsute above two packages ship the same file /usr/lib/python3/dist- packages/gi/overrides/Signon.py without specifying how to resolve the conflict. [Test Case] This can be simply tested with a focal schroot: 1) apt-get install vim libsignon-glib-dev 2) edit /etc/apt/sources.list replacing focal with hirsute 3) apt-get update 4) apt-get install libsignon-glib-dev With the version of libsignon-glib-dev from -proposed you'll no longer receive the 'dpkg: error' from below. Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 Errors were encountered while processing: /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Probably needs a conflicts/replaces dependency added to the newer hirsute package. [Regression Potential] We are adding a replaces with gir1.2-signon-1.0 so anything that depends on that package would be broken but given that that package is no longer available after focal that seems fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsignon-glib/+bug/1916250/+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 1945296] Re: To support goodix fp device [27C6:639C]
** Also affects: libfprint (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: libfprint (Ubuntu Focal) Status: New => Incomplete ** Also affects: libfprint (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: libfprint (Ubuntu Impish) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1945296 Title: To support goodix fp device [27C6:639C] Status in OEM Priority Project: New Status in libfprint package in Ubuntu: Incomplete Status in libfprint source package in Focal: Incomplete Status in libfprint source package in Impish: Incomplete Bug description: https://gitlab.freedesktop.org/libfprint/libfprint/-/blob/master/libfprint/drivers/goodixmoc/goodix.c#L1505 This ID is included in upstream. [Impact] * Devices have goodix [27c6:639c] fingerprint component will get supported. [Test Plan] * Find a machine with this fingerprint device * Launch `settings` and enable `Fingerprint Login` * Enroll finger and then logout * Login system with enrolled finger [Where problems could occur] * A lot of fingerprint ids is supported in this version, we didn't test all combination. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1945296/+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 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
snap is cancer -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in Mozilla Firefox: New Status in KeePassXC Snap Builds: Unknown Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: Confirmed Status in goopg package in Ubuntu: Confirmed Status in kdeconnect package in Ubuntu: Confirmed Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1741074/+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 1945298] Re: To support goodix fp device [27C6:63BC]
** Also affects: libfprint (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: libfprint (Ubuntu Impish) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1945298 Title: To support goodix fp device [27C6:63BC] Status in OEM Priority Project: New Status in libfprint package in Ubuntu: New Status in libfprint source package in Focal: New Status in libfprint source package in Impish: New Bug description: https://gitlab.freedesktop.org/libfprint/libfprint/-/blob/master/libfprint/drivers/goodixmoc/goodix.c#L1507 This ID is included in upstream. [Impact] * Devices have goodix [27c6:63bc] fingerprint component will get supported. [Test Plan] * Find a machine with this fingerprint device * Launch `settings` and enable `Fingerprint Login` * Enroll finger and then logout * Login system with enrolled finger [Where problems could occur] * A lot of fingerprint ids is supported in this version, we didn't test all combination. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1945298/+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 1942685] Re: pulseaudio crashed with SIGSEGV in _IceTransClose()
Hello Brian (brian-murray) Please see my comment #9 above - i have run numerous tests on Xubuntu Impish and have been unable to reproduce this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1942685 Title: pulseaudio crashed with SIGSEGV in _IceTransClose() Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Impish: Fix Committed Bug description: * Impact The pulseaudio service sometime segfaults on session closing which trigger a bug report dialog * Test plan Log out of a desktop session and back in, there should be no error prompt The issue isn't triggered only randomly it seems so it might be easier to check that reports stop on https://errors.ubuntu.com/problem/877172e07ed9f86b0674cd458a5aaf24b37fb01e * Where problems could occur The change is in the X session closing handling so shouldn't impact on normal use, if incorrect the fix could lead to increase the chance of hitting the segfault when an Xsession is closed --- Installing Xubuntu Impish daily ISO 04092021 After install I rebooted - applied updates and then rebooted again- the errors (pulseaudio crashed with SIGSEGV in _IceTransClose() ) occurred after logging in. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kx 847 F pulseaudio CasperMD5CheckResult: pass Date: Sat Sep 4 16:43:45 2021 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2021-09-04 (0 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210904) ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal Signal: 11 SourcePackage: pulseaudio StacktraceTop: _IceTransClose () from /lib/x86_64-linux-gnu/libICE.so.6 _IceFreeConnection () from /lib/x86_64-linux-gnu/libICE.so.6 IceCloseConnection () from /lib/x86_64-linux-gnu/libICE.so.6 SmcCloseConnection () from /lib/x86_64-linux-gnu/libSM.so.6 ?? () from /usr/lib/pulse-15.0+dfsg1/modules/module-x11-xsmp.so Title: pulseaudio crashed with SIGSEGV in _IceTransClose() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 12/23/2020 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN51WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V14-IIL dmi.ec.firmware.release: 1.51 dmi.modalias: dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82C4:pvrLenovoV14-IIL:skuLENOVO_MT_82C4_BU_idea_FM_V14-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV14-IIL: dmi.product.family: V14-IIL dmi.product.name: 82C4 dmi.product.sku: LENOVO_MT_82C4_BU_idea_FM_V14-IIL dmi.product.version: Lenovo V14-IIL dmi.sys.vendor: LENOVO separator: To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1942685/+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 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded after OS upgrade
Related question: https://askubuntu.com/q/1370465/21005 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Nvidia 340 Xorg driver is installed but not loaded after OS upgrade Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: I tried both nouveau and nvidia-340 drivers. It used to work at least by the latter one in Xubuntu 18.04, even with HWE kernel When using the nvidia-340 driver: $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200 default connected 1920x1200+0+0 0mm x 0mm 1920x1200 77.00* A device is connected in HDMI and xrand does not even list the connector. When using nouveau, HDMI is listed but it shows as disconnected. WORKAROUND when using nvidia driver: Log out of session. Then lightdm screen shows on both monitors. And if I then log in to a session, the extrernal monitor works there, too. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Wed Oct 13 16:27:00 2021 DistUpgraded: 2021-10-13 15:24:05,135 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2019-05-08 (888 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=dd272475-45e5-4fca-b9ab-1b1f3f3015bd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-10-13 (0 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+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 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded after OS upgrade
Maybe lightdm could do something differently? What causes HDMI to appear when I log out of session? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Nvidia 340 Xorg driver is installed but not loaded after OS upgrade Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: I tried both nouveau and nvidia-340 drivers. It used to work at least by the latter one in Xubuntu 18.04, even with HWE kernel When using the nvidia-340 driver: $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200 default connected 1920x1200+0+0 0mm x 0mm 1920x1200 77.00* A device is connected in HDMI and xrand does not even list the connector. When using nouveau, HDMI is listed but it shows as disconnected. WORKAROUND when using nvidia driver: Log out of session. Then lightdm screen shows on both monitors. And if I then log in to a session, the extrernal monitor works there, too. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Wed Oct 13 16:27:00 2021 DistUpgraded: 2021-10-13 15:24:05,135 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2019-05-08 (888 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=dd272475-45e5-4fca-b9ab-1b1f3f3015bd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-10-13 (0 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+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 1948874] Re: Some Nautilus tooltips open somewhere else than near the hovered button
** Attachment added: "`New Tab` tooltip behavior" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1948874/+attachment/5536329/+files/Screenshot%20from%202021-10-22%2010-16-26.png -- 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/1948874 Title: Some Nautilus tooltips open somewhere else than near the hovered button Status in nautilus package in Ubuntu: New Bug description: I can only include a single image This also happens with the other five buttons in the same submenu, and the other three buttons in the submenu right next to the one opened in the image This does not occur when running Ubuntu CD images ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 26 22:10:40 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'180' b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.preferences' b'click-policy' b"'single'" b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" InstallationDate: Installed on 2021-10-10 (16 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince40.4-2 file-roller 3.40.0-2 nautilus-extension-gnome-terminal 3.38.1-1ubuntu2 nautilus-share0.7.3-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1948874/+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 1948874] Re: Some Nautilus tooltips open somewhere else than near the hovered button
** Attachment added: "`New Window` tooltip behavior" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1948874/+attachment/5536330/+files/Screenshot%20from%202021-10-22%2010-14-34.png ** Description changed: I can only include a single image This also happens with the other five buttons in the same submenu, and the other three buttons in the submenu right next to the one opened in the image This does not occur when running Ubuntu CD images + ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 26 22:10:40 2021 GsettingsChanges: - b'org.gnome.nautilus.window-state' b'sidebar-width' b'180' - b'org.gnome.nautilus.window-state' b'maximized' b'true' - b'org.gnome.nautilus.preferences' b'click-policy' b"'single'" - b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" - b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" + b'org.gnome.nautilus.window-state' b'sidebar-width' b'180' + b'org.gnome.nautilus.window-state' b'maximized' b'true' + b'org.gnome.nautilus.preferences' b'click-policy' b"'single'" + b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" + b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" InstallationDate: Installed on 2021-10-10 (16 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: - evince40.4-2 - file-roller 3.40.0-2 - nautilus-extension-gnome-terminal 3.38.1-1ubuntu2 - nautilus-share0.7.3-2ubuntu4 + evince40.4-2 + file-roller 3.40.0-2 + nautilus-extension-gnome-terminal 3.38.1-1ubuntu2 + nautilus-share0.7.3-2ubuntu4 -- 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/1948874 Title: Some Nautilus tooltips open somewhere else than near the hovered button Status in nautilus package in Ubuntu: New Bug description: I can only include a single image This also happens with the other five buttons in the same submenu, and the other three buttons in the submenu right next to the one opened in the image This does not occur when running Ubuntu CD images ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 26 22:10:40 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'180' b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.preferences' b'click-policy' b"'single'" b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" InstallationDate: Installed on 2021-10-10 (16 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince40.4-2 file-roller 3.40.0-2 nautilus-extension-gnome-terminal 3.38.1-1ubuntu2 nautilus-share0.7.3-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1948874/+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 1948874] [NEW] Some Nautilus tooltips open somewhere else than near the hovered button
Public bug reported: I can only include a single image This also happens with the other five buttons in the same submenu, and the other three buttons in the submenu right next to the one opened in the image This does not occur when running Ubuntu CD images ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 26 22:10:40 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'180' b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.preferences' b'click-policy' b"'single'" b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" InstallationDate: Installed on 2021-10-10 (16 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince40.4-2 file-roller 3.40.0-2 nautilus-extension-gnome-terminal 3.38.1-1ubuntu2 nautilus-share0.7.3-2ubuntu4 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish third-party-packages wayland-session ** Attachment added: "Screenshot from 2021-10-22 10-16-39.png" https://bugs.launchpad.net/bugs/1948874/+attachment/5536325/+files/Screenshot%20from%202021-10-22%2010-16-39.png -- 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/1948874 Title: Some Nautilus tooltips open somewhere else than near the hovered button Status in nautilus package in Ubuntu: New Bug description: I can only include a single image This also happens with the other five buttons in the same submenu, and the other three buttons in the submenu right next to the one opened in the image This does not occur when running Ubuntu CD images ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 26 22:10:40 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'180' b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.preferences' b'click-policy' b"'single'" b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" InstallationDate: Installed on 2021-10-10 (16 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince40.4-2 file-roller 3.40.0-2 nautilus-extension-gnome-terminal 3.38.1-1ubuntu2 nautilus-share0.7.3-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1948874/+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 1942685] Re: pulseaudio crashed with SIGSEGV in _IceTransClose()
Hello Leó, or anyone else affected, Accepted pulseaudio into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pulseaudio/1:15.0+dfsg1-1ubuntu2.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: pulseaudio (Ubuntu Impish) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1942685 Title: pulseaudio crashed with SIGSEGV in _IceTransClose() Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Impish: Fix Committed Bug description: * Impact The pulseaudio service sometime segfaults on session closing which trigger a bug report dialog * Test plan Log out of a desktop session and back in, there should be no error prompt The issue isn't triggered only randomly it seems so it might be easier to check that reports stop on https://errors.ubuntu.com/problem/877172e07ed9f86b0674cd458a5aaf24b37fb01e * Where problems could occur The change is in the X session closing handling so shouldn't impact on normal use, if incorrect the fix could lead to increase the chance of hitting the segfault when an Xsession is closed --- Installing Xubuntu Impish daily ISO 04092021 After install I rebooted - applied updates and then rebooted again- the errors (pulseaudio crashed with SIGSEGV in _IceTransClose() ) occurred after logging in. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kx 847 F pulseaudio CasperMD5CheckResult: pass Date: Sat Sep 4 16:43:45 2021 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2021-09-04 (0 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210904) ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal Signal: 11 SourcePackage: pulseaudio StacktraceTop: _IceTransClose () from /lib/x86_64-linux-gnu/libICE.so.6 _IceFreeConnection () from /lib/x86_64-linux-gnu/libICE.so.6 IceCloseConnection () from /lib/x86_64-linux-gnu/libICE.so.6 SmcCloseConnection () from /lib/x86_64-linux-gnu/libSM.so.6 ?? () from /usr/lib/pulse-15.0+dfsg1/modules/module-x11-xsmp.so Title: pulseaudio crashed with SIGSEGV in _IceTransClose() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 12/23/2020 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN51WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V14-IIL dmi.ec.firmware.release: 1.51 dmi.modalias: dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82C4:pvrLenovoV14-IIL:skuLENOVO_MT_82C4_BU_idea_FM_V14-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV14-IIL: dmi.product.family: V14-IIL dmi.product.name: 82C4 dmi.product.sku: LENOVO_MT_82C4_BU_idea_FM_V14-IIL dmi.product.version: Lenovo V14-IIL dmi.sys.vendor: LENOVO separator: To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1942685/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1917178] Re: As of today in hirsute no longer possible to use open-fprintd
** Changed in: fprintd (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fprintd in Ubuntu. https://bugs.launchpad.net/bugs/1917178 Title: As of today in hirsute no longer possible to use open-fprintd Status in fprintd package in Ubuntu: Won't Fix Bug description: It appears that fprintd-clients was replaced with libpam-fprintd, and libpam-fprintd can't be installed without fprintd. I can't use fprintd because it's incompatible with my fingerprint reader (Lenovo Thinkpad X1 Carbon 6th gen). Prior to today I was successfully using open-fprintd. Now, however, I had to uninstall open-fprintd and install libpam- fprintd to be able to log in (see bug 1917175), and I am unable to put open-fprintd back because that will force fprintd to uninstall, which will force libpam-fprintd to uninstall, which will make me unable to log in because pam_fprintd.so will disappear. This isn't great. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: fprintd 1.90.9-1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 27 17:16:27 2021 InstallationDate: Installed on 2019-08-16 (561 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: fprintd UpgradeStatus: Upgraded to hirsute on 2021-02-20 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1917178/+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 1946143] Re: Apply upstream patches to display 5G NSA status
This bug was fixed in the package libqmi - 1.28.6-2ubuntu1 --- libqmi (1.28.6-2ubuntu1) impish; urgency=medium * Apply upstream patch to display the 5G NSA status. (lp: #1946143) -- Jerry Lee Wed, 06 Oct 2021 16:21:40 +0800 ** Changed in: libqmi (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libqmi in Ubuntu. https://bugs.launchpad.net/bugs/1946143 Title: Apply upstream patches to display 5G NSA status Status in OEM Priority Project: In Progress Status in libqmi package in Ubuntu: Fix Released Status in libqmi source package in Focal: Fix Released Status in libqmi source package in Hirsute: Fix Released Status in libqmi source package in Impish: Fix Released Bug description: [Impact] The 5G NSA status can not be displayed in the libqmi version 1.28.6-1. (LP#1937012) The 5G NSA status is supported in the libqmi version 1.30.2. The requested upstream patches are listed as below: * 5G NSA status patches https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/commit/29905223c5ae6e5e4ef9246dd9dd4d01b2819d9a * qmicli,nas: flag as 'n/a' the 5G NSA signal quality if not connected https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/commit/b05df7b658f9cfb4c5e74a3e07913de689914a8f [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Verify if the field “5G NSA Available: ” can be displayed via executing: $ sudo qmicli --device=/dev/wwan0p2MBIM --device-open-proxy --nas-get-system-info ... 5G NSA Available: 'no' ... [Where problems could occur] The requested upstream patches are for displaying the status information of 5G NSA network. This should not affect existing generic functions. [Other Info] The latest version of libqmi suit can display the 5G NSA status. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946143/+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 1930188] Re: Acer Aspire 5 sound driver issues
This bug was fixed in the package alsa-ucm-conf - 1.2.4-2ubuntu5 --- alsa-ucm-conf (1.2.4-2ubuntu5) impish; urgency=medium * d/p/0008-HDA-Intel-add-Boost-volume-control-for-Headset-Mic.patch Add Mic Boost in the HDA Intel ucm, after this change, when users adjust input volume, the Mic Boost could be adjusted as well as Capture Volume. (LP: #1930188) -- Hui Wang Tue, 14 Sep 2021 10:54:28 +0800 ** Changed in: alsa-ucm-conf (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: Fix Released Status in alsa-ucm-conf source package in Impish: Fix Released Status in linux source package in Impish: Fix Released Status in pulseaudio source package in Impish: Fix Released Bug description: SRU Justification for alsa-ucm-conf: [Impact] On the machines with the sof audio driver, users could adjust the input volume from UI, but this only adjusts the "Capture Volume", the "Mic Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture Volume" to max, the recorded volume is still very low. [Fix] Backport a upstream patch, the patch adds the "Mic Boost" into the ucm [Test] plug a headset, make sure the headset-mic is the active input device, adjust the input volume to %20, open a terminal and run alsamixer, check the "Capture Volume" and "Mic Boost" value, then adjust the input volume to 80%, check those values and we could see both values are changed. [Where problems could occur] This patch could make the parse of input volume control fail, then the input volume can't be changed anymore when users adjust the volume from UI. But this possibility is very low, I tested this patch on many lenovo and dell machines with sof audio driver, all worked well. SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU for the focal kernel. [Impact] Users plug headphone and Mic to the audio jacks, but the system can't detect them, and couldn't output sound through headphone and record sound through Mic. [Fix] Backport a upstream patch, this will set the Mic to auto-detection mode and set the headphone to left location. [Test] Plug a headset to the headset audio jack, both headphone and mic could be detected. And output the sound to headphone, could hear the sound, record the sound through Mic, the sound could be recorded. [Where problems could occur] The patch is specific to Acer Aspire 5 machine, if it could introduce regression, it will make the audio like internal mic and internal spk stop working. But this possibility is very low. Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR with
[Desktop-packages] [Bug 349943] Re: Screen blinks randomly on external monitor
Oh, thanks for all of you reported this issue. I'm using Ubuntu20.04.2 now, and encountered the exactly same issue as you met about 12 years ago on Ubuntu9.04. It seems this is a very old bug in Ubuntu or linux bug on its HDMI driver. And because not so many people using external HDMI monitor, so this issue couldn't be paid attention to for linux/Ubuntu engineering team. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/349943 Title: Screen blinks randomly on external monitor Status in xorg package in Ubuntu: Won't Fix Bug description: Hardware: Asus F8Va laptop (Core 2 Duo P8600, ATI HD3650, 1440x900) OS: Ubuntu 9.04 beta x64 (Wubi installation inside Windows Vista Home Premium x64 SP1) External monitor (Samsung SyncMaster 2493HM, 1920x1200), connected via HDMI, blinks several times a minute, randomly. When there is no user activity, it doesn't seem to blink however. By "blinking" I mean, the monitor goes off and then on, like it usually does when it changes resolution, only resolution doesn't change. Also, when I move windows around, thin horizontal stripes flash in fraction of second from time to time (only on external monitor). Screen configuration: Samsung 24": On Resolution: 1920x1200 Refresh rate: 60 Hz Rotation: Normal Laptop 14": On Resolution: 1440x900 Refresh rate: 67 Hz Rotation: Normal Mirror screens: unchecked Relative position of screens (physical and in Display Preferences) laptop screen below the external screen, centred. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/349943/+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 1948829] [NEW] AppIndicator icon looks squashed in Ubuntu focal
Public bug reported: Release of Ubuntu: Ubuntu 20.04 (focal) Version of gnome-shell: 3.36.9-0ubuntu0.20.04.2 I implemented a simple AppIndicator in python which contains an icon and a label. The icon image is SVG file and image size is 300x200 in px. When running the AppIndicator app, the icon should be scaled based on AppIndicator bar height and keeps aspect ratio, but only image height is scaled and image width still keeps 300px so the icon looks squashed on AppIndicator bar. The same AppIndicator app works fine in Ubuntu 18.04 (bionic, gnome- shell version: 3.28.4-0ubuntu18.04.7), and both weight and height are scaled and keeps aspect ratio. So this issue is only happened in gnome- shell 3.36. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1948829 Title: AppIndicator icon looks squashed in Ubuntu focal Status in gnome-shell package in Ubuntu: New Bug description: Release of Ubuntu: Ubuntu 20.04 (focal) Version of gnome-shell: 3.36.9-0ubuntu0.20.04.2 I implemented a simple AppIndicator in python which contains an icon and a label. The icon image is SVG file and image size is 300x200 in px. When running the AppIndicator app, the icon should be scaled based on AppIndicator bar height and keeps aspect ratio, but only image height is scaled and image width still keeps 300px so the icon looks squashed on AppIndicator bar. The same AppIndicator app works fine in Ubuntu 18.04 (bionic, gnome- shell version: 3.28.4-0ubuntu18.04.7), and both weight and height are scaled and keeps aspect ratio. So this issue is only happened in gnome-shell 3.36. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948829/+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 1563781] Re: Flickering and invisible mouse pointer after wakeup from suspend
** Changed in: lightdm Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1563781 Title: Flickering and invisible mouse pointer after wakeup from suspend Status in Light Display Manager: Invalid Status in lightdm package in Ubuntu: Expired Bug description: Hello, I run Arch linux on a Thinkpad X230 uname -a Linux schwarzbaer 4.4.5-1-ARCH #1 SMP PREEMPT Thu Mar 10 07:38:19 CET 2016 x86_64 GNU/Linux I use xmonad and a custom .xinitrc to start my session. I run `light- locker --lock-on-suspend` there and xmonad. - When I wake up my laptop from suspend, the login screen shows up as expected. - After about 2 second, the screen flickers once and the login screen shows up again. - If I start typing a password before the flickering, the input field will be reset upon flickering. Usually I end up with my password half-typed and a wrong password notice. - After logging back into the session, there is no mouse pointer. - Going to VT1 and back to VT7 restores the pointer. Please find the lightdm and journalctl logs below. I am happy to provide more logs and info. Thanks, Dominik The lightdm log: [+14840.86s] DEBUG: Seat seat0: Creating greeter session [+14840.86s] DEBUG: Seat seat0: Creating display server of type x [+14840.86s] DEBUG: Using VT 8 [+14840.86s] DEBUG: Seat seat0: Starting local X display on VT 8 [+14840.86s] DEBUG: DisplayServer x-1: Logging to /var/log/lightdm/x-1.log [+14840.86s] DEBUG: DisplayServer x-1: Writing X server authority to /run/lightdm/root/:1 [+14840.86s] DEBUG: DisplayServer x-1: Launching X Server [+14840.86s] DEBUG: Launching process 16458: /usr/sbin/X :1 -seat seat0 -auth /run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch [+14840.86s] DEBUG: DisplayServer x-1: Waiting for ready signal from X server :1 [+14841.11s] DEBUG: Seat seat0 changes active session to [+14841.36s] DEBUG: Got signal 10 from process 16458 [+14841.36s] DEBUG: DisplayServer x-1: Got signal from X server :1 [+14841.36s] DEBUG: DisplayServer x-1: Connecting to XServer :1 [+14841.36s] DEBUG: Seat seat0: Display server ready, starting session authentication [+14841.36s] DEBUG: Session pid=16473: Started with service 'lightdm-greeter', username 'lightdm' [+14841.37s] DEBUG: Session pid=16473: Authentication complete with return value 0: Success [+14841.37s] DEBUG: Seat seat0: Session authenticated, running command [+14841.37s] DEBUG: Session pid=16473: Running command /usr/sbin/lightdm-gtk-greeter [+14841.37s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm [+14841.37s] DEBUG: Session pid=16473: Logging to /var/log/lightdm/x-1-greeter.log [+14841.41s] DEBUG: Activating VT 8 [+14841.41s] DEBUG: Locking login1 session c2 [+14841.41s] DEBUG: Activating login1 session c16 [+14841.41s] DEBUG: Seat seat0 changes active session to c16 [+14841.41s] DEBUG: Session c16 is already active [+14841.58s] DEBUG: Session pid=16473: Greeter connected version=1.16.7 resettable=false [+14841.76s] DEBUG: Session pid=16473: Greeter start authentication for dominik [+14841.76s] DEBUG: Session pid=16510: Started with service 'lightdm', username 'dominik' [+14841.77s] DEBUG: Session pid=16510: Got 1 message(s) from PAM [+14841.77s] DEBUG: Session pid=16473: Prompt greeter with 1 message(s) [+14846.18s] DEBUG: Session pid=16473: Continue authentication [+14846.20s] DEBUG: Session pid=16510: Authentication complete with return value 0: Success [+14846.20s] DEBUG: Session pid=16473: Authenticate result for user dominik: Success [+14846.20s] DEBUG: Session pid=16473: User dominik authorized [+14846.20s] DEBUG: Session pid=16473: Greeter sets language en_US.utf8 [+14846.26s] DEBUG: Session pid=16473: Greeter requests session xmonad-dominik [+14846.26s] DEBUG: Seat seat0: Returning to existing user session dominik [+14846.26s] DEBUG: Unlocking login1 session c2 [+14846.26s] DEBUG: Activating VT 7 [+14846.45s] DEBUG: Seat seat0: Stopping greeter [+14846.45s] DEBUG: Session pid=16473: Sending SIGTERM [+14846.45s] DEBUG: Activating login1 session c2 [+14846.46s] DEBUG: Session pid=16510: Exited with return value 0 [+14846.46s] DEBUG: Seat seat0: Session stopped [+14846.46s] DEBUG: Seat seat0 changes active session to c2 [+14846.46s] DEBUG: Session c2 is already active [+14846.50s] DEBUG: Session pid=16473: Greeter closed communication channel [+14846.50s] DEBUG: Session pid=16473: Exited with return value 0 [+14846.50s] DEBUG: Seat seat0: Session stopped [+14846.50s] DEBUG: Seat seat0: Stopping display server, no sessions require it [+14846.50s] DEBUG: Sending signal 15 to process 16458 [+14846.51s] DEBUG: Process 16458 exited with return value 0 [+14846.51s] DEBUG: DisplayServer x-1: X server stopped [+14846.51s]
[Desktop-packages] [Bug 1196701] Re: cheese crashes on ARM with SEGV
** Changed in: cheese Status: Incomplete => Invalid ** Changed in: cogl Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1196701 Title: cheese crashes on ARM with SEGV Status in AC100_enablement: Expired Status in Cheese: Invalid Status in Cogl: Invalid Status in cheese package in Ubuntu: Expired Bug description: cheese segfaults always when started on Toshiba AC100 (ARM) ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: cheese 3.4.1-0ubuntu2.1 Uname: Linux 3.0.27-1-ac100 armv7l ApportVersion: 2.0.1-0ubuntu17.4 Architecture: armhf CrashCounter: 1 Date: Tue Jul 2 00:46:28 2013 ExecutablePath: /usr/bin/cheese MarkForUpload: True ProcCmdline: cheese ProcEnviron: TERM=xterm SHELL=/bin/bash PATH=(custom, no user) LANG=ru_RU.UTF-8 RelatedPackageVersions: cheese3.4.1-0ubuntu2.1 cheese-common 3.4.1-0ubuntu2.1 Signal: 11 SourcePackage: cheese StacktraceTop: ?? () from /usr/lib/arm-linux-gnueabihf/libcogl.so.9 ?? () from /usr/lib/arm-linux-gnueabihf/libcogl.so.9 ?? () from /usr/lib/arm-linux-gnueabihf/libcogl.so.9 Title: cheese crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo lspci: Error: command ['lspci', '-vvnn'] failed with exit code 1: pcilib: Cannot open /proc/bus/pci lspci: Cannot find any working access method. To manage notifications about this bug go to: https://bugs.launchpad.net/ac100/+bug/1196701/+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 1946143] Re: Apply upstream patches to display 5G NSA status
This bug was fixed in the package libqmi - 1.28.6-1~20.04.1 --- libqmi (1.28.6-1~20.04.1) focal; urgency=medium * Apply upstream patch to display the 5G NSA status. (lp: #1946143) -- Jerry Lee Tue, 05 Oct 2021 20:39:37 +0800 ** Changed in: libqmi (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libqmi in Ubuntu. https://bugs.launchpad.net/bugs/1946143 Title: Apply upstream patches to display 5G NSA status Status in OEM Priority Project: In Progress Status in libqmi package in Ubuntu: Fix Committed Status in libqmi source package in Focal: Fix Released Status in libqmi source package in Hirsute: Fix Released Status in libqmi source package in Impish: Fix Released Bug description: [Impact] The 5G NSA status can not be displayed in the libqmi version 1.28.6-1. (LP#1937012) The 5G NSA status is supported in the libqmi version 1.30.2. The requested upstream patches are listed as below: * 5G NSA status patches https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/commit/29905223c5ae6e5e4ef9246dd9dd4d01b2819d9a * qmicli,nas: flag as 'n/a' the 5G NSA signal quality if not connected https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/commit/b05df7b658f9cfb4c5e74a3e07913de689914a8f [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Verify if the field “5G NSA Available: ” can be displayed via executing: $ sudo qmicli --device=/dev/wwan0p2MBIM --device-open-proxy --nas-get-system-info ... 5G NSA Available: 'no' ... [Where problems could occur] The requested upstream patches are for displaying the status information of 5G NSA network. This should not affect existing generic functions. [Other Info] The latest version of libqmi suit can display the 5G NSA status. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946143/+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 1933828] Re: NTP servers from DHCP are not propagated to timesyncd
was the issue reported and discussed upstream yet? those scripts added to the package sound like downstream workaround we will have to carry and should be a backup plan if the issue can't be properly fixed upstream. And even if a distro hack makes sense it would be better to have it in Debian to reduce or maintainance -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1933828 Title: NTP servers from DHCP are not propagated to timesyncd Status in OEM Priority Project: New Status in network-manager package in Ubuntu: New Status in network-manager source package in Focal: New Bug description: Network manager gets NTP servers from DHCP but do not update timesyncd to use it which keeps using ntp.ubuntu.com. This is a problem on private networks which do not have access to public internet. On this type of network the configuration of timesyncd must be updated manually instead of inheriting the conf from the dhcp servers. This can be integrated with a NM dispatcher script such as below: etc/NetworkManager/dispatcher.d/10-update-timesyncd for example: ==8<=8<=8<=8<=8<== #! /usr/bin/bash [ -n "$CONNECTION_UUID" ] || exit INTERFACE=$1 ACTION=$2 case $ACTION in up | dhcp4-change | dhcp6-change) [ -n "$DHCP4_NTP_SERVERS" ] || exit mkdir -p /etc/systemd/timesyncd.conf.d/ cat< /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf [Time] NTP=$DHCP4_NTP_SERVERS RootDistanceMaxSec=15 EOF systemctl restart systemd-timesyncd ;; down) rm -f /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf systemctl restart systemd-timesyncd ;; esac ==8<=8<=8<=8<=8<== ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 28 14:08:52 2021 InstallationDate: Installed on 2020-05-31 (393 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) RebootRequiredPkgs: linux-image-5.11.0-20-generic linux-base SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933828/+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 1946143] Re: Apply upstream patches to display 5G NSA status
This bug was fixed in the package libqmi - 1.28.6-1~21.04.1 --- libqmi (1.28.6-1~21.04.1) hirsute; urgency=medium * Apply upstream patch to display the 5G NSA status. (lp: #1946143) -- Jerry Lee Tue, 05 Oct 2021 20:59:17 +0800 ** Changed in: libqmi (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libqmi in Ubuntu. https://bugs.launchpad.net/bugs/1946143 Title: Apply upstream patches to display 5G NSA status Status in OEM Priority Project: In Progress Status in libqmi package in Ubuntu: Fix Committed Status in libqmi source package in Focal: Fix Committed Status in libqmi source package in Hirsute: Fix Released Status in libqmi source package in Impish: Fix Released Bug description: [Impact] The 5G NSA status can not be displayed in the libqmi version 1.28.6-1. (LP#1937012) The 5G NSA status is supported in the libqmi version 1.30.2. The requested upstream patches are listed as below: * 5G NSA status patches https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/commit/29905223c5ae6e5e4ef9246dd9dd4d01b2819d9a * qmicli,nas: flag as 'n/a' the 5G NSA signal quality if not connected https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/commit/b05df7b658f9cfb4c5e74a3e07913de689914a8f [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Verify if the field “5G NSA Available: ” can be displayed via executing: $ sudo qmicli --device=/dev/wwan0p2MBIM --device-open-proxy --nas-get-system-info ... 5G NSA Available: 'no' ... [Where problems could occur] The requested upstream patches are for displaying the status information of 5G NSA network. This should not affect existing generic functions. [Other Info] The latest version of libqmi suit can display the 5G NSA status. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946143/+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 1948813] [NEW] cant connect to second monitor
Public bug reported: I lost projecting to my second monitor while updating in ubuntu 20 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 26 07:55:42 2021 DistUpgraded: 2021-10-15 08:30:35,667 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 5.4.0-89-generic, x86_64: installed nvidia, 470.74, 5.4.0-89-generic, x86_64: installed virtualbox, 6.1.26, 5.4.0-88-generic, x86_64: installed virtualbox, 6.1.26, 5.4.0-89-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics 630 (Mobile) [1025:1264] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev ff) (prog-if ff) InstallationDate: Installed on 2021-09-21 (34 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Acer Nitro AN515-52 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=c4de9279-4774-410d-be28-7e7083e0c939 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-10-15 (10 days ago) dmi.bios.date: 08/05/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.28 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Freed_CFS dmi.board.vendor: CFL dmi.board.version: V1.28 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.28 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.28:bd08/05/2019:svnAcer:pnNitroAN515-52:pvrV1.28:rvnCFL:rnFreed_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28: dmi.product.family: Acer Nitro 5 dmi.product.name: Nitro AN515-52 dmi.product.sku: dmi.product.version: V1.28 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1948813 Title: cant connect to second monitor Status in xorg package in Ubuntu: New Bug description: I lost projecting to my second monitor while updating in ubuntu 20 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 26 07:55:42 2021 DistUpgraded: 2021-10-15 08:30:35,667 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 5.4.0-89-generic, x86_64: installed nvidia, 470.74, 5.4.0-89-generic, x86_64: installed virtualbox, 6.1.26, 5.4.0-88-generic, x86_64: installed virtualbox, 6.1.26, 5.4.0-89-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics 630 (Mobile) [1025:1264] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev ff) (prog-if ff) InstallationDate: Installed on 2021-09-21 (34 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Acer Nitro AN515-52 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=c4de9279-4774-410d-be28-7e7083e0c939 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-10-15 (10 days ago) dmi.bios.date: 08/05/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.28 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name:
[Desktop-packages] [Bug 1948806] [NEW] [SRU] Enable support for Yoga Cloud Archive
Public bug reported: Please add support for: cloud-archive:yoga cloud-archive:yoga-proposed This will also need to be SRU'd back to focal. [Impact] End users have to manually enable the yoga cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:yoga sudo add-apt-repository cloud-archive:yoga-proposed [Regression potential] Limited - just a data item addition ** Affects: software-properties (Ubuntu) Importance: Medium Status: Triaged ** Affects: software-properties (Ubuntu Focal) Importance: Medium Status: Triaged ** Affects: software-properties (Ubuntu Jammy) Importance: Medium Status: Triaged ** Also affects: software-properties (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: software-properties (Ubuntu Focal) Status: New => Triaged ** Changed in: software-properties (Ubuntu Jammy) Status: New => Triaged ** Changed in: software-properties (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: software-properties (Ubuntu Jammy) Importance: Undecided => Medium -- 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/1948806 Title: [SRU] Enable support for Yoga Cloud Archive Status in software-properties package in Ubuntu: Triaged Status in software-properties source package in Focal: Triaged Status in software-properties source package in Jammy: Triaged Bug description: Please add support for: cloud-archive:yoga cloud-archive:yoga-proposed This will also need to be SRU'd back to focal. [Impact] End users have to manually enable the yoga cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:yoga sudo add-apt-repository cloud-archive:yoga-proposed [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1948806/+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 1946558] Re: [SRU] libreoffice 7.2.2 for impish
** Changed in: libreoffice (Ubuntu) Status: Fix Committed => Fix Released -- 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/1946558 Title: [SRU] libreoffice 7.2.2 for impish Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Impish: Fix Released Bug description: [Impact] * LibreOffice 7.2.2 is in its second bugfix release of the 7.2 line: https://wiki.documentfoundation.org/ReleasePlan/7.2#7.2.2_release * Version 7.2.1 is currently released in impish. For a list of fixed bugs compared to 7.2.1 see the list of bugs fixed in the release candidates of 7.2.2 (that's a total of 68 bugs): https://wiki.documentfoundation.org/Releases/7.2.2/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.2.2/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_72/854/ * 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-impish-libreoffice-libreoffice-prereleases/impish/amd64/libr/libreoffice/20211010_212128_a2213@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/arm64/libr/libreoffice/20211011_063847_cff27@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/armhf/libr/libreoffice/20211010_152042_46a77@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/ppc64el/libr/libreoffice/20211010_131403_b895a@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/s390x/libr/libreoffice/20211010_145947_98155@/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 68 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/1946558/+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 1948778] Re: Random flashes in gnome-shell
** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948778/+attachment/5536239/+files/lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1948778 Title: Random flashes in gnome-shell Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 22.04 development branch up to date to latest @ 26/10/2021 kernel 5.13.0-19-generic While working around on the desktop i'm getting short screen flashes like a screenshot style i cant reproduce them, they seem to come on random like every few minutes journal logs dont record anything while they occur this only happens on wayland, tested a long session on xorg where they dont occur ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 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: Tue Oct 26 11:12:30 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2021-10-23T19:12:47.175230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948778/+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 1948778] Re: Random flashes in gnome-shell
@ Daniel its a bit hard to say wich colour, as the flashes go so fast, like a fast screenshot when leaving a journalctl -f open i cant see any errors on the time of the flashes ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948778/+attachment/5536238/+files/journal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1948778 Title: Random flashes in gnome-shell Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 22.04 development branch up to date to latest @ 26/10/2021 kernel 5.13.0-19-generic While working around on the desktop i'm getting short screen flashes like a screenshot style i cant reproduce them, they seem to come on random like every few minutes journal logs dont record anything while they occur this only happens on wayland, tested a long session on xorg where they dont occur ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 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: Tue Oct 26 11:12:30 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2021-10-23T19:12:47.175230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948778/+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 1946143] Update Released
The verification of the Stable Release Update for libqmi has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libqmi in Ubuntu. https://bugs.launchpad.net/bugs/1946143 Title: Apply upstream patches to display 5G NSA status Status in OEM Priority Project: In Progress Status in libqmi package in Ubuntu: Fix Committed Status in libqmi source package in Focal: Fix Committed Status in libqmi source package in Hirsute: Fix Committed Status in libqmi source package in Impish: Fix Released Bug description: [Impact] The 5G NSA status can not be displayed in the libqmi version 1.28.6-1. (LP#1937012) The 5G NSA status is supported in the libqmi version 1.30.2. The requested upstream patches are listed as below: * 5G NSA status patches https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/commit/29905223c5ae6e5e4ef9246dd9dd4d01b2819d9a * qmicli,nas: flag as 'n/a' the 5G NSA signal quality if not connected https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/commit/b05df7b658f9cfb4c5e74a3e07913de689914a8f [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Verify if the field “5G NSA Available: ” can be displayed via executing: $ sudo qmicli --device=/dev/wwan0p2MBIM --device-open-proxy --nas-get-system-info ... 5G NSA Available: 'no' ... [Where problems could occur] The requested upstream patches are for displaying the status information of 5G NSA network. This should not affect existing generic functions. [Other Info] The latest version of libqmi suit can display the 5G NSA status. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946143/+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 1941752]
Created attachment 142865 New crash information added by DrKonqi gwenview (21.08.1) using Qt 5.15.2 Gwenview crashed when trying to open a jpg. The images in question were saved by Darktable from Canon Raw images, and ranged in size from 8.2 to 16.4 MiB. -- Backtrace (Reduced): #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139626298358848) at pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=139626298358848) at pthread_kill.c:80 #6 __GI___pthread_kill (threadid=139626298358848, signo=signo@entry=6) at pthread_kill.c:91 #7 0x7efd4d5d6476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7efd4d5bc7b7 in __GI_abort () at abort.c:79 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: Confirmed Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1930188] Re: Acer Aspire 5 sound driver issues
This bug was fixed in the package alsa-ucm-conf - 1.2.4-2ubuntu5 --- alsa-ucm-conf (1.2.4-2ubuntu5) impish; urgency=medium * d/p/0008-HDA-Intel-add-Boost-volume-control-for-Headset-Mic.patch Add Mic Boost in the HDA Intel ucm, after this change, when users adjust input volume, the Mic Boost could be adjusted as well as Capture Volume. (LP: #1930188) -- Hui Wang Tue, 14 Sep 2021 10:54:28 +0800 ** Changed in: alsa-ucm-conf (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: Fix Released Status in alsa-ucm-conf source package in Impish: Fix Released Status in linux source package in Impish: Fix Released Status in pulseaudio source package in Impish: Fix Released Bug description: SRU Justification for alsa-ucm-conf: [Impact] On the machines with the sof audio driver, users could adjust the input volume from UI, but this only adjusts the "Capture Volume", the "Mic Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture Volume" to max, the recorded volume is still very low. [Fix] Backport a upstream patch, the patch adds the "Mic Boost" into the ucm [Test] plug a headset, make sure the headset-mic is the active input device, adjust the input volume to %20, open a terminal and run alsamixer, check the "Capture Volume" and "Mic Boost" value, then adjust the input volume to 80%, check those values and we could see both values are changed. [Where problems could occur] This patch could make the parse of input volume control fail, then the input volume can't be changed anymore when users adjust the volume from UI. But this possibility is very low, I tested this patch on many lenovo and dell machines with sof audio driver, all worked well. SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU for the focal kernel. [Impact] Users plug headphone and Mic to the audio jacks, but the system can't detect them, and couldn't output sound through headphone and record sound through Mic. [Fix] Backport a upstream patch, this will set the Mic to auto-detection mode and set the headphone to left location. [Test] Plug a headset to the headset audio jack, both headphone and mic could be detected. And output the sound to headphone, could hear the sound, record the sound through Mic, the sound could be recorded. [Where problems could occur] The patch is specific to Acer Aspire 5 machine, if it could introduce regression, it will make the audio like internal mic and internal spk stop working. But this possibility is very low. Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR
[Desktop-packages] [Bug 1946143] Re: Apply upstream patches to display 5G NSA status
This bug was fixed in the package libqmi - 1.28.6-2ubuntu1 --- libqmi (1.28.6-2ubuntu1) impish; urgency=medium * Apply upstream patch to display the 5G NSA status. (lp: #1946143) -- Jerry Lee Wed, 06 Oct 2021 16:21:40 +0800 ** Changed in: libqmi (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libqmi in Ubuntu. https://bugs.launchpad.net/bugs/1946143 Title: Apply upstream patches to display 5G NSA status Status in OEM Priority Project: In Progress Status in libqmi package in Ubuntu: Fix Committed Status in libqmi source package in Focal: Fix Committed Status in libqmi source package in Hirsute: Fix Committed Status in libqmi source package in Impish: Fix Released Bug description: [Impact] The 5G NSA status can not be displayed in the libqmi version 1.28.6-1. (LP#1937012) The 5G NSA status is supported in the libqmi version 1.30.2. The requested upstream patches are listed as below: * 5G NSA status patches https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/commit/29905223c5ae6e5e4ef9246dd9dd4d01b2819d9a * qmicli,nas: flag as 'n/a' the 5G NSA signal quality if not connected https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/commit/b05df7b658f9cfb4c5e74a3e07913de689914a8f [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Verify if the field “5G NSA Available: ” can be displayed via executing: $ sudo qmicli --device=/dev/wwan0p2MBIM --device-open-proxy --nas-get-system-info ... 5G NSA Available: 'no' ... [Where problems could occur] The requested upstream patches are for displaying the status information of 5G NSA network. This should not affect existing generic functions. [Other Info] The latest version of libqmi suit can display the 5G NSA status. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946143/+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 1929999] Re: [SRU] libreoffice 6.4.7.2.M3 for Focal
This is a bit of a tricky situation I think. Let me elaborate. We allow new upstream releases for certain projects because of a certain trust shift - for upstream projects that have a sufficient quality assurance story and clear bugfix policy, we allow updating the whole version instead of requiring testing of every single change separately. Basically this is this section of the policy, even though it's a bit vague: https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases In this case, when the upstream branch of libreoffice is EOL and us switching to an unofficial branch with fixes, I think we no longer fit this policy. We can put certain level of trust to upstream developers preparing upstream releases, by shifting trust to upstream we can skip certain parts of our SRU review and verification, simply assuming that - for instance - the bugfixes listed in the changes are accurate with what's actually in the tarball. I don't think we can say the same thing about a version that is officially EOL in the mind of upstream. We certainly can't blindly trust what's in that codebase, and therefore just running the usual 'autopkgtests' + usual test-case won't work from the SRU perspective, sadly. In this case, I think I only see two options: a) Switching users of focal to a non-EOL version of libreoffice. This would of course require much more testing (maybe even a call for testing from other users), but as you already mentioned on IRC: there is risk that user extensions would be broken by this. And I think regressing existing users might be a breach of policy as well... so I'm not sure we can pull this off. b) Cherry-picking *single fixes* from the aforementioned MIMO branch, each fix having a separate test-case i.e. following the regular per-bugfix SRU policy. I know this situation is not ideal, but I don't think we can realistically do much more. We can pull in more SRU members for comment though, maybe someone would have a better idea. ** Changed in: libreoffice (Ubuntu Focal) Status: Triaged => Incomplete -- 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/192 Title: [SRU] libreoffice 6.4.7.2.M3 for Focal Status in libreoffice package in Ubuntu: Invalid Status in libreoffice source package in Focal: Incomplete Bug description: [Impact] * LibreOffice 6.4.7.2.M3 is a bug-fix release of the 6.4 line: It receives important bug-fixes on top of the 6.4 branch which is EOL since November 30, 2020. Currently maintained by Andras Timar for France's MIMO (https://blog.documentfoundation.org/blog/2013/06/17/the-document-foundation-welcomes-frances-mimo-in-the-advisory-board/) * Version 6.4.7 is currently released in focal. https://cgit.freedesktop.org/libreoffice/core/log/?h=distro/mimo/mimo-6-4 (that's a total of ?? 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] * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/12712294/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-ricotz-ppa/focal/amd64/libr/libreoffice/20210921_030416_a2220@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-ricotz-ppa/focal/arm64/libr/libreoffice/20210921_010758_2afcd@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-ricotz-ppa/focal/armhf/libr/libreoffice/20210920_223713_b4dfd@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-ricotz-ppa/focal/ppc64el/libr/libreoffice/20210920_232648_4df4d@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-ricotz-ppa/focal/s390x/libr/libreoffice/20210921_020008_6c843@/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 ?? bug fixes always carries the potential for introducing regressions, even though it is a bug-fix- 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/192/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1948665] Re: No stylus found for Wacom HID 49A3 Pen (Latitude 7320)
** Changed in: libwacom Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwacom in Ubuntu. https://bugs.launchpad.net/bugs/1948665 Title: No stylus found for Wacom HID 49A3 Pen (Latitude 7320) Status in libwacom: New Status in libwacom package in Ubuntu: Triaged Bug description: I have a Dell Latitude 7320 Detachable with a 7320 Detachable Active Pen (PN7320A). The pen mostly works, aside from a periodic bug (https://github.com/linuxwacom/input-wacom/issues/281). It shows up as a Wacom pen from libinput: Device: Wacom HID 49A3 Pen Kernel: /dev/input/event4 Group:6 Seat: seat0, default Size: 274x183mm Capabilities: tablet Tap-to-click: n/a Tap-and-drag: n/a Tap drag lock:n/a Left-handed: n/a Nat.scrolling:n/a Middle emulation: n/a Calibration: identity matrix Scroll methods: none Click methods:none Disable-w-typing: n/a Accel profiles: none Rotation: n/a I cannot configure it via the Wacom Tablet settings in the control center. It always says "No stylus found" despite being able to use the stylus with applications such as Xournal++. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-control-center 1:40.0-1ubuntu5 Uname: Linux 5.15.0-rc4-soffixes x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 25 13:47:11 2021 InstallationDate: Installed on 2021-10-12 (12 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to impish on 2021-10-14 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/libwacom/+bug/1948665/+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 1948647] Re: Screeen recording via Ctrl+Alt+Shift+R creates empty webm file, orange circle persists
Downstream bug: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4725 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4725 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4725 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1948647 Title: Screeen recording via Ctrl+Alt+Shift+R creates empty webm file, orange circle persists Status in gnome-shell package in Ubuntu: Incomplete Bug description: Running 21.10 and Gnome 40.4 the screen recording no longer works with the Ctrl+Alt+Shift+R keystroke. A .webm file does appear in the Videos folder but it is empty. The orange circle does appear in the upper corner, but it will not go away. Further Ctrl+Alt+Shift+R strokes do not make a new .webm file or remove the orange circle. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 Uname: Linux 5.15.0-rc4-soffixes x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 25 11:11:13 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-10-12 (12 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 40.5-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2021-10-14 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948647/+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 1948665] Re: No stylus found for Wacom HID 49A3 Pen (Latitude 7320)
Thanks ** Changed in: libwacom (Ubuntu) Status: New => Triaged ** Also affects: libwacom via https://github.com/linuxwacom/libwacom/issues/432 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwacom in Ubuntu. https://bugs.launchpad.net/bugs/1948665 Title: No stylus found for Wacom HID 49A3 Pen (Latitude 7320) Status in libwacom: Unknown Status in libwacom package in Ubuntu: Triaged Bug description: I have a Dell Latitude 7320 Detachable with a 7320 Detachable Active Pen (PN7320A). The pen mostly works, aside from a periodic bug (https://github.com/linuxwacom/input-wacom/issues/281). It shows up as a Wacom pen from libinput: Device: Wacom HID 49A3 Pen Kernel: /dev/input/event4 Group:6 Seat: seat0, default Size: 274x183mm Capabilities: tablet Tap-to-click: n/a Tap-and-drag: n/a Tap drag lock:n/a Left-handed: n/a Nat.scrolling:n/a Middle emulation: n/a Calibration: identity matrix Scroll methods: none Click methods:none Disable-w-typing: n/a Accel profiles: none Rotation: n/a I cannot configure it via the Wacom Tablet settings in the control center. It always says "No stylus found" despite being able to use the stylus with applications such as Xournal++. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-control-center 1:40.0-1ubuntu5 Uname: Linux 5.15.0-rc4-soffixes x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 25 13:47:11 2021 InstallationDate: Installed on 2021-10-12 (12 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to impish on 2021-10-14 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/libwacom/+bug/1948665/+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 1948046] Re: [upstream] Flameshot won't paste on Chrome with Ozone enabled
Thanks. However this issue is unique to Ubuntu and derivatives. Other distributions have not been affected with or without Ozone enabled in Chrome. Thanks again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1948046 Title: [upstream] Flameshot won't paste on Chrome with Ozone enabled Status in chromium-browser package in Ubuntu: Confirmed Bug description: This is a unique problem to Ubuntu 21.04 and later and all derivatives (pop, mint etc). Since Chrome stable 91, when Ozone was enabled by default, unless Ozone is disabled in Chrome, flameshot (any version) cannot paste on sites such as github, gitlab or kami. The workaround has been so far to disable Ozone in Chrome flags, but since Chrome 95, Ozone cannot be disabled, which means that flameshot no longer works with Chrome and those (and potentially more) sites. Everything works fine in Fedora 33/34/35 and Manjaro 20+. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1948046/+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 1948778] Re: Random flashes in gnome-shell
Thanks for the bug report. Are the flashes light or dark? Next time it happens, please immediately run: journalctl -b0 > journal.txt lspci -kv > lspci.txt and attach the resulting text files here. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1948778 Title: Random flashes in gnome-shell Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 22.04 development branch up to date to latest @ 26/10/2021 kernel 5.13.0-19-generic While working around on the desktop i'm getting short screen flashes like a screenshot style i cant reproduce them, they seem to come on random like every few minutes journal logs dont record anything while they occur this only happens on wayland, tested a long session on xorg where they dont occur ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 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: Tue Oct 26 11:12:30 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2021-10-23T19:12:47.175230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948778/+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 1948778] [NEW] Random flashes in gnome-shell
Public bug reported: Ubuntu 22.04 development branch up to date to latest @ 26/10/2021 kernel 5.13.0-19-generic While working around on the desktop i'm getting short screen flashes like a screenshot style i cant reproduce them, they seem to come on random like every few minutes journal logs dont record anything while they occur this only happens on wayland, tested a long session on xorg where they dont occur ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 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: Tue Oct 26 11:12:30 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2021-10-23T19:12:47.175230 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Description changed: Ubuntu 22.04 development branch up to date to latest @ 26/10/2021 kernel 5.13.0-19-generic While working around on the desktop i'm getting short screen flashes like a screenshot style - i cannt reproduce them, they seem to come on random like every few minutes + i cant reproduce them, they seem to come on random like every few minutes journal logs dont record anything while they occur this only happens on wayland, tested a long session on xorg where they dont occur ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 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: Tue Oct 26 11:12:30 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2021-10-23T19:12:47.175230 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1948778 Title: Random flashes in gnome-shell Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 22.04 development branch up to date to latest @ 26/10/2021 kernel 5.13.0-19-generic While working around on the desktop i'm getting short screen flashes like a screenshot style i cant reproduce them, they seem to come on random like every few minutes journal logs dont record anything while they occur this only happens on wayland, tested a long session on xorg where they dont occur ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 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: Tue Oct 26 11:12:30 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2021-10-23T19:12:47.175230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948778/+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 1948665] Re: No stylus found for Wacom HID 49A3 Pen (Latitude 7320)
The upstream bug report is here: https://github.com/linuxwacom/libwacom/issues/432 ** Bug watch added: github.com/linuxwacom/libwacom/issues #432 https://github.com/linuxwacom/libwacom/issues/432 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwacom in Ubuntu. https://bugs.launchpad.net/bugs/1948665 Title: No stylus found for Wacom HID 49A3 Pen (Latitude 7320) Status in libwacom package in Ubuntu: New Bug description: I have a Dell Latitude 7320 Detachable with a 7320 Detachable Active Pen (PN7320A). The pen mostly works, aside from a periodic bug (https://github.com/linuxwacom/input-wacom/issues/281). It shows up as a Wacom pen from libinput: Device: Wacom HID 49A3 Pen Kernel: /dev/input/event4 Group:6 Seat: seat0, default Size: 274x183mm Capabilities: tablet Tap-to-click: n/a Tap-and-drag: n/a Tap drag lock:n/a Left-handed: n/a Nat.scrolling:n/a Middle emulation: n/a Calibration: identity matrix Scroll methods: none Click methods:none Disable-w-typing: n/a Accel profiles: none Rotation: n/a I cannot configure it via the Wacom Tablet settings in the control center. It always says "No stylus found" despite being able to use the stylus with applications such as Xournal++. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-control-center 1:40.0-1ubuntu5 Uname: Linux 5.15.0-rc4-soffixes x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 25 13:47:11 2021 InstallationDate: Installed on 2021-10-12 (12 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to impish on 2021-10-14 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1948665/+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 1948046] Re: [upstream] Flameshot won't paste on Chrome with Ozone enabled
The chrome package is made and supported by Google, not by Ubuntu developers. You'll have more luck discussing this on the upstream bug report. ** No longer affects: chromium-browser -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1948046 Title: [upstream] Flameshot won't paste on Chrome with Ozone enabled Status in chromium-browser package in Ubuntu: Confirmed Bug description: This is a unique problem to Ubuntu 21.04 and later and all derivatives (pop, mint etc). Since Chrome stable 91, when Ozone was enabled by default, unless Ozone is disabled in Chrome, flameshot (any version) cannot paste on sites such as github, gitlab or kami. The workaround has been so far to disable Ozone in Chrome flags, but since Chrome 95, Ozone cannot be disabled, which means that flameshot no longer works with Chrome and those (and potentially more) sites. Everything works fine in Fedora 33/34/35 and Manjaro 20+. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1948046/+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 1948355] Re: Firefox settings font size dropdown flashes, hard to select
Thanks Janne. Indeed apport-collect won't work because you're running the snap, I should have known better before asking you to run this command. Can you re-share the details from https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1948356/comments/2 here? That would be useful. -- 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/1948355 Title: Firefox settings font size dropdown flashes, hard to select Status in firefox package in Ubuntu: Incomplete Bug description: Go to settings, then font, and try to change the font size. The dropdown flashes and disappears, and is very difficult to select. Happens both on the main screen and the "advanced.." screen for all size selectors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1948355/+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 1948356] Re: Firefox 93.0 tabs are not remembered across sessions
*** This bug is a duplicate of bug 1948652 *** https://bugs.launchpad.net/bugs/1948652 ** This bug has been marked a duplicate of bug 1948652 [upstream,regression] Firefox does not save tabs when quitting with Ctrl+Q -- 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/1948356 Title: Firefox 93.0 tabs are not remembered across sessions Status in firefox package in Ubuntu: Incomplete Bug description: If I close Firefox with a bunch of tabs, then open again, the tabs are gone. I get a list of empty tabs without any actual link to them. Only the last visited site is actually filled with the URL. Up until now Firefox always remembers and restores the list of tabs. I am using Tree Style Tab, but I believe it uses the regular tab list for itself. Ubuntu 21.10 firefox 93.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1948356/+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 1946558] Update Released
The verification of the Stable Release Update for libreoffice has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1946558 Title: [SRU] libreoffice 7.2.2 for impish Status in libreoffice package in Ubuntu: Fix Committed Status in libreoffice source package in Impish: Fix Released Bug description: [Impact] * LibreOffice 7.2.2 is in its second bugfix release of the 7.2 line: https://wiki.documentfoundation.org/ReleasePlan/7.2#7.2.2_release * Version 7.2.1 is currently released in impish. For a list of fixed bugs compared to 7.2.1 see the list of bugs fixed in the release candidates of 7.2.2 (that's a total of 68 bugs): https://wiki.documentfoundation.org/Releases/7.2.2/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.2.2/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_72/854/ * 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-impish-libreoffice-libreoffice-prereleases/impish/amd64/libr/libreoffice/20211010_212128_a2213@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/arm64/libr/libreoffice/20211011_063847_cff27@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/armhf/libr/libreoffice/20211010_152042_46a77@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/ppc64el/libr/libreoffice/20211010_131403_b895a@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/s390x/libr/libreoffice/20211010_145947_98155@/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 68 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/1946558/+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 1946558] Re: [SRU] libreoffice 7.2.2 for impish
This bug was fixed in the package libreoffice - 1:7.2.2-0ubuntu0.21.10.1 --- libreoffice (1:7.2.2-0ubuntu0.21.10.1) impish; urgency=medium * New upstream release (LP: #1946558) -- Rico Tzschichholz Sat, 09 Oct 2021 15:44:04 +0200 ** Changed in: libreoffice (Ubuntu Impish) Status: Fix Committed => Fix Released -- 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/1946558 Title: [SRU] libreoffice 7.2.2 for impish Status in libreoffice package in Ubuntu: Fix Committed Status in libreoffice source package in Impish: Fix Released Bug description: [Impact] * LibreOffice 7.2.2 is in its second bugfix release of the 7.2 line: https://wiki.documentfoundation.org/ReleasePlan/7.2#7.2.2_release * Version 7.2.1 is currently released in impish. For a list of fixed bugs compared to 7.2.1 see the list of bugs fixed in the release candidates of 7.2.2 (that's a total of 68 bugs): https://wiki.documentfoundation.org/Releases/7.2.2/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.2.2/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_72/854/ * 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-impish-libreoffice-libreoffice-prereleases/impish/amd64/libr/libreoffice/20211010_212128_a2213@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/arm64/libr/libreoffice/20211011_063847_cff27@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/armhf/libr/libreoffice/20211010_152042_46a77@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/ppc64el/libr/libreoffice/20211010_131403_b895a@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/s390x/libr/libreoffice/20211010_145947_98155@/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 68 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/1946558/+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 1942993] Re: Fail to close the window by clicking "Done" button after adding "apps" to the skip list
Will install snap-store snap instead of hiding the "apps" page. ** Changed in: gnome-initial-setup (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1942993 Title: Fail to close the window by clicking "Done" button after adding "apps" to the skip list Status in gnome-initial-setup package in Ubuntu: Invalid Bug description: For the images which only pre-load ubuntu-desktop-minimal, snap-store snap package isn't installed by default. The page "apps" should be skipped. I add "apps" into the skip list. But, I cannot close the window by clicking "Done" button" after adding "apps" into the skip list. Here are my reproduction steps: 1. Add "apps" into the skip list. /usr/lib/gnome-initial-setup/vendor.conf [pages] -skip=language; +skip=language;apps; 2. Run gnome-initial-setup with --exisiting-user $ /usr/libexec/gnome-initial-setup --exisiting-user Test result: 40.4-1ubuntu1 (impish): Failed 3.36.2-0ubuntu2 (focal): Failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1942993/+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 1855595] Re: CUPS fails to print to autodetected printers because of cups-browsed error
Same for me - printing is working on Ubuntu 18.04, but hardly (and then only after a fresh reboot) working on Ubuntu 20.04. My printer: Brother 8510DN. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1855595 Title: CUPS fails to print to autodetected printers because of cups-browsed error Status in cups-filters package in Ubuntu: Confirmed Bug description: When trying to autodetected IPP printers, print job stays in queue. lpstat -l: HP_LaserJet_CM1415fn_44A808_-23 erik 30720 So 08 Dez 2019 15:50:20 CET Status: No suitable destination host found by cups-browsed. Alarme: resources-are-not-ready in Warteschlange eingereiht für HP_LaserJet_CM1415fn_44A808_ Removing the print job, restarting cups-browsed with `service cups- browsed restart` followed by `service cups restart` enables printing for one print job; the next one fails again with the same issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups-browsed 1.25.13-1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: LXQt Date: Sun Dec 8 16:06:02 2019 InstallationDate: Installed on 2019-10-19 (50 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191019) Lpstat: device for HP_LaserJet_CM1415fn_44A808_: implicitclass://HP_LaserJet_CM1415fn_44A808_/ device for Samsung_C48x_Series_SEC84251900EE44_: implicitclass://Samsung_C48x_Series_SEC84251900EE44_/ MachineType: Dell Inc. Latitude E6530 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_LaserJet_CM1415fn_44A808_.ppd', '/etc/cups/ppd/Samsung_C48x_Series_SEC84251900EE44_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_LaserJet_CM1415fn_44A808_.ppd: Permission denied grep: /etc/cups/ppd/Samsung_C48x_Series_SEC84251900EE44_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_utwd0l@/vmlinuz-5.3.0-24-generic root=ZFS=rpool/ROOT/ubuntu_utwd0l ro quiet splash vt.handoff=1 SourcePackage: cups-filters UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A22 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA22:bd11/30/2018:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.sku: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1855595/+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
