[Desktop-packages] [Bug 2022941] Re: Zoom window not centered on text cursor
** Changed in: gnome-control-center Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2022941 Title: Zoom window not centered on text cursor Status in gnome-control-center: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: In certain applications, the zoomed in window moves to center on the text cursor instead of the pointer when typing but it does not focuses properly. This causes the typed text to be completely out of view. I use the default full-screen zoom in Ubuntu under the accessibility settings with the following settings: Magnification: 4.00 - 6.00 Magnifier position: Follow mouse cursor The problem primarily occurs when using Alt+Tab to witch tabs, but it sometimes appears when switching normally. To reproduce the problem, the following steps can be followed: - Activate the zoom function. - Start up Files and rename a file. - The zoomed in window will move to the upper left corner. Other applications in which the problem sometimes occurs (mostly when using Alt+Tab): Firefox, VSCode I also want to note that for other applications like Text Editor or Terminal, the cursor is always followed correctly. lsb_release -rd: Description: Ubuntu 22.04.2 LTS Release: 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2022941/+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 2051074] Re: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking
I think the preferred place for mutter patches is: https://salsa.debian.org/gnome-team/mutter/-/merge_requests -- 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 2051625] Re: package bluez 5.64-0ubuntu1.1 failed to install/upgrade: le sous-processus paquet bluez script post-installation installé a renvoyé un état de sortie d'erreur 1
Looks like systemd failed and started timing out for multiple things before this happened. So there's nothing bluez can do about that. ** Changed in: bluez (Ubuntu) Status: New => Invalid -- 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/2051625 Title: package bluez 5.64-0ubuntu1.1 failed to install/upgrade: le sous- processus paquet bluez script post-installation installé a renvoyé un état de sortie d'erreur 1 Status in bluez package in Ubuntu: Invalid Bug description: i don't know why ProblemType: Package DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Jan 29 19:22:29 2024 ErrorMessage: le sous-processus paquet bluez script post-installation installé a renvoyé un état de sortie d'erreur 1 InstallationDate: Installed on 2024-01-29 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. N56VZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic root=UUID=141cf8eb-0e88-4525-ba98-20cbc63c70ae ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: bluez Title: package bluez 5.64-0ubuntu1.1 failed to install/upgrade: le sous-processus paquet bluez script post-installation installé a renvoyé un état de sortie d'erreur 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N56VZ.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N56VZ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.212:bd08/28/2012:br4.6:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: N dmi.product.name: N56VZ dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: DC:85:DE:08:4E:27 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING RX bytes:1402 acl:0 sco:0 events:102 errors:0 TX bytes:6363 acl:0 sco:0 commands:102 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2051625/+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 2051617] Re: Raspberry Pi mouse buttons left and right unresponsive
Please check to see if the kernel is getting the button events:
sudo apt install evtest
sudo evtest
** Package changed: xorg (Ubuntu) => linux-raspi (Ubuntu)
** Changed in: linux-raspi (Ubuntu)
Status: New => Incomplete
** Package changed: linux-raspi (Ubuntu) => linux (Ubuntu)
** Summary changed:
- Raspberry Pi mouse buttons left and right unresponsive
+ Raspberry Pi mouse buttons left and right unresponsive (on a PC)
--
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/2051617
Title:
Raspberry Pi mouse buttons left and right unresponsive (on a PC)
Status in linux package in Ubuntu:
Incomplete
Bug description:
Using the event tracker tool
(
xmodmap -pp > ~/xmodmap-pp
xev | grep -i button
), buttons 4 and 5 are responsive, optical works (the cursor moves across the
screen).
Left and right click buttons are unresponsive. Mouse connected via
USB.
MOUSE INFO:
Raspberry Pi Mouse
CAN ICES-3 (B)/NMB-3(B)
Model No.: RPI-MOUSE
This issue has been extant every since I have tried to use this mouse.
Currently using Ubuntu Mantic Minotaur (23.10)
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
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
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 29 21:24:11 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus: virtualbox/7.0.12, 6.5.0-15-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02)
(prog-if 00 [VGA controller])
Subsystem: Dell CometLake-U GT2 [UHD Graphics] [1028:09ed]
InstallationDate: Installed on 2023-12-16 (45 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 001 Device 002: ID 8087:0026 Intel Corp. AX201 Bluetooth
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 3: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid,
1.5M
|__ Port 10: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 10: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
MachineType: {report['dmi.sys.vendor']} {report['dmi.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.5.0-15-generic
root=UUID=aa49e6e1-853a-4b59-81d9-ea0fcd3ca2cf ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/05/2021
dmi.bios.release: 1.10
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.10.1
dmi.board.name: 00V66M
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.10.1:bd08/05/2021:br1.10:svnDellInc.:pnLatitude3510:pvr:rvnDellInc.:rn00V66M:rvrA00:cvnDellInc.:ct10:cvr:sku09ED:
dmi.product.family: Latitude
dmi.product.name: Latitude 3510
dmi.product.sku: 09ED
dmi.sys.vendor: Dell Inc.
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.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051617/+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 2051548] Re: Problem in Booting and nomodeset
> Display resolution stuck at 800x600 after using nomodeset in grub. > But my Dell monitor has 1600x900 resolution. This is correct behaviour. "nomodeset" means to disable the graphics driver and to disable high resolution support. ** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu) ** Changed in: linux-hwe-6.5 (Ubuntu) Status: New => Invalid -- 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/2051548 Title: Problem in Booting and nomodeset Status in linux-hwe-6.5 package in Ubuntu: Invalid Bug description: Display resolution stuck at 800x600 after using nomodeset in grub. But my Dell monitor has 1600x900 resolution. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 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 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 29 19:27:23 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:2111] InstallationDate: Installed on 2024-01-26 (2 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic root=UUID=ba3dc7d3-3688-4f19-947e-a1d3aedb15f3 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2020 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61 dmi.board.vendor: INTEL Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/11/2020:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnH61:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. 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.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2051548/+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 2036388] Re: Login screen grey background flickers
** Tags added: flickerfreeboot noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2036388 Title: Login screen grey background flickers Status in gnome-shell package in Ubuntu: Triaged Bug description: Login screen grey background flickers on startup and again on login. It looks like it's trying to fade between two very similar shades of grey and there just aren't enough colours between them to fade smoothly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2036388/+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 2051625] [NEW] package bluez 5.64-0ubuntu1.1 failed to install/upgrade: le sous-processus paquet bluez script post-installation installé a renvoyé un état de sortie d'erreur 1
Public bug reported: i don't know why ProblemType: Package DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Jan 29 19:22:29 2024 ErrorMessage: le sous-processus paquet bluez script post-installation installé a renvoyé un état de sortie d'erreur 1 InstallationDate: Installed on 2024-01-29 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. N56VZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic root=UUID=141cf8eb-0e88-4525-ba98-20cbc63c70ae ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: bluez Title: package bluez 5.64-0ubuntu1.1 failed to install/upgrade: le sous-processus paquet bluez script post-installation installé a renvoyé un état de sortie d'erreur 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N56VZ.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N56VZ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.212:bd08/28/2012:br4.6:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: N dmi.product.name: N56VZ dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0: Type: Primary Bus: USB BD Address: DC:85:DE:08:4E:27 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING RX bytes:1402 acl:0 sco:0 events:102 errors:0 TX bytes:6363 acl:0 sco:0 commands:102 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- 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/2051625 Title: package bluez 5.64-0ubuntu1.1 failed to install/upgrade: le sous- processus paquet bluez script post-installation installé a renvoyé un état de sortie d'erreur 1 Status in bluez package in Ubuntu: New Bug description: i don't know why ProblemType: Package DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Jan 29 19:22:29 2024 ErrorMessage: le sous-processus paquet bluez script post-installation installé a renvoyé un état de sortie d'erreur 1 InstallationDate: Installed on 2024-01-29 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. N56VZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic root=UUID=141cf8eb-0e88-4525-ba98-20cbc63c70ae ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: bluez Title: package bluez 5.64-0ubuntu1.1 failed to install/upgrade: le sous-processus paquet bluez script post-installation installé a renvoyé un état de sortie d'erreur 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N56VZ.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N56VZ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.212:bd08/28/2012:br4.6:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: N dmi.product.name: N56VZ dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: Primary Bus: USB BD
[Desktop-packages] [Bug 2045245] Re: ubuntu22.04 ibus Chinese pinying input not response
[Expired for ibus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ibus (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2045245 Title: ubuntu22.04 ibus Chinese pinying input not response Status in ibus package in Ubuntu: Expired Bug description: I have used 22.04 many times, and I encountered this problem every time. During the first period of installing the system, everything was fine, but once I used the system for more than a few months, the ibus started to stop responding and I could not enter. There is no response when pressing any keys on the keyboard. The only solution is to manually click the input method icon in the upper right corner, switch to English, and then enter `ibus restart`. But this problem of input method not responding is too frequent and occurs every few minutes. I can't stand this torture anymore, and I now use a third-party input method. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2045245/+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 2051617] Re: Raspberry Pi mouse buttons left and right unresponsive
** 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/2051617
Title:
Raspberry Pi mouse buttons left and right unresponsive
Status in xorg package in Ubuntu:
New
Bug description:
Using the event tracker tool
(
xmodmap -pp > ~/xmodmap-pp
xev | grep -i button
), buttons 4 and 5 are responsive, optical works (the cursor moves across the
screen).
Left and right click buttons are unresponsive. Mouse connected via
USB.
MOUSE INFO:
Raspberry Pi Mouse
CAN ICES-3 (B)/NMB-3(B)
Model No.: RPI-MOUSE
This issue has been extant every since I have tried to use this mouse.
Currently using Ubuntu Mantic Minotaur (23.10)
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
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
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 29 21:24:11 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus: virtualbox/7.0.12, 6.5.0-15-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02)
(prog-if 00 [VGA controller])
Subsystem: Dell CometLake-U GT2 [UHD Graphics] [1028:09ed]
InstallationDate: Installed on 2023-12-16 (45 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 001 Device 002: ID 8087:0026 Intel Corp. AX201 Bluetooth
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 3: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid,
1.5M
|__ Port 10: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 10: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
MachineType: {report['dmi.sys.vendor']} {report['dmi.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.5.0-15-generic
root=UUID=aa49e6e1-853a-4b59-81d9-ea0fcd3ca2cf ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/05/2021
dmi.bios.release: 1.10
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.10.1
dmi.board.name: 00V66M
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.10.1:bd08/05/2021:br1.10:svnDellInc.:pnLatitude3510:pvr:rvnDellInc.:rn00V66M:rvrA00:cvnDellInc.:ct10:cvr:sku09ED:
dmi.product.family: Latitude
dmi.product.name: Latitude 3510
dmi.product.sku: 09ED
dmi.sys.vendor: Dell Inc.
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.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2051617/+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 2051383] Re: gnome-shell high CPU utilization when moving mouse cursor
Thanks. And good catch, yes it should be MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 on 22.04 It sounds like the main issue is the input rate of the Razer DeathAdder V2 and gnome-shell's inefficient processing of a high event rate. You should be able to bring it under control with kernel parameter usbhid.mousepoll=2 (or 4 or 8). But this is still a gnome-shell performance bug. ** Summary changed: - gnome-shell high CPU utilization when moving mouse cursor + gnome-shell high CPU utilization when moving a high frequency mouse ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2051383 Title: gnome-shell high CPU utilization when moving a high frequency mouse Status in gnome-shell package in Ubuntu: New Bug description: When I simply move my mouse cursor on an empty desktop, gnome-shell's CPU usage goes up from 20% (when idle) to 60%, which causes stuttering. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 26 23:31:26 2024 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2018-03-17 (2140 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-02 (603 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051383/+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 2051574] Re: gnome-shell-portal-helper crashed with SIGTRAP in waitUntilSyncedOrDie() from WebKit::XDGDBusProxy::launch()
** Summary changed: - WiFi connecting gives error message every time but connects - Ubuntu 24.04 + gnome-shell-portal-helper crashed with SIGTRAP in waitUntilSyncedOrDie() from WebKit::XDGDBusProxy::launch() ** Information type changed from Private to Public ** Also affects: webkit2gtk (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2051574 Title: gnome-shell-portal-helper crashed with SIGTRAP in waitUntilSyncedOrDie() from WebKit::XDGDBusProxy::launch() Status in gnome-shell package in Ubuntu: New Status in webkit2gtk package in Ubuntu: New Bug description: Same as Summary ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: gnome-shell 45.3-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 29 08:56:29 2024 DisplayManager: gdm3 ExecutablePath: /usr/libexec/gnome-shell-portal-helper InstallationDate: Installed on 2024-01-25 (4 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240116) ProcCmdline: /usr/libexec/gnome-shell-portal-helper ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.3-1ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4 ?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4 ?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4 ?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4 ?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4 Title: gnome-shell-portal-helper crashed with signal 5 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/gnome-shell/+bug/2051574/+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 2022941] Re: Zoom window not centered on text cursor
The upstream issue just moved from https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5557 to https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2873 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #2873 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2873 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #2873 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2873 ** Project changed: gnome-shell => gnome-control-center ** Changed in: gnome-control-center Status: Fix Released => Unknown ** Changed in: gnome-control-center Remote watch: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5557 => gitlab.gnome.org/GNOME/gnome-control-center/-/issues #2873 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2022941 Title: Zoom window not centered on text cursor Status in gnome-control-center: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: In certain applications, the zoomed in window moves to center on the text cursor instead of the pointer when typing but it does not focuses properly. This causes the typed text to be completely out of view. I use the default full-screen zoom in Ubuntu under the accessibility settings with the following settings: Magnification: 4.00 - 6.00 Magnifier position: Follow mouse cursor The problem primarily occurs when using Alt+Tab to witch tabs, but it sometimes appears when switching normally. To reproduce the problem, the following steps can be followed: - Activate the zoom function. - Start up Files and rename a file. - The zoomed in window will move to the upper left corner. Other applications in which the problem sometimes occurs (mostly when using Alt+Tab): Firefox, VSCode I also want to note that for other applications like Text Editor or Terminal, the cursor is always followed correctly. lsb_release -rd: Description: Ubuntu 22.04.2 LTS Release: 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2022941/+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 2051454] Re: pipewire wireplumber can not detect the sound output device when using an unofficial linux kernel
This bug was fixed in the package pipewire - 1.0.1-1ubuntu3 --- pipewire (1.0.1-1ubuntu3) noble; urgency=medium * Fix broken audio when using a kernel without "fine grained unix mediation" patch (LP: #2051504, LP: #2051454) -- Sergio Costas Rodriguez Mon, 29 Jan 2024 19:03:45 +0200 ** Changed in: pipewire (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/2051454 Title: pipewire wireplumber can not detect the sound output device when using an unofficial linux kernel Status in apparmor package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: Fix Released Status in wireplumber package in Ubuntu: Confirmed Bug description: Ubuntu 24.04 noble I tested on Kernel-6.7.2, 6.7.1, 6.6.8, don't work. relating service status: gsd-media-keys[6441]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed pipewire-pulse[5768]: mod.protocol-pulse: client 0x5e701af4f9a0 [Mutter]: ERROR command:-1 (invalid) tag:418 error:25 (Input/output error) pipewire-pulse[5768]: mod.protocol-pulse: client 0x5e701af4f9a0 [Mutter]: ERROR command:-1 (invalid) tag:426 error:25 (Input/output error) pipewire-pulse[5298]: default: snap_get_audio_permissions: failed to get the AppArmor info. wireplumber[61568]: si-standard-link: in/out items are not valid anymore wireplumber[61568]: 2 of 2 PipeWire links failed to activate It's worked on kernel linux-image-6.5.0-14-generic. I built the same version 1.0.1 from the https://gitlab.freedesktop.org/pipewire source code, The sound card can be detected normally and shown in the gnome setting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2051454/+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 2051504] Re: 0.4.17-1ubuntu1 removes all output and input sinks in gnome settings
This bug was fixed in the package pipewire - 1.0.1-1ubuntu3 --- pipewire (1.0.1-1ubuntu3) noble; urgency=medium * Fix broken audio when using a kernel without "fine grained unix mediation" patch (LP: #2051504, LP: #2051454) -- Sergio Costas Rodriguez Mon, 29 Jan 2024 19:03:45 +0200 ** Changed in: pipewire (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/2051504 Title: 0.4.17-1ubuntu1 removes all output and input sinks in gnome settings Status in pipewire package in Ubuntu: Fix Released Status in wireplumber package in Ubuntu: Confirmed Bug description: After the changes committed as part of https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1995707 (wireplumber 0.4.17-1ubuntu1), all input and output sinks are removed from gnome settings on reboot. Playing audio through celluloid (mpv) still works with the default sink, while Firefox Nightly refuses to play anything. I've tested this on two machines now; - One running on nvidia+X11, without snapd installed. - Another running on intel+wayland, also without snapd. Reverting to 0.4.17-1 works fine, and gnome settings lists all output and input sinks again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2051504/+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 2051595] [NEW] Reapplying a layout with mapped applications makes the app unresponsive
Public bug reported: Current version of the Tiling Assistant extension has a bug with a "Tiling" animation. In some cases, one of the tiled windows become unresponsive. Steps to reproduce: 1. Launch 3 instances of GNOME Text Editor a. Launch First instance and input "1". We need this to differentiate windows b. Press Ctrl+N to launch the Second instance and input "2" there c. Repeat previous step for the Third instance 2. Tile First instance to the left side ; in the Tiling Popup select Second instance for the right side 3. Switch to the Third instance, tile it to left ; in the tiling pop-up select Second instance for the right side 4. Try to input something on the Second instance (right side). Visually nothing happens but after user switches focus to the left window, the newly typed text appears. 5. "Maximize"+"Restore" window actions will help to bring tiled window to the normal state. You can find video demonstration of this issue in the attachment. Workaround: disable "Tiling" animation CLI way to apply workaround: dconf write /org/gnome/shell/extensions/tiling-assistant/enable-tile- animations "false" GUI way to apply workaround: - Install Extension Manager (gnome-shell-extension-manager). Open preferences for "Tiling Assistant" extension. Instead of installing "Extension Manager", you can also launch "gnome-extensions prefs tiling-assistant@leleat-on-github" - Enable "Advanced/Experimental settings" (can be found under "bulb" icon on the left corner of the extension preferences window header-bar) - On the "General" page under the "Animations" section disable "Tiling" animation Upstream bug report: https://github.com/Leleat/Tiling- Assistant/issues/304 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell-extension-ubuntu-tiling-assistant 44-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 29 21:38:50 2024 InstallationDate: Installed on 2024-01-14 (15 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-tiling-assistant UpgradeStatus: Upgraded to noble on 2024-01-14 (15 days ago) ** Affects: gnome-shell-extension-tiling-assistant (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session ** Attachment added: "tiling-assistant__304.webm" https://bugs.launchpad.net/bugs/2051595/+attachment/5743265/+files/tiling-assistant__304.webm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-tiling-assistant in Ubuntu. https://bugs.launchpad.net/bugs/2051595 Title: Reapplying a layout with mapped applications makes the app unresponsive Status in gnome-shell-extension-tiling-assistant package in Ubuntu: New Bug description: Current version of the Tiling Assistant extension has a bug with a "Tiling" animation. In some cases, one of the tiled windows become unresponsive. Steps to reproduce: 1. Launch 3 instances of GNOME Text Editor a. Launch First instance and input "1". We need this to differentiate windows b. Press Ctrl+N to launch the Second instance and input "2" there c. Repeat previous step for the Third instance 2. Tile First instance to the left side ; in the Tiling Popup select Second instance for the right side 3. Switch to the Third instance, tile it to left ; in the tiling pop- up select Second instance for the right side 4. Try to input something on the Second instance (right side). Visually nothing happens but after user switches focus to the left window, the newly typed text appears. 5. "Maximize"+"Restore" window actions will help to bring tiled window to the normal state. You can find video demonstration of this issue in the attachment. Workaround: disable "Tiling" animation CLI way to apply workaround: dconf write /org/gnome/shell/extensions/tiling-assistant/enable-tile- animations "false" GUI way to apply workaround: - Install Extension Manager (gnome-shell-extension-manager). Open preferences for "Tiling Assistant" extension. Instead of installing "Extension Manager", you can also launch "gnome-extensions prefs tiling-assistant@leleat-on-github" - Enable "Advanced/Experimental settings" (can be found under "bulb" icon on the left corner of the extension preferences window header-bar) - On the "General" page under the "Animations" section disable "Tiling" animation Upstream bug report: https://github.com/Leleat/Tiling- Assistant/issues/304 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell-extension-ubuntu-tiling-assistant 44-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64
[Desktop-packages] [Bug 2048892] Re: Update nautilus to 45.2.1
https://launchpad.net/ubuntu/+source/nautilus/1:45.2.1-4ubuntu1 ** Changed in: nautilus (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2048892 Title: Update nautilus to 45.2.1 Status in nautilus package in Ubuntu: Fix Released Bug description: Hi, I wanted to point out that a newer version of nautilus 45 available. The release candidate shipped in Ubuntu is not meant to be packaged by distributions, as it is pre-release software and does potentially not include fixes made before release. See e.g. https://gitlab.gnome.org/GNOME/nautilus/-/tags/45.2.1 or . https://gitlab.gnome.org/GNOME/nautilus/-/tags/45.1 which is available in Debian unstable. Thank you for your consideration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2048892/+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 2022941] Re: Zoom window not centered on text cursor
** Changed in: gnome-shell Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2022941 Title: Zoom window not centered on text cursor Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Bug description: In certain applications, the zoomed in window moves to center on the text cursor instead of the pointer when typing but it does not focuses properly. This causes the typed text to be completely out of view. I use the default full-screen zoom in Ubuntu under the accessibility settings with the following settings: Magnification: 4.00 - 6.00 Magnifier position: Follow mouse cursor The problem primarily occurs when using Alt+Tab to witch tabs, but it sometimes appears when switching normally. To reproduce the problem, the following steps can be followed: - Activate the zoom function. - Start up Files and rename a file. - The zoomed in window will move to the upper left corner. Other applications in which the problem sometimes occurs (mostly when using Alt+Tab): Firefox, VSCode I also want to note that for other applications like Text Editor or Terminal, the cursor is always followed correctly. lsb_release -rd: Description: Ubuntu 22.04.2 LTS Release: 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2022941/+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 2051371] Re: Backspace in gnome-terminal often deletes cluster
> It's never the terminal emulator (whether GNOME Terminal or any other terminal app) that decides what to print on a backspace keypress. The only thing it does is that it tells over the tty line that the backspace key has been pressed. Makes sense. However, the user thinks of gnome-terminal because that's what he runs... > If your input method cannot generate the symbols you need, and you need to press backspace as a workaround to get that, moreover, you need to rely on one particular behavior of backspace, then I'd argue that it's all the fault of your input method, it should be able to produce straight away whatever you wish to end up with. Unfortunately that's not always possible. Please take a look at the wiki page under [1]. With complex writing systems there's more than one way to write a word which look 'correct' on the screen, but the order of the code points is different [2]. Not very good if you search for that word. Therefore Keyman allows to define keyboards that can auto-correct words so that you end up with the same order of the code points regardless which way you type [3]. And that requires to replace some codepoints typed previously. > Maybe the bug you _really_ wanted to report is that gnome-terminal doesn't use the "surrounding text" feature of input methods? That would be nice to have but until then it would be good to have backspace working properly. But as you wrote in an earlier comment that has nothing to do with gnome-terminal... [1] https://github.com/keymanapp/keyman/wiki/Backspace-and-cluster-deletion [2] https://www.sil.org/resources/archives/91817 [3] https://help.keyman.com/keyboard/khmer_angkor/1.0.7/KAK_Documentation_EN.pdf ** Also affects: bash (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2051371 Title: Backspace in gnome-terminal often deletes cluster Status in bash package in Ubuntu: New Status in gnome-terminal package in Ubuntu: New Bug description: If I have ខែ្ (U+1781 U+17c2 U+17d2) in the terminal and press backspace, the first backspace deletes U+17c2 U+17d2 so that I'm left with ខ (U+1781). Instead it should only delete the last codepoint, U+17d2. If I have ខែ (U+1781 U+17c2) a backspace deletes only U+17c2, similarly if I have ខ្ (U+1781 U+17d2) where the backspace deletes U+17d2. Further investigations show that backspace often deletes the entire cluster, i.e. diacritic(s) plus the base character, for example with x̣́ (U+0078 U+0301 U+0323) where a backspace deletes all three codepoints. gnome-terminal should only delete the last codepoint [1]. A real live example where this behavior is problematic is when using ibus-keyman with the Khmer Angkor keyboard [2]. When typing xEjmr the expected output is ខ្មែរ (U+1781 U+17d2 U+1798 U+17c2 U+179a). Keyman does some reordering while typing to put the codepoints in a standardized order. Because gnome-terminal lacks support for surrounding text, the codepoints have to be deleted by emitting several backspace keypresses. Because of the deletion of the cluster the result in gnome-terminal is ្មែរ (U+17d2 U+1798 U+17c2 U+179a). [1] https://github.com/keymanapp/keyman/wiki/Backspace-and-cluster-deletion [2] https://github.com/keymanapp/keyman/issues/10481 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-terminal 3.44.0-1ubuntu1 [modified: usr/libexec/gnome-terminal-server] ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 26 12:21:42 2024 InstallationDate: Installed on 2022-04-12 (653 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/2051371/+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 2051504] Re: 0.4.17-1ubuntu1 removes all output and input sinks in gnome settings
Added pipewire to the affected packages because the patch is for it. ** Also affects: pipewire (Ubuntu) Importance: Undecided Status: New ** Changed in: pipewire (Ubuntu) Assignee: (unassigned) => Sergio Costas (rastersoft-gmail) ** Changed in: pipewire (Ubuntu) Status: New => Confirmed ** Changed in: pipewire (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/2051504 Title: 0.4.17-1ubuntu1 removes all output and input sinks in gnome settings Status in pipewire package in Ubuntu: Confirmed Status in wireplumber package in Ubuntu: Confirmed Bug description: After the changes committed as part of https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1995707 (wireplumber 0.4.17-1ubuntu1), all input and output sinks are removed from gnome settings on reboot. Playing audio through celluloid (mpv) still works with the default sink, while Firefox Nightly refuses to play anything. I've tested this on two machines now; - One running on nvidia+X11, without snapd installed. - Another running on intel+wayland, also without snapd. Reverting to 0.4.17-1 works fine, and gnome settings lists all output and input sinks again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2051504/+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 2051381] Re: gnome-terminal-server crashed with SIGSEGV in g_utf8_pointer_to_offset()
Here's the link to the failing code (mainly for me so that I can find it again...): https://gitlab.gnome.org/GNOME/gtk/-/blame/a487deb1898ff1453168594f797d38c2b38187ac/modules/input/imwayland.c#L253 ** Package changed: gnome-terminal (Ubuntu) => gtk -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2051381 Title: gnome-terminal-server crashed with SIGSEGV in g_utf8_pointer_to_offset() Status in GTK+: New Bug description: When I'm using ibus-keyman with the IPA (SIL) keyboard in gnome- terminal and type n> (or just backspace after the n), gnome-terminal crashes. The reason is that in text_input_delete_surrounding_text() (modules/input/imwayland.c:253) before_length doesn't get checked. If we don't have surrounding text (as in this case) cursor_pointer is NULL and thus (cursor_pointer - before_length) results in an invalid pointer. The other question is why we don't have surrounding text, but that's a different problem. In any case we shouldn't crash in text_input_delete_surrounding_text(). I believe this is a different bug from #2036647 because of the different callstack and that we shouldn't call g_utf8_pointer_to_offset with invalid pointers. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-terminal 3.49.92-2ubuntu1 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 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Fri Jan 26 17:43:54 2024 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2024-01-23 (3 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) JournalErrors: Jan 26 17:43:53 hostname gnome-terminal-[4907]: g_atomic_ref_count_dec: assertion 'old_value > 0' failed Jan 26 17:43:53 hostname gnome-terminal-[4907]: g_atomic_ref_count_dec: assertion 'old_value > 0' failed Jan 26 17:44:00 hostname systemd[1623]: gnome-terminal-server.service: Main process exited, code=dumped, status=11/SEGV Jan 26 17:44:00 hostname systemd[1623]: gnome-terminal-server.service: Failed with result 'core-dump'. ProcCmdline: /usr/libexec/gnome-terminal-server ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f884099c180 : movzbl (%rsi),%ecx PC (0x7f884099c180) ok source "(%rsi)" (0x) not located in a known VMA region (needed readable region)! destination "%ecx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-terminal StacktraceTop: g_utf8_pointer_to_offset () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-wayland.so ?? () from /lib/x86_64-linux-gnu/libffi.so.8 ?? () from /lib/x86_64-linux-gnu/libffi.so.8 ffi_call () from /lib/x86_64-linux-gnu/libffi.so.8 Title: gnome-terminal-server crashed with SIGSEGV in g_utf8_pointer_to_offset() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users vboxsf modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2024-01-26T17:42:28.299334 separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2051381/+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 2051381] Re: gnome-terminal-server crashed with SIGSEGV in g_utf8_pointer_to_offset()
> So I'm wondering, shouldn't you have filed this bug against that component, rather than gnome-terminal? I guess you're right. Sorry. I'll try or re-assign. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2051381 Title: gnome-terminal-server crashed with SIGSEGV in g_utf8_pointer_to_offset() Status in GTK+: New Bug description: When I'm using ibus-keyman with the IPA (SIL) keyboard in gnome- terminal and type n> (or just backspace after the n), gnome-terminal crashes. The reason is that in text_input_delete_surrounding_text() (modules/input/imwayland.c:253) before_length doesn't get checked. If we don't have surrounding text (as in this case) cursor_pointer is NULL and thus (cursor_pointer - before_length) results in an invalid pointer. The other question is why we don't have surrounding text, but that's a different problem. In any case we shouldn't crash in text_input_delete_surrounding_text(). I believe this is a different bug from #2036647 because of the different callstack and that we shouldn't call g_utf8_pointer_to_offset with invalid pointers. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-terminal 3.49.92-2ubuntu1 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 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Fri Jan 26 17:43:54 2024 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2024-01-23 (3 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) JournalErrors: Jan 26 17:43:53 hostname gnome-terminal-[4907]: g_atomic_ref_count_dec: assertion 'old_value > 0' failed Jan 26 17:43:53 hostname gnome-terminal-[4907]: g_atomic_ref_count_dec: assertion 'old_value > 0' failed Jan 26 17:44:00 hostname systemd[1623]: gnome-terminal-server.service: Main process exited, code=dumped, status=11/SEGV Jan 26 17:44:00 hostname systemd[1623]: gnome-terminal-server.service: Failed with result 'core-dump'. ProcCmdline: /usr/libexec/gnome-terminal-server ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f884099c180 : movzbl (%rsi),%ecx PC (0x7f884099c180) ok source "(%rsi)" (0x) not located in a known VMA region (needed readable region)! destination "%ecx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-terminal StacktraceTop: g_utf8_pointer_to_offset () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-wayland.so ?? () from /lib/x86_64-linux-gnu/libffi.so.8 ?? () from /lib/x86_64-linux-gnu/libffi.so.8 ffi_call () from /lib/x86_64-linux-gnu/libffi.so.8 Title: gnome-terminal-server crashed with SIGSEGV in g_utf8_pointer_to_offset() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users vboxsf modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2024-01-26T17:42:28.299334 separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2051381/+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 2051572] Re: Always preseed core and snapd snap in server seed
** Merge proposal linked: https://code.launchpad.net/~philroche/ubuntu-seeds/+git/ubuntu/+merge/459599 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2051572 Title: Always preseed core and snapd snap in server seed Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Noble: New Bug description: In removing the LXD snap from preseeding in the server seed for Ubuntu 24.04 as part LP #2051346 [1] we also removed the snaps snap and the core22 snap. This means that are subsequent snap install, like LXD, will take much longer than expected for a non minimized image. Time taken to install LXD snap using the lxd-installer package without snapd and core22 preinstalled/seeded ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m29.107s user 0m0.006s sys 0m0.005s ``` Time taken to install LXD snap using the lxd-installer package with snapd and core22 already installed. ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m15.034s user 0m0.005s sys 0m0.005s ``` This is a significant difference and for a workload we intend to remain as a core tested and tracked workload. As such I propose we re- introduce core22 and snaps snaps to our seed. LXD do intend to move to the core24 snap as their base as I'm sure snapd does too so when that does happen we need to update the preseeded core snap. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n69 [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051572/+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 2051573] [NEW] [HDA-Intel - HD-Audio Generic, playback] No sound at all
Public bug reported: Internal speakers - no sound Headphones (jack) no sound HDMI sound works while connected to external monitor, there are some minor quality issues Ubuntu 22.04 kernel 6.5.0-15-generic on Huawei Matebook 14D 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 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 29 17:39:17 2024 InstallationDate: Installed on 2023-07-13 (200 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:Generic failed Symptom_Card: acp - acp Symptom_Type: No sound at all Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/11/2023 dmi.bios.release: 1.8 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.08 dmi.board.asset.tag: N/A dmi.board.name: KLVL-WXXW-PCB dmi.board.vendor: HUAWEI dmi.board.version: M1010 dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1010 dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnHUAWEI:bvr1.08:bd01/11/2023:br1.8:efr1.8:svnHUAWEI:pnKLVL-WXXW:pvrM1010:rvnHUAWEI:rnKLVL-WXXW-PCB:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC100: dmi.product.family: MateBook 14 dmi.product.name: KLVL-WXXW dmi.product.sku: C100 dmi.product.version: M1010 dmi.sys.vendor: HUAWEI ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/2051573 Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Internal speakers - no sound Headphones (jack) no sound HDMI sound works while connected to external monitor, there are some minor quality issues Ubuntu 22.04 kernel 6.5.0-15-generic on Huawei Matebook 14D 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 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 29 17:39:17 2024 InstallationDate: Installed on 2023-07-13 (200 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:Generic failed Symptom_Card: acp - acp Symptom_Type: No sound at all Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/11/2023 dmi.bios.release: 1.8 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.08 dmi.board.asset.tag: N/A dmi.board.name: KLVL-WXXW-PCB dmi.board.vendor: HUAWEI dmi.board.version: M1010 dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1010 dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnHUAWEI:bvr1.08:bd01/11/2023:br1.8:efr1.8:svnHUAWEI:pnKLVL-WXXW:pvrM1010:rvnHUAWEI:rnKLVL-WXXW-PCB:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC100: dmi.product.family: MateBook 14 dmi.product.name: KLVL-WXXW dmi.product.sku: C100 dmi.product.version: M1010 dmi.sys.vendor: HUAWEI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2051573/+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 2051570] [NEW] [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound
Public bug reported: 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 29-01-2024 After the latest Linux kernel update to "6.5.0-15-generic." Following the update, I observed a significant reduction in crackling sound (approximately 80%) after disabling C-states from the BIOS. However, this improvement came at the cost of higher CPU temperatures, with the fan constantly running. Conversely, with C-states enabled, the crackling sound occurs only when the fan starts working. Additionally, I am still encountering the "Dummy Output" audio issue consistently on a fresh start, necessitating a reboot to resolve. I want to emphasize that I receive updates from the Tunisia Ubuntu server. 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 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.27.1:bd10/03/2023:br1.27:svnDellInc.:pnVostro3400:pvr:rvnDellInc.:rn0GGCMJ:rvrA02:cvnDellInc.:ct10:cvr:sku0A23: dmi.product.family: Vostro dmi.product.name: Vostro 3400 dmi.product.sku: 0A23 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2024-01-28T08:52:28.427855 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/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
[Desktop-packages] [Bug 2051572] [NEW] Always preseed core and snapd snap in server seed
Public bug reported: In removing the LXD snap from preseeding in the server seed for Ubuntu 24.04 as part LP #2051346 [1] we also removed the snaps snap and the core22 snap. This means that are subsequent snap install, like LXD, will take much longer than expected for a non minimized image. Time taken to install LXD snap using the lxd-installer package without snapd and core22 preinstalled/seeded ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real0m29.107s user0m0.006s sys 0m0.005s ``` Time taken to install LXD snap using the lxd-installer package with snapd and core22 already installed. ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real0m15.034s user0m0.005s sys 0m0.005s ``` This is a significant difference and for a workload we intend to remain as a core tested and tracked workload. As such I propose we re-introduce core22 and snaps snaps to our seed. LXD do intend to move to the core24 snap as their base as I'm sure snapd does too so when that does happen we need to update the preseeded core snap. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n69 [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346 ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Assignee: Philip Roche (philroche) Status: New ** Affects: ubuntu-meta (Ubuntu Noble) Importance: Undecided Assignee: Philip Roche (philroche) Status: New ** Changed in: ubuntu-meta (Ubuntu) Assignee: (unassigned) => Philip Roche (philroche) ** Also affects: ubuntu-meta (Ubuntu Noble) Importance: Undecided Assignee: Philip Roche (philroche) Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2051572 Title: Always preseed core and snapd snap in server seed Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Noble: New Bug description: In removing the LXD snap from preseeding in the server seed for Ubuntu 24.04 as part LP #2051346 [1] we also removed the snaps snap and the core22 snap. This means that are subsequent snap install, like LXD, will take much longer than expected for a non minimized image. Time taken to install LXD snap using the lxd-installer package without snapd and core22 preinstalled/seeded ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m29.107s user 0m0.006s sys 0m0.005s ``` Time taken to install LXD snap using the lxd-installer package with snapd and core22 already installed. ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m15.034s user 0m0.005s sys 0m0.005s ``` This is a significant difference and for a workload we intend to remain as a core tested and tracked workload. As such I propose we re- introduce core22 and snaps snaps to our seed. LXD do intend to move to the core24 snap as their base as I'm sure snapd does too so when that does happen we need to update the preseeded core snap. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n69 [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051572/+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 2051383] Re: gnome-shell high CPU utilization when moving mouse cursor
1. Nope, the log is normal, nothing new is logged when moving the cursor around 2. Razer DeathAdder V2. BTW switching to 60 Hz doesn't seem to change anything. However, switching to an old cheap mouse decreases gnome- shell's CPU usage down to ~10%. 3. Unfortunately that didn't help. I also had this line in my /etc/environment before: MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 Tried both with and without it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2051383 Title: gnome-shell high CPU utilization when moving mouse cursor Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I simply move my mouse cursor on an empty desktop, gnome-shell's CPU usage goes up from 20% (when idle) to 60%, which causes stuttering. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 26 23:31:26 2024 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2018-03-17 (2140 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-02 (603 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051383/+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
** Summary changed: - Backport packages from mantic to server-backports PPA for focal and jammy + Backport packages from noble(-devel) to server-backports PPA for focal and jammy, post-FF ** Changed in: dpdk (Ubuntu) Milestone: ubuntu-23.11 => ubuntu-24.02 ** Changed in: dpdk (Ubuntu) Milestone: ubuntu-24.02 => ubuntu-24.03 ** Changed in: libslirp (Ubuntu) Milestone: ubuntu-23.11 => ubuntu-24.03 ** Changed in: libvirt (Ubuntu) Milestone: ubuntu-23.11 => ubuntu-24.03 ** Changed in: libvirt-python (Ubuntu) Milestone: ubuntu-23.11 => ubuntu-24.03 ** Changed in: meson (Ubuntu) Milestone: ubuntu-23.11 => ubuntu-24.03 ** Changed in: openvswitch (Ubuntu) Milestone: ubuntu-23.11 => ubuntu-24.03 ** Changed in: qemu (Ubuntu) Milestone: ubuntu-23.11 => ubuntu-24.03 ** Changed in: rdma-core (Ubuntu) Milestone: ubuntu-23.11 => ubuntu-24.03 ** Changed in: seabios (Ubuntu) Milestone: ubuntu-23.11 => ubuntu-24.03 ** Changed in: spice (Ubuntu) Milestone: ubuntu-23.11 => ubuntu-24.03 ** Changed in: spice-protocol (Ubuntu) Milestone: ubuntu-23.11 => ubuntu-24.03 ** Changed in: spice-vdagent (Ubuntu) Milestone: ubuntu-23.11 => ubuntu-24.03 ** Changed in: virglrenderer (Ubuntu) Milestone: ubuntu-23.11 => ubuntu-24.03 ** Changed in: virt-manager (Ubuntu) Milestone: ubuntu-23.11 => ubuntu-24.03 ** Changed in: edk2 (Ubuntu) Milestone: ubuntu-23.11 => ubuntu-24.03 -- 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: New Status in edk2 source package in Jammy: New Status in libslirp source package in Jammy: New Status in libvirt source package in Jammy: New Status in libvirt-python source package in Jammy: New Status in meson source package in Jammy: New Status in openvswitch source package in Jammy: New Status in qemu source package in Jammy: New Status in rdma-core source package in Jammy: New Status in seabios source package in Jammy: New Status in spice source package in Jammy: New Status in spice-protocol source package in Jammy: New Status in spice-vdagent source package in Jammy: New 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 2024377] Re: Adsys can't fetch GPOs
Do we have any updates on this backing backported ?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.launchpad.net/bugs/2024377
Title:
Adsys can't fetch GPOs
Status in adsys package in Ubuntu:
Fix Released
Bug description:
Bad, maybe no understandable english ahead.
Can't find anything related to this on Github, Canonical Forums,
Reddit or StackOverflow.
On Ubuntu 22.04, I've followed the Wiki tutorial and verified all
steps on Integration Ubuntu Desktop whitepaper. Currently using SSSD
backend, I can log with Active Directory users however when adsys is
installed I can't fetch GPOs. In this version the error is:
ERROR Error from server: error while updating policy: can't get
policies for "ubuntu": can't download all gpos and assets: one or more
error while fetching GPOs and assets: can't download "ubuntuRoot":
can't check if ubuntuRoot needs refreshing: no GPT.INI file: cannot
open
smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}/GPT.INI:
invalid argument
It happens when using "adsysctl update -m" or "adsysctl update
usern...@domain.com.br /tmp/krb5c_getentId_randomdnumber" and just
"adsysctl update" too.
I've upgrade the machine to 22.10 and the error changed to:
ERROR Error from server: error while updating policy: can't get policies for
"ubuntu": failed to retrieve the list of GPO (exited with 1): exit status 1
Failed to bind - LDAP client internal error: NT_STATUS_INVALID_PARAMETER
Failed to connect to 'ldap://addc01.domain.com.br' with backend 'ldap': LDAP
client internal error: NT_STATUS_INVALID_PARAMETER
Failed to open session: (1, 'LDAP client internal error:
NT_STATUS_INVALID_PARAMETER').
After upgrade to 23.04 the error persist same as the above.
Full info 22.04 (- verbose):
INFO No configuration file: Config File "adsys" Not Found in "[/home/jzprates
/root /etc /usr/sbin]".
We will only use the defaults, env variables or flags.
DEBUG Connecting as [[2504:109556]]
DEBUG New request /service/UpdatePolicy
DEBUG Requesting with parameters: IsComputer: true, All: false, Target:
ubuntu, Krb5Cc:
DEBUG NormalizeTargetName for "ubuntu", type "computer"
DEBUG Check if grpc request peer is authorized
DEBUG Authorized as being administrator
DEBUG GetPolicies for "ubuntu", type "computer"
DEBUG Getting gpo list with arguments: "--objectclass computer
ldap://addc01.domain.com.br ubuntu"
DEBUG GPO "ubuntuRoot" for "ubuntu" available at
"smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}"
DEBUG Analyzing "assets"
DEBUG Analyzing "ubuntuRoot"
INFO No assets directory with GPT.INI file found on AD, skipping assets
download
ERROR Error from server: error while updating policy: can't get policies for
"ubuntu": can't download all gpos and assets: one or more error while fetching
GPOs and assets: can't download "ubuntuRoot": can't check if ubuntuRoot needs
refreshing: no GPT.INI file: cannot open
smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}/GPT.INI:
invalid argument
Full info 23.04 (- verbose):
INFO No configuration file: Config File "adsys" Not Found in "[/home/jzprates
/root /etc /usr/sbin]".
DEBUG Connecting as [[58811:006019]]
DEBUG New request /service/UpdatePolicy
DEBUG Requesting with parameters: IsComputer: true, All: false, Target:
ubuntu, Krb5Cc:
DEBUG NormalizeTargetName for "ubuntu", type "computer"
DEBUG Check if grpc request peer is authorized
DEBUG Authorized as being administrator
DEBUG GetPolicies for "ubuntu", type "computer"
DEBUG Getting gpo list with arguments: "--objectclass computer
ldap://addc01.domain.com.br ubuntu"
ERROR Error from server: error while updating policy: can't get policies for
"ubuntu": failed to retrieve the list of GPO (exited with 1): exit status 1
Failed to bind - LDAP client internal error: NT_STATUS_INVALID_PARAMETER
Failed to connect to 'ldap://addc01.domain.com.br' with backend 'ldap': LDAP
client internal error: NT_STATUS_INVALID_PARAMETER
Failed to open session: (1, 'LDAP client internal error:
NT_STATUS_INVALID_PARAMETER')
Additional info:
Domain Controller and machine are on the same subnet without firewall on any
level;
Domain Controller is a Windows Server 2019 updated to the last security
version;
Both machine and user are on the same OU with "no heritage" enabled and just
one policy added to permit usern...@domain.com.br to become root;
The info header directory is "/home/jzprates" on both logs because I've
collected them using the local account using "sudo adsysctl update -m -";
If I disable Adsys login on pam-auth-update, Ubuntu creates a homedir and
enter correctly with domain users.
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: adsys 0.11.0
[Desktop-packages] [Bug 2051346] Re: No longer preseed LXD snap to allow for LXD 5.20 release
This has been released in Noble version 1.529 ** Changed in: ubuntu-meta (Ubuntu) Status: New => Fix Released ** Also affects: ubuntu-meta (Ubuntu Noble) Importance: Undecided Status: Fix Released ** Changed in: ubuntu-meta (Ubuntu Noble) Assignee: (unassigned) => Philip Roche (philroche) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2051346 Title: No longer preseed LXD snap to allow for LXD 5.20 release Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Noble: Fix Released Bug description: With LXD 5.20 there is a license change to AGPL and it has been decided to no longer seed the snap in Ubuntu 24.04 and later and instead seed the lxd-installer package instead. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n60 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346/+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 2051548] [NEW] Problem in Booting and nomodeset
Public bug reported: Display resolution stuck at 800x600 after using nomodeset in grub. But my Dell monitor has 1600x900 resolution. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 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 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 29 19:27:23 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:2111] InstallationDate: Installed on 2024-01-26 (2 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic root=UUID=ba3dc7d3-3688-4f19-947e-a1d3aedb15f3 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2020 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61 dmi.board.vendor: INTEL Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/11/2020:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnH61:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. 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.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy 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/2051548 Title: Problem in Booting and nomodeset Status in xorg package in Ubuntu: New Bug description: Display resolution stuck at 800x600 after using nomodeset in grub. But my Dell monitor has 1600x900 resolution. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 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 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 29 19:27:23 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:2111] InstallationDate: Installed on 2024-01-26 (2 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic root=UUID=ba3dc7d3-3688-4f19-947e-a1d3aedb15f3 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2020 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61 dmi.board.vendor: INTEL Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version:
[Desktop-packages] [Bug 2049117] Re: [HP ProBook 440 G8 Notebook PC, Realtek ALC236, Speaker, Internal] No sound at all From google Chrome youtube after putting computer to sleep
** Description changed: [HP ProBook 440 G8 Notebook PC, Realtek ALC236, Speaker, Internal] No sound at all From google Chrome youtube after putting computer to sleep From testing sound came but not from google chrome ---=== Update ===--- False alarm. Sound i was able to put back on, turn out i dont remember i turned off sound on Chrome in task menu of Kubuntu. Icon shows sound playing and when clicking sound speaker icon in taskbar of chrome then it shows very thin line that sound is turned mute off. === Suggestion === Since i dont remember i turned it off or dont see big difference or red icon that sound is off then i dont know its off. NEED different icon (size, more contrast, red color, round red X sign) so i can see warning that sound is off. image attached how hard it is to see any difference from speaker icon when turned off + === Suggestion 2 === + I just accidentally again clicked on it because it appears on all open windows. Can it not be only one one window of chrome where it playing? + ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kng2239 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Jan 12 01:20:49 2024 InstallationDate: Installed on 2024-01-05 (6 days ago) InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kng2239 F pulseaudio /dev/snd/pcmC0D0p: kng2239 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [HP ProBook 440 G8 Notebook PC, Realtek ALC236, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/06/2023 dmi.bios.release: 15.0 dmi.bios.vendor: HP dmi.bios.version: T70 Ver. 01.15.00 dmi.board.name: 87E0 dmi.board.vendor: HP dmi.board.version: KBC Version 33.24.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 51.36 dmi.modalias: dmi:bvnHP:bvrT70Ver.01.15.00:bd10/06/2023:br15.0:efr51.36:svnHP:pnHPProBook440G8NotebookPC:pvrSBKPF:rvnHP:rn87E0:rvrKBCVersion33.24.00:cvnHP:ct10:cvr:sku27J72EA#B1R: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 440 G8 Notebook PC dmi.product.sku: 27J72EA#B1R dmi.product.version: SBKPF dmi.sys.vendor: HP -- 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/2049117 Title: [HP ProBook 440 G8 Notebook PC, Realtek ALC236, Speaker, Internal] No sound at all From google Chrome youtube after putting computer to sleep Status in alsa-driver package in Ubuntu: Invalid Status in plasma-workspace package in Ubuntu: New Bug description: [HP ProBook 440 G8 Notebook PC, Realtek ALC236, Speaker, Internal] No sound at all From google Chrome youtube after putting computer to sleep From testing sound came but not from google chrome ---=== Update ===--- False alarm. Sound i was able to put back on, turn out i dont remember i turned off sound on Chrome in task menu of Kubuntu. Icon shows sound playing and when clicking sound speaker icon in taskbar of chrome then it shows very thin line that sound is turned mute off. === Suggestion === Since i dont remember i turned it off or dont see big difference or red icon that sound is off then i dont know its off. NEED different icon (size, more contrast, red color, round red X sign) so i can see warning that sound is off. image attached how hard it is to see any difference from speaker icon when turned off === Suggestion 2 === I just accidentally again clicked on it because it appears on all open windows. Can it not be only one one window of chrome where it playing? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kng2239 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Jan 12 01:20:49 2024 InstallationDate: Installed on 2024-01-05 (6 days ago) InstallationMedia: Kubuntu 22.04.3 LTS "Jammy
[Desktop-packages] [Bug 2051536] Re: security update regression tracking bug
** Also affects: xwayland (Ubuntu) Importance: Undecided Status: New ** Changed in: xwayland (Ubuntu Focal) Status: New => Invalid ** Changed in: xwayland (Ubuntu Mantic) Status: New => Fix Released ** Changed in: xwayland (Ubuntu Noble) Status: New => Fix Released ** Changed in: xwayland (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2051536 Title: security update regression tracking bug Status in xorg-server package in Ubuntu: Fix Released Status in xwayland package in Ubuntu: Fix Released Status in xorg-server source package in Focal: In Progress Status in xwayland source package in Focal: Invalid Status in xorg-server source package in Jammy: In Progress Status in xwayland source package in Jammy: In Progress Status in xorg-server source package in Mantic: In Progress Status in xwayland source package in Mantic: Fix Released Status in xorg-server source package in Noble: Fix Released Status in xwayland source package in Noble: Fix Released Bug description: USN-6587-1 fixed security issues in X.Org. A commit was missing which may result in a regression (memory leak). See: https://bugs.debian.org/1061110 https://gitlab.freedesktop.org/xorg/xserver/-/issues/1623 https://gitlab.freedesktop.org/xorg/xserver/-/commit/8b75ec34dfbe435cd3a17e64138e22a37395a6d8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2051536/+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 192176] Re: Scanner output always JPEG compressed
FTR, the "Fix Released" status visible here on the Debian bug is misleading, it was closed because change was rejected by upstream. Also, if changing the default is undesirable, can upstream please reinstate the knob so that those who would like to take advantage of the full potential of their hardware can do by changing a frontend cofiguration setting? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/192176 Title: Scanner output always JPEG compressed Status in HPLIP: Invalid Status in Simple Scan: Fix Released Status in hplip package in Ubuntu: Invalid Status in simple-scan package in Ubuntu: Fix Released Status in hplip package in Debian: Fix Released Bug description: Binary package hint: hplip The hpaio backend compresses the scanned image with JPEG before it is received by xsane. This makes it impossible to scan anything losslessly. Editing ~/.sane/xsane/($scanner).drc to say "compression" "none" Fixes this temporarily. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/192176/+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 2051536] [NEW] security update regression tracking bug
*** This bug is a security vulnerability *** Public security bug reported: USN-6587-1 fixed security issues in X.Org. A commit was missing which may result in a regression (memory leak). See: https://bugs.debian.org/1061110 https://gitlab.freedesktop.org/xorg/xserver/-/issues/1623 https://gitlab.freedesktop.org/xorg/xserver/-/commit/8b75ec34dfbe435cd3a17e64138e22a37395a6d8 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: xorg-server (Ubuntu Focal) Importance: Undecided Assignee: Marc Deslauriers (mdeslaur) Status: In Progress ** Affects: xorg-server (Ubuntu Jammy) Importance: Undecided Assignee: Marc Deslauriers (mdeslaur) Status: In Progress ** Affects: xorg-server (Ubuntu Mantic) Importance: Undecided Assignee: Marc Deslauriers (mdeslaur) Status: In Progress ** Affects: xorg-server (Ubuntu Noble) Importance: Undecided Status: Fix Released ** Also affects: xorg-server (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu Noble) Status: New => Fix Released ** Changed in: xorg-server (Ubuntu Focal) Status: New => In Progress ** Changed in: xorg-server (Ubuntu Jammy) Status: New => In Progress ** Changed in: xorg-server (Ubuntu Mantic) Status: New => In Progress ** Changed in: xorg-server (Ubuntu Focal) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) ** Changed in: xorg-server (Ubuntu Jammy) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) ** Changed in: xorg-server (Ubuntu Mantic) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2051536 Title: security update regression tracking bug Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Focal: In Progress Status in xorg-server source package in Jammy: In Progress Status in xorg-server source package in Mantic: In Progress Status in xorg-server source package in Noble: Fix Released Bug description: USN-6587-1 fixed security issues in X.Org. A commit was missing which may result in a regression (memory leak). See: https://bugs.debian.org/1061110 https://gitlab.freedesktop.org/xorg/xserver/-/issues/1623 https://gitlab.freedesktop.org/xorg/xserver/-/commit/8b75ec34dfbe435cd3a17e64138e22a37395a6d8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2051536/+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 2049628] Re: Persistent Audio Issues on Dell Vostro 3400 Running Ubuntu 22.04.3 LTS
UPDATE 29-01-2024 After the latest Linux kernel update to "6.5.0-15-generic." Following the update, I observed a significant reduction in crackling sound (approximately 80%) after disabling C-states from the BIOS. However, this improvement came at the cost of higher CPU temperatures, with the fan constantly running. Conversely, with C-states enabled, the crackling sound occurs only when the fan starts working. Additionally, I am still encountering the "Dummy Output" audio issue consistently on a fresh start, necessitating a reboot to resolve. -- 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/2049628 Title: Persistent Audio Issues on Dell Vostro 3400 Running Ubuntu 22.04.3 LTS Status in pulseaudio 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 I want to emphasize that I receive updates from the Tunisia Ubuntu server. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: galxy-a10 1404 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 14:56:16 2024 InstallationDate: Installed on 2024-01-16 (1 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio 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 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.27.1:bd10/03/2023:br1.27:svnDellInc.:pnVostro3400:pvr:rvnDellInc.:rn0GGCMJ:rvrA02:cvnDellInc.:ct10:cvr:sku0A23: dmi.product.family: Vostro dmi.product.name: Vostro 3400 dmi.product.sku: 0A23 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2049628/+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 1588197] Re: Can't type anything in search box
I have attached a copy of the output I get with this issue. The first error ```console (evince:25290): IBUS-WARNING **: 10:54:21.331: Unable to connect to ibus: Could not connect: Permission denied ``` happens immediately when I run evince. The second error: ```console (evince:25403): GLib-WARNING **: 10:56:05.731: getpwuid_r(): failed due to unknown user id (1855985172) ``` occurs when I try to add a note to the PDF document. Evince does not accept keyboard input. I can fix the problem by doing: ```console rm -r ~/.config/ibus ``` which is a fix I saw on a duplicate version of this bug on here ** Attachment added: "EvinceError.png" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1588197/+attachment/5743054/+files/EvinceError.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1588197 Title: Can't type anything in search box Status in evince package in Ubuntu: Invalid Bug description: Since Ubuntu 16.04, I can't search strings in PDF using Evince viewer. Clicking search button or CTRL+F shows search box, but I can't type anything inside. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1588197/+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 2049061] Re: adsysctl update with a domain user fails if KRB5CCNAME is not set
** Changed in: adsys (Ubuntu)
Importance: Undecided => Critical
** Changed in: adsys (Ubuntu)
Status: Confirmed => Triaged
** Changed in: adsys (Ubuntu)
Assignee: (unassigned) => Gabriel Nagy (gabuscus)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.launchpad.net/bugs/2049061
Title:
adsysctl update with a domain user fails if KRB5CCNAME is not set
Status in adsys package in Ubuntu:
Triaged
Bug description:
In an environment where /etc/krb5.conf sets "default_ccache_name =
FILE:/tmp/krb5cc_%{uid}" and you don't have the KRB5CCNAME variable
set, running "adsysctl update" with a AD domain user will fail.
If you either export the variable with the path to the kerberos ticket
OR run the command "adsysctl update
" it works.
The adsysctl command should fallback to the default location when
KRB5CCNAME is not defined or have a mechanism to query klist and find
the Kerberos tickets location.
Given that adsys can't find Kerberos tickets when `klist` does. It
seems like a feature parity issue, granted, an edge case.
Here is an example of a reproducer:
https://pastebin.ubuntu.com/p/FjyTWQChjM/
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: adsys 0.9.2~22.04.2
ProcVersionSignature: Ubuntu 6.2.0-1014.14~22.04.1-aws 6.2.16
Uname: Linux 6.2.0-1014-aws x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudID: aws
CloudName: aws
CloudPlatform: ec2
CloudRegion: us-west-2
CloudSubPlatform: metadata (http://169.254.169.254)
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 11 11:39:06 2024
Ec2AMI: ami-00094f7041bb1b79d
Ec2AMIManifest: (unknown)
Ec2Architecture: x86_64
Ec2AvailabilityZone: us-west-2b
Ec2Imageid: ami-00094f7041bb1b79d
Ec2InstanceType: t3.large
Ec2Instancetype: t3.large
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
Ec2Region: us-west-2
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.utf8
SHELL=/bin/bash
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
sssd 2.6.3-1ubuntu3.2
python3-samba 2:4.15.13+dfsg-0ubuntu1.5
SourcePackage: adsys
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.polkit-1.localauthority.conf.d.99-adsys-privilege-enforcement.conf:
[deleted]
modified.conffile..etc.sudoers.d.99-adsys-privilege-enforcement: [deleted]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2049061/+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 2051504] [NEW] 0.4.17-1ubuntu1 removes all output and input sinks in gnome settings
Public bug reported: After the changes committed as part of https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1995707 (wireplumber 0.4.17-1ubuntu1), all input and output sinks are removed from gnome settings on reboot. Playing audio through celluloid (mpv) still works with the default sink, while Firefox Nightly refuses to play anything. I've tested this on two machines now; - One running on nvidia+X11, without snapd installed. - Another running on intel+wayland, also without snapd. Reverting to 0.4.17-1 works fine, and gnome settings lists all output and input sinks again. ** Affects: wireplumber (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wireplumber in Ubuntu. https://bugs.launchpad.net/bugs/2051504 Title: 0.4.17-1ubuntu1 removes all output and input sinks in gnome settings Status in wireplumber package in Ubuntu: New Bug description: After the changes committed as part of https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1995707 (wireplumber 0.4.17-1ubuntu1), all input and output sinks are removed from gnome settings on reboot. Playing audio through celluloid (mpv) still works with the default sink, while Firefox Nightly refuses to play anything. I've tested this on two machines now; - One running on nvidia+X11, without snapd installed. - Another running on intel+wayland, also without snapd. Reverting to 0.4.17-1 works fine, and gnome settings lists all output and input sinks again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireplumber/+bug/2051504/+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 2051478] Re: unlock passphrase doesn't work in plymouth but works in recovery mode
By downgrading plymouth from 23.360.11-0ubuntu2 to 22.02.122-4ubuntu2 by hand, the passphrase worked so it's a plymouth issue rather than cryptsetup, it seems. https://launchpad.net/ubuntu/+source/plymouth/22.02.122-4ubuntu2/+build/27587072/+files/libplymouth5_22.02.122-4ubuntu2_amd64.deb https://launchpad.net/ubuntu/+source/plymouth/22.02.122-4ubuntu2/+build/27587072/+files/plymouth_22.02.122-4ubuntu2_amd64.deb https://launchpad.net/ubuntu/+source/plymouth/22.02.122-4ubuntu2/+build/27587072/+files/plymouth-label_22.02.122-4ubuntu2_amd64.deb https://launchpad.net/ubuntu/+source/plymouth/22.02.122-4ubuntu2/+build/27587072/+files/plymouth-theme-spinner_22.02.122-4ubuntu2_amd64.deb https://launchpad.net/ubuntu/+source/plymouth/22.02.122-4ubuntu2/+build/27587072/+files/plymouth-theme-ubuntu-text_22.02.122-4ubuntu2_amd64.deb ** Also affects: plymouth (Ubuntu) Importance: Undecided Status: New ** Changed in: cryptsetup (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/2051478 Title: unlock passphrase doesn't work in plymouth but works in recovery mode Status in cryptsetup package in Ubuntu: Invalid Status in plymouth package in Ubuntu: New Bug description: The system suddenly stopped accepting the existing passphrase on boot. However, the passphrase is definitely correct since the same one can be used in the recovery mode and it unlocks the volume appropriately. I'm not sure which recent update brought this behavior. Last successful graphical boot: 2024-01-28 00:43:09 +0900 Fwiw, the existing passphrase was long enough and contains some special characters such as "!". The confusing part is shorter passphrase but with "!" seems to work. WORKAROUND: 1. boot into the recovery mode 2. unlock the volume in the console 3. add a new key with `cryptsetup luksAddKey /dev/nvme0n1p3` or remove "splash" from /etc/default/grub and run `update-grub` 3. reboot ProblemType: BugDistroRelease: Ubuntu 24.04 Package: cryptsetup 2:2.6.1-6ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 29 15:41:03 2024 InstallationDate: Installed on 2024-01-08 (21 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240104) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=SourcePackage: cryptsetup UpgradeStatus: No upgrade log present (probably fresh install) cmdline: BOOT_IMAGE=/vmlinuz-6.6.0-14-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crypttab: dm_crypt-0 UUID=cfd8c295-9988-4934-a91a-460a9d16d80f none luks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2051478/+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 2051383] Re: gnome-shell high CPU utilization when moving mouse cursor
Yes it's normal for the application's CPU usage to go up when it's receiving input events. So that suggests this is just a high frequency problem. * Is your log flooding at all? (journalctl -f) * I can already see you monitor is 144Hz. What model of mouse are you using? * Try adding MUTTER_DEBUG_FORCE_KMS_MODE=simple to /etc/environment and reboot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2051383 Title: gnome-shell high CPU utilization when moving mouse cursor Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I simply move my mouse cursor on an empty desktop, gnome-shell's CPU usage goes up from 20% (when idle) to 60%, which causes stuttering. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 26 23:31:26 2024 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2018-03-17 (2140 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-02 (603 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051383/+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 2051383] Re: gnome-shell high CPU utilization when moving mouse cursor
** Attachment added: "8-wayland-thunderbird.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051383/+attachment/5743011/+files/8-wayland-thunderbird.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2051383 Title: gnome-shell high CPU utilization when moving mouse cursor Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I simply move my mouse cursor on an empty desktop, gnome-shell's CPU usage goes up from 20% (when idle) to 60%, which causes stuttering. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 26 23:31:26 2024 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2018-03-17 (2140 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-02 (603 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051383/+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 2051383] Re: gnome-shell high CPU utilization when moving mouse cursor
** Attachment added: "7-wayland-firefox.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051383/+attachment/5743010/+files/7-wayland-firefox.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2051383 Title: gnome-shell high CPU utilization when moving mouse cursor Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I simply move my mouse cursor on an empty desktop, gnome-shell's CPU usage goes up from 20% (when idle) to 60%, which causes stuttering. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 26 23:31:26 2024 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2018-03-17 (2140 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-02 (603 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051383/+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 2051383] Re: gnome-shell high CPU utilization when moving mouse cursor
** Attachment added: "5-wayland-no-windows.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051383/+attachment/5743008/+files/5-wayland-no-windows.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2051383 Title: gnome-shell high CPU utilization when moving mouse cursor Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I simply move my mouse cursor on an empty desktop, gnome-shell's CPU usage goes up from 20% (when idle) to 60%, which causes stuttering. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 26 23:31:26 2024 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2018-03-17 (2140 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-02 (603 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051383/+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 2051383] Re: gnome-shell high CPU utilization when moving mouse cursor
** Attachment added: "6-wayland-gnome-terminal.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051383/+attachment/5743009/+files/6-wayland-gnome-terminal.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2051383 Title: gnome-shell high CPU utilization when moving mouse cursor Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I simply move my mouse cursor on an empty desktop, gnome-shell's CPU usage goes up from 20% (when idle) to 60%, which causes stuttering. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 26 23:31:26 2024 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2018-03-17 (2140 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-02 (603 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051383/+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 2051383] Re: gnome-shell high CPU utilization when moving mouse cursor
** Attachment added: "4-xorg-thunderbird.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051383/+attachment/5743007/+files/4-xorg-thunderbird.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2051383 Title: gnome-shell high CPU utilization when moving mouse cursor Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I simply move my mouse cursor on an empty desktop, gnome-shell's CPU usage goes up from 20% (when idle) to 60%, which causes stuttering. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 26 23:31:26 2024 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2018-03-17 (2140 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-02 (603 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051383/+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 2051383] Re: gnome-shell high CPU utilization when moving mouse cursor
** Attachment added: "3-xorg-firefox.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051383/+attachment/5743006/+files/3-xorg-firefox.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2051383 Title: gnome-shell high CPU utilization when moving mouse cursor Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I simply move my mouse cursor on an empty desktop, gnome-shell's CPU usage goes up from 20% (when idle) to 60%, which causes stuttering. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 26 23:31:26 2024 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2018-03-17 (2140 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-02 (603 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051383/+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 2051383] Re: gnome-shell high CPU utilization when moving mouse cursor
** Attachment added: "1-xorg-no-windows.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051383/+attachment/5743004/+files/1-xorg-no-windows.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2051383 Title: gnome-shell high CPU utilization when moving mouse cursor Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I simply move my mouse cursor on an empty desktop, gnome-shell's CPU usage goes up from 20% (when idle) to 60%, which causes stuttering. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 26 23:31:26 2024 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2018-03-17 (2140 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-02 (603 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051383/+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 2051383] Re: gnome-shell high CPU utilization when moving mouse cursor
** Attachment added: "2-xorg-gnome-terminal.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051383/+attachment/5743005/+files/2-xorg-gnome-terminal.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2051383 Title: gnome-shell high CPU utilization when moving mouse cursor Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I simply move my mouse cursor on an empty desktop, gnome-shell's CPU usage goes up from 20% (when idle) to 60%, which causes stuttering. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 26 23:31:26 2024 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2018-03-17 (2140 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-02 (603 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051383/+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 2051383] Re: gnome-shell high CPU utilization when moving mouse cursor
** Attachment added: "top.mp4" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051383/+attachment/5743003/+files/top.mp4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2051383 Title: gnome-shell high CPU utilization when moving mouse cursor Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I simply move my mouse cursor on an empty desktop, gnome-shell's CPU usage goes up from 20% (when idle) to 60%, which causes stuttering. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 26 23:31:26 2024 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2018-03-17 (2140 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-02 (603 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051383/+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 2051383] Re: gnome-shell high CPU utilization when moving mouse cursor
I'm sorry, the 20% part was a bit of an overstatement, after observing more I can say it's somewhere between 1% to 5%. I have the following extensions active: - Desktop Icons NG - Ubuntu AppIndicators - Ubuntu Dock Disabling all extensions didn't change anything in my case. Also I've noticed an interesting thing: when moving the cursor, CPU usage goes up for gnome-shell AND for whatever process on top of whose window I"m moving it. For example, if a Text Editor window is active, it goes up for the gedit process. If it helps, below are a few screenshots of "top" taken when I moved my mouse, with Xorg and Wayland for comparison, and a video. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2051383 Title: gnome-shell high CPU utilization when moving mouse cursor Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I simply move my mouse cursor on an empty desktop, gnome-shell's CPU usage goes up from 20% (when idle) to 60%, which causes stuttering. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 26 23:31:26 2024 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2018-03-17 (2140 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-02 (603 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051383/+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
