[Desktop-packages] [Bug 2027844] [NEW] opening sound settings from GNOME top menu yields blank control center
Public bug reported: 1. Click the sound icon in the upper right corner of the screen. 2. Click the arrow next to the sound slider. 3. Select "Sound Settings". 4. Observe how the control panel window that opens up is empty. 5. If you then click on a different control center section and then click on Sound, it shows up properly. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:44.3-1ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 15 00:32:27 2023 InstallationDate: Installed on 2022-09-17 (300 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to mantic on 2023-05-20 (55 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2027844 Title: opening sound settings from GNOME top menu yields blank control center Status in gnome-control-center package in Ubuntu: New Bug description: 1. Click the sound icon in the upper right corner of the screen. 2. Click the arrow next to the sound slider. 3. Select "Sound Settings". 4. Observe how the control panel window that opens up is empty. 5. If you then click on a different control center section and then click on Sound, it shows up properly. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:44.3-1ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 15 00:32:27 2023 InstallationDate: Installed on 2022-09-17 (300 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to mantic on 2023-05-20 (55 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2027844/+subscriptions -- Mailing list: https://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 2019143] Re: xdg-desktop-portal.service
[Expired for xdg-desktop-portal (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xdg-desktop-portal (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/2019143 Title: xdg-desktop-portal.service Status in xdg-desktop-portal package in Ubuntu: Expired Bug description: hallo, since i upgraded to mantic, i cant start xdg-desktop-portal.service` systemctl --user status xdg-desktop-portal.service × xdg-desktop-portal.service - Portal service Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static) Active: failed (Result: timeout) since Wed 2023-05-10 19:00:58 CEST; 56min ago Process: 2251968 ExecStart=/usr/libexec/xdg-desktop-portal (code=killed, signal=TERM) Main PID: 2251968 (code=killed, signal=TERM) CPU: 25ms May 10 18:59:28 cex systemd[2503]: Starting xdg-desktop-portal.service - Portal service... May 10 19:00:18 cex xdg-desktop-por[2251968]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: Failed to create file chooser proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached May 10 19:00:43 cex xdg-desktop-por[2251968]: No skeleton to export May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: start operation timed out. Terminating. May 10 19:00:58 cex systemd[2503]: xdg-desktop-portal.service: Failed with result 'timeout'. May 10 19:00:58 cex systemd[2503]: Failed to start xdg-desktop-portal.service - Portal service. --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2021-01-13 (847 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1003-lowlatency root=UUID=a8161076-a843-4c8b-aba3-640ea33fbc6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-1003.3-lowlatency 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-1003-lowlatency N/A linux-backports-modules-6.2.0-1003-lowlatency N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 Tags: wayland-session mantic Uname: Linux 6.2.0-1003-lowlatency x86_64 UpgradeStatus: Upgraded to mantic on 2023-05-10 (0 days ago) UserGroups: adm audio cdrom davfs2 dip libvirt lpadmin lxd plugdev sambashare sudo video wireshark _MarkForUpload: True dmi.bios.date: 12/08/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A02 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A02:bd12/08/2020:br5.16:efr1.4:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnSchenkerTechnologiesGmbH:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.family: RENOIR dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/2019143/+subscriptions -- Mailing list: https://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 2018982] Re: gnome-shell segfaulted
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2018982 Title: gnome-shell segfaulted Status in gnome-shell package in Ubuntu: Expired Bug description: Gnome crashed, and an inspection of the logs showed that it had a segfault, followed by an OOM event. Release: 23.04 $ apt-cache policy gnome-shell gnome-shell: Installed: 44.0-2ubuntu3 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 9 11:04:50 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-01 (462 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 44.0-2ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-03-06 (64 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2018982/+subscriptions -- Mailing list: https://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 2027843] [NEW] gnome-control-center does not open: symbol lookup error
Public bug reported: Hi, I am running into an error and much googling has led me to close- but-not-quite solutions (including related one linked at bottom). Specifically, I am unable to open Ubuntu Settings either via the GUI or command line. When I run the command line, I get this error: $ gnome-control-center gnome-control-center: symbol lookup error: /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37: undefined symbol: _ZN9Inspector33IndexedDBBackendDispatcherHandler23RequestDatabaseCallback11sendSuccessEON3WTF3RefINS_8Protocol9IndexedDB24DatabaseWithObjectStoresENS2_12RawPtrTraitsIS6_ In other threads, the immediate suggestion is to run the following commands to find improperly linked dependencies: $ ldd $(which gnome-control-center) | grep local $ dpkg -S /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 dpkg-query: no path found matching pattern /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 $ ldd /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 | grep local Which do not produce output for me aside from the dpkg telling me it didn't find anything. I'm stumped! My System: Description:Ubuntu 22.04.2 LTS Release:22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6 Uname: 5.19.0-46-generic #47~22.04.1-Ubuntu Related but different issue: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1970610 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2027843 Title: gnome-control-center does not open: symbol lookup error Status in gnome-control-center package in Ubuntu: New Bug description: Hi, I am running into an error and much googling has led me to close- but-not-quite solutions (including related one linked at bottom). Specifically, I am unable to open Ubuntu Settings either via the GUI or command line. When I run the command line, I get this error: $ gnome-control-center gnome-control-center: symbol lookup error: /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37: undefined symbol: _ZN9Inspector33IndexedDBBackendDispatcherHandler23RequestDatabaseCallback11sendSuccessEON3WTF3RefINS_8Protocol9IndexedDB24DatabaseWithObjectStoresENS2_12RawPtrTraitsIS6_ In other threads, the immediate suggestion is to run the following commands to find improperly linked dependencies: $ ldd $(which gnome-control-center) | grep local $ dpkg -S /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 dpkg-query: no path found matching pattern /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 $ ldd /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 | grep local Which do not produce output for me aside from the dpkg telling me it didn't find anything. I'm stumped! My System: Description: Ubuntu 22.04.2 LTS Release: 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6 Uname: 5.19.0-46-generic #47~22.04.1-Ubuntu Related but different issue: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1970610 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2027843/+subscriptions -- Mailing list: https://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 2026886] Re: [amdgpu] google chrome hardware acceleration broken on 42.9-0ubuntu2
Daniel van Vught wrote: > I'm still struggling to understand how gnome-shell is triggering the > corruption. Maybe try switching between 42.5 and 42.9 a few times again and > verify in both cases the mutter packages remain 42.9. I tried everything again from the beginning, and I _can_ reproduce this with mutter 42.9 and gnome-shell 42.0. So I think you're right - this is probably a mutter bug. When I was testing initially, I relied on the built in chrome 'relaunch' button, which does not give a full clean restart. I have to fully restart the application for the bug to manifest (after re-enabling hardware acceleration). I tried to downgrade mutter to confirm that this package was the problem, but I can't go all the way back to v42.0 without apt trying to remove a whole bunch of critical packages. Unfortunately, I couldn't find v42.5 in my local cache or the repositories, either, to test with. Maybe you have a better suggestion that I could do to try and isolate the offending package? > Also can you find any other app affected? I haven't been able to reproduce this with any other applications, though I don't really use anything that stresses the GPU (likes games and such). I could look this weekend for something to try -- 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/2026886 Title: [amdgpu] google chrome hardware acceleration broken on 42.9-0ubuntu2 Status in gnome-shell package in Ubuntu: Incomplete Bug description: This morning, I upgraded gnome-shell and gnome-shell-common from 42.5-0ubuntu1 to 42.9-0ubuntu2, and I noticed that chrome no longer renders properly. Notice the missing image header on the Ubuntu website and the garbled right click menu here: https://i.imgur.com/BPnqfVG.png I downgraded gnome-shell and gnome-shell-common version to 42.0-2ubuntu1, restarted gnome, and the rendering issues went away: https://i.imgur.com/CzEPgqY.png I upgraded gnome-shell and gnome-shell-common again to the latest and the rendering issues came back. Going to chrome://settings/system and disabling hardware acceleration fixes the rendering issues (but now I don't have hardware acceleration). I'm running the latest stable version of chrome which was released a few weeks ago: 114.0.5735.198 --- $ lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 $ apt-cache policy gnome-shell gnome-shell: Installed: 42.9-0ubuntu2 Candidate: 42.9-0ubuntu2 Version table: *** 42.9-0ubuntu2 500 (phased 40%) 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026886/+subscriptions -- Mailing list: https://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 2018175] Re: [Zenbook UP6502ZD_Q539ZD, Realtek ALC294, Speaker, Internal] No sound at all
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2018175 Title: [Zenbook UP6502ZD_Q539ZD, Realtek ALC294, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: headphone jack works speakers don't work Tried some fixes I found in the ubuntu forums to no avail ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Apr 29 22:40:09 2023 InstallationDate: Installed on 2023-04-21 (8 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_AlsaPlaybackTestStderr: F a i l u r e t o s u s p e n d : N o s u c h e n t i t y Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Zenbook UP6502ZD_Q539ZD, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/30/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UP6502ZD.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UP6502ZD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUP6502ZD.305:bd06/30/2022:br5.25:svnASUSTeKCOMPUTERINC.:pnZenbookUP6502ZD_Q539ZD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUP6502ZD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: Zenbook Flip dmi.product.name: Zenbook UP6502ZD_Q539ZD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2023-04-29T21:55:59.760443 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2018175/+subscriptions -- Mailing list: https://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 2027828] Re: firefox: No Firefox entry in the Ubuntu MATE menu
** Description changed: In Ubuntu MATE 22.04 (upgraded): - * Menu -> Internet -> Firefox (snap) -- exists (less relevant: it's not added via /usr/share/applications/) + * Menu -> Internet -> Firefox (snap) -- exists (less relevant: it's not added via /usr/share/applications/firefox.desktop) * Run these steps: sudo add-apt-repository ppa:mozillateam/ppa echo ' Package: * Pin: release o=LP-PPA-mozillateam Pin-Priority: 1001 Package: firefox Pin: version 1:1snap1-0ubuntu2 Pin-Priority: -1 ' | sudo tee /etc/apt/preferences.d/mozilla-firefox sudo snap remove firefox * Menu -> Internet -- has been removed * Run: sudo apt install firefox - * Menu -> Internet -> Firefox -- is not added (and Menu -> Internet -- is still removed). But /usr/share/applications/Firefox has been created + * Menu -> Internet -> Firefox -- is not added (and Menu -> Internet -- is still removed). But /usr/share/applications/firefox.desktop has been created * Run: sudo apt install thunderbird - * Menu -> Internet -> Thunderbird Mail -- is added. /usr/share/applications/Thunderbird Mail has been created + * Menu -> Internet -> Thunderbird Mail -- is added. /usr/share/applications/thunderbird.desktop has been created Temporary solution: * cp /usr/share/applications/firefox.desktop ~/.local/share/applications/ ** Description changed: In Ubuntu MATE 22.04 (upgraded): - * Menu -> Internet -> Firefox (snap) -- exists (less relevant: it's not added via /usr/share/applications/firefox.desktop) + * "Menu -> Internet -> Firefox" (snap) exists (less relevant: it's not added via /usr/share/applications/firefox.desktop) * Run these steps: sudo add-apt-repository ppa:mozillateam/ppa echo ' Package: * Pin: release o=LP-PPA-mozillateam Pin-Priority: 1001 Package: firefox Pin: version 1:1snap1-0ubuntu2 Pin-Priority: -1 ' | sudo tee /etc/apt/preferences.d/mozilla-firefox sudo snap remove firefox * Menu -> Internet -- has been removed * Run: sudo apt install firefox - * Menu -> Internet -> Firefox -- is not added (and Menu -> Internet -- is still removed). But /usr/share/applications/firefox.desktop has been created + * "Menu -> Internet -> Firefox" is not added (so "Menu -> Internet" -- is still removed). But /usr/share/applications/firefox.desktop has been created * Run: sudo apt install thunderbird - * Menu -> Internet -> Thunderbird Mail -- is added. /usr/share/applications/thunderbird.desktop has been created + * "Menu -> Internet -> Thunderbird Mail" is added. /usr/share/applications/thunderbird.desktop has been created Temporary solution: * cp /usr/share/applications/firefox.desktop ~/.local/share/applications/ -- 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/2027828 Title: firefox: No Firefox entry in the Ubuntu MATE menu Status in firefox package in Ubuntu: New Bug description: In Ubuntu MATE 22.04 (upgraded): * "Menu -> Internet -> Firefox" (snap) exists (less relevant: it's not added via /usr/share/applications/firefox.desktop) * Run these steps: sudo add-apt-repository ppa:mozillateam/ppa echo ' Package: * Pin: release o=LP-PPA-mozillateam Pin-Priority: 1001 Package: firefox Pin: version 1:1snap1-0ubuntu2 Pin-Priority: -1 ' | sudo tee /etc/apt/preferences.d/mozilla-firefox sudo snap remove firefox * Menu -> Internet -- has been removed * Run: sudo apt install firefox * "Menu -> Internet -> Firefox" is not added (so "Menu -> Internet" -- is still removed). But /usr/share/applications/firefox.desktop has been created * Run: sudo apt install thunderbird * "Menu -> Internet -> Thunderbird Mail" is added. /usr/share/applications/thunderbird.desktop has been created Temporary solution: * cp /usr/share/applications/firefox.desktop ~/.local/share/applications/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2027828/+subscriptions -- Mailing list: https://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 2027828] Re: firefox: No Firefox entry in the Ubuntu MATE menu
** Description changed: In Ubuntu MATE 22.04 (upgraded): * Menu -> Internet -> Firefox (snap) -- exists (less relevant: it's not added via /usr/share/applications/) * Run these steps: sudo add-apt-repository ppa:mozillateam/ppa echo ' Package: * Pin: release o=LP-PPA-mozillateam Pin-Priority: 1001 Package: firefox Pin: version 1:1snap1-0ubuntu2 Pin-Priority: -1 ' | sudo tee /etc/apt/preferences.d/mozilla-firefox sudo snap remove firefox * Menu -> Internet -- has been removed * Run: sudo apt install firefox - * Menu -> Internet -> Firefox -- is not added, and /usr/share/applications/Firefox has not been created. Menu -> Internet -- is still removed. + * Menu -> Internet -> Firefox -- is not added (and Menu -> Internet -- is still removed). But /usr/share/applications/Firefox has been created * Run: sudo apt install thunderbird - * Menu -> Internet -> Thunderbird Mail -- is added. It is located in /usr/share/applications/Thunderbird Mail + * Menu -> Internet -> Thunderbird Mail -- is added. /usr/share/applications/Thunderbird Mail has been created ** Description changed: In Ubuntu MATE 22.04 (upgraded): * Menu -> Internet -> Firefox (snap) -- exists (less relevant: it's not added via /usr/share/applications/) * Run these steps: sudo add-apt-repository ppa:mozillateam/ppa echo ' Package: * Pin: release o=LP-PPA-mozillateam Pin-Priority: 1001 Package: firefox Pin: version 1:1snap1-0ubuntu2 Pin-Priority: -1 ' | sudo tee /etc/apt/preferences.d/mozilla-firefox sudo snap remove firefox * Menu -> Internet -- has been removed * Run: sudo apt install firefox * Menu -> Internet -> Firefox -- is not added (and Menu -> Internet -- is still removed). But /usr/share/applications/Firefox has been created * Run: sudo apt install thunderbird * Menu -> Internet -> Thunderbird Mail -- is added. /usr/share/applications/Thunderbird Mail has been created + + Temporary solution: + * cp /usr/share/applications/firefox.desktop /home/blues/.local/share/applications/ ** Description changed: In Ubuntu MATE 22.04 (upgraded): * Menu -> Internet -> Firefox (snap) -- exists (less relevant: it's not added via /usr/share/applications/) * Run these steps: sudo add-apt-repository ppa:mozillateam/ppa echo ' Package: * Pin: release o=LP-PPA-mozillateam Pin-Priority: 1001 Package: firefox Pin: version 1:1snap1-0ubuntu2 Pin-Priority: -1 ' | sudo tee /etc/apt/preferences.d/mozilla-firefox sudo snap remove firefox * Menu -> Internet -- has been removed * Run: sudo apt install firefox * Menu -> Internet -> Firefox -- is not added (and Menu -> Internet -- is still removed). But /usr/share/applications/Firefox has been created * Run: sudo apt install thunderbird * Menu -> Internet -> Thunderbird Mail -- is added. /usr/share/applications/Thunderbird Mail has been created Temporary solution: - * cp /usr/share/applications/firefox.desktop /home/blues/.local/share/applications/ + * cp /usr/share/applications/firefox.desktop ~/.local/share/applications/ -- 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/2027828 Title: firefox: No Firefox entry in the Ubuntu MATE menu Status in firefox package in Ubuntu: New Bug description: In Ubuntu MATE 22.04 (upgraded): * Menu -> Internet -> Firefox (snap) -- exists (less relevant: it's not added via /usr/share/applications/) * Run these steps: sudo add-apt-repository ppa:mozillateam/ppa echo ' Package: * Pin: release o=LP-PPA-mozillateam Pin-Priority: 1001 Package: firefox Pin: version 1:1snap1-0ubuntu2 Pin-Priority: -1 ' | sudo tee /etc/apt/preferences.d/mozilla-firefox sudo snap remove firefox * Menu -> Internet -- has been removed * Run: sudo apt install firefox * Menu -> Internet -> Firefox -- is not added (and Menu -> Internet -- is still removed). But /usr/share/applications/Firefox has been created * Run: sudo apt install thunderbird * Menu -> Internet -> Thunderbird Mail -- is added. /usr/share/applications/Thunderbird Mail has been created Temporary solution: * cp /usr/share/applications/firefox.desktop ~/.local/share/applications/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2027828/+subscriptions -- Mailing list: https://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 2026228] Re: gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution
Hello Dirk, or anyone else affected, Accepted gnome-control-center into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-control- center/1:44.0-1ubuntu6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-control-center (Ubuntu Lunar) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-lunar ** Changed in: gnome-control-center (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2026228 Title: gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution Status in OEM Priority Project: Confirmed Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Jammy: Fix Committed Status in gnome-control-center source package in Kinetic: Won't Fix Status in gnome-control-center source package in Lunar: Fix Committed Bug description: [Impact] gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution [Test case] Mirror mode is only an option if there are only 2 monitors connected even if one monitor is disabled. A laptop's internal screen counts as one of the monitors. This particular bug requires two screens that have a screen resolution that they don't both share. (See comment 12 for an example). 1. Connect the monitors 2. Open the GNOME Settings app (gnome-control-center) 3. On the left sidebar, click Displays to switch to the Display panel 4. Switch to mirror mode 3. gnome-control-center won't crash [Where problems could occur] This only modifies the code related to mirror mode in Displays panel. For Lunar, check variable (best_mode) before using it. This patch is backported from GNOME 45 Alpha. For Jammy, include the Lunar patch and update the way to find cloning mode. These 2 additional patches are backported from gnome-control- center 43. [Other info] Two Merge Request are related 1. Check best_mode exist before adding flag (https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1835) 2. Use virtual clone modes when mirroring (https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1376) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2026228/+subscriptions -- Mailing list: https://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 2026228] Please test proposed package
Hello Dirk, or anyone else affected, Accepted gnome-control-center into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-control- center/1:41.7-0ubuntu0.22.04.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2026228 Title: gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution Status in OEM Priority Project: Confirmed Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Jammy: Fix Committed Status in gnome-control-center source package in Kinetic: Won't Fix Status in gnome-control-center source package in Lunar: Fix Committed Bug description: [Impact] gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution [Test case] Mirror mode is only an option if there are only 2 monitors connected even if one monitor is disabled. A laptop's internal screen counts as one of the monitors. This particular bug requires two screens that have a screen resolution that they don't both share. (See comment 12 for an example). 1. Connect the monitors 2. Open the GNOME Settings app (gnome-control-center) 3. On the left sidebar, click Displays to switch to the Display panel 4. Switch to mirror mode 3. gnome-control-center won't crash [Where problems could occur] This only modifies the code related to mirror mode in Displays panel. For Lunar, check variable (best_mode) before using it. This patch is backported from GNOME 45 Alpha. For Jammy, include the Lunar patch and update the way to find cloning mode. These 2 additional patches are backported from gnome-control- center 43. [Other info] Two Merge Request are related 1. Check best_mode exist before adding flag (https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1835) 2. Use virtual clone modes when mirroring (https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1376) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2026228/+subscriptions -- Mailing list: https://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 2027828] Re: firefox: No Firefox entry in the Ubuntu MATE menu
** Summary changed: - Ubuntu MATE: Firefox not added to the menu + firefox: No Firefox entry in the Ubuntu MATE menu -- 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/2027828 Title: firefox: No Firefox entry in the Ubuntu MATE menu Status in firefox package in Ubuntu: New Bug description: In Ubuntu MATE 22.04 (upgraded): * Menu -> Internet -> Firefox (snap) -- exists (less relevant: it's not added via /usr/share/applications/) * Run these steps: sudo add-apt-repository ppa:mozillateam/ppa echo ' Package: * Pin: release o=LP-PPA-mozillateam Pin-Priority: 1001 Package: firefox Pin: version 1:1snap1-0ubuntu2 Pin-Priority: -1 ' | sudo tee /etc/apt/preferences.d/mozilla-firefox sudo snap remove firefox * Menu -> Internet -- has been removed * Run: sudo apt install firefox * Menu -> Internet -> Firefox -- is not added, and /usr/share/applications/Firefox has not been created. Menu -> Internet -- is still removed. * Run: sudo apt install thunderbird * Menu -> Internet -> Thunderbird Mail -- is added. It is located in /usr/share/applications/Thunderbird Mail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2027828/+subscriptions -- Mailing list: https://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 2027828] Re: Ubuntu MATE: Firefox not added to the menu
** Package changed: ubuntu => firefox (Ubuntu) ** Tags added: jammy -- 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/2027828 Title: Ubuntu MATE: Firefox not added to the menu Status in firefox package in Ubuntu: New Bug description: In Ubuntu MATE 22.04 (upgraded): * Menu -> Internet -> Firefox (snap) -- exists (less relevant: it's not added via /usr/share/applications/) * Run these steps: sudo add-apt-repository ppa:mozillateam/ppa echo ' Package: * Pin: release o=LP-PPA-mozillateam Pin-Priority: 1001 Package: firefox Pin: version 1:1snap1-0ubuntu2 Pin-Priority: -1 ' | sudo tee /etc/apt/preferences.d/mozilla-firefox sudo snap remove firefox * Menu -> Internet -- has been removed * Run: sudo apt install firefox * Menu -> Internet -> Firefox -- is not added, and /usr/share/applications/Firefox has not been created. Menu -> Internet -- is still removed. * Run: sudo apt install thunderbird * Menu -> Internet -> Thunderbird Mail -- is added. It is located in /usr/share/applications/Thunderbird Mail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2027828/+subscriptions -- Mailing list: https://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 2027571] Re: gnome-extensions-app crash, parser_get_compose_table: assertion failed:
here is the list of gtk4 package installed on my machine, maybe there is something wrong with them ? $ apt list | grep -i "gtk4\|gtk-4" awf-gtk4/jammy 2.5.0-5 amd64 fcitx5-frontend-gtk4/jammy 5.0.12-1 amd64 gir1.2-gtk-4.0/jammy-updates,now 4.6.6+ds-0ubuntu1 amd64 [installed,automatic] gir1.2-gtk-4.0/jammy-updates 4.6.6+ds-0ubuntu1 i386 gir1.2-javascriptcoregtk-4.0/jammy-updates,jammy-security,now 2.38.6-0ubuntu0.22.04.1 amd64 [installed,automatic] gir1.2-javascriptcoregtk-4.0/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 i386 gir1.2-javascriptcoregtk-4.1/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 amd64 gir1.2-javascriptcoregtk-4.1/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 i386 gir1.2-xdpgtk4-1.0/jammy 0.6-2 amd64 gtk-4-examples/jammy-updates,now 4.6.6+ds-0ubuntu1 amd64 [installed] gtk-4-examples/jammy-updates 4.6.6+ds-0ubuntu1 i386 gtk-4-tests/jammy-updates 4.6.6+ds-0ubuntu1 amd64 gtk-4-tests/jammy-updates 4.6.6+ds-0ubuntu1 i386 ibus-gtk4/jammy 1.5.26-4 amd64 ibus-gtk4/jammy 1.5.26-4 i386 libdbusmenu-gtk4/jammy 16.04.1+18.10.20180917-0ubuntu8 amd64 libfm-gtk4/jammy 1.3.2-1 amd64 libgtk-4-1/jammy-updates,now 4.6.6+ds-0ubuntu1 amd64 [installed,automatic] libgtk-4-1/jammy-updates 4.6.6+ds-0ubuntu1 i386 libgtk-4-bin/jammy-updates 4.6.6+ds-0ubuntu1 amd64 libgtk-4-bin/jammy-updates 4.6.6+ds-0ubuntu1 i386 libgtk-4-common/jammy-updates,jammy-updates,now 4.6.6+ds-0ubuntu1 all [installed,automatic] libgtk-4-dev/jammy-updates,now 4.6.6+ds-0ubuntu1 amd64 [installed] libgtk-4-dev/jammy-updates 4.6.6+ds-0ubuntu1 i386 libgtk-4-doc/jammy-updates,jammy-updates 4.6.6+ds-0ubuntu1 all libgtk-4-media-gstreamer/jammy-updates 4.6.6+ds-0ubuntu1 amd64 libgtk-4-media-gstreamer/jammy-updates 4.6.6+ds-0ubuntu1 i386 libjavascriptcoregtk-4.0-18/jammy-updates,jammy-security,now 2.38.6-0ubuntu0.22.04.1 amd64 [installed,automatic] libjavascriptcoregtk-4.0-18/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 i386 libjavascriptcoregtk-4.0-bin/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 amd64 libjavascriptcoregtk-4.0-bin/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 i386 libjavascriptcoregtk-4.0-dev/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 amd64 libjavascriptcoregtk-4.0-dev/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 i386 libjavascriptcoregtk-4.1-0/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 amd64 libjavascriptcoregtk-4.1-0/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 i386 libjavascriptcoregtk-4.1-dev/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 amd64 libjavascriptcoregtk-4.1-dev/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 i386 libportal-gtk4-1/jammy 0.6-2 amd64 libportal-gtk4-dev/jammy 0.6-2 amd64 libportal-tests-gtk4/jammy,jammy 0.6-2 all librust-gtk4-macros-dev/jammy 0.3.1-1 amd64 librust-gtk4-sys-dev/jammy 0.3.1-1 amd64 libswt-cairo-gtk-4-jni/jammy 4.20.0-2 amd64 libswt-glx-gtk-4-jni/jammy 4.20.0-2 amd64 libswt-gtk-4-java/jammy 4.20.0-2 amd64 libswt-gtk-4-jni/jammy 4.20.0-2 amd64 libswt-webkit-gtk-4-jni/jammy 4.20.0-2 amd64 libwebkit2gtk-4.0-37/jammy-updates,jammy-security,now 2.38.6-0ubuntu0.22.04.1 amd64 [installed,automatic] libwebkit2gtk-4.0-37/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 i386 libwebkit2gtk-4.0-dev/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 amd64 libwebkit2gtk-4.0-dev/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 i386 libwebkit2gtk-4.0-doc/jammy-updates,jammy-updates,jammy-security,jammy-security 2.38.6-0ubuntu0.22.04.1 all libwebkit2gtk-4.1-0/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 amd64 libwebkit2gtk-4.1-0/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 i386 libwebkit2gtk-4.1-dev/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 amd64 libwebkit2gtk-4.1-dev/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 i386 python3-wxgtk4.0/jammy 4.0.7+dfsg-13build1 amd64 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2027571 Title: gnome-extensions-app crash, parser_get_compose_table: assertion failed: Status in GNOME Shell: New Status in GTK+: Fix Released Status in gtk4 package in Ubuntu: New Bug description: ENV: Ubuntu 22.04.2 LTS on X11, GNOME Shell 42.9 symptom : gnome-extensions-app crash everytime right at start. message: ``` /usr/bin/gnome-extensions-app ** Gtk:ERROR:../../../gtk/gtkcomposetable.c:981:parser_get_compose_table: assertion failed: (data[first_pos + i] <= data[first_pos + i + 1]) Bail out! Gtk:ERROR:../. ``` gdb backtrace: ``` ** Gtk:ERROR:../../../gtk/gtkcomposetable.c:981:parser_get_compose_table: assertion failed: (data[first_pos + i] <= data[first_pos + i + 1]) Bail out! Gtk:ERROR:../../../gtk/gtkcomposetable.c:981:parser_get_compose_table: assertion failed: (data[first_pos + i] <= data[first_pos + i + 1]) Thread 16 "pool-gnome-exte" received signal SIGABRT, Aborted.
[Desktop-packages] [Bug 2027571] Re: gnome-extensions-app crash, parser_get_compose_table: assertion failed:
it seems to be an issue with gtk 4. $ sudo apt install gtk-4-examples $ gtk4-demo-application the demo app gives me the same error -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2027571 Title: gnome-extensions-app crash, parser_get_compose_table: assertion failed: Status in GNOME Shell: New Status in GTK+: Fix Released Status in gtk4 package in Ubuntu: New Bug description: ENV: Ubuntu 22.04.2 LTS on X11, GNOME Shell 42.9 symptom : gnome-extensions-app crash everytime right at start. message: ``` /usr/bin/gnome-extensions-app ** Gtk:ERROR:../../../gtk/gtkcomposetable.c:981:parser_get_compose_table: assertion failed: (data[first_pos + i] <= data[first_pos + i + 1]) Bail out! Gtk:ERROR:../. ``` gdb backtrace: ``` ** Gtk:ERROR:../../../gtk/gtkcomposetable.c:981:parser_get_compose_table: assertion failed: (data[first_pos + i] <= data[first_pos + i + 1]) Bail out! Gtk:ERROR:../../../gtk/gtkcomposetable.c:981:parser_get_compose_table: assertion failed: (data[first_pos + i] <= data[first_pos + i + 1]) Thread 16 "pool-gnome-exte" received signal SIGABRT, Aborted. [Switching to Thread 0x70858640 (LWP 9456)] __pthread_kill_implementation (no_tid=0, signo=6, threadid=140737228670528) at ./nptl/pthread_kill.c:44 44./nptl/pthread_kill.c: No such file or directory. (gdb) bt #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140737228670528) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=140737228670528) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=140737228670528, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x776bb476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x776a17f3 in __GI_abort () at ./stdlib/abort.c:79 #5 0x77d44b57 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x77d9e70f in g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x711be0e3 in () at /lib/x86_64-linux-gnu/libgtk-4.so.1 #8 0x7123a0b4 in () at /lib/x86_64-linux-gnu/libgtk-4.so.1 #9 0x7123a7b1 in () at /lib/x86_64-linux-gnu/libgtk-4.so.1 #10 0x77b9f194 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #11 0x77dad6b4 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x77daaa51 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7770db43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #14 0x7779fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 ``` Moreover, I found in my snap logs that there was update recently applied, might be linked ``` $snap changes ID Status SpawnReadySummary 253 Doneyesterday at 21:47 CEST yesterday at 21:47 CEST Remove "gnome-3-34-1804" snap 254 Doneyesterday at 22:23 CEST yesterday at 22:23 CEST Refresh "gnome-3-38-2004" snap ``` Moreover, is seems I have multiple snap version of gnome installed ``` snap list ... gnome-3-28-18043.28.0-19-g98f9e67.98f9e67 198latest/stable canonical✓ - gnome-3-38-20040+git.efb213a 143latest/stable canonical✓ - gnome-42-2204 0+git.ff35a85 120latest/stable canonical✓ - ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome (not installed) ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99 Uname: Linux 5.15.0-76-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jul 12 12:10:10 2023 InstallationDate: Installed on 2021-08-18 (692 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: meta-gnome3 UpgradeStatus: Upgraded to jammy on 2023-07-01 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2027571/+subscriptions -- Mailing list: https://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 2026887] Re: gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers
Hi Andreas, Will try to check new packages in next days. Thanks for all. -- 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/2026887 Title: gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: Fix Released Status in linux-intel-iotg package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Kinetic: Invalid Status in mutter source package in Lunar: Invalid Status in mutter source package in Mantic: Invalid Bug description: [ Impact ] gnome-shell/mutter 42.9 fails to start (black screen) on Intel Alder Lake systems running older kernels such as 5.15. [ Test Plan ] Try to log into gnome-shell. Verify there is a picture on the screen. [ Where problems could occur ] The offending code change relates to Intel-specific chip IDs so the change is limited to Intel systems. Although affected Intel systems worked perfectly before the change so we don't expect any problems in reverting the change. In theory the worst case is limited to more problems like that described in Impact above. [ Workarounds ] Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment or upgrade to a newer kernel: sudo apt install linux-generic-hwe-22.04 [ Other Info ] The log messages relating to this bug are: iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument ... For kinetic: The bug never existed in mutter 43.0 (it was introduced in 43.2) and was already fixed in the kernel anyway. For lunar and later: The bug was already fixed in the kernel. You would only ever encounter it in theory if you downgrade the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026887/+subscriptions -- Mailing list: https://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 2026887] Re: gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers
Hi Daniel, I reinstalled today my ADL-P PC with Ubuntu Desktop 22.04.02. And this is not reproduced with -generic kernel. I have this: 5.19.0-46-generic #47~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jun 21 15:35:31 UTC 2 x86_64 x86_64 x86_64 GNU/Linux And no error with this. LIBMUTTER VERSION: dpkg -l | grep libmutter ii libmutter-10-0:amd64 42.9-0ubuntu1 amd64window manager library from the Mutter window manage GNOME SHELL VERSION: dpkg -l | grep gnome-shell ii gnome-shell42.9-0ubuntu2 amd64graphical shell for the GNOME desktop KERNEL VERSION: dpkg -l | grep linux-image ii linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 amd64Signed kernel image generic ii linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1 amd64Signed kernel image generic ii linux-image-generic-hwe-22.04 5.19.0.46.47~22.04.21 amd64Generic Linux kernel image -- 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/2026887 Title: gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: Fix Released Status in linux-intel-iotg package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Kinetic: Invalid Status in mutter source package in Lunar: Invalid Status in mutter source package in Mantic: Invalid Bug description: [ Impact ] gnome-shell/mutter 42.9 fails to start (black screen) on Intel Alder Lake systems running older kernels such as 5.15. [ Test Plan ] Try to log into gnome-shell. Verify there is a picture on the screen. [ Where problems could occur ] The offending code change relates to Intel-specific chip IDs so the change is limited to Intel systems. Although affected Intel systems worked perfectly before the change so we don't expect any problems in reverting the change. In theory the worst case is limited to more problems like that described in Impact above. [ Workarounds ] Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment or upgrade to a newer kernel: sudo apt install linux-generic-hwe-22.04 [ Other Info ] The log messages relating to this bug are: iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument ... For kinetic: The bug never existed in mutter 43.0 (it was introduced in 43.2) and was already fixed in the kernel anyway. For lunar and later: The bug was already fixed in the kernel. You would only ever encounter it in theory if you downgrade the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026887/+subscriptions -- Mailing list: https://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 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
Hello Fabio, or anyone else affected, Accepted mutter into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done-jammy ** Tags added: verification-needed-jammy -- 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/2020782 Title: Xdcv: Changing display scale setting and reverting it fails Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Kinetic: Fix Released Status in mutter source package in Lunar: Fix Released Status in mutter source package in Mantic: Fix Released Bug description: [ Impact ] When running GNOME on the Xdcv X11 server, changing the display scale in Settings and then clicking 'Revert Settings' instead of 'Keep Changes' does not revert the settings. [ Test Plan ] Very complicated; see comment #8. [ Where problems could occur ] In the list of available graphics modes in Xorg sessions on jammy only (an equivalent fix already exists in later Ubuntu releases). [ Original Description ] * Anything else you think is useful to include * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board * and address these questions in advance In Amazon Workspaces running Ubuntu 22.04, when attempting to change the Scale in the Gnome Display settings, if you click on a different scale (i.e. changing from 100% to 200%) and hitting apply, it will bring up a prompt asking if you want to keep or revert the changes and there will be a timer of 20 seconds. If you try to revert the changes (either by letting the timer expire or by clicking the "revert" button), we will hit one of the following two behaviors: 1 - The setting won't revert and will keep scaled 2 - gnome-shell will show some error messages in syslog and the display will be "corrupted", where the only window you are able to click is the display setting and if you try to drag it, it will leave a "blur" throughout the window (per discussions, this seems to be https://launchpad.net/bugs/1924689) For both situations, changing the display resolution (i.e. going into and out of full screen in the workspaces client) will fix the issue When hitting situation 1, syslog shows: May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x1080 (19.958942) for monitor 'unknown unknown' When hitting situation 2, syslog shows: May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label (0x557090d07de0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 0x557090bee180 == May 17
[Desktop-packages] [Bug 2020834] Re: Properly convert DNS names with '-' characters to valid dbus object paths
Agreed, I think it's reasonable to track down why this seemed to break Kinetic entirely before releasing to the other stable series. I can see from the logs that adsys seems to be failing due to an internal LDAP error (NT_STATUS_INVALID_PARAMETER), so it might be worth looking into that a bit deeper. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2020834 Title: Properly convert DNS names with '-' characters to valid dbus object paths Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Status in adsys source package in Jammy: Fix Committed Status in adsys source package in Kinetic: Fix Committed Bug description: [Impact] It is common that domain names contain the '-' character, as in "test- example.com", and adsys versions 0.9.2 and below cannot parse these correctly, leading to the error: ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name when attempting to run adsys on a system attached to "test- example.com" Active Directory. Currently, 0.9.2 only changes '.' into '_2e', and this would change all special characters to use their hexadecimal representations, notably '-' becomes '_2d'. There is plans from Foundations + Desktop to SRU 0.12.0 back to at least Jammy, documented in bug 2020682 which depends on golang 1.20 to be included in the jammy archive, documented in bug 2020658. However, this fixup is required with high priority while the 0.12.0 release is being prepared, and the SRU will hopefully bridge a few weeks between SRU release to release of 0.12.0. [Testcase] Start a Windows Server VM, 2022 will be fine, and create an Active Directory with the domain "test-example.com". Launch a Focal, or Jammy, or Kinetic VM, and use SSSD to join the domain. Try to enable adsys: $ sudo apt install adsys $ adsysctl update ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name There are test packages in the below ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf360012-test If you install the test package and retry to join the domain, it will succeed. [Where problems could occur] We are changing how domain names are being parsed and converted to valid dbus object path names. Domain names can only contain [0-9], [A-Z], [a-z], [.], and [-], so by adding '-' to being processed to its hexadecimal representation of '_2d', there should be limited scope of regressions. However, if a regression were to occur, then users may not be able to use adsys to apply group policy restrictions, and could run into issues accessing files, shares and networks. As mentioned in the impact section, this will be a temporary fix to 0.9.2 while 0.12.0 is being prepared to be released into the archive, which contains the full fix and testsuite coverage. This SRU should hopefully be short lived. [Other Info] The upstream merge request is: https://github.com/ubuntu/adsys/pull/498 This was fixed in 0.10.0 by the commit: commit 5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Author: Didier Roche Date: Tue Nov 15 11:10:51 2022 +0100 Subject: Fix special characters in domain conversion to dbus object path Link: https://github.com/ubuntu/adsys/commit/5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Now, there were some additional commits that added testsuite coverage: commit cd79b3f81441a3d9ab50f11bc8c3b5c7bf722540 Author: Didier Roche Date: Tue Nov 15 11:13:03 2022 +0100 Subject: Refresh golden file now that we properly handle the path. Link: https://github.com/ubuntu/adsys/commit/cd79b3f81441a3d9ab50f11bc8c3b5c7bf722540 commit 4571e39cd724a973270a586d2b18f653f0007de9 Author: Didier Roche Date: Tue Nov 15 11:14:35 2022 +0100 Subject: Use a better case to assert on ServerURL() failure being ignored. Link: https://github.com/ubuntu/adsys/commit/4571e39cd724a973270a586d2b18f653f0007de9 commit fdca6e462c26e1cbecdb8386f43515c1947d423d Author: Didier Roche Date: Tue Nov 15 11:16:21 2022 +0100 Subject: Add a separate case for special characters in domain name. Link: https://github.com/ubuntu/adsys/commit/fdca6e462c26e1cbecdb8386f43515c1947d423d These commits are not compatible with 0.9.2 due to testsuite harnesses and frameworks and test data files not being added until 0.10.0, and adding such commits is numerous, and contains too many changes for a SRU. Regrettably, the testsuite commits must be omitted. To manage notifications about
[Desktop-packages] [Bug 2023766] Re: Mouse cursor stutters over GUI elements that are animated
Hello Daniel, or anyone else affected, Accepted mutter into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done-jammy ** Tags added: verification-needed-jammy -- 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/2023766 Title: Mouse cursor stutters over GUI elements that are animated Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Lunar: Fix Committed Status in mutter source package in Mantic: Fix Released Bug description: [ Impact ] Mouse cursor stutters over GUI elements that are animated, such as GTK apps, web pages and shell elements. [ Test Plan ] 1. Open Settings. 2. Move the cursor up/down over an empty area of the desktop. 3. Move the cursor up/down over the list pane on the left side of the Settings window. Expect: No difference in cursor smoothness whether the window below is animating in response to movement or not. [ Where problems could occur ] In frame scheduling, so the risk is more stuttering or screen freezes. [ Workaround ] Add this to /etc/environment: CLUTTER_PAINT=disable-dynamic-max-render-time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023766/+subscriptions -- Mailing list: https://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 2026887] Please test proposed package
Hello Ionut, or anyone else affected, Accepted mutter into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2026887 Title: gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: Fix Released Status in linux-intel-iotg package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Kinetic: Invalid Status in mutter source package in Lunar: Invalid Status in mutter source package in Mantic: Invalid Bug description: [ Impact ] gnome-shell/mutter 42.9 fails to start (black screen) on Intel Alder Lake systems running older kernels such as 5.15. [ Test Plan ] Try to log into gnome-shell. Verify there is a picture on the screen. [ Where problems could occur ] The offending code change relates to Intel-specific chip IDs so the change is limited to Intel systems. Although affected Intel systems worked perfectly before the change so we don't expect any problems in reverting the change. In theory the worst case is limited to more problems like that described in Impact above. [ Workarounds ] Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment or upgrade to a newer kernel: sudo apt install linux-generic-hwe-22.04 [ Other Info ] The log messages relating to this bug are: iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument ... For kinetic: The bug never existed in mutter 43.0 (it was introduced in 43.2) and was already fixed in the kernel anyway. For lunar and later: The bug was already fixed in the kernel. You would only ever encounter it in theory if you downgrade the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026887/+subscriptions -- Mailing list: https://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 2026887] Re: gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers
In the test plan, can you also please confirm it keeps working with the current and upcoming HWE kernels for jammy? ** Changed in: mutter (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- 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/2026887 Title: gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: Fix Released Status in linux-intel-iotg package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Kinetic: Invalid Status in mutter source package in Lunar: Invalid Status in mutter source package in Mantic: Invalid Bug description: [ Impact ] gnome-shell/mutter 42.9 fails to start (black screen) on Intel Alder Lake systems running older kernels such as 5.15. [ Test Plan ] Try to log into gnome-shell. Verify there is a picture on the screen. [ Where problems could occur ] The offending code change relates to Intel-specific chip IDs so the change is limited to Intel systems. Although affected Intel systems worked perfectly before the change so we don't expect any problems in reverting the change. In theory the worst case is limited to more problems like that described in Impact above. [ Workarounds ] Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment or upgrade to a newer kernel: sudo apt install linux-generic-hwe-22.04 [ Other Info ] The log messages relating to this bug are: iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument ... For kinetic: The bug never existed in mutter 43.0 (it was introduced in 43.2) and was already fixed in the kernel anyway. For lunar and later: The bug was already fixed in the kernel. You would only ever encounter it in theory if you downgrade the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026887/+subscriptions -- Mailing list: https://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 2027737] Re: Can't login to or add google accounts through control center
*** This bug is a duplicate of bug 2023322 *** https://bugs.launchpad.net/bugs/2023322 ** This bug has been marked a duplicate of bug 2023322 Unable to setup Google Online Accounts with Nvidia drivers -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2027737 Title: Can't login to or add google accounts through control center Status in gnome-control-center package in Ubuntu: New Bug description: My google account credentials say expired and the control center says I need to log in so I click on it, select to log in. A window for google sign in pops up with my email already entered and a next button. when you click the next button nothing happens. Ubuntu 23.04, gnome-control-center Installed: 1:44.0-1ubuntu5 I expected it to work it did not work ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44.0-1ubuntu5 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jul 13 15:21:54 2023 ExecutablePath: /usr/libexec/gnome-control-center-goa-helper InstallationDate: Installed on 2023-07-11 (2 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2027737/+subscriptions -- Mailing list: https://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 2027617] Re: Expose custom display modes in Wayland sessions like Xorg does
** Changed in: mutter Status: Unknown => New -- 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/2027617 Title: Expose custom display modes in Wayland sessions like Xorg does Status in Mutter: New Status in mutter package in Ubuntu: Triaged Bug description: I guess it is related to the latest updates. Before I can change refresh rate. As for now, the refresh rate is fixed (59.88Hz) and I don't have any option to change it. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 12 12:23:31 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:3802] InstallationDate: Installed on 2018-09-15 (1760 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 80Y8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-25-generic root=UUID=56a0d470-0b27-4743-8549-8b7195c884a1 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2017 dmi.bios.release: 1.28 dmi.bios.vendor: LENOVO dmi.bios.version: 5NCN28WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 920-13IKB Glass dmi.ec.firmware.release: 0.29 dmi.modalias: dmi:bvnLENOVO:bvr5NCN28WW:bd08/23/2017:br1.28:efr0.29:svnLENOVO:pn80Y8:pvrLenovoYOGA920-13IKBGlass:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKBGlass:skuLENOVO_MT_80Y8_BU_idea_FM_YOGA920-13IKBGlass: dmi.product.family: YOGA 920-13IKB Glass dmi.product.name: 80Y8 dmi.product.sku: LENOVO_MT_80Y8_BU_idea_FM_YOGA 920-13IKB Glass dmi.product.version: Lenovo YOGA 920-13IKB Glass dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~23.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2027617/+subscriptions -- Mailing list: https://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 2027571] Re: gnome-extensions-app crash, parser_get_compose_table: assertion failed:
** Changed in: gnome-shell Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2027571 Title: gnome-extensions-app crash, parser_get_compose_table: assertion failed: Status in GNOME Shell: New Status in GTK+: Fix Released Status in gtk4 package in Ubuntu: New Bug description: ENV: Ubuntu 22.04.2 LTS on X11, GNOME Shell 42.9 symptom : gnome-extensions-app crash everytime right at start. message: ``` /usr/bin/gnome-extensions-app ** Gtk:ERROR:../../../gtk/gtkcomposetable.c:981:parser_get_compose_table: assertion failed: (data[first_pos + i] <= data[first_pos + i + 1]) Bail out! Gtk:ERROR:../. ``` gdb backtrace: ``` ** Gtk:ERROR:../../../gtk/gtkcomposetable.c:981:parser_get_compose_table: assertion failed: (data[first_pos + i] <= data[first_pos + i + 1]) Bail out! Gtk:ERROR:../../../gtk/gtkcomposetable.c:981:parser_get_compose_table: assertion failed: (data[first_pos + i] <= data[first_pos + i + 1]) Thread 16 "pool-gnome-exte" received signal SIGABRT, Aborted. [Switching to Thread 0x70858640 (LWP 9456)] __pthread_kill_implementation (no_tid=0, signo=6, threadid=140737228670528) at ./nptl/pthread_kill.c:44 44./nptl/pthread_kill.c: No such file or directory. (gdb) bt #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140737228670528) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=140737228670528) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=140737228670528, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x776bb476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x776a17f3 in __GI_abort () at ./stdlib/abort.c:79 #5 0x77d44b57 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x77d9e70f in g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x711be0e3 in () at /lib/x86_64-linux-gnu/libgtk-4.so.1 #8 0x7123a0b4 in () at /lib/x86_64-linux-gnu/libgtk-4.so.1 #9 0x7123a7b1 in () at /lib/x86_64-linux-gnu/libgtk-4.so.1 #10 0x77b9f194 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #11 0x77dad6b4 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x77daaa51 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7770db43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #14 0x7779fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 ``` Moreover, I found in my snap logs that there was update recently applied, might be linked ``` $snap changes ID Status SpawnReadySummary 253 Doneyesterday at 21:47 CEST yesterday at 21:47 CEST Remove "gnome-3-34-1804" snap 254 Doneyesterday at 22:23 CEST yesterday at 22:23 CEST Refresh "gnome-3-38-2004" snap ``` Moreover, is seems I have multiple snap version of gnome installed ``` snap list ... gnome-3-28-18043.28.0-19-g98f9e67.98f9e67 198latest/stable canonical✓ - gnome-3-38-20040+git.efb213a 143latest/stable canonical✓ - gnome-42-2204 0+git.ff35a85 120latest/stable canonical✓ - ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome (not installed) ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99 Uname: Linux 5.15.0-76-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jul 12 12:10:10 2023 InstallationDate: Installed on 2021-08-18 (692 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: meta-gnome3 UpgradeStatus: Upgraded to jammy on 2023-07-01 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2027571/+subscriptions -- Mailing list: https://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 2027792] [NEW] After upgrading to 23.04 I have no ubuntu dock or desktop icons. I reinstalled gnome desktop and all gnome app, but only get the apps menu on moving my mouse to
Public bug reported: No ubuntu dock on screen and no desktop icons appear. The ubuntu desktop settings is not present ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.2-0ubuntu1 Uname: Linux 6.2.9-060209-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 14 11:48:28 2023 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-14 (1216 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 44.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar third-party-packages wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2027792 Title: After upgrading to 23.04 I have no ubuntu dock or desktop icons. I reinstalled gnome desktop and all gnome app, but only get the apps menu on moving my mouse to the left screen edge Status in gnome-shell package in Ubuntu: New Bug description: No ubuntu dock on screen and no desktop icons appear. The ubuntu desktop settings is not present ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.2-0ubuntu1 Uname: Linux 6.2.9-060209-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 14 11:48:28 2023 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-14 (1216 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 44.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2027792/+subscriptions -- Mailing list: https://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 2027790] [NEW] bash completion doesn't show "remove" option
Public bug reported: Flatpak package contains bash script for bash completion feature. If I say `flatpak in`, I will got `info` and `install` options. Flatpak autocomplete options doesn't work for `remove` option. If I say `flatpak rem`, I will got only `remote`, and `remove` will not be suggested. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: flatpak 1.14.4-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 14 13:30:21 2023 ProcEnviron: LANG=ru_RU.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: flatpak UpgradeStatus: Upgraded to lunar on 2023-05-14 (60 days ago) ** Affects: flatpak (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/2027790 Title: bash completion doesn't show "remove" option Status in flatpak package in Ubuntu: New Bug description: Flatpak package contains bash script for bash completion feature. If I say `flatpak in`, I will got `info` and `install` options. Flatpak autocomplete options doesn't work for `remove` option. If I say `flatpak rem`, I will got only `remote`, and `remove` will not be suggested. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: flatpak 1.14.4-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 14 13:30:21 2023 ProcEnviron: LANG=ru_RU.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: flatpak UpgradeStatus: Upgraded to lunar on 2023-05-14 (60 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/2027790/+subscriptions -- Mailing list: https://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 2027779] Re: Second screen over usb-c stopped working after update
Thanks for the bug report. When the second monitor is plugged in, please run: sudo apt install drm-info drm_info > drminfo.txt grep . /sys/class/drm/*/status > connections.txt journalctl -b0 > journal.txt and attach the resulting text file here. Please also clarify if you are using a native USB-C monitor or a DisplayLink adapter. ** Package changed: xorg (Ubuntu) => linux-hwe-5.19 (Ubuntu) ** Changed in: linux-hwe-5.19 (Ubuntu) Status: New => Incomplete ** Tags added: multimonitor -- 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/2027779 Title: Second screen over usb-c stopped working after update Status in linux-hwe-5.19 package in Ubuntu: Incomplete Bug description: Hello, I recently got an update on my system which wrecked havoc on my display drivers. I cannot use a second monitor now any more through usb-c. When I plug in the screen nothing happens. I have verified whether there is any hardware failure (screen, cable, usb-c converter, usb-c ports on the laptop) and they all seem to be fine. I suspect it's this update which caused it: Start-Date: 2023-07-12 06:21:02 Commandline: /usr/bin/unattended-upgrade Upgrade: ghostscript-x:amd64 (9.55.0~dfsg1-0ubuntu5.2, 9.55.0~dfsg1-0ubuntu5.3), libgs9-common:amd64 (9.55.0~dfsg1-0ubuntu5.2, 9.55.0~dfsg1-0ubuntu5.3), ghostscript:amd64 (9.55.0~dfsg1-0ubuntu5.2, 9.55.0~dfsg1-0ubuntu5.3), libgs9:amd64 (9.55.0~dfsg1-0ubuntu5.2, 9.55.0~dfsg1-0ubuntu5.3) End-Date: 2023-07-12 06:21:02 Start-Date: 2023-07-12 06:21:04 Commandline: /usr/bin/unattended-upgrade Upgrade: libllvm15:amd64 (1:15.0.7-0ubuntu0.22.04.1, 1:15.0.7-0ubuntu0.22.04.2) End-Date: 2023-07-12 06:21:04 Could you please have a look and let me know if there is any workaround. This sets me back hours in investigation time... Regards, Hendrik ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jul 14 08:24:17 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:a7a1] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:230e] InstallationDate: Installed on 2023-06-19 (24 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: LENOVO 21HDCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic root=UUID=280c519f-c813-4a8e-8b21-28d80f5dbd8d ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2023 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: N3QET32W (1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 21HDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnLENOVO:bvrN3QET32W(1.32):bd05/09/2023:br1.32:efr1.6:svnLENOVO:pn21HDCTO1WW:pvrThinkPadT14Gen4:rvnLENOVO:rn21HDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21HD_BU_Think_FM_ThinkPadT14Gen4: dmi.product.family: ThinkPad T14 Gen 4 dmi.product.name: 21HDCTO1WW dmi.product.sku: LENOVO_MT_21HD_BU_Think_FM_ThinkPad T14 Gen 4 dmi.product.version: ThinkPad T14 Gen 4 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.0.20230414.1+2061~u22.04 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.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-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2027779/+subscriptions -- Mailing list: https://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 2027783] Re: Can't see login screen on resume after YoutTube fullscreen
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Also affects: mutter (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/2027783 Title: Can't see login screen on resume after YoutTube fullscreen Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Watchign youtube fullscreen, closed laptop, opened laptop, YT stuck in fullscreen and unable to see login screen. I was able to enter pass to get in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.4.3-060403-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jul 14 04:19:52 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:3803] InstallationDate: Installed on 2023-06-26 (17 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 8087:0032 Intel Corp. AX210 Bluetooth Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 04f2:b61e Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81C4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.4.3-060403-generic root=UUID=9d73ee34-4258-4eaa-9690-c36f0155d2a8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/23/2020 dmi.bios.release: 1.37 dmi.bios.vendor: LENOVO dmi.bios.version: 8GCN37WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA C930-13IKB dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvr8GCN37WW:bd11/23/2020:br1.37:efr1.33:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:skuLENOVO_MT_81C4_BU_idea_FM_YOGAC930-13IKB: dmi.product.family: YOGA C930-13IKB dmi.product.name: 81C4 dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB dmi.product.version: Lenovo YOGA C930-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.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-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2027783/+subscriptions -- Mailing list: https://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 2027783] [NEW] Can't see login screen on resume after YoutTube fullscreen
Public bug reported: Watchign youtube fullscreen, closed laptop, opened laptop, YT stuck in fullscreen and unable to see login screen. I was able to enter pass to get in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.4.3-060403-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jul 14 04:19:52 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:3803] InstallationDate: Installed on 2023-06-26 (17 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 8087:0032 Intel Corp. AX210 Bluetooth Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 04f2:b61e Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81C4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.4.3-060403-generic root=UUID=9d73ee34-4258-4eaa-9690-c36f0155d2a8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/23/2020 dmi.bios.release: 1.37 dmi.bios.vendor: LENOVO dmi.bios.version: 8GCN37WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA C930-13IKB dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvr8GCN37WW:bd11/23/2020:br1.37:efr1.33:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:skuLENOVO_MT_81C4_BU_idea_FM_YOGAC930-13IKB: dmi.product.family: YOGA C930-13IKB dmi.product.name: 81C4 dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB dmi.product.version: Lenovo YOGA C930-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.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-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- 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/2027783 Title: Can't see login screen on resume after YoutTube fullscreen Status in xorg package in Ubuntu: New Bug description: Watchign youtube fullscreen, closed laptop, opened laptop, YT stuck in fullscreen and unable to see login screen. I was able to enter pass to get in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.4.3-060403-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jul 14 04:19:52 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:3803] InstallationDate: Installed on 2023-06-26 (17 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 8087:0032 Intel Corp. AX210 Bluetooth Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 04f2:b61e Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81C4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.4.3-060403-generic root=UUID=9d73ee34-4258-4eaa-9690-c36f0155d2a8
[Desktop-packages] [Bug 2027779] Re: Second screen over usb-c stopped working after update
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2027779 Title: Second screen over usb-c stopped working after update Status in xorg package in Ubuntu: New Bug description: Hello, I recently got an update on my system which wrecked havoc on my display drivers. I cannot use a second monitor now any more through usb-c. When I plug in the screen nothing happens. I have verified whether there is any hardware failure (screen, cable, usb-c converter, usb-c ports on the laptop) and they all seem to be fine. I suspect it's this update which caused it: Start-Date: 2023-07-12 06:21:02 Commandline: /usr/bin/unattended-upgrade Upgrade: ghostscript-x:amd64 (9.55.0~dfsg1-0ubuntu5.2, 9.55.0~dfsg1-0ubuntu5.3), libgs9-common:amd64 (9.55.0~dfsg1-0ubuntu5.2, 9.55.0~dfsg1-0ubuntu5.3), ghostscript:amd64 (9.55.0~dfsg1-0ubuntu5.2, 9.55.0~dfsg1-0ubuntu5.3), libgs9:amd64 (9.55.0~dfsg1-0ubuntu5.2, 9.55.0~dfsg1-0ubuntu5.3) End-Date: 2023-07-12 06:21:02 Start-Date: 2023-07-12 06:21:04 Commandline: /usr/bin/unattended-upgrade Upgrade: libllvm15:amd64 (1:15.0.7-0ubuntu0.22.04.1, 1:15.0.7-0ubuntu0.22.04.2) End-Date: 2023-07-12 06:21:04 Could you please have a look and let me know if there is any workaround. This sets me back hours in investigation time... Regards, Hendrik ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jul 14 08:24:17 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:a7a1] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:230e] InstallationDate: Installed on 2023-06-19 (24 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: LENOVO 21HDCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic root=UUID=280c519f-c813-4a8e-8b21-28d80f5dbd8d ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2023 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: N3QET32W (1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 21HDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnLENOVO:bvrN3QET32W(1.32):bd05/09/2023:br1.32:efr1.6:svnLENOVO:pn21HDCTO1WW:pvrThinkPadT14Gen4:rvnLENOVO:rn21HDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21HD_BU_Think_FM_ThinkPadT14Gen4: dmi.product.family: ThinkPad T14 Gen 4 dmi.product.name: 21HDCTO1WW dmi.product.sku: LENOVO_MT_21HD_BU_Think_FM_ThinkPad T14 Gen 4 dmi.product.version: ThinkPad T14 Gen 4 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.0.20230414.1+2061~u22.04 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.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-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2027779/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
