[Desktop-packages] [Bug 2021446] [NEW] rhythmbox plugin grilo no longer discovers UPNP media share
Public bug reported: In Ubuntu <=22.10 the grilo rhythmbox plugin automatically discovered a UPnP media share from my Synology Network Attached Storage device on my local network. When I upgraded to Ubuntu 23.04, rhythmbox no longer detects the media share. I've confirmed that the share is detected on a computer with 22.10 but not on two computers with 23.04 (all on the same LAN). I've also confirmed that VLC media player detects the share on the Ubuntu 23.04 computers. I first posted a report here, thinking it was due to an update on the NAS: https://community.synology.com/enu/forum/1/post/160502 I then opened this issue on Rhythmbox's bug tracker: https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/2047 I expected Rhythmbox+Grilo to automatically discover a UPnP share on my local area network when on Ubuntu 22.10, but it does not discover the share. ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/2021446 Title: rhythmbox plugin grilo no longer discovers UPNP media share Status in rhythmbox package in Ubuntu: New Bug description: In Ubuntu <=22.10 the grilo rhythmbox plugin automatically discovered a UPnP media share from my Synology Network Attached Storage device on my local network. When I upgraded to Ubuntu 23.04, rhythmbox no longer detects the media share. I've confirmed that the share is detected on a computer with 22.10 but not on two computers with 23.04 (all on the same LAN). I've also confirmed that VLC media player detects the share on the Ubuntu 23.04 computers. I first posted a report here, thinking it was due to an update on the NAS: https://community.synology.com/enu/forum/1/post/160502 I then opened this issue on Rhythmbox's bug tracker: https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/2047 I expected Rhythmbox+Grilo to automatically discover a UPnP share on my local area network when on Ubuntu 22.10, but it does not discover the share. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/2021446/+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 2018455] Re: gnome-shell exits after screen lock / unlock & login segfault libmutter-12.so.0.0.0 in Ubuntu 23.04 on Lenovo X1 Carbon Gen10
This bug is incomplete awaiting a clear crash report. For each file you find in /var/crash please run ubuntu-bug so the crashes can be analysed automatically. That will also create new bug reports each time. -- 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/2018455 Title: gnome-shell exits after screen lock / unlock & login segfault libmutter-12.so.0.0.0 in Ubuntu 23.04 on Lenovo X1 Carbon Gen10 Status in mutter package in Ubuntu: Incomplete Bug description: The issue is happening 9 out of 10 times. It is hard to get a crash dump in /var/crash during this error though, but I found one from few days ago. Looks like should be relevant. I've reported it, see OOPS ID: b68253a2-ea4c-11ed-af33-fa163e55efd0 Laptop: Lenovo ThinkPad X1 Carbon Gen 10, model 21CB007WCK root@x1:~# uname -a Linux x1 6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 6 07:48:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux To reproduce: 1. Win+L to lock the session 2. Screen turns black as expected 3. Login back to your session 4. Welcome to the new & clean session... all unsaved work is lost! 5. see gnome-shell segfault in libmutter-12.so in dmesg root@x1:~# dmesg -T |grep segf [Thu May 4 17:45:04 2023] gnome-shell[2554]: segfault at ff78 ip 7f3d10961115 sp 7ffd72b85f78 error 5 in libmutter-12.so.0.0.0[7f3d1084a000+13d000] likely on CPU 0 (core 0, socket 0) [Fri May 5 14:09:43 2023] gnome-shell[24568]: segfault at 11 ip 7f4c14161119 sp 7ffd4590de28 error 4 in libmutter-12.so.0.0.0[7f4c1404a000+13d000] likely on CPU 9 (core 17, socket 0) Logs from "ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash" command May 04 09:24:31 x1 systemd[1]: Started whoopsie.service - crash report submission. May 04 09:24:31 x1 whoopsie[54307]: [09:24:31] Using lock path: /var/lock/whoopsie/lock May 04 09:24:31 x1 whoopsie[54307]: [09:24:31] Parsing /var/crash/_usr_bin_gnome-shell.1000.crash. May 04 09:24:31 x1 whoopsie[54307]: [09:24:31] Uploading /var/crash/_usr_bin_gnome-shell.1000.crash. May 04 09:24:32 x1 whoopsie[54307]: [09:24:32] Sent; server replied with: No error May 04 09:24:32 x1 whoopsie[54307]: [09:24:32] Response code: 200 May 04 09:24:32 x1 whoopsie[54307]: [09:24:32] Reported OOPS ID b68253a2-ea4c-11ed-af33-fa163e55efd0 It was difficult to figure how to send the report in Ubuntu 23.04, previously it was just working... but with Ubuntu 23.04 there was this error: May 04 09:21:33 x1 systemd[1]: Starting apport-autoreport.service - Process error reports when automatic reporting is enabled... May 04 09:21:33 x1 systemd[1]: Started whoopsie.service - crash report submission. May 04 09:21:33 x1 whoopsie[53709]: [09:21:33] Using lock path: /var/lock/whoopsie/lock May 04 09:21:33 x1 systemd[1]: whoopsie.service: Deactivated successfully. May 04 09:21:33 x1 whoopsie-upload-all[53708]: ERROR: whoopsie.path is not enabled May 04 09:21:33 x1 systemd[1]: apport-autoreport.service: Main process exited, code=exited, status=1/FAILURE May 04 09:21:33 x1 systemd[1]: apport-autoreport.service: Failed with result 'exit-code'. May 04 09:21:33 x1 systemd[1]: Failed to start apport-autoreport.service - Process error reports when automatic reporting is enabled. Fixed by changing "Send error reports to Canonical" (in gnome control panel -> "Privacy" -> "Diagnostics") from "Automatic" to "Never" and re-running the `ubuntu-bug` command again. gnome-shell 44.0-2ubuntu3 intel-media-va-driver:amd64 23.1.2+dfsg1-1 root@x1:~# lshw -class display *-display description: VGA compatible controller product: Alder Lake-P Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 logical name: /dev/fb0 version: 0c width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb configuration: depth=32 driver=i915 latency=0 mode=1920x1200 resolution=1920,1200 visual=truecolor xres=1920 yres=1200 resources: iomemory:600-5ff iomemory:400-3ff irq:199 memory:603d00-603dff memory:40-400fff ioport:2000(size=64) memory:c-d memory:401000-4016ff memory:402000-40 root@x1:~# lshw -class multimedia *-multimedia:0 UNCLAIMED description: Multimedia controller product: Intel Corporation vendor: Intel Corporation physical id: 5 bus info: pci@:00:05.0 version: 02 width: 64 bits clock: 33MHz capabilities: pciexpress pm cap_list configuration: latency=0 resources: iomemory:600-5ff memory:603c00-603cff *-multimedia:1 description: Audio device
[Desktop-packages] [Bug 1993054] Re: USB key eject does not eject
Still same problem in Ubuntu 23.10 with gnome-shell-extension-ubuntu- dock: Installed: 81ubuntu1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1993054 Title: USB key eject does not eject Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I insert an USB key: icon appear in the dock and in the nautilus sidebar with title and a small arrow right click on icon in the dock and select 'Eject': the icon disappear in the dock but does NOT disappear from the nautilus sidebar click on the arrow near the icon in nautilus sidebar: the icon disappear and I see a message in notification area with: '... USB flash memory ... can be removed' problem happens when org.gnome.shell.extensions.dash-to-dock show-mounts-only-mounted is set to TRUE the problem does not occur if show-mounts-only-mounted is set to FALSE ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell-extension-ubuntu-dock 74ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 16 09:48:16 2022 InstallationDate: Installed on 2022-09-30 (15 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1993054/+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 1772212] Re: [nvidia] Night light doesn't cover all monitors fully
[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-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1772212 Title: [nvidia] Night light doesn't cover all monitors fully Status in gnome-settings-daemon package in Ubuntu: Expired Status in gnome-shell package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Bug description: Hi, The GNOME night light only seems to work on the first half of the first screen within a dual monitor setup (Ubuntu 18.04 stock, using X11 with Gefore GT240, NVIDIA proprietary drivers). See attached screenshots. br, Koen. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: koen 1820 F pulseaudio /dev/snd/controlC1: koen 1820 F pulseaudio /dev/snd/controlC3: koen 1820 F pulseaudio /dev/snd/controlC2: koen 1820 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=9b7457bf-328f-4fe5-9e46-ed14b65d4fb2 InstallationDate: Installed on 2018-05-05 (14 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. enp0s10 no wireless extensions. MachineType: . . NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=5dcdbe58-6afd-4f90-ab58-1f53f5cfa9f4 ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 07/31/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: AN-M2HD(MCP68) dmi.board.vendor: http://www.abit.com.tw/ dmi.board.version: 1.x dmi.chassis.asset.tag: Unknow dmi.chassis.type: 3 dmi.chassis.vendor: nVIDIA dmi.chassis.version: Unknow dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd07/31/2008:svn.:pn.:pvrUnknow:rvnhttp//www.abit.com.tw/:rnAN-M2HD(MCP68):rvr1.x:cvnnVIDIA:ct3:cvrUnknow: dmi.product.name: . dmi.product.version: Unknow dmi.sys.vendor: . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1772212/+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 1772212] Re: [nvidia] Night light doesn't cover all monitors fully
[Expired for mutter (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mutter (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1772212 Title: [nvidia] Night light doesn't cover all monitors fully Status in gnome-settings-daemon package in Ubuntu: Expired Status in gnome-shell package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Bug description: Hi, The GNOME night light only seems to work on the first half of the first screen within a dual monitor setup (Ubuntu 18.04 stock, using X11 with Gefore GT240, NVIDIA proprietary drivers). See attached screenshots. br, Koen. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: koen 1820 F pulseaudio /dev/snd/controlC1: koen 1820 F pulseaudio /dev/snd/controlC3: koen 1820 F pulseaudio /dev/snd/controlC2: koen 1820 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=9b7457bf-328f-4fe5-9e46-ed14b65d4fb2 InstallationDate: Installed on 2018-05-05 (14 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. enp0s10 no wireless extensions. MachineType: . . NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=5dcdbe58-6afd-4f90-ab58-1f53f5cfa9f4 ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 07/31/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: AN-M2HD(MCP68) dmi.board.vendor: http://www.abit.com.tw/ dmi.board.version: 1.x dmi.chassis.asset.tag: Unknow dmi.chassis.type: 3 dmi.chassis.vendor: nVIDIA dmi.chassis.version: Unknow dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd07/31/2008:svn.:pn.:pvrUnknow:rvnhttp//www.abit.com.tw/:rnAN-M2HD(MCP68):rvr1.x:cvnnVIDIA:ct3:cvrUnknow: dmi.product.name: . dmi.product.version: Unknow dmi.sys.vendor: . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1772212/+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 1772212] Re: [nvidia] Night light doesn't cover all monitors fully
[Expired for gnome-settings-daemon (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-settings-daemon (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1772212 Title: [nvidia] Night light doesn't cover all monitors fully Status in gnome-settings-daemon package in Ubuntu: Expired Status in gnome-shell package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Bug description: Hi, The GNOME night light only seems to work on the first half of the first screen within a dual monitor setup (Ubuntu 18.04 stock, using X11 with Gefore GT240, NVIDIA proprietary drivers). See attached screenshots. br, Koen. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: koen 1820 F pulseaudio /dev/snd/controlC1: koen 1820 F pulseaudio /dev/snd/controlC3: koen 1820 F pulseaudio /dev/snd/controlC2: koen 1820 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=9b7457bf-328f-4fe5-9e46-ed14b65d4fb2 InstallationDate: Installed on 2018-05-05 (14 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. enp0s10 no wireless extensions. MachineType: . . NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=5dcdbe58-6afd-4f90-ab58-1f53f5cfa9f4 ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 07/31/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: AN-M2HD(MCP68) dmi.board.vendor: http://www.abit.com.tw/ dmi.board.version: 1.x dmi.chassis.asset.tag: Unknow dmi.chassis.type: 3 dmi.chassis.vendor: nVIDIA dmi.chassis.version: Unknow dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd07/31/2008:svn.:pn.:pvrUnknow:rvnhttp//www.abit.com.tw/:rnAN-M2HD(MCP68):rvr1.x:cvnnVIDIA:ct3:cvrUnknow: dmi.product.name: . dmi.product.version: Unknow dmi.sys.vendor: . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1772212/+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 2012832] Re: Xorg crashes on second and next unbind operations of Arc GPU
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2012832 Title: Xorg crashes on second and next unbind operations of Arc GPU Status in linux package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: Hello folks, Experimenting with new Lenovo Yoga i7 with Intel Arc on board and found that even if it's possible to disable the GPU to save power, Xorg session crashes the session after the second attempt (the first after reboot works just fine). This works like that - after poweroff/poweron of the system I execute the next commands: 1. First attempt: * DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Arc(tm) A370M Graphics (DG2)" * echo -n ":04:00.0" | sudo tee /sys/bus/pci/drivers/i915/unbind # Works great * DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Graphics (ADL GT2)", it's embedded graphics * echo -n ":04:00.0" | sudo tee /sys/bus/pci/drivers/i915/bind * DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Arc(tm) A370M Graphics (DG2)" 2. Second attempt: * echo -n ":04:00.0" | sudo tee /sys/bus/pci/drivers/i915/unbind # Here the Xorg crashes, but I can login again * DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Graphics (ADL GT2)", it's embedded graphics * echo -n ":04:00.0" | sudo tee /sys/bus/pci/drivers/i915/bind * DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Arc(tm) A370M Graphics (DG2)" 3. This and the next attempts are just the same as second one I collected the info and can reproduce this state after each reboot, so hopefully it will help you to find what's going wrong during second and next unbind operations. I can always help with additional information if you will need some. Thank you ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.2.8-060208-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Sun Mar 26 12:25:03 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3ae3] Subsystem: Lenovo Device [17aa:3ae3] InstallationDate: Installed on 2023-02-21 (33 days ago) InstallationMedia: Xubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 82UF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.8-060208-generic root=UUID=52e0f674-3384-4128-973b-d049407f961a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2022 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: J1CN35WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 7 16IAH7 dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrJ1CN35WW:bd11/16/2022:br1.35:efr1.35:svnLENOVO:pn82UF:pvrYoga716IAH7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct31:cvrYoga716IAH7:skuLENOVO_MT_82UF_BU_idea_FM_Yoga716IAH7: dmi.product.family: Yoga 7 16IAH7 dmi.product.name: 82UF dmi.product.sku: LENOVO_MT_82UF_BU_idea_FM_Yoga 7 16IAH7 dmi.product.version: Yoga 7 16IAH7 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.0.0.20221126.1+2050~u22.04 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.8 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/+bug/2012832/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 2012832] Re: Xorg crashes on second and next unbind operations of Arc GPU
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2012832 Title: Xorg crashes on second and next unbind operations of Arc GPU Status in linux package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: Hello folks, Experimenting with new Lenovo Yoga i7 with Intel Arc on board and found that even if it's possible to disable the GPU to save power, Xorg session crashes the session after the second attempt (the first after reboot works just fine). This works like that - after poweroff/poweron of the system I execute the next commands: 1. First attempt: * DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Arc(tm) A370M Graphics (DG2)" * echo -n ":04:00.0" | sudo tee /sys/bus/pci/drivers/i915/unbind # Works great * DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Graphics (ADL GT2)", it's embedded graphics * echo -n ":04:00.0" | sudo tee /sys/bus/pci/drivers/i915/bind * DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Arc(tm) A370M Graphics (DG2)" 2. Second attempt: * echo -n ":04:00.0" | sudo tee /sys/bus/pci/drivers/i915/unbind # Here the Xorg crashes, but I can login again * DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Graphics (ADL GT2)", it's embedded graphics * echo -n ":04:00.0" | sudo tee /sys/bus/pci/drivers/i915/bind * DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Arc(tm) A370M Graphics (DG2)" 3. This and the next attempts are just the same as second one I collected the info and can reproduce this state after each reboot, so hopefully it will help you to find what's going wrong during second and next unbind operations. I can always help with additional information if you will need some. Thank you ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.2.8-060208-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Sun Mar 26 12:25:03 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3ae3] Subsystem: Lenovo Device [17aa:3ae3] InstallationDate: Installed on 2023-02-21 (33 days ago) InstallationMedia: Xubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 82UF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.8-060208-generic root=UUID=52e0f674-3384-4128-973b-d049407f961a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2022 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: J1CN35WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 7 16IAH7 dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrJ1CN35WW:bd11/16/2022:br1.35:efr1.35:svnLENOVO:pn82UF:pvrYoga716IAH7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct31:cvrYoga716IAH7:skuLENOVO_MT_82UF_BU_idea_FM_Yoga716IAH7: dmi.product.family: Yoga 7 16IAH7 dmi.product.name: 82UF dmi.product.sku: LENOVO_MT_82UF_BU_idea_FM_Yoga 7 16IAH7 dmi.product.version: Yoga 7 16IAH7 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.0.0.20221126.1+2050~u22.04 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.8 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/+bug/2012832/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 2013135] Re: Dissapearing Mouse Cursor
[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/2013135 Title: Dissapearing Mouse Cursor Status in gnome-shell package in Ubuntu: Expired Bug description: Touching the touch screen display removes the mouse cursor. It comes back after blindly navigating to the menu bar. This also happends randomly without touching the touchscreen. There doesn't appear to be a trigger for the random disappearances that is user input. Thanks, ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..04.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.157 Wed Oct 12 09:19:07 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 28 18:19:00 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05fc] Subsystem: Dell GK107M [GeForce GT 750M] [1028:05fc] InstallationDate: Installed on 2023-02-28 (28 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Dell Inc. Inspiron 7737 ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=1322e8b8-bc4a-464a-89b8-6bc305451ff5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2013 dmi.bios.release: 0.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0H9X60 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.ec.firmware.release: 0.4 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd10/09/2013:br0.4:efr0.4:svnDellInc.:pnInspiron7737:pvr:rvnDellInc.:rn0H9X60:rvrA00:cvnDellInc.:ct8:cvr0.1:skuInspiron7737: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7737 dmi.product.sku: Inspiron 7737 dmi.sys.vendor: Dell Inc. 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.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 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/2013135/+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 2013542] Re: [lunar] windows size/position is not saved for some apps
It might work in a VM because that uses Xorg? I'd expect this to be more of a problem for Wayland (https://gitlab.gnome.org/GNOME/mutter/-/issues/2374). At least with X11, apps/toolkits can remember and enforce their window position. In Wayland they can't. I can't find any upstream reports saying that it works less now than in previous releases though. ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2374 https://gitlab.gnome.org/GNOME/mutter/-/issues/2374 -- 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/2013542 Title: [lunar] windows size/position is not saved for some apps Status in gnome-shell package in Ubuntu: Confirmed Bug description: Hi, Lunar up to date, Ubuntu session, Wayland or X11 1) open Synaptic not in full screen 2) change window size to full screen 3) close Synaptic 4) open Synaptic 5) its window is not maximized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2013542/+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 2012100] Re: gnome-shell crashed with SIGSEGV in meta_wayland_compositor_get_context() from display_from_offer() from data_offer_receive() from ffi_call_unix64()
Yes, if you know how to safely. -- 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/2012100 Title: gnome-shell crashed with SIGSEGV in meta_wayland_compositor_get_context() from display_from_offer() from data_offer_receive() from ffi_call_unix64() Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Committed Status in mutter source package in Mantic: Fix Released Bug description: https://errors.ubuntu.com/problem/d525586b43c9aeae86d5c9c7bb28ba925afb I have this error when I'm connecting to nym-connect (nymtech.net) ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44~beta-1ubuntu1 Uname: Linux 5.19.0-21-generic x86_64 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 17 18:10:09 2023 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1677216555 ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/judemont ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 11 SourcePackage: gnome-shell UserGroups: adm cdrom dip lpadmin plugdev sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2012100/+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 1993214] Re: [jammy] Update gjs to 1.74 using mozjs102 102.3
Per comment #8, I think this should still be blocked on bug 1994010 or else we risk jammy getting flooded with that crash like kinetic still is: https://errors.ubuntu.com/?release=Ubuntu%2022.10=gnome- shell=week -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1993214 Title: [jammy] Update gjs to 1.74 using mozjs102 102.3 Status in gjs package in Ubuntu: Fix Released Status in mozjs102 package in Ubuntu: Fix Released Status in gjs source package in Jammy: Incomplete Status in mozjs102 source package in Jammy: Fix Committed Status in mozjs102 source package in Kinetic: Fix Committed Bug description: Impact -- GNOME Shell uses the SpiderMonkey JavaScript engine from Firefox ESR (mozjs). Firefox 92 ESR has reached end of life; therefore, we should switch to the 102 ESR series for security updates for the next year. This requires updating gjs from 1.72 to 1.74 from GNOME 43, as packaged in Ubuntu 22.10. This will be done as a Security Update. Updating mozjs in stable Ubuntu releases was recommended when Ubuntu first switched back to GNOME, but this is the first time it's been done. Security Impact --- I looked through https://github.com/mozilla/gecko-dev/commits/esr102/js and searched for referenced bug numbers in https://www.mozilla.org/en-US/security/advisories/ for Firefox ESR releases since Ubuntu's 91.10 and found one CVE. Also, there's the vague Mozilla Bug 1771084 (no CVE issued) mentioned at https://www.mozilla.org/en-US/security/advisories/mfsa2022-24/ Uploaded Packages - We will introduce mozjs102, a new source package for Ubuntu 22.04 LTS, being careful to publish it in main, not universe. And we'll update gjs. No other packages need to be updated for this change. mozjs91 will remain in Ubuntu 22.04 LTS (source package removals are generally not possible), but nothing else in Ubuntu uses it. Test Case - https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs Security Sponsoring --- sudo apt install git-buildpackage gbp clone https://salsa.debian.org/gnome-team/gjs cd gjs git checkout ubuntu/jammy gbp buildpackage --git-builder="debuild -S -nc" mkdir ../tarballs; cd ../tarballs pull-lp-source mozjs102 kinetic cd .. gbp clone https://salsa.debian.org/gnome-team/mozjs cd mozjs git checkout ubuntu/102/jammy gbp buildpackage --git-builder="debuild --no-lintian -S -nc" --git-tarball-dir=../tarballs # That avoids needing to recreate the original tarball from pristine-tar which takes a while. Also, running lintian takes a while. Initial Testing Done I built the packages in my PPA. I installed the packages on Ubuntu 22.04 LTS and successfully completed the Test Case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1993214/+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 2021444] [NEW] Gnome Shell memory leaking problem. When drag the windows from small to big, the memory usage increase and will never fall
Public bug reported: Gnome Shell memory leaking problem. When drag the windows from small to big, the memory usage increase and will never fall. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 Uname: Linux 6.3.4-cjktty x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 29 11:27:15 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-05-24 (4 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-05-26T16:38:49.940102 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- 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/2021444 Title: Gnome Shell memory leaking problem. When drag the windows from small to big, the memory usage increase and will never fall Status in gnome-shell package in Ubuntu: New Bug description: Gnome Shell memory leaking problem. When drag the windows from small to big, the memory usage increase and will never fall. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 Uname: Linux 6.3.4-cjktty x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 29 11:27:15 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-05-24 (4 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-05-26T16:38:49.940102 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2021444/+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 1974293] Re: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl()
Ghadi, Please create a merge request at https://salsa.debian.org/gnome- team/gjs/-/merge_requests targeting the ubuntu/jammy branch Although if it lands in proposed first, we can do that afterwards. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1974293 Title: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl() Status in gjs: Fix Released Status in OEM Priority Project: Confirmed Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Jammy: In Progress Status in gjs source package in Kinetic: Triaged Status in gjs source package in Lunar: Fix Released Status in gnome-shell package in Fedora: Confirmed Bug description: [ Impact ] gnome-shell often crashes on logout causing annoyance to the user as an error report dialog is displayed at the next login. [ Test Plan ] 1. Log into gnome-shell 2. Use gnome-shell for long enough to trigger a garbage collection cycle: Scroll the app grid and repeatedly open the calendar from the top bar for 30 seconds. 3. Log out. 4. Verify no new gnome-shell crash files appear in /var/crash/ [ Where problems could occur ] Only gnome-shell shutdown/logout is affected. [ Other Info ] https://errors.ubuntu.com/problem/256d1c0d1aad03bb024b525f4c80868e8f6a85b4 https://errors.ubuntu.com/problem/b1669e114babda005eb5a6414867a0eb7293f7e7 Description: Ubuntu 22.04 LTS Release: 22.04 ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 20 16:06:35 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1649813447 InstallationDate: Installed on 2022-05-05 (14 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/ubuntu RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libmozjs-91.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () Title: gnome-shell crashed with SIGSEGV in g_object_unref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1974293/+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: Changing display scale setting and reverting it, causes gnome-shell to error with "Failed to restore previous configuration" and other error messages
Fabio, please try building mutter without the fractional scaling patch. So just delete: ubuntu/x11-Add-support-for-fractional-scaling-using-Randr.patch from debian/patches/series. That should retain support for integer scaling, but will tell us if the fractional scaling patch is causing this bug as a side effect. -- 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: Changing display scale setting and reverting it, causes gnome-shell to error with "Failed to restore previous configuration" and other error messages Status in mutter package in Ubuntu: New Bug description: 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 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0 557093f00e68 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 (2cdac32b2e20 @ 105) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1 557093f00dd8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 (2cdac32a5d80 @ 27) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2 557093f00d58 i resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: monitor is null#012_updateWorkAreaBox@resource:///org/gnome/shell/ui/overviewControls.js:58:26#012_init/<@resource:///org/gnome/shell/ui/overviewControls.js:51:45 Sometimes the stack trace isn't shown, but the symptom is the same: May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 18:31:40 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". I'm unable to reproduce the problem if I manually install ubuntu-desktop and use the Nice DCV Server (as used by Workspaces) by following the steps from
[Desktop-packages] [Bug 2021438] [NEW] Display
Public bug reported: When the system turns off the screen by power management, the screen does not come back active again, having to activate the brightness keys for it to come back. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.105.17 Tue Mar 28 18:02:59 UTC 2023 GCC version: ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 28 21:14:21 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo CoffeeLake-H GT2 [UHD Graphics 630] [17aa:3a2d] NVIDIA Corporation GP107M [GeForce GTX 1050 3 GB Max-Q] [10de:1c91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GP107M [GeForce GTX 1050 3 GB Max-Q] [17aa:3a2d] InstallationDate: Installed on 2023-05-28 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: LENOVO 81TR ProcEnviron: LANG=pt_BR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=efac633a-69bd-49a0-b3ca-ba7e617e416a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2021 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: BGCN34WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO IDEAPAD L340-15IRH dmi.ec.firmware.release: 1.34 dmi.modalias: dmi:bvnLENOVO:bvrBGCN34WW:bd05/21/2021:br1.34:efr1.34:svnLENOVO:pn81TR:pvrLENOVOIDEAPADL340-15IRH:rvnLENOVO:rnINVALID:rvrNoDPK:cvnLENOVO:ct10:cvrLENOVOIDEAPADL340-15IRH:skuLENOVO_MT_81TR_BU_idea_FM_IDEAPAD: dmi.product.family: IDEAPAD dmi.product.name: 81TR dmi.product.sku: LENOVO_MT_81TR_BU_idea_FM_IDEAPAD dmi.product.version: LENOVO IDEAPAD L340-15IRH 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.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar 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/2021438 Title: Display Status in xorg package in Ubuntu: New Bug description: When the system turns off the screen by power management, the screen does not come back active again, having to activate the brightness keys for it to come back. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.105.17 Tue Mar 28 18:02:59 UTC 2023 GCC version: ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 28 21:14:21 2023 DistUpgraded: Fresh install DistroCodename: lunar
[Desktop-packages] [Bug 2020803] Re: logging in at the lock screen causes the system to log me out and start over.
Inexplicably the problem has disappeared. I'll this thread if it resurfaces, but for now there's no additional information I can provide. Sorry about that! -- 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/2020803 Title: logging in at the lock screen causes the system to log me out and start over. Status in gnome-shell package in Ubuntu: Incomplete Bug description: After my system lock screen enables (whether through timeout or if I manually lock it), unlocking the system causes all programs to forcibly shut down and a new session to start. Effectively, I'm logging in fresh every time the lock screen is enabled. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gdm3 44.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu May 25 12:41:01 2023 InstallationDate: Installed on 2020-12-03 (902 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gdm3 UpgradeStatus: Upgraded to lunar on 2023-04-26 (28 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2020803/+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 1962327]
Also in Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 3070091c9eafc964ebb3f53d3b44124b40571fd8 CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1962327 Title: [Upstream] Vertical fraction feature present in font not applied by Writer Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Triaged Bug description: ~ $ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 ~$ apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:6.4.7-0ubuntu0.20.04.2 Candidate: 1:6.4.7-0ubuntu0.20.04.2 Version table: *** 1:6.4.7-0ubuntu0.20.04.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 1:6.4.2-0ubuntu3 500 500 http://in.archive.ubuntu.com/ubuntu focal/main amd64 Packages ~$ apt-show-versions -r libreoffice* liblibreofficekitgtk:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-base-core:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-calc:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-common:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-core:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-draw:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gnome:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gtk:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gtk2:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gtk3:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-impress:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-java-common:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-l10n-bn:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-math:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-style-colibre:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-style-elementary:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-style-tango:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-writer:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreofficekit-data:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate What is expected to happen in Writer is My font has vertical fraction look up for Bengali script. On selecting Format > Characters > CTL Font > Features Alternate (vertical) Fraction Feature is visible in options. Selecting the option should apply the feature on selected fraction see screenshot http://cloud.atipra.in/index.php/s/YosGiyFSoTQeW8i What happened instead is.. The feature is not applied, and the selected text is unchanged It should change as happens in firefox on selecting alternate (Vertical) fraction lookup in css see screenshot http://cloud.atipra.in/index.php/s/MxYbEisyFT3KnKT Extension installed : None ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-writer 1:6.4.7-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 20:33:24 2022 InstallationDate: Installed on 2020-01-03 (783 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: libreoffice UpgradeStatus: Upgraded to focal on 2021-09-16 (162 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1962327/+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 2017716] Re: Folders and files frequently need to be clicked twice
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2017716 Title: Folders and files frequently need to be clicked twice Status in nautilus package in Ubuntu: Confirmed Bug description: Nautilus randomly drops about half of my mouse clicks. Clicked folders or files will sometimes open at once, yet the next time(s) fail to respond until clicked a second time. I am seeing this both on X11 and on wayland. Single or double click policy does not make any difference. I have experimented with different mouse speeds but have not seen any noticeable difference. This behaviour is, in fact, something that I already noticed when I was trying out Ubuntu 22.10. It was enough to send me back to 22.04. I was really hoping that the issue would be solved by now, but clearly it is not. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 26 02:25:07 2023 InstallationDate: Installed on 2022-10-29 (178 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-04-12 (13 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 python3-nautilus 4.0-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2017716/+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 2017716] Re: Folders and files frequently need to be clicked twice
Maybe it's just this bug: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2816. ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #2816 https://gitlab.gnome.org/GNOME/nautilus/-/issues/2816 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2017716 Title: Folders and files frequently need to be clicked twice Status in nautilus package in Ubuntu: Confirmed Bug description: Nautilus randomly drops about half of my mouse clicks. Clicked folders or files will sometimes open at once, yet the next time(s) fail to respond until clicked a second time. I am seeing this both on X11 and on wayland. Single or double click policy does not make any difference. I have experimented with different mouse speeds but have not seen any noticeable difference. This behaviour is, in fact, something that I already noticed when I was trying out Ubuntu 22.10. It was enough to send me back to 22.04. I was really hoping that the issue would be solved by now, but clearly it is not. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 26 02:25:07 2023 InstallationDate: Installed on 2022-10-29 (178 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-04-12 (13 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 python3-nautilus 4.0-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2017716/+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 2018455] Re: gnome-shell exits after screen lock / unlock & login segfault libmutter-12.so.0.0.0 in Ubuntu 23.04 on Lenovo X1 Carbon Gen10
Exact the same problem on next gen of x1. Full-upgrade doesn't help. Lenovo ThinkPad X1 Carbon Gen 11 uname -a Linux x1g11-21HMCTO1WW 6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 6 07:48:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Same reproduction, same behavior, same logs. -- 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/2018455 Title: gnome-shell exits after screen lock / unlock & login segfault libmutter-12.so.0.0.0 in Ubuntu 23.04 on Lenovo X1 Carbon Gen10 Status in mutter package in Ubuntu: Incomplete Bug description: The issue is happening 9 out of 10 times. It is hard to get a crash dump in /var/crash during this error though, but I found one from few days ago. Looks like should be relevant. I've reported it, see OOPS ID: b68253a2-ea4c-11ed-af33-fa163e55efd0 Laptop: Lenovo ThinkPad X1 Carbon Gen 10, model 21CB007WCK root@x1:~# uname -a Linux x1 6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 6 07:48:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux To reproduce: 1. Win+L to lock the session 2. Screen turns black as expected 3. Login back to your session 4. Welcome to the new & clean session... all unsaved work is lost! 5. see gnome-shell segfault in libmutter-12.so in dmesg root@x1:~# dmesg -T |grep segf [Thu May 4 17:45:04 2023] gnome-shell[2554]: segfault at ff78 ip 7f3d10961115 sp 7ffd72b85f78 error 5 in libmutter-12.so.0.0.0[7f3d1084a000+13d000] likely on CPU 0 (core 0, socket 0) [Fri May 5 14:09:43 2023] gnome-shell[24568]: segfault at 11 ip 7f4c14161119 sp 7ffd4590de28 error 4 in libmutter-12.so.0.0.0[7f4c1404a000+13d000] likely on CPU 9 (core 17, socket 0) Logs from "ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash" command May 04 09:24:31 x1 systemd[1]: Started whoopsie.service - crash report submission. May 04 09:24:31 x1 whoopsie[54307]: [09:24:31] Using lock path: /var/lock/whoopsie/lock May 04 09:24:31 x1 whoopsie[54307]: [09:24:31] Parsing /var/crash/_usr_bin_gnome-shell.1000.crash. May 04 09:24:31 x1 whoopsie[54307]: [09:24:31] Uploading /var/crash/_usr_bin_gnome-shell.1000.crash. May 04 09:24:32 x1 whoopsie[54307]: [09:24:32] Sent; server replied with: No error May 04 09:24:32 x1 whoopsie[54307]: [09:24:32] Response code: 200 May 04 09:24:32 x1 whoopsie[54307]: [09:24:32] Reported OOPS ID b68253a2-ea4c-11ed-af33-fa163e55efd0 It was difficult to figure how to send the report in Ubuntu 23.04, previously it was just working... but with Ubuntu 23.04 there was this error: May 04 09:21:33 x1 systemd[1]: Starting apport-autoreport.service - Process error reports when automatic reporting is enabled... May 04 09:21:33 x1 systemd[1]: Started whoopsie.service - crash report submission. May 04 09:21:33 x1 whoopsie[53709]: [09:21:33] Using lock path: /var/lock/whoopsie/lock May 04 09:21:33 x1 systemd[1]: whoopsie.service: Deactivated successfully. May 04 09:21:33 x1 whoopsie-upload-all[53708]: ERROR: whoopsie.path is not enabled May 04 09:21:33 x1 systemd[1]: apport-autoreport.service: Main process exited, code=exited, status=1/FAILURE May 04 09:21:33 x1 systemd[1]: apport-autoreport.service: Failed with result 'exit-code'. May 04 09:21:33 x1 systemd[1]: Failed to start apport-autoreport.service - Process error reports when automatic reporting is enabled. Fixed by changing "Send error reports to Canonical" (in gnome control panel -> "Privacy" -> "Diagnostics") from "Automatic" to "Never" and re-running the `ubuntu-bug` command again. gnome-shell 44.0-2ubuntu3 intel-media-va-driver:amd64 23.1.2+dfsg1-1 root@x1:~# lshw -class display *-display description: VGA compatible controller product: Alder Lake-P Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 logical name: /dev/fb0 version: 0c width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb configuration: depth=32 driver=i915 latency=0 mode=1920x1200 resolution=1920,1200 visual=truecolor xres=1920 yres=1200 resources: iomemory:600-5ff iomemory:400-3ff irq:199 memory:603d00-603dff memory:40-400fff ioport:2000(size=64) memory:c-d memory:401000-4016ff memory:402000-40 root@x1:~# lshw -class multimedia *-multimedia:0 UNCLAIMED description: Multimedia controller product: Intel Corporation vendor: Intel Corporation physical id: 5 bus info: pci@:00:05.0 version: 02 width: 64 bits clock: 33MHz capabilities: pciexpress pm cap_list configuration: latency=0 resources: iomemory:600-5ff
[Desktop-packages] [Bug 1974293] Re: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl()
** Tags added: se-sponsor-dgadomski -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1974293 Title: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl() Status in gjs: Fix Released Status in OEM Priority Project: Confirmed Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Jammy: In Progress Status in gjs source package in Kinetic: Triaged Status in gjs source package in Lunar: Fix Released Status in gnome-shell package in Fedora: Confirmed Bug description: [ Impact ] gnome-shell often crashes on logout causing annoyance to the user as an error report dialog is displayed at the next login. [ Test Plan ] 1. Log into gnome-shell 2. Use gnome-shell for long enough to trigger a garbage collection cycle: Scroll the app grid and repeatedly open the calendar from the top bar for 30 seconds. 3. Log out. 4. Verify no new gnome-shell crash files appear in /var/crash/ [ Where problems could occur ] Only gnome-shell shutdown/logout is affected. [ Other Info ] https://errors.ubuntu.com/problem/256d1c0d1aad03bb024b525f4c80868e8f6a85b4 https://errors.ubuntu.com/problem/b1669e114babda005eb5a6414867a0eb7293f7e7 Description: Ubuntu 22.04 LTS Release: 22.04 ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 20 16:06:35 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1649813447 InstallationDate: Installed on 2022-05-05 (14 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/ubuntu RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libmozjs-91.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () Title: gnome-shell crashed with SIGSEGV in g_object_unref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1974293/+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 2006483] Re: Fails autopkgtests when tested against fuse3 >= 3.13
https://launchpad.net/ubuntu/+source/fuse3/3.14.0-2 ** Changed in: ostree (Ubuntu) Status: New => Fix Released ** Changed in: fuse3 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ostree in Ubuntu. https://bugs.launchpad.net/bugs/2006483 Title: Fails autopkgtests when tested against fuse3 >= 3.13 Status in fuse3 package in Ubuntu: Fix Released Status in ostree package in Ubuntu: Fix Released Status in fuse3 package in Debian: Fix Released Status in ostree package in Debian: Fix Released Bug description: The autopkgtest in `tests/test-rofiles-fuse.sh` (executed via `gnome- desktop-testing-runner libostree/test-rofiles-fuse.sh.test`) fails to execute `setfattr -n user.foo -v bar mnt/anewfile-for-fuse` with the error message "setfattr: mnt/anewfile-for-fuse: Numerical result out of range". It's unclear if this is related to glibc, FUSE_USE_VERSION, kernel fuse protocol or another component. On Debian this specific test is skipped, due to missing the "capsh" binary (libcap2-bin) in the test env: ``` /usr/libexec/installed-tests/libostree/libtest.sh: line 688: capsh: command not found 1..0 # SKIP No cap_sys_admin in bounding set, can't use FUSE ``` The relevant log (inside an Ubuntu autopkgtest qemu runner) is provided here: ``` $ ../tests/test-rofiles-fuse.sh Copying gpghome to /tmp/autopkgtest.Eaudsf/build.b3k/src/tmp4 checking for xattrs.../usr/bin/setfattr /tmp/autopkgtest.Eaudsf/build.b3k/src/tmp4 /tmp/autopkgtest.Eaudsf/build.b3k/src/tmp4 # testlabel.txt: security.selinux: No such attribute Unable to retrieve SELinux label, assuming disabled /tmp/autopkgtest.Eaudsf/build.b3k/src/tmp4 done checking for overlayfs whiteouts...done /usr/bin/setfattr d9793c4639f817fb95e3f1ae7a3f0571826db12a28baffaa3b3510f2ef0434a4 812152c68bb9c0b2a3bfcafeb5c4a4aa53827d8df5eeb755fe307f6a68f0febf fsck objects (20/20) [=] 100% object fsck of 2 commits completed successfully - no errors found. 1..12 a122802794e487785d14b58fe8969ab8716fd5c4c0ceed7de5c76061cd93f896 ok mount ok failed inplace mutation (open O_TRUNCATE) ok failed mutation chmod + chown setfattr: mnt/firstfile-link: Read-only file system ok new content setfattr: mnt/anewfile-for-fuse: Numerical result out of range Unexpected nonzero exit status 1 while running: setfattr -n user.foo -v bar mnt/anewfile-for-fuse gpg-connect-agent: no running gpg-agent - starting '/usr/bin/gpg-agent' gpg-connect-agent: waiting for the agent to come up ... (5s) gpg-connect-agent: connection to agent established OK closing connection ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fuse3/+bug/2006483/+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 2021418] Re: Incorrect response to mouse pointing
** 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/2021418 Title: Incorrect response to mouse pointing Status in xorg package in Ubuntu: New Bug description: I am using a high resolution screen and have AnyDesk installed. The program icon appears in the right corner of the screen next to the icons for the selected language in the system, network management, sound volume and system shutdown. All icons respond correctly to mouse pointing. Anomaly - clicking on the desktop under the icons in the small space below the top line, results in the appearance of the AnyDesk configuration window. This makes it impossible to click on the icons of other windows whose top right corner is directly below the top bar. For example, you cannot close the program window, minimize it, etc. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 28 13:55:38 2023 DistUpgraded: 2023-05-14 13:56:08,498 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2023-02-02 (114 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 0e0f:0008 VMware, Inc. Virtual Bluetooth Adapter Bus 001 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 001 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=ee607178-4028-4d20-91a5-41aa1cc72740 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-05-14 (13 days ago) dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A 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/ubuntu/+source/xorg/+bug/2021418/+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 1932537] Re: CUPS + SSSD: cannot access local CUPS web interface with domain user (apparmor problem)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1932537 Title: CUPS + SSSD: cannot access local CUPS web interface with domain user (apparmor problem) Status in apparmor package in Ubuntu: Confirmed Status in cups package in Ubuntu: Confirmed Bug description: [Summary] My domain user can not access the local CUPS web interface due to apparmor denials. Adding the following two lines to /etc/apparmor.d/local/usr.sbin.cupsd fixes it: /var/lib/sss/pipes/private/pam rw, unix (bind) type=dgram addr=@userdb-*, [Details] I have a (relatively) clean install of Ubuntu 20.04 (no upgrade), which is joined to a Windows AD-domain via sssd, but currently used off site with cached credentials. When I try to log in with my domain user (who is in the lpadmingroup) at the local cups web interface (localhost:631 ...> Add Printer) with the default apparmor config for cupsd I get a: AVC apparmor="DENIED" operation="connect" profile="/usr/sbin/cupsd" name="/var/lib/sss/pipes/private/pam" pid=189759 comm="cupsd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 This already existed in Bionic and my workaround was to add '/var/lib/sss/pipes/private/pam rw,' to /etc/apparmor.d/local/usr.sbin.cupsd and reload the profile: # echo '/var/lib/sss/pipes/private/pam rw,' > /etc/apparmor.d/local/usr.sbin.cupsd # apparmor_parser -r -W -T /etc/apparmor.d/usr.sbin.cupsd This worked in Bionic, but leads to a crash of cupsd in Focal when I try to log in as domain user with a the following log message nearby: AVC apparmor="DENIED" operation="bind" profile="/usr/sbin/cupsd" pid=189759 comm="cupsd" family="unix" sock_type="dgram" protocol=0 requested_mask="bind" denied_mask="bind" addr="@userdb-7625b1ef65396344ef05f0a8aeda870e" This looks very similar to https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1890858 , so I applied the same fix and added 'unix (bind) type=dgram addr=@userdb-*,' to /etc/apparmor.d/local/usr.sbin.cupsd: # echo 'unix (bind) type=dgram addr=@userdb-*,' >> /etc/apparmor.d/local/usr.sbin.cupsd # apparmor_parser -r -W -T /etc/apparmor.d/usr.sbin.cupsd Which fixed my problem. I am not an expert on apparmor, so I have no idea, if the first line gives too broad permissions. I think that there are two unrelated issues: 1) Cupsd cannot access sssd at all. This already existed in Bionic (but I failed to report the issue -- sorry for that). 2) Once the login succeeds, cups tries to resolve a uid/gid as it isn't known locally. To resolve it it needs to bind a unix socket. See: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1890858/comments/37 I will attach a full log with added comments on what I did. [Infos] 1) lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 2) apt-cache policy cups-daemon cups-daemon: Installiert: 2.3.1-9ubuntu1.1 Installationskandidat: 2.3.1-9ubuntu1.1 Versionstabelle: *** 2.3.1-9ubuntu1.1 500 500 http://ftp.uni-hannover.de/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://ftp.uni-hannover.de/ubuntu focal/main amd64 Packages 3) What you expected to happen: Be able to log in at the local cups web interface with my domain user, which is in the lpadmin group 4) What happened instead: Access was denied (asked again for my credentials) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1932537/+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 1932537] Re: CUPS + SSSD: cannot access local CUPS web interface with domain user (apparmor problem)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apparmor (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1932537 Title: CUPS + SSSD: cannot access local CUPS web interface with domain user (apparmor problem) Status in apparmor package in Ubuntu: Confirmed Status in cups package in Ubuntu: Confirmed Bug description: [Summary] My domain user can not access the local CUPS web interface due to apparmor denials. Adding the following two lines to /etc/apparmor.d/local/usr.sbin.cupsd fixes it: /var/lib/sss/pipes/private/pam rw, unix (bind) type=dgram addr=@userdb-*, [Details] I have a (relatively) clean install of Ubuntu 20.04 (no upgrade), which is joined to a Windows AD-domain via sssd, but currently used off site with cached credentials. When I try to log in with my domain user (who is in the lpadmingroup) at the local cups web interface (localhost:631 ...> Add Printer) with the default apparmor config for cupsd I get a: AVC apparmor="DENIED" operation="connect" profile="/usr/sbin/cupsd" name="/var/lib/sss/pipes/private/pam" pid=189759 comm="cupsd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 This already existed in Bionic and my workaround was to add '/var/lib/sss/pipes/private/pam rw,' to /etc/apparmor.d/local/usr.sbin.cupsd and reload the profile: # echo '/var/lib/sss/pipes/private/pam rw,' > /etc/apparmor.d/local/usr.sbin.cupsd # apparmor_parser -r -W -T /etc/apparmor.d/usr.sbin.cupsd This worked in Bionic, but leads to a crash of cupsd in Focal when I try to log in as domain user with a the following log message nearby: AVC apparmor="DENIED" operation="bind" profile="/usr/sbin/cupsd" pid=189759 comm="cupsd" family="unix" sock_type="dgram" protocol=0 requested_mask="bind" denied_mask="bind" addr="@userdb-7625b1ef65396344ef05f0a8aeda870e" This looks very similar to https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1890858 , so I applied the same fix and added 'unix (bind) type=dgram addr=@userdb-*,' to /etc/apparmor.d/local/usr.sbin.cupsd: # echo 'unix (bind) type=dgram addr=@userdb-*,' >> /etc/apparmor.d/local/usr.sbin.cupsd # apparmor_parser -r -W -T /etc/apparmor.d/usr.sbin.cupsd Which fixed my problem. I am not an expert on apparmor, so I have no idea, if the first line gives too broad permissions. I think that there are two unrelated issues: 1) Cupsd cannot access sssd at all. This already existed in Bionic (but I failed to report the issue -- sorry for that). 2) Once the login succeeds, cups tries to resolve a uid/gid as it isn't known locally. To resolve it it needs to bind a unix socket. See: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1890858/comments/37 I will attach a full log with added comments on what I did. [Infos] 1) lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 2) apt-cache policy cups-daemon cups-daemon: Installiert: 2.3.1-9ubuntu1.1 Installationskandidat: 2.3.1-9ubuntu1.1 Versionstabelle: *** 2.3.1-9ubuntu1.1 500 500 http://ftp.uni-hannover.de/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://ftp.uni-hannover.de/ubuntu focal/main amd64 Packages 3) What you expected to happen: Be able to log in at the local cups web interface with my domain user, which is in the lpadmin group 4) What happened instead: Access was denied (asked again for my credentials) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1932537/+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 2021412] [NEW] nautilus hang creating a folder
Public bug reported: created a folder in another folder, ok: the new folder appears in the window, try create a second folder nautilus hang. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: nautilus 1:44.1-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6 Uname: Linux 6.2.0-21-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun May 28 08:07:58 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1063, 761)' InstallationDate: Installed on 2023-05-21 (6 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230521) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.1-1ubuntu1 python3-nautilus 4.0-1build1 ** Affects: nautilus (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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2021412 Title: nautilus hang creating a folder Status in nautilus package in Ubuntu: New Bug description: created a folder in another folder, ok: the new folder appears in the window, try create a second folder nautilus hang. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: nautilus 1:44.1-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6 Uname: Linux 6.2.0-21-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun May 28 08:07:58 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1063, 761)' InstallationDate: Installed on 2023-05-21 (6 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230521) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.1-1ubuntu1 python3-nautilus 4.0-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2021412/+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
