[Desktop-packages] [Bug 2054510] Re: Incomplete screen redraws in virtual machines running Xorg
Thanks for the fix! -- 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/2054510 Title: Incomplete screen redraws in virtual machines running Xorg Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Mantic: Fix Committed Status in mutter source package in Noble: Fix Committed Bug description: [ Impact ] When using software rendering on Xorg (so usually just in VMs), some parts of app windows may fail to redraw. https://gitlab.gnome.org/GNOME/mutter/-/issues/2880 [ Test Plan ] 1. Set up a virtual machine without graphics acceleration. 2. Log into 'Ubuntu on Xorg'. 3. Open Settings > About and verify Graphics = llvmpipe (or "Software Rendering"), and Windowing System = X11. 4. sudo snap install chromium 5. Open Chromium and find a web page with lots of text. Plain text without any links and staying at the top of the page will work best because you don't want to trigger any scrolling. 6. Start selecting text with the mouse and while holding the button move the mouse up and down rapidly. Avoid triggering any page scrolling. 7. Release the mouse button in roughly the middle of the area of text that was selected. 8. Verify the remaining text selection is contiguous and not broken into multiple disconnected text selections (the bug). 9. Repeat steps 7 and 8 several times to be sure. [ Where problems could occur ] The fix adds a new synchronization point between the compositor and X server. This should be inconsequential, although there is a "sync ring" in mutter used for this, and if a mistake occurs there then other parts of the desktop could appear to stop responding in Xorg sessions. [ Other Info ] This is a regression that started in 3.37.3 due to https://gitlab.gnome.org/GNOME/mutter/-/commit/551101c65cda. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054510/+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 1971434] Re: Display powersave only blanks, but does not turn off
Yes I too have believed for years there must be a feedback problem causing this. The reason it's still not fixed is just that it's so rare... every time I try to debug it the problem doesn't happen at all. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1971434 Title: Display powersave only blanks, but does not turn off Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Recently upgraded to Ubuntu 22.04, and it seems like the power-saving feature in Gnome 42 does not actually turn off the screen(s) after X minutes, but just blanks them. When I manually run `xset dpms force off`, they do properly turn off and go to powersave mode. 1) Description: Ubuntu 22.04 LTS Release: 22.04 2) gnome-settings-daemon: Installed: 42.1-1ubuntu2 Candidate: 42.1-1ubuntu2 3) In Settings -> Power -> Screen Blank, set the inactivity period to 5 minutes. After 5 minutes, the screens should turn off. 4) Screens go black, but remain active and consume (too much) power. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-07-04 (667 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: gnome-settings-daemon 42.1-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-30 (3 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers video wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+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 2040472] Re: Backport packages from noble(-devel) to server-backports PPA for focal and jammy, post-FF
** Changed in: rdma-core (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: spice-vdagent (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/2040472 Title: Backport packages from noble(-devel) to server-backports PPA for focal and jammy, post-FF Status in dpdk package in Ubuntu: New Status in edk2 package in Ubuntu: New Status in libslirp package in Ubuntu: New Status in libvirt package in Ubuntu: New Status in libvirt-python package in Ubuntu: New Status in meson package in Ubuntu: New Status in openvswitch package in Ubuntu: New Status in qemu package in Ubuntu: New Status in rdma-core package in Ubuntu: New Status in seabios package in Ubuntu: New Status in spice package in Ubuntu: New Status in spice-protocol package in Ubuntu: New Status in spice-vdagent package in Ubuntu: New Status in virglrenderer package in Ubuntu: New Status in virt-manager package in Ubuntu: New Status in dpdk source package in Focal: New Status in edk2 source package in Focal: New Status in libslirp source package in Focal: New Status in libvirt source package in Focal: New Status in libvirt-python source package in Focal: New Status in meson source package in Focal: New Status in openvswitch source package in Focal: New Status in qemu source package in Focal: New Status in rdma-core source package in Focal: New Status in seabios source package in Focal: New Status in spice source package in Focal: New Status in spice-protocol source package in Focal: New Status in spice-vdagent source package in Focal: New Status in virglrenderer source package in Focal: New Status in virt-manager source package in Focal: New Status in dpdk source package in Jammy: In Progress Status in edk2 source package in Jammy: Fix Committed Status in libslirp source package in Jammy: Fix Committed Status in libvirt source package in Jammy: Fix Committed Status in libvirt-python source package in Jammy: Fix Committed Status in meson source package in Jammy: New Status in openvswitch source package in Jammy: New Status in qemu source package in Jammy: Fix Committed Status in rdma-core source package in Jammy: Fix Committed Status in seabios source package in Jammy: Fix Committed Status in spice source package in Jammy: Fix Committed Status in spice-protocol source package in Jammy: New Status in spice-vdagent source package in Jammy: In Progress Status in virglrenderer source package in Jammy: New Status in virt-manager source package in Jammy: New Bug description: Backport the following packages to the server-backports PPA for noble:* ['meson', 'dpdk', 'edk2', 'libslirp', 'libvirt', 'libvirt- python', 'openvswitch', 'qemu', 'rdma-core', 'seabios', 'spice', 'spice-protocol', 'spice-vdagent', 'virglrenderer', 'virt-manager'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2040472/+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 2059033] Re: Xorg crashes with SIGABRT
** Changed in: mesa Status: Unknown => 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/2059033 Title: Xorg crashes with SIGABRT Status in Mesa: New Status in mesa package in Ubuntu: New Bug description: I am running an Intel Kabylake CPU with Ubuntu 22.04, and i915 graphics driver. I am seeing random Xorg crashes due to SIGABRT, which kicks me back to the login screen. Ubuntu version: 22.04 Kernel version: 5.19.0-50-generic libgl1-mesa-dri version: 23.0.4-0ubuntu1~22.04.1 I am seeing this message in kern.log: i915 :00:02.0: [drm] GPU HANG: ecode 9:1:85db, in Xorg [1617] I have also gotten a core dump; here is the track trace: #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=140131874372224, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x7f72fec42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x7f72fec287f3 in __GI_abort () at ./stdlib/abort.c:79 #5 0x560c5cc756a0 in OsAbort () at ../../../../os/utils.c:1352 #6 0x560c5cc7aea9 in AbortServer () at ../../../../os/log.c:879 #7 0x560c5cc7be9a in FatalError (f=f@entry=0x560c5ccadc10 "Caught signal %d (%s). Server aborting\n") at ../../../../os/log.c:1017 #8 0x560c5cc72abd in OsSigHandler (unused=, sip=0x713ae7b0, signo=6) at ../../../../os/osinit.c:156 #9 OsSigHandler (signo=6, sip=0x713ae7b0, unused=) at ../../../../os/osinit.c:110 #10 #11 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:44 #12 __pthread_kill_internal (signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:78 #13 __GI___pthread_kill (threadid=140131874372224, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #14 0x7f72fec42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #15 0x7f72fec287f3 in __GI_abort () at ./stdlib/abort.c:79 #16 0x7f72fc49d86d in _iris_batch_flush (batch=0x560c5e916118, file=, line=) at ../src/gallium/drivers/iris/iris_batch.c:1116 #17 0x7f72fd1da6ff in iris_fence_flush (ctx=0x560c5e915be0, out_fence=0x0, flags=) at ../src/gallium/drivers/iris/iris_fence.c:267 #18 0x7f72fc55f127 in st_flush (flags=0, fence=0x0, st=0x560c5e93bbc0) at ../src/mesa/state_tracker/st_cb_flush.c:60 #19 st_glFlush (ctx=, gallium_flush_flags=0) at ../src/mesa/state_tracker/st_cb_flush.c:94 #20 0x7f72fe56b604 in _glamor_block_handler (screen=0x560c5e8655a0, timeout=0x713af054) at ../../../../glamor/glamor.c:285 #21 0x7f72fe5a6157 in msBlockHandler (pScreen=0x560c5e8655a0, timeout=0x713af054) at ../../../../../../../hw/xfree86/drivers/modesetting/driver.c:701 #22 0x560c5cb01095 in BlockHandler (pTimeout=pTimeout@entry=0x713af054) at ../../../../dix/dixutils.c:394 #23 0x560c5cc6c0c9 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:201 #24 0x560c5cafc3e7 in Dispatch () at ../../../../dix/dispatch.c:492 #25 0x560c5cb006b4 in dix_main (argc=11, argv=0x713af268, envp=) at ../../../../dix/main.c:272 #26 0x7f72fec29d90 in __libc_start_call_main (main=main@entry=0x560c5cae95d0 , argc=argc@entry=11, argv=argv@entry=0x713af268) at ../sysdeps/nptl/libc_start_call_main.h:58 #27 0x7f72fec29e40 in __libc_start_main_impl (main=0x560c5cae95d0 , argc=11, argv=0x713af268, init=, fini=, rtld_fini=, stack_end=0x713af258) at ../csu/libc-start.c:392 #28 0x560c5cae9605 in _start () This post describes a similar issue: https://gitlab.freedesktop.org/drm/intel/-/issues/4858 I tried using a workaround from the above link, to set GPU to max frequency using command "intel_gpu_frequency -m", this seemed to reduce the rate of occurrence from once per day to once every 3 days, but this is not a permanent solution. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2059033/+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 2057836] Re: gst-python1.0 fails to build: test failures
same test failures with pygobject 3.48.1-1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/2057836 Title: gst-python1.0 fails to build: test failures Status in pygobject: New Status in gst-python1.0 package in Ubuntu: Triaged Status in pygobject package in Ubuntu: Triaged Status in gst-python1.0 package in Debian: Confirmed Bug description: gst-python1.0 fails to build because of test failures. https://launchpad.net/ubuntu/+source/gst-python1.0/1.22.10-1build1 https://launchpad.net/ubuntu/+source/gst-python1.0/1.24.0-1 I have reported the issue to the upstream developers https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3353 To manage notifications about this bug go to: https://bugs.launchpad.net/pygobject/+bug/2057836/+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 2059033] Re: Xorg crashes with SIGABRT
** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #4858 https://gitlab.freedesktop.org/drm/intel/-/issues/4858 ** Also affects: mesa via https://gitlab.freedesktop.org/drm/intel/-/issues/4858 Importance: Unknown Status: Unknown -- 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/2059033 Title: Xorg crashes with SIGABRT Status in Mesa: Unknown Status in mesa package in Ubuntu: New Bug description: I am running an Intel Kabylake CPU with Ubuntu 22.04, and i915 graphics driver. I am seeing random Xorg crashes due to SIGABRT, which kicks me back to the login screen. Ubuntu version: 22.04 Kernel version: 5.19.0-50-generic libgl1-mesa-dri version: 23.0.4-0ubuntu1~22.04.1 I am seeing this message in kern.log: i915 :00:02.0: [drm] GPU HANG: ecode 9:1:85db, in Xorg [1617] I have also gotten a core dump; here is the track trace: #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=140131874372224, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x7f72fec42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x7f72fec287f3 in __GI_abort () at ./stdlib/abort.c:79 #5 0x560c5cc756a0 in OsAbort () at ../../../../os/utils.c:1352 #6 0x560c5cc7aea9 in AbortServer () at ../../../../os/log.c:879 #7 0x560c5cc7be9a in FatalError (f=f@entry=0x560c5ccadc10 "Caught signal %d (%s). Server aborting\n") at ../../../../os/log.c:1017 #8 0x560c5cc72abd in OsSigHandler (unused=, sip=0x713ae7b0, signo=6) at ../../../../os/osinit.c:156 #9 OsSigHandler (signo=6, sip=0x713ae7b0, unused=) at ../../../../os/osinit.c:110 #10 #11 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:44 #12 __pthread_kill_internal (signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:78 #13 __GI___pthread_kill (threadid=140131874372224, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #14 0x7f72fec42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #15 0x7f72fec287f3 in __GI_abort () at ./stdlib/abort.c:79 #16 0x7f72fc49d86d in _iris_batch_flush (batch=0x560c5e916118, file=, line=) at ../src/gallium/drivers/iris/iris_batch.c:1116 #17 0x7f72fd1da6ff in iris_fence_flush (ctx=0x560c5e915be0, out_fence=0x0, flags=) at ../src/gallium/drivers/iris/iris_fence.c:267 #18 0x7f72fc55f127 in st_flush (flags=0, fence=0x0, st=0x560c5e93bbc0) at ../src/mesa/state_tracker/st_cb_flush.c:60 #19 st_glFlush (ctx=, gallium_flush_flags=0) at ../src/mesa/state_tracker/st_cb_flush.c:94 #20 0x7f72fe56b604 in _glamor_block_handler (screen=0x560c5e8655a0, timeout=0x713af054) at ../../../../glamor/glamor.c:285 #21 0x7f72fe5a6157 in msBlockHandler (pScreen=0x560c5e8655a0, timeout=0x713af054) at ../../../../../../../hw/xfree86/drivers/modesetting/driver.c:701 #22 0x560c5cb01095 in BlockHandler (pTimeout=pTimeout@entry=0x713af054) at ../../../../dix/dixutils.c:394 #23 0x560c5cc6c0c9 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:201 #24 0x560c5cafc3e7 in Dispatch () at ../../../../dix/dispatch.c:492 #25 0x560c5cb006b4 in dix_main (argc=11, argv=0x713af268, envp=) at ../../../../dix/main.c:272 #26 0x7f72fec29d90 in __libc_start_call_main (main=main@entry=0x560c5cae95d0 , argc=argc@entry=11, argv=argv@entry=0x713af268) at ../sysdeps/nptl/libc_start_call_main.h:58 #27 0x7f72fec29e40 in __libc_start_main_impl (main=0x560c5cae95d0 , argc=11, argv=0x713af268, init=, fini=, rtld_fini=, stack_end=0x713af258) at ../csu/libc-start.c:392 #28 0x560c5cae9605 in _start () This post describes a similar issue: https://gitlab.freedesktop.org/drm/intel/-/issues/4858 I tried using a workaround from the above link, to set GPU to max frequency using command "intel_gpu_frequency -m", this seemed to reduce the rate of occurrence from once per day to once every 3 days, but this is not a permanent solution. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2059033/+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 2058691] Re: No sound card detected on the Dell xps 16 2024 (9640)
I think sof-mtl-rt711-4ch.tplg and sof-mtl-rt711.tplg aren't the same thing. I'm guessing the former is for devices with four audio channels? I'm on arch with a sof-mtl-rt711-4ch.tplg and another file beginning with "sof-mtl-rt711", but no "sof-mtl-rt711.tplg". Renaming either of them to sof-mtl-rt711 produces the same error. Also, googling "sof-mtl- rt711" reveals an internal Intel document mentioning the existence of this file, so I'd imagine Intel hasn't released the file yet. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2058691 Title: No sound card detected on the Dell xps 16 2024 (9640) Status in alsa-driver package in Ubuntu: New Bug description: The sound card is not detected on the Dell XPS 16 2024 (9640). A Cirrus Logic CS42L43 card is used which apparently got support in Linux 6.6 https://www.google.com/url?sa=t=web=j=89978449=https://www.phoronix.com/forums/forum/software/general- linux-open-source/1408193-linux-6-6-lands-support-for-the-cirrus- logic-cs42l43-audio-codec=2ahUKEwiukq-ZroaFAxUWhf0HHe- jCngQFnoECA8QAQ=AOvVaw3VW5hROJFzdJPUaIX-3igC https://www.reddit.com/r/DellXPS/comments/1ax1i4t/support_for_xps_16_9640_documentation/ No LSB modules are available. Description: Ubuntu Noble Numbat (development branch) Release: 24.04 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 21 23:00:06 2024 InstallationDate: Installed on 2024-03-19 (2 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240319) MachineType: Dell Inc. XPS 16 9640 PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2024 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.0 dmi.board.name: 0YFT36 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnDellInc.:bvr1.1.0:bd01/15/2024:br1.1:efr1.2:svnDellInc.:pnXPS169640:pvr:rvnDellInc.:rn0YFT36:rvrA00:cvnDellInc.:ct10:cvr:sku0C62: dmi.product.family: XPS dmi.product.name: XPS 16 9640 dmi.product.sku: 0C62 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2058691/+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 2059033] [NEW] Xorg crashes with SIGABRT
Public bug reported: I am running an Intel Kabylake CPU with Ubuntu 22.04, and i915 graphics driver. I am seeing random Xorg crashes due to SIGABRT, which kicks me back to the login screen. Ubuntu version: 22.04 Kernel version: 5.19.0-50-generic libgl1-mesa-dri version: 23.0.4-0ubuntu1~22.04.1 I am seeing this message in kern.log: i915 :00:02.0: [drm] GPU HANG: ecode 9:1:85db, in Xorg [1617] I have also gotten a core dump; here is the track trace: #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=140131874372224, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x7f72fec42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x7f72fec287f3 in __GI_abort () at ./stdlib/abort.c:79 #5 0x560c5cc756a0 in OsAbort () at ../../../../os/utils.c:1352 #6 0x560c5cc7aea9 in AbortServer () at ../../../../os/log.c:879 #7 0x560c5cc7be9a in FatalError (f=f@entry=0x560c5ccadc10 "Caught signal %d (%s). Server aborting\n") at ../../../../os/log.c:1017 #8 0x560c5cc72abd in OsSigHandler (unused=, sip=0x713ae7b0, signo=6) at ../../../../os/osinit.c:156 #9 OsSigHandler (signo=6, sip=0x713ae7b0, unused=) at ../../../../os/osinit.c:110 #10 #11 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:44 #12 __pthread_kill_internal (signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:78 #13 __GI___pthread_kill (threadid=140131874372224, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #14 0x7f72fec42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #15 0x7f72fec287f3 in __GI_abort () at ./stdlib/abort.c:79 #16 0x7f72fc49d86d in _iris_batch_flush (batch=0x560c5e916118, file=, line=) at ../src/gallium/drivers/iris/iris_batch.c:1116 #17 0x7f72fd1da6ff in iris_fence_flush (ctx=0x560c5e915be0, out_fence=0x0, flags=) at ../src/gallium/drivers/iris/iris_fence.c:267 #18 0x7f72fc55f127 in st_flush (flags=0, fence=0x0, st=0x560c5e93bbc0) at ../src/mesa/state_tracker/st_cb_flush.c:60 #19 st_glFlush (ctx=, gallium_flush_flags=0) at ../src/mesa/state_tracker/st_cb_flush.c:94 #20 0x7f72fe56b604 in _glamor_block_handler (screen=0x560c5e8655a0, timeout=0x713af054) at ../../../../glamor/glamor.c:285 #21 0x7f72fe5a6157 in msBlockHandler (pScreen=0x560c5e8655a0, timeout=0x713af054) at ../../../../../../../hw/xfree86/drivers/modesetting/driver.c:701 #22 0x560c5cb01095 in BlockHandler (pTimeout=pTimeout@entry=0x713af054) at ../../../../dix/dixutils.c:394 #23 0x560c5cc6c0c9 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:201 #24 0x560c5cafc3e7 in Dispatch () at ../../../../dix/dispatch.c:492 #25 0x560c5cb006b4 in dix_main (argc=11, argv=0x713af268, envp=) at ../../../../dix/main.c:272 #26 0x7f72fec29d90 in __libc_start_call_main (main=main@entry=0x560c5cae95d0 , argc=argc@entry=11, argv=argv@entry=0x713af268) at ../sysdeps/nptl/libc_start_call_main.h:58 #27 0x7f72fec29e40 in __libc_start_main_impl (main=0x560c5cae95d0 , argc=11, argv=0x713af268, init=, fini=, rtld_fini=, stack_end=0x713af258) at ../csu/libc-start.c:392 #28 0x560c5cae9605 in _start () This post describes a similar issue: https://gitlab.freedesktop.org/drm/intel/-/issues/4858 I tried using a workaround from the above link, to set GPU to max frequency using command "intel_gpu_frequency -m", this seemed to reduce the rate of occurrence from once per day to once every 3 days, but this is not a permanent solution. ** 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/2059033 Title: Xorg crashes with SIGABRT Status in mesa package in Ubuntu: New Bug description: I am running an Intel Kabylake CPU with Ubuntu 22.04, and i915 graphics driver. I am seeing random Xorg crashes due to SIGABRT, which kicks me back to the login screen. Ubuntu version: 22.04 Kernel version: 5.19.0-50-generic libgl1-mesa-dri version: 23.0.4-0ubuntu1~22.04.1 I am seeing this message in kern.log: i915 :00:02.0: [drm] GPU HANG: ecode 9:1:85db, in Xorg [1617] I have also gotten a core dump; here is the track trace: #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=140131874372224, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x7f72fec42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x7f72fec287f3 in __GI_abort () at
[Desktop-packages] [Bug 991471] Re: multi-device btrfs filesystem automatically mounted once for each device
The problem is not confined to Ubuntu. I am seeing the same problem in Fedora SilverBlue 38 and Fedora SilverBlue 39. The problem is restricted to `btrfs` only; other partitions such as ext3, ext4, NTFS look fine. -- 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/991471 Title: multi-device btrfs filesystem automatically mounted once for each device Status in btrfs package in Ubuntu: Invalid Status in btrfs-tools package in Ubuntu: Confirmed Status in gvfs package in Ubuntu: Confirmed Status in udev package in Ubuntu: Confirmed Status in udisks2 package in Ubuntu: Confirmed Bug description: If I have a multi-device btrfs filesystem, and I plug it in via some removable interface (for example, USB3), it will automatically mount on the desktop multiple times. For example, if I have a filesystem labeled FooBar on /dev/sdb /dev/sdc /dev/sdd and /dev/sde, it will be mounted as /media/FooBar, /media/FooBar1, /media/FooBar2, and /media/FooBar3. It should show up only once. It seems like everything still basically works, but I didn't test writing to said filesystem under the different aliases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/btrfs/+bug/991471/+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 2057836] Re: gst-python1.0 fails to build: test failures
Debian added a b-d on pygobject >= 3.48.1, which we don't have -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/2057836 Title: gst-python1.0 fails to build: test failures Status in pygobject: New Status in gst-python1.0 package in Ubuntu: Triaged Status in pygobject package in Ubuntu: Triaged Status in gst-python1.0 package in Debian: Confirmed Bug description: gst-python1.0 fails to build because of test failures. https://launchpad.net/ubuntu/+source/gst-python1.0/1.22.10-1build1 https://launchpad.net/ubuntu/+source/gst-python1.0/1.24.0-1 I have reported the issue to the upstream developers https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3353 To manage notifications about this bug go to: https://bugs.launchpad.net/pygobject/+bug/2057836/+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 1971434] Re: Display powersave only blanks, but does not turn off
I can confirm with #47, I have dual system on the same machine, Windows is works without issue, and Ubuntu does have. My monitor is HDMI but not Lenovo. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1971434 Title: Display powersave only blanks, but does not turn off Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Recently upgraded to Ubuntu 22.04, and it seems like the power-saving feature in Gnome 42 does not actually turn off the screen(s) after X minutes, but just blanks them. When I manually run `xset dpms force off`, they do properly turn off and go to powersave mode. 1) Description: Ubuntu 22.04 LTS Release: 22.04 2) gnome-settings-daemon: Installed: 42.1-1ubuntu2 Candidate: 42.1-1ubuntu2 3) In Settings -> Power -> Screen Blank, set the inactivity period to 5 minutes. After 5 minutes, the screens should turn off. 4) Screens go black, but remain active and consume (too much) power. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-07-04 (667 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: gnome-settings-daemon 42.1-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-30 (3 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers video wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 2051570] Re: [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound
Hello Hui Wang, yeah unfortunately i think it's a hardware issue since i tried windows and fedora but same thing. For the bluetooth headphone (Redmi buds 4 active) in windows and fedora works fine, in ubuntu even if I set output a configuration to HSP/HFP instead of A2DP mic doesn't work, the only way to get it work is to remove the device from bluetooth settings and set it up again. I recorded a short video for the issue : https://youtu.be/cZaSqgFJ-Gw On Sat, Mar 23, 2024 at 1:20 AM Hui Wang <2051...@bugs.launchpad.net> wrote: > Please upload a complete dmesg with the kernel you updated on 19/03/2024 > (dummy output). > > And could you also test the latest upstream mainline kernel or ubuntu > 24.04 (just put the iso to usb flash drive, boot from it and try ubuntu > 24.04, no need to install). > > https://kernel.ubuntu.com/mainline/v6.8/ > > > And also, it looks like a hardware issue to me. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2051570 > > Title: > [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] > Underruns, dropouts or crackling sound > > Status in alsa-driver package in Ubuntu: > New > > Bug description: > Since the last three weeks' updates, I have encountered several > challenges with the audio functionality on my system. Primarily, upon > starting my laptop, the audio often fails to work, displaying "Dummy > Output." To resolve this, I find myself needing to restart the laptop > two or three times before the audio becomes functional. > > Even when the audio is working, I've noticed a recurring issue where, > after playing video or audio for approximately 2-3 minutes, the sound > starts crackling and buzzing. The intensity of these distortions > gradually increases, resembling the static interference on a radio > station with a weak signal. This issue persists even when using 3.5mm > headphones, requiring the use of a USB headset or Bluetooth headphones > to enjoy distortion-free audio. > > Furthermore, I have observed that, regardless of the Ubuntu version > (ranging from 22.04 to 22.04.3), I face difficulties changing the > microphone output settings when an external audio peripheral, such as > a USB headset, 3.5mm headphones, or Bluetooth headphones, is > connected. The OS appears to exclusively utilize the microphone from > the connected peripheral, making it impossible to switch to the > laptop's built-in microphone. > > For your reference, here are the specifications of my laptop and the > Ubuntu version I am currently using: > > Laptop: Dell Vostro 3400 > CPU: 11th Gen Intel i5-1135G7 > GPU: Intel TigerLake-LP GT2 Iris Xe > Memory: 2490MiB / 19720MiB > Resolution: 1920x1080 > OS: Ubuntu 22.04.3 LTS x86_64 > Kernel: 6.5.0-14-generic > DE: GNOME 42.9 > Shell: bash 5.1.16 > Sound Card: Card: HDA Intel PCH, Chip: Cirrus Logic CS8409/CS42L42 > > **UPDATE 12/02/2024 Noticed that every time my laptop fan starts > spinning the crackling sound appears, after fan stops the crackling sound > disappear. > **UPDATE 19/03/2024 I did a software update to the linux kernel > 6.5.0-26, now i get a dummy output in sound even if i restart the system > many times, and if i use my Bluetooth headphone i can't use the mic, > neither the mic of the laptop or of the headphone (there is no option is > the settings to choose from) it's all blank. > > ProblemType: Bug > DistroRelease: Ubuntu 22.04 > Package: alsa-base 1.0.25+dfsg-0ubuntu7 > ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 > Uname: Linux 6.5.0-15-generic x86_64 > ApportVersion: 2.20.11-0ubuntu82.5 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: galxy-a10 1437 F pulseaudio > CasperMD5CheckResult: pass > CurrentDesktop: ubuntu:GNOME > Date: Mon Jan 29 17:50:44 2024 > InstallationDate: Installed on 2024-01-16 (13 days ago) > InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 > (20230807.2) > PackageArchitecture: all > SourcePackage: alsa-driver > Symptom: audio > Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH > successful > Symptom_Card: Built-in Audio - HDA Intel PCH > Symptom_Jack: Speaker, Internal > Symptom_PulseAudioLog: جانفي 29 17:49:49 galxya10-VR > whoopsie-upload-all[712]: > INFO:root:/var/crash/_usr_bin_pulseaudio.1000.crash already marked for > upload, skipping > Symptom_PulsePlaybackTest: PulseAudio playback test successful > Symptom_Type: Underruns, dropouts, or "crackling" sound > Title: [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] > Underruns, dropouts or crackling sound > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 10/03/2023 > dmi.bios.release: 1.27 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 1.27.1 > dmi.board.name: 0GGCMJ >
[Desktop-packages] [Bug 2058930] Re: Missing in i386 Packages index
Actually, this seems to be an issue of the source package not being pulled from -proposed, as I can install the binaries just fine in a LXD container: root@nn:~# dpkg --add-architecture i386 root@nn:~# apt update [...] root@nn:~# apt install libvpx9:i386 Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: libnsl-dev libtirpc-dev Use 'apt autoremove' to remove them. The following additional packages will be installed: gcc-14-base:i386 libc-bin libc-dev-bin libc-devtools libc6 libc6:i386 libc6-dev libgcc-s1:i386 libidn2-0:i386 libunistring5:i386 locales Suggested packages: glibc-doc glibc-doc:i386 locales:i386 libnss-nis:i386 libnss-nisplus:i386 The following NEW packages will be installed: gcc-14-base:i386 libc6:i386 libgcc-s1:i386 libidn2-0:i386 libunistring5:i386 libvpx9:i386 The following packages will be upgraded: libc-bin libc-dev-bin libc-devtools libc6 libc6-dev locales 6 upgraded, 6 newly installed, 0 to remove and 7 not upgraded. Need to get 15.3 MB of archives. After this operation, 18.6 MB of additional disk space will be used. Do you want to continue? [Y/n] [...] Get:12 http://archive.ubuntu.com/ubuntu noble-proposed/main i386 libvpx9 i386 1.14.0-1ubuntu1 [1129 kB] 0 root@nn:~# apt-get source libvpx Reading package lists... Done NOTICE: 'libvpx' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/multimedia-team/libvpx.git Please use: git clone https://salsa.debian.org/multimedia-team/libvpx.git to retrieve the latest (possibly unreleased) updates to the package. Need to get 4332 kB of source archives. Get:1 http://archive.ubuntu.com/ubuntu noble/main libvpx 1.13.1-2ubuntu1 (dsc) [2366 B] Get:2 http://archive.ubuntu.com/ubuntu noble/main libvpx 1.13.1-2ubuntu1 (tar) [4316 kB] Get:3 http://archive.ubuntu.com/ubuntu noble/main libvpx 1.13.1-2ubuntu1 (diff) [13.6 kB] Fetched 4332 kB in 1s (8427 kB/s) dpkg-source: info: extracting libvpx in libvpx-1.13.1 dpkg-source: info: unpacking libvpx_1.13.1.orig.tar.xz dpkg-source: info: unpacking libvpx_1.13.1-2ubuntu1.debian.tar.xz dpkg-source: info: using patch list from debian/patches/series dpkg-source: info: applying 0001-Relax-ABI-check.patch dpkg-source: info: applying 0002-Do-not-undefine-_FORTIFY_SOURCE.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libvpx in Ubuntu. https://bugs.launchpad.net/bugs/2058930 Title: Missing in i386 Packages index Status in libvpx package in Ubuntu: New Bug description: The new version of libvpx 1.14 seems not to be published to http://ftpmaster.internal on i386 only. This leads to the autopkgtest trigger "libvpx/1.14.0-1ubuntu1", not having any effect on i386: https://autopkgtest.ubuntu.com/packages/libvpx/noble/i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/2058930/+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 2058930] Re: Missing in i386 Packages index
** Description changed: - The new version of libvpx 1.14 seems to be missing in - http://archive.ubuntu.com/ubuntu/dists/noble- - proposed/main/binary-i386/Packages.xz, while it's still available in - http://archive.ubuntu.com/ubuntu/dists/noble- - proposed/main/binary-i386/Packages.gz. - - Grep for "Source: libvpx". + The new version of libvpx 1.14 seems not to be published to + http://ftpmaster.internal on i386 only. This leads to the autopkgtest trigger "libvpx/1.14.0-1ubuntu1", not having any effect on i386: https://autopkgtest.ubuntu.com/packages/libvpx/noble/i386 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libvpx in Ubuntu. https://bugs.launchpad.net/bugs/2058930 Title: Missing in i386 Packages index Status in libvpx package in Ubuntu: New Bug description: The new version of libvpx 1.14 seems not to be published to http://ftpmaster.internal on i386 only. This leads to the autopkgtest trigger "libvpx/1.14.0-1ubuntu1", not having any effect on i386: https://autopkgtest.ubuntu.com/packages/libvpx/noble/i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/2058930/+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 2058930] [NEW] Missing in i386 Packages index
Public bug reported: The new version of libvpx 1.14 seems not to be published to http://ftpmaster.internal on i386 only. This leads to the autopkgtest trigger "libvpx/1.14.0-1ubuntu1", not having any effect on i386: https://autopkgtest.ubuntu.com/packages/libvpx/noble/i386 ** Affects: libvpx (Ubuntu) Importance: Undecided Status: New ** Tags: rls-nn-incoming update-excuse ** Tags added: rls-nn-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libvpx in Ubuntu. https://bugs.launchpad.net/bugs/2058930 Title: Missing in i386 Packages index Status in libvpx package in Ubuntu: New Bug description: The new version of libvpx 1.14 seems not to be published to http://ftpmaster.internal on i386 only. This leads to the autopkgtest trigger "libvpx/1.14.0-1ubuntu1", not having any effect on i386: https://autopkgtest.ubuntu.com/packages/libvpx/noble/i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/2058930/+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 2055148] Re: NetworkManager connections with an explicit DoT (DNS over TLS) are not supported with Netplan
** Tags added: fr-7190 -- 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/2055148 Title: NetworkManager connections with an explicit DoT (DNS over TLS) are not supported with Netplan Status in Netplan: Triaged Status in netplan.io package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: From: https://discourse.ubuntu.com/t/blog-netplan-developer- diaries/35932/11 Hi all, NetworkManager connections with an explicit DoT (DNS over TLS) configuration are not supported with Netplan, but NetworkManager does feed back the DoT DNS info with server address and Server Name Indication (SNI) in the form server_address#SNI, e.g. 1.2.3.4#dns.myhome.com as nameserver addresses to Netplan. As a result, subsequent Netplan config applications fail because DNS servers don’t have the expected dotted decimal (IPv4) or colon’ed hex (IPv6) form. ``` nmcli> describe ipv4.dns === [dns] === [NM property description] Array of IP addresses of DNS servers. For DoT (DNS over TLS), the SNI server name can be specified by appending "#example.com" to the IP address of the DNS server. This currently only has effect when using systemd-resolved. ``` To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2055148/+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 2058923] Re: Clicking 'App Details' from the Apps tab does not work
Thanks, it's a feature that is currently missing from the new app- center, https://github.com/ubuntu/app-center/issues/1356 We might need to update the settings side to remove that action ** Bug watch added: github.com/ubuntu/app-center/issues #1356 https://github.com/ubuntu/app-center/issues/1356 ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low -- 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/2058923 Title: Clicking 'App Details' from the Apps tab does not work Status in gnome-control-center package in Ubuntu: New Bug description: This was tested on Ubuntu 24.04 with all current updates applied. To reproduce the issue: - Open gnome-control-centre - Navigate to the 'Apps' section - Click on any app - Click the 'App Details' button The system will open the snap-store front-page, but won't show the given apps details. This seems to be the same for both .deb and Snap packages. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-control-center 1:46~beta-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 25 11:05:37 2024 ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/usr/local/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2058923/+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 2058409] Re: Install of tevlive-full hangs: tex/context/base/mkiv/l-sandbox.lua:180: module 'socket.core' not found
I came across this bug while trying to install texlive-full. The installation process would hang on this line: Pregenerating ConTeXt MarkIV format. This may take some time... Running luatex manually as listed above results in an identical stack trace. While doing so I typed 'quit' at the debugger prompt '?'. Doing so resulted in the program continuing to run till the end with no more errors. I then tried to install texlive-full again, and at the point where it would hang earlier, I typed 'quit' then the Enter key. This made the configuration of the context package continue, followed by context- modules and then texlive-full. All other packages pulled in by texlive- full installed successfully earlier. The bug can be reproduced by doing 'sudo apt-get install context'. As of now the installation of texlive-full has completed as far as apt- get is concerned, but I guess the context package is broken. Hope this information helps. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/2058409 Title: Install of tevlive-full hangs: tex/context/base/mkiv/l-sandbox.lua:180: module 'socket.core' not found Status in texlive-base package in Ubuntu: Confirmed Bug description: Before 3 weeks at least it was possible to install texlive-full without any issues. Now this is not possible anymore. So the bug was probably introduced with one of the latest updates. How to reproduce: Install package texlive-full $ apt install texlive-full Install hangs: texlive-lang-japanese (2021.20220204-1) wird eingerichtet ... context (2021.03.05.20220211-1) wird eingerichtet ... Running mtxrun --generate. This may take some time... done. Pregenerating ConTeXt MarkIV format. This may take some time... Related running processes: root 18747 0.4 0.0 13936 7456 pts/2Ss+ 17:47 0:01 /usr/bin/dpkg --status-fd 43 --configure --pending root 20584 0.0 0.0 2892 960 pts/2S+ 17:48 0:00 /bin/sh /var/lib/dpkg/info/context.postinst configure root 20592 0.0 0.0 2892 1064 pts/2S+ 17:48 0:00 /bin/sh /usr/bin/luatools --make cont-en root 20593 0.1 0.9 92868 79952 pts/2S+ 17:48 0:00 texlua /usr/bin/mtxrun --script base --make cont-en root 20596 0.0 0.0 2892 1004 pts/2S+ 17:48 0:00 sh -c /usr/bin/luatex --ini --lua=/usr/share/texmf/tex/context/base/mkiv/luat-cod.lua /usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv root 20597 0.0 0.3 40816 28684 pts/2S+ 17:48 0:00 /usr/bin/luatex --ini --lua=/usr/share/texmf/tex/context/base/mkiv/luat-cod.lua /usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv Run luatex manually: # /usr/bin/luatex --ini --lua=/usr/share/texmf/tex/context/base/mkiv/luat-cod.lua /usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv This is LuaTeX, Version 1.14.0 (TeX Live 2022/dev/Debian) (INITEX) system commands enabled. (/usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv (/usr/share/texmf/tex/context/base/mkiv/context.mkiv (/usr/share/texmf/tex/context/base/mkiv/syst-ini.mkiv) (/usr/share/texmf/tex/context/base/mkiv/norm-ctx.mkiv) (/usr/share/texmf/tex/context/base/mkiv/syst-pln.mkiv) (/usr/share/texmf/tex/context/base/mkiv/syst-mes.mkiv) (/usr/share/texmf/tex/context/base/mkiv/luat-cod.mkiv<+ /usr/share/texmf/tex/context/base/mkiv/luat-cod.lua>) (/usr/share/texmf/tex/context/base/mkiv/luat-bas.mkiv loading: ConTeXt Lua Macros / Basic Lua Libraries<+ /usr/share/texmf/tex/context/base/mkiv/l-bit32.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-lua.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-macro.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-sandbox.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-package.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-lpeg.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-function.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-string.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-table.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-boolean.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-number.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-math.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-io.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-os.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-file.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-gzip.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-md5.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-sha.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-dir.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-unicode.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-url.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-set.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-macro-imp-optimize.lua>) (/usr/share/texmf/tex/context/base/mkiv/luat-lib.mkiv loading: ConTeXt Lua Macros / Libraries<+
[Desktop-packages] [Bug 2052652] Re: [MIR] gnome-snapshot
Thanks, we hve a +1 from the security team now I've - promoted gstreamer1.0-libcamera to main - demoted -S cheese - subscribed the desktop-packages team to the package on launchpad Which were the remaining 'required' items from the MIR side, we will try to address the recommended one still but that's enough for now so I'm promoted gnome-snapshot (the desktop seed has also been updated to cheese -> gnome-snapshot) $ ./change-override -c main -S gnome-snapshot Override component to main gnome-snapshot 45.2+vendored-0ubuntu1 in noble: universe/misc -> main gnome-snapshot 45.2+vendored-0ubuntu1 in noble amd64: universe/gnome/optional/100% -> main gnome-snapshot 45.2+vendored-0ubuntu1 in noble arm64: universe/gnome/optional/100% -> main gnome-snapshot 45.2+vendored-0ubuntu1 in noble armhf: universe/gnome/optional/100% -> main gnome-snapshot 45.2+vendored-0ubuntu1 in noble ppc64el: universe/gnome/optional/100% -> main gnome-snapshot 45.2+vendored-0ubuntu1 in noble riscv64: universe/gnome/optional/100% -> main gnome-snapshot 45.2+vendored-0ubuntu1 in noble s390x: universe/gnome/optional/100% -> main Override [y|N]? y 7 publications overridden. ** Changed in: gnome-snapshot (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-snapshot in Ubuntu. https://bugs.launchpad.net/bugs/2052652 Title: [MIR] gnome-snapshot Status in gnome-snapshot package in Ubuntu: Fix Released Bug description: [Availability] The package gnome-snapshot is already in Ubuntu universe. The package gnome-snapshot build for the architectures it is designed to work on. It currently builds and works for architectures: amd64 arm64 armhf ppc64el riscv64 s390x Link to package https://launchpad.net/ubuntu/+source/gnome-snapshot [Rationale] - The package gnome-snapshot is required in Ubuntu main to replace cheese (which is unmaintained) as our default camera application. Cheese will go to universe as part of the transition. - The package gnome-snapshot is required in Ubuntu main no later than February 29th due to the Noble feature freeze. [Security] - No CVEs/security issues in this software in the past - no `suid` or `sgid` binaries - no executables in `/sbin` and `/usr/sbin` - Package does not install services, timers or recurring jobs - Packages does not open privileged ports (ports < 1024). - Package does not expose any external endpoints - Packages does not contain extensions to security-sensitive software [Quality assurance - function/usage] - The package works well right after install [Quality assurance - maintenance] - The package is maintained well in Debian/Ubuntu/Upstream and does not have important issues listed - Ubuntu https://bugs.launchpad.net/ubuntu/+source/gnome-snapshot/+bug - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=gnome-snapshot - Upstream's bug tracker, https://gitlab.gnome.org/GNOME/snapshot/-/issues - The package does not deal with exotic hardware we cannot support [Quality assurance - testing] - The package runs a test suite on build time, if it fails it makes the build fail, link to build log https://launchpad.net/ubuntu/+source/gnome-snapshot/45.2+vendored-0ubuntu1/+latestbuild/amd64 - The package does not run an autopkgtest because it's a graphical application dealing with hardware and we don't have a proper way to include those in the autopkgtest infra today. Instead we have a manual testplan that we will use to validate updates before uploading: https://wiki.ubuntu.com/DesktopTeam/TestPlans/GnomeSnapshot [Quality assurance - packaging] - debian/watch is present and works - debian/control defines a correct Maintainer - This package has only one minor lintian warning - Please link to a recent build log of the package https://launchpad.net/ubuntu/+source/gnome- snapshot/45.2+vendored-0ubuntu1/+latestbuild/amd64 - Log of `lintian --pedantic` # lintian --pedantic gnome-snapshot_45.2-2_amd64.changes W: snapshot: no-manual-page [usr/bin/snapshot] - Lintian overrides are not present - This package does not rely on obsolete or about to be demoted packages. - This package has no python2 or GTK2 dependencies - The package will be installed by default, but does not ask debconf questions - Packaging and build is easy, link to debian/rules https://salsa.debian.org/gnome- team/snapshot/-/blob/debian/latest/debian/rules [UI standards] - Application is end-user facing, Translation is present, via standard gettext - End-user applications that ships a standard conformant desktop file [Dependencies] - No further depends or recommends dependencies that are not yet in main [Standards compliance] - This package correctly follows FHS and Debian Policy [Maintenance/Owner] - The owning team will be desktop-packages and I have their
[Desktop-packages] [Bug 2058923] [NEW] Clicking 'App Details' from the Apps tab does not work
Public bug reported: This was tested on Ubuntu 24.04 with all current updates applied. To reproduce the issue: - Open gnome-control-centre - Navigate to the 'Apps' section - Click on any app - Click the 'App Details' button The system will open the snap-store front-page, but won't show the given apps details. This seems to be the same for both .deb and Snap packages. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-control-center 1:46~beta-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 25 11:05:37 2024 ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/usr/local/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2058923 Title: Clicking 'App Details' from the Apps tab does not work Status in gnome-control-center package in Ubuntu: New Bug description: This was tested on Ubuntu 24.04 with all current updates applied. To reproduce the issue: - Open gnome-control-centre - Navigate to the 'Apps' section - Click on any app - Click the 'App Details' button The system will open the snap-store front-page, but won't show the given apps details. This seems to be the same for both .deb and Snap packages. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-control-center 1:46~beta-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 25 11:05:37 2024 ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/usr/local/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2058923/+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 2058409] Re: Install of tevlive-full hangs: tex/context/base/mkiv/l-sandbox.lua:180: module 'socket.core' not found
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: texlive-base (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/2058409 Title: Install of tevlive-full hangs: tex/context/base/mkiv/l-sandbox.lua:180: module 'socket.core' not found Status in texlive-base package in Ubuntu: Confirmed Bug description: Before 3 weeks at least it was possible to install texlive-full without any issues. Now this is not possible anymore. So the bug was probably introduced with one of the latest updates. How to reproduce: Install package texlive-full $ apt install texlive-full Install hangs: texlive-lang-japanese (2021.20220204-1) wird eingerichtet ... context (2021.03.05.20220211-1) wird eingerichtet ... Running mtxrun --generate. This may take some time... done. Pregenerating ConTeXt MarkIV format. This may take some time... Related running processes: root 18747 0.4 0.0 13936 7456 pts/2Ss+ 17:47 0:01 /usr/bin/dpkg --status-fd 43 --configure --pending root 20584 0.0 0.0 2892 960 pts/2S+ 17:48 0:00 /bin/sh /var/lib/dpkg/info/context.postinst configure root 20592 0.0 0.0 2892 1064 pts/2S+ 17:48 0:00 /bin/sh /usr/bin/luatools --make cont-en root 20593 0.1 0.9 92868 79952 pts/2S+ 17:48 0:00 texlua /usr/bin/mtxrun --script base --make cont-en root 20596 0.0 0.0 2892 1004 pts/2S+ 17:48 0:00 sh -c /usr/bin/luatex --ini --lua=/usr/share/texmf/tex/context/base/mkiv/luat-cod.lua /usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv root 20597 0.0 0.3 40816 28684 pts/2S+ 17:48 0:00 /usr/bin/luatex --ini --lua=/usr/share/texmf/tex/context/base/mkiv/luat-cod.lua /usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv Run luatex manually: # /usr/bin/luatex --ini --lua=/usr/share/texmf/tex/context/base/mkiv/luat-cod.lua /usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv This is LuaTeX, Version 1.14.0 (TeX Live 2022/dev/Debian) (INITEX) system commands enabled. (/usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv (/usr/share/texmf/tex/context/base/mkiv/context.mkiv (/usr/share/texmf/tex/context/base/mkiv/syst-ini.mkiv) (/usr/share/texmf/tex/context/base/mkiv/norm-ctx.mkiv) (/usr/share/texmf/tex/context/base/mkiv/syst-pln.mkiv) (/usr/share/texmf/tex/context/base/mkiv/syst-mes.mkiv) (/usr/share/texmf/tex/context/base/mkiv/luat-cod.mkiv<+ /usr/share/texmf/tex/context/base/mkiv/luat-cod.lua>) (/usr/share/texmf/tex/context/base/mkiv/luat-bas.mkiv loading: ConTeXt Lua Macros / Basic Lua Libraries<+ /usr/share/texmf/tex/context/base/mkiv/l-bit32.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-lua.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-macro.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-sandbox.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-package.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-lpeg.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-function.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-string.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-table.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-boolean.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-number.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-math.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-io.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-os.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-file.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-gzip.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-md5.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-sha.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-dir.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-unicode.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-url.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-set.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-macro-imp-optimize.lua>) (/usr/share/texmf/tex/context/base/mkiv/luat-lib.mkiv loading: ConTeXt Lua Macros / Libraries<+ /usr/share/texmf/tex/context/base/mkiv/util-str.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-tab.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-fil.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-sac.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-sto.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-pck.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-prs.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-fmt.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-dim.lua><+ /usr/share/texmf/tex/context/base/mkiv/trac-set.lua><+ /usr/share/texmf/tex/context/base/mkiv/luat-log.lua><+ /usr/share/texmf/tex/context/base/mkiv/trac-inf.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-lua.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-deb.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-tpl.lua><+
[Desktop-packages] [Bug 2054510] Re: Incomplete screen redraws in virtual machines running Xorg
Done: https://salsa.debian.org/gnome- team/mutter/-/commit/1e2c8fedb0bcd293501420390c3bea48f9049301 -- 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/2054510 Title: Incomplete screen redraws in virtual machines running Xorg Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Mantic: Fix Committed Status in mutter source package in Noble: Fix Committed Bug description: [ Impact ] When using software rendering on Xorg (so usually just in VMs), some parts of app windows may fail to redraw. https://gitlab.gnome.org/GNOME/mutter/-/issues/2880 [ Test Plan ] 1. Set up a virtual machine without graphics acceleration. 2. Log into 'Ubuntu on Xorg'. 3. Open Settings > About and verify Graphics = llvmpipe (or "Software Rendering"), and Windowing System = X11. 4. sudo snap install chromium 5. Open Chromium and find a web page with lots of text. Plain text without any links and staying at the top of the page will work best because you don't want to trigger any scrolling. 6. Start selecting text with the mouse and while holding the button move the mouse up and down rapidly. Avoid triggering any page scrolling. 7. Release the mouse button in roughly the middle of the area of text that was selected. 8. Verify the remaining text selection is contiguous and not broken into multiple disconnected text selections (the bug). 9. Repeat steps 7 and 8 several times to be sure. [ Where problems could occur ] The fix adds a new synchronization point between the compositor and X server. This should be inconsequential, although there is a "sync ring" in mutter used for this, and if a mistake occurs there then other parts of the desktop could appear to stop responding in Xorg sessions. [ Other Info ] This is a regression that started in 3.37.3 due to https://gitlab.gnome.org/GNOME/mutter/-/commit/551101c65cda. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054510/+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 2058881] Re: [snap] Allow chromium snap to access Pressure Stall Information (PSI)
I reproduced that now. Do you observe any problem or hindrance as a result of those denials? I had a look at the source code and it seems that it doesn't actually use that information for load balancing or anything of the sorts, but actually only for informational purposes, namely for assembling histograms and reporting the results to the so called UMA, User Metrics Analysis according to the developer's glossary, for instance if the user chooses to report a session crash back to Google. ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Wishlist -- 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/2058881 Title: [snap] Allow chromium snap to access Pressure Stall Information (PSI) Status in chromium-browser package in Ubuntu: Confirmed Bug description: Hi, Currently seeing this: | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 audit(1711343543.539:657): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/proc/pressure/cpu" pid=63335 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid=0 | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 audit(1711343543.539:658): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/proc/pressure/io" pid=63335 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid=0 | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 audit(1711343543.539:659): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/proc/pressure/memory" pid=63335 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid> It seems the AppAmor profile should be updated to allow Chromium access to the pressure stall information for it to monitor and manage it's processes? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2058881/+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 2058876] Re: display freeze
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. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.
2. 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.
3. If step 2 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.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
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/2058876
Title:
display freeze
Status in Ubuntu:
Incomplete
Bug description:
The display keeps freezing. Sometime mouse keeps freezing. Sometime
after a sleep, when the laptop wake ups, the display not working or it
remain blank. again I have to restart it. It is very annoying as your
workspace i.e. all the opened apps got deleted. Again you have to
restart. It hampers the work. I am using NVIDIA driver 535 (tested)
display driver, which is recommended. I have gtx 1650 graphics. Ryzen
5 4000 series processor.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.161.07 Sat Feb 17
22:55:48 UTC 2024
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 25 09:29:55 2024
DistUpgraded: 2024-01-13 13:01:05,362 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: I don't know
GraphicsCard:
NVIDIA Corporation TU117M [10de:1f99] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] TU117M [1025:1447]
Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c7) (prog-if
00 [VGA controller])
Subsystem: Acer Incorporated [ALI] Renoir [1025:1455]
InstallationDate: Installed on 2023-08-30 (208 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64
(20230223)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_IN
LANGUAGE=en_IN:en
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic
root=UUID=33f81450-d6fa-4803-aba2-9ddca9a4a12a ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to mantic on 2024-01-13 (72 days ago)
dmi.bios.date: 02/04/2021
dmi.bios.release: 1.4
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.04
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Stonic_RNS
dmi.board.vendor: RO
dmi.board.version: V1.04
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.04
dmi.ec.firmware.release: 1.2
dmi.modalias:
dmi:bvnInsydeCorp.:bvrV1.04:bd02/04/2021:br1.4:efr1.2:svnAcer:pnNitroAN515-44:pvrV1.04:rvnRO:rnStonic_RNS:rvrV1.04:cvnAcer:ct10:cvrV1.04:sku:
dmi.product.family: Nitro 5
dmi.product.name: Nitro AN515-44
dmi.product.sku:
dmi.product.version: V1.04
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
[Desktop-packages] [Bug 2058881] Re: [snap] Allow chromium snap to access Pressure Stall Information (PSI)
It's used here: | https://github.com/chromium/chromium/blob/123.0.6312.58/chrome/browser/metrics/pressure/pressure_metrics_reporter.cc#L19 >From this commit: | https://github.com/chromium/chromium/commit/dace5562b1d56bf2d2e5b2de6f4518c44844be9f References this bug: | https://issues.chromium.org/issues/40256157 ** Bug watch added: issues.chromium.org/issues #40256157 https://issues.chromium.org/issues/40256157 -- 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/2058881 Title: [snap] Allow chromium snap to access Pressure Stall Information (PSI) Status in chromium-browser package in Ubuntu: Confirmed Bug description: Hi, Currently seeing this: | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 audit(1711343543.539:657): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/proc/pressure/cpu" pid=63335 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid=0 | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 audit(1711343543.539:658): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/proc/pressure/io" pid=63335 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid=0 | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 audit(1711343543.539:659): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/proc/pressure/memory" pid=63335 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid> It seems the AppAmor profile should be updated to allow Chromium access to the pressure stall information for it to monitor and manage it's processes? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2058881/+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 2058840] Re: Chromium Snap & KDE Plasma 6: AppArmor Profile Update Needed
Hi Gunter, thanks for the report. From what I understand Plasma 6 is not
(and will not be) available in Ubuntu 24.04, did you get it in by
building it from source or by using some PPA? I ask because it would be
nice to reproduce your observations before incorporating a fix.
Many thanks for raising this way before Plasma 6 is released to Ubuntu,
this way we can assure this bug is gone by the time Plasma 6 becomes
officially supported in Ubuntu.
--
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/2058840
Title:
Chromium Snap & KDE Plasma 6: AppArmor Profile Update Needed
Status in chromium-browser package in Ubuntu:
New
Bug description:
Ubuntu 22.04 LTS Jammy x64
I hope this is the correct package to assign this request to:
In KDE Plasma 6, the Chromium snap cannot longer access KDE Wallet to
decrypt its password store.
This makes all stored passwords unavailable as soon as the system is
upgraded from Plasma 5 to Plasma 6.
Chromium writes the following error messages to the console:
-
[5362:5362:0324/103716.837413:ERROR:object_proxy.cc(576)] Failed to call
method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd6:
org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this
sender from sending this message to this recipient; type="method_call",
sender=":1.113" (uid=1000 pid=5362
comm="/snap/chromium/2786/usr/lib/chromium-browser/chrom"
label="snap.chromium.chromium (enforce)") interface="org.kde.KWallet"
member="isEnabled" error name="(unset)" requested_reply="0"
destination="org.kde.kwalletd6" (uid=1000 pid=2523 comm="/usr/bin/kwalletd6
--pam-login 13 14 " label="unconfined")
[5362:5362:0324/103716.837451:ERROR:kwallet_dbus.cc(112)] Error contacting
kwalletd6 (isEnabled)
[5362:5362:0324/103716.838022:ERROR:object_proxy.cc(576)] Failed to call
method: org.kde.KLauncher.start_service_by_desktop_name: object_path=
/KLauncher: org.freedesktop.DBus.Error.ServiceUnknown: The name
org.kde.klauncher was not provided by any .service files
[5362:5362:0324/103716.838042:ERROR:kwallet_dbus.cc(81)] Error contacting
klauncher to start kwalletd6
[5362:5362:0324/103716.838264:ERROR:object_proxy.cc(576)] Failed to call
method: org.kde.KWallet.close: object_path= /modules/kwalletd6:
org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this
sender from sending this message to this recipient; type="method_call",
sender=":1.113" (uid=1000 pid=5362
comm="/snap/chromium/2786/usr/lib/chromium-browser/chrom"
label="snap.chromium.chromium (enforce)") interface="org.kde.KWallet"
member="close" error name="(unset)" requested_reply="0"
destination="org.kde.kwalletd6" (uid=1000 pid=2523 comm="/usr/bin/kwalletd6
--pam-login 13 14 " label="unconfined")
[5362:5362:0324/103716.838295:ERROR:kwallet_dbus.cc(503)] Error contacting
kwalletd6 (close)
-
Followed by hundreds of messages as the following:
-
ERROR:login_database.cc(1046) Password decryption failed, encryption_result
is 2
-
It appears to work to "just" whitelist the new kwalletd module name in
/var/lib/snapd/apparmor/profiles/snap.chromium.chromium (and maybe
/var/lib/snapd/apparmor/profiles/snap.chromium.chromedriver ?)
followed by
$ systemctl restart apparmor
$ systemctl restart snapd.apparmor
$ systemctl restart apparmor
(Not sure if both of these are necessary, and if so, in what order.)
and completely restart Chromium.
The new KWallet section looks as follows - I only added the ",6" to
the patterns:
-
# KWallet's client API is still in use in KDE/Plasma. It's DBus API relies
upon
# member data for access to its 'folders' and 'entries' and it therefore does
# not allow for application isolation via AppArmor. For details, see:
# - https://cgit.kde.org/kdelibs.git/tree/kdeui/util/kwallet.h?h=v4.14.33
#
dbus (receive, send)
bus=session
path=/modules/kwalletd{,5,6}
interface=org.freedesktop.DBus.*
peer=(label=unconfined),
dbus (receive, send)
bus=session
path=/modules/kwalletd{,5,6}
interface=org.kde.KWallet
peer=(label=unconfined),
-
I hope that at least this report may be found by other people running
into the same trouble I just did...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2058840/+subscriptions
--
Mailing list:
[Desktop-packages] [Bug 2058847] Re: budgie-wm crashes immediately when mutter-common has been upgraded to version 46.0
FYI: Still missing from the latest and greatest mutter-common: $ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: mutter-common 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 47.2 kB of archives. After this operation, 4,096 B disk space will be freed. Do you want to continue? [Y/n] Get:1 http://ch.archive.ubuntu.com/ubuntu noble-proposed/main amd64 mutter-common all 46.0-1ubuntu3 [47.2 kB] Fetched 47.2 kB in 0s (1,005 kB/s) (Reading database ... 886859 files and directories currently installed.) Preparing to unpack .../mutter-common_46.0-1ubuntu3_all.deb ... Unpacking mutter-common (46.0-1ubuntu3) over (45.3-1ubuntu1) ... Setting up mutter-common (46.0-1ubuntu3) ... Processing triggers for libglib2.0-0t64:i386 (2.79.3-3ubuntu5) ... Processing triggers for man-db (2.12.0-3build4) ... Processing triggers for libglib2.0-0t64:amd64 (2.79.3-3ubuntu5) ... $ ls -l /usr/share/glib-2.0/schemas/org.gnome.mutter.x11.gschema.xml ls: cannot access '/usr/share/glib-2.0/schemas/org.gnome.mutter.x11.gschema.xml': No such file or directory $ dpkg-query -S org.gnome.mutter.x11 dpkg-query: no path found matching pattern *org.gnome.mutter.x11* -- 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/2058847 Title: budgie-wm crashes immediately when mutter-common has been upgraded to version 46.0 Status in budgie-desktop package in Ubuntu: Triaged Status in mutter package in Ubuntu: New Bug description: mutter-common 46.0 packages remove the org.gnome.mutter.x11 gconf schema. This causes budgie-wm to crash immediately on login. Downgrading to 45.3 fixes everything. $ apt policy mutter-common mutter-common: Installed: 45.3-1ubuntu1 Candidate: 46.0-1ubuntu1 Version table: 46.0-1ubuntu1 500 500 http://ch.archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages 500 http://ch.archive.ubuntu.com/ubuntu noble-proposed/main i386 Packages *** 45.3-1ubuntu1 500 500 http://ch.archive.ubuntu.com/ubuntu noble/main amd64 Packages 500 http://ch.archive.ubuntu.com/ubuntu noble/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: budgie-core 10.9.1-3ubuntu1 Uname: Linux 6.8.1-060801-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Sun Mar 24 16:00:24 2024 InstallationDate: Installed on 2022-03-19 (736 days ago) InstallationMedia: Ubuntu-Budgie 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: budgie-desktop UpgradeStatus: Upgraded to noble on 2023-11-03 (142 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/2058847/+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 2058881] Re: [snap] Allow chromium snap to access Pressure Stall Information (PSI)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed -- 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/2058881 Title: [snap] Allow chromium snap to access Pressure Stall Information (PSI) Status in chromium-browser package in Ubuntu: Confirmed Bug description: Hi, Currently seeing this: | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 audit(1711343543.539:657): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/proc/pressure/cpu" pid=63335 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid=0 | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 audit(1711343543.539:658): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/proc/pressure/io" pid=63335 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid=0 | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 audit(1711343543.539:659): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/proc/pressure/memory" pid=63335 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid> It seems the AppAmor profile should be updated to allow Chromium access to the pressure stall information for it to monitor and manage it's processes? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2058881/+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 2058881] Re: [snap] Allow chromium snap to access Pressure Stall Information (PSI)
Sorry, I should have mentioned the version. I'm using the chromium from the candidate channel: | $ snap info chromium | grep installed | installed: 123.0.6312.58 (2795) 168MB - Seems to be happening every 10 mins. -- 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/2058881 Title: [snap] Allow chromium snap to access Pressure Stall Information (PSI) Status in chromium-browser package in Ubuntu: Confirmed Bug description: Hi, Currently seeing this: | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 audit(1711343543.539:657): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/proc/pressure/cpu" pid=63335 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid=0 | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 audit(1711343543.539:658): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/proc/pressure/io" pid=63335 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid=0 | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 audit(1711343543.539:659): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/proc/pressure/memory" pid=63335 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid> It seems the AppAmor profile should be updated to allow Chromium access to the pressure stall information for it to monitor and manage it's processes? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2058881/+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 2058876] Re: display freeze
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2058876
Title:
display freeze
Status in xorg package in Ubuntu:
New
Bug description:
The display keeps freezing. Sometime mouse keeps freezing. Sometime
after a sleep, when the laptop wake ups, the display not working or it
remain blank. again I have to restart it. It is very annoying as your
workspace i.e. all the opened apps got deleted. Again you have to
restart. It hampers the work. I am using NVIDIA driver 535 (tested)
display driver, which is recommended. I have gtx 1650 graphics. Ryzen
5 4000 series processor.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.161.07 Sat Feb 17
22:55:48 UTC 2024
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 25 09:29:55 2024
DistUpgraded: 2024-01-13 13:01:05,362 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: I don't know
GraphicsCard:
NVIDIA Corporation TU117M [10de:1f99] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] TU117M [1025:1447]
Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c7) (prog-if
00 [VGA controller])
Subsystem: Acer Incorporated [ALI] Renoir [1025:1455]
InstallationDate: Installed on 2023-08-30 (208 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64
(20230223)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_IN
LANGUAGE=en_IN:en
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic
root=UUID=33f81450-d6fa-4803-aba2-9ddca9a4a12a ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to mantic on 2024-01-13 (72 days ago)
dmi.bios.date: 02/04/2021
dmi.bios.release: 1.4
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.04
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Stonic_RNS
dmi.board.vendor: RO
dmi.board.version: V1.04
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.04
dmi.ec.firmware.release: 1.2
dmi.modalias:
dmi:bvnInsydeCorp.:bvrV1.04:bd02/04/2021:br1.4:efr1.2:svnAcer:pnNitroAN515-44:pvrV1.04:rvnRO:rnStonic_RNS:rvrV1.04:cvnAcer:ct10:cvrV1.04:sku:
dmi.product.family: Nitro 5
dmi.product.name: Nitro AN515-44
dmi.product.sku:
dmi.product.version: V1.04
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2058876/+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 2058876] [NEW] display freeze
You have been subscribed to a public bug:
The display keeps freezing. Sometime mouse keeps freezing. Sometime
after a sleep, when the laptop wake ups, the display not working or it
remain blank. again I have to restart it. It is very annoying as your
workspace i.e. all the opened apps got deleted. Again you have to
restart. It hampers the work. I am using NVIDIA driver 535 (tested)
display driver, which is recommended. I have gtx 1650 graphics. Ryzen 5
4000 series processor.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.161.07 Sat Feb 17
22:55:48 UTC 2024
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 25 09:29:55 2024
DistUpgraded: 2024-01-13 13:01:05,362 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: I don't know
GraphicsCard:
NVIDIA Corporation TU117M [10de:1f99] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] TU117M [1025:1447]
Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c7) (prog-if 00
[VGA controller])
Subsystem: Acer Incorporated [ALI] Renoir [1025:1455]
InstallationDate: Installed on 2023-08-30 (208 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64
(20230223)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_IN
LANGUAGE=en_IN:en
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic
root=UUID=33f81450-d6fa-4803-aba2-9ddca9a4a12a ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to mantic on 2024-01-13 (72 days ago)
dmi.bios.date: 02/04/2021
dmi.bios.release: 1.4
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.04
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Stonic_RNS
dmi.board.vendor: RO
dmi.board.version: V1.04
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.04
dmi.ec.firmware.release: 1.2
dmi.modalias:
dmi:bvnInsydeCorp.:bvrV1.04:bd02/04/2021:br1.4:efr1.2:svnAcer:pnNitroAN515-44:pvrV1.04:rvnRO:rnStonic_RNS:rvrV1.04:cvnAcer:ct10:cvrV1.04:sku:
dmi.product.family: Nitro 5
dmi.product.name: Nitro AN515-44
dmi.product.sku:
dmi.product.version: V1.04
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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 mantic ubuntu
--
display freeze
https://bugs.launchpad.net/bugs/2058876
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 2058881] [NEW] [snap] Allow chromium snap to access Pressure Stall Information (PSI)
Hello, do you have a reproduction case? I don't get this when I launch Chromium, does it try that when on heavy load? -- 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/2058881 Title: [snap] Allow chromium snap to access Pressure Stall Information (PSI) Status in chromium-browser package in Ubuntu: New Bug description: Hi, Currently seeing this: | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 audit(1711343543.539:657): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/proc/pressure/cpu" pid=63335 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid=0 | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 audit(1711343543.539:658): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/proc/pressure/io" pid=63335 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid=0 | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 audit(1711343543.539:659): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/proc/pressure/memory" pid=63335 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid> It seems the AppAmor profile should be updated to allow Chromium access to the pressure stall information for it to monitor and manage it's processes? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2058881/+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 2058687] Re: [SRU] libreoffice 7.6.6 for mantic
** Description changed: [Impact] * LibreOffice 7.6.6 is in its sixth bugfix release of the 7.6 line: https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.6_release * Version 7.6.5 is currently released in mantic. For a list of fixed bugs compared to 7.6.5 see the list of bugs fixed in the release candidates of 7.6.6 (that's a total of ? bugs): https://wiki.documentfoundation.org/Releases/7.6.6/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.6.6/RC2#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.6.6/RC3#List_of_fixed_bugs 7.6.6 RC3 is identical to the 7.6.6 release * 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_76/1898/ * 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. Tested build can be found at https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/15869507/+listing-archive-extra - * [amd64] ... - * [arm64] ... + * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/amd64/libr/libreoffice/20240323_001335_50e00@/log.gz + * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/arm64/libr/libreoffice/20240324_215819_0b108@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/armhf/libr/libreoffice/20240322_202324_f628d@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/ppc64el/libr/libreoffice/20240322_145135_f3904@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/s390x/libr/libreoffice/20240322_140411_ca6c5@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of ? bug fixes always carries the potential for introducing regressions, even though it is a 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. -- 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/2058687 Title: [SRU] libreoffice 7.6.6 for mantic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Mantic: In Progress Bug description: [Impact] * LibreOffice 7.6.6 is in its sixth bugfix release of the 7.6 line: https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.6_release * Version 7.6.5 is currently released in mantic. For a list of fixed bugs compared to 7.6.5 see the list of bugs fixed in the release candidates of 7.6.6 (that's a total of ? bugs): https://wiki.documentfoundation.org/Releases/7.6.6/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.6.6/RC2#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.6.6/RC3#List_of_fixed_bugs 7.6.6 RC3 is identical to the 7.6.6 release * 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_76/1898/ * More information about the upstream QA testing can be found here: * Automated tests
[Desktop-packages] [Bug 2003168] Re: Dash-to-dock and Ubuntu Dock may accidentally call each other [JS ERROR: TypeError: dockManager is null]
Sounds like the original problem is now fixed in: https://github.com/micheleg/dash-to-dock/pull/2165 https://launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/89ubuntu3 ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Triaged => Fix Released -- 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/2003168 Title: Dash-to-dock and Ubuntu Dock may accidentally call each other [JS ERROR: TypeError: dockManager is null] Status in Dash to dock: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: SIdebar, files gets unresponsive after unlocking locked season. Clicking on search bar also freezes the whole season. Issue requires Restarting GTK3 or restarting the season. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-59.65-generic 5.15.78 Uname: Linux 5.15.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 18 13:35:36 2023 InstallationDate: Installed on 2021-06-20 (576 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/2003168/+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 2058838] Re: Xorg crash
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. Run these commands: journalctl -b0 > journal.txt journalctl -b-1 > prevjournal.txt and attach the resulting text files here. 2. 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. 3. If step 2 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. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Summary changed: - Xorg crash + Crash -- 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/2058838 Title: Crash Status in Ubuntu: Incomplete Bug description: When switching KVM my X session crashes. Syslog gets cleared as well for some reason. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.161.07 Sat Feb 17 22:55:48 UTC 2024 GCC version: ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Mar 23 23:58:33 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GA102GL [RTX A5000] [10de:2231] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GA102GL [RTX A5000] [10de:147e] InstallationDate: Installed on 2022-04-07 (717 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) MachineType: ASUS System Product Name ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=c56061b9-1478-4914-a919-96eb077fff48 ro quiet splash nvidia-drm.modeset=1 initcall_blacklist=acpi_cpufreq_init amd_pstate=active amd_pstate.shared_mem=1 acpi_enforce_resources=lax vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2023 dmi.bios.release: 18.7 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1807 dmi.board.asset.tag: Default string dmi.board.name: PRIME B650-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1807:bd09/26/2023:br18.7:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS mtime.conffile..etc.init.d.apport: 2024-02-22T08:20:00 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1 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/+bug/2058838/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
