[Desktop-packages] [Bug 1960898] Re: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[
Please run this command: gsettings set org.gnome.shell.extensions.dash-to-dock show-mounts false and then reboot. Has that solved the problem? ** No longer affects: gnome-shell (Ubuntu) -- 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/1960898 Title: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[0].isObject()) from ubuntu- d...@ubuntu.com/locations.js:1108 Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: Hardware: https://linux-hardware.org/?probe=1055dc7082 Worked without Problem in 21.04 Had some flicker and problem with the left dock in 21.10 not working since updating to 22.04 now I'm running xorg. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-450/libnvidia-gl-450_450.102.04-0ubuntu2_amd64.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Tue Feb 15 08:07:04 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-08-15 (183 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 41.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-02-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1960898/+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 1960898] Re: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[
If the problem is not fixed by comment #5 then please log into a Xorg session and run: journalctl -b0 > journal.txt and attach the resulting text file here. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Incomplete ** Summary changed: - Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[0].isObject()) + Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[0].isObject()) from ubuntu-d...@ubuntu.com/locations.js:1108 -- 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/1960898 Title: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[0].isObject()) from ubuntu- d...@ubuntu.com/locations.js:1108 Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: Hardware: https://linux-hardware.org/?probe=1055dc7082 Worked without Problem in 21.04 Had some flicker and problem with the left dock in 21.10 not working since updating to 22.04 now I'm running xorg. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-450/libnvidia-gl-450_450.102.04-0ubuntu2_amd64.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Tue Feb 15 08:07:04 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-08-15 (183 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 41.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-02-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1960898/+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 1574154] Re: xorg.conf changed on start of lightdm service
Thanks for your reply. Yes, some bug reports do seem to be forgotten. ;o) Closing as "Invalid" on the basis the issue was never confirmed by another user and the Xenial release is now EOL. ** Changed in: xorg (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1574154 Title: xorg.conf changed on start of lightdm service Status in xorg package in Ubuntu: Invalid Bug description: After upgrading from 15.10 (Wily) to 16.04 (Xenial), X wont start. It appears that my xorg.conf is modified such that I get a non-working way (I get a coredump in the video driver I think). I have a Thinkpad T530 with dual video cards, so I change the from the nvidia that is somewere(?) auto selected back to intel. Alas, restarting of lightdm service does not work: xorg.conf is re-modified. Manually starting a X session with 'startx' (after correcting xorg.conf) works as expected. Alas, nobody logs about this; that would have helped me find the culprit.. Who modifies my xorg.conf? Why? This never happened before, and should IMHO not be done. Temporary solution: 'chattr +i /etc/X11/xorg.conf'. This makes auto- changing impossible. But this is a hack. I should be allowed to change my system such that it works the way I want. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: MATE Date: Sun Apr 24 05:45:17 2016 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to xenial on 2016-04-21 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574154/+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 1959937] Re: gnome-shell crashed with SIGSEGV in meta_context_terminate()
Launchpad has imported 15 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=2036604. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2022-01-03T11:10:45+00:00 khoorasan wrote: Description of problem: An application named "Backup" downloaded from the app store finished making back up of the whole system, then I unplugged the external USB, closed the application, a browser named "Brave" was running, when issued the command "poweroff" in the terminal, and my macbook pro 2012 shut down, once I restarted I noticed this error message. Version-Release number of selected component: gnome-shell-41.2-1.fc35 Additional info: reporter: libreport-2.15.2 backtrace_rating: 4 cgroup: 0::/user.slice/user-42.slice/session-c1.scope cmdline:/usr/bin/gnome-shell crash_function: meta_context_terminate executable: /usr/bin/gnome-shell journald_cursor: s=3036cc978c2c4faca5c818849161ed45;i=1432e;b=de82c8ea70844d16a59c2bf73d776781;m=5a37134;t=5d4495cd257c9;x=9eb7bfee5d98542a kernel: 5.15.11-200.fc35.x86_64 rootdir:/ runlevel: N 5 type: CCpp uid:42 Truncated backtrace: Thread no. 1 (4 frames) #0 meta_context_terminate at ../src/core/meta-context.c:451 #1 process_ice_messages at ../src/x11/session.c:116 #5 g_main_context_iterate.constprop.0 at ../glib/gmain.c:4175 #7 meta_context_run_main_loop at ../src/core/meta-context.c:433 Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1959937/comments/0 On 2022-01-03T11:10:47+00:00 khoorasan wrote: Created attachment 1848679 File: backtrace Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1959937/comments/1 On 2022-01-03T11:10:49+00:00 khoorasan wrote: Created attachment 1848680 File: core_backtrace Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1959937/comments/2 On 2022-01-03T11:10:50+00:00 khoorasan wrote: Created attachment 1848681 File: cpuinfo Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1959937/comments/3 On 2022-01-03T11:10:51+00:00 khoorasan wrote: Created attachment 1848682 File: dso_list Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1959937/comments/4 On 2022-01-03T11:10:52+00:00 khoorasan wrote: Created attachment 1848683 File: environ Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1959937/comments/5 On 2022-01-03T11:10:53+00:00 khoorasan wrote: Created attachment 1848684 File: exploitable Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1959937/comments/6 On 2022-01-03T11:10:54+00:00 khoorasan wrote: Created attachment 1848685 File: limits Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1959937/comments/7 On 2022-01-03T11:10:55+00:00 khoorasan wrote: Created attachment 1848686 File: maps Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1959937/comments/8 On 2022-01-03T11:10:56+00:00 khoorasan wrote: Created attachment 1848687 File: mountinfo Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1959937/comments/9 On 2022-01-03T11:10:57+00:00 khoorasan wrote: Created attachment 1848688 File: open_fds Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1959937/comments/10 On 2022-01-03T11:10:58+00:00 khoorasan wrote: Created attachment 1848689 File: proc_pid_status Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1959937/comments/11 On 2022-01-03T11:10:59+00:00 khoorasan wrote: Created attachment 1848690 File: var_log_messages Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1959937/comments/12 On 2022-01-12T11:12:20+00:00 bkb wrote: *** Bug 2039748 has been marked as a duplicate of thi
[Desktop-packages] [Bug 1960768] Re: fwupd crash on stop
debian sid now has libgusb version 0.3.10. And it's in jammy-proposed now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgusb in Ubuntu. https://bugs.launchpad.net/bugs/1960768 Title: fwupd crash on stop Status in OEM Priority Project: In Progress Status in fwupd package in Ubuntu: Invalid Status in libgusb package in Ubuntu: Confirmed Status in libusb package in Ubuntu: Invalid Bug description: I can reproduce crash with a similar stack as below as I stop fwupd service. https://errors.ubuntu.com/problem/4bfcf571c017010afe4775687ff2a9ca7ff79661 also test fwupd 1.7.5 (https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd175) still can reproduce this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1960768/+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 1960313] Re: [snap] chromium crashes regularly
Thanks for the additional info and for the logs Chris. So Chromium was abruptly killed, and the logs don't contain any hint as to why this might have happened. I wonder whether this could be an out of memory situation, where the kernel decided to kill Chromium to free up memory. Could you inspect the output of `journalctl` around the timestamp when the crash occurred? In the DiskUsage section of the data attached by apport, I'm seeing that your /home partition is almost full (63M free out of 32GB), maybe that could explain this sort of abrupt termination if Chromium is trying to write profile or cache data to disk? -- 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/1960313 Title: [snap] chromium crashes regularly Status in chromium-browser package in Ubuntu: New Bug description: This was initially mentioned here (https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb- to-snap-transition/11179/317) ** Description For awhile now I just find my chromium just closes and is gone. It’s been at least the last two updates (I get the nag screen on my screen telling me an update is available; I tend to ignore it but reboot my box every ~fortnight so it’ll update at least once per fortnight as I ensure it’s upgraded before I load it after reboot). It’s ~10:40 local time, and I’ve lost the chromium snap at least twice today… no clues as to why, just I get to see my wallpaper on that part of my monitor as the window silently disappears. On re-opening I get a ‘closed ; do you want to restore you tabs’ dialog (something like that anyway) which works, but my box has been up ~13 days, and it was giving me trouble before this reboot as I hoped that reboot would help; alas no; neither last update(s). If I was to guess how long, I'd guess 20-30 days if not more; ie. I'm basing that on two ~14 day reboot cycles... I can't recall if started during the last cycle or just prior to my second-last reboot ~28 days ago As I file this bug; it's now ~23:15 and whilst I mentioned it'd closed twice prior to ~10:40 (I turn box on ~07:30), I'm pretty sure the window has not closed since I posted on the community hub. I'm not usually using the window when it closes; though its closed ~twice whilst I'm using it. ** Limited details sorry I'm not very specific here sorry, I'd file it as 'incomplete', but I don't know how/where to get details. As a snap there is nothing in /var/crash; so as an aside; is there somewhere I can look for clues as to why etc. (like the .crash file in /var/crash, even if I can only understand bits of it) My box is slow (2009 dell desktop)... and I've got in the habit of keeping a terminal open with `htop` running so I can detect if `firefox` (deb package still) or `chromium` are losing RAM.. I've concluded (rightly/wrongly) it's extension related; but if I recognize extensive swapping I look at the `htop` window and if either browser is using a load more RAM than usual & swap size is growing, I tend to close browser, wait for OS to recover the RAM, then re-open.. I've NOT been doing this with chromium of late; so I wondered if it's started crashing where I'd normally notice a slowing box & switch to my htop window, then close the window down... HOWEVER it could also be the regular crashing means the 'ram bleed' issue isn't getting bad enough for the thrashing to become a problem; it's usually only a problem after 2-4 days.. I'm convinced the issue (what I call 'ram bleed') is related to extensions, as the issue didn't occur with no extensions being used; but I prefer having privacy badger/ublock running - google docs offline - privacy badger - ublock origin - startpage (this was only ~recently added; not this one) FYI: I use same extensions with firefox too (except no startpage), and issue is the same; ~same frequency too (2-4 days) Anyway; if you can tell me if it'd be helpful to get/keep certain details; I'll do it, as I realize I'm not giving much. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt DRM.card0-DVI-I-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAs7hAkAQEBAQAaAQOANB14KrclpFdRoCYQUFS/74CzAKlAlQCBwIGAqcBxT4EAAjqAGHE4LUBYLEUACSUhAAAeZiFQsFEAGzBAcDYACSUhAAAe/QA3TB5SEQAKICAgICAg/ABLQUxFRDI0TU9OQ0EKAJo= modes: 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1280x1024 1440x900 1360x768 1280x800 1152x864 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 720x400 DRM.card0-DVI-I-2: enabled: ena
[Desktop-packages] [Bug 1951878] Re: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xwayland (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1951878 Title: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session Status in gtk+3.0 package in Ubuntu: Confirmed Status in xwayland package in Ubuntu: Confirmed Bug description: Ubuntu 21.10 on Wayland session mutter 40.5-1ubuntu3~21.10.1 My apologies if this does not belong in mutter but because it happens in multiple applications, it's my best guess. This is a weird bug because I don't know what causes it but it happens consistently after normal usage which for me means several times leaving the laptop idle and unlocking. If I leave gnome-terminal and/or evince open, eventually any UI action like switching from multiple tabs, opening context menu etc will output the following to journal gnome-terminal-[2393]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window evince[3213]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window I suspect this may happen with other gtk apps as well. This persists until each individual app is restarted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1951878/+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 1951878] Re: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session
ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2020-06-06 (618 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: xwayland 2:21.1.2-0ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Tags: impish wayland-session Uname: Linux 5.13.0-28-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-25 (112 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True ** Tags added: apport-collected wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1951878 Title: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session Status in gtk+3.0 package in Ubuntu: Confirmed Status in xwayland package in Ubuntu: Confirmed Bug description: Ubuntu 21.10 on Wayland session mutter 40.5-1ubuntu3~21.10.1 My apologies if this does not belong in mutter but because it happens in multiple applications, it's my best guess. This is a weird bug because I don't know what causes it but it happens consistently after normal usage which for me means several times leaving the laptop idle and unlocking. If I leave gnome-terminal and/or evince open, eventually any UI action like switching from multiple tabs, opening context menu etc will output the following to journal gnome-terminal-[2393]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window evince[3213]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window I suspect this may happen with other gtk apps as well. This persists until each individual app is restarted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1951878/+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 1951878] Re: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk+3.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1951878 Title: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session Status in gtk+3.0 package in Ubuntu: Confirmed Status in xwayland package in Ubuntu: Confirmed Bug description: Ubuntu 21.10 on Wayland session mutter 40.5-1ubuntu3~21.10.1 My apologies if this does not belong in mutter but because it happens in multiple applications, it's my best guess. This is a weird bug because I don't know what causes it but it happens consistently after normal usage which for me means several times leaving the laptop idle and unlocking. If I leave gnome-terminal and/or evince open, eventually any UI action like switching from multiple tabs, opening context menu etc will output the following to journal gnome-terminal-[2393]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window evince[3213]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window I suspect this may happen with other gtk apps as well. This persists until each individual app is restarted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1951878/+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 1951878] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1951878/+attachment/5561009/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1951878 Title: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session Status in gtk+3.0 package in Ubuntu: Confirmed Status in xwayland package in Ubuntu: Confirmed Bug description: Ubuntu 21.10 on Wayland session mutter 40.5-1ubuntu3~21.10.1 My apologies if this does not belong in mutter but because it happens in multiple applications, it's my best guess. This is a weird bug because I don't know what causes it but it happens consistently after normal usage which for me means several times leaving the laptop idle and unlocking. If I leave gnome-terminal and/or evince open, eventually any UI action like switching from multiple tabs, opening context menu etc will output the following to journal gnome-terminal-[2393]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window evince[3213]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window I suspect this may happen with other gtk apps as well. This persists until each individual app is restarted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1951878/+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 1951878] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1951878/+attachment/5561010/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1951878 Title: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session Status in gtk+3.0 package in Ubuntu: Confirmed Status in xwayland package in Ubuntu: Confirmed Bug description: Ubuntu 21.10 on Wayland session mutter 40.5-1ubuntu3~21.10.1 My apologies if this does not belong in mutter but because it happens in multiple applications, it's my best guess. This is a weird bug because I don't know what causes it but it happens consistently after normal usage which for me means several times leaving the laptop idle and unlocking. If I leave gnome-terminal and/or evince open, eventually any UI action like switching from multiple tabs, opening context menu etc will output the following to journal gnome-terminal-[2393]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window evince[3213]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window I suspect this may happen with other gtk apps as well. This persists until each individual app is restarted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1951878/+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 1951878] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1951878/+attachment/5561008/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1951878 Title: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session Status in gtk+3.0 package in Ubuntu: Confirmed Status in xwayland package in Ubuntu: Confirmed Bug description: Ubuntu 21.10 on Wayland session mutter 40.5-1ubuntu3~21.10.1 My apologies if this does not belong in mutter but because it happens in multiple applications, it's my best guess. This is a weird bug because I don't know what causes it but it happens consistently after normal usage which for me means several times leaving the laptop idle and unlocking. If I leave gnome-terminal and/or evince open, eventually any UI action like switching from multiple tabs, opening context menu etc will output the following to journal gnome-terminal-[2393]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window evince[3213]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window I suspect this may happen with other gtk apps as well. This persists until each individual app is restarted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1951878/+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 1960898] Re: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[
#5 "gsettings set org.gnome.shell.extensions.dash-to-dock show-mounts false" helped. Login now work. Thanks a lot. -- 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/1960898 Title: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[0].isObject()) from ubuntu- d...@ubuntu.com/locations.js:1108 Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: Hardware: https://linux-hardware.org/?probe=1055dc7082 Worked without Problem in 21.04 Had some flicker and problem with the left dock in 21.10 not working since updating to 22.04 now I'm running xorg. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-450/libnvidia-gl-450_450.102.04-0ubuntu2_amd64.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Tue Feb 15 08:07:04 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-08-15 (183 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 41.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-02-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1960898/+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 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
Hirsute is EOL so closing this bug. Please open a new one if the problem still persists with one of the supported series. ** Changed in: linux-firmware (Ubuntu Hirsute) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" Status in amd: New Status in linux-firmware package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in linux-firmware source package in Hirsute: Won't Fix Bug description: After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and severe GPU instability. When this happens, I see this error in dmesg: [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 pid 1236) [20061.061103] amdgpu :03:00.0: amdgpu: in page starting at address 0x80401000 from client 27 [20061.061135] amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00101031 [20061.061147] amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [20061.061157] amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 [20061.061167] amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 [20061.061174] amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [20061.061183] amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 [20061.061189] amdgpu :03:00.0: amdgpu: RW: 0x0 I'll attach a couple of full dmesgs that I collected. Many of the times when this happens, the screen and keyboard freeze irreversibly (I tried waiting for more than 30 minutes, but it doesn't help). I can still log in via ssh though. When there's no freeze, I can continue using the computer normally, but the laptop fans keep running are always running and the battery depletes fast. There's probably something on a permanent loop either in the kernel or in the GPU. This bug happens several times a day, rendering the machine so unstable as to be almost unusable. It is a severe regression and I'm aghast that it passed AMD's Quality Assurance. After downgrading back to linux-firmware 1.190.5, the machine is back to the previous, mostly-reliable state. Which is to say, this bug is gone, I'm just left with the other amdgpu suspend bug I've learned to live with since I bought this computer. Please revert the amdgpu firmware in this package as soon as possible. This is unbearable. Relevant information: Ubuntu version: 21.04 Linux kernel: 5.11.0-17-generic x86_64 CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c1) Laptop model: Lenovo Ideapad S145 To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960898] Re: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[
** Tags added: rls-jj-incoming -- 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/1960898 Title: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[0].isObject()) from ubuntu- d...@ubuntu.com/locations.js:1108 Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: Hardware: https://linux-hardware.org/?probe=1055dc7082 Worked without Problem in 21.04 Had some flicker and problem with the left dock in 21.10 not working since updating to 22.04 now I'm running xorg. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-450/libnvidia-gl-450_450.102.04-0ubuntu2_amd64.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Tue Feb 15 08:07:04 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-08-15 (183 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 41.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-02-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1960898/+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 1952107] Re: Google Contacts API Deprecated
Here just a little workaround for Ubuntu 18.04.6 LTS and Gnome 3.28.2. I suppose it could work with other distributions: 1-backup your evolution data 2-install to upgrade evolution from 3.28 to 3.42 via flatpack (https://flathub.org/apps/details/org.gnome.Evolution) 3-import evolution data from the previous backup 4-reboot and I have all contacts, calendars and tasks working again! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated Status in evolution-data-server: Unknown Status in evolution package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution source package in Focal: Fix Committed Status in evolution-data-server source package in Focal: Fix Committed Status in evolution source package in Impish: Fix Released Status in evolution-data-server source package in Impish: Fix Released Bug description: * Impact The google contacts integration with the GNOME component will stop working since it relies on an API which is going to be shutdown * Testcase - use evolution - add a google account - go the contacts section The contacts stored on the google account should be listed, no error should be displayed * Regression potential The patch changes the google contact backend so any potential issue is likely to be with contacts integration. I opened Evolution today and a red banner appeared on top with the following message: > Failed to connect address book “ : Contacts” > Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. I found the upstream bug report for this[0], which references the commit[1] that fixes it. However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 3.40.4-1. Is it possible to backport this commit so that Evolution will continue to work properly? [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658 [1]: https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+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 1960313] Re: [snap] chromium crashes regularly
I'm embarrassed now as I'd not detected that (and further telegram was also shutdown & I'd not even noticed..) Alas I'm somewhat aware of disk space issues.. (but deal with that only if the box won't let me login) but as I'd not been denied login for awhile hadn't noticed how serious it'd become.. You were spot on - OOM errors (chromium, then telegram) THANK YOU FOR THE SUPPORT :) & sorry I'd not picked the issue & my issues. Feb 15 17:10:20 d960-ubu2 systemd-oomd[949]: Killed /user.slice/user-1000.slice/user@1000.service/app.slice/snap.chromium.chromium.82bbbfd7-c79b-4b57-b425-e543631ca054.scope due to memory p> Feb 15 17:10:22 d960-ubu2 mtp-probe[446025]: checking bus 5, device 89: "/sys/devices/pci:00/:00:1a.2/usb5/5-2" Feb 15 17:10:23 d960-ubu2 systemd[5610]: snap.chromium.chromium.82bbbfd7-c79b-4b57-b425-e543631ca054.scope: Consumed 5h 29min 24.000s CPU time. Feb 15 17:10:22 d960-ubu2 mtp-probe[446025]: bus: 5, device: 89 was not an MTP device Feb 15 17:10:23 d960-ubu2 upowerd[151570]: treating change event as add on /sys/devices/pci:00/:00:1a.2/usb5/5-2 Feb 15 17:10:23 d960-ubu2 mtp-probe[446048]: checking bus 5, device 89: "/sys/devices/pci:00/:00:1a.2/usb5/5-2" Feb 15 17:10:23 d960-ubu2 mtp-probe[446048]: bus: 5, device: 89 was not an MTP device Feb 15 17:10:34 d960-ubu2 kernel: usb 5-2: input irq status -75 received Feb 15 17:10:34 d960-ubu2 kernel: usb 5-2: USB disconnect, device number 89 Feb 15 17:10:35 d960-ubu2 kernel: usb 5-2: new low-speed USB device number 90 using uhci_hcd Feb 15 17:10:35 d960-ubu2 kernel: usb 5-2: New USB device found, idVendor=0461, idProduct=4d15, bcdDevice= 2.00 Feb 15 17:10:35 d960-ubu2 kernel: usb 5-2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 Feb 15 17:10:35 d960-ubu2 kernel: usb 5-2: Product: USB Optical Mouse Feb 15 17:10:35 d960-ubu2 kernel: input: USB Optical Mouse as /devices/pci:00/:00:1a.2/usb5/5-2/5-2:1.0/0003:0461:4D15.01CF/input/input499 Feb 15 17:10:35 d960-ubu2 kernel: hid-generic 0003:0461:4D15.01CF: input,hidraw0: USB HID v1.11 Mouse [USB Optical Mouse] on usb-:00:1a.2-2/input0 Feb 15 17:10:35 d960-ubu2 upowerd[151570]: treating change event as add on /sys/devices/pci:00/:00:1a.2/usb5/5-2 Feb 15 17:10:35 d960-ubu2 mtp-probe[446683]: checking bus 5, device 90: "/sys/devices/pci:00/:00:1a.2/usb5/5-2" Feb 15 17:10:35 d960-ubu2 mtp-probe[446683]: bus: 5, device: 90 was not an MTP device Feb 15 17:10:35 d960-ubu2 mtp-probe[446698]: checking bus 5, device 90: "/sys/devices/pci:00/:00:1a.2/usb5/5-2" Feb 15 17:10:35 d960-ubu2 mtp-probe[446698]: bus: 5, device: 90 was not an MTP device Feb 15 17:10:36 d960-ubu2 systemd-oomd[949]: Killed /user.slice/user-1000.slice/user@1000.service/app.slice/snap.telegram-desktop.telegram-desktop.c0a93946-0960-44ed-aeb3-f9903b01056b.scope> Feb 15 17:10:36 d960-ubu2 systemd[5610]: snap.telegram-desktop.telegram-desktop.c0a93946-0960-44ed-aeb3-f9903b01056b.scope: Consumed 49min 26.108s CPU time. Feb 15 17:10:57 d960-ubu2 kernel: usb 5-2: reset low-speed USB device number 90 using uhci_hcd ** Changed in: chromium-browser (Ubuntu) Status: New => Invalid -- 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/1960313 Title: [snap] chromium crashes regularly Status in chromium-browser package in Ubuntu: Invalid Bug description: This was initially mentioned here (https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb- to-snap-transition/11179/317) ** Description For awhile now I just find my chromium just closes and is gone. It’s been at least the last two updates (I get the nag screen on my screen telling me an update is available; I tend to ignore it but reboot my box every ~fortnight so it’ll update at least once per fortnight as I ensure it’s upgraded before I load it after reboot). It’s ~10:40 local time, and I’ve lost the chromium snap at least twice today… no clues as to why, just I get to see my wallpaper on that part of my monitor as the window silently disappears. On re-opening I get a ‘closed ; do you want to restore you tabs’ dialog (something like that anyway) which works, but my box has been up ~13 days, and it was giving me trouble before this reboot as I hoped that reboot would help; alas no; neither last update(s). If I was to guess how long, I'd guess 20-30 days if not more; ie. I'm basing that on two ~14 day reboot cycles... I can't recall if started during the last cycle or just prior to my second-last reboot ~28 days ago As I file this bug; it's now ~23:15 and whilst I mentioned it'd closed twice prior to ~10:40 (I turn box on ~07:30), I'm pretty sure the window has not closed since I posted on the community hub. I'm not usually using the window when it closes; though its closed ~twice whilst I'm using it. **
[Desktop-packages] [Bug 1960917] [NEW] Please remove gnome-desktop3, replaced by gnome-desktop
Public bug reported: Please remove the gnome-desktop3 source package. Its binaries are now all provided by the gnome-desktop source package. We will be dropping the gnome-desktop3 source package from Debian soon too. ** Affects: gnome-desktop3 (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1960917 Title: Please remove gnome-desktop3, replaced by gnome-desktop Status in gnome-desktop3 package in Ubuntu: New Bug description: Please remove the gnome-desktop3 source package. Its binaries are now all provided by the gnome-desktop source package. We will be dropping the gnome-desktop3 source package from Debian soon too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1960917/+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 1960848] Re: sane-backends stuck in -proposed due to gscan2pdf autopkgtest failure
I've got a fix for this, and I'll upload a new upstream version of gscan2pdf to fix this ASAP, I hope in the next 12 hours. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1960848 Title: sane-backends stuck in -proposed due to gscan2pdf autopkgtest failure Status in gscan2pdf package in Ubuntu: New Status in sane-backends package in Ubuntu: New Status in gscan2pdf package in Debian: New Bug description: Version 1.1.1-2ubuntu1 of sane-backends does not migrate to jammy since the autopkgtest for gscan2pdf fails for multiple architectures. It's actually the upstream tests which fail, and gscan2pdf also fails to build on Debian unstable with the very same errors: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005576 Probably a gscan2pdf rebuild would fail on Ubuntu too, but I haven't confirmed that. Several other packages are blocked from migration because of this problem with gscan2pdf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/1960848/+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 1960768] Re: fwupd crash on stop
** Changed in: libgusb (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgusb in Ubuntu. https://bugs.launchpad.net/bugs/1960768 Title: fwupd crash on stop Status in OEM Priority Project: In Progress Status in fwupd package in Ubuntu: Invalid Status in libgusb package in Ubuntu: Fix Released Status in libusb package in Ubuntu: Invalid Bug description: I can reproduce crash with a similar stack as below as I stop fwupd service. https://errors.ubuntu.com/problem/4bfcf571c017010afe4775687ff2a9ca7ff79661 also test fwupd 1.7.5 (https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd175) still can reproduce this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1960768/+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 1960768] Re: fwupd crash on stop
This bug was fixed in the package libgusb - 0.3.10-1 --- libgusb (0.3.10-1) unstable; urgency=medium * New upstream version (0.3.10) - Fixes hangs on cleanup introduced in 0.3.8. (LP: #1960768) -- Mario Limonciello Mon, 14 Feb 2022 10:37:07 -0600 ** Changed in: libgusb (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgusb in Ubuntu. https://bugs.launchpad.net/bugs/1960768 Title: fwupd crash on stop Status in OEM Priority Project: In Progress Status in fwupd package in Ubuntu: Invalid Status in libgusb package in Ubuntu: Fix Released Status in libusb package in Ubuntu: Invalid Bug description: I can reproduce crash with a similar stack as below as I stop fwupd service. https://errors.ubuntu.com/problem/4bfcf571c017010afe4775687ff2a9ca7ff79661 also test fwupd 1.7.5 (https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd175) still can reproduce this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1960768/+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 1960313] Re: [snap] chromium crashes regularly
You're welcome, I'm glad we eventually figured it out. -- 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/1960313 Title: [snap] chromium crashes regularly Status in chromium-browser package in Ubuntu: Invalid Bug description: This was initially mentioned here (https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb- to-snap-transition/11179/317) ** Description For awhile now I just find my chromium just closes and is gone. It’s been at least the last two updates (I get the nag screen on my screen telling me an update is available; I tend to ignore it but reboot my box every ~fortnight so it’ll update at least once per fortnight as I ensure it’s upgraded before I load it after reboot). It’s ~10:40 local time, and I’ve lost the chromium snap at least twice today… no clues as to why, just I get to see my wallpaper on that part of my monitor as the window silently disappears. On re-opening I get a ‘closed ; do you want to restore you tabs’ dialog (something like that anyway) which works, but my box has been up ~13 days, and it was giving me trouble before this reboot as I hoped that reboot would help; alas no; neither last update(s). If I was to guess how long, I'd guess 20-30 days if not more; ie. I'm basing that on two ~14 day reboot cycles... I can't recall if started during the last cycle or just prior to my second-last reboot ~28 days ago As I file this bug; it's now ~23:15 and whilst I mentioned it'd closed twice prior to ~10:40 (I turn box on ~07:30), I'm pretty sure the window has not closed since I posted on the community hub. I'm not usually using the window when it closes; though its closed ~twice whilst I'm using it. ** Limited details sorry I'm not very specific here sorry, I'd file it as 'incomplete', but I don't know how/where to get details. As a snap there is nothing in /var/crash; so as an aside; is there somewhere I can look for clues as to why etc. (like the .crash file in /var/crash, even if I can only understand bits of it) My box is slow (2009 dell desktop)... and I've got in the habit of keeping a terminal open with `htop` running so I can detect if `firefox` (deb package still) or `chromium` are losing RAM.. I've concluded (rightly/wrongly) it's extension related; but if I recognize extensive swapping I look at the `htop` window and if either browser is using a load more RAM than usual & swap size is growing, I tend to close browser, wait for OS to recover the RAM, then re-open.. I've NOT been doing this with chromium of late; so I wondered if it's started crashing where I'd normally notice a slowing box & switch to my htop window, then close the window down... HOWEVER it could also be the regular crashing means the 'ram bleed' issue isn't getting bad enough for the thrashing to become a problem; it's usually only a problem after 2-4 days.. I'm convinced the issue (what I call 'ram bleed') is related to extensions, as the issue didn't occur with no extensions being used; but I prefer having privacy badger/ublock running - google docs offline - privacy badger - ublock origin - startpage (this was only ~recently added; not this one) FYI: I use same extensions with firefox too (except no startpage), and issue is the same; ~same frequency too (2-4 days) Anyway; if you can tell me if it'd be helpful to get/keep certain details; I'll do it, as I realize I'm not giving much. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt DRM.card0-DVI-I-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAs7hAkAQEBAQAaAQOANB14KrclpFdRoCYQUFS/74CzAKlAlQCBwIGAqcBxT4EAAjqAGHE4LUBYLEUACSUhAAAeZiFQsFEAGzBAcDYACSUhAAAe/QA3TB5SEQAKICAgICAg/ABLQUxFRDI0TU9OQ0EKAJo= modes: 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1280x1024 1440x900 1360x768 1280x800 1152x864 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 720x400 DRM.card0-DVI-I-2: enabled: enabled dpms: On status: connected edid-base64: AP///wAEchMBz9ogAhYUAQOAMx14KsKFpFZNnCUSUFSzDABxT4EAgYCVALMA0cABAQEBAjqAGHE4LUBYLEUA/h8RAAAe/QA4Sx5TEQAKICAgICAg/ABBY2VyIEcyMzVICiAg/wBMSkswVzAxNjQzMjAKAIg= modes: 1920x1080 1680x1050 1280x1024 1440x900 1280x800 1152x864 1024x768 1024x768 800x600 800x600 640x480 640x480 720x400 Date: Tue Feb 8 22:48:11 2022 DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/sda4 xfs32G 32G 63M 100% /home tmpfs tmpfs
Re: [Desktop-packages] [Bug 1956348] Re: Chromium uses 100% CPU after upgrade to 20.04
It looks like the issue is resolved because it's no longer in the new version (98). Let me know if you still want apport-collect output. -Original Message- From: Olivier Tilloy <1956...@bugs.launchpad.net> Reply-To: Bug 1956348 <1956...@bugs.launchpad.net> To: al...@gmx.com Subject: [Bug 1956348] Re: Chromium uses 100% CPU after upgrade to 20.04 Date: Wed, 09 Feb 2022 10:38:21 - Can you please run `apport-collect 1956348` to attach additional debuginformation to this bug? Is this still happening with the latest revision of the chromium snap inthe stable channel? ** Summary changed: - Chromium uses 100% CPU after upgrade to 20.04+ [snap] Chromium uses 100% CPU after upgrade to 20.04 ** Tags removed: chromium chromium-browser** Tags added: snap ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- 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/1956348 Title: [snap] Chromium uses 100% CPU after upgrade to 20.04 Status in chromium-browser package in Ubuntu: Incomplete Bug description: I recently upgraded from 18.04.6LTS to 20.04.3LTS (both 64-bit). From the very first time I launched chromium (after the upgrade) it started using 100% CPU. I'm running this on a VM which only has 1 CPU allocated (and 2GB RAM with 2GB SWAP) but I've been running 18.04 (and Chromium) on this VM for several months without any performance issues. https://askubuntu.com/questions/1271382/why-is-chromium-using-100-cpu also seems to confirm this as an issue/bug. Let me know if you need anything else as it would be good to get this resolved ASAP. I've attached a screenshot showing the nature of the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1956348/+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 1960924] [NEW] qpdf 10.6.1 not syncing?
Public bug reported: I'm noticing that qpdf-10.6.1 is not syncing from Debian even though, as far as I can see, automatic sync freeze has not yet happened. There are some major changes in 10.6 that I would really like to get into Ubuntu because they include transitional code to help users migrate to qpdf 11. Is there something that needs to happen for this to sync? I don't want to miss the window. At this time, there are test failures in pikepdf because of a bug fix to qpdf in transcoding. We have determined that these test failures don't indicate a serious problem with either qpdf or pikepdf -- they are basically that pikepdf had some tests that were depending on incorrect qpdf functionality. For details, see https://github.com/pikepdf/pikepdf/issues/303 The pikepdf author is aware of the upcoming Ubuntu 22.04 freeze and is trying to get a fix in in time, but I'm hoping we can avoid getting into a situation where we miss the bus. There's a chance I might release 10.6.2 to fix one other minor transcoding issue, but I don't consider the issue to be important enough to justify a release. But if the pikepdf author wants a release to simplify his testing, I will do it. ** Affects: qpdf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1960924 Title: qpdf 10.6.1 not syncing? Status in qpdf package in Ubuntu: New Bug description: I'm noticing that qpdf-10.6.1 is not syncing from Debian even though, as far as I can see, automatic sync freeze has not yet happened. There are some major changes in 10.6 that I would really like to get into Ubuntu because they include transitional code to help users migrate to qpdf 11. Is there something that needs to happen for this to sync? I don't want to miss the window. At this time, there are test failures in pikepdf because of a bug fix to qpdf in transcoding. We have determined that these test failures don't indicate a serious problem with either qpdf or pikepdf -- they are basically that pikepdf had some tests that were depending on incorrect qpdf functionality. For details, see https://github.com/pikepdf/pikepdf/issues/303 The pikepdf author is aware of the upcoming Ubuntu 22.04 freeze and is trying to get a fix in in time, but I'm hoping we can avoid getting into a situation where we miss the bus. There's a chance I might release 10.6.2 to fix one other minor transcoding issue, but I don't consider the issue to be important enough to justify a release. But if the pikepdf author wants a release to simplify his testing, I will do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1960924/+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 1960768] Re: fwupd crash on stop
I test the libgusb from jammy-proposed, and it fixed this issue on a machine that previously can reliably reproduce this issue. Guess it's on it's way to jammy or jammy-update channel. ** Changed in: oem-priority Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgusb in Ubuntu. https://bugs.launchpad.net/bugs/1960768 Title: fwupd crash on stop Status in OEM Priority Project: Fix Released Status in fwupd package in Ubuntu: Invalid Status in libgusb package in Ubuntu: Fix Released Status in libusb package in Ubuntu: Invalid Bug description: I can reproduce crash with a similar stack as below as I stop fwupd service. https://errors.ubuntu.com/problem/4bfcf571c017010afe4775687ff2a9ca7ff79661 also test fwupd 1.7.5 (https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd175) still can reproduce this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1960768/+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 1956348] Re: [snap] Chromium uses 100% CPU after upgrade to 20.04
Thanks for following up! No need for apport data if the issue appears to be resolved. I'm closing the bug, feel free to re-open if it happens again. ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1956348 Title: [snap] Chromium uses 100% CPU after upgrade to 20.04 Status in chromium-browser package in Ubuntu: Fix Released Bug description: I recently upgraded from 18.04.6LTS to 20.04.3LTS (both 64-bit). From the very first time I launched chromium (after the upgrade) it started using 100% CPU. I'm running this on a VM which only has 1 CPU allocated (and 2GB RAM with 2GB SWAP) but I've been running 18.04 (and Chromium) on this VM for several months without any performance issues. https://askubuntu.com/questions/1271382/why-is-chromium-using-100-cpu also seems to confirm this as an issue/bug. Let me know if you need anything else as it would be good to get this resolved ASAP. I've attached a screenshot showing the nature of the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1956348/+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 1960848] Re: sane-backends stuck in -proposed due to gscan2pdf autopkgtest failure
Great news, Jeffrey. Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1960848 Title: sane-backends stuck in -proposed due to gscan2pdf autopkgtest failure Status in gscan2pdf package in Ubuntu: New Status in sane-backends package in Ubuntu: New Status in gscan2pdf package in Debian: New Bug description: Version 1.1.1-2ubuntu1 of sane-backends does not migrate to jammy since the autopkgtest for gscan2pdf fails for multiple architectures. It's actually the upstream tests which fail, and gscan2pdf also fails to build on Debian unstable with the very same errors: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005576 Probably a gscan2pdf rebuild would fail on Ubuntu too, but I haven't confirmed that. Several other packages are blocked from migration because of this problem with gscan2pdf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/1960848/+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 1959596] Re: Applications end up in session scope, rather than per .desktop scope
I feel the way we launch applications from the dock also may imapct... Just to be clear, do we have a difference here? App launched from overview VS app launched from dock -- 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/1959596 Title: Applications end up in session scope, rather than per .desktop scope Status in gnome-shell package in Ubuntu: New Status in gnome-shell source package in Jammy: New Bug description: During systemd-oomd install in jammy (w/ GNOME session) today, I noticed that applications ended up in the wrong control group - in the session scope, rather than per .desktop one: Control group /: -.slice ├─user.slice │ └─user-1000.slice │ ├─user@1000.service │ │ ├─session.slice │ │ │ ├─xdg-document-portal.service │ │ │ │ ├─4514 /usr/libexec/xdg-document-portal │ │ │ │ └─4556 fusermount3 -o rw,nosuid,nodev,fsname=portal,auto_unmount,subt… │ │ │ ├─xdg-desktop-portal.service │ │ │ │ └─6186 /usr/libexec/xdg-desktop-portal │ │ │ ├─pipewire-pulse.service │ │ │ │ └─4473 /usr/bin/pipewire-pulse │ │ │ ├─wireplumber.service │ │ │ │ └─4472 /usr/bin/wireplumber │ │ │ └─pipewire.service │ │ │ └─4461 /usr/bin/pipewire │ │ ├─background.slice │ │ │ └─tracker-miner-fs-3.service │ │ │ └─4940 /usr/libexec/tracker-miner-fs-3 │ │ ├─user.slice │ │ │ └─podman-pause-6313308764925138924.scope │ │ │ └─4602 /usr/bin/podman │ │ ├─app.slice │ │ │ ├─gvfs-goa-volume-monitor.service │ │ │ │ └─5417 /usr/libexec/gvfs-goa-volume-monitor │ │ │ ├─snap.syncthing.syncthing.908e68e0-47a9-47b6-80b0-a6a3afdd4f24.scope │ │ │ │ ├─4470 /snap/syncthing/501/syncthing │ │ │ │ └─5510 /snap/syncthing/501/syncthing │ │ │ ├─xdg-permission-store.service │ │ │ │ └─4527 /usr/libexec/xdg-permission-store │ │ │ ├─snap.spotify.spotify.b3c54917-38c3-473b-8774-b90e1d30a8c3.scope │ │ │ │ ├─198100 /snap/spotify/57/usr/share/spotify/spotify │ │ │ │ ├─198169 /snap/spotify/57/usr/share/spotify/spotify --type=zygote --n… │ │ │ │ ├─198170 /snap/spotify/57/usr/share/spotify/spotify --type=zygote --n… │ │ │ │ ├─198188 /snap/spotify/57/usr/share/spotify/spotify --type=gpu-proces… │ │ │ │ ├─198205 /snap/spotify/57/usr/share/spotify/spotify --type=utility --… │ │ │ │ ├─198208 /snap/spotify/57/usr/share/spotify/spotify --type=utility --… │ │ │ │ └─198235 /snap/spotify/57/usr/share/spotify/spotify --type=renderer -… │ │ │ ├─evolution-calendar-factory.service │ │ │ │ └─6018 /usr/libexec/evolution-calendar-factory │ │ │ ├─xdg-desktop-portal-gnome.service │ │ │ │ └─6193 /usr/libexec/xdg-desktop-portal-gnome │ │ │ ├─dconf.service │ │ │ │ └─5837 /usr/libexec/dconf-service │ │ │ ├─gvfs-daemon.service │ │ │ │ ├─ 4515 /usr/libexec/gvfsd │ │ │ │ ├─ 4531 /usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f │ │ │ │ ├─ 8485 /usr/libexec/gvfsd-http --spawner :1.4 /org/gtk/gvfs/exec_spa… │ │ │ │ ├─29658 /usr/libexec/gvfsd-trash --spawner :1.4 /org/gtk/gvfs/exec_sp… │ │ │ │ └─29990 /usr/libexec/gvfsd-burn --spawner :1.4 /org/gtk/gvfs/exec_spa… │ │ │ ├─evolution-source-registry.service │ │ │ │ └─5820 /usr/libexec/evolution-source-registry │ │ │ ├─gvfs-udisks2-volume-monitor.service │ │ │ │ └─5202 /usr/libexec/gvfs-udisks2-volume-monitor │ │ │ ├─app-org.gnome.Terminal.slice │ │ │ │ ├─gnome-terminal-server.service │ │ │ │ │ └─8577 /usr/libexec/gnome-terminal-server │ │ │ │ └─vte-spawn-e31cc856-c6d7-4247-935c-6d28706ab542.scope │ │ │ │ ├─ 8595 -bash │ │ │ │ ├─ 8617 tmux -u -2 -f /usr/share/byobu/profiles/tmuxrc new-session… │ │ │ │ ├─ 8648 tmux -u -2 -f /usr/share/byobu/profiles/tmuxrc new-session… │ │ │ │ ├─ 8655 /bin/bash │ │ │ │ ├─ 8749 journalctl -f │ │ │ │ ├─ 25429 /bin/bash │ │ │ │ ├─179012 /bin/bash │ │ │ │ ├─208170 systemd-cgls │ │ │ │ └─208171 xclip │ │ │ ├─gpg-agent.service │ │ │ │ ├─29718 /usr/bin/gpg-agent --supervised │ │ │ │ └─70766 scdaemon --multi-server │ │ │ ├─gvfs-gphoto2-volume-monitor.service │ │ │ │ └─5403 /usr/libexec/gvfs-gphoto2-volume-monitor │ │ │ ├─xdg-desktop-portal-gtk.service │ │ │ │ └─7143 /usr/libexec/xdg-desktop-portal-gtk │ │ │ ├─obex.service │ │ │ │ └─63426 /usr/lib/bluetooth/obexd │ │ │ ├─at-spi-dbus-bus.service │ │ │ │ ├─5443 /usr/libexec/at-spi-bus-launcher │ │ │ │ ├─5457 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2… │ │ │ │ └─5886 /usr/libexec/at-spi2-registryd --use-gnome-session │ │ │ ├─gvfs-metadata.service │ │ │ │ └─5931 /usr/libexec/gvfsd-metadata │ │ │ ├─dbus.service │ │ │ │ ├─ 4508 /usr/bin/dbus-daemon --session --address=systemd: --nofork --… │ │ │ │ ├─ 5431 /usr/libexec/goa-daemon │ │ │ │ ├─ 5513 /usr/libexec/goa-identit
[Desktop-packages] [Bug 1743366] Re: The user session should run under systemd
@Paride, thanks, I'm going to close it if it was fixed it's not the same issue anymore, also Iain isn't working on it at this point? Bug #1959596 is likely the regression you mentioned ** Changed in: gnome-session (Ubuntu) Status: Confirmed => Fix Released ** Tags removed: rls-jj-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1743366 Title: The user session should run under systemd Status in gnome-session package in Ubuntu: Fix Released Bug description: Currently the user session doesn't run under systemd. As a consequence: [Original Description] In Bionic the systemd .path units are not properly activated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1743366/+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 1960898] Re: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided => High ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => New ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1960898 Title: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[0].isObject()) from ubuntu- d...@ubuntu.com/locations.js:1108 Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Hardware: https://linux-hardware.org/?probe=1055dc7082 Worked without Problem in 21.04 Had some flicker and problem with the left dock in 21.10 not working since updating to 22.04 now I'm running xorg. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-450/libnvidia-gl-450_450.102.04-0ubuntu2_amd64.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Tue Feb 15 08:07:04 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-08-15 (183 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 41.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-02-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1960898/+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 1951653] Re: can't use NM for ethernet device on 20.04 LTS because it is 'strictly unmanaged'
We want to implement an explicit allow- and denylist for NM to handle
certain device (or not). NM’s own matching engine is not powerful enough
to handle all of netplan’s matching needs, but it can also be
implemented with udev matching rules, using ENV{NM_UNMANAGED}="1"
We also want to discuss with the desktop team if we really need/want
/usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf (this is
a change in Ubuntu's default behavior)
--
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/1951653
Title:
can't use NM for ethernet device on 20.04 LTS because it is 'strictly
unmanaged'
Status in netplan.io package in Ubuntu:
Triaged
Status in network-manager package in Ubuntu:
New
Bug description:
I have tried to tell netplan to let my ethernet device be managed by
NetworkManager, so that I can then configure a pppoe connection on top
of this device.
This fails with:
# nmcli c up netplan-wan
Error: Connection activation failed: No suitable device found for this
connection (device lo not available because device is strictly unmanaged).
#
I don't know why it mentions 'lo' in that message, but the wan
interface is unmanaged (as are all devices on the system, but this one
is supposed to be managed):
# nmcli d status | grep wan
wan ethernet unmanaged --
#
After much searching, I've figured out that this comes from
/usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf:
keyfile]
unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma
Even though I've told netplan to use the NM renderer for this device,
the configuration emitted by netplan is insufficient to override this.
Using the workaround from
https://askubuntu.com/questions/71159/network-manager-says-device-not-
managed (sudo touch /etc/NetworkManager/conf.d/10-globally-managed-
devices.conf) doesn't work, but if I set NetworkManager as the
toplevel renderer in /etc/netplan,
/run/NetworkManager/conf.d/10-globally-managed-devices.conf is
emitted, which evidently DOES work. But I only have one device that I
want rendered by NM, so I shouldn't have to declare NM at the top
level of the yaml with a lot of duplication in order to get this
result.
I would argue that the 10-globally-managed-devices.conf should not be
there at all. But if it is going to be, then netplan needs to
consistently override it whenever there is any use of the
NetworkManager backend.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1951653/+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 1952947] Re: ubuntu-bug -w (using xprop) doesn't work under wayland
** Merge proposal linked: https://code.launchpad.net/~enr0n/ubuntu/+source/apport/+git/apport/+merge/415620 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11-utils in Ubuntu. https://bugs.launchpad.net/bugs/1952947 Title: ubuntu-bug -w (using xprop) doesn't work under wayland Status in apport package in Ubuntu: Triaged Status in x11-utils package in Ubuntu: Invalid Status in apport source package in Impish: Triaged Status in x11-utils source package in Impish: Invalid Status in apport source package in Jammy: Triaged Status in x11-utils source package in Jammy: Invalid Bug description: I want to report a Bug about the application Studio Controls. As I did it already quite a few times, I run "ubuntu-bug -w", get a message that I can select the window of the app I want to report a bug about after closing this message. I close the message with a click on the appropriate button. I click on the window of the application "Studio Controls" that I want to report a bug about. Nothing happens. I wait for a few minutes. Still nothing happens. In the console where I started ubuntu-bug -w I see the following message: (apport-gtk:11537): Gdk-CRITICAL **: 20:06:41.384: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed What I expect: Usaully when I use this procedure, after a relatively short while a new message window pops up asking me if the bug should be reported and showing me the data that is sent to Launchpad. I tried other applications, too, same effect. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: apport 2.20.11-0ubuntu71 ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18 Uname: Linux 5.13.0-21-lowlatency x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Dec 1 20:01:23 2021 InstallationDate: Installed on 2020-04-12 (597 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to impish on 2021-11-14 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1952947/+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 1959596] Re: Applications end up in session scope, rather than per .desktop scope
That did not make a difference, no -- 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/1959596 Title: Applications end up in session scope, rather than per .desktop scope Status in gnome-shell package in Ubuntu: New Status in gnome-shell source package in Jammy: New Bug description: During systemd-oomd install in jammy (w/ GNOME session) today, I noticed that applications ended up in the wrong control group - in the session scope, rather than per .desktop one: Control group /: -.slice ├─user.slice │ └─user-1000.slice │ ├─user@1000.service │ │ ├─session.slice │ │ │ ├─xdg-document-portal.service │ │ │ │ ├─4514 /usr/libexec/xdg-document-portal │ │ │ │ └─4556 fusermount3 -o rw,nosuid,nodev,fsname=portal,auto_unmount,subt… │ │ │ ├─xdg-desktop-portal.service │ │ │ │ └─6186 /usr/libexec/xdg-desktop-portal │ │ │ ├─pipewire-pulse.service │ │ │ │ └─4473 /usr/bin/pipewire-pulse │ │ │ ├─wireplumber.service │ │ │ │ └─4472 /usr/bin/wireplumber │ │ │ └─pipewire.service │ │ │ └─4461 /usr/bin/pipewire │ │ ├─background.slice │ │ │ └─tracker-miner-fs-3.service │ │ │ └─4940 /usr/libexec/tracker-miner-fs-3 │ │ ├─user.slice │ │ │ └─podman-pause-6313308764925138924.scope │ │ │ └─4602 /usr/bin/podman │ │ ├─app.slice │ │ │ ├─gvfs-goa-volume-monitor.service │ │ │ │ └─5417 /usr/libexec/gvfs-goa-volume-monitor │ │ │ ├─snap.syncthing.syncthing.908e68e0-47a9-47b6-80b0-a6a3afdd4f24.scope │ │ │ │ ├─4470 /snap/syncthing/501/syncthing │ │ │ │ └─5510 /snap/syncthing/501/syncthing │ │ │ ├─xdg-permission-store.service │ │ │ │ └─4527 /usr/libexec/xdg-permission-store │ │ │ ├─snap.spotify.spotify.b3c54917-38c3-473b-8774-b90e1d30a8c3.scope │ │ │ │ ├─198100 /snap/spotify/57/usr/share/spotify/spotify │ │ │ │ ├─198169 /snap/spotify/57/usr/share/spotify/spotify --type=zygote --n… │ │ │ │ ├─198170 /snap/spotify/57/usr/share/spotify/spotify --type=zygote --n… │ │ │ │ ├─198188 /snap/spotify/57/usr/share/spotify/spotify --type=gpu-proces… │ │ │ │ ├─198205 /snap/spotify/57/usr/share/spotify/spotify --type=utility --… │ │ │ │ ├─198208 /snap/spotify/57/usr/share/spotify/spotify --type=utility --… │ │ │ │ └─198235 /snap/spotify/57/usr/share/spotify/spotify --type=renderer -… │ │ │ ├─evolution-calendar-factory.service │ │ │ │ └─6018 /usr/libexec/evolution-calendar-factory │ │ │ ├─xdg-desktop-portal-gnome.service │ │ │ │ └─6193 /usr/libexec/xdg-desktop-portal-gnome │ │ │ ├─dconf.service │ │ │ │ └─5837 /usr/libexec/dconf-service │ │ │ ├─gvfs-daemon.service │ │ │ │ ├─ 4515 /usr/libexec/gvfsd │ │ │ │ ├─ 4531 /usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f │ │ │ │ ├─ 8485 /usr/libexec/gvfsd-http --spawner :1.4 /org/gtk/gvfs/exec_spa… │ │ │ │ ├─29658 /usr/libexec/gvfsd-trash --spawner :1.4 /org/gtk/gvfs/exec_sp… │ │ │ │ └─29990 /usr/libexec/gvfsd-burn --spawner :1.4 /org/gtk/gvfs/exec_spa… │ │ │ ├─evolution-source-registry.service │ │ │ │ └─5820 /usr/libexec/evolution-source-registry │ │ │ ├─gvfs-udisks2-volume-monitor.service │ │ │ │ └─5202 /usr/libexec/gvfs-udisks2-volume-monitor │ │ │ ├─app-org.gnome.Terminal.slice │ │ │ │ ├─gnome-terminal-server.service │ │ │ │ │ └─8577 /usr/libexec/gnome-terminal-server │ │ │ │ └─vte-spawn-e31cc856-c6d7-4247-935c-6d28706ab542.scope │ │ │ │ ├─ 8595 -bash │ │ │ │ ├─ 8617 tmux -u -2 -f /usr/share/byobu/profiles/tmuxrc new-session… │ │ │ │ ├─ 8648 tmux -u -2 -f /usr/share/byobu/profiles/tmuxrc new-session… │ │ │ │ ├─ 8655 /bin/bash │ │ │ │ ├─ 8749 journalctl -f │ │ │ │ ├─ 25429 /bin/bash │ │ │ │ ├─179012 /bin/bash │ │ │ │ ├─208170 systemd-cgls │ │ │ │ └─208171 xclip │ │ │ ├─gpg-agent.service │ │ │ │ ├─29718 /usr/bin/gpg-agent --supervised │ │ │ │ └─70766 scdaemon --multi-server │ │ │ ├─gvfs-gphoto2-volume-monitor.service │ │ │ │ └─5403 /usr/libexec/gvfs-gphoto2-volume-monitor │ │ │ ├─xdg-desktop-portal-gtk.service │ │ │ │ └─7143 /usr/libexec/xdg-desktop-portal-gtk │ │ │ ├─obex.service │ │ │ │ └─63426 /usr/lib/bluetooth/obexd │ │ │ ├─at-spi-dbus-bus.service │ │ │ │ ├─5443 /usr/libexec/at-spi-bus-launcher │ │ │ │ ├─5457 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2… │ │ │ │ └─5886 /usr/libexec/at-spi2-registryd --use-gnome-session │ │ │ ├─gvfs-metadata.service │ │ │ │ └─5931 /usr/libexec/gvfsd-metadata │ │ │ ├─dbus.service │ │ │ │ ├─ 4508 /usr/bin/dbus-daemon --session --address=systemd: --nofork --… │ │ │ │ ├─ 5431 /usr/libexec/goa-daemon │ │ │ │ ├─ 5513 /usr/libexec/goa-identity-service │ │ │ │ ├─ 5804 /usr/libexec/gnome-shell-calendar-server │ │ │ │ ├─ 5888 /usr/bin/gjs /usr/share/gnome-shell/org.gnome.
[Desktop-packages] [Bug 1960614] Re: Add mid: scheme handler to thunderbird.desktop
This bug was fixed in the package thunderbird - 1:91.6.1+build1-0ubuntu1 --- thunderbird (1:91.6.1+build1-0ubuntu1) jammy; urgency=medium * New upstream stable release (91.6.1build1) -- Olivier Tilloy Mon, 14 Feb 2022 20:35:29 +0100 ** Changed in: thunderbird (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1960614 Title: Add mid: scheme handler to thunderbird.desktop Status in thunderbird package in Ubuntu: Fix Released Bug description: Since thunderbird-91 version (actually even earlier, but only ESR releases are packaged in Ubuntu) it is possible to open particular messages from command line using Message-ID: thunderbird mid:a...@example.com See e.g. https://bugzilla.mozilla.org/264270 However to open links from other application "mid:" scheme should be advertised in the thunderbird.desktop file: MimeType=x-scheme-handler/mailto;application/x-xpinstall;x-scheme- handler/mid; Please, adjust this field in the desktop file. To check that the change has effect the following command may be used: xdg-open mid:a...@example.com Notice that it is not upstream issue. Thunderbird developers left desktop integration up to maintainers of Linux distributions. Long time ago it was possible to create such links to particular messages using thunderlink extension but migration from XUL to WebExtension add-ons broke it. Support of mid: scheme restores linking of mail messages from other applications. There is a related issue: request to add message/rfc822 MIME type in lp:1861262 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1960614/+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 1861262] Re: Add message/rfc822 to thunderbird.desktop
This bug was fixed in the package thunderbird - 1:91.6.1+build1-0ubuntu1 --- thunderbird (1:91.6.1+build1-0ubuntu1) jammy; urgency=medium * New upstream stable release (91.6.1build1) -- Olivier Tilloy Mon, 14 Feb 2022 20:35:29 +0100 ** Changed in: thunderbird (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1861262 Title: Add message/rfc822 to thunderbird.desktop Status in thunderbird package in Ubuntu: Fix Released Bug description: Please add message/rfc822 to thunderbird.desktop: -MimeType=x-scheme-handler/mailto;application/x-xpinstall; +MimeType=x-scheme-handler/mailto;application/x-xpinstall;message/rfc822; It will allow to open *.eml files. I attach an example eml file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1861262/+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 1960421] Re: webcal:// URLs do not open calendar application
This bug was fixed in the package thunderbird - 1:91.6.1+build1-0ubuntu1 --- thunderbird (1:91.6.1+build1-0ubuntu1) jammy; urgency=medium * New upstream stable release (91.6.1build1) -- Olivier Tilloy Mon, 14 Feb 2022 20:35:29 +0100 ** Changed in: thunderbird (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1960421 Title: webcal:// URLs do not open calendar application Status in firefox package in Ubuntu: Invalid Status in thunderbird package in Ubuntu: Fix Released Bug description: I have Thunderbird 91.5.0 (64-Bit) installed on Ubuntu 20.04 and use it for calendaring. When clicking on a webcal:// or webcals:// URL in Firefox 96.0 (64-Bit) on Ubuntu 20.04, nothing happens. I expect that Thunderbird opens and asks to subscribe to the calendar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1960421/+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 1953052] Re: In Jammy sound level reset after reboot
Problem reappeared -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1953052 Title: In Jammy sound level reset after reboot Status in alsa-utils package in Ubuntu: Confirmed Bug description: After reboot sound level is reset ignoring the level set in previous session. I manually set the sound output level at next boot the sound is set at a different level (about 70%) Expected: the sound level is persistent across power off/on What happens : sound level is set at a different level (about 70%) Note: this problem does not occur on different partitions of same PC running Ubuntu 20.04 or 21.10 corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center gnome-control-center: Installed: 1:41.1-1ubuntu1 Candidate: 1:41.1-1ubuntu1 Version table: *** 1:41.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-p3-jj-1130:~$ inxi -Fx System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish) Machine: Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: Mobo: Dell model: 0C1PF2 v: A00 serial: UEFI: Dell v: 1.5.0 date: 12/17/2019 Battery: ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) volts: 11.3 min: 11.4 model: SWD-ATL3.618 DELL WJPC403 status: Discharging CPU: Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP arch: Ice Lake rev: 5 cache: L2: 6 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19046 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 710 3: 706 4: 714 5: 966 6: 712 7: 724 8: 821 Graphics: Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: kernel bus-ID: 00:02.0 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-6:3 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell driver: loaded: i915 note: n/a (using device driver) resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 21.2.2 direct render: Yes Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes Sound Server-2: PulseAudio v: 15.0 running: yes Sound Server-3: PipeWire v: 0.3.40 running: yes Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 v: kernel port: 3000 bus-ID: 01:00.0 IF: enp1s0 state: down mac: 98:e7:43:59:19:19 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Dell driver: ath10k_pci v: kernel bus-ID: 02:00.0 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9 Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 1-10:4 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: D8:12:65:B8:21:BA Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%) ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 512GB size: 476.94 GiB temp: 24.9 C ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: /dev/nvme0n1p3 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: /dev/nvme0n1p1 Swap: Alert: No swap data was found. Sensors: System Temperatures: cpu: 27.8 C mobo: N/A Fan Speeds (RPM): cpu: 0 Info: Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 1785 Shell: Bash v: 5.1.12 inxi: 3.3.07 corrado@corrado-p3-jj-1130:~$ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-30 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) Package: gnome-control-center 1:41.1-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Tags: wayland-session jammy Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubunt
[Desktop-packages] [Bug 1960945] [NEW] package chromium-browser 97.0.4692.71-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error
Public bug reported: Failed on upgrade from Ubuntu 18.xx to latest version for Jetson nano. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 97.0.4692.71-0ubuntu0.18.04.1 Uname: Linux 4.9.253-tegra aarch64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: arm64 CasperMD5CheckResult: skip Date: Tue Feb 15 17:14:31 2022 Desktop-Session: 'None' 'None' 'None' Env: 'None' 'None' ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstalledPlugins: Load-Avg-1min: 1.52 Load-Processes-Running-Percent: 0.4% Lspci-vt: -[:00]---02.0-[01]00.0 Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller ProcKernelCmdLine: tegraid=21.1.2.0.0 ddr_die=4096M@2048M section=512M memtype=0 vpr_resize usb_port_owner_info=0 lane_owner_info=0 emc_max_dvfs=0 touch_id=0@63 video=tegrafb no_console_suspend=1 console=ttyS0,115200n8 debug_uartport=lsport,4 earlyprintk=uart8250-32bit,0x70006000 maxcpus=4 usbcore.old_scheme_first=1 lp0_vec=0x1000@0xff78 core_edp_mv=1125 core_edp_ma=4000 gpt tegra_fbmem=0x14@0x92ca9000 is_hdmi_initialised=1 earlycon=uart8250,mmio32,0x70006000 root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 quiet root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: chromium-browser Title: package chromium-browser 97.0.4692.71-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2022-02-15 (0 days ago) acpidump: modified.conffile..etc.default.chromium-browser: [deleted] ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 focal need-duplicate-check -- 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/1960945 Title: package chromium-browser 97.0.4692.71-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 Status in chromium-browser package in Ubuntu: New Bug description: Failed on upgrade from Ubuntu 18.xx to latest version for Jetson nano. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 97.0.4692.71-0ubuntu0.18.04.1 Uname: Linux 4.9.253-tegra aarch64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: arm64 CasperMD5CheckResult: skip Date: Tue Feb 15 17:14:31 2022 Desktop-Session: 'None' 'None' 'None' Env: 'None' 'None' ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstalledPlugins: Load-Avg-1min: 1.52 Load-Processes-Running-Percent: 0.4% Lspci-vt: -[:00]---02.0-[01]00.0 Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller ProcKernelCmdLine: tegraid=21.1.2.0.0 ddr_die=4096M@2048M section=512M memtype=0 vpr_resize usb_port_owner_info=0 lane_owner_info=0 emc_max_dvfs=0 touch_id=0@63 video=tegrafb no_console_suspend=1 console=ttyS0,115200n8 debug_uartport=lsport,4 earlyprintk=uart8250-32bit,0x70006000 maxcpus=4 usbcore.old_scheme_first=1 lp0_vec=0x1000@0xff78 core_edp_mv=1125 core_edp_ma=4000 gpt tegra_fbmem=0x14@0x92ca9000 is_hdmi_initialised=1 earlycon=uart8250,mmio32,0x70006000 root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 quiet root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: chromium-browser Title: package chromium-browser 97.0.4692.71-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2022-02-15 (0 days ago) acpidump: modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1960945/+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 1954649] Re: autopkgtest regressions with python3.10 as supported
** Changed in: ipywidgets (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1954649 Title: autopkgtest regressions with python3.10 as supported Status in ipywidgets package in Ubuntu: Fix Released Status in pygobject package in Ubuntu: Fix Released Status in pytest-twisted package in Ubuntu: New Status in python-b2sdk package in Ubuntu: New Status in python-hypothesis package in Ubuntu: Fix Released Status in python-taskflow package in Ubuntu: Fix Released Status in python3-defaults package in Ubuntu: New Status in skimage package in Ubuntu: Invalid Status in supysonic package in Ubuntu: Fix Released Status in vorta package in Ubuntu: Fix Released Status in ipywidgets package in Debian: New Status in pygobject package in Debian: Fix Released Status in pytest-twisted package in Debian: New Status in python-b2sdk package in Debian: Confirmed Status in python-hypothesis package in Debian: Fix Released Status in supysonic package in Debian: Fix Released Status in vorta package in Debian: Fix Released Bug description: This bug is for tracking the packages having autopkgtest regressions with python3.10 as a supported version, blocking migration of python3-defaults/3.9.7-4. All packages are in universe except pygobject and python-taskflow in main. All packages have RC bugs in Debian except python-taskflow which is based on a newer upstream version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipywidgets/+bug/1954649/+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 1960947] [NEW] Graphical issues for GtKGL in software rendering
Public bug reported: * Issue GTK applications using GL graphic show corruption problems under software rendering * Test case 1. install gtk-3-examples 2. $ LIBGL_ALWAYS_SOFTWARE=1 gtk3-demo 3. select the gl example, it should render without issues * Regression potentiel The change is in the GL backend so check for rendering issues in GTK softwares using GL, including flutter applications ** Affects: gtk+3.0 (Ubuntu) Importance: High Status: Fix Released ** Changed in: gtk+3.0 (Ubuntu) Status: New => Fix Released ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1960947 Title: Graphical issues for GtKGL in software rendering Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: * Issue GTK applications using GL graphic show corruption problems under software rendering * Test case 1. install gtk-3-examples 2. $ LIBGL_ALWAYS_SOFTWARE=1 gtk3-demo 3. select the gl example, it should render without issues * Regression potentiel The change is in the GL backend so check for rendering issues in GTK softwares using GL, including flutter applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1960947/+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 1960945] Re: package chromium-browser 97.0.4692.71-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error ex
Relevant excerpt from DpkgTerminalLog.txt: ==> Installing the chromium snap 2022-02-15T17:11:20Z INFO Waiting for automatic snapd restart... error: cannot perform the following tasks: - Mount snap "chromium" (1904) (systemctl command [start snap-chromium-1904.mount] failed with exit status 1: Job failed. See "journalctl -xe" for details. ) Can you please invoke "journalctl -xe" and scroll up to see if there is relevant information from snapd in the journal? Does installing the snap "manually" (i.e. "sudo snap install chromium") work? ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- 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/1960945 Title: package chromium-browser 97.0.4692.71-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 Status in chromium-browser package in Ubuntu: Incomplete Bug description: Failed on upgrade from Ubuntu 18.xx to latest version for Jetson nano. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 97.0.4692.71-0ubuntu0.18.04.1 Uname: Linux 4.9.253-tegra aarch64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: arm64 CasperMD5CheckResult: skip Date: Tue Feb 15 17:14:31 2022 Desktop-Session: 'None' 'None' 'None' Env: 'None' 'None' ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstalledPlugins: Load-Avg-1min: 1.52 Load-Processes-Running-Percent: 0.4% Lspci-vt: -[:00]---02.0-[01]00.0 Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller ProcKernelCmdLine: tegraid=21.1.2.0.0 ddr_die=4096M@2048M section=512M memtype=0 vpr_resize usb_port_owner_info=0 lane_owner_info=0 emc_max_dvfs=0 touch_id=0@63 video=tegrafb no_console_suspend=1 console=ttyS0,115200n8 debug_uartport=lsport,4 earlyprintk=uart8250-32bit,0x70006000 maxcpus=4 usbcore.old_scheme_first=1 lp0_vec=0x1000@0xff78 core_edp_mv=1125 core_edp_ma=4000 gpt tegra_fbmem=0x14@0x92ca9000 is_hdmi_initialised=1 earlycon=uart8250,mmio32,0x70006000 root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 quiet root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: chromium-browser Title: package chromium-browser 97.0.4692.71-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2022-02-15 (0 days ago) acpidump: modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1960945/+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 1954970] Re: remmina "Cannot connect to the RDP server ... via TLS. Check that the client and server support a common TLS version"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: freerdp2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to freerdp2 in Ubuntu. https://bugs.launchpad.net/bugs/1954970 Title: remmina "Cannot connect to the RDP server ... via TLS. Check that the client and server support a common TLS version" Status in freerdp2 package in Ubuntu: Confirmed Status in freerdp2 source package in Jammy: Confirmed Bug description: Xubuntu Jammy (21.04) after upgrade libfreerdp-client2-2 (2.3.0+dfsg1-2ubuntu2 => 2.4.1+dfsg1-1) libfreerdp2-2 (2.3.0+dfsg1-2ubuntu2 => 2.4.1+dfsg1-1) Remmina can't connect to any RDP server (Win2008 R2) with error: "Cannot connect to the RDP server ... via TLS. Check that the client and server support a common TLS version" Rollback to Impish version of libs libfreerdp-client2-2 2.3.0+dfsg1-2ubuntu2 libfreerdp2-2 2.3.0+dfsg1-2ubuntu2 makes it work normal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1954970/+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 1959140] Re: [needs-packaging] pls raise libwacom to 2.0.0 for new device support
Thanks for reporting. libwacom 2.0.0-2 was just synced from Debian and is now in Ubuntu Jammy https://bugs.launchpad.net/ubuntu/+source/libwacom/2.0.0-2 ** Changed in: libwacom (Ubuntu) Status: New => Fix Released ** Tags added: upgrade-software-version -- 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/1959140 Title: [needs-packaging] pls raise libwacom to 2.0.0 for new device support Status in libwacom package in Ubuntu: Fix Released Bug description: It would be nice to have up to date libwacom in Ubuntu 22.04 to support current hardware. https://github.com/linuxwacom/libwacom/releases/tag/libwacom-2.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1959140/+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 1878301] Re: Focal regression: poor discoverability for search in Ubuntu Software Center
+1000 Just installed Ubuntu for my mother today, and I learned her yesterday how to install a software. We were both confused (I'm a developer and I'm very confused about this "feature" too) about the fact that the search bar is hidden until we type some text on the keyboard. Today she called me trying to install a software (not listed in the featured softwares in the main page), and she didn't remember how to search for a particular software by name. Last month I installed Ubuntu for friends (30 years old, daly users of Android phone so used to softwares) and same thing: they called me 2 times to ask how to search for a software ? "is it possible to install another software than those that are listed in the main page ?" I've seen in Gnome's issues that Gnome devs thinks that this is a typical Gnome behavior; okay maybe; I hate Nautilus and most of Gnome apps for their "simple designs". But this is definitively not a typical Ubuntu design: when we display the "magical search bar" that appears after pressing super key, we see the search bar, really well highlighted in the center. I really think that software search bar should be obvious to find. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1878301 Title: Focal regression: poor discoverability for search in Ubuntu Software Center Status in GNOME Software: Unknown Status in gnome-software package in Ubuntu: Triaged Bug description: I wanted to install a new package. Launched Ubuntu Software and... how do I search for anything? Search is a key function. It should be front and center. I couldn't see it. That was annoying enough that I wanted to file a bug against it. In the process I did notice the lens icon in the top left, but seriously - does that look easily discoverable to anyone? There's usually nothing in that cornerl so users don't look there, and the contrast is poor, which makes it very easy to not notice. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1878301/+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 1960954] [NEW] Update gvfs to 1.50
Public bug reported: gvfs 1.50 switched to libsoup3 which we will not be including in Ubuntu 22.04 LTS.2 We should stay with the 1.48 series unless we want to revert this commit: https://gitlab.gnome.org/GNOME/gvfs/-/commit/beaaf78 https://gitlab.gnome.org/GNOME/gvfs/-/blob/master/NEWS ** Affects: gvfs (Ubuntu) Importance: Wishlist Status: Triaged ** Tags: jammy upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1960954 Title: Update gvfs to 1.50 Status in gvfs package in Ubuntu: Triaged Bug description: gvfs 1.50 switched to libsoup3 which we will not be including in Ubuntu 22.04 LTS.2 We should stay with the 1.48 series unless we want to revert this commit: https://gitlab.gnome.org/GNOME/gvfs/-/commit/beaaf78 https://gitlab.gnome.org/GNOME/gvfs/-/blob/master/NEWS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1960954/+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 1960898] Re: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[
Once you've enabled the mount point again, could you please tell me what
are you mountable devices?
In any case it would be helpful if you could manually edit (just use
sudo with your editor) the file /usr/share/gnome-
shell/extensions/ubuntu-d...@ubuntu.com/locations.js so that it contains
at around line 1108 (just after the initVolumePromises() definition):
print('o', object)
print('oc', object?.constructor)
print('ocp', object?.constructor?.prototype)
Then post the content of your journal here.
Another test you could do is try to remove these lines at all:
if (!(object instanceof Gio.Volume) ||
object.constructor.prototype._d2dPromisified)
return;
(or probably just remove '!(object instanceof Gio.Volume) ||').
--
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/1960898
Title:
Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool
InterfacePrototype::has_instance_impl(JSContext*, const
JS::CallArgs&): assertion failed: (args[0].isObject()) from ubuntu-
d...@ubuntu.com/locations.js:1108
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
New
Bug description:
Hardware: https://linux-hardware.org/?probe=1055dc7082
Worked without Problem in 21.04
Had some flicker and problem with the left dock in 21.10
not working since updating to 22.04
now I'm running xorg.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 41.3-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu76
Architecture: amd64
CasperMD5CheckMismatches:
./pool/restricted/n/nvidia-graphics-drivers-450/libnvidia-gl-450_450.102.04-0ubuntu2_amd64.deb
CasperMD5CheckResult: fail
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 15 08:07:04 2022
DisplayManager: gdm3
InstallationDate: Installed on 2021-08-15 (183 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
RelatedPackageVersions: mutter-common 41.3-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-02-14 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1960898/+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 1960848] Re: sane-backends stuck in -proposed due to gscan2pdf autopkgtest failure
I've uploaded a new upstream version, also to sid. Can you upload to jammy? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1960848 Title: sane-backends stuck in -proposed due to gscan2pdf autopkgtest failure Status in gscan2pdf package in Ubuntu: New Status in sane-backends package in Ubuntu: New Status in gscan2pdf package in Debian: New Bug description: Version 1.1.1-2ubuntu1 of sane-backends does not migrate to jammy since the autopkgtest for gscan2pdf fails for multiple architectures. It's actually the upstream tests which fail, and gscan2pdf also fails to build on Debian unstable with the very same errors: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005576 Probably a gscan2pdf rebuild would fail on Ubuntu too, but I haven't confirmed that. Several other packages are blocked from migration because of this problem with gscan2pdf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/1960848/+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 1960924] Re: qpdf 10.6.1 not syncing?
There will definitely be a 10.6.2 in the next day or two. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1960924 Title: qpdf 10.6.1 not syncing? Status in qpdf package in Ubuntu: New Bug description: I'm noticing that qpdf-10.6.1 is not syncing from Debian even though, as far as I can see, automatic sync freeze has not yet happened. There are some major changes in 10.6 that I would really like to get into Ubuntu because they include transitional code to help users migrate to qpdf 11. Is there something that needs to happen for this to sync? I don't want to miss the window. At this time, there are test failures in pikepdf because of a bug fix to qpdf in transcoding. We have determined that these test failures don't indicate a serious problem with either qpdf or pikepdf -- they are basically that pikepdf had some tests that were depending on incorrect qpdf functionality. For details, see https://github.com/pikepdf/pikepdf/issues/303 The pikepdf author is aware of the upcoming Ubuntu 22.04 freeze and is trying to get a fix in in time, but I'm hoping we can avoid getting into a situation where we miss the bus. There's a chance I might release 10.6.2 to fix one other minor transcoding issue, but I don't consider the issue to be important enough to justify a release. But if the pikepdf author wants a release to simplify his testing, I will do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1960924/+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 1960848] Re: sane-backends stuck in -proposed due to gscan2pdf autopkgtest failure
No need to. It will be sync'ed automatically in a few hours. Thanks again! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1960848 Title: sane-backends stuck in -proposed due to gscan2pdf autopkgtest failure Status in gscan2pdf package in Ubuntu: New Status in sane-backends package in Ubuntu: New Status in gscan2pdf package in Debian: New Bug description: Version 1.1.1-2ubuntu1 of sane-backends does not migrate to jammy since the autopkgtest for gscan2pdf fails for multiple architectures. It's actually the upstream tests which fail, and gscan2pdf also fails to build on Debian unstable with the very same errors: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005576 Probably a gscan2pdf rebuild would fail on Ubuntu too, but I haven't confirmed that. Several other packages are blocked from migration because of this problem with gscan2pdf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/1960848/+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 1952947] Re: ubuntu-bug -w (using xprop) doesn't work under wayland
** Branch linked: lp:~ubuntu-core-dev/ubuntu/jammy/apport/ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11-utils in Ubuntu. https://bugs.launchpad.net/bugs/1952947 Title: ubuntu-bug -w (using xprop) doesn't work under wayland Status in apport package in Ubuntu: Triaged Status in x11-utils package in Ubuntu: Invalid Status in apport source package in Impish: Triaged Status in x11-utils source package in Impish: Invalid Status in apport source package in Jammy: Triaged Status in x11-utils source package in Jammy: Invalid Bug description: I want to report a Bug about the application Studio Controls. As I did it already quite a few times, I run "ubuntu-bug -w", get a message that I can select the window of the app I want to report a bug about after closing this message. I close the message with a click on the appropriate button. I click on the window of the application "Studio Controls" that I want to report a bug about. Nothing happens. I wait for a few minutes. Still nothing happens. In the console where I started ubuntu-bug -w I see the following message: (apport-gtk:11537): Gdk-CRITICAL **: 20:06:41.384: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed What I expect: Usaully when I use this procedure, after a relatively short while a new message window pops up asking me if the bug should be reported and showing me the data that is sent to Launchpad. I tried other applications, too, same effect. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: apport 2.20.11-0ubuntu71 ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18 Uname: Linux 5.13.0-21-lowlatency x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Dec 1 20:01:23 2021 InstallationDate: Installed on 2020-04-12 (597 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to impish on 2021-11-14 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1952947/+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 1960972] [NEW] All snap applications missing from gnome-search after update
Public bug reported: After this "upgrade", snapd:amd64 2.53+21.10ubuntu1 2.54.2+21.10ubuntu1 (Some video drivers were upgraded at the same time, but this doesn't seem relevant.) ...all snap applications have disappeared from gnome-shell search. All snaps are still installed and can be executed with "snap run app". All applications work correctly when launched this way, except that they will be missing their dock icons showing the "gears"/missing icon indicator. Application icons are also missing in the Ubuntu Software Center. Reinstalling the snap applications affected does not help, including "snap remove --purge && snap install". Non-snap applications are unaffected. To reproduce, press super key and type the name of any installed in /snap. No snap applications appear but normal applications and files will be listed as usual. Tried to uninstall shell extensions removed and reboot. Nothing improved. --- gnome-shell logs complain of the following: Feb 15 15:26:56 gnome-shell[3135]: GNOME Shell started at Tue Feb 15 2022 15:26:53 GMT-0800 (PST) Feb 15 15:26:56 gnome-shell[3135]: Registering session with GDM Feb 15 15:27:03 ubuntu-appindicat...@ubuntu.com[3135]: Slack1, Impossible to lookup icon for 'Slack1_2-panel' in path /run/user/1000/.org.chromium.Chromium.cgr> Feb 15 15:27:03 ubuntu-appindicat...@ubuntu.com[3135]: unable to update icon for Slack1 Feb 15 15:27:09 gnome-shell[3135]: Failed to set the markup of the actor 'ClutterText': Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity — escape ampersand as & Feb 15 15:27:09 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell.SearchProvider2” on object at path /org/gnome/seahorse/Application Feb 15 15:27:09 gnome-shell[3135]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 5 but got 0 Feb 15 15:27:10 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell.SearchProvider2” on object at path /org/gnome/seahorse/Application Feb 15 15:27:10 gnome-shell[3135]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 5 but got 0 Feb 15 15:27:13 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Feb 15 15:27:13 gnome-shell[3135]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 5 but got 0 Feb 15 15:29:06 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell.SearchProvider2” on object at path /org/gnome/seahorse/Application Feb 15 15:29:06 gnome-shell[3135]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 5 but got 0 Feb 15 15:29:33 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell.SearchProvider2” on object at path /org/gnome/seahorse/Application Feb 15 15:29:33 gnome-shell[3135]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 5 but got 0 Feb 15 15:29:34 gnome-shell[3135]: Timelines with detached actors are not supported Feb 15 15:29:34 gnome-shell[3135]: Timelines with detached actors are not supported Feb 15 15:29:34 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell.SearchProvider2” on object at path /org/gnome/seahorse/Application Feb 15 15:29:34 gnome-shell[3135]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 5 but got 0 Feb 15 15:35:17 gnome-shell[3135]: Timelines with detached actors are not supported Feb 15 15:35:22 gnome-shell[3135]: Timelines with detached actors are not supported Feb 15 15:35:22 gnome-shell[3135]: Timelines with detached actors are not supported Feb 15 15:35:25 gnome-shell[3135]: Timelines with detached actors are not supported --- Description:Ubuntu 21.10 Release:21.10 gnome-shell: Installed: 40.
[Desktop-packages] [Bug 1960972] Re: All snap applications missing from gnome-search after update
Downgrading snapd to the previous version 2.53+21.10ubuntu1 resolves the issue. As such this may actually be a snapd issue, or something involving both communications between the two applications. Neither version of snapd logs any errors. -- 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/1960972 Title: All snap applications missing from gnome-search after update Status in gnome-shell package in Ubuntu: New Bug description: After this "upgrade", snapd:amd64 2.53+21.10ubuntu1 2.54.2+21.10ubuntu1 (Some video drivers were upgraded at the same time, but this doesn't seem relevant.) ...all snap applications have disappeared from gnome-shell search. All snaps are still installed and can be executed with "snap run app". All applications work correctly when launched this way, except that they will be missing their dock icons showing the "gears"/missing icon indicator. Application icons are also missing in the Ubuntu Software Center. Reinstalling the snap applications affected does not help, including "snap remove --purge && snap install". Non-snap applications are unaffected. To reproduce, press super key and type the name of any installed in /snap. No snap applications appear but normal applications and files will be listed as usual. Tried to uninstall shell extensions removed and reboot. Nothing improved. --- gnome-shell logs complain of the following: Feb 15 15:26:56 gnome-shell[3135]: GNOME Shell started at Tue Feb 15 2022 15:26:53 GMT-0800 (PST) Feb 15 15:26:56 gnome-shell[3135]: Registering session with GDM Feb 15 15:27:03 ubuntu-appindicat...@ubuntu.com[3135]: Slack1, Impossible to lookup icon for 'Slack1_2-panel' in path /run/user/1000/.org.chromium.Chromium.cgr> Feb 15 15:27:03 ubuntu-appindicat...@ubuntu.com[3135]: unable to update icon for Slack1 Feb 15 15:27:09 gnome-shell[3135]: Failed to set the markup of the actor 'ClutterText': Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity — escape ampersand as & Feb 15 15:27:09 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell.SearchProvider2” on object at path /org/gnome/seahorse/Application Feb 15 15:27:09 gnome-shell[3135]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 5 but got 0 Feb 15 15:27:10 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell.SearchProvider2” on object at path /org/gnome/seahorse/Application Feb 15 15:27:10 gnome-shell[3135]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 5 but got 0 Feb 15 15:27:13 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Feb 15 15:27:13 gnome-shell[3135]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 5 but got 0 Feb 15 15:29:06 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell.SearchProvider2” on object at path /org/gnome/seahorse/Application Feb 15 15:29:06 gnome-shell[3135]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 5 but got 0 Feb 15 15:29:33 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell.SearchProvider2” on object at path /org/gnome/seahorse/Application Feb 15 15:29:33 gnome-shell[3135]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 5 but got 0 Feb 15 15:29:34 gnome-shell[3135]: Timelines with detached actors are not supported Feb 15 15:29:34 gnome-shell[3135]: Timelines with detached actors are not supported Feb 15 15:29:34 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell.SearchProvider2” on object at path /org/gnome/s
[Desktop-packages] [Bug 1960768] Re: fwupd crash on stop
saw the new libgusb goes to jammy channel. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgusb in Ubuntu. https://bugs.launchpad.net/bugs/1960768 Title: fwupd crash on stop Status in OEM Priority Project: Fix Released Status in fwupd package in Ubuntu: Invalid Status in libgusb package in Ubuntu: Fix Released Status in libusb package in Ubuntu: Invalid Bug description: I can reproduce crash with a similar stack as below as I stop fwupd service. https://errors.ubuntu.com/problem/4bfcf571c017010afe4775687ff2a9ca7ff79661 also test fwupd 1.7.5 (https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd175) still can reproduce this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1960768/+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 1960898] Re: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[
This bug shouldn't be given High priority. There are no other reports of it, even on errors.ubuntu.com -- 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/1960898 Title: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[0].isObject()) from ubuntu- d...@ubuntu.com/locations.js:1108 Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Hardware: https://linux-hardware.org/?probe=1055dc7082 Worked without Problem in 21.04 Had some flicker and problem with the left dock in 21.10 not working since updating to 22.04 now I'm running xorg. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-450/libnvidia-gl-450_450.102.04-0ubuntu2_amd64.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Tue Feb 15 08:07:04 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-08-15 (183 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 41.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-02-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1960898/+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 1942789] Re: On-demand and RTD3 need to be separated
Test plan had been updated to cover the nvidia-driver-390 case. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942789 Title: On-demand and RTD3 need to be separated Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Incomplete Status in nvidia-prime source package in Hirsute: New Bug description: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Catch BrokenPipeError. - Use bootvga detection when last_gfx_boot is not available. nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942789/+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 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver
** Tags added: hybrid multigpu -- 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/1959888 Title: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver Status in mutter package in Ubuntu: New Bug description: When an external display is connected to my laptop, running Ubuntu 22.04, the display is detected and I am sent to the login screen. After logging in again, the display is not running, although the primary laptop display works fine. The external monitor is looking for connection in that moment, which it never founds. The bug is tested on two Samsung monitors: S24R350FHUXEN and S22F350FHU. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 495.46 Wed Oct 27 16:31:33 UTC 2021 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-14ubuntu1) ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 3 13:25:04 2022 DistUpgraded: 2022-01-13 15:37:13,056 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/495.46, 5.15.0-17-generic, x86_64: installed nvidia/495.46, 5.15.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:086f] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:086f] InstallationDate: Installed on 2021-09-09 (146 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. G3 3579 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-01-13 (20 days ago) dmi.bios.date: 04/20/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0M5H57 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 086F dmi.sys.vendor: Dell Inc. nvidia-settings: ERROR: Unable to find display on any available system ERROR: Unable to find display on any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-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/mutter/+bug/1959888/+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 1960865] Re: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [
Also tracking in https://gitlab.gnome.org/GNOME/mutter/-/issues/1891 ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/1891 Importance: Unknown Status: Unknown -- 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/1960865 Title: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to get memory pages for NvKmsKapiMemory Status in Mutter: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I recently upgraded my NVidia drivers on my ThinkPad P1 Gen 3. If I start Ubuntu on Wayland session and plug in my USB-C monitor the system reliably completely freeze. The freeze is also reproducible if the screen is plugged in during startup and trying to login into a Wayland session. Only Wayland session experiences a crash. The crash happens ONLY if the USB-C monitor is plugged in. USB-C monitor is also a USB3 hub. Hardware seems to work fine, as Windows shows no issues with the setup. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.103.01 Thu Jan 6 12:10:04 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 14 16:39:34 2022 DistUpgraded: 2021-10-14 18:36:11,564 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo CometLake-H GT2 [UHD Graphics] [17aa:22c1] NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:22c1] InstallationDate: Installed on 2020-10-05 (497 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20THCT01WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to impish on 2021-10-14 (122 days ago) dmi.bios.date: 12/27/2021 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: N2VET36W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20THCT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.10 dmi.modalias: dmi:bvnLENOVO:bvrN2VET36W(1.21):bd12/27/2021:br1.21:efr1.10:svnLENOVO:pn20THCT01WW:pvrThinkPadP1Gen3:rvnLENOVO:rn20THCT01WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TH_BU_Think_FM_ThinkPadP1Gen3: dmi.product.family: ThinkPad P1 Gen 3 dmi.product.name: 20THCT01WW dmi.product.sku: LENOVO_MT_20TH_BU_Think_FM_ThinkPad P1 Gen 3 dmi.product.version: ThinkPad P1 Gen 3 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 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-i
[Desktop-packages] [Bug 1960865] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1960865 Title: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to get memory pages for NvKmsKapiMemory Status in Mutter: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I recently upgraded my NVidia drivers on my ThinkPad P1 Gen 3. If I start Ubuntu on Wayland session and plug in my USB-C monitor the system reliably completely freeze. The freeze is also reproducible if the screen is plugged in during startup and trying to login into a Wayland session. Only Wayland session experiences a crash. The crash happens ONLY if the USB-C monitor is plugged in. USB-C monitor is also a USB3 hub. Hardware seems to work fine, as Windows shows no issues with the setup. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.103.01 Thu Jan 6 12:10:04 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 14 16:39:34 2022 DistUpgraded: 2021-10-14 18:36:11,564 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo CometLake-H GT2 [UHD Graphics] [17aa:22c1] NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:22c1] InstallationDate: Installed on 2020-10-05 (497 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20THCT01WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to impish on 2021-10-14 (122 days ago) dmi.bios.date: 12/27/2021 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: N2VET36W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20THCT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.10 dmi.modalias: dmi:bvnLENOVO:bvrN2VET36W(1.21):bd12/27/2021:br1.21:efr1.10:svnLENOVO:pn20THCT01WW:pvrThinkPadP1Gen3:rvnLENOVO:rn20THCT01WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TH_BU_Think_FM_ThinkPadP1Gen3: dmi.product.family: ThinkPad P1 Gen 3 dmi.product.name: 20THCT01WW dmi.product.sku: LENOVO_MT_20TH_BU_Think_FM_ThinkPad P1 Gen 3 dmi.product.version: ThinkPad P1 Gen 3 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 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 b
[Desktop-packages] [Bug 1960972] Re: All snap applications missing from gnome-search after update
** Tags added: impish ** Tags added: regression-update ** Also affects: snapd (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/1960972 Title: All snap applications missing from gnome-search after update Status in snapd: New Status in snapd package in Ubuntu: New Bug description: After this "upgrade", snapd:amd64 2.53+21.10ubuntu1 2.54.2+21.10ubuntu1 (Some video drivers were upgraded at the same time, but this doesn't seem relevant.) ...all snap applications have disappeared from gnome-shell search. All snaps are still installed and can be executed with "snap run app". All applications work correctly when launched this way, except that they will be missing their dock icons showing the "gears"/missing icon indicator. Application icons are also missing in the Ubuntu Software Center. Reinstalling the snap applications affected does not help, including "snap remove --purge && snap install". Non-snap applications are unaffected. To reproduce, press super key and type the name of any installed in /snap. No snap applications appear but normal applications and files will be listed as usual. Tried to uninstall shell extensions removed and reboot. Nothing improved. --- gnome-shell logs complain of the following: Feb 15 15:26:56 gnome-shell[3135]: GNOME Shell started at Tue Feb 15 2022 15:26:53 GMT-0800 (PST) Feb 15 15:26:56 gnome-shell[3135]: Registering session with GDM Feb 15 15:27:03 ubuntu-appindicat...@ubuntu.com[3135]: Slack1, Impossible to lookup icon for 'Slack1_2-panel' in path /run/user/1000/.org.chromium.Chromium.cgr> Feb 15 15:27:03 ubuntu-appindicat...@ubuntu.com[3135]: unable to update icon for Slack1 Feb 15 15:27:09 gnome-shell[3135]: Failed to set the markup of the actor 'ClutterText': Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity — escape ampersand as & Feb 15 15:27:09 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell.SearchProvider2” on object at path /org/gnome/seahorse/Application Feb 15 15:27:09 gnome-shell[3135]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 5 but got 0 Feb 15 15:27:10 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell.SearchProvider2” on object at path /org/gnome/seahorse/Application Feb 15 15:27:10 gnome-shell[3135]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 5 but got 0 Feb 15 15:27:13 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Feb 15 15:27:13 gnome-shell[3135]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 5 but got 0 Feb 15 15:29:06 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell.SearchProvider2” on object at path /org/gnome/seahorse/Application Feb 15 15:29:06 gnome-shell[3135]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 5 but got 0 Feb 15 15:29:33 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell.SearchProvider2” on object at path /org/gnome/seahorse/Application Feb 15 15:29:33 gnome-shell[3135]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 5 but got 0 Feb 15 15:29:34 gnome-shell[3135]: Timelines with detached actors are not supported Feb 15 15:29:34 gnome-shell[3135]: Timelines with detached actors are not supported Feb 15 15:29:34 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell.SearchProvider2” on object at path /org/gnome/seahorse/Application Feb 15 15:29:34 gnome-shell[3135]: Wrong number of result metas retu
[Desktop-packages] [Bug 1960865] Re: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [
** Changed in: mutter (Ubuntu) Status: New => Confirmed ** Changed in: mutter (Ubuntu) Importance: Undecided => High -- 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/1960865 Title: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to get memory pages for NvKmsKapiMemory Status in Mutter: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: I recently upgraded my NVidia drivers on my ThinkPad P1 Gen 3. If I start Ubuntu on Wayland session and plug in my USB-C monitor the system reliably completely freeze. The freeze is also reproducible if the screen is plugged in during startup and trying to login into a Wayland session. Only Wayland session experiences a crash. The crash happens ONLY if the USB-C monitor is plugged in. USB-C monitor is also a USB3 hub. Hardware seems to work fine, as Windows shows no issues with the setup. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.103.01 Thu Jan 6 12:10:04 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 14 16:39:34 2022 DistUpgraded: 2021-10-14 18:36:11,564 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo CometLake-H GT2 [UHD Graphics] [17aa:22c1] NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:22c1] InstallationDate: Installed on 2020-10-05 (497 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20THCT01WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to impish on 2021-10-14 (122 days ago) dmi.bios.date: 12/27/2021 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: N2VET36W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20THCT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.10 dmi.modalias: dmi:bvnLENOVO:bvrN2VET36W(1.21):bd12/27/2021:br1.21:efr1.10:svnLENOVO:pn20THCT01WW:pvrThinkPadP1Gen3:rvnLENOVO:rn20THCT01WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TH_BU_Think_FM_ThinkPadP1Gen3: dmi.product.family: ThinkPad P1 Gen 3 dmi.product.name: 20THCT01WW dmi.product.sku: LENOVO_MT_20TH_BU_Think_FM_ThinkPad P1 Gen 3 dmi.product.version: ThinkPad P1 Gen 3 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 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
[Desktop-packages] [Bug 1960972] Re: All snap applications missing from gnome-search after update
** No longer affects: gnome-shell (Ubuntu) ** Also affects: snapd 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/1960972 Title: All snap applications missing from gnome-search after update Status in snapd: New Status in snapd package in Ubuntu: New Bug description: After this "upgrade", snapd:amd64 2.53+21.10ubuntu1 2.54.2+21.10ubuntu1 (Some video drivers were upgraded at the same time, but this doesn't seem relevant.) ...all snap applications have disappeared from gnome-shell search. All snaps are still installed and can be executed with "snap run app". All applications work correctly when launched this way, except that they will be missing their dock icons showing the "gears"/missing icon indicator. Application icons are also missing in the Ubuntu Software Center. Reinstalling the snap applications affected does not help, including "snap remove --purge && snap install". Non-snap applications are unaffected. To reproduce, press super key and type the name of any installed in /snap. No snap applications appear but normal applications and files will be listed as usual. Tried to uninstall shell extensions removed and reboot. Nothing improved. --- gnome-shell logs complain of the following: Feb 15 15:26:56 gnome-shell[3135]: GNOME Shell started at Tue Feb 15 2022 15:26:53 GMT-0800 (PST) Feb 15 15:26:56 gnome-shell[3135]: Registering session with GDM Feb 15 15:27:03 ubuntu-appindicat...@ubuntu.com[3135]: Slack1, Impossible to lookup icon for 'Slack1_2-panel' in path /run/user/1000/.org.chromium.Chromium.cgr> Feb 15 15:27:03 ubuntu-appindicat...@ubuntu.com[3135]: unable to update icon for Slack1 Feb 15 15:27:09 gnome-shell[3135]: Failed to set the markup of the actor 'ClutterText': Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity — escape ampersand as & Feb 15 15:27:09 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell.SearchProvider2” on object at path /org/gnome/seahorse/Application Feb 15 15:27:09 gnome-shell[3135]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 5 but got 0 Feb 15 15:27:10 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell.SearchProvider2” on object at path /org/gnome/seahorse/Application Feb 15 15:27:10 gnome-shell[3135]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 5 but got 0 Feb 15 15:27:13 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Feb 15 15:27:13 gnome-shell[3135]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 5 but got 0 Feb 15 15:29:06 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell.SearchProvider2” on object at path /org/gnome/seahorse/Application Feb 15 15:29:06 gnome-shell[3135]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 5 but got 0 Feb 15 15:29:33 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell.SearchProvider2” on object at path /org/gnome/seahorse/Application Feb 15 15:29:33 gnome-shell[3135]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 5 but got 0 Feb 15 15:29:34 gnome-shell[3135]: Timelines with detached actors are not supported Feb 15 15:29:34 gnome-shell[3135]: Timelines with detached actors are not supported Feb 15 15:29:34 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell.SearchProvider2” on object at path /org/gnome/seahorse/Application Feb 15 15:29:34 gnome-shell[3135]: Wrong number of result metas returned by search provid
[Desktop-packages] [Bug 1960865] Re: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [
** Also affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: New => Confirmed -- 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/1960865 Title: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to get memory pages for NvKmsKapiMemory Status in Mutter: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: I recently upgraded my NVidia drivers on my ThinkPad P1 Gen 3. If I start Ubuntu on Wayland session and plug in my USB-C monitor the system reliably completely freeze. The freeze is also reproducible if the screen is plugged in during startup and trying to login into a Wayland session. Only Wayland session experiences a crash. The crash happens ONLY if the USB-C monitor is plugged in. USB-C monitor is also a USB3 hub. Hardware seems to work fine, as Windows shows no issues with the setup. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.103.01 Thu Jan 6 12:10:04 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 14 16:39:34 2022 DistUpgraded: 2021-10-14 18:36:11,564 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo CometLake-H GT2 [UHD Graphics] [17aa:22c1] NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:22c1] InstallationDate: Installed on 2020-10-05 (497 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20THCT01WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to impish on 2021-10-14 (122 days ago) dmi.bios.date: 12/27/2021 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: N2VET36W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20THCT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.10 dmi.modalias: dmi:bvnLENOVO:bvrN2VET36W(1.21):bd12/27/2021:br1.21:efr1.10:svnLENOVO:pn20THCT01WW:pvrThinkPadP1Gen3:rvnLENOVO:rn20THCT01WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TH_BU_Think_FM_ThinkPadP1Gen3: dmi.product.family: ThinkPad P1 Gen 3 dmi.product.name: 20THCT01WW dmi.product.sku: LENOVO_MT_20TH_BU_Think_FM_ThinkPad P1 Gen 3 dmi.product.version: ThinkPad P1 Gen 3 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xo
[Desktop-packages] [Bug 1955001] Re: File reading speed is slow
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- 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/1955001 Title: File reading speed is slow Status in nautilus package in Ubuntu: Expired Bug description: I created the user's home directory on the computer's mechanical hard drive, but the user's login speed is very slow, and the speed of viewing the file content in the desktop environment is slow. At the same time, I tested the hard disk read speed: hdparm -Tt /dev/sdb /dev/sdb: Timing cached reads: 23962 MB in 2.00 seconds = 11993.56 MB/sec Timing buffered disk reads: 456 MB in 3.00 seconds = 151.78 MB/sec There is no problem with the read speed of the hard disk. And when I have a lot of data exchange while running a python program, the speed used to be 3s, but now it suddenly becomes 30-50s. The above is when my computer is running well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1955001/+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 1960865] Re: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [
The strange thing to me is that Nvidia shouldn't be involved here. A USB-C port is likely to be wired to the Intel chips only. As a DisplayPort the USB-C is wired to the Intel GPU. And gnome-shell by default will use the integrated Intel GPU only for the desktop. Please reproduce the freeze again, then reboot and run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. -- 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/1960865 Title: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to get memory pages for NvKmsKapiMemory Status in Mutter: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: I recently upgraded my NVidia drivers on my ThinkPad P1 Gen 3. If I start Ubuntu on Wayland session and plug in my USB-C monitor the system reliably completely freeze. The freeze is also reproducible if the screen is plugged in during startup and trying to login into a Wayland session. Only Wayland session experiences a crash. The crash happens ONLY if the USB-C monitor is plugged in. USB-C monitor is also a USB3 hub. Hardware seems to work fine, as Windows shows no issues with the setup. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.103.01 Thu Jan 6 12:10:04 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 14 16:39:34 2022 DistUpgraded: 2021-10-14 18:36:11,564 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo CometLake-H GT2 [UHD Graphics] [17aa:22c1] NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:22c1] InstallationDate: Installed on 2020-10-05 (497 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20THCT01WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to impish on 2021-10-14 (122 days ago) dmi.bios.date: 12/27/2021 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: N2VET36W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20THCT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.10 dmi.modalias: dmi:bvnLENOVO:bvrN2VET36W(1.21):bd12/27/2021:br1.21:efr1.10:svnLENOVO:pn20THCT01WW:pvrThinkPadP1Gen3:rvnLENOVO:rn20THCT01WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TH_BU_Think_FM_ThinkPadP1Gen3: dmi.product.family: ThinkPad P1 Gen 3 dmi.product.name: 20THCT01WW dmi.product.sku: LENOVO_MT_20TH_BU_Think_FM_ThinkPad P1 Gen 3 dmi.product.version: ThinkPad P1 Gen 3 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:
[Desktop-packages] [Bug 1942791] Re: _has_integrated_gpu() needs to consider the desktop case
** Changed in: oem-priority Importance: High => Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942791 Title: _has_integrated_gpu() needs to consider the desktop case Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: New Bug description: In recovery (from a storage) case, the /var/lib/ubuntu-drivers- common/last_gfx_boot is empty. Thus, the _has_integrated_gpu() returns false in I+N laptop case. In this case, there is a iGPU actually. --- During the recovery, a worker executes ubuntu-drivers install. The expected result is "on-demand" but it goes to "on" because /var/lib/ubuntu-drivers-common/last_gfx_boot doesn't exist `ubuntu-drivers install` calls `prime-select on-demand` calls enable_profile() and then enable_profile() calls _has_integrated_gpu() before switching mode. Since _has_integrated_gpu() returns false, it won't switch nvidia mode To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942791/+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 1942791] Re: _has_integrated_gpu() needs to consider the desktop case
the solution is included in the SRU from LP#1957094 and LP#1942789 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942791 Title: _has_integrated_gpu() needs to consider the desktop case Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: New Bug description: In recovery (from a storage) case, the /var/lib/ubuntu-drivers- common/last_gfx_boot is empty. Thus, the _has_integrated_gpu() returns false in I+N laptop case. In this case, there is a iGPU actually. --- During the recovery, a worker executes ubuntu-drivers install. The expected result is "on-demand" but it goes to "on" because /var/lib/ubuntu-drivers-common/last_gfx_boot doesn't exist `ubuntu-drivers install` calls `prime-select on-demand` calls enable_profile() and then enable_profile() calls _has_integrated_gpu() before switching mode. Since _has_integrated_gpu() returns false, it won't switch nvidia mode To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942791/+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 1960865] Re: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [
This sounds like a simple bug in nvidia-drm-470 or kernel 5.13. Both have been upgraded in Ubuntu 22.04 already so there's a chance this issue is already fixed. Still, please follow the instruction in comment #7 because I would like to understand more about the system. ** Changed in: mutter (Ubuntu) Status: Confirmed => Opinion -- 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/1960865 Title: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to get memory pages for NvKmsKapiMemory Status in Mutter: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Opinion Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: I recently upgraded my NVidia drivers on my ThinkPad P1 Gen 3. If I start Ubuntu on Wayland session and plug in my USB-C monitor the system reliably completely freeze. The freeze is also reproducible if the screen is plugged in during startup and trying to login into a Wayland session. Only Wayland session experiences a crash. The crash happens ONLY if the USB-C monitor is plugged in. USB-C monitor is also a USB3 hub. Hardware seems to work fine, as Windows shows no issues with the setup. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.103.01 Thu Jan 6 12:10:04 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 14 16:39:34 2022 DistUpgraded: 2021-10-14 18:36:11,564 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo CometLake-H GT2 [UHD Graphics] [17aa:22c1] NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:22c1] InstallationDate: Installed on 2020-10-05 (497 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20THCT01WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to impish on 2021-10-14 (122 days ago) dmi.bios.date: 12/27/2021 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: N2VET36W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20THCT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.10 dmi.modalias: dmi:bvnLENOVO:bvrN2VET36W(1.21):bd12/27/2021:br1.21:efr1.10:svnLENOVO:pn20THCT01WW:pvrThinkPadP1Gen3:rvnLENOVO:rn20THCT01WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TH_BU_Think_FM_ThinkPadP1Gen3: dmi.product.family: ThinkPad P1 Gen 3 dmi.product.name: 20THCT01WW dmi.product.sku: LENOVO_MT_20TH_BU_Think_FM_ThinkPad P1 Gen 3 dmi.product.version: ThinkPad P1 Gen 3 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xser
[Desktop-packages] [Bug 1952947] Re: ubuntu-bug -w (using xprop) doesn't work under wayland
This bug was fixed in the package apport - 2.20.11-0ubuntu77 --- apport (2.20.11-0ubuntu77) jammy; urgency=medium * apport/ui.py: Error out when -w option is used on wayland (LP: #1952947). -- Nick Rosbrook Tue, 15 Feb 2022 10:10:59 -0500 ** Changed in: apport (Ubuntu Jammy) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11-utils in Ubuntu. https://bugs.launchpad.net/bugs/1952947 Title: ubuntu-bug -w (using xprop) doesn't work under wayland Status in apport package in Ubuntu: Fix Released Status in x11-utils package in Ubuntu: Invalid Status in apport source package in Impish: Triaged Status in x11-utils source package in Impish: Invalid Status in apport source package in Jammy: Fix Released Status in x11-utils source package in Jammy: Invalid Bug description: I want to report a Bug about the application Studio Controls. As I did it already quite a few times, I run "ubuntu-bug -w", get a message that I can select the window of the app I want to report a bug about after closing this message. I close the message with a click on the appropriate button. I click on the window of the application "Studio Controls" that I want to report a bug about. Nothing happens. I wait for a few minutes. Still nothing happens. In the console where I started ubuntu-bug -w I see the following message: (apport-gtk:11537): Gdk-CRITICAL **: 20:06:41.384: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed What I expect: Usaully when I use this procedure, after a relatively short while a new message window pops up asking me if the bug should be reported and showing me the data that is sent to Launchpad. I tried other applications, too, same effect. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: apport 2.20.11-0ubuntu71 ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18 Uname: Linux 5.13.0-21-lowlatency x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Dec 1 20:01:23 2021 InstallationDate: Installed on 2020-04-12 (597 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to impish on 2021-11-14 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1952947/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1715642] Re: displey problem
Really After 4 years???I'm using Ubuntu 20.04 NowLOLThanks anywayNima On Saturday, February 12, 2022, 08:45:43 PM GMT+3:30, Paul White <1715...@bugs.launchpad.net> wrote: We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019. Do you still see a problem related to the one that you reported when using a currently supported version of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. ** Changed in: xorg (Ubuntu) Status: New => Incomplete ** Summary changed: - displey problem + display problem -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1715642 Title: display problem Status in xorg package in Ubuntu: Incomplete Bug description: when I run a program through wine that needs to reduce the resolution to windows xp basic (800 x 600), wine program stopping unexpectedly and my desktop changes resolution so every time I need to restart my ubuntu. for more information pls check the photo I sent. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-93.116~14.04.1-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 381.22 Thu May 4 00:55:03 PDT 2017 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ApportVersion: 2.14.1-0ubuntu3.25 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 7 17:33:30 2017 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 4.4.0-93-generic, x86_64: installed nvidia-381, 381.22, 4.4.0-93-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:108d] NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:108d] InstallationDate: Installed on 2016-12-06 (274 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: Micro-Star International Co., Ltd. GE620/GE620DX/FX620DX ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic root=UUID=f01602a0-6076-4436-9a4b-e05e01b6cdc5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16G5IMS V1.0F dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16G5 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16G5IMSV1.0F:bd05/26/2011:svnMicro-StarInternationalCo.,Ltd.:pnGE620/GE620DX/FX620DX:pvrTobefilledbyO.E.M.:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16G5:rvrTobefilledbyO.E.M.:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrTobefilledbyO.E.M.: dmi.product.name: GE620/GE620DX/FX620DX dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Sep 7 17:29:53 2017 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.3~trusty2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1715642/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribe
[Desktop-packages] [Bug 1961010] Re: firefox doesn't let its user control how or when it upgrades
Added screenshot that happens when this bug is triggered. Firefox
refuses to operate normally after this point, just displaying "Sorry. We
just need to do one small thing to keep going. Firefox has just been
updated in the background. Click Restart Firefox to complete the update.
We will restore all your pages, windows and tabs afterwards, so you can
be on your way quickly." over and over.
** Attachment added: "Screenshot from 2022-02-15 20-06-57.png"
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1961010/+attachment/5561208/+files/Screenshot%20from%202022-02-15%2020-06-57.png
--
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/1961010
Title:
firefox doesn't let its user control how or when it upgrades
Status in firefox package in Ubuntu:
New
Bug description:
The Firefox package does not act like ordinary packages. When it is
running, it forcibly downloads upgraded binary versions of itself and
then forces the user to restart Firefox and run the new version.
There used to be a Firefox setting by which the user could control
this, but it has been deliberately removed.
This is problematic in many ways. The first way is that it undermines
the user's control over their own environment. The essential element
of free software is that users control it, it does not control them.
If there is behavior that is undesirable, they can fix it, not just be
subjected to the arbitrary decisions of a distant corporation. For
example, some users require that they have a copy of the source code
that matches each binary package they are running. Firefox's covert
upgrades undermine this local user policy, installing binaries that
have no local matching source code. Other users may be using plugins
or other applications that do not work with later versions of Firefox.
It is not Firefox's decision when to upgrade -- it is the user's or
system operator's.
The second problem is that restarting one's browser has many side effects.
For example, if one window or tab is in a video conference, forcing a restart
of Firefox ejects the user from their video conference. If a video or audio
file is merely playing in another window or tab, it is
interrupted and not necessarily resumed after restart in the right place.
Cookies and permissions (e.g. for NoScript) are not carried forward after a
restart, when they are set to persist only for one session.
If the Mozilla Corporation has firmly and permanently decided that it
doesn't believe in the freedom of the end-users of its software, then
Ubuntu should ship a patched version that DOES give its end-users
freedom, by restoring the setting to disable automated updates.
Firefox would continue to be able to be updated by the usual update-
manager GUI (which IS under the control of the user), apt-get, or by
the user explicitly installing new versions via dpkg or by building
from source code.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 97.0+build2-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-28-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: gnu2520 F pulseaudio
/dev/snd/controlC1: gnu2520 F pulseaudio
/dev/snd/controlC0: gnu2520 F pulseaudio
BuildID: 20220202182137
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 15 22:55:07 2022
ForcedLayersAccel: False
IncompatibleExtensions:
Global Menu Bar integration - globalm...@ubuntu.com
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2020-05-04 (652 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
IpRoute:
default via 209.16.159.254 dev enp6s0 proto static metric 100
75.101.100.0/24 dev enp6s0 proto kernel scope link src 75.101.100.46 metric
100
169.254.0.0/16 dev enp6s0 scope link metric 1000
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
209.16.159.0/24 dev enp6s0 proto kernel scope link src 209.16.159.252 metric
100
MostRecentCrashID: bp-f3d4806a-b277-49a1-b452-902072161127
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:365
PrefSources: prefs.js
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=97.0/20220202182137 (In use)
RunningIncompatibleAddons: True
SourcePackage: firefox
Submitted
[Desktop-packages] [Bug 1961010] [NEW] firefox doesn't let its user control how or when it upgrades
Public bug reported:
The Firefox package does not act like ordinary packages. When it is
running, it forcibly downloads upgraded binary versions of itself and
then forces the user to restart Firefox and run the new version. There
used to be a Firefox setting by which the user could control this, but
it has been deliberately removed.
This is problematic in many ways. The first way is that it undermines
the user's control over their own environment. The essential element of
free software is that users control it, it does not control them. If
there is behavior that is undesirable, they can fix it, not just be
subjected to the arbitrary decisions of a distant corporation. For
example, some users require that they have a copy of the source code
that matches each binary package they are running. Firefox's covert
upgrades undermine this local user policy, installing binaries that have
no local matching source code. Other users may be using plugins or
other applications that do not work with later versions of Firefox. It
is not Firefox's decision when to upgrade -- it is the user's or system
operator's.
The second problem is that restarting one's browser has many side effects. For
example, if one window or tab is in a video conference, forcing a restart of
Firefox ejects the user from their video conference. If a video or audio file
is merely playing in another window or tab, it is
interrupted and not necessarily resumed after restart in the right place.
Cookies and permissions (e.g. for NoScript) are not carried forward after a
restart, when they are set to persist only for one session.
If the Mozilla Corporation has firmly and permanently decided that it
doesn't believe in the freedom of the end-users of its software, then
Ubuntu should ship a patched version that DOES give its end-users
freedom, by restoring the setting to disable automated updates. Firefox
would continue to be able to be updated by the usual update-manager GUI
(which IS under the control of the user), apt-get, or by the user
explicitly installing new versions via dpkg or by building from source
code.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 97.0+build2-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-28-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: gnu2520 F pulseaudio
/dev/snd/controlC1: gnu2520 F pulseaudio
/dev/snd/controlC0: gnu2520 F pulseaudio
BuildID: 20220202182137
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 15 22:55:07 2022
ForcedLayersAccel: False
IncompatibleExtensions:
Global Menu Bar integration - globalm...@ubuntu.com
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2020-05-04 (652 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
IpRoute:
default via 209.16.159.254 dev enp6s0 proto static metric 100
75.101.100.0/24 dev enp6s0 proto kernel scope link src 75.101.100.46 metric
100
169.254.0.0/16 dev enp6s0 scope link metric 1000
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
209.16.159.0/24 dev enp6s0 proto kernel scope link src 209.16.159.252 metric
100
MostRecentCrashID: bp-f3d4806a-b277-49a1-b452-902072161127
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:365
PrefSources: prefs.js
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=97.0/20220202182137 (In use)
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs:
bp-f3d4806a-b277-49a1-b452-902072161127
bp-4da20c64-dde1-4304-9118-238562160914
bp-16b8bc44-ebd0-46e0-a272-95feb2160908
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/16/2019
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F25
dmi.board.asset.tag: Default string
dmi.board.name: AX370-Gaming 5
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrF25:bd01/16/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: AX370-Gaming 5
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., L
