[Desktop-packages] [Bug 1921931]
*** Bug 1878528 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1921931 Title: Opening links results in "Firefox is already running, but is not responding" Status in Mozilla Firefox: Won't Fix Status in firefox package in Ubuntu: Fix Released Bug description: Since the latest package release enabling wayland, I often get the "Firefox is already running, but is not responding. To use Firefox, you must first close the existing Firefox process, restart your device, or use a different profile." message when trying to open links from other applications (eg geary, slack) instead of having the link open in the existing firefox window. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 87.0+build3-0ubuntu2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 829438 F pulseaudio BuildID: 20210318103112 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: GNOME Date: Tue Mar 30 09:14:13 2021 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2019-08-17 (591 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) IpRoute: default via 192.168.4.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.4.0/22 dev wlp2s0 proto kernel scope link src 192.168.4.89 metric 600 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-76c5697a-ecec-48ea-b09a-9db310190506 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js prefs.js Profiles: Profile0 (Default) - LastVersion=87.0/20210318103112 RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-76c5697a-ecec-48ea-b09a-9db310190506 Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to hirsute on 2021-02-23 (34 days ago) dmi.bios.date: 07/15/2020 dmi.bios.release: 1.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd07/15/2020:br1.13:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1921931/+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 2052492] Re: Pairing: passcode dialogue disappears in <1 second
I'm not sure whether to call this a GUI bug or a feature. It depends on whether the device changing its name, but keeping the same ID, should affect your ability to pair with it. ** Package changed: ubuntu => gnome-control-center (Ubuntu) ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2052492 Title: Pairing: passcode dialogue disappears in <1 second Status in gnome-control-center package in Ubuntu: New Bug description: UPDATE: I am creating this bug in case it comes back again. My Fix was to put the bluetooth keyboard aside for a week (not use it), then reconnect after the laptop had been rebooted after an update and daily use. I will post the things that I tried, just in case: 1) There is something I messed that someone else can suggest; and 2) it occurs for someone else. I suspect that it will happen again at some stage. -- I am seeing this issue in Ubuntu 23.10. bluez 5.68-0ubuntu1.1 Hardware: Logi POP Keys https://www.logitech.com/en-au/products/keyboards/pop-keys-wireless-mechanical.920-011226.html I have managed to have it working in the past, but the 6-digit code pop-up disappears very quickly (as described, <1sec). System details - $ lsb_release -rd No LSB modules are available. Description: Ubuntu 23.10 Release: 23.10 - ii bluez 5.68-0ubuntu1.1amd64Bluetooth tools and daemons -- Bluetooth Device Logitech - Logi POP Keys (see link below) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2052492/+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 2052492] [NEW] Pairing: passcode dialogue disappears in <1 second
You have been subscribed to a public bug: UPDATE: I am creating this bug in case it comes back again. My Fix was to put the bluetooth keyboard aside for a week (not use it), then reconnect after the laptop had been rebooted after an update and daily use. I will post the things that I tried, just in case: 1) There is something I messed that someone else can suggest; and 2) it occurs for someone else. I suspect that it will happen again at some stage. -- I am seeing this issue in Ubuntu 23.10. bluez 5.68-0ubuntu1.1 Hardware: Logi POP Keys https://www.logitech.com/en-au/products/keyboards/pop-keys-wireless-mechanical.920-011226.html I have managed to have it working in the past, but the 6-digit code pop- up disappears very quickly (as described, <1sec). System details - $ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.10 Release:23.10 - ii bluez 5.68-0ubuntu1.1amd64Bluetooth tools and daemons -- Bluetooth Device Logitech - Logi POP Keys (see link below) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: mantic -- Pairing: passcode dialogue disappears in <1 second https://bugs.launchpad.net/bugs/2052492 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center 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
[Desktop-packages] [Bug 2052580] Re: Update to 122.0.1
References: https://ubuntu.com/security/notices/USN-6610-2 Package Information: https://launchpad.net/ubuntu/+source/firefox/122.0.1+build1-0ubuntu0.20.04.1 ** Changed in: firefox (Ubuntu) Status: New => Fix Released ** Changed in: firefox (Ubuntu Focal) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2052580 Title: Update to 122.0.1 Status in firefox package in Ubuntu: Fix Released Status in firefox source package in Focal: Fix Released Bug description: https://www.mozilla.org/en-US/firefox/122.0.1/releasenotes/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2052580/+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 2045855] Re: package bluez 5.64-0ubuntu1.1 failed to install/upgrade: end of file on stdin at conffile prompt
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2045855 Title: package bluez 5.64-0ubuntu1.1 failed to install/upgrade: end of file on stdin at conffile prompt Status in bluez package in Ubuntu: Expired Bug description: I did not recognized the error. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: bluez:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Dec 7 15:44:57 2023 ErrorMessage: end of file on stdin at conffile prompt InstallationDate: Installed on 2021-01-30 (1040 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. OptiPlex 7010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=UUID=1aa27b2f-8d22-4b4e-931f-bd8e304ed0d4 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.12, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: bluez Title: package bluez 5.64-0ubuntu1.1 failed to install/upgrade: end of file on stdin at conffile prompt UpgradeStatus: Upgraded to jammy on 2023-03-28 (253 days ago) dmi.bios.date: 03/25/2013 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0GY6Y8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd03/25/2013:br4.6:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0GY6Y8:rvrA00:cvnDellInc.:ct6:cvr:sku: dmi.product.name: OptiPlex 7010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:1A:7D:DA:71:03 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:1332 acl:0 sco:0 events:84 errors:0 TX bytes:3786 acl:0 sco:0 commands:81 errors:0 mtime.conffile..etc.bluetooth.input.conf: 2020-04-03T15:47:01 mtime.conffile..etc.bluetooth.main.conf: 2020-02-26T18:57:50 mtime.conffile..etc.bluetooth.network.conf: 2012-12-25T02:46:55 mtime.conffile..etc.dbus-1.system.d.bluetooth.conf: 2022-03-24T15:30:38 mtime.conffile..etc.init.d.bluetooth: 2020-02-26T18:57:50 rfkill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045855/+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 2052580] [NEW] Update to 122.0.1
Public bug reported: https://www.mozilla.org/en-US/firefox/122.0.1/releasenotes/ ** Affects: firefox (Ubuntu) Importance: Undecided Assignee: Nishit Majithia (0xnishit) Status: New ** Affects: firefox (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: firefox (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2052580 Title: Update to 122.0.1 Status in firefox package in Ubuntu: New Status in firefox source package in Focal: New Bug description: https://www.mozilla.org/en-US/firefox/122.0.1/releasenotes/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2052580/+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 1888505]
Dear Severo Raz, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- 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/1888505 Title: Two-finger touchpad zoom extremely sensitive Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: New Bug description: Open Calc -> + Expected behaviour: document viewpan zooms/unzooms at a reasonable speed Observed behaviour: document viewpan zooms/unzooms from maximum zoom in to maximum zoom out in maybe 10-15% of the height of the touchpad, i.e. it is unusably oversensitive. Also affects Draw and Writer, 100% reproducible. Other apps (Firefox, Eye of Gnome/Image viewer) behave as expected (very usable zoom/unzoom sensitivity). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-core 1:6.0.7-0ubuntu0.18.04.10 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 14:43:20 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-05-10 (804 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2020-03-04 (140 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1888505/+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 2051855] Re: Mutter causes desktop to extend beyond screen, looks like 2160p on 1440p screen
Please attach a copy of $HOME/.config/monitors.xml ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- 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/2051855 Title: Mutter causes desktop to extend beyond screen, looks like 2160p on 1440p screen Status in mutter package in Ubuntu: Incomplete Bug description: Mutter causes desktop to extend beyond screen, looks like 2160p on 1440p screen. This appeared only after installing the latest update of the libmutter package. I am using 2x Samsung S27AG502NUXEN displays in extended desktop mode (join). So far the only fix i have found is holding back this package. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: libmutter-13-0 45.2-0ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 31 14:33:53 2024 InstallationDate: Installed on 2021-10-04 (849 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mutter UpgradeStatus: Upgraded to mantic on 2023-10-16 (107 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2051855/+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 2016013] Re: New windows don't get centered if Desktop Icons NG is loaded
I feel like that work is something we do want in LTS. There's still 3 weeks before feature freeze and months to fix any bugs thereafter. ** Tags added: noble -- 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/2016013 Title: New windows don't get centered if Desktop Icons NG is loaded Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: New windows don't get centered if Desktop Icons NG is loaded. With vanilla GNOME, if an app window is too large for tiling (larger than a quarter of the screen) then it will be centered by default. But this doesn't happen when DING is loaded, probably because DING is incorrectly treated as an app window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/2016013/+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 2016013] Re: New windows don't get centered if Desktop Icons NG is loaded
Also since we know what the problem is, a fix could be patched into mutter to accommodate even the older version of DING. -- 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/2016013 Title: New windows don't get centered if Desktop Icons NG is loaded Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: New windows don't get centered if Desktop Icons NG is loaded. With vanilla GNOME, if an app window is too large for tiling (larger than a quarter of the screen) then it will be centered by default. But this doesn't happen when DING is loaded, probably because DING is incorrectly treated as an app window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/2016013/+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 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
Sam issue here with Razer Blade 16 2024: cat /proc/asound/card1/codec* | grep Codec Codec: Realtek ALC298 -- 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/2011385 Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: only bluetooth can work,im sungsang book2 pro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 15:41:47 2023 InstallationDate: Installed on 2023-03-08 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P08RGF.054.220817.ZQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NT950XEW-A51AS dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF: dmi.product.family: Galaxy Book2 Pro dmi.product.name: 950XED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF dmi.product.version: P08RGF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 2015405] Re: spice-vdagent crashed with SIGSEGV
I saw this again yesterday in a standard Ubuntu Noble install in QEMU/KVM. It's not a ISO install test; it's been updated regularly for a while. Again, other than the crash notice, nothing obvious happens. -- 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/2015405 Title: spice-vdagent crashed with SIGSEGV Status in spice-vdagent package in Ubuntu: Confirmed Bug description: Just launching an ubuntu 23.04 beta VM on libvirtd/qemu/KVM and this brings the reporting crash app as soon as loging into the desktop. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: spice-vdagent 0.22.1-3 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 5 23:21:08 2023 ExecutablePath: /usr/bin/spice-vdagent InstallationDate: Installed on 2023-03-31 (5 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329) ProcCmdline: /usr/bin/spice-vdagent ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x559a23cd00e0:mov(%r15),%rdi PC (0x559a23cd00e0) ok source "(%r15)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: spice-vdagent StacktraceTop: () __libc_start_call_main (main=main@entry=0x559a23ccfe80, argc=argc@entry=1, argv=argv@entry=0x7ffce18a7c08) at ../sysdeps/nptl/libc_start_call_main.h:58 __libc_start_main_impl (main=0x559a23ccfe80, argc=1, argv=0x7ffce18a7c08, init=, fini=, rtld_fini=, stack_end=0x7ffce18a7bf8) at ../csu/libc-start.c:360 () Title: spice-vdagent crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/2015405/+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 2051855] Re: Mutter causes desktop to extend beyond screen, looks like 2160p on 1440p screen
** Summary changed: - Mutter causes desktop to extend beyond screen, looks like 2140p on 1440p screen + Mutter causes desktop to extend beyond screen, looks like 2160p on 1440p screen ** Description changed: - Mutter causes desktop to extend beyond screen, looks like 2140p on 1440p screen. + Mutter causes desktop to extend beyond screen, looks like 2160p on 1440p screen. This appeared only after installing the latest update of the libmutter package. I am using 2x Samsung S27AG502NUXEN displays in extended desktop mode (join). So far the only fix i have found is holding back this package. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: libmutter-13-0 45.2-0ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 31 14:33:53 2024 InstallationDate: Installed on 2021-10-04 (849 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mutter UpgradeStatus: Upgraded to mantic on 2023-10-16 (107 days ago) -- 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/2051855 Title: Mutter causes desktop to extend beyond screen, looks like 2160p on 1440p screen Status in mutter package in Ubuntu: New Bug description: Mutter causes desktop to extend beyond screen, looks like 2160p on 1440p screen. This appeared only after installing the latest update of the libmutter package. I am using 2x Samsung S27AG502NUXEN displays in extended desktop mode (join). So far the only fix i have found is holding back this package. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: libmutter-13-0 45.2-0ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 31 14:33:53 2024 InstallationDate: Installed on 2021-10-04 (849 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mutter UpgradeStatus: Upgraded to mantic on 2023-10-16 (107 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2051855/+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 2052529] Re: L'économiseur d'écran ne se déclenche pas comme il le devrait
** Description changed: - Sous wayland, GNOME, L'écran est configuré pour s'éteindre toutes les 2 minutes depuis les paramètres. L'écran s'éteint bien, mais il se rallume quelques secondes plus tard. Seul l'économiseur d'écran (écran noir mais non éteint) fonctionne. + Sous X11, GNOME, L'écran est configuré pour s'éteindre toutes les 2 minutes depuis les paramètres. L'écran s'éteint bien, mais il se rallume quelques secondes plus tard. Seul l'économiseur d'écran (écran noir mais non éteint) fonctionne. Je précise que lorsque l'écran s'éteint et se rallume quelques secondes plus tard, un message "détection automatique de source" apparaît, ce qui laisse penser que l'écran détecte automatiquement une source puis décide de se rallumer. Le problème est que je n'arrive pas à désactiver cette "recherche automatique des sources" depuis le menu de l'écran ni nulle part ailleur, ce qui est à l'origine du problème je pense. - Mon écran est un modèle BenQ Mobiuz. - J'ai indiqué que le paquet était lié à x11-xserver-utils mais je ne suis pas sûr, je suis sur Wayland et je pense que l'économiseur d'écran est directement lié à Gnome. + Mon écran est un modèle BenQ Mobiuz. J'utilise Ubuntu 22.04.3 LTS killianp@killianp ~> apt-cache Policy x11-server-utils E: L'opération Policy n'est pas valable - Merci beaucoup. Achille Pyréa Type de problème : Bug DistroRelease : Ubuntu 22.04 Package : x11-xserver-utils 7.7+9build1 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 BootLog : Erreur : [Errno 13] Permission non accordée : '/var/log/boot.log ' CasperMD5CheckR esult: pass CompositorRunning: Aucun CurrentDesktop: ubuntu:GNOME Date: mar 6 février 16:40:22 2024 DistUpgraded: nouvelle installation DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.48, 6.5.0-14-generic, x86_64 : virtualbox/6.1.48, 6.5.0-15-generic installé, x86_64 : installé Carte graphique : Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] [1002:73ff ] (rév c7) (prog-if 00 [Contrôleur VGA]) Sous-système : XFX Limited Navi 23 [Radeon RX 6600/6600 XT/6600M] [1eae:6505] Date d'installation : Installé le 2023-12-30 (il y a 37 jours) InstallationMedia : Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Version amd64 (20230807.2) Type de machine : Gigabyte Technology Co., Ltd. B550 GAMING X V2 ProcEnviron : - PATH=( personnalisé, aucun utilisateur) + PATH=(personnalisé, aucun utilisateur) XDG_RUNTIME_ DIR = LANG=fr_FR.UTF -8 SHELL= /usr/bin/ fish ProcKernelCmdLine : BOOT_IMAGE= /boot/vmlinuz- 6.5.0-15- generic root=UUID= 66dfa360- 6016-472f- b236-fef2f4bb11 74 ro quiet splash vt.handoff=7 RebootRequiredPkgs : Erreur : le chemin contient des liens symboliques. SourcePackage : x11-xserver-utils UpgradeStatus : Aucun journal de mise à niveau présent (probablement une nouvelle installation) dmi.bios.date : 20/09/2023 dmi.bios.release : 5.17 dmi.bios.vendor : American Megatrends International, SARL. dmi.bios.version : FDc dmi.board. Asset.tag : chaîne par défaut dmi.board.name : B550 GAMING X V2 dmi.board.vendor : Gigabyte Technology Co., Ltd. dmi.board.version : xx dmi.chassis. Asset.tag : chaîne par défaut dmi.chassis.type : 3 dmi.chassis.vendor : chaîne par défaut dmi.chassis. version : Chaîne par défaut dmi.modalias : dmi:bvnAmerican MegatrendsInter national, LLC.:bvrFDc : bd09/20/ 2023:br5. 17 : svnGigabyteT echnologyCo. , Ltd. : pnB550GAM INGXV2 : pvr-CF : rvnGigabyteTech nologyCo. , Ltd. - _ + _ dmi.product.sku : chaîne par défaut dmi.product. version : -CF - dmi.sys.vendor : Gigabyte Technology Co., Ltd. + dmi.sys.vendor : Gigabyte Technology Co., Ltd. version.compiz : compiz N/A version.libdrm2 : libdrm2 2.4.113- 2~ubuntu0. Version 22.04.1 . libgl1- mesa-dri : libgl1-mesa-dri 23.0.4-0ubuntu1 ~ version 22.04.1 - . libgl1- mesa-glx : version libgl1-mesa-glx + . libgl1-mesa-glx : version libgl1-mesa-glx N/A. xserver-xorg-core : xserver-xorg-core 2:21.1. 4-2ubuntu1. 7 ~ 22.04. 8 - versions. xserver-xorg-input-evdev : xserver-xorg-input-evdev version N/A - . xserver-xorg-video-ati : xserver-xorg-video-ati 1:19.1.0-2ubuntu1 - version. xserver-xorg-video-intel : xserver-xorg-video-intel 2:2.99. 917+git20210115-1version + versions. xserver- xorg-input- evdev : xserver- xorg-input- evdev version N/A + . xserver- xorg-video- ati : xserver- xorg-video- ati 1:19.1.0-2ubuntu1 + version. xserver- xorg-video- intel : xserver- xorg-video- intel 2:2.99. 917+git20210115 -1version . xserver- xorg-video- nouveau : xserver- xorg-video- nouveau 1:1.0.17-2build1 ** Description changed: - Sous X11, GNOME, L'écran est configuré pour s'éteindre toutes les 2 minutes depuis les paramètres. L'écran s'éteint
[Desktop-packages] [Bug 2051074] Re: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking
Hi Kai-Heng, It looks like you're working on this through Salsa. The debdiffs on this bug mean that this shows in the sponsor queue, so I'm removing Ubuntu Sponsors from this bug since there looks like no action to take for Sponsors. Please re-subscribe Sponsors if you feel otherwise. Thanks! -- 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/2051074 Title: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking Status in HWE Next: New Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: New Status in mutter source package in Mantic: New Status in mutter source package in Noble: Fix Committed Bug description: [Impact] On systems equipped with reduced blanking panel, mirror mode can result to no image on external monitor. The reason is due to current fallback modes don't have pixelclock for reduced blanking, so inadequate refresh rate is used to mode set, and result with atomic commit failure. [Fix] https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3449 Add reduced blanking (RB) to fallback modes, so mutter can use RB mode to meet pixelclock requirement in order to pick the right refresh rate. [Test] Connect an external monitor to affected system. Use the monitor hotkey to switch to mirror mode or use GNOME control center to choose mirror mode. With the patch included, the issue is no longer observed. [Where problems could occur] The modelines of reduced blanking have reversed Hsync and Vsync flags, so if the driver doesn't handle those flags correctly, the atomic modeset/commit may fail. I haven't observe any issue on Intel/AMD/Nvidia GPU so far. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051074/+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 2052529] Re: L'économiseur d'écran ne se déclenche pas comme il le devrait
** Description changed: - The screen is set to turn off every 2 minutes. The screen turns off fine, however it comes back on a few seconds later. Only the screen saver (black screen but not turned off) works. - I should point out that when the screen turns off and turns back on a few seconds later, an "automatic source detection" message appears, which suggests that the screen automatically detects a source and then decides to turn back on . The problem is that I cannot deactivate this "automatic search for sources" from the menu which is at the origin of the problem I think. - My screen is a BenQ Mobiuz model. + L'écran est configuré pour s'éteindre toutes les 2 minutes. L'écran s'éteint bien, mais il se rallume quelques secondes plus tard. Seul l'économiseur d'écran (écran noir mais non éteint) fonctionne. + Précisons que lorsque l'écran s'éteint et se rallume quelques secondes plus tard, un message "détection automatique de source" apparaît, ce qui laisse penser que l'écran détecte automatiquement une source puis décide de se rallumer. Le problème est que je n'arrive pas à désactiver cette "recherche automatique des sources" depuis le menu ce qui est à l'origine du problème je pense. + Mon écran est un modèle BenQ Mobiuz. - I'm using Ubuntu 22.04.3 LTS + J'utilise Ubuntu 22.04.3 LTS - killianp@killianp ~> apt-cache Policy x11-server-utils + killianp@killianp ~> apt-cache Policy x11-server-utils E: L'opération Policy n'est pas valable - I'm waiting that the screen turn off in order to save its duration. + J'attends que l'écran s'éteigne pour sauvegarder sa durée. + J'ai indiqué que le paquet était lié à x11-xserver-utils mais je ne suis pas sûr, je suis sur Wayland et je pense que l'économiseur d'écran est directement lié à Gnome. - Thanks a lot. + Merci beaucoup. - Achille Pyrea + Achille Pyréa - ProblemType: Bug - DistroRelease: Ubuntu 22.04 - Package: x11-xserver-utils 7.7+9build1 - 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 - BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' - CasperMD5CheckResult: pass - CompositorRunning: None - CurrentDesktop: ubuntu:GNOME - Date: Tue Feb 6 16:40:22 2024 - DistUpgraded: Fresh install - DistroCodename: jammy - DistroVariant: ubuntu - DkmsStatus: - virtualbox/6.1.48, 6.5.0-14-generic, x86_64: installed - virtualbox/6.1.48, 6.5.0-15-generic, x86_64: installed - GraphicsCard: - Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] [1002:73ff] (rev c7) (prog-if 00 [VGA controller]) -Subsystem: XFX Limited Navi 23 [Radeon RX 6600/6600 XT/6600M] [1eae:6505] - InstallationDate: Installed on 2023-12-30 (37 days ago) - InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) - MachineType: Gigabyte Technology Co., Ltd. B550 GAMING X V2 - ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=fr_FR.UTF-8 - SHELL=/usr/bin/fish - ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic root=UUID=66dfa360-6016-472f-b236-fef2f4bb1174 ro quiet splash vt.handoff=7 - RebootRequiredPkgs: Error: path contained symlinks. - SourcePackage: x11-xserver-utils - UpgradeStatus: No upgrade log present (probably fresh install) - dmi.bios.date: 09/20/2023 - dmi.bios.release: 5.17 - dmi.bios.vendor: American Megatrends International, LLC. - dmi.bios.version: FDc - dmi.board.asset.tag: Default string - dmi.board.name: B550 GAMING X V2 - dmi.board.vendor: Gigabyte Technology Co., Ltd. - dmi.board.version: x.x - dmi.chassis.asset.tag: Default string - dmi.chassis.type: 3 - dmi.chassis.vendor: Default string - dmi.chassis.version: Default string - dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFDc:bd09/20/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550GAMINGXV2:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnB550GAMINGXV2:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: - dmi.product.family: B550 MB - dmi.product.name: B550 GAMING X V2 - dmi.product.sku: Default string - dmi.product.version: -CF - dmi.sys.vendor: Gigabyte Technology Co., Ltd. - version.compiz: compiz N/A - version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 - version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 - version.libgl1-mesa-glx: libgl1-mesa-glx N/A - version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 - version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A - version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 - version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 - version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 + Type de problème : Bug + DistroRelease : Ubuntu 22.04 + Package : x11-xserver-utils 7.7+9build1 + ProcVersionSignature : Ubuntu 6.5.0-15. 15~22.04. 1-generic 6.5.3 + Uname : Linux 6.5.0-15-generic x86_64 +
[Desktop-packages] [Bug 2052529] [NEW] L'économiseur d'écran ne se déclenche pas comme il le devrait
Public bug reported: The screen is set to turn off every 2 minutes. The screen turns off fine, however it comes back on a few seconds later. Only the screen saver (black screen but not turned off) works. I should point out that when the screen turns off and turns back on a few seconds later, an "automatic source detection" message appears, which suggests that the screen automatically detects a source and then decides to turn back on . The problem is that I cannot deactivate this "automatic search for sources" from the menu which is at the origin of the problem I think. My screen is a BenQ Mobiuz model. I'm using Ubuntu 22.04.3 LTS killianp@killianp ~> apt-cache Policy x11-server-utils E: L'opération Policy n'est pas valable I'm waiting that the screen turn off in order to save its duration. Thanks a lot. Achille Pyrea ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: x11-xserver-utils 7.7+9build1 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 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 6 16:40:22 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.48, 6.5.0-14-generic, x86_64: installed virtualbox/6.1.48, 6.5.0-15-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] [1002:73ff] (rev c7) (prog-if 00 [VGA controller]) Subsystem: XFX Limited Navi 23 [Radeon RX 6600/6600 XT/6600M] [1eae:6505] InstallationDate: Installed on 2023-12-30 (37 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Gigabyte Technology Co., Ltd. B550 GAMING X V2 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/usr/bin/fish ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic root=UUID=66dfa360-6016-472f-b236-fef2f4bb1174 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: x11-xserver-utils UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: FDc dmi.board.asset.tag: Default string dmi.board.name: B550 GAMING X V2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFDc:bd09/20/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550GAMINGXV2:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnB550GAMINGXV2:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B550 MB dmi.product.name: B550 GAMING X V2 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: x11-xserver-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11-xserver-utils in Ubuntu. https://bugs.launchpad.net/bugs/2052529 Title: L'économiseur d'écran ne se déclenche pas comme il le devrait Status in x11-xserver-utils package in Ubuntu: New Bug description: The screen is set to turn off every 2 minutes. The screen turns off fine, however it comes back on a few seconds later. Only the screen saver (black screen but not turned off) works. I should point out that when the screen turns off and turns back on a few seconds later, an "automatic source detection" message appears, which suggests that the screen automatically detects a source and then decides to turn back on . The problem is that I cannot deactivate this "automatic search for sources" from the menu which is at the origin of the problem I think. My screen is a BenQ Mobiuz model. I'm using Ubuntu 22.04.3 LTS killianp@killianp ~> apt-cache Policy x11-server-utils E: L'opération Policy n'est pas valable I'm waiting that the screen turn off in order to save its duration. Thanks a lot. Achille Pyrea ProblemType: Bug DistroRelease: Ubuntu 22.04
[Desktop-packages] [Bug 2015405] Re: spice-vdagent crashed with SIGSEGV
** Tags added: noble -- 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/2015405 Title: spice-vdagent crashed with SIGSEGV Status in spice-vdagent package in Ubuntu: Confirmed Bug description: Just launching an ubuntu 23.04 beta VM on libvirtd/qemu/KVM and this brings the reporting crash app as soon as loging into the desktop. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: spice-vdagent 0.22.1-3 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 5 23:21:08 2023 ExecutablePath: /usr/bin/spice-vdagent InstallationDate: Installed on 2023-03-31 (5 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329) ProcCmdline: /usr/bin/spice-vdagent ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x559a23cd00e0:mov(%r15),%rdi PC (0x559a23cd00e0) ok source "(%r15)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: spice-vdagent StacktraceTop: () __libc_start_call_main (main=main@entry=0x559a23ccfe80, argc=argc@entry=1, argv=argv@entry=0x7ffce18a7c08) at ../sysdeps/nptl/libc_start_call_main.h:58 __libc_start_main_impl (main=0x559a23ccfe80, argc=1, argv=0x7ffce18a7c08, init=, fini=, rtld_fini=, stack_end=0x7ffce18a7bf8) at ../csu/libc-start.c:360 () Title: spice-vdagent crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/2015405/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
** Changed in: kalgebra (Ubuntu) Importance: Undecided => High ** Changed in: kalgebra (Ubuntu) Status: Confirmed => In Progress ** Changed in: kalgebra (Ubuntu) Milestone: None => ubuntu-24.04-feature-freeze ** Changed in: kalgebra (Ubuntu) Assignee: (unassigned) => Scarlett Gately Moore (scarlettmoore) ** Changed in: konqueror (Ubuntu) Importance: Undecided => High ** Changed in: konqueror (Ubuntu) Status: Confirmed => In Progress ** Changed in: konqueror (Ubuntu) Milestone: None => ubuntu-24.04-feature-freeze ** Changed in: konqueror (Ubuntu) Assignee: (unassigned) => Scarlett Gately Moore (scarlettmoore) ** Changed in: kontact (Ubuntu) Status: Confirmed => In Progress ** Changed in: kontact (Ubuntu) Milestone: None => ubuntu-24.04-feature-freeze ** Changed in: kontact (Ubuntu) Assignee: (unassigned) => Scarlett Gately Moore (scarlettmoore) ** Changed in: tellico (Ubuntu) Importance: Undecided => High ** Changed in: tellico (Ubuntu) Status: Confirmed => In Progress ** Changed in: tellico (Ubuntu) Milestone: None => ubuntu-24.04-feature-freeze ** Changed in: tellico (Ubuntu) Assignee: (unassigned) => Scarlett Gately Moore (scarlettmoore) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bubblewrap in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in akregator package in Ubuntu: In Progress Status in angelfish package in Ubuntu: In Progress Status in apparmor package in Ubuntu: Confirmed Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: In Progress Status in devhelp package in Ubuntu: Confirmed Status in digikam package in Ubuntu: In Progress Status in epiphany-browser package in Ubuntu: Confirmed Status in evolution package in Ubuntu: Confirmed Status in falkon package in Ubuntu: In Progress Status in freecad package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: In Progress Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: In Progress Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Confirmed Status in kiwix package in Ubuntu: Confirmed Status in konqueror package in Ubuntu: In Progress Status in kontact package in Ubuntu: In Progress Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Confirmed Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Confirmed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: In Progress Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akregator/+bug/2046844/+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 2016013] Re: New windows don't get centered if Desktop Icons NG is loaded
Sorry for the delay. Yes, it is because of that. In Gnome 46 is a new API that allows to mark a window as "desktop window" and should fix it, and I want to use it, but I'm waiting for 24.04 to go out because it would be a big change, and I don't want to risk a LTS. -- 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/2016013 Title: New windows don't get centered if Desktop Icons NG is loaded Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: New windows don't get centered if Desktop Icons NG is loaded. With vanilla GNOME, if an app window is too large for tiling (larger than a quarter of the screen) then it will be centered by default. But this doesn't happen when DING is loaded, probably because DING is incorrectly treated as an app window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/2016013/+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 2052512] [NEW] uninstalling snap crashes xwayland server
Public bug reported: environment * desktop: Ubuntu 22.04.3 LTS * xwayland: 2:22.1.1-1ubuntu0.11 * kernel: 5.15.0-92-generic * desktop: KDE (kwin 5.24.7) * snap: 2.60.4 * snapcraft: 8.0.2 step to reproduce (with the snapcraft definition below): * snapcraft try --lxd * snap try * snap remove vlc my snapcraft.yaml file (I only kept the interesting bits): ``` base: core22 confinement: strict compression: lzo plugs: dot-config-aacs: interface: personal-files read: - $HOME/.config/aacs apps: vlc: extensions: - kde-neon plugs: - unity7 - network - network-bind - home - opengl - alsa - pulseaudio - mount-observe - optical-drive - camera - removable-media - screen-inhibit-control - x11 - wayland - desktop - desktop-legacy - dvb - audio-playback - audio-record - jack1 - avahi-control - dot-config-aacs slots: - mpris ``` xwayland backtrace gives me ``` #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139859840395456) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=139859840395456) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=139859840395456, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x7f33a87de476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x7f33a87c47f3 in __GI_abort () at ./stdlib/abort.c:79 #5 0x558b0cfc12a0 in OsAbort () at ../os/utils.c:1353 #6 0x558b0cfccd3f in AbortServer () at ../os/log.c:879 #7 FatalError (f=0x558b0d020090 "Caught signal %d (%s). Server aborting\n") at ../os/log.c:1017 #8 0x558b0cfbf494 in OsSigHandler (unused=, sip=0x7fff8fb38df0, signo=7) at ../os/osinit.c:156 #9 OsSigHandler (signo=7, sip=0x7fff8fb38df0, unused=) at ../os/osinit.c:110 #10 #11 xwl_screen_destroy_drm_lease_device (xwl_screen=0x558b0e4cd770, wp_drm_lease_device_v1=0x558b0e668b20) at ../hw/xwayland/xwayland-drm-lease.c:430 #12 0x7f33a867be2e in ?? () from /lib/x86_64-linux-gnu/libffi.so.8 #13 0x7f33a8678493 in ?? () from /lib/x86_64-linux-gnu/libffi.so.8 #14 0x7f33a8e15ad0 in ?? () from /lib/x86_64-linux-gnu/libwayland-client.so.0 #15 0x7f33a8e16243 in ?? () from /lib/x86_64-linux-gnu/libwayland-client.so.0 #16 0x7f33a8e1643c in wl_display_dispatch_queue_pending () from /lib/x86_64-linux-gnu/libwayland-client.so.0 #17 0x558b0ce984bb in xwl_read_events (xwl_screen=0x558b0da53550) at ../hw/xwayland/xwayland-screen.c:482 #18 xwl_read_events (xwl_screen=0x558b0da53550) at ../hw/xwayland/xwayland-screen.c:469 #19 0x558b0cfc0a61 in ospoll_wait (ospoll=0x558b0da4f210, timeout=) at ../os/ospoll.c:657 #20 0x558b0cf00e30 in WaitForSomething (are_ready=0) at ../os/WaitFor.c:208 #21 Dispatch () at ../dix/dispatch.c:492 #22 0x558b0ce8ec63 in dix_main (envp=, argv=, argc=) at ../dix/main.c:271 #23 main (argc=, argv=, envp=) at ../dix/stubmain.c:34 ``` ** Affects: xwayland (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2052512 Title: uninstalling snap crashes xwayland server Status in xwayland package in Ubuntu: New Bug description: environment * desktop: Ubuntu 22.04.3 LTS * xwayland: 2:22.1.1-1ubuntu0.11 * kernel: 5.15.0-92-generic * desktop: KDE (kwin 5.24.7) * snap: 2.60.4 * snapcraft: 8.0.2 step to reproduce (with the snapcraft definition below): * snapcraft try --lxd * snap try * snap remove vlc my snapcraft.yaml file (I only kept the interesting bits): ``` base: core22 confinement: strict compression: lzo plugs: dot-config-aacs: interface: personal-files read: - $HOME/.config/aacs apps: vlc: extensions: - kde-neon plugs: - unity7 - network - network-bind - home - opengl - alsa - pulseaudio - mount-observe - optical-drive - camera - removable-media - screen-inhibit-control - x11 - wayland - desktop - desktop-legacy - dvb - audio-playback - audio-record - jack1 - avahi-control - dot-config-aacs slots: - mpris ``` xwayland backtrace gives me ``` #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139859840395456) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=139859840395456) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=139859840395456, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x7f33a87de476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x7f33a87c47f3 in __GI_abort () at ./stdlib/abort.c:79 #5 0x558b0cfc12a0 in
[Desktop-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
** Changed in: akregator (Ubuntu) Importance: Undecided => Critical ** Changed in: akregator (Ubuntu) Status: Confirmed => In Progress ** Changed in: akregator (Ubuntu) Assignee: (unassigned) => Scarlett Gately Moore (scarlettmoore) ** Changed in: angelfish (Ubuntu) Importance: Undecided => Critical ** Changed in: angelfish (Ubuntu) Status: Confirmed => In Progress ** Changed in: angelfish (Ubuntu) Assignee: (unassigned) => Scarlett Gately Moore (scarlettmoore) ** Changed in: cantor (Ubuntu) Importance: Undecided => Critical ** Changed in: cantor (Ubuntu) Status: Confirmed => In Progress ** Changed in: cantor (Ubuntu) Milestone: None => ubuntu-24.04-feature-freeze ** Changed in: cantor (Ubuntu) Assignee: (unassigned) => Scarlett Gately Moore (scarlettmoore) ** Changed in: angelfish (Ubuntu) Milestone: None => ubuntu-24.04-feature-freeze ** Changed in: akregator (Ubuntu) Milestone: None => ubuntu-24.04-feature-freeze ** Changed in: digikam (Ubuntu) Status: Confirmed => In Progress ** Changed in: digikam (Ubuntu) Milestone: None => ubuntu-24.04-feature-freeze ** Changed in: digikam (Ubuntu) Assignee: (unassigned) => Scarlett Gately Moore (scarlettmoore) ** Changed in: falkon (Ubuntu) Status: Confirmed => In Progress ** Changed in: falkon (Ubuntu) Milestone: None => ubuntu-24.04-feature-freeze ** Changed in: falkon (Ubuntu) Assignee: (unassigned) => Scarlett Gately Moore (scarlettmoore) ** Changed in: ghostwriter (Ubuntu) Importance: Undecided => High ** Changed in: ghostwriter (Ubuntu) Status: Confirmed => In Progress ** Changed in: ghostwriter (Ubuntu) Milestone: None => ubuntu-24.04-feature-freeze ** Changed in: ghostwriter (Ubuntu) Assignee: (unassigned) => Scarlett Gately Moore (scarlettmoore) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bubblewrap in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in akregator package in Ubuntu: In Progress Status in angelfish package in Ubuntu: In Progress Status in apparmor package in Ubuntu: Confirmed Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: In Progress Status in devhelp package in Ubuntu: Confirmed Status in digikam package in Ubuntu: In Progress Status in epiphany-browser package in Ubuntu: Confirmed Status in evolution package in Ubuntu: Confirmed Status in falkon package in Ubuntu: In Progress Status in freecad package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: In Progress Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Confirmed Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Confirmed Status in kiwix package in Ubuntu: Confirmed Status in konqueror package in Ubuntu: Confirmed Status in kontact package in Ubuntu: Confirmed Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Confirmed Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Confirmed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Confirmed Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akregator/+bug/2046844/+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 2047356] Re: gvfs-disks2-volume-monitor and gsd-housekeeping processes can eat a lot of CPU with k3s workload
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gvfs (Ubuntu)
Status: New => Confirmed
--
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/2047356
Title:
gvfs-disks2-volume-monitor and gsd-housekeeping processes can eat a
lot of CPU with k3s workload
Status in gvfs package in Ubuntu:
Confirmed
Bug description:
On Ubuntu 22.04.3 desktop, when running a k3s workload that uses volumes
(using default local-path storageClass), process gvfs-disks2-volume-monitor can
take around 100% of one CPU core, and process gsd-housekeeping around 25% of
one CPU core.
Even if the actual k3s workload is idle.
Steps To Reproduce:
- Use or install a desktop Ubuntu 22.04.3 (with default settings)
- Install K3s on it (current version is "v1.28.4+k3s2"), with default
settings: "curl -sfL https://get.k3s.io | sh -"
- Deploy k8s manifests with many volumes, like
https://gitlab.com/-/snippets/3634487: "wget
https://gitlab.com/-/snippets/3634487/raw/main/deployment-with-many-volumes.yaml
&& sudo k3s kubectl apply -f deployment-with-many-volumes.yaml"
- Check CPU consumption on the host, with top, gnome-system-monitor or
anything else
Expected behavior:
Gnome desktop tools should not interfere with k3s.
Actual behavior:
Processes gvfs-disks2-volume-monitor and gsd-housekeeping consume a lot of
CPU, at least at provisioning time.
Same CPU consumption if you then remove the workload ("sudo k3s kubectl
delete -f deployment-with-many-volumes.yaml"), until the PVs are deleted by k3s.
I have other workloads (with data in PVs) where this CPU consumption is
always there, when the workload is running (even if idle)
Additional context:
The symptoms are very similar to https://github.com/k3s-io/k3s/issues/522,
but the workaround of comment
https://github.com/k3s-io/k3s/issues/522#issuecomment-811737023 (adding a udev
rule to ignore some loopback devices) does not help.
Executing "systemctl stop --user gvfs-udisks2-volume-monitor" can be a
temporary workaround
Technical details:
k3s uses containerd to run containers. The local-path storageClass mounts
local volumes (physically stored in /var/lib/rancher/k3s/storage subfolders) in
these containers.
I suppose gnome applications try to scan these mount points. In this case,
the solution might be to make them ignore them, a bit like
https://github.com/moby/moby/blob/master/contrib/udev/80-docker.rules does for
docker
NB: Was initially reported on
https://github.com/k3s-io/k3s/issues/9093
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/2047356/+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 2047356] Re: gvfs-disks2-volume-monitor and gsd-housekeeping processes can eat a lot of CPU with k3s workload
Thanks for your feedback, I feel less alone.
Can you mark that this issue affects you at the top of this page (under the
issue description)?
--
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/2047356
Title:
gvfs-disks2-volume-monitor and gsd-housekeeping processes can eat a
lot of CPU with k3s workload
Status in gvfs package in Ubuntu:
New
Bug description:
On Ubuntu 22.04.3 desktop, when running a k3s workload that uses volumes
(using default local-path storageClass), process gvfs-disks2-volume-monitor can
take around 100% of one CPU core, and process gsd-housekeeping around 25% of
one CPU core.
Even if the actual k3s workload is idle.
Steps To Reproduce:
- Use or install a desktop Ubuntu 22.04.3 (with default settings)
- Install K3s on it (current version is "v1.28.4+k3s2"), with default
settings: "curl -sfL https://get.k3s.io | sh -"
- Deploy k8s manifests with many volumes, like
https://gitlab.com/-/snippets/3634487: "wget
https://gitlab.com/-/snippets/3634487/raw/main/deployment-with-many-volumes.yaml
&& sudo k3s kubectl apply -f deployment-with-many-volumes.yaml"
- Check CPU consumption on the host, with top, gnome-system-monitor or
anything else
Expected behavior:
Gnome desktop tools should not interfere with k3s.
Actual behavior:
Processes gvfs-disks2-volume-monitor and gsd-housekeeping consume a lot of
CPU, at least at provisioning time.
Same CPU consumption if you then remove the workload ("sudo k3s kubectl
delete -f deployment-with-many-volumes.yaml"), until the PVs are deleted by k3s.
I have other workloads (with data in PVs) where this CPU consumption is
always there, when the workload is running (even if idle)
Additional context:
The symptoms are very similar to https://github.com/k3s-io/k3s/issues/522,
but the workaround of comment
https://github.com/k3s-io/k3s/issues/522#issuecomment-811737023 (adding a udev
rule to ignore some loopback devices) does not help.
Executing "systemctl stop --user gvfs-udisks2-volume-monitor" can be a
temporary workaround
Technical details:
k3s uses containerd to run containers. The local-path storageClass mounts
local volumes (physically stored in /var/lib/rancher/k3s/storage subfolders) in
these containers.
I suppose gnome applications try to scan these mount points. In this case,
the solution might be to make them ignore them, a bit like
https://github.com/moby/moby/blob/master/contrib/udev/80-docker.rules does for
docker
NB: Was initially reported on
https://github.com/k3s-io/k3s/issues/9093
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/2047356/+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 2047356] Re: gvfs-disks2-volume-monitor and gsd-housekeeping processes can eat a lot of CPU with k3s workload
I have the same issue. It is hard to work with docker as those two
processes consume almost 70% of my cpu. The udev rule does not help me
:/
--
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/2047356
Title:
gvfs-disks2-volume-monitor and gsd-housekeeping processes can eat a
lot of CPU with k3s workload
Status in gvfs package in Ubuntu:
New
Bug description:
On Ubuntu 22.04.3 desktop, when running a k3s workload that uses volumes
(using default local-path storageClass), process gvfs-disks2-volume-monitor can
take around 100% of one CPU core, and process gsd-housekeeping around 25% of
one CPU core.
Even if the actual k3s workload is idle.
Steps To Reproduce:
- Use or install a desktop Ubuntu 22.04.3 (with default settings)
- Install K3s on it (current version is "v1.28.4+k3s2"), with default
settings: "curl -sfL https://get.k3s.io | sh -"
- Deploy k8s manifests with many volumes, like
https://gitlab.com/-/snippets/3634487: "wget
https://gitlab.com/-/snippets/3634487/raw/main/deployment-with-many-volumes.yaml
&& sudo k3s kubectl apply -f deployment-with-many-volumes.yaml"
- Check CPU consumption on the host, with top, gnome-system-monitor or
anything else
Expected behavior:
Gnome desktop tools should not interfere with k3s.
Actual behavior:
Processes gvfs-disks2-volume-monitor and gsd-housekeeping consume a lot of
CPU, at least at provisioning time.
Same CPU consumption if you then remove the workload ("sudo k3s kubectl
delete -f deployment-with-many-volumes.yaml"), until the PVs are deleted by k3s.
I have other workloads (with data in PVs) where this CPU consumption is
always there, when the workload is running (even if idle)
Additional context:
The symptoms are very similar to https://github.com/k3s-io/k3s/issues/522,
but the workaround of comment
https://github.com/k3s-io/k3s/issues/522#issuecomment-811737023 (adding a udev
rule to ignore some loopback devices) does not help.
Executing "systemctl stop --user gvfs-udisks2-volume-monitor" can be a
temporary workaround
Technical details:
k3s uses containerd to run containers. The local-path storageClass mounts
local volumes (physically stored in /var/lib/rancher/k3s/storage subfolders) in
these containers.
I suppose gnome applications try to scan these mount points. In this case,
the solution might be to make them ignore them, a bit like
https://github.com/moby/moby/blob/master/contrib/udev/80-docker.rules does for
docker
NB: Was initially reported on
https://github.com/k3s-io/k3s/issues/9093
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/2047356/+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 1722603] Re: No automatic driver install for Apple facetime camera ( experimental working driver available)
** Description changed: - the facetime camera does not work on Ubuntu 17.10 out of the box. + the integrated facetime camera does not work on Ubuntu 22.04 out of the + box. the current workaround is outlined here: https://github.com/patjak/bcwc_pcie/wiki/Get-Started#additional-notes - would it be possible to have something simpler to follow or perhaps be built in? - --- + would it be possible to have this driver supported by ubuntu-drivers ? + + + Manual Dkms Solution : + + git clone https://github.com/ekimiateam/facetimehd + git clone https://github.com/patjak/facetimehd-firmware + make -C facetimehd-firmware/ deb + cp facetimehd-firmware/debian/*.deb . + cd facetimehd/ + dpkg-buildpackage -us -uc + cd .. + sudo apt install ./facetimehd*.deb + + - + ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: peter 1906 F pulseaudio - /dev/snd/controlC1: peter 1906 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: peter 1906 F pulseaudio + /dev/snd/controlC1: peter 1906 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-04-05 (553 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) MachineType: Apple Inc. MacBookPro12,1 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic.efi.signed root=UUID=540e40c6-4d83-4c9e-8dfe-18c9ab5e2234 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 RelatedPackageVersions: - linux-restricted-modules-4.13.0-12-generic N/A - linux-backports-modules-4.13.0-12-generic N/A - linux-firmware 1.169 + linux-restricted-modules-4.13.0-12-generic N/A + linux-backports-modules-4.13.0-12-generic N/A + linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-12-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-09 (1 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B33.1706181928 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Also affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1722603 Title: No automatic driver install for Apple facetime camera ( experimental working driver available) Status in linux package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: New Status in linux source package in Artful: Won't Fix Status in ubuntu-drivers-common source package in Artful: New Bug description: the integrated facetime camera does not work on Ubuntu 22.04 out of the box. the current workaround is outlined here: https://github.com/patjak/bcwc_pcie/wiki/Get-Started#additional-notes would it be possible to have this driver supported by ubuntu-drivers ? Manual Dkms Solution : git clone https://github.com/ekimiateam/facetimehd git clone https://github.com/patjak/facetimehd-firmware make -C facetimehd-firmware/ deb cp facetimehd-firmware/debian/*.deb . cd facetimehd/ dpkg-buildpackage -us -uc cd .. sudo apt install ./facetimehd*.deb - ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1906 F pulseaudio /dev/snd/controlC1: peter 1906 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-04-05 (553 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) MachineType: Apple Inc. MacBookPro12,1 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic.efi.signed root=UUID=540e40c6-4d83-4c9e-8dfe-18c9ab5e2234 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A
[Desktop-packages] [Bug 2043524] Re: audio disappeared after upgrade to Ubuntu 23.10
I also did a clean install since last report. The issue is still present -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2043524 Title: audio disappeared after upgrade to Ubuntu 23.10 Status in pulseaudio package in Ubuntu: Confirmed Bug description: I upgraded to Ubuntu 23.10 from 23.04. Everything seems to work except there is no audio output on streaming functions. The external bluetooth speaker is connected and detected. It is charged and responds to testing. Just no sound when playing videos or podcasts. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: owner 975 F wireplumber /dev/snd/seq:owner 971 F pipewire CasperMD5CheckResult: fail CurrentDesktop: KDE Date: Tue Nov 14 17:50:17 2023 InstallationDate: Installed on 2023-04-15 (213 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to mantic on 2023-11-09 (5 days ago) dmi.bios.date: 07/04/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-P31/W8 (MS-7788) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.0:bd07/04/2012:br4.6:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31/W8(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7788 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2043524/+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 2052492] Re: Pairing: passcode dialogue disappears in <1 second
Incomplete: Waiting for the bug to reoccur... It sounds to me like a kernel or hardware problem though, in which the device itself is believed to have disappeared, and so would the dialog. ** Tags added: mantic ** Package changed: bluez (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/2052492 Title: Pairing: passcode dialogue disappears in <1 second Status in Ubuntu: Incomplete Bug description: UPDATE: I am creating this bug in case it comes back again. My Fix was to put the bluetooth keyboard aside for a week (not use it), then reconnect after the laptop had been rebooted after an update and daily use. I will post the things that I tried, just in case: 1) There is something I messed that someone else can suggest; and 2) it occurs for someone else. I suspect that it will happen again at some stage. -- I am seeing this issue in Ubuntu 23.10. bluez 5.68-0ubuntu1.1 Hardware: Logi POP Keys https://www.logitech.com/en-au/products/keyboards/pop-keys-wireless-mechanical.920-011226.html I have managed to have it working in the past, but the 6-digit code pop-up disappears very quickly (as described, <1sec). System details - $ lsb_release -rd No LSB modules are available. Description: Ubuntu 23.10 Release: 23.10 - ii bluez 5.68-0ubuntu1.1amd64Bluetooth tools and daemons -- Bluetooth Device Logitech - Logi POP Keys (see link below) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2052492/+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
