[Desktop-packages] [Bug 2012832] Re: Xorg crashes on second and next unbind operations of Arc GPU
Please try a kernel version that is supported on Ubuntu 22.04, like 5.15.0-69.76, 5.19.0-38.39~22.04.1 or 6.1.0-1008.8 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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: Incomplete Status in xorg-server package in Ubuntu: Incomplete 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:
[Desktop-packages] [Bug 1553328] Re: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings
*** This bug is a duplicate of bug 1497593 *** https://bugs.launchpad.net/bugs/1497593 ** This bug has been marked a duplicate of bug 1497593 [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1553328 Title: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings Status in Canonical System Image: Triaged Status in Mesa: New Status in Mir: Triaged Status in Nouveau Xorg driver: Unknown Status in Unity System Compositor: Triaged Status in libdrm package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: In Progress Status in qtubuntu package in Ubuntu: In Progress Bug description: Unit8 froze up while I was trying to open system settings. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: unity8 8.11+16.04.20160216.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Fri Mar 4 19:12:54 2016 ExecutablePath: /usr/bin/unity8 InstallationDate: Installed on 2015-05-10 (299 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: unity8 SegvAnalysis: Segfault happened at: 0x7f58d568706c:mov0x8(%rsi),%edx PC (0x7f58d568706c) ok source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%edx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity8 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 Title: unity8 crashed with SIGSEGV UpgradeStatus: Upgraded to xenial on 2015-11-07 (118 days ago) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1553328/+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 1623507] Re: unity-system-compositor crashed with "Failed to schedule page flip", but only after nouveau crashed in glClear().
*** This bug is a duplicate of bug 1497593 *** https://bugs.launchpad.net/bugs/1497593 ** This bug is no longer a duplicate of bug 1553328 Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings ** This bug has been marked a duplicate of bug 1497593 [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1623507 Title: unity-system-compositor crashed with "Failed to schedule page flip", but only after nouveau crashed in glClear(). Status in Canonical System Image: New Status in Mir: Triaged Status in libdrm package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mir package in Ubuntu: Triaged Bug description: 16.10 first unity 8 run ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: unity-system-compositor 0.7.1+16.10.20160824-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Wed Sep 14 10:34:45 2016 ExecutablePath: /usr/sbin/unity-system-compositor GraphicsCard: Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1462:7817] NVIDIA Corporation G92 [GeForce 9800 GT] [10de:0614] (rev a2) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. G92 [GeForce 9800 GT] [3842:c988] InstallationDate: Installed on 2016-09-14 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160913) ProcCmdline: /usr/sbin/unity-system-compositor --disable-inactivity-policy=true --on-fatal-error-abort --file /run/mir_socket --from-dm-fd 11 --to-dm-fd 14 --vt 7 ProcEnviron: Signal: 6 SourcePackage: unity-system-compositor StacktraceTop: mir::fatal_error_abort(char const*, ...) () from /usr/lib/x86_64-linux-gnu/libmircommon.so.6 ?? () from /usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.10 ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41 ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Title: unity-system-compositor crashed with SIGABRT in mir::fatal_error_abort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: version.libdrm: libdrm2 2.4.70-1 version.lightdm: lightdm 1.19.4-0ubuntu1 version.mesa: libegl1-mesa-dev N/A To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623507/+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 1623508] Re: unity8 crashed with SIGSEGV
*** This bug is a duplicate of bug 1497593 *** https://bugs.launchpad.net/bugs/1497593 ** This bug is no longer a duplicate of bug 1553328 Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings ** This bug has been marked a duplicate of bug 1497593 [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1623508 Title: unity8 crashed with SIGSEGV Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu: New Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: 16.10 first unity 8 run16.10 first unity 8 run ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: unity8 8.14+16.10.20160831.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Wed Sep 14 10:32:07 2016 ExecutablePath: /usr/bin/unity8 InstallationDate: Installed on 2016-09-14 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160913) ProcCmdline: unity8 --mode=full-shell Signal: 11 SourcePackage: unity8 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 Title: unity8 crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1623508/+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 2008897] Re: Desktop freezes or crashes intermittently (amdgpu: [gfxhub] page fault)
"Fix Released" in lunar, assuming it is the above issue. If it's not then please just change the status back. ** Also affects: mesa via https://gitlab.freedesktop.org/mesa/mesa/-/issues/7504 Importance: Unknown Status: Unknown ** Changed in: mesa (Ubuntu) Status: New => Fix Released ** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2008897 Title: Desktop freezes or crashes intermittently (amdgpu: [gfxhub] page fault) Status in Mesa: Unknown Status in mesa package in Ubuntu: Fix Released Bug description: My desktop unexpectedly freezes or crashes every now and then (once or week or less). Typically the machine is not usable but this time I managed to log back in via the text console and grab the following text from dmesg: [11689.245277] gmc_v10_0_process_interrupt: 10 callbacks suppressed [11689.245284] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245291] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a01000 from client 0x1b (UTCL2) [11689.245294] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00301031 [11689.245296] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [11689.245298] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x1 [11689.245299] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x0 [11689.245301] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [11689.245302] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x0 [11689.245304] amdgpu :09:00.0: amdgpu: RW: 0x0 [11689.245308] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245311] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a0c000 from client 0x1b (UTCL2) [11689.245313] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00301031 [11689.245315] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [11689.245316] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x1 [11689.245318] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x0 [11689.245319] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [11689.245320] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x0 [11689.245322] amdgpu :09:00.0: amdgpu: RW: 0x0 [11689.245326] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245329] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a0b000 from client 0x1b (UTCL2) [11689.245331] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x [11689.245333] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0) [11689.245334] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x0 [11689.245336] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x0 [11689.245337] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [11689.245339] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x0 [11689.245340] amdgpu :09:00.0: amdgpu: RW: 0x0 [11689.245344] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245347] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a06000 from client 0x1b (UTCL2) [11689.245349] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x [11689.245350] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0) [11689.245351] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x0 [11689.245352] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x0 [11689.245354] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [11689.245355] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x0 [11689.245356] amdgpu :09:00.0: amdgpu: RW: 0x0 [11689.245360] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245362] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a0a000 from client 0x1b (UTCL2) [11689.245363] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x [11689.245364] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0) [11689.245366] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x0 [11689.245367] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x0 [11689.245368] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [11689.245369] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x0 [11689.245370] amdgpu :09:00.0: amdgpu:
[Desktop-packages] [Bug 2008897] Re: Desktop freezes or crashes intermittently (amdgpu: [gfxhub] page fault)
Looks most likely to be https://gitlab.freedesktop.org/mesa/mesa/-/issues/7504 which is fixed in Mesa 22.3.1. But then similar bugs still exist like bug 2012819. ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #7504 https://gitlab.freedesktop.org/mesa/mesa/-/issues/7504 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2008897 Title: Desktop freezes or crashes intermittently (amdgpu: [gfxhub] page fault) Status in Mesa: Unknown Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Fix Released Bug description: My desktop unexpectedly freezes or crashes every now and then (once or week or less). Typically the machine is not usable but this time I managed to log back in via the text console and grab the following text from dmesg: [11689.245277] gmc_v10_0_process_interrupt: 10 callbacks suppressed [11689.245284] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245291] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a01000 from client 0x1b (UTCL2) [11689.245294] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00301031 [11689.245296] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [11689.245298] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x1 [11689.245299] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x0 [11689.245301] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [11689.245302] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x0 [11689.245304] amdgpu :09:00.0: amdgpu: RW: 0x0 [11689.245308] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245311] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a0c000 from client 0x1b (UTCL2) [11689.245313] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00301031 [11689.245315] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [11689.245316] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x1 [11689.245318] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x0 [11689.245319] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [11689.245320] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x0 [11689.245322] amdgpu :09:00.0: amdgpu: RW: 0x0 [11689.245326] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245329] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a0b000 from client 0x1b (UTCL2) [11689.245331] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x [11689.245333] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0) [11689.245334] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x0 [11689.245336] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x0 [11689.245337] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [11689.245339] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x0 [11689.245340] amdgpu :09:00.0: amdgpu: RW: 0x0 [11689.245344] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245347] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a06000 from client 0x1b (UTCL2) [11689.245349] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x [11689.245350] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0) [11689.245351] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x0 [11689.245352] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x0 [11689.245354] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [11689.245355] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x0 [11689.245356] amdgpu :09:00.0: amdgpu: RW: 0x0 [11689.245360] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245362] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a0a000 from client 0x1b (UTCL2) [11689.245363] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x [11689.245364] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0) [11689.245366] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x0 [11689.245367] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x0 [11689.245368] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [11689.245369] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x0 [11689.245370] amdgpu :09:00.0: amdgpu: RW:
[Desktop-packages] [Bug 2008897] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2008897 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2008897 Title: Desktop freezes or crashes intermittently (amdgpu: [gfxhub] page fault) Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: New Bug description: My desktop unexpectedly freezes or crashes every now and then (once or week or less). Typically the machine is not usable but this time I managed to log back in via the text console and grab the following text from dmesg: [11689.245277] gmc_v10_0_process_interrupt: 10 callbacks suppressed [11689.245284] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245291] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a01000 from client 0x1b (UTCL2) [11689.245294] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00301031 [11689.245296] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [11689.245298] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x1 [11689.245299] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x0 [11689.245301] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [11689.245302] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x0 [11689.245304] amdgpu :09:00.0: amdgpu: RW: 0x0 [11689.245308] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245311] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a0c000 from client 0x1b (UTCL2) [11689.245313] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00301031 [11689.245315] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [11689.245316] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x1 [11689.245318] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x0 [11689.245319] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [11689.245320] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x0 [11689.245322] amdgpu :09:00.0: amdgpu: RW: 0x0 [11689.245326] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245329] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a0b000 from client 0x1b (UTCL2) [11689.245331] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x [11689.245333] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0) [11689.245334] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x0 [11689.245336] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x0 [11689.245337] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [11689.245339] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x0 [11689.245340] amdgpu :09:00.0: amdgpu: RW: 0x0 [11689.245344] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245347] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a06000 from client 0x1b (UTCL2) [11689.245349] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x [11689.245350] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0) [11689.245351] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x0 [11689.245352] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x0 [11689.245354] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [11689.245355] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x0 [11689.245356] amdgpu :09:00.0: amdgpu: RW: 0x0 [11689.245360] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245362] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a0a000 from client 0x1b (UTCL2) [11689.245363] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x [11689.245364] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0) [11689.245366] amdgpu :09:00.0: amdgpu:
[Desktop-packages] [Bug 2008897] Re: Desktop freezes or crashes intermittently (amdgpu: [gfxhub] page fault)
** Summary changed: - Desktop freezes or crashes intermittently + Desktop freezes or crashes intermittently (amdgpu: [gfxhub] page fault) ** Package changed: kwin (Ubuntu) => linux (Ubuntu) ** Tags added: amdgpu ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2008897 Title: Desktop freezes or crashes intermittently (amdgpu: [gfxhub] page fault) Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: New Bug description: My desktop unexpectedly freezes or crashes every now and then (once or week or less). Typically the machine is not usable but this time I managed to log back in via the text console and grab the following text from dmesg: [11689.245277] gmc_v10_0_process_interrupt: 10 callbacks suppressed [11689.245284] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245291] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a01000 from client 0x1b (UTCL2) [11689.245294] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00301031 [11689.245296] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [11689.245298] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x1 [11689.245299] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x0 [11689.245301] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [11689.245302] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x0 [11689.245304] amdgpu :09:00.0: amdgpu: RW: 0x0 [11689.245308] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245311] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a0c000 from client 0x1b (UTCL2) [11689.245313] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00301031 [11689.245315] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [11689.245316] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x1 [11689.245318] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x0 [11689.245319] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [11689.245320] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x0 [11689.245322] amdgpu :09:00.0: amdgpu: RW: 0x0 [11689.245326] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245329] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a0b000 from client 0x1b (UTCL2) [11689.245331] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x [11689.245333] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0) [11689.245334] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x0 [11689.245336] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x0 [11689.245337] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [11689.245339] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x0 [11689.245340] amdgpu :09:00.0: amdgpu: RW: 0x0 [11689.245344] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245347] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a06000 from client 0x1b (UTCL2) [11689.245349] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x [11689.245350] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0) [11689.245351] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x0 [11689.245352] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x0 [11689.245354] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [11689.245355] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x0 [11689.245356] amdgpu :09:00.0: amdgpu: RW: 0x0 [11689.245360] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245362] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a0a000 from client 0x1b (UTCL2) [11689.245363] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x [11689.245364] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0) [11689.245366] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x0 [11689.245367] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x0 [11689.245368] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [11689.245369] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x0 [11689.245370] amdgpu :09:00.0: amdgpu: RW: 0x0 [11689.245374] amdgpu
[Desktop-packages] [Bug 2003962] Re: [snap] Chromium update makes system unresponsive, black screen
[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.] ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2003962 Title: [snap] Chromium update makes system unresponsive, black screen Status in chromium-browser package in Ubuntu: Expired Bug description: Every day for the past few days I've been getting notification 'pending update of chromium snap (n) days left'. I noticed earlier that chromium seems to crash my system when it updates(at least it warns now so i can know it's doing it) - as in when i come back to log in after the update, to xorg/gnome, the caps lock doesn't turn on when pressed, and there's nothing but a black screen - ie the system is completely unresponsive. tried hitting magic Sysrq+i to no avail. Had to hard reboot the system with the power button. system was working just fine last night at 1030pm, so whatever happened had to be after then is what did it: I just got another one saying 13 days left. from kern.log Jan 26 02:38:38 eva kernel: [2487580.958314] loop20: detected capacity change from 0 to 303936 Jan 26 02:38:42 eva kernel: [2487585.064103] audit: type=1400 audit(1674722322.852:26188): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/snap/snapd/17950/usr/lib/snapd/snap-confine" pid=1586575 comm="apparmor_parser" Jan 26 02:38:42 eva kernel: [2487585.064110] audit: type=1400 audit(1674722322.852:26189): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/snap/snapd/17950/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=1586575 comm="apparmor_parser" Jan 26 02:38:43 eva kernel: [2487585.240118] audit: type=1400 audit(1674722323.028:26190): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.chromium.hook.configure" pid=1586580 comm="apparmor_parser" Jan 26 02:38:43 eva kernel: [2487585.933271] audit: type=1400 audit(1674722323.721:26191): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap-update-ns.chromium" pid=1586577 comm="apparmor_parser" Jan 26 02:38:43 eva kernel: [2487586.166852] audit: type=1400 audit(1674722323.955:26192): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.chromium.chromium" pid=1586579 comm="apparmor_parser" Jan 26 02:38:43 eva kernel: [2487586.192853] audit: type=1400 audit(1674722323.981:26193): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.chromium.chromedriver" pid=1586578 comm="apparmor_parser" Jan 26 02:38:44 eva kernel: [2487586.321626] audit: type=1400 audit(1674722324.110:26194): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap-update-ns.cups" pid=1586582 comm="apparmor_parser" Jan 26 02:38:44 eva kernel: [2487586.330187] audit: type=1400 audit(1674722324.118:26195): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.cups.cups-browsed" pid=1586585 comm="apparmor_parser" Jan 26 02:38:44 eva kernel: [2487586.330708] audit: type=1400 audit(1674722324.119:26196): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.cups.cancel" pid=1586584 comm="apparmor_parser" Jan 26 02:38:44 eva kernel: [2487586.336931] audit: type=1400 audit(1674722324.125:26197): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.cups.accept" pid=1586583 comm="apparmor_parser" nothing in syslog from 2:38am ubuntu 20.04 linux: custom kernel 6.0.7 with squashfs bug hotfix ( but it's been crashing during snap updates since at least the 5.x ) root@eva1:/var/log# apt-cache policy chromium-browser chromium-browser: Installed: 80.0.3987.163-0ubuntu1 Candidate: 80.0.3987.163-0ubuntu1 Version table: *** 80.0.3987.163-0ubuntu1 500 500 http://muug.ca/mirror/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status actual version post update: Version 109.0.5414.74 (Official Build) snap (64-bit) which is different than the last time I saw it ( 103.0.5060.134 ) so it's clearly updating itself, which supports the idea that the snap is updating during the crash but it would be nice to not hard lock my whole desktop system every 2 weeks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Uname: Linux 6.0.7-gnulibre-squashfix x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 26 09:44:00 2023
[Desktop-packages] [Bug 2008453] Re: Wrong trash icon at some scales
It's probably not worth fixing kinetic at this stage. It will be EOL in July. ** Also affects: yaru-theme (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: yaru-theme (Ubuntu Lunar) Importance: Medium Assignee: Paul (jupiter007) Status: Fix Released ** Changed in: yaru-theme (Ubuntu Kinetic) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/2008453 Title: Wrong trash icon at some scales Status in Yaru Theme: Unknown Status in yaru-theme package in Ubuntu: Fix Released Status in yaru-theme source package in Kinetic: Won't Fix Status in yaru-theme source package in Lunar: Fix Released Bug description: The trash icon changes from Yaru theme to the default blue icon at some scales. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell-extension-desktop-icons-ng 46+really47.0.2-2 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 Uname: Linux 5.19.0-28-generic x86_64 ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Feb 24 14:47:25 2023 InstallationDate: Installed on 2022-11-28 (87 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons-ng UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/2008453/+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 2012733] Re: Unthemed and unscaled titlebars for server-side decorations in GNOME 44 Xorg sessions
** Bug watch added: github.com/ubuntu/yaru/issues #3876 https://github.com/ubuntu/yaru/issues/3876 ** Also affects: yaru via https://github.com/ubuntu/yaru/issues/3876 Importance: Unknown Status: Unknown -- 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/2012733 Title: Unthemed and unscaled titlebars for server-side decorations in GNOME 44 Xorg sessions Status in Yaru Theme: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Confirmed Bug description: Hi, Nvidia 530 (graphics ppa), dGPU mode, GS 44, Lunar X1 session: If I launch Synaptic or ChessX, eg., the title bar is Adwaita-styled (greyish + icons). No issue with GNOME apps (and some other like FF or TB snaps, etc.). Wayland session: all is ok (except many other bugs!) To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/2012733/+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 2012973] Re: Trash icon changes when reducing size
*** This bug is a duplicate of bug 2008453 *** https://bugs.launchpad.net/bugs/2008453 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2008453, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 2008453 Wrong trash icon at some scales ** Also affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** No longer affects: gnome-shell-extension-ubuntu-dock (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2012973 Title: Trash icon changes when reducing size Status in Yaru Theme: New Status in yaru-theme package in Ubuntu: New Bug description: Ubuntu 22.10 When changing the size of the Ubuntu dock icons to any value between 34 and 44 it changes the trash icon changes from the regular Ubuntu trash icon to a different (blueish) icon. I would expect the icon to remain the same and only reduce its size. Before noticing this issue I installed the regular GNOME dash to dock extension but I removed it again, reinstalled the package gnome-shell- extension-ubuntu-dock and also reset dock settings with dconf reset -f /org/gnome/shell/extensions/dash-to-dock/. Also I tried updating icon cache with sudo update-icon-caches /usr/share/icons/*. I am not sure if the issue existed before installing dash to dock. I am using a HighDPI screen in case this has something to do with the issue. I am not seeing this problem on my desktop computer without HighDPI but I also didn't install dash to dock there. I am running Wayland. Any idea what else I could try to reset? ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell-extension-ubuntu-dock 74ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 21:01:30 2023 InstallationDate: Installed on 2023-03-05 (22 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash 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/yaru/+bug/2012973/+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 2009767] Re: External HDMI monitor is laggy on NVIDIA-525 reverse PRIME system
** No longer affects: xorg-server (Ubuntu Jammy) ** Also affects: xorg-server (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-525 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu Jammy) Status: New => Confirmed ** Changed in: xorg-server (Ubuntu Jammy) Importance: Undecided => High -- 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/2009767 Title: External HDMI monitor is laggy on NVIDIA-525 reverse PRIME system Status in OEM Priority Project: New Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 source package in Jammy: New Status in xorg-server source package in Jammy: Confirmed Status in nvidia-graphics-drivers-525 source package in Kinetic: Confirmed Status in xorg-server source package in Kinetic: Fix Released Bug description: [Summary] When the graphic mode is on-demand mode and plug in the monitor to HDMI port, there are two issue occures: 1. External monitor's screen is very laggy in external monitor mode only. 2. External monitor's screen sometimes (~50%) will be blak in join display mode. [Steps to reproduce] 1. Boot in OS 2. Plug in the external monitor in HDMI port 3. Find the cursor moving in external monitor is laggy [Workaround] Downgrade to NVIDIA driver 515. [Additional information] Feedback from NV: An NVIDIA driver built with the features needed to get rid of the laggy monitor problem causes Xorg 1.21.1.3 to crash. There's a patch for Xorg to fix the crash (https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275) and it was first included in the 1.21.1.4 release. Since the older X servers crash, NVIDIA deliberately does a version check in the driver and enables these features for Xorg servers that are known to work, i.e. 1.21.1.4 or higher. This unfortunately prevents backporting the fix to 1.21.1.3. Engineering has chosen this approach since a crash is worse than the low FPS lag and the user might lose work merely by plugging/unplugging displays. If it was about a performance degradation, slight corruption, or something non-fatal, we wouldn't need to check Xorg version To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2009767/+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 1961508] Re: Dock displaying over window after resuming from blank screen
** Tags added: lunar -- 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/1961508 Title: Dock displaying over window after resuming from blank screen Status in Dash to dock: Unknown Status in Mutter: New Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in gnome-desktop package in Fedora: Confirmed Bug description: I have Blank Screen set to happen after 2 minutes of inactivity. When resuming from a Blank Screen (by moving the mouse or touching the keyboard), the Dock is displayed over the top of the current program. To get it back to normal I need to click "Restore Down" on the current programs window and then "Maximize" so that the Dock no longer overlaps it. (Note: I have Auto-hide dock turned off.) This only happens sometimes. I can't reproduce the bug it every time. - 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu - Ubuntu 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center - Not sure (I guess the Dock is part of the Gnome interface?) 3) What you expected to happen - Dock should not overlap the current program on resume from screen blank. 4) What happened instead - The Dock overlaps the current program on resume from screen blank. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2022-02-18 (24 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell-extension-ubuntu-dock PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 Tags: wayland-session impish Uname: Linux 5.13.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-02-18 (328 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 43.0-1ubuntu4 Tags: wayland-session third-party-packages kinetic Uname: Linux 5.19.0-28-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-25 (79 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+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 2006044] Re: Cursor becomes separated from window when unmaximizing via mouse drag
Now tracking in https://gitlab.gnome.org/GNOME/mutter/-/issues/2730 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2730 https://gitlab.gnome.org/GNOME/mutter/-/issues/2730 ** Project changed: gnome-shell => mutter ** Changed in: mutter Remote watch: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4006 => gitlab.gnome.org/GNOME/mutter/-/issues #2730 -- 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/2006044 Title: Cursor becomes separated from window when unmaximizing via mouse drag Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: Processor: Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz Architecture: x86_64 Address sizes: 36 bits physical, 48 bits virtual CPU(s): 4 On-line CPU(s) list: 0-3 Vendor ID: GenuineIntel Model name: Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz CPU family: 6 Core(s) per socket: 4 Socket(s): 1 Virtualization: VT-x --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: sddm DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2023-01-24 (12 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Package: gnome-shell 43.1-0ubuntu1 PackageArchitecture: amd64 RelatedPackageVersions: mutter-common 43.0-1ubuntu4 Tags: kinetic Uname: Linux 6.1.9-060109-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2006044/+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 1961508] Re: Dock displaying over window after resuming from blank screen
** Tags added: rls-ll-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1961508 Title: Dock displaying over window after resuming from blank screen Status in Dash to dock: Unknown Status in Mutter: New Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in gnome-desktop package in Fedora: Confirmed Bug description: I have Blank Screen set to happen after 2 minutes of inactivity. When resuming from a Blank Screen (by moving the mouse or touching the keyboard), the Dock is displayed over the top of the current program. To get it back to normal I need to click "Restore Down" on the current programs window and then "Maximize" so that the Dock no longer overlaps it. (Note: I have Auto-hide dock turned off.) This only happens sometimes. I can't reproduce the bug it every time. - 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu - Ubuntu 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center - Not sure (I guess the Dock is part of the Gnome interface?) 3) What you expected to happen - Dock should not overlap the current program on resume from screen blank. 4) What happened instead - The Dock overlaps the current program on resume from screen blank. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2022-02-18 (24 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell-extension-ubuntu-dock PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 Tags: wayland-session impish Uname: Linux 5.13.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-02-18 (328 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 43.0-1ubuntu4 Tags: wayland-session third-party-packages kinetic Uname: Linux 5.19.0-28-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-25 (79 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+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 1966905] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from free_fetch_user_request() [accountsservice]
** Tags added: fixed-in-accountsservice-23.12ish fixed-upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1966905 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from free_fetch_user_request() [accountsservice] Status in accountsservice: New Status in gnome-control-center: Unknown Status in accountsservice package in Ubuntu: Fix Committed Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Triaged Bug description: This is now the #1 gnome-shell crasher in Ubuntu 23.04. https://errors.ubuntu.com/problem/d85747462e756cb405d1e87b9c59b0b995a7d394 https://errors.ubuntu.com/problem/1674bdbf40a28b5f59067ffde832ba508ecba114 Valgrind memory errors in gnome-shell 42 from accountsservice: ==60511== Invalid read of size 8 ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120) ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417) ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557) ==60511==by 0x1E428ECA: _act_user_update_from_object_path (act-user.c:1346) ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511== Block was alloc'd at ==60511==at 0x4848899: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4DA5718: g_malloc (gmem.c:125) ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072) ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098) ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911) ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011) ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181) ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821) ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706) ==60511==by 0x1E429BD8: act_user_manager_get_user (act-user-manager.c:1879) ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511== ==60511== Invalid read of size 8 ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a (gtype.c:4091) ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982) ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C:
[Desktop-packages] [Bug 2012832] Re: Xorg crashes on second and next unbind operations of Arc GPU
Or maybe I just have to wait until linux 6.4: https://www.phoronix.com/news/Intel-Linux-6.4-More-GT-Next -- 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 xorg-server package in Ubuntu: Incomplete 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/xorg-server/+bug/2012832/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 2012996] [NEW] Editing device name doesn't cancel when pressing escape
Public bug reported: The device name in the Sharing or About panels can be changed by clicking the icon to the right of the name (see screenshot). Pressing escape doesn't cancel the edit and re-show this icon. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: rls-ll-incoming ** Attachment added: "Screenshot of device name widget" https://bugs.launchpad.net/bugs/2012996/+attachment/5658049/+files/Screenshot%20from%202023-03-28%2014-46-06.png -- 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/2012996 Title: Editing device name doesn't cancel when pressing escape Status in gnome-control-center package in Ubuntu: New Bug description: The device name in the Sharing or About panels can be changed by clicking the icon to the right of the name (see screenshot). Pressing escape doesn't cancel the edit and re-show this icon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2012996/+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 2012994] [NEW] Automatic Date & Time switch shows as insensitive when enabled
Public bug reported: Go to Settings > Date & Time and toggle the "Automatic Date & Time" switch. When enabled it shows as insensitive (i.e. grey instead of orange). The "Automatic Time Zone" switch below behaves as expected. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: rls-ll-incoming ** Attachment added: "Screenshot showing automatic date & time enabled with insensitive switch" https://bugs.launchpad.net/bugs/2012994/+attachment/5658048/+files/Screenshot%20from%202023-03-28%2014-41-08.png -- 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/2012994 Title: Automatic Date & Time switch shows as insensitive when enabled Status in gnome-control-center package in Ubuntu: New Bug description: Go to Settings > Date & Time and toggle the "Automatic Date & Time" switch. When enabled it shows as insensitive (i.e. grey instead of orange). The "Automatic Time Zone" switch below behaves as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2012994/+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
Ok, looks like I see what's happening: 1. I boot the laptop after cold-reboot and it crashes during xorg startup and shows on VT: i915 :04:00.0: [drm] *ERROR* Writing dc state to 0x1 failed, now 0x0 i915 :04:00.0: [drm] *ERROR* DC state mismatch (0x1 -> 0x0) 2. It starts in 5sec-1min up and shows the login screen, then I login and send this first crash: https://errors.ubuntu.com/oops/ea15e7a0-cd06-11ed-9fcb-fa163e993415 (~300KB) 3. Now I executing sequentially the steps to unbind, then bind, then unbind - and it crashes again. 4. I login back and sending this bigger crash log: https://errors.ubuntu.com/oops/a797a552-cd07-11ed-b9a4-fa163ef35206 (~6MB) Now I can find the X crash "Backtrace" in the last crash: [98.987] (EE) Backtrace: [98.987] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x5610ac7d2809] [98.988] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f36ec042520] [98.990] (EE) 2: ? (?+0x0) [0x0] [98.990] (EE) [98.990] (EE) Segmentation fault at address 0x0 So I hope it is the one you look for - or I can try to find something else, just describe which additional info I need to look for and I will do that) Maybe journalctl logs or something else? Thank you -- 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 xorg-server package in Ubuntu: Incomplete 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:
[Desktop-packages] [Bug 2012691] Re: Triple buffering is missing/disabled in lunar
It's in proposed, not released yet. ** Changed in: mutter (Ubuntu) Status: Fix Released => Fix Committed -- 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/2012691 Title: Triple buffering is missing/disabled in lunar Status in mutter package in Ubuntu: Fix Committed Bug description: Triple buffering is missing/disabled in lunar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2012691/+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 2012991] Re: Insensitive items in system tray menus not visible
Changing the theme to dark makes the text visible. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2012991 Title: Insensitive items in system tray menus not visible Status in gnome-shell-extension-appindicator package in Ubuntu: New Bug description: If you use the multicast system tray menu the text on the items that are insensitive aren't visible. It appears they have the same colour as the background. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2012991/+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 2012991] [NEW] Insensitive items in system tray menus not visible
Public bug reported: If you use the multicast system tray menu the text on the items that are insensitive aren't visible. It appears they have the same colour as the background. ** Affects: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided Status: New ** Tags: rls-ll-incoming ** Attachment added: "Screenshot of multipass system tray menu" https://bugs.launchpad.net/bugs/2012991/+attachment/5658046/+files/Screenshot%20from%202023-03-28%2014-11-35.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2012991 Title: Insensitive items in system tray menus not visible Status in gnome-shell-extension-appindicator package in Ubuntu: New Bug description: If you use the multicast system tray menu the text on the items that are insensitive aren't visible. It appears they have the same colour as the background. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2012991/+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 1788420] Re: Don't update netpbm-free to 2:10.78.05-0.1 for now
** Changed in: netpbm-free (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to netpbm-free in Ubuntu. https://bugs.launchpad.net/bugs/1788420 Title: Don't update netpbm-free to 2:10.78.05-0.1 for now Status in netpbm-free package in Ubuntu: Fix Released Status in netpbm-free package in Debian: New Status in netpbm-free package in Fedora: Fix Released Bug description: The new version is in Debian/experimental but has a soname change and require a transition. Unless we find a good reason to want to it now that's probably not for eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netpbm-free/+bug/1788420/+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 1917052] Re: Don't update giflib to newer versions for now
** Changed in: giflib (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to giflib in Ubuntu. https://bugs.launchpad.net/bugs/1917052 Title: Don't update giflib to newer versions for now Status in giflib package in Ubuntu: Fix Released Bug description: There is an ABI incompatible change in the new version https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935088 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/giflib/+bug/1917052/+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 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
@ BloodyIron It looks like the problem you are experiencing is the same issue as I have had. I think the reason that it works after you kill gvfsd-smb-browse is that your FreeNAS server is advertising itself via mDNS, and gvfsd will see that. You don't need SMB1 or WSDD for gvfsd to discover your NAS. But it is also looking for a "Windows Network" (i.e. the Windows "network neighborhood" or workgroup that shows up as a separate subfolder) using SMB1, and that fails if the server does not provide SMB1. Crucially, however, it fails in a way that leaves the gvfsd-smb-browse process in a bad state where it fails to allow browsing of the server even though it has been discovered via mDNS. I encourage you to take a look at my patch, or to use the PPA at https://launchpad.net/~wmaddox3rd/+archive/ubuntu/gvfs-smb-sharelist- patch. It does indeed look like there is a bug here in that attempting discovery via SMB1 somehow breaks browsing of the server discovered via mDNS. See also my remarks here: https://gitlab.gnome.org/GNOME/gvfs/-/issues/307#note_1632096 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 Status in gvfs: New Status in gvfs package in Ubuntu: Triaged Bug description: After bug #1778322 is fixed (just needs a gvfs rebuild with newer samba), samba machines will start to show up again in the "windows network" tab in nautilus. But if a server has disabled the SMB1 protocol, nautilus will show an error when that server is clicked on, instead of showing the shares list. Even with SMB1 disabled, it should still be technically possible to get a share list, since smbclient can do it: andreas@nsnx:~$ nmblookup -A 192.168.122.101 Looking up status of 192.168.122.101 D-NO-SMB1 <00> - B D-NO-SMB1 <03> - B D-NO-SMB1 <20> - B ..__MSBROWSE__. <01> - B WORKGROUP <00> - B WORKGROUP <1d> - B WORKGROUP <1e> - B MAC Address = 00-00-00-00-00-00 andreas@nsnx:~$ smbclient -L 192.168.122.101 -N WARNING: The "syslog" option is deprecated Sharename Type Comment - --- print$ Disk Printer Drivers pub_no_smb1 Disk IPC$IPC IPC Service (d-no-smb1 server (Samba, Ubuntu)) Reconnecting with SMB1 for workgroup listing. protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE Failed to connect with SMB1 -- no workgroup available andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m NT1 WARNING: The "syslog" option is deprecated protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m SMB2 WARNING: The "syslog" option is deprecated Try "help" to get a list of possible commands. smb: \> dir . D0 Fri May 3 18:16:38 2019 .. D0 Fri May 3 18:15:24 2019 hello.txt N 21 Fri May 3 18:16:12 2019 hello-from-nsnx.txt A9 Fri May 3 18:16:38 2019 20509264 blocks of size 1024. 13121800 blocks available To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+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 2009354] Update Released
The verification of the Stable Release Update for libreoffice has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2009354 Title: [SRU] libreoffice 7.4.6 for kinetic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Kinetic: Fix Released Bug description: [Impact] * LibreOffice 7.4.6 is in its sixth bugfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.6_release * Version 7.4.4 is currently released in kinetic. For a list of fixed bugs compared to 7.4.5 see the list of bugs fixed in the release candidates of 7.4.6 (that's a total of 74 bugs): https://wiki.documentfoundation.org/Releases/7.4.6/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.4.6/RC2#List_of_fixed_bugs * 7.4.5 was an intermediate hotfix release with one bug fix which got cherry-picked as 1:7.4.4-0ubuntu0.22.10.2 * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_74/1717/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/amd64/libr/libreoffice/20230308_174140_556be@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/arm64/libr/libreoffice/20230308_194429_0c8b8@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/armhf/libr/libreoffice/20230308_202215_690b5@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/ppc64el/libr/libreoffice/20230308_174403_74fe7@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/s390x/libr/libreoffice/20230308_200234_9c534@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 74 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2009354/+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 2009354] Re: [SRU] libreoffice 7.4.6 for kinetic
This bug was fixed in the package libreoffice - 1:7.4.6-0ubuntu0.22.10.1
---
libreoffice (1:7.4.6-0ubuntu0.22.10.1) kinetic; urgency=medium
* New upstream release (LP: #2009354)
[ Rico Tzschichholz ]
* Drop upstreamed patches
- debian/patches/tdf153059-after-ChangeHeaderOrFooter-the-c.patch
* debian/rules:
- Disable make check on s390x (builders failing without a log),
the autopkgtests are still providing runtime checks
* debian/control{.in}:
- Add missing Breaks on -core-nogui in -common
* tests/patches/s390x-skip-tests.diff:
- Skip four more failing tests on s390x
[ Rene Engelhard ]
* debian/rules: Use system-lockfile; lockfile is actually built during the
build in non-cross builds
* debian/rules: also add forgotten DEB_LDFLAGS_MAINT_STRIP for -flto=auto
and (if using "small symbols" anyway -ffat-lto-objects)
* debian/rules:
- set extra builid to BINARY_VERSION instead of DEB_VERSION to reflect
the actual binary package version of libreoffice-core if they differed
* debian/rules:
- Do not add documentation symlinks when not building documentation
-- Rico Tzschichholz Wed, 08 Mar 2023 17:34:09
+0100
** Changed in: libreoffice (Ubuntu Kinetic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/2009354
Title:
[SRU] libreoffice 7.4.6 for kinetic
Status in libreoffice package in Ubuntu:
Fix Released
Status in libreoffice source package in Kinetic:
Fix Released
Bug description:
[Impact]
* LibreOffice 7.4.6 is in its sixth bugfix release of the 7.4 line:
https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.6_release
* Version 7.4.4 is currently released in kinetic. For a list of fixed bugs
compared to 7.4.5 see the list of bugs fixed in the release candidates of 7.4.6
(that's a total of 74 bugs):
https://wiki.documentfoundation.org/Releases/7.4.6/RC1#List_of_fixed_bugs
https://wiki.documentfoundation.org/Releases/7.4.6/RC2#List_of_fixed_bugs
* 7.4.5 was an intermediate hotfix release with one bug fix which got
cherry-picked as 1:7.4.4-0ubuntu0.22.10.2
* Given the nature of the project, the complexity of the codebase and
the high level of quality assurance upstream, it is preferable to SRU
a minor release rather than cherry-pick selected bug fixes.
[Testing]
* Upstream testing. Bugs fixed upstream typically include
unit/regression tests, and the release itself is extensively exercised
(both in an automated manner and manually).
* A recent set of upstream's automated jenkins testing can be found here:
https://ci.libreoffice.org/job/gerrit_74/1717/
* More information about the upstream QA testing can be found here:
* Automated tests
https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
* Automated UI tests
https://wiki.documentfoundation.org/Development/UITests
* Regression tests
https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
* Feature tests
https://wiki.documentfoundation.org/QA/Testing/Feature_Tests
* Launchpad testing. The libreoffice packages include autopkgtests that were
run and verified as passing.
* [amd64]
https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/amd64/libr/libreoffice/20230308_174140_556be@/log.gz
* [arm64]
https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/arm64/libr/libreoffice/20230308_194429_0c8b8@/log.gz
* [armhf]
https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/armhf/libr/libreoffice/20230308_202215_690b5@/log.gz
* [ppc64el]
https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/ppc64el/libr/libreoffice/20230308_174403_74fe7@/log.gz
* [s390x]
https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/s390x/libr/libreoffice/20230308_200234_9c534@/log.gz
* General smoke testing of all the applications in the office suite were
carried out by going through the manual testplan as documented by:
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice
[Regression Potential]
* A minor release with a total of 74 bug fixes always carries the
potential for introducing regressions, even though it is a bugfix-only
release, meaning that no new features were added, and no existing
features were removed.
* A combination of autopkgtests and careful smoke testing as
described above should provide reasonable confidence that no
regressions sneaked in.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2009354/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe :
[Desktop-packages] [Bug 2011806] Re: [lunar] Snaps don't launch due to cgroup issue
** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed -- 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/2011806 Title: [lunar] Snaps don't launch due to cgroup issue Status in gnome-shell package in Ubuntu: Fix Committed Status in kio package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: Hi, Lunar up to date, Intel+Nvidia GPUs, Ubuntu Wayland or X11 session, hybrid or discrete graphics. If I click on a snap dash icon, nothing happens. Tested with Thunderbird, Firefox, Shortwave... (VS Code seems ok, maybe due to classic confinment?) I can launch without issue Chrome (deb), Synaptic, GNOME apps, etc. Recent updates included gnome-shell and libadwaita. --- I get this type of log for all problematic snaps: /user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome- shortwave_shortwave-11885.scope is not a snap cgroup --- Context: $ snap --version snap2.58.3+23.04ubuntu1 snapd 2.58.3+23.04ubuntu1 series 16 ubuntu 23.04 kernel 6.1.0-16-generic $ snap list Nom Version Révision Suivi Éditeur Notes bare 1.0 5 latest/stable canonical✓base code ee2b180d122 latest/stable vscode✓ classic core 16-2.58.2 14784 latest/stable canonical✓core core18202303082714 latest/stable canonical✓base core20202302071828 latest/stable canonical✓base core2220230210522 latest/stable canonical✓base firefox 111.0-2 2432 latest/candidate mozilla✓ - gimp 2.10.30 393 latest/stable snapcrafters - gnome-3-28-1804 3.28.0-19-g98f9e67.98f9e67 161 latest/stable canonical✓- gnome-3-38-2004 0+git.6f39565 119 latest/stable canonical✓- gnome-42-2204 0+git.09673a5 65 latest/stable canonical✓- gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓- gtk-theme-pocillo 0.14.4.15 latest/stable ubuntubudgie - gtk-theme-qogirbudgie 22.04.1 8 latest/stable ubuntubudgie - gtk2-common-themes0.1 13 latest/stable canonical✓- hunspell-dictionaries-1-7-20041.7-20.04+pkg-6fd6 2 latest/stable brlin - kde-frameworks-5-91-qt-5-15-3-core20 5.91.0 1 latest/stable kde✓ - kde-frameworks-5-99-qt-5-15-7-core20 5.99.0 15 latest/stable kde✓ - kde-frameworks-5-core18 5.67.0 35 latest/stable kde✓ - libreoffice 7.5.1.2 270 latest/stable canonical✓- shortwave 3.0.0 79 latest/stable alexmurray✪ - snapd 2.58.2 18357 latest/stable canonical✓snapd snapd-desktop-integration 0.1 71 latest/stable/… canonical✓- stellarium-daily v1.21396 latest/stable t4saha- thunderbird 102.9.0-1 305 latest/candidate canonical✓- vlc 3.0.18 3078 latest/stable videolan✓ - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011806/+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 2012691] Re: Triple buffering is missing/disabled in lunar
Manually closing. https://launchpad.net/ubuntu/+source/mutter/44.0-2ubuntu2 https://launchpad.net/ubuntu/+source/mutter/44.0-2ubuntu1 ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Released -- 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/2012691 Title: Triple buffering is missing/disabled in lunar Status in mutter package in Ubuntu: Fix Released Bug description: Triple buffering is missing/disabled in lunar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2012691/+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 1966905] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from free_fetch_user_request() [accountsservice]
** Changed in: accountsservice (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1966905 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from free_fetch_user_request() [accountsservice] Status in accountsservice: New Status in gnome-control-center: Unknown Status in accountsservice package in Ubuntu: Fix Committed Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Triaged Bug description: This is now the #1 gnome-shell crasher in Ubuntu 23.04. https://errors.ubuntu.com/problem/d85747462e756cb405d1e87b9c59b0b995a7d394 https://errors.ubuntu.com/problem/1674bdbf40a28b5f59067ffde832ba508ecba114 Valgrind memory errors in gnome-shell 42 from accountsservice: ==60511== Invalid read of size 8 ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120) ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417) ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557) ==60511==by 0x1E428ECA: _act_user_update_from_object_path (act-user.c:1346) ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511== Block was alloc'd at ==60511==at 0x4848899: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4DA5718: g_malloc (gmem.c:125) ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072) ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098) ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911) ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011) ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181) ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821) ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706) ==60511==by 0x1E429BD8: act_user_manager_get_user (act-user-manager.c:1879) ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511== ==60511== Invalid read of size 8 ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a (gtype.c:4091) ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982) ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C:
[Desktop-packages] [Bug 2012978] Re: Memory leak
the cmd: gnome-extensions list --enabled shows: ubuntu-appindicat...@ubuntu.com ubuntu-d...@ubuntu.com d...@rastersoft.com disabling extensions does not make effects -- 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/2012978 Title: Memory leak Status in gnome-shell package in Ubuntu: New Bug description: High Memory Usage 3.1gb in 2h after reboot ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 Uname: Linux 6.2.8-060208-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 22:46:07 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-25 (366 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-09-03 (205 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012978/+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 2012978] [NEW] Memory leak
Public bug reported: High Memory Usage 3.1gb in 2h after reboot ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 Uname: Linux 6.2.8-060208-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 22:46:07 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-25 (366 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-09-03 (205 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy 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/2012978 Title: Memory leak Status in gnome-shell package in Ubuntu: New Bug description: High Memory Usage 3.1gb in 2h after reboot ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 Uname: Linux 6.2.8-060208-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 22:46:07 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-25 (366 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-09-03 (205 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012978/+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 2012973] Re: Trash icon changes when reducing size
Seems to have been fixed lately in Yaru: https://git.launchpad.net/ubuntu/+source/yaru- theme/commit/icons/Yaru/256x256/places. -- 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/2012973 Title: Trash icon changes when reducing size Status in Yaru Theme: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Ubuntu 22.10 When changing the size of the Ubuntu dock icons to any value between 34 and 44 it changes the trash icon changes from the regular Ubuntu trash icon to a different (blueish) icon. I would expect the icon to remain the same and only reduce its size. Before noticing this issue I installed the regular GNOME dash to dock extension but I removed it again, reinstalled the package gnome-shell- extension-ubuntu-dock and also reset dock settings with dconf reset -f /org/gnome/shell/extensions/dash-to-dock/. Also I tried updating icon cache with sudo update-icon-caches /usr/share/icons/*. I am not sure if the issue existed before installing dash to dock. I am using a HighDPI screen in case this has something to do with the issue. I am not seeing this problem on my desktop computer without HighDPI but I also didn't install dash to dock there. I am running Wayland. Any idea what else I could try to reset? ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell-extension-ubuntu-dock 74ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 21:01:30 2023 InstallationDate: Installed on 2023-03-05 (22 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash 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/yaru/+bug/2012973/+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 2012973] Re: Trash icon changes when reducing size
Found this on AskUbuntu: https://askubuntu.com/questions/1440136/new- blue-trash-icon-in-22-10 ** Also affects: yaru Importance: Undecided Status: New -- 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/2012973 Title: Trash icon changes when reducing size Status in Yaru Theme: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Ubuntu 22.10 When changing the size of the Ubuntu dock icons to any value between 34 and 44 it changes the trash icon changes from the regular Ubuntu trash icon to a different (blueish) icon. I would expect the icon to remain the same and only reduce its size. Before noticing this issue I installed the regular GNOME dash to dock extension but I removed it again, reinstalled the package gnome-shell- extension-ubuntu-dock and also reset dock settings with dconf reset -f /org/gnome/shell/extensions/dash-to-dock/. Also I tried updating icon cache with sudo update-icon-caches /usr/share/icons/*. I am not sure if the issue existed before installing dash to dock. I am using a HighDPI screen in case this has something to do with the issue. I am not seeing this problem on my desktop computer without HighDPI but I also didn't install dash to dock there. I am running Wayland. Any idea what else I could try to reset? ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell-extension-ubuntu-dock 74ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 21:01:30 2023 InstallationDate: Installed on 2023-03-05 (22 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash 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/yaru/+bug/2012973/+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 2012973] Re: Trash icon changes when reducing size
** Attachment added: "Bildschirmfoto vom 2023-03-27 21-04-34.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2012973/+attachment/5657992/+files/Bildschirmfoto%20vom%202023-03-27%2021-04-34.png -- 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/2012973 Title: Trash icon changes when reducing size Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Ubuntu 22.10 When changing the size of the Ubuntu dock icons to any value between 34 and 44 it changes the trash icon changes from the regular Ubuntu trash icon to a different (blueish) icon. I would expect the icon to remain the same and only reduce its size. Before noticing this issue I installed the regular GNOME dash to dock extension but I removed it again, reinstalled the package gnome-shell- extension-ubuntu-dock and also reset dock settings with dconf reset -f /org/gnome/shell/extensions/dash-to-dock/. Also I tried updating icon cache with sudo update-icon-caches /usr/share/icons/*. I am not sure if the issue existed before installing dash to dock. I am using a HighDPI screen in case this has something to do with the issue. I am not seeing this problem on my desktop computer without HighDPI but I also didn't install dash to dock there. I am running Wayland. Any idea what else I could try to reset? ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell-extension-ubuntu-dock 74ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 21:01:30 2023 InstallationDate: Installed on 2023-03-05 (22 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash 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/2012973/+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 2012973] [NEW] Trash icon changes when reducing size
Public bug reported: Ubuntu 22.10 When changing the size of the Ubuntu dock icons to any value between 34 and 44 it changes the trash icon changes from the regular Ubuntu trash icon to a different (blueish) icon. I would expect the icon to remain the same and only reduce its size. Before noticing this issue I installed the regular GNOME dash to dock extension but I removed it again, reinstalled the package gnome-shell- extension-ubuntu-dock and also reset dock settings with dconf reset -f /org/gnome/shell/extensions/dash-to-dock/. Also I tried updating icon cache with sudo update-icon-caches /usr/share/icons/*. I am not sure if the issue existed before installing dash to dock. I am using a HighDPI screen in case this has something to do with the issue. I am not seeing this problem on my desktop computer without HighDPI but I also didn't install dash to dock there. I am running Wayland. Any idea what else I could try to reset? ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell-extension-ubuntu-dock 74ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 21:01:30 2023 InstallationDate: Installed on 2023-03-05 (22 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session ** Attachment added: "Bildschirmfoto vom 2023-03-27 21-04-49.png" https://bugs.launchpad.net/bugs/2012973/+attachment/5657989/+files/Bildschirmfoto%20vom%202023-03-27%2021-04-49.png -- 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/2012973 Title: Trash icon changes when reducing size Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Ubuntu 22.10 When changing the size of the Ubuntu dock icons to any value between 34 and 44 it changes the trash icon changes from the regular Ubuntu trash icon to a different (blueish) icon. I would expect the icon to remain the same and only reduce its size. Before noticing this issue I installed the regular GNOME dash to dock extension but I removed it again, reinstalled the package gnome-shell- extension-ubuntu-dock and also reset dock settings with dconf reset -f /org/gnome/shell/extensions/dash-to-dock/. Also I tried updating icon cache with sudo update-icon-caches /usr/share/icons/*. I am not sure if the issue existed before installing dash to dock. I am using a HighDPI screen in case this has something to do with the issue. I am not seeing this problem on my desktop computer without HighDPI but I also didn't install dash to dock there. I am running Wayland. Any idea what else I could try to reset? ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell-extension-ubuntu-dock 74ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 21:01:30 2023 InstallationDate: Installed on 2023-03-05 (22 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash 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/2012973/+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 1988836] Autopkgtest regression report (linux-restricted-modules-gcp-5.19/5.19.0-1020.22~22.04.2+1)
All autopkgtests for the newly accepted linux-restricted-modules-gcp-5.19 (5.19.0-1020.22~22.04.2+1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-gcp-5.19 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 2006940] Re: PIN validation affects interface even if the manual token button is selected
** Changed in: software-properties (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2006940 Title: PIN validation affects interface even if the manual token button is selected Status in software-properties package in Ubuntu: Fix Released Bug description: 1. software-properties-gtk 2. Go to Ubuntu Pro 3. Go to Enable Ubuntu Pro 4. Press "Or add token manually button" radio 5. Go to ubuntu.com/pro/attach and submit the PIN Expected: Nothing happens until the user clicks "Enter code..." radio. Observed: UI is locked with "Valid token" message next to the manual token field, which won't allow to attach the token received from PIN validation. Similar issue happens when PIN expires instead of being validated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2006940/+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 2011806] Re: [lunar] Snaps don't launch due to cgroup issue
** Changed in: snapd (Ubuntu) Status: Won't Fix => Confirmed -- 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/2011806 Title: [lunar] Snaps don't launch due to cgroup issue Status in gnome-shell package in Ubuntu: In Progress Status in kio package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: Hi, Lunar up to date, Intel+Nvidia GPUs, Ubuntu Wayland or X11 session, hybrid or discrete graphics. If I click on a snap dash icon, nothing happens. Tested with Thunderbird, Firefox, Shortwave... (VS Code seems ok, maybe due to classic confinment?) I can launch without issue Chrome (deb), Synaptic, GNOME apps, etc. Recent updates included gnome-shell and libadwaita. --- I get this type of log for all problematic snaps: /user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome- shortwave_shortwave-11885.scope is not a snap cgroup --- Context: $ snap --version snap2.58.3+23.04ubuntu1 snapd 2.58.3+23.04ubuntu1 series 16 ubuntu 23.04 kernel 6.1.0-16-generic $ snap list Nom Version Révision Suivi Éditeur Notes bare 1.0 5 latest/stable canonical✓base code ee2b180d122 latest/stable vscode✓ classic core 16-2.58.2 14784 latest/stable canonical✓core core18202303082714 latest/stable canonical✓base core20202302071828 latest/stable canonical✓base core2220230210522 latest/stable canonical✓base firefox 111.0-2 2432 latest/candidate mozilla✓ - gimp 2.10.30 393 latest/stable snapcrafters - gnome-3-28-1804 3.28.0-19-g98f9e67.98f9e67 161 latest/stable canonical✓- gnome-3-38-2004 0+git.6f39565 119 latest/stable canonical✓- gnome-42-2204 0+git.09673a5 65 latest/stable canonical✓- gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓- gtk-theme-pocillo 0.14.4.15 latest/stable ubuntubudgie - gtk-theme-qogirbudgie 22.04.1 8 latest/stable ubuntubudgie - gtk2-common-themes0.1 13 latest/stable canonical✓- hunspell-dictionaries-1-7-20041.7-20.04+pkg-6fd6 2 latest/stable brlin - kde-frameworks-5-91-qt-5-15-3-core20 5.91.0 1 latest/stable kde✓ - kde-frameworks-5-99-qt-5-15-7-core20 5.99.0 15 latest/stable kde✓ - kde-frameworks-5-core18 5.67.0 35 latest/stable kde✓ - libreoffice 7.5.1.2 270 latest/stable canonical✓- shortwave 3.0.0 79 latest/stable alexmurray✪ - snapd 2.58.2 18357 latest/stable canonical✓snapd snapd-desktop-integration 0.1 71 latest/stable/… canonical✓- stellarium-daily v1.21396 latest/stable t4saha- thunderbird 102.9.0-1 305 latest/candidate canonical✓- vlc 3.0.18 3078 latest/stable videolan✓ - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011806/+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 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
This is about a bug in this piece of software, and not about finding another piece of software to take its place. wsdd, as you proposed, is not included by default in Ubuntu. The point of seeking a fix for this issue is so that the UX, out of the box, is better than it is now. Users should not have to install another tool to get this basic functionality working. I would like to remind those reading that this issue was posted ALMOST FOUR YEARS ago. And the "temporary workaround" is to kill the process so it reinitalises. Can we PLEASE get this fixed already?!?!?!? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 Status in gvfs: New Status in gvfs package in Ubuntu: Triaged Bug description: After bug #1778322 is fixed (just needs a gvfs rebuild with newer samba), samba machines will start to show up again in the "windows network" tab in nautilus. But if a server has disabled the SMB1 protocol, nautilus will show an error when that server is clicked on, instead of showing the shares list. Even with SMB1 disabled, it should still be technically possible to get a share list, since smbclient can do it: andreas@nsnx:~$ nmblookup -A 192.168.122.101 Looking up status of 192.168.122.101 D-NO-SMB1 <00> - B D-NO-SMB1 <03> - B D-NO-SMB1 <20> - B ..__MSBROWSE__. <01> - B WORKGROUP <00> - B WORKGROUP <1d> - B WORKGROUP <1e> - B MAC Address = 00-00-00-00-00-00 andreas@nsnx:~$ smbclient -L 192.168.122.101 -N WARNING: The "syslog" option is deprecated Sharename Type Comment - --- print$ Disk Printer Drivers pub_no_smb1 Disk IPC$IPC IPC Service (d-no-smb1 server (Samba, Ubuntu)) Reconnecting with SMB1 for workgroup listing. protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE Failed to connect with SMB1 -- no workgroup available andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m NT1 WARNING: The "syslog" option is deprecated protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m SMB2 WARNING: The "syslog" option is deprecated Try "help" to get a list of possible commands. smb: \> dir . D0 Fri May 3 18:16:38 2019 .. D0 Fri May 3 18:15:24 2019 hello.txt N 21 Fri May 3 18:16:12 2019 hello-from-nsnx.txt A9 Fri May 3 18:16:38 2019 20509264 blocks of size 1024. 13121800 blocks available To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+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 2012645] Re: Double icon in the dock starting system-monitor
The version of stellarion i'm using is NOT a snap corrado@corrado-n5-ll-0224:~$ apt policy stellarium stellarium: Installed: 0.22.2-1 Candidate: 0.22.2-1 Version table: *** 0.22.2-1 500 500 http://archive.ubuntu.com/ubuntu lunar/universe amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-n5-ll-0224:~$ -- 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/2012645 Title: Double icon in the dock starting system-monitor Status in gnome-shell package in Ubuntu: In Progress Bug description: I have gnome-system-monitor pinned to the dock (favorites). When i click the icon in the dock a new icon with the red dot appears in the dock instead adding the red dot to the 1st icon. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-system-monitor 44~beta-1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 23 16:09:01 2023 InstallationDate: Installed on 2023-02-25 (26 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230224) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-system-monitor 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/2012645/+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 2012957] [NEW] Xorg freeze
Public bug reported: I'm not sure if this is an xorg bug because i'm pretty sure I'm using wayland, however ubuntu-bug says it's an xorg issue. I installed the GNOME desktop instead of the ubuntu one, however it does happen on the ubuntu desktop as well. It seems to happen less often on the GNOME desktop (though still multiple times a day) When I perform certain actions I can semi-reliably produce a total screen freeze. Some examples include using the search menu on gnome, opening a video in fullscreen, and clicking buttons in fractal (matrix client.) There are many more scenarios that I haven't listed. The screen will completely freeze but the computer will keep going normally (e.g. I can type, use the cursor, listen to audio, etc.) This can be remedied by pressing CONTROL+ALT+F3 which brings me into the console, then waiting about 5 seconds, then switching back with CONTROL+ALT+F2 This doesn't seem to be related to any computer load issues and occurs reliably after clicking on something/typing in a text field until the offending program is restarted. When the program is restarted, the issue sometimes goes away but sometimes persists. This has been happening since I installed ubuntu a couple weeks ago. I am able to provide more details if necessary and do some debugging things, but I'm not a technical user so will need babying. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: GNOME Date: Mon Mar 27 12:47:02 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since before I upgraded GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Matsushita Electric Industrial Co., Ltd. Alder Lake-P Integrated Graphics Controller [10f7:8338] InstallationDate: Installed on 2023-03-15 (12 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: Panasonic Connect Co., Ltd. CFFV3-1 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=f8060648-d61e-4101-984c-4f5a1ff087f8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2022 dmi.bios.release: 1.0 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: V1.00L15 dmi.board.asset.tag: No Asset Tag dmi.board.name: CFFV3-1L dmi.board.vendor: Panasonic Connect Co., Ltd. dmi.board.version: 1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Panasonic Connect Co., Ltd. dmi.chassis.version: 001 dmi.ec.firmware.release: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrV1.00L15:bd05/09/2022:br1.0:efr1.0:svnPanasonicConnectCo.,Ltd.:pnCFFV3-1:pvr001:rvnPanasonicConnectCo.,Ltd.:rnCFFV3-1L:rvr1:cvnPanasonicConnectCo.,Ltd.:ct10:cvr001:skuCF-FV3DFNCR: dmi.product.family: Let'snote/TOUGHBOOK dmi.product.name: CFFV3-1 dmi.product.sku: CF-FV3DFNCR dmi.product.version: 001 dmi.sys.vendor: Panasonic Connect Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.6 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 freeze kinetic 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/2012957 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: I'm not sure if this is an xorg bug because i'm pretty sure I'm using wayland, however ubuntu-bug says it's an xorg issue. I installed the GNOME desktop instead of the ubuntu one, however it does happen on the ubuntu desktop as well. It seems to happen less often on the GNOME desktop (though still multiple times a day) When I perform certain actions I can semi-reliably produce a total screen freeze. Some examples include using the search menu
[Desktop-packages] [Bug 2012954] [NEW] drag and drop files via hot corner Activities Overview don't work anymore
Public bug reported: With gnome 42, you can drag and drop a file (for example from nautilus to firefox) via hot corner to move from one maximized window to another maximized window. to do this we click on the file, while maintaining the click we move it to the upper corner to switch to another application and deposit it (drop a file drop a file on a website for example) on gnome 43 (ubuntu 22.10) it doesn't work anymore. Moving file to hot corner does not open the Activities Overview ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2012954 Title: drag and drop files via hot corner Activities Overview don't work anymore Status in gnome-shell package in Ubuntu: New Bug description: With gnome 42, you can drag and drop a file (for example from nautilus to firefox) via hot corner to move from one maximized window to another maximized window. to do this we click on the file, while maintaining the click we move it to the upper corner to switch to another application and deposit it (drop a file drop a file on a website for example) on gnome 43 (ubuntu 22.10) it doesn't work anymore. Moving file to hot corner does not open the Activities Overview To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012954/+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 2012942] Re: Unable to switch to Chinese IME from Russian
That's expected behavior. But you can change it to better fit your situation: * Open /usr/share/ibus/component/libpinyin.xml for editing. * For the libpinyin engine, change this line: default to: us ** Changed in: ibus-libpinyin (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/2012942 Title: Unable to switch to Chinese IME from Russian Status in ibus-libpinyin package in Ubuntu: Invalid Bug description: I use ibus input framework for my Ubuntu 22.10, and I have English (US), Russian and Chinese (Intelligent Pinyin) installed as my IMEs. If I switch to Russian, then switch to Chinese, what the IME typed into my laptop is still Russian characters, instead of pinyin. I can switch to Chinese with success if I switch to English from Russian first, then to Chinese. ibus-libpinyin 1.13.0-2ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: ibus-libpinyin 1.13.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 22:18:15 2023 InstallationDate: Installed on 2022-02-18 (402 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: ibus-libpinyin UpgradeStatus: Upgraded to kinetic on 2023-03-10 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/2012942/+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 2012940] Re: English word as top candidate for some pinyin input
Thanks for your report! I noticed the same thing a while ago, and reported it upstream. The upstream maintainer moved the English candidates after the sentence candidates, and the new behavior should be present in Ubuntu 23.04. ** Changed in: ibus-libpinyin (Ubuntu) Status: New => Fix Released ** Bug watch added: github.com/libpinyin/ibus-libpinyin/issues #378 https://github.com/libpinyin/ibus-libpinyin/issues/378 ** Also affects: ibus-libpinyin via https://github.com/libpinyin/ibus-libpinyin/issues/378 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/2012940 Title: English word as top candidate for some pinyin input Status in ibus-libpinyin: Unknown Status in ibus-libpinyin package in Ubuntu: Fix Released Bug description: For some user input, linpinyin provides English words as top candidates, which is extremely unhelpful. For example: - For 'shang', 'shanghai' is provided as 1st candidate. - For 'rang', 'rang' and 'range' is provided as 1st and 2nd candidate. However, for Chinese speakers, they expect following candidates: - For 'shang', '上' is much more expected. - For 'rang', '让' is much more expected. This bugs makes ibus-libpinyin sometimes annoying. As a native Chinese speaker, I suggest: If ibus-libpinyin wants to suggest English words, it should first check if the input is pinyin, not an English word. Ubuntu 22.10 ibus-libpinyin 1.13.0-2ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: ibus-libpinyin 1.13.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 22:08:33 2023 InstallationDate: Installed on 2022-02-18 (402 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: ibus-libpinyin UpgradeStatus: Upgraded to kinetic on 2023-03-10 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus-libpinyin/+bug/2012940/+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 2012904] Re: Trash icon missing on desktop (on some machines, randomly)
ubuntu-settings contains an override that sets show-trash to false for new installs. My issue apparently is that at some point I enabled show-trash and relying on: dconf reset -f / is incorrect because it's resetting to the upstream default of true while ignoring the Ubuntu override of false. ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons-ng in Ubuntu. https://bugs.launchpad.net/bugs/2012904 Title: Trash icon missing on desktop (on some machines, randomly) Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Invalid Bug description: Trash icon missing on desktop despite the settings schema having a default value of true for "show-trash". Out of my three machines running lunar, only one of them successfully displays the Trash icon on the desktop. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell-extension-desktop-icons-ng 46+really47.0.2-3 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Mar 27 16:29:47 2023 InstallationDate: Installed on 2023-03-25 (1 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230317) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-shell-extension-desktop-icons-ng 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-desktop-icons-ng/+bug/2012904/+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 2012942] [NEW] Unable to switch to Chinese IME from Russian
Public bug reported: I use ibus input framework for my Ubuntu 22.10, and I have English (US), Russian and Chinese (Intelligent Pinyin) installed as my IMEs. If I switch to Russian, then switch to Chinese, what the IME typed into my laptop is still Russian characters, instead of pinyin. I can switch to Chinese with success if I switch to English from Russian first, then to Chinese. ibus-libpinyin 1.13.0-2ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: ibus-libpinyin 1.13.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 22:18:15 2023 InstallationDate: Installed on 2022-02-18 (402 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: ibus-libpinyin UpgradeStatus: Upgraded to kinetic on 2023-03-10 (17 days ago) ** Affects: ibus-libpinyin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/2012942 Title: Unable to switch to Chinese IME from Russian Status in ibus-libpinyin package in Ubuntu: New Bug description: I use ibus input framework for my Ubuntu 22.10, and I have English (US), Russian and Chinese (Intelligent Pinyin) installed as my IMEs. If I switch to Russian, then switch to Chinese, what the IME typed into my laptop is still Russian characters, instead of pinyin. I can switch to Chinese with success if I switch to English from Russian first, then to Chinese. ibus-libpinyin 1.13.0-2ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: ibus-libpinyin 1.13.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 22:18:15 2023 InstallationDate: Installed on 2022-02-18 (402 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: ibus-libpinyin UpgradeStatus: Upgraded to kinetic on 2023-03-10 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/2012942/+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 2012940] [NEW] English word as top candidate for some pinyin input
Public bug reported: For some user input, linpinyin provides English words as top candidates, which is extremely unhelpful. For example: - For 'shang', 'shanghai' is provided as 1st candidate. - For 'rang', 'rang' and 'range' is provided as 1st and 2nd candidate. However, for Chinese speakers, they expect following candidates: - For 'shang', '上' is much more expected. - For 'rang', '让' is much more expected. This bugs makes ibus-libpinyin sometimes annoying. As a native Chinese speaker, I suggest: If ibus-libpinyin wants to suggest English words, it should first check if the input is pinyin, not an English word. Ubuntu 22.10 ibus-libpinyin 1.13.0-2ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: ibus-libpinyin 1.13.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 22:08:33 2023 InstallationDate: Installed on 2022-02-18 (402 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: ibus-libpinyin UpgradeStatus: Upgraded to kinetic on 2023-03-10 (17 days ago) ** Affects: ibus-libpinyin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/2012940 Title: English word as top candidate for some pinyin input Status in ibus-libpinyin package in Ubuntu: New Bug description: For some user input, linpinyin provides English words as top candidates, which is extremely unhelpful. For example: - For 'shang', 'shanghai' is provided as 1st candidate. - For 'rang', 'rang' and 'range' is provided as 1st and 2nd candidate. However, for Chinese speakers, they expect following candidates: - For 'shang', '上' is much more expected. - For 'rang', '让' is much more expected. This bugs makes ibus-libpinyin sometimes annoying. As a native Chinese speaker, I suggest: If ibus-libpinyin wants to suggest English words, it should first check if the input is pinyin, not an English word. Ubuntu 22.10 ibus-libpinyin 1.13.0-2ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: ibus-libpinyin 1.13.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 22:08:33 2023 InstallationDate: Installed on 2022-02-18 (402 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: ibus-libpinyin UpgradeStatus: Upgraded to kinetic on 2023-03-10 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/2012940/+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 2012788] Re: Entering Unicode characters with code points broken
If I install ibus 1.5.28-2 from experimental on Debian, there is no code point issue. While the source is identical with 1.5.28-2 on Ubuntu, the binaries on Debian were built with older versions of some libraries. I'm not sure that the problem lies in glib. It's simply my intuition. ;) ** Changed in: glib2.0 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2012788 Title: Entering Unicode characters with code points broken Status in glib2.0 package in Ubuntu: New Status in ibus package in Ubuntu: Confirmed Bug description: On an updated lunar, following this instruction: https://help.ubuntu.com/stable/ubuntu-help/tips- specialchars.html#ctrlshiftu no longer works. If I press for instance Ctrl+Shift+U followed by 2014 I see u2014 (underlined) on the screen. But it's not replaced with the expected character (in this case an Em Dash) when I confirm with Space or Enter — it just disappears. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2012788/+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 2012645] Re: Double icon in the dock starting system-monitor
Snap store issue is different (see https://gitlab.gnome.org/Community/Ubuntu/gnome-software/-/issues/12), in stellarium case I need to check the snap, but I did not notice it in repository version. ** Bug watch added: gitlab.gnome.org/Community/Ubuntu/gnome-software/-/issues #12 https://gitlab.gnome.org/Community/Ubuntu/gnome-software/-/issues/12 -- 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/2012645 Title: Double icon in the dock starting system-monitor Status in gnome-shell package in Ubuntu: In Progress Bug description: I have gnome-system-monitor pinned to the dock (favorites). When i click the icon in the dock a new icon with the red dot appears in the dock instead adding the red dot to the 1st icon. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-system-monitor 44~beta-1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 23 16:09:01 2023 InstallationDate: Installed on 2023-02-25 (26 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230224) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-system-monitor 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/2012645/+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 2012931] [NEW] No way to permanently disable Check Spelling
Public bug reported: Editing a document i see many words underlined by red dots. Red dots disappear if I disable check spelling but after saving the documents next time red dots reappear. I find no way to permanently disable Check Spelling. see screenshot ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-text-editor 44~rc-1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 15:04:20 2023 InstallationDate: Installed on 2023-02-25 (30 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230224) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-text-editor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session ** Attachment added: "Screenshot from 2023-03-27 15-02-34.png" https://bugs.launchpad.net/bugs/2012931/+attachment/5657870/+files/Screenshot%20from%202023-03-27%2015-02-34.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-text-editor in Ubuntu. https://bugs.launchpad.net/bugs/2012931 Title: No way to permanently disable Check Spelling Status in gnome-text-editor package in Ubuntu: New Bug description: Editing a document i see many words underlined by red dots. Red dots disappear if I disable check spelling but after saving the documents next time red dots reappear. I find no way to permanently disable Check Spelling. see screenshot ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-text-editor 44~rc-1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 15:04:20 2023 InstallationDate: Installed on 2023-02-25 (30 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230224) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/2012931/+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 1966905] Re: Segfault in g_type_check_instance_cast → free_fetch_user_request → fetch_user_incrementally → on_find_user_by_name_finished → g_task_return_now
** Summary changed: - Invalid memory access in accountsservice: free_fetch_user_request() + Segfault in g_type_check_instance_cast → free_fetch_user_request → fetch_user_incrementally → on_find_user_by_name_finished → g_task_return_now ** Description changed: + This is now the #1 gnome-shell crasher in Ubuntu 23.04. + https://errors.ubuntu.com/problem/d85747462e756cb405d1e87b9c59b0b995a7d394 https://errors.ubuntu.com/problem/1674bdbf40a28b5f59067ffde832ba508ecba114 Valgrind memory errors in gnome-shell 42 from accountsservice: ==60511== Invalid read of size 8 ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120) ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417) ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557) ==60511==by 0x1E428ECA: _act_user_update_from_object_path (act-user.c:1346) ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511== Block was alloc'd at ==60511==at 0x4848899: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4DA5718: g_malloc (gmem.c:125) ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072) ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098) ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911) ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011) ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181) ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821) ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706) ==60511==by 0x1E429BD8: act_user_manager_get_user (act-user-manager.c:1879) ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511== ==60511== Invalid read of size 8 ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a (gtype.c:4091) ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982) ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562) ==60511==by 0x1E428ECA: UnknownInlinedFun
[Desktop-packages] [Bug 2012788] Re: Entering Unicode characters with code points broken
The problem is reproducible on amd64, arm64, riscv64. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2012788 Title: Entering Unicode characters with code points broken Status in glib2.0 package in Ubuntu: New Status in ibus package in Ubuntu: Confirmed Bug description: On an updated lunar, following this instruction: https://help.ubuntu.com/stable/ubuntu-help/tips- specialchars.html#ctrlshiftu no longer works. If I press for instance Ctrl+Shift+U followed by 2014 I see u2014 (underlined) on the screen. But it's not replaced with the expected character (in this case an Em Dash) when I confirm with Space or Enter — it just disappears. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2012788/+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 2012788] Re: Entering Unicode characters with code points broken
Yes, Heinrich, on the surface this seems to be an ibus issue. But I think the root cause lies in some package which ibus is built with. If I downgrade to the binaries built by ibus 1.5.28-1 on February 23, using code points works fine. In 1.5.28-2 two upstream commits were added as patches, but if I now build ibus with those patches disabled, it doesn't help. A no-change rebuild does not help either. Maybe glib is the culprit? ibus 1.5.28-1 was built with glib 2.74. ** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2012788 Title: Entering Unicode characters with code points broken Status in glib2.0 package in Ubuntu: New Status in ibus package in Ubuntu: Confirmed Bug description: On an updated lunar, following this instruction: https://help.ubuntu.com/stable/ubuntu-help/tips- specialchars.html#ctrlshiftu no longer works. If I press for instance Ctrl+Shift+U followed by 2014 I see u2014 (underlined) on the screen. But it's not replaced with the expected character (in this case an Em Dash) when I confirm with Space or Enter — it just disappears. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2012788/+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 1922276] Re: Select All (Shift+Ctrl+A) followed by Copy (Shift+Ctrl+C) copies only visible part of terminal output
** Changed in: vte2.91 (Ubuntu) Importance: Undecided => Medium ** Changed in: vte2.91 (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1922276 Title: Select All (Shift+Ctrl+A) followed by Copy (Shift+Ctrl+C) copies only visible part of terminal output Status in MATE Desktop: Unknown Status in Gnome Virtual Terminal Emulator: New Status in mate-terminal package in Ubuntu: Invalid Status in vte2.91 package in Ubuntu: Triaged Status in vte2.91 package in Debian: Unknown Bug description: Steps to reproduce: 1. Have Ubuntu MATE 21.04 installed (or use Live session) 2. Launch MATE Terminal 3. Enable infinite history (Edit - Profile Preferences - Scrolling, Scrollback - Unlimited) 4. Execute command with long output such as `journalctl | cat` 5. Select Edit - Select All (or press ++), then Edit - Copy (or press ++) 6. Open Pluma text editor and paste just copied terminal output Expected results: * whole terminal output is copied - staring by `user@host:~$ journalctl | cat` and ending by `user@host:~$` Actual results: * only last 15 lines were copied (depends on terminal size) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 Date: Thu Apr 1 17:35:47 2021 LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1922276/+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 2007331] Re: Fix HFP mSBC support on Realtek Bluetooth USB controller
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8 --- linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352) * overlayfs mounts as R/O over idmapped mount (LP: #2009065) - SAUCE: overlayfs: handle idmapped mounts in ovl_do_(set|remove)xattr * Some QHD panels fail to refresh when PSR2 enabled (LP: #2009014) - SAUCE: drm/i915/psr: Use calculated io and fast wake lines * Fix mediatek wifi driver crash when loading wrong SAR table (LP: #2009118) - wifi: mt76: mt7921: fix error code of return in mt7921_acpi_read * Packaging resync (LP: #1786013) - [Packaging] update update.conf * Update dg2_dmc to 2.08 (LP: #1999375) - drm/i915/dmc: Update DG2 DMC version to v2.08 * New DG2 workarounds (LP: #2006945) - drm/i915/dg2: Introduce Wa_18017747507 - drm/i915/dg2: Introduce Wa_18018764978 - drm/i915/dg2: Introduce Wa_18019271663 * Screen backlight keeps in minimized and can't change it with amdgpu (LP: #2008871) - SAUCE: ACPI: video: Add backlight=native DMI quirk for Dell Vostro 15 3535 * Remove all other acpi_video backlight interface on Dell AIO platforms (LP: #2008882) - SAUCE: ACPI: video: Dell AIO UART backlight detection * screen flicker after PSR2 enabled (LP: #2007516) - SAUCE: drm/i915/display/psr: Disable PSR2 sel fetch on panel SHP 5457 * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * Fix HFP mSBC support on Realtek Bluetooth USB controller (LP: #2007331) - Bluetooth: btrtl: Add btrealtek data struct - Bluetooth: btusb: Ignore zero length of USB packets on ALT 6 for specific chip * Jammy update: v6.1.14 upstream stable release (LP: #2008708) - drm/etnaviv: don't truncate physical page address - wifi: ath11k: fix warning in dma_free_coherent() of memory chunks while recovery - wifi: rtl8xxxu: gen2: Turn on the rate control - drm/edid: Fix minimum bpc supported with DSC1.2 for HDMI sink - clk: mxl: Switch from direct readl/writel based IO to regmap based IO - clk: mxl: Remove redundant spinlocks - clk: mxl: Add option to override gate clks - clk: mxl: Fix a clk entry by adding relevant flags - powerpc: dts: t208x: Mark MAC1 and MAC2 as 10G - clk: mxl: syscon_node_to_regmap() returns error pointers - sched/psi: Stop relying on timer_pending() for poll_work rescheduling - random: always mix cycle counter in add_latent_entropy() - scsi: libsas: Add smp_ata_check_ready_type() - scsi: hisi_sas: Fix SATA devices missing issue during I_T nexus reset - spi: mediatek: Enable irq when pdata is ready - docs: perf: Fix PMU instance name of hisi-pcie-pmu - KVM: x86: Fail emulation during EMULTYPE_SKIP on any exception - KVM: SVM: Skip WRMSR fastpath on VM-Exit if next RIP isn't valid - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS - can: kvaser_usb: hydra: help gcc-13 to figure out cmd_len - powerpc: dts: t208x: Disable 10G on MAC1 and MAC2 - spi: mediatek: Enable irq before the spi registration - drm/i915: Remove __maybe_unused from mtl_info - KVM: x86: fix deadlock for KVM_XEN_EVTCHN_RESET - selftests: kvm: move declaration at the beginning of main() - powerpc/64s/radix: Fix RWX mapping with relocated kernel - nfp: ethtool: support reporting link modes - nfp: ethtool: fix the bug of setting unsupported port speed - uaccess: Add speculation barrier to copy_from_user() - x86/alternatives: Introduce int3_emulate_jcc() - x86/alternatives: Teach text_poke_bp() to patch Jcc.d32 instructions - x86/static_call: Add support for Jcc tail-calls - Bluetooth: btusb: Add more device IDs for WCN6855 - riscv: remove special treatment for the link order of head.o - arm64: remove special treatment for the link order of head.o - arch: fix broken BuildID for arm64 and riscv - powerpc/vmlinux.lds: Define RUNTIME_DISCARD_EXIT - powerpc/vmlinux.lds: Don't discard .rela* for relocatable builds - s390: define RUNTIME_DISCARD_EXIT to fix link error with GNU ld < 2.36 - sh: define RUNTIME_DISCARD_EXIT - wifi: mwifiex: Add missing compatible string for SD8787 - audit: update the mailing list in MAINTAINERS - platform/x86/amd/pmf: Add depends on CONFIG_POWER_SUPPLY - platform/x86: nvidia-wmi-ec-backlight: Add force module parameter - ext4: Fix function prototype mismatch for ext4_feat_ktype - randstruct: disable Clang 15 support - bpf: add missing header file include - Linux 6.1.14 - upstream stable to v6.1.14 * Jammy update: v6.1.13 upstream stable release (LP: #2008707) - mptcp: sockopt: make 'tcp_fastopen_connect' generic - mptcp: fix locking for setsockopt corner-case - mptcp: deduplicate error paths on endpoint creation
[Desktop-packages] [Bug 2007331] Re: Fix HFP mSBC support on Realtek Bluetooth USB controller
This bug was fixed in the package linux-oem-6.0 - 6.0.0-1013.13 --- linux-oem-6.0 (6.0.0-1013.13) jammy; urgency=medium * jammy/linux-oem-6.0: 6.0.0-1013.13 -proposed tracker (LP: #2008351) * CVE-2023-1281 - net/sched: tcindex: update imperfect hash filters respecting rcu * CVE-2023-1032 - net: avoid double iput when sock_alloc_file fails * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * CVE-2022-2196 - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS * Fix HFP mSBC support on Realtek Bluetooth USB controller (LP: #2007331) - Bluetooth: btrtl: Add btrealtek data struct - Bluetooth: btusb: Ignore zero length of USB packets on ALT 6 for specific chip -- Timo Aaltonen Thu, 16 Mar 2023 17:59:47 +0200 ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: Won't Fix => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-2196 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-1032 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-1281 ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2007331 Title: Fix HFP mSBC support on Realtek Bluetooth USB controller Status in HWE Next: New Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in pulseaudio source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in pulseaudio source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in pulseaudio source package in Lunar: Fix Released Bug description: [Impact] When a BT headset is connected Realtek BT USB controller, HFP profile can't play or record sound when mSBC codec is used. [Fix] At Linux kernel side, add a Realtek specific quirk to support mSBC. At PulseAudio side, send more data frames until the connected device sends response. [Test] Connect different headsets to the said controller, HFP can play and record sounds now. Also verified A2DP profile is unaffected. [Where problems could occur] The kernel part is Realtek specific, so the regression risk is very limited. The pulseaudio side only affects HFP profile, since the codeflow only changes when a mic is present. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2007331/+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 2012869] Re: Ubuntu font repeated many times
see https://gitlab.gnome.org/GNOME/gnome-font-viewer/-/issues/70 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-font-viewer/-/issues #70 https://gitlab.gnome.org/GNOME/gnome-font-viewer/-/issues/70 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/2012869 Title: Ubuntu font repeated many times Status in gnome-font-viewer package in Ubuntu: New Bug description: In the page same Ubuntu font is repeated many times see screenshot ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-font-viewer 44~beta-1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 07:41:19 2023 InstallationDate: Installed on 2023-02-25 (29 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230224) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-font-viewer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/2012869/+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 2012371] Re: [FFe] ubuntu-proxy-manager and adsys
FFe granted, please go ahead. ** Changed in: adsys (Ubuntu) Status: New => Triaged -- 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/2012371 Title: [FFe] ubuntu-proxy-manager and adsys Status in adsys package in Ubuntu: Triaged Bug description: Ubuntu Proxy Manager is a D-Bus mediated service that allows for managing system proxy settings via multiple backends (APT, environment variables and GSettings). We request a FFe for this new source package (ubuntu-proxy-manager). As it's a new source package the risk of it breaking existing setups is non-existent as it must be explicitly opted into by users. The package is written in Go and benefits from an extensive test suite covering over 90% of the codebase. Additionally, we would like to request a FFe for adsys where we added a Suggests dependency on ubuntu-proxy-manager. We have taken great care on the adsys part to maintain backwards compatibility and not affect users who do not install the ubuntu-proxy-manager package. Installing the ubuntu-proxy-manager package on its own has no impact to the system. To benefit from its functionality adsys has to be upgraded and correctly configured. - Relevant URLs: 1. ubuntu-proxy-manager homepage: https://github.com/ubuntu/ubuntu-proxy-manager 2. ubuntu-proxy-manager implementation in ADSys: https://github.com/ubuntu/adsys/pull/637 3. LP build of ubuntu-proxy-manager: https://launchpad.net/~gabuscus/+archive/ubuntu/ppa/+sourcepub/14562796/+listing-archive-extra 4. LP build of adsys: https://launchpad.net/~gabuscus/+archive/ubuntu/ppa/+sourcepub/14562807/+listing-archive-extra To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2012371/+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 2012902] Re: netplan plugin: generated NM config when using globbing will be used for only one connection
** Tags added: netplan-everywhere -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2012902 Title: netplan plugin: generated NM config when using globbing will be used for only one connection Status in network-manager package in Ubuntu: New Bug description: There is a mismatch between what netplan expresses when using globbing in a netplan file and what NM understands when using a match setting. For instance: network: version: 2 ethernets: all-en: match: name: "en*" dhcp4: true Generates a NM connection in /run/NetworkManager/system-connections: ... [match] interface-name=en*; ... But an NM connection can only match one interface, so if two interfaces like ens2 and ens3 exist, only one of them will be configured, even though the netplan configuration is expected to be applied to both. Solving this might involve generating one NM connection in the netplan plugin per detected interface. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2012902/+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 2012904] [NEW] Trash icon missing on desktop (on some machines, randomly)
Public bug reported: Trash icon missing on desktop despite the settings schema having a default value of true for "show-trash". Out of my three machines running lunar, only one of them successfully displays the Trash icon on the desktop. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell-extension-desktop-icons-ng 46+really47.0.2-3 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Mar 27 16:29:47 2023 InstallationDate: Installed on 2023-03-25 (1 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230317) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-shell-extension-desktop-icons-ng UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar rls-ll-incoming ** Summary changed: - Trash icon missing on desktop + Trash icon missing on desktop (on some machines, randomly) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons-ng in Ubuntu. https://bugs.launchpad.net/bugs/2012904 Title: Trash icon missing on desktop (on some machines, randomly) Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Bug description: Trash icon missing on desktop despite the settings schema having a default value of true for "show-trash". Out of my three machines running lunar, only one of them successfully displays the Trash icon on the desktop. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell-extension-desktop-icons-ng 46+really47.0.2-3 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Mar 27 16:29:47 2023 InstallationDate: Installed on 2023-03-25 (1 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230317) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-shell-extension-desktop-icons-ng 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-desktop-icons-ng/+bug/2012904/+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 2012901] Re: Top-left window border corruption after increasing display scale from 100% to 200% in Xorg
The new window is also non-interactive until resized, as if it still exists at the old scale. -- 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/2012901 Title: Top-left window border corruption after increasing display scale from 100% to 200% in Xorg Status in mutter package in Ubuntu: New Bug description: Top-left window border corruption after increasing display scale from 100% to 200% in Xorg. This happens both on the Settings window when you change the scale, and on the new installer window if the display scale is increased automatically on high DPI screens. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter 44.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Mar 27 16:18:34 2023 InstallationDate: Installed on 2022-11-28 (119 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2012901/+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 2012901] Re: Top-left window border corruption after increasing display scale from 100% to 200% in Xorg
** Attachment added: "Screenshot from 2023-03-25 12-48-44.png" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2012901/+attachment/5657729/+files/Screenshot%20from%202023-03-25%2012-48-44.png -- 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/2012901 Title: Top-left window border corruption after increasing display scale from 100% to 200% in Xorg Status in mutter package in Ubuntu: New Bug description: Top-left window border corruption after increasing display scale from 100% to 200% in Xorg. This happens both on the Settings window when you change the scale, and on the new installer window if the display scale is increased automatically on high DPI screens. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter 44.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Mar 27 16:18:34 2023 InstallationDate: Installed on 2022-11-28 (119 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2012901/+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 2012901] Re: Top-left window border corruption after increasing display scale from 100% to 200% in Xorg
** Attachment added: "Screenshot from 2023-03-27 16-08-06.png" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2012901/+attachment/5657728/+files/Screenshot%20from%202023-03-27%2016-08-06.png -- 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/2012901 Title: Top-left window border corruption after increasing display scale from 100% to 200% in Xorg Status in mutter package in Ubuntu: New Bug description: Top-left window border corruption after increasing display scale from 100% to 200% in Xorg. This happens both on the Settings window when you change the scale, and on the new installer window if the display scale is increased automatically on high DPI screens. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter 44.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Mar 27 16:18:34 2023 InstallationDate: Installed on 2022-11-28 (119 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2012901/+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 2012901] [NEW] Top-left window border corruption after increasing display scale from 100% to 200% in Xorg
Public bug reported: Top-left window border corruption after increasing display scale from 100% to 200% in Xorg. This happens both on the Settings window when you change the scale, and on the new installer window if the display scale is increased automatically on high DPI screens. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter 44.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Mar 27 16:18:34 2023 InstallationDate: Installed on 2022-11-28 (119 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-bug lunar rls-ll-incoming visual-quality -- 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/2012901 Title: Top-left window border corruption after increasing display scale from 100% to 200% in Xorg Status in mutter package in Ubuntu: New Bug description: Top-left window border corruption after increasing display scale from 100% to 200% in Xorg. This happens both on the Settings window when you change the scale, and on the new installer window if the display scale is increased automatically on high DPI screens. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter 44.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Mar 27 16:18:34 2023 InstallationDate: Installed on 2022-11-28 (119 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2012901/+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 2012902] [NEW] netplan plugin: generated NM config when using globbing will be used for only one connection
Public bug reported: There is a mismatch between what netplan expresses when using globbing in a netplan file and what NM understands when using a match setting. For instance: network: version: 2 ethernets: all-en: match: name: "en*" dhcp4: true Generates a NM connection in /run/NetworkManager/system-connections: ... [match] interface-name=en*; ... But an NM connection can only match one interface, so if two interfaces like ens2 and ens3 exist, only one of them will be configured, even though the netplan configuration is expected to be applied to both. Solving this might involve generating one NM connection in the netplan plugin per detected interface. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2012902 Title: netplan plugin: generated NM config when using globbing will be used for only one connection Status in network-manager package in Ubuntu: New Bug description: There is a mismatch between what netplan expresses when using globbing in a netplan file and what NM understands when using a match setting. For instance: network: version: 2 ethernets: all-en: match: name: "en*" dhcp4: true Generates a NM connection in /run/NetworkManager/system-connections: ... [match] interface-name=en*; ... But an NM connection can only match one interface, so if two interfaces like ens2 and ens3 exist, only one of them will be configured, even though the netplan configuration is expected to be applied to both. Solving this might involve generating one NM connection in the netplan plugin per detected interface. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2012902/+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 2012788] Re: Entering Unicode characters with code points broken
See https://wiki.archlinux.org/title/IBus#Unicode_input -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2012788 Title: Entering Unicode characters with code points broken Status in ibus package in Ubuntu: Confirmed Bug description: On an updated lunar, following this instruction: https://help.ubuntu.com/stable/ubuntu-help/tips- specialchars.html#ctrlshiftu no longer works. If I press for instance Ctrl+Shift+U followed by 2014 I see u2014 (underlined) on the screen. But it's not replaced with the expected character (in this case an Em Dash) when I confirm with Space or Enter — it just disappears. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2012788/+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 2012900] [NEW] Desktop icons blurry after increasing the display scale
Public bug reported: Desktop icons blurry after increasing the display scale. They only become sharp after logging in again. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell-extension-desktop-icons-ng 46+really47.0.2-3 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Mar 27 16:16:15 2023 InstallationDate: Installed on 2022-11-28 (119 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons-ng UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: Low Status: New ** Tags: amd64 apport-bug lunar rls-ll-incoming visual-quality ** Attachment added: "Screenshot from 2023-03-27 16-08-41.png" https://bugs.launchpad.net/bugs/2012900/+attachment/5657721/+files/Screenshot%20from%202023-03-27%2016-08-41.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons-ng in Ubuntu. https://bugs.launchpad.net/bugs/2012900 Title: Desktop icons blurry after increasing the display scale Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Bug description: Desktop icons blurry after increasing the display scale. They only become sharp after logging in again. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell-extension-desktop-icons-ng 46+really47.0.2-3 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Mar 27 16:16:15 2023 InstallationDate: Installed on 2022-11-28 (119 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons-ng 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-desktop-icons-ng/+bug/2012900/+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 2012788] Re: Entering Unicode characters with code points broken
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ibus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2012788 Title: Entering Unicode characters with code points broken Status in ibus package in Ubuntu: Confirmed Bug description: On an updated lunar, following this instruction: https://help.ubuntu.com/stable/ubuntu-help/tips- specialchars.html#ctrlshiftu no longer works. If I press for instance Ctrl+Shift+U followed by 2014 I see u2014 (underlined) on the screen. But it's not replaced with the expected character (in this case an Em Dash) when I confirm with Space or Enter — it just disappears. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2012788/+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 2012788] Re: Entering Unicode characters with code points broken
The same problem exists on KDE. So this looks more like an issue in ibus then in gnome-shell. ** Package changed: gnome-shell (Ubuntu) => ibus (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2012788 Title: Entering Unicode characters with code points broken Status in ibus package in Ubuntu: Confirmed Bug description: On an updated lunar, following this instruction: https://help.ubuntu.com/stable/ubuntu-help/tips- specialchars.html#ctrlshiftu no longer works. If I press for instance Ctrl+Shift+U followed by 2014 I see u2014 (underlined) on the screen. But it's not replaced with the expected character (in this case an Em Dash) when I confirm with Space or Enter — it just disappears. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2012788/+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
I can't see where Xorg crashed, but it looks like your kernel graphics driver also crashed at about the same time. Can you collect more from around this time in your system log? Mar 26 12:21:08 anna-yoga kernel: RDX: RSI: 7fdb0f0f8441 RDI: 0018 Mar 26 12:21:08 anna-yoga kernel: RBP: 0002 R08: R09: 0011 Mar 26 12:21:08 anna-yoga kernel: R10: 0018 R11: 0246 R12: 7fdb0f0f8441 Mar 26 12:21:08 anna-yoga kernel: R13: 5642fef3dbe0 R14: 5642fef3da80 R15: 5642fef465b0 Mar 26 12:21:08 anna-yoga kernel: Mar 26 12:21:08 anna-yoga kernel: ---[ end trace ]--- Mar 26 12:21:08 anna-yoga kernel: i915 :04:00.0: [drm] *ERROR* Writing dc state to 0x1 failed, now 0x0 -- 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 xorg-server package in Ubuntu: Incomplete 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
[Desktop-packages] [Bug 1966905] Re: Invalid memory access in accountsservice: free_fetch_user_request()
Tracking also in https://errors.ubuntu.com/problem/1674bdbf40a28b5f59067ffde832ba508ecba114 -- 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/1966905 Title: Invalid memory access in accountsservice: free_fetch_user_request() Status in accountsservice: New Status in gnome-control-center: Unknown Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/d85747462e756cb405d1e87b9c59b0b995a7d394 https://errors.ubuntu.com/problem/1674bdbf40a28b5f59067ffde832ba508ecba114 Valgrind memory errors in gnome-shell 42 from accountsservice: ==60511== Invalid read of size 8 ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120) ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417) ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557) ==60511==by 0x1E428ECA: _act_user_update_from_object_path (act-user.c:1346) ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511== Block was alloc'd at ==60511==at 0x4848899: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4DA5718: g_malloc (gmem.c:125) ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072) ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098) ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911) ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011) ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181) ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821) ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706) ==60511==by 0x1E429BD8: act_user_manager_get_user (act-user-manager.c:1879) ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511== ==60511== Invalid read of size 8 ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a (gtype.c:4091) ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982) ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511== Address 0x185b5110 is 0 bytes inside a block of size
[Desktop-packages] [Bug 1966905] Re: Memory access errors in gnome-shell from accountsservice
Upstream reckons this has fixed it for gnome-control-center: https://gitlab.gnome.org/GNOME/gnome-control- center/-/merge_requests/1681 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #2348 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2348 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2348 Importance: Unknown Status: Unknown ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-control-center (Ubuntu) Status: New => Fix Released ** Tags added: fixed-in-gnome-control-center-44.rc ** Summary changed: - Memory access errors in gnome-shell from accountsservice + Invalid memory access in accountsservice: free_fetch_user_request() ** Description changed: https://errors.ubuntu.com/problem/d85747462e756cb405d1e87b9c59b0b995a7d394 + https://errors.ubuntu.com/problem/1674bdbf40a28b5f59067ffde832ba508ecba114 Valgrind memory errors in gnome-shell 42 from accountsservice: ==60511== Invalid read of size 8 ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120) ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417) ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557) ==60511==by 0x1E428ECA: _act_user_update_from_object_path (act-user.c:1346) ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511== Block was alloc'd at ==60511==at 0x4848899: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4DA5718: g_malloc (gmem.c:125) ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072) ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098) ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911) ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011) ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181) ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821) ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706) ==60511==by 0x1E429BD8: act_user_manager_get_user (act-user-manager.c:1879) ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511== ==60511== Invalid read of size 8 ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a (gtype.c:4091) ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982) ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E:
[Desktop-packages] [Bug 2012832] Re: Xorg crashes on second and next unbind operations of Arc GPU
Hi Daniel, So here what I found: https://errors.ubuntu.com/oops/0e9e0a38-cc6e-11ed-b99a-fa163ef35206 - seems about that, but I did not found the same Backtrace thing inside. If it will not help - I can try to reproduce again and see if it will generate the crash again. Thank you -- 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 xorg-server package in Ubuntu: Incomplete 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/xorg-server/+bug/2012832/+subscriptions --
[Desktop-packages] [Bug 2012893] Re: /usr/bin/gnome-control-center:11:g_type_check_instance_cast:free_fetch_user_request:fetch_user_incrementally:on_find_user_by_id_finished:g_task_return_now
*** This bug is a duplicate of bug 1966905 *** https://bugs.launchpad.net/bugs/1966905 ** This bug has been marked a duplicate of bug 1966905 Memory access errors in gnome-shell from accountsservice -- 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/2012893 Title: /usr/bin/gnome-control- center:11:g_type_check_instance_cast:free_fetch_user_request:fetch_user_incrementally:on_find_user_by_id_finished:g_task_return_now Status in gnome-control-center package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:44~rc-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/1674bdbf40a28b5f59067ffde832ba508ecba114 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2012893/+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 2012893] [NEW] /usr/bin/gnome-control-center:11:g_type_check_instance_cast:free_fetch_user_request:fetch_user_incrementally:on_find_user_by_id_finished:g_task_return_now
*** This bug is a duplicate of bug 1966905 *** https://bugs.launchpad.net/bugs/1966905 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:44~rc-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/1674bdbf40a28b5f59067ffde832ba508ecba114 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: lunar -- 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/2012893 Title: /usr/bin/gnome-control- center:11:g_type_check_instance_cast:free_fetch_user_request:fetch_user_incrementally:on_find_user_by_id_finished:g_task_return_now Status in gnome-control-center package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:44~rc-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/1674bdbf40a28b5f59067ffde832ba508ecba114 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2012893/+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 1966905] Re: Memory access errors in gnome-shell from accountsservice
See also bug 2012879 -- 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/1966905 Title: Invalid memory access in accountsservice: free_fetch_user_request() Status in accountsservice: New Status in gnome-control-center: Unknown Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/d85747462e756cb405d1e87b9c59b0b995a7d394 Valgrind memory errors in gnome-shell 42 from accountsservice: ==60511== Invalid read of size 8 ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120) ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417) ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557) ==60511==by 0x1E428ECA: _act_user_update_from_object_path (act-user.c:1346) ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511== Block was alloc'd at ==60511==at 0x4848899: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4DA5718: g_malloc (gmem.c:125) ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072) ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098) ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911) ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011) ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181) ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821) ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706) ==60511==by 0x1E429BD8: act_user_manager_get_user (act-user-manager.c:1879) ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511== ==60511== Invalid read of size 8 ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a (gtype.c:4091) ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982) ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4:
[Desktop-packages] [Bug 2012879] Re: Crash in indicator-messages-service
Tracking in https://errors.ubuntu.com/problem/2416b63fd3efcd8ec09f184b6f50981fc56fb16d ** Tags added: jammy kinetic ** Description changed: + https://errors.ubuntu.com/problem/2416b63fd3efcd8ec09f184b6f50981fc56fb16d + Crash in indicator-messages-service ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: indicator-messages 13.10.1+18.10.20180918-0ubuntu3 Uname: Linux 6.2.0-18-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 14:25:09 2023 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service ExecutableTimestamp: 1633601577 ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service ProcCwd: /home/dan ProcEnviron: - LANG=en_AU.UTF-8 - LANGUAGE=en_AU:en - PATH=(custom, no user) - SHELL=/bin/bash - XDG_RUNTIME_DIR= + LANG=en_AU.UTF-8 + LANGUAGE=en_AU:en + PATH=(custom, no user) + SHELL=/bin/bash + XDG_RUNTIME_DIR= Signal: 11 SourcePackage: indicator-messages UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo ** Summary changed: - Crash in indicator-messages-service + indicator-messages-service crashed with SIGSEGV in ACT_IS_USER() from _act_user_update_from_object_path() from fetch_user_incrementally() from on_find_user_by_name_finished() from g_task_return_now() ** Package changed: indicator-messages (Ubuntu) => accountsservice (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2012879 Title: indicator-messages-service crashed with SIGSEGV in ACT_IS_USER() from _act_user_update_from_object_path() from fetch_user_incrementally() from on_find_user_by_name_finished() from g_task_return_now() Status in accountsservice package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/2416b63fd3efcd8ec09f184b6f50981fc56fb16d Crash in indicator-messages-service ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: indicator-messages 13.10.1+18.10.20180918-0ubuntu3 Uname: Linux 6.2.0-18-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 14:25:09 2023 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service ExecutableTimestamp: 1633601577 ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service ProcCwd: /home/dan ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 11 SourcePackage: indicator-messages UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2012879/+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 2012891] [NEW] /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service:11:ACT_IS_USER:_act_user_update_from_object_path:fetch_user_incrementally:on_find_user_by
*** This bug is a duplicate of bug 2012879 *** https://bugs.launchpad.net/bugs/2012879 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/2416b63fd3efcd8ec09f184b6f50981fc56fb16d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: indicator-messages (Ubuntu) Importance: Undecided Status: New ** Tags: jammy kinetic lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/2012891 Title: /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages- service:11:ACT_IS_USER:_act_user_update_from_object_path:fetch_user_incrementally:on_find_user_by_name_finished:g_task_return_now Status in indicator-messages package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/2416b63fd3efcd8ec09f184b6f50981fc56fb16d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/2012891/+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 2012645] Re: Double icon in the dock starting system-monitor
Similar problem (double icon) with snap-store and stellarium ** Attachment added: "Screenshot from 2023-03-27 08-48-28.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012645/+attachment/5657693/+files/Screenshot%20from%202023-03-27%2008-48-28.png -- 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/2012645 Title: Double icon in the dock starting system-monitor Status in gnome-shell package in Ubuntu: In Progress Bug description: I have gnome-system-monitor pinned to the dock (favorites). When i click the icon in the dock a new icon with the red dot appears in the dock instead adding the red dot to the 1st icon. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-system-monitor 44~beta-1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 23 16:09:01 2023 InstallationDate: Installed on 2023-02-25 (26 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230224) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-system-monitor 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/2012645/+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 2011806] Re: [lunar] Snaps don't launch due to cgroup issue
** Changed in: kio (Ubuntu) Importance: Undecided => Critical ** Changed in: snapd (Ubuntu) Importance: Undecided => Critical -- 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/2011806 Title: [lunar] Snaps don't launch due to cgroup issue Status in gnome-shell package in Ubuntu: In Progress Status in kio package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Won't Fix Bug description: Hi, Lunar up to date, Intel+Nvidia GPUs, Ubuntu Wayland or X11 session, hybrid or discrete graphics. If I click on a snap dash icon, nothing happens. Tested with Thunderbird, Firefox, Shortwave... (VS Code seems ok, maybe due to classic confinment?) I can launch without issue Chrome (deb), Synaptic, GNOME apps, etc. Recent updates included gnome-shell and libadwaita. --- I get this type of log for all problematic snaps: /user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome- shortwave_shortwave-11885.scope is not a snap cgroup --- Context: $ snap --version snap2.58.3+23.04ubuntu1 snapd 2.58.3+23.04ubuntu1 series 16 ubuntu 23.04 kernel 6.1.0-16-generic $ snap list Nom Version Révision Suivi Éditeur Notes bare 1.0 5 latest/stable canonical✓base code ee2b180d122 latest/stable vscode✓ classic core 16-2.58.2 14784 latest/stable canonical✓core core18202303082714 latest/stable canonical✓base core20202302071828 latest/stable canonical✓base core2220230210522 latest/stable canonical✓base firefox 111.0-2 2432 latest/candidate mozilla✓ - gimp 2.10.30 393 latest/stable snapcrafters - gnome-3-28-1804 3.28.0-19-g98f9e67.98f9e67 161 latest/stable canonical✓- gnome-3-38-2004 0+git.6f39565 119 latest/stable canonical✓- gnome-42-2204 0+git.09673a5 65 latest/stable canonical✓- gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓- gtk-theme-pocillo 0.14.4.15 latest/stable ubuntubudgie - gtk-theme-qogirbudgie 22.04.1 8 latest/stable ubuntubudgie - gtk2-common-themes0.1 13 latest/stable canonical✓- hunspell-dictionaries-1-7-20041.7-20.04+pkg-6fd6 2 latest/stable brlin - kde-frameworks-5-91-qt-5-15-3-core20 5.91.0 1 latest/stable kde✓ - kde-frameworks-5-99-qt-5-15-7-core20 5.99.0 15 latest/stable kde✓ - kde-frameworks-5-core18 5.67.0 35 latest/stable kde✓ - libreoffice 7.5.1.2 270 latest/stable canonical✓- shortwave 3.0.0 79 latest/stable alexmurray✪ - snapd 2.58.2 18357 latest/stable canonical✓snapd snapd-desktop-integration 0.1 71 latest/stable/… canonical✓- stellarium-daily v1.21396 latest/stable t4saha- thunderbird 102.9.0-1 305 latest/candidate canonical✓- vlc 3.0.18 3078 latest/stable videolan✓ - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011806/+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
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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 xorg-server package in Ubuntu: Incomplete 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:
[Desktop-packages] [Bug 2012832] Re: Xorg crashes on second and next unbind operations of Arc GPU
Definitely a crash, but not yet actionable: [ 220.992] (II) config/udev: removing GPU device /sys/devices/pci:00/:00:06.2/:02:00.0/:03:01.0/:04:00.0/drm/card1 /dev/dri/card1 [ 220.992] xf86: remove device 1 /sys/devices/pci:00/:00:06.2/:02:00.0/:03:01.0/:04:00.0/drm/card1 [ 220.992] (EE) [ 220.992] (EE) Backtrace: [ 220.995] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x561dfa9a3809] [ 220.996] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f0ed6842520] [ 220.997] (EE) 2: ? (?+0x0) [0x0] [ 220.997] (EE) [ 220.997] (EE) Segmentation fault at address 0x0 [ 220.997] (EE) Fatal server error: [ 220.997] (EE) Caught signal 11 (Segmentation fault). Server aborting ** Package changed: xorg (Ubuntu) => xorg-server (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/2012832 Title: Xorg crashes on second and next unbind operations of Arc GPU Status in xorg-server package in Ubuntu: Incomplete 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:
[Desktop-packages] [Bug 2012869] Re: Ubuntu font repeated many times
same problem for other fonts ** Attachment added: "Screenshot from 2023-03-27 08-03-38.png" https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/2012869/+attachment/5657667/+files/Screenshot%20from%202023-03-27%2008-03-38.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/2012869 Title: Ubuntu font repeated many times Status in gnome-font-viewer package in Ubuntu: New Bug description: In the page same Ubuntu font is repeated many times see screenshot ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-font-viewer 44~beta-1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 07:41:19 2023 InstallationDate: Installed on 2023-02-25 (29 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230224) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-font-viewer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/2012869/+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 2012809] Re: IBM/Lenovo Scrollpoint mouse insane fast scrolling speed
** Changed in: libinput (Ubuntu) Status: New => Fix Released ** Tags added: jammy rls-jj-incoming ** Tags added: fixed-in-libinput-1.21 fixed-upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/2012809 Title: IBM/Lenovo Scrollpoint mouse insane fast scrolling speed Status in libinput package in Ubuntu: Fix Released Bug description: Base: Ubuntu 22.04 jammy Package: libinput Version: 1.20.0 This bug is already fixed in upstream version 1.21 included in later Ubuntu versions and Debian "bookworm" base has been upgraded to 1.22, thus fixed. Previous Ubuntu LTS version "focal" is not affected. Please backport this simple fix into 22.04 "jammy" updates or upgrade to newer version like Debian "bookworm" base. Minimal effective fix patch attached. Complete upstream fix and issue: https://gitlab.freedesktop.org/libinput/libinput/-/merge_requests/778 Complete patch, but one unnecessary test file has rejection, due to other changes: https://gitlab.freedesktop.org/libinput/libinput/-/merge_requests/778.diff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/2012809/+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 2011806] Re: [lunar] Snaps don't launch due to cgroup issue
** Also affects: snapd (Ubuntu) Importance: Undecided Status: New ** Changed in: snapd (Ubuntu) Status: New => Won't Fix ** Also affects: kio (Ubuntu) Importance: Undecided Status: New ** Changed in: kio (Ubuntu) Status: New => Confirmed -- 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/2011806 Title: [lunar] Snaps don't launch due to cgroup issue Status in gnome-shell package in Ubuntu: In Progress Status in kio package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Won't Fix Bug description: Hi, Lunar up to date, Intel+Nvidia GPUs, Ubuntu Wayland or X11 session, hybrid or discrete graphics. If I click on a snap dash icon, nothing happens. Tested with Thunderbird, Firefox, Shortwave... (VS Code seems ok, maybe due to classic confinment?) I can launch without issue Chrome (deb), Synaptic, GNOME apps, etc. Recent updates included gnome-shell and libadwaita. --- I get this type of log for all problematic snaps: /user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome- shortwave_shortwave-11885.scope is not a snap cgroup --- Context: $ snap --version snap2.58.3+23.04ubuntu1 snapd 2.58.3+23.04ubuntu1 series 16 ubuntu 23.04 kernel 6.1.0-16-generic $ snap list Nom Version Révision Suivi Éditeur Notes bare 1.0 5 latest/stable canonical✓base code ee2b180d122 latest/stable vscode✓ classic core 16-2.58.2 14784 latest/stable canonical✓core core18202303082714 latest/stable canonical✓base core20202302071828 latest/stable canonical✓base core2220230210522 latest/stable canonical✓base firefox 111.0-2 2432 latest/candidate mozilla✓ - gimp 2.10.30 393 latest/stable snapcrafters - gnome-3-28-1804 3.28.0-19-g98f9e67.98f9e67 161 latest/stable canonical✓- gnome-3-38-2004 0+git.6f39565 119 latest/stable canonical✓- gnome-42-2204 0+git.09673a5 65 latest/stable canonical✓- gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓- gtk-theme-pocillo 0.14.4.15 latest/stable ubuntubudgie - gtk-theme-qogirbudgie 22.04.1 8 latest/stable ubuntubudgie - gtk2-common-themes0.1 13 latest/stable canonical✓- hunspell-dictionaries-1-7-20041.7-20.04+pkg-6fd6 2 latest/stable brlin - kde-frameworks-5-91-qt-5-15-3-core20 5.91.0 1 latest/stable kde✓ - kde-frameworks-5-99-qt-5-15-7-core20 5.99.0 15 latest/stable kde✓ - kde-frameworks-5-core18 5.67.0 35 latest/stable kde✓ - libreoffice 7.5.1.2 270 latest/stable canonical✓- shortwave 3.0.0 79 latest/stable alexmurray✪ - snapd 2.58.2 18357 latest/stable canonical✓snapd snapd-desktop-integration 0.1 71 latest/stable/… canonical✓- stellarium-daily v1.21396 latest/stable t4saha- thunderbird 102.9.0-1 305 latest/candidate canonical✓- vlc 3.0.18 3078 latest/stable videolan✓ - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011806/+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 2012733] Re: Unthemed and unscaled titlebars for server-side decorations in GNOME 44 Xorg sessions
** Summary changed: - Small unthemed titlebars for server-side decorations in Xorg sessions + Unthemed and unscaled titlebars for server-side decorations in GNOME 44 Xorg sessions -- 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/2012733 Title: Unthemed and unscaled titlebars for server-side decorations in GNOME 44 Xorg sessions Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Confirmed Bug description: Hi, Nvidia 530 (graphics ppa), dGPU mode, GS 44, Lunar X1 session: If I launch Synaptic or ChessX, eg., the title bar is Adwaita-styled (greyish + icons). No issue with GNOME apps (and some other like FF or TB snaps, etc.). Wayland session: all is ok (except many other bugs!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012733/+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 2012670] Re: plymouth: font missing at decrypt root prompt
** Changed in: plymouth (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/2012670 Title: plymouth: font missing at decrypt root prompt Status in plymouth package in Ubuntu: Fix Released Bug description: Fonts are missing (incorrectly displayed) at the plymouth splash screen when prompting for the luks decryption passphrase (ie just below the input box). I have the same issue on my laptop (where this report has been generated) and my desktop (where the photo is from). ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: plymouth 22.02.122-3ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 23 19:40:58 2023 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2023-03-14 (9 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 20XW0055UK ProcCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth UpgradeStatus: Upgraded to lunar on 2023-03-22 (1 days ago) dmi.bios.date: 02/09/2023 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET83W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XW0055UK dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET83W(1.59):bd02/09/2023:br1.59:efr1.33:svnLENOVO:pn20XW0055UK:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XW0055UK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XW0055UK dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2012670/+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 2012733] Re: Small unthemed titlebars for server-side decorations in Xorg sessions
Are we missing custom theming in Yaru for mutter-x11-frames in GNOME 44? ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Confirmed ** Also affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Changed in: yaru-theme (Ubuntu) Status: New => Confirmed ** Changed in: mutter (Ubuntu) Milestone: None => ubuntu-23.04 ** Changed in: gnome-shell (Ubuntu) Milestone: ubuntu-23.04-beta => ubuntu-23.04 ** Changed in: yaru-theme (Ubuntu) Milestone: None => ubuntu-23.04 -- 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/2012733 Title: Small unthemed titlebars for server-side decorations in Xorg sessions Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Confirmed Bug description: Hi, Nvidia 530 (graphics ppa), dGPU mode, GS 44, Lunar X1 session: If I launch Synaptic or ChessX, eg., the title bar is Adwaita-styled (greyish + icons). No issue with GNOME apps (and some other like FF or TB snaps, etc.). Wayland session: all is ok (except many other bugs!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012733/+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
