[Desktop-packages] [Bug 1993912] Re: GNOME screen recorder drops vast majority of frames
*** This bug is a duplicate of bug 1987631 *** https://bugs.launchpad.net/bugs/1987631 That's the fix for bug 1987631 so we can merge with that. ** This bug has been marked a duplicate of bug 1987631 Screencast only records one second -- 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/1993912 Title: GNOME screen recorder drops vast majority of frames Status in gnome-shell package in Ubuntu: New Bug description: When I try to record a region on my screen, after about 4 seconds the frames stop updating. In the attached video, I am toggling between the two visible windows every half second, roughly. The only frame updates after 0:04 occur at 0:33, 1:07, and 1:40. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 12:13:30 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-01 (174 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993912/+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 1993920] Re: Some windows overflow to other monitors whenever they're near to border and wider than main screen
*** This bug is a duplicate of bug 1990563 *** https://bugs.launchpad.net/bugs/1990563 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1990563, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** This bug has been marked a duplicate of bug 1990563 Some maximized windows appear on both monitors -- 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/1993920 Title: Some windows overflow to other monitors whenever they're near to border and wider than main screen Status in mutter package in Ubuntu: New Bug description: After upgrading to Ubuntu 22.10, some applications (for example, VSCode and MySQL Workbench) are presenting weird behavior: if I move it to the secondary monitor and maximize the window, it gets mirrored in the main monitor. I've made some tests and realized that this issue occurs if I place the application window near to the divisor between the two monitors and this window's width is greater than the main monitor's one. Here is a link to a video that shows this issue: https://youtu.be/FmYSgpwS6Bk ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 18:19:27 2022 DistUpgraded: 2022-10-20 20:40:37,319 DEBUG icon theme changed, re-reading DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Comet Lake UHD Graphics [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Comet Lake UHD Graphics [144d:c834] InstallationDate: Installed on 2022-10-15 (7 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: SAMSUNG ELECTRONICS CO., LTD. 550XCJ/550XCR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-21-generic root=UUID=46adeab8-b7f5-472d-b479-38b045a695ff ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2022-10-20 (1 days ago) dmi.bios.date: 02/23/2022 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P12RFH.054.220223.HC dmi.board.asset.tag: No Asset Tag dmi.board.name: NP550XCJ-KF1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLA664A0C-C01-G002-S0001+10.0.19041 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP12RFH.054.220223.HC:bd02/23/2022:br5.16:svnSAMSUNGELECTRONICSCO.,LTD.:pn550XCJ/550XCR:pvrP12RFH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP550XCJ-KF1BR:rvrSGLA664A0C-C01-G002-S0001+10.0.19041:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-A5A5-PRFH: dmi.product.family: Notebook 5 Series dmi.product.name: 550XCJ/550XCR dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PRFH dmi.product.version: P12RFH dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1 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/mutter/+bug/1993920/+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 1993935] Re: Bluetooth is not connecting to any of my phone or headsets [Intel 3165 8086:3166]
** Summary changed: - Bluetooth issue + Bluetooth is not connecting to any of my phone or headsets [Intel 3165 8086:3166] ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1993935 Title: Bluetooth is not connecting to any of my phone or headsets [Intel 3165 8086:3166] Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Bluetooth is not connecting to any of my phone or headsets ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: bluez 5.65-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Oct 23 15:04:45 2022 InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 04f2:b628 Chicony Electronics Co., Ltd EasyCamera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81H7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=a1ad31f9-4430-4654-856d-9a144597827d ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/29/2020 dmi.bios.release: 1.26 dmi.bios.vendor: LENOVO dmi.bios.version: 8QCN26WW(V1.14) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 130-15IKB dmi.ec.firmware.release: 1.26 dmi.modalias: dmi:bvnLENOVO:bvr8QCN26WW(V1.14):bd12/29/2020:br1.26:efr1.26:svnLENOVO:pn81H7:pvrLenovoideapad130-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad130-15IKB:skuLENOVO_MT_81H7_BU_idea_FM_ideapad130-15IKB: dmi.product.family: ideapad 130-15IKB dmi.product.name: 81H7 dmi.product.sku: LENOVO_MT_81H7_BU_idea_FM_ideapad 130-15IKB dmi.product.version: Lenovo ideapad 130-15IKB dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A8:6D:AA:B9:23:31 ACL MTU: 1021:5 SCO MTU: 96:6 DOWN RX bytes:1914 acl:9 sco:0 events:106 errors:0 TX bytes:1359 acl:10 sco:0 commands:83 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1993935/+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 1987631] Re: Screencast only records one second
>From the upstream bug: > I think we can close this given that the workaround that has now been > released in 43 and 42.5 is all we can do from the shell side and the > required pipewire 0.3.57 has been out for a while now as well. ** Tags added: fixed-in-gnome-shell-42.5 fixed-in-gnome-shell-43.rc fixed-upstream ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Fix Released ** Also affects: gnome-shell (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu Jammy) Status: New => Fix Released ** Changed in: gnome-shell (Ubuntu Jammy) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1987631 Title: Screencast only records one second Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Committed Bug description: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 1993892] Re: Window area is unusable
Thanks for the bug report. Please try deleting any local extensions: cd ~/.local/share/gnome-shell/ rm -rf extensions and then log in again. If the problem still occurs then next time it does please: 1. Wait 10 seconds. 2. Reboot. 3. Run: journalctl -b-1 > prevboot.txt 4. Attach the resulting text file here. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1993892 Title: Window area is unusable Status in gnome-shell package in Ubuntu: Incomplete Bug description: The window area becomes unusable without warning and the same visual artefacts are seen (see attached). The system taskbar is still responsive, so I can logout/login, which resolves the issues temporarily. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 16:10:38 2022 DistUpgraded: 2022-10-21 06:47:07,363 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:2081] InstallationDate: Installed on 2022-10-14 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Intel(R) Client Systems NUC10i5FNH ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_6w0xyh@/vmlinuz-5.19.0-21-generic root=ZFS=rpool/ROOT/ubuntu_6w0xyh ro quiet splash vt.handoff=1 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago) dmi.bios.date: 04/09/2021 dmi.bios.release: 5.16 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0052.2021.0409.1144 dmi.board.asset.tag: Default string dmi.board.name: NUC10i5FNB dmi.board.vendor: Intel Corporation dmi.board.version: M38063-307 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.9 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0052.2021.0409.1144:bd04/09/2021:br5.16:efr3.9:svnIntel(R)ClientSystems:pnNUC10i5FNH:pvrM38014-308:rvnIntelCorporation:rnNUC10i5FNB:rvrM38063-307:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC10i5FNHN: dmi.product.family: FN dmi.product.name: NUC10i5FNH dmi.product.sku: BXNUC10i5FNHN dmi.product.version: M38014-308 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1 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/gnome-shell/+bug/1993892/+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 1993912] Re: GNOME screen recorder drops vast majority of frames
** Tags added: amdgpu -- 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/1993912 Title: GNOME screen recorder drops vast majority of frames Status in gnome-shell package in Ubuntu: New Bug description: When I try to record a region on my screen, after about 4 seconds the frames stop updating. In the attached video, I am toggling between the two visible windows every half second, roughly. The only frame updates after 0:04 occur at 0:33, 1:07, and 1:40. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 12:13:30 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-01 (174 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993912/+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 1993926] Re: No icon in tray and integration in menu when someone is connected
This orange screencast icon is only shown in Wayland sessions. In x11, any application can listen to input for any application (including passwords) and peek at their rendered content, so it is pointless to show that icon in x11 sessions too, since with no icon shown, applications can still spy on others there. In any case, it is not g-r-d, that shows that icon, but gnome-shell, when either a remote desktop session or screencast session was created. ** Changed in: gnome-remote-desktop (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1993926 Title: No icon in tray and integration in menu when someone is connected Status in gnome-remote-desktop package in Ubuntu: Invalid Bug description: I'm running an up to date Ubuntu 22.04.1 LTS using X. A friend of mine is having the same hardware and it's fully functional. Just few extensions but even I I disable everything still no orange icon and no integration, got no info. It's working perfectly, just a tiny bug. Anything I can provide to help? ... if you can provide commands I can do it. OS: Ubuntu 22.04.1 LTS Kernel: 5.15.0-52-generic Package: 42.4-0ubuntu1 *** 42.4-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-4ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1993926/+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 1993864] Re: Nautilus extension for gnome-console bad localization
** Tags added: jammy ** Package changed: mutter (Ubuntu) => gnome-console (Ubuntu) -- 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/1993864 Title: Nautilus extension for gnome-console bad localization Status in gnome-console package in Ubuntu: New Bug description: I've installed the nautilus-extension-gnome-console to have a right click item in Nautilus to open the current folder in Console, but it doesn't match my system language (French) and keeps displaying "Open in Console"). Tested on Ubuntu 22.04 with : - nautilus-extension-gnome-console 42~beta-1 - libnautilus-extension1a:amd64 1:42.2-0ubuntu1 - nautilus 1:42.2-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-console/+bug/1993864/+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 1993806] Re: Bluetooth not turning on and not connecting to my device [8087:0aaa Intel Corp. Bluetooth 9460/9560]
This is probably a kernel or firmware bug. Please try using the officially supported Ubuntu kernel (5.15.0-52.58) and/or try a newer upstream kernel like https://kernel.ubuntu.com/~kernel- ppa/mainline/v6.0.3/amd64/ ** Summary changed: - bluetooth not turning on and not connectting to my device + Bluetooth not turning on and not connecting to my device [8087:0aaa Intel Corp. Bluetooth 9460/9560] ** Package changed: bluez (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1993806 Title: Bluetooth not turning on and not connecting to my device [8087:0aaa Intel Corp. Bluetooth 9460/9560] Status in linux package in Ubuntu: Incomplete Bug description: Yesterday I connect my bluettoh phone in my new computer with Ubuntu 22.04, then today I wasnt able to reconect my phone, I tryes to disconect it in ubuntu interface, but this doesnt disconect, but no sound come from my earphone, then I tryed to turn bluetooth off, and it doesnt turn in again now. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluetooth (not installed) Uname: Linux 5.19.2-051902-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Oct 21 08:37:09 2022 InstallationDate: Installed on 2022-08-18 (63 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Positivo Bahia - VAIO VJFE44F11X-B2111H ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.2-051902-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/17/2022 dmi.bios.release: 5.24 dmi.bios.version: V1.19.X dmi.board.asset.tag: Default string dmi.board.name: VJFE-ADLBAT55 dmi.board.vendor: Positivo Tecnologia SA dmi.board.version: 11179464 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Positivo Tecnologia SA dmi.chassis.version: Default string dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvn:bvrV1.19.X:bd06/17/2022:br5.24:efr1.14:svnPositivoBahia-VAIO:pnVJFE44F11X-B2111H:pvrV1.19.X:rvnPositivoTecnologiaSA:rnVJFE-ADLBAT55:rvr11179464:cvnPositivoTecnologiaSA:ct10:cvrDefaultstring:sku3343073: dmi.product.family: VJFE44 dmi.product.name: VJFE44F11X-B2111H dmi.product.sku: 3343073 dmi.product.version: V1.19.X dmi.sys.vendor: Positivo Bahia - VAIO hciconfig: hci0:Type: Primary Bus: USB BD Address: 70:32:17:8B:A0:FF ACL MTU: 1021:4 SCO MTU: 96:6 DOWN RX bytes:2874357 acl:298 sco:0 events:409778 errors:0 TX bytes:251252400 acl:406246 sco:0 commands:3297 errors:0 syslog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993806/+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 1993831] Re: gnome-shell does not contain gjs dependence
** Tags added: kinetic -- 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/1993831 Title: gnome-shell does not contain gjs dependence Status in gnome-shell package in Ubuntu: Triaged Bug description: Hi, I updated from Ubuntu 22.04 to Ubuntu 22.10 and I had an issue with GNOME shell "Extensions" app. I replaced "Extensions" (gnome-shell-extension-prefs) with Flatpak version of it from Flathub using GNOME "Software" center. After this, I'm not sure, I might have used the "sudo apt auto-remove" command. After these changes, Flatpak version of the "Extensions" app gave an error: (https://github.com/flathub/org.gnome.Extensions/issues/13) After a bit of digging, I realized removing "Extensions" packages also removes gjs dependence. So I installed gjs package and "Extensions" works again. 1) OS OS: Ubuntu 22.10 Desktop: GNOME 2) Package gnome-shell: 43.0-1ubuntu2 gnome-shell-extension-prefs: 43.0-1ubuntu2 3) What you expected to happen Removing the package and installing Flatpak version without any error. 4) What happened instead I replaced the app with Flatpak version and it removed gjs and gnome- shell extension support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993831/+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 422012] Re: Emptying the trash can lead to have files still on disk in expunged
Same behaviour on Ubuntu 22.04.1 LTS with nemo 5.2.4-1 ... The files seem to be moved there if you delete a directory of yours with files from other users in it from the trash. Proposal for behaviour changes: 1. Not create and use the "expunged" folder at all and just fail to delete other users' files from your own trash. 2. Continue to use the "expunged" folder but warn the user when and why and which files are being moved there (and maybe even continuing to show them in "trash:///"). -- 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/422012 Title: Emptying the trash can lead to have files still on disk in expunged Status in nautilus package in Ubuntu: Triaged Status in thunar package in Ubuntu: Confirmed Bug description: Binary package hint: nautilus When moving files to the Trash which are belong to another user and you don't have access to, nautilus moves the files into a folder ~/.local/share/Trash/expunged. The problem is that there is no warning that this is happening and the location of the files is far from obvious. I only discovered the folder by using disk analyser and finding that there was a massive folder in ~/.local/share/Trash/expunged. It transpired after deleting the offending files that there had been some 70Gb worth of files!!! Would it not make far more sense from a function point of view to move the files into the Trash as per normal but just fail to empty them? At least you would be able to see them and know that you needed to do something! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/422012/+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 1993992] [NEW] kinetic.xml has wrong filename for a wallpaper
Public bug reported: In the kinetic wallpaper package, the kinetic.xml file that handles the rotating background has the wrong filename for "/usr/share/backgrounds/Twisted_Gradients_by_Gustavo_Brenner.png". It uses ".jpg" instead of the correct ".png" extension. ** Affects: ubuntu-wallpapers (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1993992 Title: kinetic.xml has wrong filename for a wallpaper Status in ubuntu-wallpapers package in Ubuntu: New Bug description: In the kinetic wallpaper package, the kinetic.xml file that handles the rotating background has the wrong filename for "/usr/share/backgrounds/Twisted_Gradients_by_Gustavo_Brenner.png". It uses ".jpg" instead of the correct ".png" extension. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1993992/+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 1710209] Re: package libappstream3 0.9.4-1ubuntu3 [modified: usr/share/doc/libappstream3/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/
[Expired for appstream (Ubuntu) because there has been no activity for 60 days.] ** Changed in: appstream (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1710209 Title: package libappstream3 0.9.4-1ubuntu3 [modified: usr/share/doc/libappstream3/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libappstream3/changelog.Debian.gz', which is different from other instances of package libappstream3:i386 Status in appstream package in Ubuntu: Expired Bug description: . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libappstream3 0.9.4-1ubuntu3 [modified: usr/share/doc/libappstream3/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Fri Aug 11 07:58:41 2017 DpkgHistoryLog: Start-Date: 2017-08-11 07:58:37 Commandline: apt-get -f install Requested-By: mike (1000) Upgrade: libappstream3:i386 (0.9.4-1ubuntu1, 0.9.4-1ubuntu3) DpkgTerminalLog: Preparing to unpack .../libappstream3_0.9.4-1ubuntu3_i386.deb ... Unpacking libappstream3:i386 (0.9.4-1ubuntu3) over (0.9.4-1ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/libappstream3_0.9.4-1ubuntu3_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libappstream3/changelog.Debian.gz', which is different from other instances of package libappstream3:i386 DuplicateSignature: package:libappstream3:0.9.4-1ubuntu3 [modified: usr/share/doc/libappstream3/changelog.Debian.gz] Unpacking libappstream3:i386 (0.9.4-1ubuntu3) over (0.9.4-1ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/libappstream3_0.9.4-1ubuntu3_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libappstream3/changelog.Debian.gz', which is different from other instances of package libappstream3:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libappstream3/changelog.Debian.gz', which is different from other instances of package libappstream3:i386 InstallationDate: Installed on 2017-02-20 (171 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: appstream Title: package libappstream3 0.9.4-1ubuntu3 [modified: usr/share/doc/libappstream3/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libappstream3/changelog.Debian.gz', which is different from other instances of package libappstream3:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1710209/+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 1601971] Re: update fails, "AppStream cache update failed."
[Expired for appstream (Ubuntu) because there has been no activity for 60 days.] ** Changed in: appstream (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1601971 Title: update fails, "AppStream cache update failed." Status in appstream package in Ubuntu: Expired Bug description: Booted 16.04 amd64 from DVD, opened a gnome-terminal and ran, ubuntu@ubuntu:~$ sudo apt-get update Ign:1 cdrom://Ubuntu 16.04 LTS _Xenial Xerus_ - Release amd64 (20160420.1) xenial InRelease Hit:2 cdrom://Ubuntu 16.04 LTS _Xenial Xerus_ - Release amd64 (20160420.1) xenial Release Get:4 http://archive.ubuntu.com/ubuntu xenial InRelease [247 kB] Get:5 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB] Get:6 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [94.5 kB] Get:7 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages [119 kB] Get:8 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages [1,201 kB] Get:9 http://archive.ubuntu.com/ubuntu xenial/main Translation-en [568 kB] Get:10 http://security.ubuntu.com/ubuntu xenial-security/main Translation-en [45.3 kB] Get:11 http://security.ubuntu.com/ubuntu xenial-security/main amd64 DEP-11 Metadata [44.0 kB] Get:12 http://security.ubuntu.com/ubuntu xenial-security/main DEP-11 64x64 Icons [50.8 kB] Get:13 http://security.ubuntu.com/ubuntu xenial-security/restricted amd64 DEP-11 Metadata [158 B] Get:14 http://archive.ubuntu.com/ubuntu xenial/main amd64 DEP-11 Metadata [733 kB] Get:15 http://archive.ubuntu.com/ubuntu xenial/main DEP-11 64x64 Icons [409 kB] Get:16 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [252 kB] Get:17 http://archive.ubuntu.com/ubuntu xenial-updates/main Translation-en [99.8 kB] Get:18 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 DEP-11 Metadata [186 kB] Get:19 http://archive.ubuntu.com/ubuntu xenial-updates/main DEP-11 64x64 Icons [150 kB] Get:20 http://archive.ubuntu.com/ubuntu xenial-updates/restricted amd64 DEP-11 Metadata [157 B] Fetched 4,293 kB in 1s (2,360 kB/s) ** (appstreamcli:2593): CRITICAL **: Error while moving old database out of the way. AppStream cache update failed. Reading package lists... Done ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: appstream 0.9.4-1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.376 CurrentDesktop: Unity Date: Mon Jul 11 19:24:40 2016 LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: appstream UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1601971/+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 1987527] Re: package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1987527 Title: package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 Status in firefox package in Ubuntu: Expired Bug description: After upgrade from Ubuntu 20.04 to 22.04, the Firefox browser could not open. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Aug 16 12:05:53 2022 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-03-08 (1629 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 Snap: firefox 104.0-3 (latest/stable) Snap.Changes: ID Status Spawn Ready Summary 603 Done2022-08-23T16:40:48+01:00 2022-08-23T16:42:16+01:00 Refresh "firefox" snap from "esr/edge" channel 604 Done2022-08-23T16:42:39+01:00 2022-08-23T16:44:13+01:00 Refresh "firefox" snap from "latest/stable" channel SourcePackage: firefox Title: package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1987527/+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 1993892] Re: Window area is unusable
Today it happened again: I had 2 terminal windows open. I was viewing one when I clicked the Terminal icon in the dock. Then the desktop became unusable. I right-clicked the Terminal icon and chose "Quit 2 Windows". Nothing happened. When I tried again, it was "Quit 3 Windows". -- 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/1993892 Title: Window area is unusable Status in xorg package in Ubuntu: New Bug description: The window area becomes unusable without warning and the same visual artefacts are seen (see attached). The system taskbar is still responsive, so I can logout/login, which resolves the issues temporarily. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 16:10:38 2022 DistUpgraded: 2022-10-21 06:47:07,363 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:2081] InstallationDate: Installed on 2022-10-14 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Intel(R) Client Systems NUC10i5FNH ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_6w0xyh@/vmlinuz-5.19.0-21-generic root=ZFS=rpool/ROOT/ubuntu_6w0xyh ro quiet splash vt.handoff=1 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago) dmi.bios.date: 04/09/2021 dmi.bios.release: 5.16 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0052.2021.0409.1144 dmi.board.asset.tag: Default string dmi.board.name: NUC10i5FNB dmi.board.vendor: Intel Corporation dmi.board.version: M38063-307 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.9 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0052.2021.0409.1144:bd04/09/2021:br5.16:efr3.9:svnIntel(R)ClientSystems:pnNUC10i5FNH:pvrM38014-308:rvnIntelCorporation:rnNUC10i5FNB:rvrM38063-307:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC10i5FNHN: dmi.product.family: FN dmi.product.name: NUC10i5FNH dmi.product.sku: BXNUC10i5FNHN dmi.product.version: M38014-308 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1 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/1993892/+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 1993940] Re: applications start in the background instead of the foreground
This problem sounds related to focus stealing prevention. That's the feature intended to put new windows in the background when the system thinks you're still busy in the foreground. However, since you're using a 4-year old release I would first recommend trying the latest long term release (22.04.1): https://ubuntu.com/download/desktop because this bug is likely to have been fixed already. ** Summary changed: - applications start in the background instead of the foreground + [bionic] applications start in the background instead of the foreground -- 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/1993940 Title: [bionic] applications start in the background instead of the foreground Status in gnome-shell package in Ubuntu: New Bug description: I frequently see new applications windows open in the background instead of the foreground, e.g., if I click on a link in an e-mail in Thunderbird, a new browser window will open and a notification at the top of the screen will let me know that the windows has been opened, but Thunderbird remains in the foreground and the new window opens in the background. I've been seeing this for a long time now, but I'd like to stop wrestling with the GUI shell to get to the application that I just started. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.7 ProcVersionSignature: Ubuntu 5.4.0-126.142~18.04.1-generic 5.4.203 Uname: Linux 5.4.0-126-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 23 11:52:17 2022 DisplayManager: gdm3 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-05-10 (1626 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2020-03-04 (963 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993940/+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 1985089] Re: Resizing two edge tiled windows is laggy
I think we can wait for the discussions to be resolved and it for it to be merged upstream: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2579 Then hopefully the fix will be included in mutter 42.6. ** Changed in: mutter (Ubuntu) Status: Confirmed => In Progress -- 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/1985089 Title: Resizing two edge tiled windows is laggy Status in Mutter: Unknown Status in mutter package in Ubuntu: In Progress Bug description: Just to report an issue that other people have reported to GNOME and in Reddit, that seems to also affect Ubuntu 22.04. If you snap 2 windows side-by-side in Wayland and then try to resize them, it's very slow and uses a lot of memory. Check here for more details: - https://gitlab.gnome.org/GNOME/mutter/-/issues/2246 - https://old.reddit.com/r/gnome/comments/whjgel/resizing_two_tiled_windows_leaks_memory_and_is/ To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1985089/+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 1993668] Re: mSBC codec not available only CVSD one
** Changed in: pipewire Status: Fix Released => Unknown ** Changed in: pipewire Remote watch: gitlab.freedesktop.org/pipewire/wireplumber/-/issues #363 => gitlab.freedesktop.org/pipewire/pipewire/-/issues #2783 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Linux Kernel Bug Tracker #216615 https://bugzilla.kernel.org/show_bug.cgi?id=216615 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=216615 Importance: Unknown Status: Unknown -- 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/1993668 Title: mSBC codec not available only CVSD one Status in Linux: Unknown Status in PipeWire: Unknown Status in linux package in Ubuntu: New Status in pipewire package in Ubuntu: New Bug description: I am using Ubuntu 22.10 and my headset Pixel Buds Pro works correctly but only the low-quality CVSD codec is available and not the mSBC one for the Handsfree profile. I know the Pixel Buds Pro headset are compatible with mSBC because on another machine also running Ubuntu 22.10, this headset correctly works with the mSBC codec (and the audio quality is much better for both input and output audio). My motherboard is an Aorus x670 with AMD Zen 4 CPU. The bluetooth controller seems to be: ``` Bus 005 Device 003: ID 0e8d:0616 MediaTek Inc. Wireless_Device ``` Let me know if you need more informations. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-09-27 (22 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1) NonfreeKernelModules: nvidia_modeset nvidia Package: pipewire 0.3.58-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Tags: kinetic Uname: Linux 5.19.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1993668/+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 1966787] Re: Totem crashes on launch | GStreamer-GL-CRITICAL **: Failed to flush Wayland connection | Gdk-Message: Error flushing display: Protocol error
*** This bug is a duplicate of bug 1965563 *** https://bugs.launchpad.net/bugs/1965563 Yes the fix is in egl-wayland 1.1.10 - https://launchpad.net/ubuntu/+source/egl-wayland -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1966787 Title: Totem crashes on launch | GStreamer-GL-CRITICAL **: Failed to flush Wayland connection | Gdk-Message: Error flushing display: Protocol error Status in NVIDIA / egl-wayland: Unknown Status in egl-wayland package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in totem package in Ubuntu: Confirmed Bug description: If I launch totem, it crashes pretty much immediately. I resolved this by deleting .config/totem. I had moved some video files that had been previously opened within it recently, so possibly it was trying to reference them (for thumbnails or whatever) and that broke it. robin@malik:~$ totem (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection Gdk-Message: 18:00:17.844: Error flushing display: Protocol error robin@malik:~$ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: totem 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 18:00:39 2022 InstallationDate: Installed on 2022-03-23 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/egl-wayland/+bug/1966787/+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 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Jorge, Please open a new bug to discuss that, by running: ubuntu-bug gnome-shell -- 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/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in GNOME Shell: New Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: [ Workaround ] Add to /etc/environment (in Ubuntu 22.04): MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 or in Ubuntu 22.10 and later: MUTTER_DEBUG_FORCE_KMS_MODE=simple and then reboot. [ Original report ] (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+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 1992667] Re: Application windows invisible (on DG2 graphics)
** Changed in: mesa (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1992667 Title: Application windows invisible (on DG2 graphics) Status in linux-oem-6.0 package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Fix Released Status in linux-oem-6.0 source package in Jammy: New Status in mesa source package in Jammy: New Bug description: When using GNOME Shell with Wayland, all application windows become invisible from time to time. This usually happens right after starting GNOME Shell for the first time or after having a VRAM intensive application open, such as a game. I have installed the latest linux-oem-6.0 kernel and manually enabled support for DG2 graphics by passing the i915.force_probe parameter with the PCIe ID of the graphics card. I have attached a screenshot of the described behavior below. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0 Uname: Linux 6.0.0-1005-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Oct 12 17:23:40 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-10-11 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1992667/+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 1969422] Re: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object(
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- 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/1969422 Title: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object() Status in Mutter: Unknown Status in OEM Priority Project: Fix Committed Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Kinetic: Fix Released Bug description: [ Impact ] On dual-GPU systems, gnome-shell may crash in gbm_surface_release_buffer() during display config changes, like when rearranging monitor positions. [ Test Plan ] 1. Find a dual GPU system where both use open source drivers (like Intel + AMD). 2. Ideally also attach one monitor to each GPU. 3. Open Settings and repeatedly change the monitor layout pressing Apply each time. Expect: System does not crash. [ Where problems could occur ] Anywhere to do with screen updates since the entire triple buffering patch has been updated. [ Other Info ] The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/4fa0be3b67c650c621a425137efd7376c32451b4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1969422/+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 1987076] Re: Mouse cannot control windows after suspend and display change
** Changed in: mutter (Ubuntu) Status: Expired => New -- 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/1987076 Title: Mouse cannot control windows after suspend and display change Status in mutter package in Ubuntu: New Bug description: My setup is this: Ubuntu: 22.04.1 LTS (Vanilla Gnome session on Wayland) Laptop: Lenovo ThinkPad P14s Gen 2a (AMD). Display: Lenovo T34w-20, connected via USB-C The problem started with upgrade to 22.04 I have had the same exact problem with my previous laptop, a ThinkPad T14s. Both of these are AMD laptops, but I had no problem on 21.10. Way I can usually reproduce (always?) 1. Suspend my laptop by yanking out the USB-C cable. 2. Resume the laptop by connecting a different monitor (same make and model, but not the same physical one) and hit the keyboard a few times. Note: Resuming on the same physical display does not seem to result in the same problem. After this, I can no longer control the Windows on my desktop. The mouse cursor is active, but moves behind the open windows, and mouse click is not registered (at least not in a way that is useful). I can navigate the windows and use the applications, using the keyboard. Ctrl+Alt+F1 to get to GDM, the mouse works fine. Going back the the real session, mouse is still "broken". Ctrl+Alt+F2 to get to a TTY, and going back to the original session, mouse is still "broken". Only way I have found to reliably restore functionality is a reboot (which I have been doing a lot of the last few months). Please let me know what else I can provide you with, in order to get this fixed. :) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter 42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Fri Aug 19 10:32:48 2022 InstallationDate: Installed on 2022-05-20 (91 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1987076/+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 1993844] Re: three finger gesture
1. Which three finger gesture are you trying to use? 2. Please run this command to collect more system information: apport-collect 1993844 ** Package changed: gdm3 (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1993844 Title: three finger gesture Status in gnome-shell package in Ubuntu: Incomplete Bug description: three finger gesture for multitask window off suddenly i don't know why in ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993844/+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 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
One can use the builds directly from Mozilla https://www.mozilla.org/firefox/all/ but the onus is on the user/sysadmin to keep it updated. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in Mozilla Firefox: In Progress Status in KeePassXC Snap Builds: Unknown Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: In Progress Status in goopg package in Ubuntu: Confirmed Status in kdeconnect package in Ubuntu: Confirmed Status in plasma-browser-integration package in Ubuntu: Confirmed Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. [Workaround] If you're using Ubuntu 22.04 LTS, you can install GNOME Shell extensions with this app. sudo apt install gnome-shell-extension-manager To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1741074/+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 1979096] Re: gnome-shell search can't launch apps if dock auto-hide is enabled
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1979096 Title: gnome-shell search can't launch apps if dock auto-hide is enabled Status in Dash to dock: Fix Released Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Confirmed Bug description: The problem happens, when I enable the dock to hide automatically. With this enabled, it is not possible to run the programs through the search. But when disabled, it is possible to search and run the programs. Here's the video of the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 17 18:21:45 2022 DistUpgraded: 2022-04-21 13:52:59,951 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: v4l2loopback/0.12.5, 5.15.0-37-generic, x86_64: installed v4l2loopback/0.12.5, 5.15.0-39-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. RS780L [Radeon 3000] [1043:8388] InstallationDate: Installed on 2021-04-15 (428 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=7e3c483e-6d02-4fc2-be0e-48207eb147eb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-21 (57 days ago) dmi.bios.date: 03/04/2017 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX/BR dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd03/04/2017:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX/BR:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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/dash-to-dock/+bug/1979096/+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 1993889] Re: nautilus does not launch
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1993889 Title: nautilus does not launch Status in nautilus package in Ubuntu: Confirmed Bug description: Problem: nautilus does not launch after it was closed previously. Expectation: Close nautilus, start nautilus again -> new nautilus window spawns. What happens: nautilus does not launch a second time. The cursor spins, but no window opens. Observations: the nautilus process does not get terminated properly. There is a nautilus process remaining with almost no CPU consumption. Workarounds: Killing the process and starting nautilus again works. Starting it via console and exiting it via X button does not end the task in the terminal. CTRL+C terminates the process and it's restarting fine. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 14:03:06 2022 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1033, 685)' InstallationDate: Installed on 2022-10-22 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 python3-nautilus 4.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1993889/+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 1993907] Re: nautilus freezes randomly
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1993907 Title: nautilus freezes randomly Status in nautilus package in Ubuntu: Confirmed Bug description: nautilus becomes unresponsive and "files" is not responding sign appears at random ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-1007.7-lowlatency 5.19.7 Uname: Linux 5.19.0-1007-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 15:39:58 2022 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'medium'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1272, 787)' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2022-05-13 (161 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-10-19 (3 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 python3-nautilus 4.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1993907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1961508] Re: Dock displaying over window after resuming from blank screen
Hi, I just wanted to say that I am also having this problem. I'm on Ubuntu 22.04 LTS with all of the available updates applied. In the attached screenshot, you'll see my terminal window as being underneath the Dock, which I didn't have it like that originally. It tends to happen after unlocking the screen. I do not have the Dock set to use the Auto-hide mode and I've tried using the Dock in both panel and non-panel mode. This bug is super annoying as I need to click the "Restore Down" and then "Maximize" in the window controls in each affected application window to get them fixed temporarily. --William ** Attachment added: "Terminal window underneath the Dock now. Ugh." https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1961508/+attachment/5626231/+files/Screenshot%20from%202022-10-23%2016-34-03.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1961508 Title: Dock displaying over window after resuming from blank screen Status in Dash to dock: Unknown Status in Mutter: New Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I have Blank Screen set to happen after 2 minutes of inactivity. When resuming from a Blank Screen (by moving the mouse or touching the keyboard), the Dock is displayed over the top of the current program. To get it back to normal I need to click "Restore Down" on the current programs window and then "Maximize" so that the Dock no longer overlaps it. (Note: I have Auto-hide dock turned off.) This only happens sometimes. I can't reproduce the bug it every time. - 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu - Ubuntu 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center - Not sure (I guess the Dock is part of the Gnome interface?) 3) What you expected to happen - Dock should not overlap the current program on resume from screen blank. 4) What happened instead - The Dock overlaps the current program on resume from screen blank. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2022-02-18 (24 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell-extension-ubuntu-dock PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 Tags: wayland-session impish Uname: Linux 5.13.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966126] Re: Current Firefox 98.0.1 in 21.10 refuses to play Netflix videos due to lack of upstream available patch
New 'current' firefox solves the problem ** Changed in: firefox (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1966126 Title: Current Firefox 98.0.1 in 21.10 refuses to play Netflix videos due to lack of upstream available patch Status in firefox package in Ubuntu: Fix Released Bug description: The version of Firefox > LANG="en" apt-cache policy firefox firefox: Installed: 98.0.1+build2-0ubuntu0.21.10.1 Candidate: 98.0.1+build2-0ubuntu0.21.10.1 Version table: *** 98.0.1+build2-0ubuntu0.21.10.1 500 500 http://archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish-security/main amd64 Packages 100 /var/lib/dpkg/status 93.0+build1-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages refuses to play Netflix DRM videos with Netflix error F7702-1003. The Firefox Nighly: $ LANG="en" apt-cache policy firefox-trunk firefox-trunk: Installed: 99.0~a1~hg20220220r608252-0ubuntu0.18.04.1~umd1 Candidate: 99.0~a1~hg20220220r608252-0ubuntu0.18.04.1~umd1 Version table: *** 99.0~a1~hg20220220r608252-0ubuntu0.18.04.1~umd1 100 doesn't have such problem. It seems this comes symlinking problem related to have the app was packaged and known bug which was described here: https://bugzilla.mozilla.org/show_bug.cgi?id=1236680#c5 . It would be good to dissect those versions and include patch in base package instead of firefox-trunk only. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: firefox 98.0.1+build2-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.10.0-1057.61-oem 5.10.83 Uname: Linux 5.10.0-1057-oem x86_64 NonfreeKernelModules: wl AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nusch 4524 F pipewire nusch 4526 F wireplumber /dev/snd/pcmC0D0p: nusch 4524 F...m pipewire /dev/snd/seq:nusch 4524 F pipewire BuildID: 20220313140707 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Mar 23 21:17:20 2022 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2015-05-08 (2511 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-43cfcdf0-6905-4f8c-b01a-ef1520190505 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 PrefSources: prefs.js ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=98.0.1/20220313140707 (In use) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-43cfcdf0-6905-4f8c-b01a-ef1520190505 bp-eeff7831-f848-48bd-acb5-f1e671180331 bp-2319616a-a598-4912-b7cc-951892160929 Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to impish on 2022-02-21 (30 days ago) dmi.bios.date: 02/25/2022 dmi.bios.release: 3.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.5.1 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.5.1:bd02/25/2022:br3.5:svnDellInc.:pnXPS139310:pvr:sku0991:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966126/+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 1894400] Re: Establishing connection to PulseAudio. Please wait...
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/1894400 Title: Establishing connection to PulseAudio. Please wait... Status in pulseaudio package in Ubuntu: Confirmed Bug description: Sometimes when i start up firefox in the morning i can't hear any audio. Or sometimes a page that wants to play audio will freeze, waiting. When these happen i'll launch pavucontrol next and it'll say "Establishing connection to PulseAudio. Please wait..." and just keep waiting. i look for the pulseaudio process, it's there as usual. Even so i just launch an additional pulseaudio process, and then pavucontrol is immediately all happy. Firefox might also immediately become all happy, or less often i'll also need to restart firefox before i can play audio. i usually shut off my computer at night. Starting it up each morning, manifestations as described above might be separated by a couple weeks, or might happen a couple times within a week. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.4 [modified: usr/share/pulseaudio/alsa-mixer/paths/steelseries-arctis-7-output-mono.conf] ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 5 16:45:50 2020 ProcEnviron: LC_TIME=en_DK.utf8 TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash 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: 04/30/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0PU052 dmi.board.vendor: Dell Inc. dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd04/30/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 755 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894400/+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 1992756] Re: Screen turns black for a long time after each login and when detecting screens or changing screen layout.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-515 (Ubuntu) Status: New => Confirmed -- 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/1992756 Title: Screen turns black for a long time after each login and when detecting screens or changing screen layout. Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: I have a Thinkpad P15 with a A2000 GPU with Ubuntu 22.04.1 LTS. This happens using Wayland and nvidia cuda drivers. It seems like the system uses very long to identify the screens. This happens when I use external monitors, but also when only using the laptop screen. Changing the screen layout takes so long that I am unable to accept the change before it is reverted to the previous. Only the mouse pointer is visible, the rest of the screens are black during this process. $ apt-cache policy cuda cuda: Installed: 11.7.1-1 Candidate: 11.8.0-1 Version table: 11.8.0-1 600 600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64 Packages *** 11.7.1-1 600 600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64 Packages 100 /var/lib/dpkg/status 11.7.0-1 600 600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64 Packages $ nvidia-smi Thu Oct 13 10:46:02 2022 +-+ | NVIDIA-SMI 515.65.01Driver Version: 515.65.01CUDA Version: 11.7 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===+==+==| | 0 NVIDIA RTX A200... On | :01:00.0 On | N/A | | N/A 46CP5 8W / N/A |146MiB / 4096MiB | 22% Default | | | | N/A | +---+--+--+ +-+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |=| |0 N/A N/A 4451 G /usr/lib/xorg/Xorg145MiB | +-+ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 13 10:25:17 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-05 (37 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1992756/+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 1992756] Re: Screen turns black for a long time after each login and when detecting screens or changing screen layout.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed -- 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/1992756 Title: Screen turns black for a long time after each login and when detecting screens or changing screen layout. Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: I have a Thinkpad P15 with a A2000 GPU with Ubuntu 22.04.1 LTS. This happens using Wayland and nvidia cuda drivers. It seems like the system uses very long to identify the screens. This happens when I use external monitors, but also when only using the laptop screen. Changing the screen layout takes so long that I am unable to accept the change before it is reverted to the previous. Only the mouse pointer is visible, the rest of the screens are black during this process. $ apt-cache policy cuda cuda: Installed: 11.7.1-1 Candidate: 11.8.0-1 Version table: 11.8.0-1 600 600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64 Packages *** 11.7.1-1 600 600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64 Packages 100 /var/lib/dpkg/status 11.7.0-1 600 600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64 Packages $ nvidia-smi Thu Oct 13 10:46:02 2022 +-+ | NVIDIA-SMI 515.65.01Driver Version: 515.65.01CUDA Version: 11.7 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===+==+==| | 0 NVIDIA RTX A200... On | :01:00.0 On | N/A | | N/A 46CP5 8W / N/A |146MiB / 4096MiB | 22% Default | | | | N/A | +---+--+--+ +-+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |=| |0 N/A N/A 4451 G /usr/lib/xorg/Xorg145MiB | +-+ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 13 10:25:17 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-05 (37 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1992756/+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 1992756] Re: Screen turns black for a long time after each login and when detecting screens or changing screen layout.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- 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/1992756 Title: Screen turns black for a long time after each login and when detecting screens or changing screen layout. Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: I have a Thinkpad P15 with a A2000 GPU with Ubuntu 22.04.1 LTS. This happens using Wayland and nvidia cuda drivers. It seems like the system uses very long to identify the screens. This happens when I use external monitors, but also when only using the laptop screen. Changing the screen layout takes so long that I am unable to accept the change before it is reverted to the previous. Only the mouse pointer is visible, the rest of the screens are black during this process. $ apt-cache policy cuda cuda: Installed: 11.7.1-1 Candidate: 11.8.0-1 Version table: 11.8.0-1 600 600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64 Packages *** 11.7.1-1 600 600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64 Packages 100 /var/lib/dpkg/status 11.7.0-1 600 600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64 Packages $ nvidia-smi Thu Oct 13 10:46:02 2022 +-+ | NVIDIA-SMI 515.65.01Driver Version: 515.65.01CUDA Version: 11.7 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===+==+==| | 0 NVIDIA RTX A200... On | :01:00.0 On | N/A | | N/A 46CP5 8W / N/A |146MiB / 4096MiB | 22% Default | | | | N/A | +---+--+--+ +-+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |=| |0 N/A N/A 4451 G /usr/lib/xorg/Xorg145MiB | +-+ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 13 10:25:17 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-05 (37 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1992756/+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 1993562] Re: [snap] apparmor denials on /sys/devices/virtual/dmi/id/bios_vendor, bios_version, board_name and board_vendor
Thanks for the test build Nathan, it works as I no longer see those denials with the provided snap (chromium 107.0.5304.62). Thanks again! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1993562 Title: [snap] apparmor denials on /sys/devices/virtual/dmi/id/bios_vendor, bios_version, board_name and board_vendor Status in chromium-browser package in Ubuntu: Fix Committed Bug description: When starting chromium's snap, those messages are logged: $ journalctl -o cat -k --grep 'apparmor="DENIED"' | grep -F snap.chromium.chromium audit: type=1400 audit(1666201583.608:610): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/board_vendor" pid=320950 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 audit: type=1400 audit(1666201583.608:611): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/board_name" pid=320950 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 audit: type=1400 audit(1666201583.608:612): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/bios_vendor" pid=320950 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 audit: type=1400 audit(1666201583.608:613): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/bios_version" pid=320950 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Chromium behaves OK but generates log pollution. Additional info: $ snap list chromium snapd Name Version RevTracking Publisher Notes chromium 106.0.5249.119 2136 latest/stable canonical✓ - snapd 2.57.4 17336 latest/stable canonical✓ snapd $ uname -rm 5.15.0-52-generic x86_64 $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993562/+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 1970148] Re: Brave & Chrome browsers freezes on download and print to pdf
I have same problem. I tried sudo apt install xdg-dessktop-portal-gnome and/or disable "Use hardware acceleration when available" from browser. The problem was fixed but not completely. Reinstall Nvidia driver work for me I applied the solution found here: https://askubuntu.com/a/1416189/1591703 I changed Nvidia driver 510 to another version and it solved my problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1970148 Title: Brave & Chrome browsers freezes on download and print to pdf Status in chromium-browser package in Ubuntu: Invalid Bug description: Whenever any file is downloaded, the browser will freeze. Download files, from any page does not work. Same issue with Firefox. Similarly, the browser will freeze when a page is printed to pdf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1970148/+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 1991524] Re: regression: broadwell-rt286 sound card audio output is extremely low
Issue is still present in the release version of 22.10. -- 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/1991524 Title: regression: broadwell-rt286 sound card audio output is extremely low Status in alsa-driver package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center alsa-base: Installed: 1.0.25+dfsg-0ubuntu7 Candidate: 1.0.25+dfsg-0ubuntu7 Version table: *** 1.0.25+dfsg-0ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu kinetic/main i386 Packages 100 /var/lib/dpkg/status 3) What you expected to happen In Ubuntu 22.04 and prior versions, audio output via my laptop speakers worked just fine. It was clear and played at a reasonable max volume. I expected the same for 22.10. 4) What happened instead Audio output for my laptop (an HP Spectre x360 Convertible 13--802D) is extremely low, to the point where I thought sound wasn't playing at all. It was only when I played an extremely loud YouTube video with volume at max with the speaker held up to my ear that I realized it was playing. The same issue is happening with my laptop's headphone jack, but not when I plug in a USB speaker or play sound via HDMI. I know that Ubuntu is switching to pipewire and wireplumber for audio in the 22.10 release. Pipewire has given me trouble on other distributions that already use it for this particular device, so that may be part of the problem. I've tried increasing all volume sliders in alsamixer as well, with no improvement. Please let me know if there's any other information you need. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 3 07:18:54 2022 InstallationDate: Installed on 2022-10-03 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2018 dmi.bios.release: 15.81 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.51 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 802D dmi.board.vendor: Hewlett-Packard dmi.board.version: 58.63 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 58.99 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.51:bd06/20/2018:br15.81:efr58.99:svnHewlett-Packard:pnHPSpectrex360Convertible13:pvr:rvnHewlett-Packard:rn802D:rvr58.63:cvnHewlett-Packard:ct10:cvrChassisVersion:skuL0Q56UA#ABA: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre x360 Convertible 13 dmi.product.sku: L0Q56UA#ABA dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1991524/+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 1969315] Re: text in torrent info tabs change after opening it to gibberish
On 10-10-2022 I have, in 'startup applications', delayed the startup of transmission by 5 seconds. It seems to have helped. So far so good. Let's see if it keeps on working this way. Maybe this turns out to be a useful workaround. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1969315 Title: text in torrent info tabs change after opening it to gibberish Status in transmission package in Ubuntu: Confirmed Bug description: on transmission-gtk after opening the torrent's properties panel, the text at first it's showing ok, buy on mouse hover it changes to random text worked fine on 21.10 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: transmission-gtk 3.00-2ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 17 19:28:03 2022 SourcePackage: transmission UpgradeStatus: Upgraded to jammy on 2022-03-26 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1969315/+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 1980937] Re: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise
Updating to 22.10 fixes the problem entirely, including the internal speaker. -- 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/1980937 Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise Status in alsa-driver package in Ubuntu: Confirmed Bug description: New laptop with fresh installation of Xubuntu 22.04. Intel Tiger Lake- LP audio controller. When playing any audio, the internal speaker plays no sound except periodic loud crackling noise. The 3.5mm jack does not work either, producing the same craclking noise alongside some eletrical noise. HDMI audio skimmishly tested, but also gave no sound. Curiously, USB headphone (along with microphone) works perfectly, also the internal microphone. As attempts to fix the problem, I have tried the following separately, with no avail: - Installing some Ubuntu OEM version of the 5.17 kernel - Updating to the v2.2 firmware from Sound Open Firmware Project (thesofproject on github), reverted afterwards I found exactly the same problem reported in the Fedora community: https://forums.fedoraforum.org/showthread.php?328627-HP-Elitebook-840-G8-Tiger-Lake-audio-only-produces-popping-sound&p=1860086 As the pre-installed Windows has been destroyed, no further test on Windows has been done. Since USB headphone and internal microphone work, I think that there is no problem on the Intel Tiger Lake-LP controller and its driver. The bug probably lies elsewhere, like in the handling of ALC245 on this new laptop model. Thank you very much for your time and effort in advance. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Jul 7 10:59:22 2022 InstallationDate: Installed on 2022-06-29 (7 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2022 dmi.bios.release: 9.1 dmi.bios.vendor: HP dmi.bios.version: T37 Ver. 01.09.01 dmi.board.name: 8AB8 dmi.board.vendor: HP dmi.board.version: KBC Version 58.03.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 88.3 dmi.modalias: dmi:bvnHP:bvrT37Ver.01.09.01:bd05/05/2022:br9.1:efr88.3:svnHP:pnHPEliteBook840G8NotebookPC:pvr:rvnHP:rn8AB8:rvrKBCVersion58.03.00:cvnHP:ct10:cvr:sku6A3P3AV: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 G8 Notebook PC dmi.product.sku: 6A3P3AV dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-07-02T17:07:35.783239 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1980937/+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 1993912] Re: GNOME screen recorder drops vast majority of frames
It looks like the fix for this was just prepared for jammy-proposed a couple of days ago: https://git.launchpad.net/ubuntu/+source/gnome- shell/commit/js/dbusServices/screencast/screencastService.js?h=applied/ubuntu/jammy- proposed&id=40715f8dfa77b9edd5a8fad033718df4d4d65440 I've tested this change locally and verified it resolves the issue: 1. $ mkdir -p ~/.gnome-shell-custom-overlays/Screencast 2. $ gresource extract /usr/share/gnome-shell/org.gnome.Shell.Screencast.src.gresource /org/gnome/Shell/Screencast/js/screencastService.js > ~/.gnome-shell-custom-overlays/Screencast/screencastService.js 3. Apply changes to screencastService.js from https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/d32c03488fcf6cdb0ca2e99b0ed6ade078460deb ) 4. Add the following to ~/.profile: export G_RESOURCE_OVERLAYS="/org/gnome/Shell/Screencast/js/screencastService.js=$HOME/.gnome-shell-custom-overlays/Screencast/screencastService.js" 5. Logout and login -- 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/1993912 Title: GNOME screen recorder drops vast majority of frames Status in gnome-shell package in Ubuntu: New Bug description: When I try to record a region on my screen, after about 4 seconds the frames stop updating. In the attached video, I am toggling between the two visible windows every half second, roughly. The only frame updates after 0:04 occur at 0:33, 1:07, and 1:40. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 12:13:30 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-01 (174 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993912/+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 1993912] Re: GNOME screen recorder drops vast majority of frames
I believe this is the same issue as reported here: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5585 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5585 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5585 -- 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/1993912 Title: GNOME screen recorder drops vast majority of frames Status in gnome-shell package in Ubuntu: New Bug description: When I try to record a region on my screen, after about 4 seconds the frames stop updating. In the attached video, I am toggling between the two visible windows every half second, roughly. The only frame updates after 0:04 occur at 0:33, 1:07, and 1:40. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 12:13:30 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-01 (174 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993912/+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 1993912] Re: GNOME screen recorder drops vast majority of frames
Additional testing: - My laptop (also with AMD graphics, Lenovo T14s Gen2) running the same OS also exhibits this issue. - Switching my session from wayland to XOrg does not remedy the problem. - Installing AMD drivers from https://www.amd.com/en/support/linux-drivers does not remedy the problem. ** Description changed: - I was trying to screen record for a different bug report, but I can't - seem to screen record properly and so find myself here reporting this - bug. When I try to record a region on my screen, after about 4 seconds - the frames stop updating. In the attached video, I am toggling between - the two visible windows every half second, roughly. The only frame - updates after 0:04 occur at 0:33, 1:07, and 1:40. + When I try to record a region on my screen, after about 4 seconds the + frames stop updating. In the attached video, I am toggling between the + two visible windows every half second, roughly. The only frame updates + after 0:04 occur at 0:33, 1:07, and 1:40. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 12:13:30 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-01 (174 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1993912 Title: GNOME screen recorder drops vast majority of frames Status in gnome-shell package in Ubuntu: New Bug description: When I try to record a region on my screen, after about 4 seconds the frames stop updating. In the attached video, I am toggling between the two visible windows every half second, roughly. The only frame updates after 0:04 occur at 0:33, 1:07, and 1:40. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 12:13:30 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-01 (174 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993912/+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 1992667] Re: Application windows invisible (on DG2 graphics)
Hi Timo, Upgrading to Mesa 22.2 seems to resolve this issue. Using the packages from the intel repository (https://dgpu-docs.intel.com/installation- guides/ubuntu/ubuntu-jammy-arc.html) works as well. Is it planned to release the updated mesa 22.2 packages to Ubuntu 22.04? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1992667 Title: Application windows invisible (on DG2 graphics) Status in linux-oem-6.0 package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Status in linux-oem-6.0 source package in Jammy: New Status in mesa source package in Jammy: New Bug description: When using GNOME Shell with Wayland, all application windows become invisible from time to time. This usually happens right after starting GNOME Shell for the first time or after having a VRAM intensive application open, such as a game. I have installed the latest linux-oem-6.0 kernel and manually enabled support for DG2 graphics by passing the i915.force_probe parameter with the PCIe ID of the graphics card. I have attached a screenshot of the described behavior below. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0 Uname: Linux 6.0.0-1005-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Oct 12 17:23:40 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-10-11 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1992667/+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 1982463] Re: cheese - webcam image frozen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cheese (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1982463 Title: cheese - webcam image frozen Status in cheese package in Ubuntu: Confirmed Bug description: Ubuntu 22.04LTS Related to bug: https://bugreports.qt.io/browse/QTBUG-105062 Not only cheese has this problem, also the "Camera" program of ubuntu has the same freeze problems. When I start cheese from the command line, it reports: >cheese (cheese:87986): cheese-WARNING **: 10:38:26.334: Er worden veel buffers gedropt.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. The image freezes and there's no camerastream. WebCamoid does not have these problems. cheese: Geïnstalleerd: 41.1-1build1 Kandidaat: 41.1-1build1 Versietabel: *** 41.1-1build1 500 500 http://nl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-25 (56 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Intel Corporation NUC6CAYH Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: jammy gstreamer-error Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2017 dmi.bios.release: 5.6 dmi.bios.vendor: Intel Corp. dmi.bios.version: AYAPLCEL.86A.0043.2017.1123.1559 dmi.board.name: NUC6CAYB dmi.board.vendor: Intel Corporation dmi.board.version: J23203-404 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2 dmi.ec.firmware.release: 20.0 dmi.modalias: dmi:bvnIntelCorp.:bvrAYAPLCEL.86A.0043.2017.1123.1559:bd11/23/2017:br5.6:efr20.0:svnIntelCorporation:pnNUC6CAYH:pvrJ26843-405:rvnIntelCorporation:rnNUC6CAYB:rvrJ23203-404:cvnIntelCorporation:ct3:cvr2:sku: dmi.product.family: Intel NUC dmi.product.name: NUC6CAYH dmi.product.version: J26843-405 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1982463/+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 1969422] Re: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object(
Just in time before updating to 22.10 :) I tested with mutter 42.5-0ubuntu1 and for me the problem seems to be fixed, i can finally work with multiple monitors again :) Thanks a lot! -- 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/1969422 Title: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object() Status in Mutter: Unknown Status in OEM Priority Project: Fix Committed Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Kinetic: Fix Released Bug description: [ Impact ] On dual-GPU systems, gnome-shell may crash in gbm_surface_release_buffer() during display config changes, like when rearranging monitor positions. [ Test Plan ] 1. Find a dual GPU system where both use open source drivers (like Intel + AMD). 2. Ideally also attach one monitor to each GPU. 3. Open Settings and repeatedly change the monitor layout pressing Apply each time. Expect: System does not crash. [ Where problems could occur ] Anywhere to do with screen updates since the entire triple buffering patch has been updated. [ Other Info ] The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/4fa0be3b67c650c621a425137efd7376c32451b4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1969422/+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 1981190] Re: Fibcom FM350-GL not able connect to network with 5G mode
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: modemmanager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1981190 Title: Fibcom FM350-GL not able connect to network with 5G mode Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: Confirmed Status in libqmi package in Ubuntu: Confirmed Status in modemmanager package in Ubuntu: Confirmed Bug description: Fibcom FM350-GL can support 5G network (https://www.fibocom.com/en/products/5G-FM350-GL.html). But in Ubuntu 22.04, system can only connect to mobile network with 4G mode. General | path: /org/freedesktop/ModemManager1/Modem/0 |device id: e045a43cd7977e24e1a11af409a780c054e26b0e Hardware | manufacturer: generic |model: MBIM [14C3:4D75] |firmware revision: 81600..00.29.18.01_GC | C01 | h/w revision: V1.0.6 |supported: gsm-umts, lte | current: gsm-umts, lte | equipment id: 352750140002001 System | device: /sys/devices/pci:00/:00:1c.0/:73:00.0 | drivers: mtk_t7xx | plugin: generic | primary port: wwan0mbim0 |ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim) Status | unlock retries: sim-pin (3), sim-pin2 (3) |state: connected | power state: on | access tech: lte | signal quality: 74% (recent) Modes|supported: allowed: 3g, 4g; preferred: none | current: allowed: 3g, 4g; preferred: none IP |supported: ipv4, ipv6, ipv4v6 3GPP | imei: 352750140002001 |enabled locks: sim, fixed-dialing | operator id: 46692 |operator name: Chunghwa Telecom | registration: home 3GPP EPS | ue mode of operation: csps-2 | initial bearer path: /org/freedesktop/ModemManager1/Bearer/0 SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0 Bearer |paths: /org/freedesktop/ModemManager1/Bearer/1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-15 (26 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) NonfreeKernelModules: nvidia_modeset nvidia Package: modemmanager 1.18.6-1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.17.0-9012.13+exp.27-oem 5.17.9 Tags: jammy Uname: Linux 5.17.0-9012-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1981190/+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 1981190] Re: Fibcom FM350-GL not able connect to network with 5G mode
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libqmi (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1981190 Title: Fibcom FM350-GL not able connect to network with 5G mode Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: Confirmed Status in libqmi package in Ubuntu: Confirmed Status in modemmanager package in Ubuntu: Confirmed Bug description: Fibcom FM350-GL can support 5G network (https://www.fibocom.com/en/products/5G-FM350-GL.html). But in Ubuntu 22.04, system can only connect to mobile network with 4G mode. General | path: /org/freedesktop/ModemManager1/Modem/0 |device id: e045a43cd7977e24e1a11af409a780c054e26b0e Hardware | manufacturer: generic |model: MBIM [14C3:4D75] |firmware revision: 81600..00.29.18.01_GC | C01 | h/w revision: V1.0.6 |supported: gsm-umts, lte | current: gsm-umts, lte | equipment id: 352750140002001 System | device: /sys/devices/pci:00/:00:1c.0/:73:00.0 | drivers: mtk_t7xx | plugin: generic | primary port: wwan0mbim0 |ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim) Status | unlock retries: sim-pin (3), sim-pin2 (3) |state: connected | power state: on | access tech: lte | signal quality: 74% (recent) Modes|supported: allowed: 3g, 4g; preferred: none | current: allowed: 3g, 4g; preferred: none IP |supported: ipv4, ipv6, ipv4v6 3GPP | imei: 352750140002001 |enabled locks: sim, fixed-dialing | operator id: 46692 |operator name: Chunghwa Telecom | registration: home 3GPP EPS | ue mode of operation: csps-2 | initial bearer path: /org/freedesktop/ModemManager1/Bearer/0 SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0 Bearer |paths: /org/freedesktop/ModemManager1/Bearer/1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-15 (26 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) NonfreeKernelModules: nvidia_modeset nvidia Package: modemmanager 1.18.6-1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.17.0-9012.13+exp.27-oem 5.17.9 Tags: jammy Uname: Linux 5.17.0-9012-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1981190/+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 1981190] Re: Fibcom FM350-GL not able connect to network with 5G mode
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libmbim (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1981190 Title: Fibcom FM350-GL not able connect to network with 5G mode Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: Confirmed Status in libqmi package in Ubuntu: Confirmed Status in modemmanager package in Ubuntu: Confirmed Bug description: Fibcom FM350-GL can support 5G network (https://www.fibocom.com/en/products/5G-FM350-GL.html). But in Ubuntu 22.04, system can only connect to mobile network with 4G mode. General | path: /org/freedesktop/ModemManager1/Modem/0 |device id: e045a43cd7977e24e1a11af409a780c054e26b0e Hardware | manufacturer: generic |model: MBIM [14C3:4D75] |firmware revision: 81600..00.29.18.01_GC | C01 | h/w revision: V1.0.6 |supported: gsm-umts, lte | current: gsm-umts, lte | equipment id: 352750140002001 System | device: /sys/devices/pci:00/:00:1c.0/:73:00.0 | drivers: mtk_t7xx | plugin: generic | primary port: wwan0mbim0 |ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim) Status | unlock retries: sim-pin (3), sim-pin2 (3) |state: connected | power state: on | access tech: lte | signal quality: 74% (recent) Modes|supported: allowed: 3g, 4g; preferred: none | current: allowed: 3g, 4g; preferred: none IP |supported: ipv4, ipv6, ipv4v6 3GPP | imei: 352750140002001 |enabled locks: sim, fixed-dialing | operator id: 46692 |operator name: Chunghwa Telecom | registration: home 3GPP EPS | ue mode of operation: csps-2 | initial bearer path: /org/freedesktop/ModemManager1/Bearer/0 SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0 Bearer |paths: /org/freedesktop/ModemManager1/Bearer/1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-15 (26 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) NonfreeKernelModules: nvidia_modeset nvidia Package: modemmanager 1.18.6-1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.17.0-9012.13+exp.27-oem 5.17.9 Tags: jammy Uname: Linux 5.17.0-9012-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1981190/+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 1993904] Re: key binding to launch gnome-control-center doesn't work
After upgrading to Ubuntu 22.10, I get the same error when using the hotkeys set in Keyboard Shortcuts -> Launchers -> Settings. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1993904 Title: key binding to launch gnome-control-center doesn't work Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: There's a default keybinding of XF86Tools to launch gnome-control- center. On my ThinkPad X390's keyboard it is Fn-F9. This keybinding no longer works in Ubuntu 22.10. Instead I see this error in my journal: spal. 22 20:27:34 blynas gsd-media-keys[3793]: Could not find application 'gnome-control-center.desktop' or '(null)' AFACT gnome-control-center 43 renamed the .desktop file to /usr/share/applications/org.gnome.Settings.desktop ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-settings-daemon 43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 20:29:29 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (1227 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1993904/+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 1993904] Re: key binding to launch gnome-control-center doesn't work
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1993904 Title: key binding to launch gnome-control-center doesn't work Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: There's a default keybinding of XF86Tools to launch gnome-control- center. On my ThinkPad X390's keyboard it is Fn-F9. This keybinding no longer works in Ubuntu 22.10. Instead I see this error in my journal: spal. 22 20:27:34 blynas gsd-media-keys[3793]: Could not find application 'gnome-control-center.desktop' or '(null)' AFACT gnome-control-center 43 renamed the .desktop file to /usr/share/applications/org.gnome.Settings.desktop ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-settings-daemon 43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 20:29:29 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (1227 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1993904/+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 1993928] Re: Switching to new input method does nothing
** Package changed: ibus (Ubuntu) => ibus-m17n (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-m17n in Ubuntu. https://bugs.launchpad.net/bugs/1993928 Title: Switching to new input method does nothing Status in ibus-m17n package in Ubuntu: New Bug description: I have ibus-m17n installed, but switching to a different input method does nothing. STR: 1. Make sure my 2nd input method (in my case, "Sanskrit (sa-IAST (m17n))" appears under "Settings-->Keyboard-->Input sources." 2. Use alt-space to switch to my second input method. 3. Notice on the top panel that the indicator shows that the input method has changed. 4. Attempt to key in some special characters (using Gedit, LibreOffice, etc.). Expected result: The special characters will appear. Actual result: The keyboard behaves as if the input method were my usual "English (US)." No such problem with 22.04. Removing and re-adding "Sanskrit (sa-IAST (m17n))" in Settings doesn't solve the issue. Hardware: IBM ThinkPad Carbon X-1, 5th generation. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: ibus 1.5.27-2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Oct 23 08:44:46 2022 InstallationDate: Installed on 2017-12-08 (1779 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ibus UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-m17n/+bug/1993928/+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 1420914] Re: secret-tool does not run on headless system
Hi I'm still having this issue on my ubuntu terminal secret-tool: No such interface “org.freedesktop.Secret.Collection” on object at path /org/freedesktop/secrets/collection/login -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsecret in Ubuntu. https://bugs.launchpad.net/bugs/1420914 Title: secret-tool does not run on headless system Status in libsecret package in Ubuntu: Confirmed Bug description: Description: Ubuntu 14.04 LTS Release: 14.04 libsecret-tools: Installed: 0.16-0ubuntu1 Candidate: 0.16-0ubuntu1 Version table: *** 0.16-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status I expected to be able to run secret-tool on a headless sytem, but got this message after running it. secret-tool store ... (secret-tool:26626): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed secret-tool: Cannot autolaunch D-Bus without X11 $DISPLAY # didn't expect thisto work, but thought I'd give it a try. export DISPLAY=:0 secret-tool store ... (secret-tool:26639): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed secret-tool: Error spawning command line 'dbus-launch --autolaunch=0feb8b37e7d1bdde6782aa3e537cfda6 --binary-syntax --close-stderr': Child process exited with code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsecret/+bug/1420914/+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 1993940] [NEW] applications start in the background instead of the foreground
Public bug reported: I frequently see new applications windows open in the background instead of the foreground, e.g., if I click on a link in an e-mail in Thunderbird, a new browser window will open and a notification at the top of the screen will let me know that the windows has been opened, but Thunderbird remains in the foreground and the new window opens in the background. I've been seeing this for a long time now, but I'd like to stop wrestling with the GUI shell to get to the application that I just started. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.7 ProcVersionSignature: Ubuntu 5.4.0-126.142~18.04.1-generic 5.4.203 Uname: Linux 5.4.0-126-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 23 11:52:17 2022 DisplayManager: gdm3 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-05-10 (1626 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2020-03-04 (963 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1993940 Title: applications start in the background instead of the foreground Status in gnome-shell package in Ubuntu: New Bug description: I frequently see new applications windows open in the background instead of the foreground, e.g., if I click on a link in an e-mail in Thunderbird, a new browser window will open and a notification at the top of the screen will let me know that the windows has been opened, but Thunderbird remains in the foreground and the new window opens in the background. I've been seeing this for a long time now, but I'd like to stop wrestling with the GUI shell to get to the application that I just started. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.7 ProcVersionSignature: Ubuntu 5.4.0-126.142~18.04.1-generic 5.4.203 Uname: Linux 5.4.0-126-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 23 11:52:17 2022 DisplayManager: gdm3 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-05-10 (1626 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2020-03-04 (963 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993940/+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 1993938] [NEW] language change doesn't work while renaming or creating new folder
Public bug reported: SHIFT+ALT is not working when while in the renaming state or creating a new folder ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 23 12:43:18 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.compression' b'default-compression-format' b"'encrypted_zip'" b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'initial-size' b'(873, 779)' InstallationDate: Installed on 2022-01-27 (268 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2022-02-07T09:04:41.555461 usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 nautilus-share0.7.5-0.1 python3-nautilus 4.0-1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1993938 Title: language change doesn't work while renaming or creating new folder Status in nautilus package in Ubuntu: New Bug description: SHIFT+ALT is not working when while in the renaming state or creating a new folder ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 23 12:43:18 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.compression' b'default-compression-format' b"'encrypted_zip'" b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'initial-size' b'(873, 779)' InstallationDate: Installed on 2022-01-27 (268 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2022-02-07T09:04:41.555461 usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 nautilus-share0.7.5-0.1 python3-nautilus 4.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1993938/+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 1993935] [NEW] Bluetooth issue
Public bug reported: Bluetooth is not connecting to any of my phone or headsets ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: bluez 5.65-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Oct 23 15:04:45 2022 InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 04f2:b628 Chicony Electronics Co., Ltd EasyCamera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81H7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=a1ad31f9-4430-4654-856d-9a144597827d ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/29/2020 dmi.bios.release: 1.26 dmi.bios.vendor: LENOVO dmi.bios.version: 8QCN26WW(V1.14) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 130-15IKB dmi.ec.firmware.release: 1.26 dmi.modalias: dmi:bvnLENOVO:bvr8QCN26WW(V1.14):bd12/29/2020:br1.26:efr1.26:svnLENOVO:pn81H7:pvrLenovoideapad130-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad130-15IKB:skuLENOVO_MT_81H7_BU_idea_FM_ideapad130-15IKB: dmi.product.family: ideapad 130-15IKB dmi.product.name: 81H7 dmi.product.sku: LENOVO_MT_81H7_BU_idea_FM_ideapad 130-15IKB dmi.product.version: Lenovo ideapad 130-15IKB dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: A8:6D:AA:B9:23:31 ACL MTU: 1021:5 SCO MTU: 96:6 DOWN RX bytes:1914 acl:9 sco:0 events:106 errors:0 TX bytes:1359 acl:10 sco:0 commands:83 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1993935 Title: Bluetooth issue Status in bluez package in Ubuntu: New Bug description: Bluetooth is not connecting to any of my phone or headsets ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: bluez 5.65-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Oct 23 15:04:45 2022 InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 04f2:b628 Chicony Electronics Co., Ltd EasyCamera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81H7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=a1ad31f9-4430-4654-856d-9a144597827d ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/29/2020 dmi.bios.release: 1.26 dmi.bios.vendor: LENOVO dmi.bios.version: 8QCN26WW(V1.14) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 130-15IKB dmi.ec.firmware.release: 1.26 dmi.modalias: dmi:bvnLENOVO:bvr8QCN26WW(V1.14):bd12/29/2020:br1.26:efr1.26:svnLENOVO:pn81H7:pvrLenovoideapad130-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad130-15IKB:skuLENOVO_MT_81H7_BU_idea_FM_ideapad130-15IKB: dmi.product.family: ideapad 130-15IKB dmi.product.name: 81H7 dmi.product.sku: LENOVO_MT_81H7_BU_idea_FM_ideapad 130-15IKB dmi.product.version: Lenovo ideapad 130-15IKB dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A8:6D:AA:B9:23:31 ACL MTU: 1021:5 SCO MTU: 96:6 DOWN RX bytes:1914 acl:9 sco:0 events:106 errors:0 TX bytes:1359 acl:10 sco:0 commands:83 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1993935/+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 1993933] [NEW] bluetooth is not connecting
Public bug reported: bluetooth is not connecting with any phone or earbuds ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: pulseaudio 1:16.1+dfsg1-1ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1869 F pipewire-media- /dev/snd/seq:ubuntu 1868 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Oct 23 14:53:18 2022 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/29/2020 dmi.bios.release: 1.26 dmi.bios.vendor: LENOVO dmi.bios.version: 8QCN26WW(V1.14) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 130-15IKB dmi.ec.firmware.release: 1.26 dmi.modalias: dmi:bvnLENOVO:bvr8QCN26WW(V1.14):bd12/29/2020:br1.26:efr1.26:svnLENOVO:pn81H7:pvrLenovoideapad130-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad130-15IKB:skuLENOVO_MT_81H7_BU_idea_FM_ideapad130-15IKB: dmi.product.family: ideapad 130-15IKB dmi.product.name: 81H7 dmi.product.sku: LENOVO_MT_81H7_BU_idea_FM_ideapad 130-15IKB dmi.product.version: Lenovo ideapad 130-15IKB dmi.sys.vendor: LENOVO ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1993933 Title: bluetooth is not connecting Status in pulseaudio package in Ubuntu: New Bug description: bluetooth is not connecting with any phone or earbuds ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: pulseaudio 1:16.1+dfsg1-1ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1869 F pipewire-media- /dev/snd/seq:ubuntu 1868 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Oct 23 14:53:18 2022 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/29/2020 dmi.bios.release: 1.26 dmi.bios.vendor: LENOVO dmi.bios.version: 8QCN26WW(V1.14) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 130-15IKB dmi.ec.firmware.release: 1.26 dmi.modalias: dmi:bvnLENOVO:bvr8QCN26WW(V1.14):bd12/29/2020:br1.26:efr1.26:svnLENOVO:pn81H7:pvrLenovoideapad130-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad130-15IKB:skuLENOVO_MT_81H7_BU_idea_FM_ideapad130-15IKB: dmi.product.family: ideapad 130-15IKB dmi.product.name: 81H7 dmi.product.sku: LENOVO_MT_81H7_BU_idea_FM_ideapad 130-15IKB dmi.product.version: Lenovo ideapad 130-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1993933/+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
