[Desktop-packages] [Bug 1908992] Re: SYNA30B4:00 06CB:CE09 Mouse on HP EliteBook 850 G7 not working at all
** Package changed: xserver-xorg-input-libinput (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1908992 Title: SYNA30B4:00 06CB:CE09 Mouse on HP EliteBook 850 G7 not working at all Status in linux package in Ubuntu: Confirmed Bug description: $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SYNA30B4:00 06CB:CE09 Mouse id=11 [slave pointer (2)] ⎜ ↳ SYNA30B4:00 06CB:CE09 Touchpad id=12 [slave pointer (2)] The touchpad is working fine, but the pointing stick/trackpoint does not work at all. No input is registered with xinput and libinput device tests. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-input-libinput 0.29.0-1 ProcVersionSignature: Ubuntu 5.8.0-33.36~20.04.1-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Dec 22 10:13:13 2020 DistUpgraded: 2020-12-22 07:48:08,643 DEBUG /openCache(), new cache size 70584 DistroCodename: focal DistroVariant: ubuntu InstallationDate: Installed on 2020-12-11 (10 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP EliteBook 850 G7 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/vgxubuntu-root ro quiet splash psmouse.proto=bare SourcePackage: xserver-xorg-input-libinput UpgradeStatus: Upgraded to focal on 2020-12-22 (0 days ago) dmi.bios.date: 08/24/2020 dmi.bios.release: 1.7 dmi.bios.vendor: HP dmi.bios.version: S73 Ver. 01.01.07 dmi.board.name: 8724 dmi.board.vendor: HP dmi.board.version: KBC Version 06.34.00 dmi.chassis.asset.tag: 5CG0471SRC dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 6.52 dmi.modalias: dmi:bvnHP:bvrS73Ver.01.01.07:bd08/24/2020:br1.7:efr6.52:svnHP:pnHPEliteBook850G7NotebookPC:pvr:rvnHP:rn8724:rvrKBCVersion06.34.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 850 G7 Notebook PC dmi.product.sku: 1J6F3EA#ABD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908992/+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 1810913] Re: xorg w. QXL driver crashes while using Intellij IDEA or PyCharm
also affects 20.04 as i tried once again after 2 years ... -- 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/1810913 Title: xorg w. QXL driver crashes while using Intellij IDEA or PyCharm Status in xorg-server package in Ubuntu: Confirmed Status in xserver-xorg-video-qxl package in Ubuntu: Confirmed Bug description: i try to have development VM on my home machine. everything is fine, i use spice/QXL and virt-manager and spice agent for resizing the desktop. surfing w. firefox is working fine and all the x apps i triad are ok. but shortly after starting IDEA or PyCharm X crashes the session. sometimes right after the splash screen. ALWAYS after i click "Open" and scrolling in the directory tree. to narrow down i tried several things: - using the same software version on a physical machine: works - using another graphics driver instead of QXL like cirrus etc: works - created a debian stretch vm with roughly the same software: crashes too so it seems QXL is to blame ... ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Tue Jan 8 10:07:19 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc QEMU Virtual Machine [1af4:1100] InstallationDate: Installed on 2018-12-16 (22 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=72ad7cdc-a16e-43db-93dc-52508a3d5cea ro quiet splash nomodeset vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.8 dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.8:cvnQEMU:ct1:cvrpc-i440fx-2.8: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.8 dmi.sys.vendor: QEMU version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1810913/+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 1909946] Re: Gnome Wayland session starts, then quits.
Regarding Item #3: Didn't know /var/crash existed, thanks for the heads up with the article too. I browsed /var/crash, there are quite a few files (18) from yesterday and today. Now none dated Jan 04 matched XWayland, however 2 from yesterday. The more recent ones (Jan 04) mention 'Blueman Applet' only. Do you want both? According to the article referenced, it seems to indicate using ubuntu-bug to run on the most recent files in /var/log/crash — were you meaning that I should do that in the future? Anywho, will touch base in the morning EST. -- 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/1909946 Title: Gnome Wayland session starts, then quits. Status in gnome-shell package in Ubuntu: Incomplete Bug description: So, this started about a week ago after an update from Ubuntu. I can initially login with XWayland, but something loading after the desktop appears, causes the session to exit. The only thing I can find relevant in the logs at the timestamp this occurred are the following: -gkr-pam: unable to locate daemon control file -Failed to start Process error reports when automatic reporting is enabled. -A start job for unit UNIT has failed I hope this helps track down the issue. Thanks for reading. BTW I have to submit this as a bug on something else, launchpad keeps telling me that XWayland doesn't exist. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xwayland 2:1.20.9-2ubuntu1.1 Uname: Linux 5.9.16-xanmod1 x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jan 3 19:33:28 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [148c:2356] InstallationDate: Installed on 2020-04-25 (253 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.9.16-xanmod1 root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1405 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:br5.14:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.103-1ubuntu1~g~mesarc0 version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.1+git2012290142.009e2aa5460~g~mesarc2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1909946/+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 1909946] Re: Gnome Wayland session starts, then quits.
Thanks Daniel, yes I meant a crash, just different wording. OK Attached is the file with all extensions disabled. If I'm reading the file correctly it seems to be a snap issue with an app not autostarting? Anyway lots of errors but when I scrolled down to the bottom showing the most recent boot up using XWayland, only two errors, relating to a snap launch. ** Attachment added: "journalctl log file" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1909946/+attachment/5449337/+files/prevboot.txt -- 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/1909946 Title: Gnome Wayland session starts, then quits. Status in gnome-shell package in Ubuntu: Incomplete Bug description: So, this started about a week ago after an update from Ubuntu. I can initially login with XWayland, but something loading after the desktop appears, causes the session to exit. The only thing I can find relevant in the logs at the timestamp this occurred are the following: -gkr-pam: unable to locate daemon control file -Failed to start Process error reports when automatic reporting is enabled. -A start job for unit UNIT has failed I hope this helps track down the issue. Thanks for reading. BTW I have to submit this as a bug on something else, launchpad keeps telling me that XWayland doesn't exist. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xwayland 2:1.20.9-2ubuntu1.1 Uname: Linux 5.9.16-xanmod1 x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jan 3 19:33:28 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [148c:2356] InstallationDate: Installed on 2020-04-25 (253 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.9.16-xanmod1 root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1405 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:br5.14:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.103-1ubuntu1~g~mesarc0 version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.1+git2012290142.009e2aa5460~g~mesarc2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1909946/+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 1902749] Re: [amdgpu] Log in screen flashes on and off until I log in
[Expired for mutter (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mutter (Ubuntu) Status: Incomplete => Expired -- 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/1902749 Title: [amdgpu] Log in screen flashes on and off until I log in Status in linux package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Bug description: Im on Ubuntu 20.04.1 with an AMD Ryzen 7 4800h CPU and a Nvidia GTX 1650ti [Mobile] GPU using nvidia-driver-450 Kernel is up to date (5.9.3) When my laptop boots, the log in screen flashes black and quickly back on until i log in. When i reach the desktop the flashing stops. Still, having the screen flickering on the log in screen is very annoying. As far as i can tell, the laptop doesn't have any further screen issues. Thanks in advance! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.9.3-050903-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Nov 3 17:46:21 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation TU116M [GeForce GTX 1650 Ti Mobile] [10de:2192] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Tongfang Hongkong Limited Device [1d05:1101] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c6) (prog-if 00 [VGA controller]) Subsystem: Tongfang Hongkong Limited Renoir [1d05:1100] InstallationDate: Installed on 2020-10-27 (7 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Standard GK5NPFO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.9.3-050903-generic root=UUID=a7144690-52e4-4688-a61a-b208b0648077 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.16PCS01 dmi.board.asset.tag: Standard dmi.board.name: GK5NPFO dmi.board.vendor: TongFang dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: Standard dmi.chassis.version: Standard dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.16PCS01:bd09/01/2020:br5.16:efr1.22:svnStandard:pnGK5NPFO:pvrStandard:rvnTongFang:rnGK5NPFO:rvrStandard:cvnStandard:ct10:cvrStandard: dmi.product.family: Standard dmi.product.name: GK5NPFO dmi.product.sku: 0001 dmi.product.version: Standard dmi.sys.vendor: Standard version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902749/+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 1902749] Re: [amdgpu] Log in screen flashes on and off until I log in
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1902749 Title: [amdgpu] Log in screen flashes on and off until I log in Status in linux package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Bug description: Im on Ubuntu 20.04.1 with an AMD Ryzen 7 4800h CPU and a Nvidia GTX 1650ti [Mobile] GPU using nvidia-driver-450 Kernel is up to date (5.9.3) When my laptop boots, the log in screen flashes black and quickly back on until i log in. When i reach the desktop the flashing stops. Still, having the screen flickering on the log in screen is very annoying. As far as i can tell, the laptop doesn't have any further screen issues. Thanks in advance! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.9.3-050903-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Nov 3 17:46:21 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation TU116M [GeForce GTX 1650 Ti Mobile] [10de:2192] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Tongfang Hongkong Limited Device [1d05:1101] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c6) (prog-if 00 [VGA controller]) Subsystem: Tongfang Hongkong Limited Renoir [1d05:1100] InstallationDate: Installed on 2020-10-27 (7 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Standard GK5NPFO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.9.3-050903-generic root=UUID=a7144690-52e4-4688-a61a-b208b0648077 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.16PCS01 dmi.board.asset.tag: Standard dmi.board.name: GK5NPFO dmi.board.vendor: TongFang dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: Standard dmi.chassis.version: Standard dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.16PCS01:bd09/01/2020:br5.16:efr1.22:svnStandard:pnGK5NPFO:pvrStandard:rvnTongFang:rnGK5NPFO:rvrStandard:cvnStandard:ct10:cvrStandard: dmi.product.family: Standard dmi.product.name: GK5NPFO dmi.product.sku: 0001 dmi.product.version: Standard dmi.sys.vendor: Standard version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902749/+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 1909496] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1909496 Title: Blinking login screen Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Bug description: Hello, I am facing this issue since the upgrade of Ubuntu to Ubuntu 20.04.1 LTS. The issue still persists even after re-installing Ubuntu 20.04.1 LTS. Due to inactivity the system goes to the Suspend mode. On restoring from the suspend mode the login screen appears but it starts to blink continuously making it impossible to use the system. The only option is to force restart the system. Please let me know if this is an already known issue/bug and if there is a solution available for the same. Thank You ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 28 19:21:12 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0793] InstallationDate: Installed on 2020-12-27 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Vostro 15-3568 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=44a1973f-ce3f-46bb-ab72-156c1d047556 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.08.00 dmi.board.name: 05HRPP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn05HRPP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0793 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909496/+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 1909496] Re: Blinking login screen
** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** 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 mutter in Ubuntu. https://bugs.launchpad.net/bugs/1909496 Title: Blinking login screen Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Hello, I am facing this issue since the upgrade of Ubuntu to Ubuntu 20.04.1 LTS. The issue still persists even after re-installing Ubuntu 20.04.1 LTS. Due to inactivity the system goes to the Suspend mode. On restoring from the suspend mode the login screen appears but it starts to blink continuously making it impossible to use the system. The only option is to force restart the system. Please let me know if this is an already known issue/bug and if there is a solution available for the same. Thank You ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 28 19:21:12 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0793] InstallationDate: Installed on 2020-12-27 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Vostro 15-3568 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=44a1973f-ce3f-46bb-ab72-156c1d047556 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.08.00 dmi.board.name: 05HRPP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn05HRPP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0793 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909496/+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 1910174] Re: nautilus is slow to start
logs in journalctl -b are like: ``` 1月 05 11:35:04 hy-sgao nautilus[1025336]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x5583f18c7120 1月 05 11:35:04 hy-sgao nautilus[1025336]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x5583f15688f0 1月 05 11:35:04 hy-sgao nautilus[1025336]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x5583f16c97c0 1月 05 11:35:04 hy-sgao nautilus[1025336]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x5583f1b5c9b0 1月 05 11:35:04 hy-sgao nautilus[1025336]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x5583f18e4fc0 1月 05 11:35:04 hy-sgao nautilus[1025336]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x5583f1b5c1f0 1月 05 11:35:04 hy-sgao nautilus[1025336]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x5583f1b52170 1月 05 11:35:04 hy-sgao nautilus[1025336]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x5583f15e2500 1月 05 11:35:04 hy-sgao nautilus[1025336]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x5583f1b49200 1月 05 11:35:04 hy-sgao nautilus[1025336]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x5583f1b5bde0 1月 05 11:35:04 hy-sgao nautilus[1025336]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x5583f1b5c590 1月 05 11:35:54 hy-sgao nautilus[1026060]: libnautilus-cloud-extension.so init 1月 05 11:35:54 hy-sgao nautilus[1026060]: thread_start [271]:bind successfull for path = '/home/sgao/.cloud-ipc-socket' 1月 05 11:35:54 hy-sgao nautilus[1026060]: thread_start [275]:running with sock 21. 1月 05 11:35:54 hy-sgao nautilus[1026060]: setDumpCacheReady [95]:Set dump cache as ready 1月 05 11:36:19 hy-sgao dbus-daemon[1028]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.2584' (uid=1001 pid=1026060 comm="nautilus " label="unconfined") 1月 05 11:37:25 hy-sgao dbus-daemon[1028]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.2587' (uid=1001 pid=1026060 comm="nautilus " label="unconfined") ``` -- 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/1910174 Title: nautilus is slow to start Status in nautilus package in Ubuntu: New Bug description: I don' t know the reason. My nautilus and gnome-tweak became slow to start. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jan 5 11:40:46 2021 InstallationDate: Installed on 2019-05-06 (610 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-11-25 (40 days ago) usr_lib_nautilus: synology-drive 6.0.2-11078 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1910174/+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 1909670] Re: Screen gets corrupted
*** This bug is a duplicate of bug 1896091 *** https://bugs.launchpad.net/bugs/1896091 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 1896091, 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) => linux (Ubuntu) ** This bug has been marked a duplicate of bug 1896091 [i915] Noise-like lines of graphics corruption when moving windows in Xorg sessions -- 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/1909670 Title: Screen gets corrupted Status in linux package in Ubuntu: New Bug description: There is a huge corruption in the screen. My laptop is lenovo- ideapad-330-151kb. Please fix. Thanking you. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 30 19:42:03 2020 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: rtl8821ce, 5.5.2.1, 5.8.0-31-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.8.0-33-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:3965] InstallationDate: Installed on 2020-11-21 (38 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 002: ID 0bc2:231a Seagate RSS LLC Expansion Portable Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:58ea Realtek Semiconductor Corp. EasyCamera Bus 001 Device 002: ID 0bda:c024 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81DE ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-33-generic root=UUID=0d397bc8-aadd-4e17-ba85-a15afd730cd8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2020 dmi.bios.release: 1.58 dmi.bios.vendor: LENOVO dmi.bios.version: 8TCN58WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55724 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnLENOVO:bvr8TCN58WW:bd06/18/2020:br1.58:efr1.7:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: dmi.product.family: ideapad 330-15IKB dmi.product.name: 81DE dmi.product.sku: LENOVO_MT_81DE_BU_idea_FM_ideapad 330-15IKB dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909670/+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 1910174] [NEW] nautilus is slow to start
Public bug reported: I don' t know the reason. My nautilus and gnome-tweak became slow to start. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jan 5 11:40:46 2021 InstallationDate: Installed on 2019-05-06 (610 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-11-25 (40 days ago) usr_lib_nautilus: synology-drive 6.0.2-11078 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1910174 Title: nautilus is slow to start Status in nautilus package in Ubuntu: New Bug description: I don' t know the reason. My nautilus and gnome-tweak became slow to start. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jan 5 11:40:46 2021 InstallationDate: Installed on 2019-05-06 (610 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-11-25 (40 days ago) usr_lib_nautilus: synology-drive 6.0.2-11078 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1910174/+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 1908167] Re: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic
Focal: the version 1:13.99.1-1ubuntu3.9 introduced a regression: after unplug the headphone, the speakers can't be auto selected. This issue is similar to https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1043 upstream has a fix for it: eaa6d5d6c1a7 (switch-on-port-available: Fix switching away from unplugged headphones), so as this fix does, I changed the 0703-switch-on-unknown.patch to move the code to port_available_hook_callback() in the ubuntu3.10. Please help upload ubuntu3.10 debdiff. Thanks. ** Patch added: "pulseaudio_13.99.1-1ubuntu3.10.debdiff" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908167/+attachment/5449308/+files/pulseaudio_13.99.1-1ubuntu3.10.debdiff -- 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/1908167 Title: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic Status in HWE Next: New Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Groovy: Fix Committed Status in pulseaudio source package in Hirsute: Fix Released Bug description: [Impact] On the Dell AIO machines, there is no internal mic, after plugging a headset, users expect the headset-mic or headphone-mic could be selected automatically. But with the current rule, the headset-mic/headphone-mic will not be selected automatically and even users manually select them, they will not show up in the gnome sound setting, and users could not record sound by headset-mic/headphone-mic. [Fix] backport a patch from pulseaudio mergerequest, the patch is going to be merged to pulseaudio 14.1. This patch could be backported to hirsute without any change, but need to be changed if backport it to groovy and focal. [Test] On those Dell AIO, plug a headset, open the gnome sound setting, the headset-mic is selected automatically, use the headset-mic to record the sound, the sound could be recorded and the sound quality is good. [Where problems could occur] This patch could change the policy of audio device switching, it will not affect all audio devices, but only the devices which has AVAIL_UNKNOWN available status, that means it has possibility to introduce the regression on headphone-mic ,headset-mic, internal mic and internal speaker's switching since they all has AVAIL_UNKNOWN status. For example, after unpluging the headset, the input device will not switch to internal mic automatically or after unplug the headphone, the output device will not switch to internal speaker automatically. But this possibility is very low, we have tested the patch on many Dell and Lenovo machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908167/+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 1908167] Re: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic
Groovy: the version 1:13.99.2-1ubuntu2.2 introduced a regression: after unplug the headphone, the speakers can't be auto selected. This issue is similar to https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1043 upstream has a fix for it: eaa6d5d6c1a7 (switch-on-port-available: Fix switching away from unplugged headphones), so as this fix does, I changed the 0703-switch-on-unknown.patch to move the code to port_available_hook_callback() in the ubuntu2.3. Please help upload ubuntu2.3 debdiff. Thanks.?field.comment=Groovy: the version 1:13.99.2-1ubuntu2.2 introduced a regression: after unplug the headphone, the speakers can't be auto selected. This issue is similar to https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1043 upstream has a fix for it: eaa6d5d6c1a7 (switch-on-port-available: Fix switching away from unplugged headphones), so as this fix does, I changed the 0703-switch-on-unknown.patch to move the code to port_available_hook_callback() in the ubuntu2.3. Please help upload ubuntu2.3 debdiff. Thanks. ** Patch added: "pulseaudio_13.99.2-1ubuntu2.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908167/+attachment/5449306/+files/pulseaudio_13.99.2-1ubuntu2.3.debdiff -- 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/1908167 Title: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic Status in HWE Next: New Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Groovy: Fix Committed Status in pulseaudio source package in Hirsute: Fix Released Bug description: [Impact] On the Dell AIO machines, there is no internal mic, after plugging a headset, users expect the headset-mic or headphone-mic could be selected automatically. But with the current rule, the headset-mic/headphone-mic will not be selected automatically and even users manually select them, they will not show up in the gnome sound setting, and users could not record sound by headset-mic/headphone-mic. [Fix] backport a patch from pulseaudio mergerequest, the patch is going to be merged to pulseaudio 14.1. This patch could be backported to hirsute without any change, but need to be changed if backport it to groovy and focal. [Test] On those Dell AIO, plug a headset, open the gnome sound setting, the headset-mic is selected automatically, use the headset-mic to record the sound, the sound could be recorded and the sound quality is good. [Where problems could occur] This patch could change the policy of audio device switching, it will not affect all audio devices, but only the devices which has AVAIL_UNKNOWN available status, that means it has possibility to introduce the regression on headphone-mic ,headset-mic, internal mic and internal speaker's switching since they all has AVAIL_UNKNOWN status. For example, after unpluging the headset, the input device will not switch to internal mic automatically or after unplug the headphone, the output device will not switch to internal speaker automatically. But this possibility is very low, we have tested the patch on many Dell and Lenovo machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908167/+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 1908167] Re: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic
Groovy: the version 1:13.99.2-1ubuntu2.2 introduced a regression: after unplug the headphone, the speakers can't be auto selected. This issue is similar to https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1043 upstream has a fix for it: eaa6d5d6c1a7 (switch-on-port-available: Fix switching away from unplugged headphones), so as this fix does, I changed the 0703-switch-on-unknown.patch to move the code to port_available_hook_callback() in the ubuntu2.3. Please help upload ubuntu2.3 debdiff. Thanks. ** Patch added: "pulseaudio_13.99.2-1ubuntu2.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908167/+attachment/5449307/+files/pulseaudio_13.99.2-1ubuntu2.3.debdiff -- 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/1908167 Title: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic Status in HWE Next: New Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Groovy: Fix Committed Status in pulseaudio source package in Hirsute: Fix Released Bug description: [Impact] On the Dell AIO machines, there is no internal mic, after plugging a headset, users expect the headset-mic or headphone-mic could be selected automatically. But with the current rule, the headset-mic/headphone-mic will not be selected automatically and even users manually select them, they will not show up in the gnome sound setting, and users could not record sound by headset-mic/headphone-mic. [Fix] backport a patch from pulseaudio mergerequest, the patch is going to be merged to pulseaudio 14.1. This patch could be backported to hirsute without any change, but need to be changed if backport it to groovy and focal. [Test] On those Dell AIO, plug a headset, open the gnome sound setting, the headset-mic is selected automatically, use the headset-mic to record the sound, the sound could be recorded and the sound quality is good. [Where problems could occur] This patch could change the policy of audio device switching, it will not affect all audio devices, but only the devices which has AVAIL_UNKNOWN available status, that means it has possibility to introduce the regression on headphone-mic ,headset-mic, internal mic and internal speaker's switching since they all has AVAIL_UNKNOWN status. For example, after unpluging the headset, the input device will not switch to internal mic automatically or after unplug the headphone, the output device will not switch to internal speaker automatically. But this possibility is very low, we have tested the patch on many Dell and Lenovo machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908167/+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 1909479] Re: Composed characteres are still not managed by gdm greeter
The greeter GUI is actually a gnome-shell process so reassigning. Also, please run this command to gather more system info: apport-collect 1909479 ** Package changed: gdm3 (Ubuntu) => gnome-shell (Ubuntu) -- 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/1909479 Title: Composed characteres are still not managed by gdm greeter Status in gnome-shell package in Ubuntu: New Bug description: Similary behaviour of this bug was report in #1716159 and #1765261, but still occured. Step to reproduce : - Login your Ubuntu 20.04 desktop session, - Modifi the user password with User Pannel Settings, - Select a User, - Change his password with a new one containing some composed char like "ë" or "ê" (composed by two keys for example "^" key + "e" key), - Validate. Now, the User is not abble to connect himself with gdm, because it never allow the user fills the composed characters (nothing appends) in the password field. The user can login by using command line with the new password. "password" cmd line produce same thing when use composed character, gdm is still not able to manage composed character. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1909479/+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 1866999] Re: gnome-calendar does not sync with Google Calendar
The same thing also happens with Flatpak version 3.38.2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1866999 Title: gnome-calendar does not sync with Google Calendar Status in gnome-calendar package in Ubuntu: Confirmed Bug description: Since upgrading to 20.04dev, gnome-calendar doesn't show the events in my Google Calendar. Online accounts is activated and, for example, gnome-contacts does show the contacts I have in Google. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-calendar 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 11 09:47:25 2020 InstallationDate: Installed on 2018-02-23 (746 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: gnome-calendar UpgradeStatus: Upgraded to focal on 2020-03-01 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1866999/+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 1733292] Re: Xorg crashed with SIGSEGV in point_on_screen from miPointerSetPosition from positionSprite from positionSprite from fill_pointer_events
** Description changed: + https://errors.ubuntu.com/problem/26998ca1a748ac33e8d1e0fe7d2bb9555465f34c + occasional screen locks up, the session ends, reverts to display manager (lightdm?), have to log in again. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 .tmp.unity_support_test.0: - + ApportVersion: 2.20.8-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Mon Nov 20 09:11:46 2017 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.0, 4.13.0-16-generic, x86_64: installed ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: - Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) -Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1028:05a4] + Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) + Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1028:05a4] InstallationDate: Installed on 2014-08-13 (1194 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140810) MachineType: Dell Inc. OptiPlex 9020 ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: - LANGUAGE=en_GB:en - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_GB.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_GB:en + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_GB.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=e2d4a833-d4fd-4295-95a5-57c52551e6ba ro splash vt.handoff=7 SegvAnalysis: - Segfault happened at: 0x56286fd4bad0:movswl 0x8(%rdi),%ecx - PC (0x56286fd4bad0) ok - source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed readable region)! - destination "%ecx" ok - Stack memory exhausted (SP below stack segment) + Segfault happened at: 0x56286fd4bad0:movswl 0x8(%rdi),%ecx + PC (0x56286fd4bad0) ok + source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed readable region)! + destination "%ecx" ok + Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: xorg-server StacktraceTop: - () - miPointerSetPosition () - () - () - GetPointerEvents () + () + miPointerSetPosition () + () + () + GetPointerEvents () Title: Xorg crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo dmi.bios.date: 05/23/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A20 dmi.board.name: 06X1TJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA20:bd05/23/2017:svnDellInc.:pnOptiPlex9020:pvr00:rvnDellInc.:rn06X1TJ:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 9020 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1 version.libdrm2: libdrm2 2.4.88-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Sep 12 12:13:51 2017 xserver.configfile: default xserver.errors: - /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied - /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied + /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied + /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu6 xserver.video_driver: modeset -- 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/1733292 Title: Xorg crashed with SIGSEGV in point_on_screen from miPointerSetPosition from positionSprite from positionSprite from fill_pointer_events Status in xorg-server package in Ubuntu: Confirmed Bug description:
[Desktop-packages] [Bug 1910168] Re: /usr/lib/xorg/Xorg:11:point_on_screen:miPointerSetPosition:positionSprite:positionSprite:fill_pointer_events
*** This bug is a duplicate of bug 1733292 *** https://bugs.launchpad.net/bugs/1733292 ** This bug has been marked a duplicate of bug 1733292 Xorg crashed with SIGSEGV in point_on_screen from miPointerSetPosition from positionSprite from positionSprite from fill_pointer_events -- 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/1910168 Title: /usr/lib/xorg/Xorg:11:point_on_screen:miPointerSetPosition:positionSprite:positionSprite:fill_pointer_events Status in xorg-server package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.9-2ubuntu1.1, the problem page at https://errors.ubuntu.com/problem/26998ca1a748ac33e8d1e0fe7d2bb9555465f34c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1910168/+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 1909387] Re: Xorg crash (libinput related) on middle mouse click with firefox icognito window
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Summary changed:
- Xorg crash (libinput related) on middle mouse click with firefox icognito
window
+ Xorg crashed with SEGV in miPointerMoveNoEvent from miPointerSetPosition from
positionSprite from positionSprite from fill_pointer_events
--
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/1909387
Title:
Xorg crashed with SEGV in miPointerMoveNoEvent from
miPointerSetPosition from positionSprite from positionSprite from
fill_pointer_events
Status in xorg-server package in Ubuntu:
New
Bug description:
What happens:
==
Xorg crashes, all unsaved data will be lost.
Reproduce
==
I can't reproduce it on demand. But it happens after a while.
- Usually I browse within a Firefox incognito window and use my middle mouse
button.
- In todays particular case, I pressed the middle mouse button to close a
window.
- Note: I have `EasyStroke` setup to run on middle-mouse-button click
(Program to enable mouse gestures). From experience, I strongly believe this is
related.
- Maybe `suspend`ing the computer several times is related to this problem.
Backtrace
==
Reading symbols from /usr/lib/xorg/Xorg...
Reading symbols from
/usr/lib/debug/.build-id/c0/8b99fc7191c25e710bd8e607615730e39962fe.debug...
[New LWP 1106]
[New LWP 1092]
[New LWP 1094]
[New LWP 1093]
[New LWP 1096]
[New LWP 978]
[New LWP 1097]
[New LWP 1098]
[New LWP 1095]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth
/var/run/lightdm/root/:0 -noliste'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 miPointerMoveNoEvent (pDev=pDev@entry=0x56198f5dc280,
pScreen=pScreen@entry=0x56198f0b2810, x=981, y=77)
at ../../../../mi/mipointer.c:570
570 ../../../../mi/mipointer.c: No such file or directory.
[Current thread is 1 (Thread 0x7fd057816640 (LWP 1106))]
(gdb) bt full
#0 miPointerMoveNoEvent (pDev=pDev@entry=0x56198f5dc280,
pScreen=pScreen@entry=0x56198f0b2810, x=981, y=77)
at ../../../../mi/mipointer.c:570
pPointer = 0x0
pScreenPriv = 0x56198f0b2eb0
#1 0x56198e979d2c in miPointerSetPosition
(pDev=pDev@entry=0x56198f5dc280, mode=mode@entry=0,
screenx=screenx@entry=0x7fd057814500, screeny=screeny@entry=0x7fd057814508,
nevents=nevents@entry=0x7fd0578144fc, events=events@entry=0x7fd069d6bc20)
at ../../../../mi/mipointer.c:669
pScreenPriv =
pScreen = 0x56198f0b2810
newScreen = 0x7fd0004d
x = 981
y = 77
switch_screen = 0
should_constrain_barriers = 1
i =
pPointer = 0x56198f2249a0
#2 0x56198e840e90 in positionSprite
(dev=dev@entry=0x56198f5dc280, mode=mode@entry=0,
mask=mask@entry=0x7fd057814550, devx=devx@entry=0x7fd057814510,
devy=devy@entry=0x7fd057814518, screenx=screenx@entry=0x7fd057814500,
screeny=0x7fd057814508, nevents=0x7fd0578144fc, events=0x7fd069d6bc20) at
../../../../dix/getevents.c:961
scr =
tmpx = 981.15761067398421
tmpy = 77.59964237213
#3 0x56198e84141c in positionSprite
(events=0x7fd069d6bc20, nevents=0x7fd0578144fc, screeny=0x7fd057814508,
screenx=0x7fd057814500, devy=0x7fd057814518, devx=0x7fd057814510,
mask=0x7fd057814550, mode=0, dev=0x56198f5dc280) at
../../../../dix/getevents.c:952
scr = 0x56198f0b2810
num_events = 2
event =
raw = 0x7fd069d6b010
screenx = 981.15761067398421
screeny = 77.59964237213
devx = 981.15761067398421
devy = 77.59964237213
sx =
sy = 0
mask =
{last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask =
"\003\000\000\000", valuators = {981.15761067398421, 77.59964237213, 0
}, unaccelerated = {0 }}
scr =
--Type for more, q to quit, c to continue without paging--
num_barrier_events = 0
#4 fill_pointer_events (events=0x7fd069d6bc20,
events@entry=0x7fd069d6b010, pDev=pDev@entry=0x56198f5dc280, type=6,
buttons=buttons@entry=0, ms=ms@entry=60064638, flags=flags@entry=10,
mask_in=0x7fd057814860) at ../../../../dix/getevents.c:1434
num_events = 2
event =
raw = 0x7fd069d6b010
screenx = 981.15761067398421
screeny = 77.59964237213
devx = 981.15761067398421
devy = 77.59964237213
sx =
sy = 0
mask =
{last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask =
"\003\000\000\000", valuators = {981.15761067398421, 77.59964237213, 0
}, unaccelerated = {0 }}
scr =
[Desktop-packages] [Bug 1910168] [NEW] /usr/lib/xorg/Xorg:11:point_on_screen:miPointerSetPosition:positionSprite:positionSprite:fill_pointer_events
*** This bug is a duplicate of bug 1733292 *** https://bugs.launchpad.net/bugs/1733292 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.9-2ubuntu1.1, the problem page at https://errors.ubuntu.com/problem/26998ca1a748ac33e8d1e0fe7d2bb9555465f34c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic cosmic disco eoan focal groovy zesty -- 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/1910168 Title: /usr/lib/xorg/Xorg:11:point_on_screen:miPointerSetPosition:positionSprite:positionSprite:fill_pointer_events Status in xorg-server package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.9-2ubuntu1.1, the problem page at https://errors.ubuntu.com/problem/26998ca1a748ac33e8d1e0fe7d2bb9555465f34c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1910168/+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 1909946] Re: Gnome Wayland session starts, then quits.
Sessions generally can't quit themselves so this is probably a crash. Please: 1. Uninstall any gnome-shell extensions you might have added, because extensions are the most common cause of bugs. 2. Next time the problem happens, reboot immediately and then run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. 3. Check for crashes using these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Summary changed: - XWayland session starts, then quits. + Gnome Wayland session starts, then quits. ** Package changed: xorg-server (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 xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1909946 Title: Gnome Wayland session starts, then quits. Status in gnome-shell package in Ubuntu: Incomplete Bug description: So, this started about a week ago after an update from Ubuntu. I can initially login with XWayland, but something loading after the desktop appears, causes the session to exit. The only thing I can find relevant in the logs at the timestamp this occurred are the following: -gkr-pam: unable to locate daemon control file -Failed to start Process error reports when automatic reporting is enabled. -A start job for unit UNIT has failed I hope this helps track down the issue. Thanks for reading. BTW I have to submit this as a bug on something else, launchpad keeps telling me that XWayland doesn't exist. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xwayland 2:1.20.9-2ubuntu1.1 Uname: Linux 5.9.16-xanmod1 x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jan 3 19:33:28 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [148c:2356] InstallationDate: Installed on 2020-04-25 (253 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.9.16-xanmod1 root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1405 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:br5.14:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.103-1ubuntu1~g~mesarc0 version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.1+git2012290142.009e2aa5460~g~mesarc2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1909946/+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 1866999] Re: gnome-calendar does not sync with Google Calendar
Same here. Using the apt-installed version (3.36.2). It seems to connect intermittently. Some days it works fine, other days, it doesn't even acknowledge that any of my Google calendars exist, with nothing in the calendar menu and Manage Calendars window except the default locally- stored file. The other day, it was blank. I left it sitting there for a few minutes and suddenly my Google calendars appeared. Yesterday, it was showing the Google calendars all day without problems. Today, it was blank again. I left it sitting for quite a while, and it's still blank. So it's really very random. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1866999 Title: gnome-calendar does not sync with Google Calendar Status in gnome-calendar package in Ubuntu: Confirmed Bug description: Since upgrading to 20.04dev, gnome-calendar doesn't show the events in my Google Calendar. Online accounts is activated and, for example, gnome-contacts does show the contacts I have in Google. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-calendar 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 11 09:47:25 2020 InstallationDate: Installed on 2018-02-23 (746 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: gnome-calendar UpgradeStatus: Upgraded to focal on 2020-03-01 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1866999/+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 1909791] Re: Pulseaudio profiles not available (analouge stereo) so no sound
*** This bug is a duplicate of bug 1897965 *** https://bugs.launchpad.net/bugs/1897965 This is probably another case of bug 1897965 so please check out the suggestions there. ** This bug has been marked a duplicate of bug 1897965 PulseAudio doesn't work when pipewire is installed (ie. KDE) -- 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/1909791 Title: Pulseaudio profiles not available (analouge stereo) so no sound Status in pulseaudio package in Ubuntu: New Bug description: regression-update bug 1876065 I am running Pulseaudio version 1:13.99.2-1Ubuntu2.1 which I assume is a newer release than 1:13.99.1-1ubuntu3.3 as described in bug 1876065. I am trying to use and set analogue stereo sound as my default sound. On each boot Pulse reverts to these available profiles (extract only, full text as attachment) pacmd list-cards name: ... profiles: input:analog-stereo: Analogue Stereo Input (priority 65, available: no) output:iec958-stereo: Digital Stereo (IEC958) Output (priority 5500, available: unknown) output:iec958-stereo+input:analog-stereo: Digital Stereo (IEC958) Output + Analogue Stereo Input (priority 5565, available: no) off: Off (priority 0, available: unknown) active profile: ... After deleting the files in ~/.config/Pulse and entering: pulseaudio -k, the output changes to: pacmd list-cards name: ... profiles: input:analog-stereo: Analogue Stereo Input (priority 65, available: no) output:analog-stereo: Analogue Stereo Output (priority 6500, available: unknown) output:analog-stereo+input:analog-stereo: Analogue Stereo Duplex (priority 6565, available: no) output:iec958-stereo: Digital Stereo (IEC958) Output (priority 5500, available: unknown) output:iec958-stereo+input:analog-stereo: Digital Stereo (IEC958) Output + Analogue Stereo Input (priority 5565, available: no) off: Off (priority 0, available: unknown) active profile: ... Having discovered the correct sink and profile one would proceed to make them the default by adding these 2 lines to /etc/pulse/default.pa: 1/ set-default-sink alsa_output.pci-_09_00.3.analog-stereo 2/ set-card-profile alsa_card.pci-_09_00.3 output:analog-stereo: Analogue Stereo Output, or, set-card-profile alsa_card.pci-_09_00.3 output:analog-stereo+input:analog-stereo: Analogue Stereo Duplex Setting the default sink (1) causes no problems but only allows selection of iec958 stereo but attempting to set the default profile (2) and rebooting and opening PulseAudio Volume Control leads to a pop-up window displaying: establishing connection to PulseAudio please wait... In other words PulseAudio is not running. So in summary I can get sound by buggering around each boot but cannot fix the issue on a permanent basis. This PC was release upgraded to 20.10 yesterday. This is the 3rd PC in the last several months I have had to spend significant time to get sound working, the others I found a permanent work-around for. All are fairly new, the other PCs are running a Ryzon 3000 and 5000 series CPU and Kubuntu 20.04 and 20.10. Having sound is something that should work out of the box. Operating System: Kubuntu 20.10 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 Kernel Version: 5.8.0-33-generic OS Type: 64-bit Processors: 12 × AMD Ryzen 5 2600X Six-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: GeForce GTX 1080/PCIe/SSE2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1909791/+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 1909877] Re: Clock in top bar doesn't update
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2973 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2973 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2973 Importance: Unknown Status: Unknown ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: New => Fix Released ** Tags added: fixed-in-3.38.2 fixed-upstream ** Also affects: mutter (Ubuntu Hirsute) Importance: Undecided Status: Fix Released ** Also affects: mutter (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Groovy) Status: New => Fix Committed -- 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/1909877 Title: Clock in top bar doesn't update Status in GNOME Shell: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Groovy: Fix Committed Status in mutter source package in Hirsute: Fix Released Bug description: When exiting fullscreen from chromium (YouTube), the clock widget in the top bar seems stuck and only updates after being updated from the mouse hovering over it. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.45.01 Thu Nov 5 23:03:56 UTC 2020 GCC version: gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1) ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 2 21:56:27 2021 DistUpgraded: 2020-12-27 18:29:34,023 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 455.45.01, 5.4.0-58-generic, x86_64: installed nvidia, 455.45.01, 5.8.0-33-generic, x86_64: installed virtualbox, 6.1.14, 5.4.0-58-generic, x86_64: installed virtualbox, 6.1.14, 5.8.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics 630 (Mobile) [1025:1264] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Ti Mobile] [1025:1265] InstallationDate: Installed on 2020-12-11 (22 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Acer Nitro AN515-52 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-33-generic root=UUID=8753fbc2-cbcd-41b4-ad44-9e1a6f940ddf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2020-12-27 (6 days ago) dmi.bios.date: 08/05/2019 dmi.bios.release: 1.28 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.28 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Freed_CFS dmi.board.vendor: CFL dmi.board.version: V1.28 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.28 dmi.ec.firmware.release: 1.26 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.28:bd08/05/2019:br1.28:efr1.26:svnAcer:pnNitroAN515-52:pvrV1.28:rvnCFL:rnFreed_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28: dmi.product.family: Acer Nitro 5 dmi.product.name: Nitro AN515-52 dmi.product.sku: dmi.product.version: V1.28 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.1-1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel
[Desktop-packages] [Bug 1910140] Re: Alignment of password field in 20.04 login screen not in centre
Please try uninstalling: apps-menu@gnome-shell- extensions.gcampax.github.com If that doesn't resolve the problem then next please attach a photo of it happening. ** 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/1910140 Title: Alignment of password field in 20.04 login screen not in centre Status in gnome-shell package in Ubuntu: Incomplete Bug description: ubuntu is now launching slowly for me it gives me a black screen at launch that shows the result of a system file check then it jumps to the login screen which seems strange as the alignment of the password field appears now on the left of the screen instead of in the centre as it used to be then ubuntu desktop starts, the screen seems to be shifting or 3 seconds then it adjusts itself to normal what should I reinstall to fix this please ? thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 4 19:35:37 2021 DisplayManager: lightdm InstallationDate: Installed on 2021-01-01 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 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/1910140/+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 1908559] Re: Steam or discord: "pushModal: invocation of begin_modal failed"
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid -- 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/1908559 Title: Steam or discord: "pushModal: invocation of begin_modal failed" Status in gnome-shell package in Ubuntu: Invalid Bug description: Roughly every 10 minutes two entries of the heading is printed to the logs ``` $ journalctl -b | grep "pushModal: invocation of begin_modal failed" des. 17 19:38:53 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:45:15 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:45:18 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:54:00 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:54:02 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 20:03:34 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 20:03:37 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed ``` I'm suspecting this is caused by either the discord snap, or steam missing some kind of permission ``` ps -ef | grep 8626 centx 86268293 3 19:18 ?00:01:38 /usr/bin/gnome-shell centx 86928626 0 19:18 ?00:00:00 ibus-daemon --panel disable --xim centx 184538626 0 19:39 ?00:00:13 /snap/discord/119/usr/share/discord/Discord --no-sandbox centx 192378626 0 19:41 ?00:00:00 /bin/sh -e /usr/games/steam ``` --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2018-12-30 (718 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: gnome-shell 3.38.1-1ubuntu1.1 PackageArchitecture: amd64 RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 Tags: third-party-packages groovy Uname: Linux 5.9.12-050912-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-12-12 (5 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1908559/+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 1910135] Re: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 5530 (aptd)
Thank you for taking the time to report this bug and helping to make Ubuntu better. A Support site maybe more appropriate, eg. https://answers.launchpad.net/ubuntu (this bug report can be changed into a question) . You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org , or for more support options please look at https://discourse.ubuntu.com/t /community-support/709 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1910135 Title: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 5530 (aptd) Status in ibus package in Ubuntu: Invalid Bug description: 04/0833 Error report when att apply update: “E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 5530 (aptd) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? E: _cache->open() failed, please report. W: Be aware that removing the lock file is not a solution and may break your system.”04/0833 Error report when att apply update: “E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 5530 (aptd) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? E: _cache->open() failed, please report. W: Be aware that removing the lock file is not a solution and may break your system.”04/0833 Error report when att apply update: “E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 5530 (aptd) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? E: _cache->open() failed, please report. W: Be aware that removing the lock file is not a solution and may break your system.” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1910135/+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 1910158] [NEW] Macbook Air trackpad stops tracking when finger contact area increases moderately
Public bug reported: I don't know if this has to do with libinput, I'm just guessing. When using a 2012 Macbook Air the trackpad regularly stops tracking individual finger movements during use (the cursor stops responding to movement). Once I lift my finger and once again touch the trackpad it starts working again, so the symptoms are isolated to a single uninterrupted touch. Needless to say it is very disruptive to whatever you're doing at the time. This occurred seemingly randomly until today when I could deteremine that I only have to tilt my finger towards me to create a larger area of contact with the trackpad in order to make it stop tracking. This also explains why it often appeared to happen right after a click, where I'm using extra force on the trackpad in order to activate the physical switch. The tolerances are apparently much too low, making me lose control of the mouse cursor extremely often (compared to Windows and macOS, where it basically never happens). A gradual increase of the contact area should not result in a complete failure to continue tracking, especially after the touch has long since been identified as a single finger. Ubuntu 20.10, Wayland ** Affects: libinput (Ubuntu) Importance: Undecided Status: New ** Description changed: I don't know if this has to do with libinput, I'm just guessing. When using a 2012 Macbook Air the trackpad regularly stops tracking individual finger movements during use (the cursor stops responding to movement). Once I lift my finger and once again touch the trackpad it starts working again, so the symptoms are isolated to a single uninterrupted touch. Needless to say it is very disruptive to whatever you're doing at the time. This occurred seemingly randomly until today when I could deteremine that I only have to tilt my finger towards me to create a larger area of contact with the trackpad in order to make it stop tracking. This also explains why it often appeared to happen right after a click, where I'm using extra force on the trackpad in order to activate the physical switch. The tolerances are apparently much too low, making me lose control of the mouse cursor extremely often (compared to Windows and macOS, where it basically never happens). A gradual increase of the contact area should not result in a complete failure to continue tracking, especially after the touch has long since been identified as a single finger. + + Ubuntu 20.10, Wayland -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1910158 Title: Macbook Air trackpad stops tracking when finger contact area increases moderately Status in libinput package in Ubuntu: New Bug description: I don't know if this has to do with libinput, I'm just guessing. When using a 2012 Macbook Air the trackpad regularly stops tracking individual finger movements during use (the cursor stops responding to movement). Once I lift my finger and once again touch the trackpad it starts working again, so the symptoms are isolated to a single uninterrupted touch. Needless to say it is very disruptive to whatever you're doing at the time. This occurred seemingly randomly until today when I could deteremine that I only have to tilt my finger towards me to create a larger area of contact with the trackpad in order to make it stop tracking. This also explains why it often appeared to happen right after a click, where I'm using extra force on the trackpad in order to activate the physical switch. The tolerances are apparently much too low, making me lose control of the mouse cursor extremely often (compared to Windows and macOS, where it basically never happens). A gradual increase of the contact area should not result in a complete failure to continue tracking, especially after the touch has long since been identified as a single finger. Ubuntu 20.10, Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1910158/+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 1895199] Re: web apps no longer launch into separate windows
I tried to link this bug to https://bugs.chromium.org/p/chromium/issues/detail?id=1125020 and Launchpad complained it does not recognize the bug tracker. Weird! -- 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/1895199 Title: web apps no longer launch into separate windows Status in chromium-browser package in Ubuntu: New Bug description: Chromium-browser updated on my system yesterday and today I noticed that unlike the previous version (84.0.4147.105-0ubuntu0.18.04.1) when I click my "favorite" shortcuts for Google Messages, Google Contacts, Google Calendar, and a website for a local radio station, the "app" shortcuts no longer create separate independent windows, but instead open a new tab in a Chromium browser window. Strangely enough, the web app shortcut for GMail still opens correctly in a separate browser window. As I mentioned, this seems to be a regression from version 84.0.4147.105-0ubuntu0.18.04.1 which got installed on my system yesterday. I am concerned because broken webapps is one of several features I will miss when I must upgrade this system from bionic. (I have another system running 20.04 and of course the snap version of Chromium does not do web apps reliably nor does the snap version work with the KeePassXC plugin.) Just in case this is just an incompatibility with existing shortcuts, I just created a NEW shortcut for the radio station web site and the new shortcut exhibits the same behavior. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser 85.0.4183.83-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 10 14:10:26 2020 DetectedPlugins: InstallationDate: Installed on 2020-04-07 (156 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1895199/+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 1895199] Re: web apps no longer launch into separate windows
I believe I found the relevant Chromium bug! https://bugs.chromium.org/p/chromium/issues/detail?id=1125020 On a different system I have been trying to fix my webapps (I have not found a way to make webapps open in separate taskbar icons in Ubuntu Groovy), and was digging through Chromium bug reports. I went to chrome://flags/ and found chrome://flags/#enable-desktop-pwas-migration-user-display-mode-clean-up which specifically mentions https://crbug.com/1125020 which resolves to the link at the top. This sounds similar to what I was experiencing that broke the windowing of webapps after a software upgrade, and it's also just about the right timeframe. I'm not on the same system and may not be able to test that one but I turned on the flag and fortunately it didn't break anything. Unfortunately it hasn't fixed my other bug. -- 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/1895199 Title: web apps no longer launch into separate windows Status in chromium-browser package in Ubuntu: New Bug description: Chromium-browser updated on my system yesterday and today I noticed that unlike the previous version (84.0.4147.105-0ubuntu0.18.04.1) when I click my "favorite" shortcuts for Google Messages, Google Contacts, Google Calendar, and a website for a local radio station, the "app" shortcuts no longer create separate independent windows, but instead open a new tab in a Chromium browser window. Strangely enough, the web app shortcut for GMail still opens correctly in a separate browser window. As I mentioned, this seems to be a regression from version 84.0.4147.105-0ubuntu0.18.04.1 which got installed on my system yesterday. I am concerned because broken webapps is one of several features I will miss when I must upgrade this system from bionic. (I have another system running 20.04 and of course the snap version of Chromium does not do web apps reliably nor does the snap version work with the KeePassXC plugin.) Just in case this is just an incompatibility with existing shortcuts, I just created a NEW shortcut for the radio station web site and the new shortcut exhibits the same behavior. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser 85.0.4183.83-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 10 14:10:26 2020 DetectedPlugins: InstallationDate: Installed on 2020-04-07 (156 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1895199/+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 1908915] Re: package chromium-browser 1:85.0.4183.83-0ubuntu2 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit sta
** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => hormoz hatamiyan (hormoz) -- 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/1908915 Title: package chromium-browser 1:85.0.4183.83-0ubuntu2 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 10 Status in chromium-browser package in Ubuntu: New Bug description: Errors were encountered while processing: /var/cache/apt/archives/chromium-browser_1%3a85.0.4183.83-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.10 Package: chromium-browser 1:85.0.4183.83-0ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 AptOrdering: chromium-browser:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Dec 21 19:13:28 2020 Dependencies: ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 10 Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.1 SourcePackage: chromium-browser Title: package chromium-browser 1:85.0.4183.83-0ubuntu2 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1908915/+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 768211] Re: chromium-browser fails to import bookmarks from firefox
** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Fix Released -- 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/768211 Title: chromium-browser fails to import bookmarks from firefox Status in chromium-browser package in Ubuntu: Fix Released Bug description: Binary package hint: chromium-browser chromium 10.0.648.205 (81283) on Ubuntu 11.04 beta 2 does not import bookmarks properly from firefox. After deleting ~/.config/chromium and starting chromium, I was offered to import the bookmarks, saved passwords etc... from firefox. I selected a few options and launched the import process. The bookmarks were not imported, even though the rest was. Now every time chromium is restarted it offers to import the bookmarks, but always fails to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/768211/+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 1909884] Re: tracker-extract crashes with SIGSYS when adding pdf to filesystem
** Also affects: tracker-miners (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker-miners in Ubuntu. https://bugs.launchpad.net/bugs/1909884 Title: tracker-extract crashes with SIGSYS when adding pdf to filesystem Status in linux-raspi package in Ubuntu: New Status in tracker-miners package in Ubuntu: New Bug description: Almost daily, _usr_libexec_tracker-extract.1000.crash shows up in /var/crash. I'm using Raspberry Pi 4B 8GB with Ubuntu 20.10 Desktop and lxqt as Desktop. uname -a: Linux myRaspi 5.8.0-1010-raspi #13-Ubuntu SMP PREEMPT Wed Dec 9 17:14:07 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux I saw in a previous backtrace that a pdf was the problem. So i downloaded some pdf with firefox to /home/username/Documents. In my case it was https://www.who.int/ceh/capacity/sanitation_hygiene.pdf After doing that, a crash-report was dumped by apport to /var/crash. A backtrace and full backtrace is in the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1909884/+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 1174162] Re: chrome-browser makes gnome-keyring-daemon use 100% cpu
** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Fix Released ** Changed in: gnome-keyring (Ubuntu) Status: Confirmed => Fix Released -- 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/1174162 Title: chrome-browser makes gnome-keyring-daemon use 100% cpu Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Fix Released Status in gnome-keyring package in Ubuntu: Fix Released Bug description: After upgrading to 13.04, when starting the chromium browser, the gnome-keyring-daemon runs at full CPU load and the chromium-browser has no access to the stored passwords. The issue seems to be known (https://code.google.com/p/chromium/issues/detail?id=98601). I'm personally a bit surprised that Ubuntu 13.04 was released with such a serious problem. The frequently proposed workaround (e.g. https://plus.google.com/110130355317073712944/posts/PckhFj5HUn4) doesn't work because (a) there is no .gnome2/keyrings any more and (b) it's rather inresponsible to store your passwords unencryted. I found that killing gnome-keyring-server several times eventually gives you a working system. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mnl 18759 F pulseaudio CRDA: country DE: (2400 - 2483 @ 40), (N/A, 20) (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS (5470 - 5725 @ 40), (N/A, 26), DFS DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=86292e17-edd2-4a1b-8e1b-5208a1731140 InstallationDate: Installed on 2010-11-10 (900 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: Hewlett-Packard HP Compaq 6730b (GB990EA#ABD) MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=cff10fb4-08a2-459b-be12-80698b20d2d3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-19-generic i686 UpgradeStatus: Upgraded to raring on 2013-04-28 (0 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare voice wireshark WifiSyslog: Apr 29 07:28:34 lipp-nb wpa_supplicant[1803]: wlan0: WPA: Group rekeying completed with c0:25:06:24:93:e1 [GTK=CCMP] dmi.bios.date: 12/07/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PDD Ver. F.20 dmi.board.name: 30DD dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 96.23 dmi.chassis.asset.tag: CNU9326SJY dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PDDVer.F.20:bd12/07/2011:svnHewlett-Packard:pnHPCompaq6730b(GB990EA#ABD):pvrF.20:rvnHewlett-Packard:rn30DD:rvrKBCVersion96.23:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq 6730b (GB990EA#ABD) dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1174162/+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 1902952] Re: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1
** Changed in: chromium-browser (Ubuntu) Status: Expired => Fix Released ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => hormoz hatamiyan (hormoz) -- 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/1902952 Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 Status in chromium-browser package in Ubuntu: Fix Released Bug description: This is the third time. ProblemType: Package DistroRelease: Ubuntu 20.10 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 5.8.0-1006.9-raspi 5.8.14 Uname: Linux 5.8.0-1006-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50 AptOrdering: chromium-browser:arm64: Install chromium-browser-l10n:arm64: Install NULL: ConfigurePending Architecture: arm64 CasperMD5CheckResult: skip Date: Wed Nov 4 09:42:36 2020 ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 ImageMediaBuild: 20201022 Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10 SourcePackage: chromium-browser Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser 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/chromium-browser/+bug/1902952/+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 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs
The bug is appear after resuming PC from the suspend when VLC was paused. I love VLC and don't want to switch to other player, so the workaround is simply to kill VLC after resume. I created systemd service for that and now it's fine Look at the gist https://gist.github.com/Red-Eyed/0fdaae7876254dccf4396f33aa1a8875 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1846374 Title: Having a video playing/paused when switched to another user generates gigabytes of error logs Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: To replicate: 1. Start a video playing, for example in vlc. 'avcodec decoder: Using NVIDIA VDPAU Driver Shared Library 418.56 Fri Mar 15 12:31:51 CDT 2019 for hardware decoding' 2. Optionally pause it. 3. Switch to another user. The original user's ~/.xsession-errors will rapidly fill up with errors along the lines of "vdpau_chroma filter error". At the same time, errors are put in /var/log/syslog as well: [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: An invalid handle value was provided. (repeat ad nauseum) At least one of the two will rapidly fill up its partition and problems will arise. With AMD video hardware and driver, the video continues playing - you can hear the sound despite being in the other user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1846374/+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 1910135] Re: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 5530 (aptd)
What makes you think that the issue is related to the ibus package? Usually that happens right after you have logged in to the session, when some processes are checking for updates behind the scenes. Just wait a few minutes, and try again. ** Changed in: ibus (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1910135 Title: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 5530 (aptd) Status in ibus package in Ubuntu: Invalid Bug description: 04/0833 Error report when att apply update: “E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 5530 (aptd) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? E: _cache->open() failed, please report. W: Be aware that removing the lock file is not a solution and may break your system.”04/0833 Error report when att apply update: “E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 5530 (aptd) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? E: _cache->open() failed, please report. W: Be aware that removing the lock file is not a solution and may break your system.”04/0833 Error report when att apply update: “E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 5530 (aptd) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? E: _cache->open() failed, please report. W: Be aware that removing the lock file is not a solution and may break your system.” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1910135/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
Strange, maybe yours is broken? Sound from mic should be quiet good, like on Windows or Android (mono 16 kHz, or even 48 kHz if your headset supports FastStream codec). I have also Zoweetek B0310, this one also works for me but it doesn't have auto profile switching. I'm using Lenovo T480, ArchLinux with kernel 5.10, pulseaudio 14 and latest Gnome. -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 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: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1904859] Update Released
The verification of the Stable Release Update for nautilus-sendto has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus-sendto in Ubuntu. https://bugs.launchpad.net/bugs/1904859 Title: [snap] cannot send file from Nautilus Status in nautilus-sendto package in Ubuntu: Fix Released Status in nautilus-sendto source package in Focal: Fix Released Status in nautilus-sendto source package in Groovy: Fix Committed Bug description: * Impact Nautilus->sendto fails to use the thunderbird snap command * Test case On a Ubuntu default session $ snap install thunderbird $ nautilus $ right click on a file and select the sendto entry -> thunderbird should be started with a composer dialog and the selected attachment included * Regression potential The patch removes an old hack that parsed and changed the thunderbird command, verify that thunderbird is still correctly start using it from different source (snap, deb, flatpak?) - TB 78.5.0 snap Focal Nothing happens when I right-click on a file (using Nautilus) from my home and choose 'send to'. I did not have such a problem using TB deb. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus-sendto/+bug/1904859/+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 1902244] Re: Backport packages for 20.04.2 HWE stack
This bug was fixed in the package libclc - 0.2.0+git20190827-7~ubuntu0.20.04.1 --- libclc (0.2.0+git20190827-7~ubuntu0.20.04.1) focal; urgency=medium * Backport to focal. (LP: #1902244) -- Timo Aaltonen Thu, 19 Nov 2020 08:53:21 +0200 ** Changed in: libclc (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libglvnd in Ubuntu. https://bugs.launchpad.net/bugs/1902244 Title: Backport packages for 20.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libglvnd package in Ubuntu: Invalid Status in llvm-toolchain-11 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in libclc source package in Focal: Fix Released Status in libdrm source package in Focal: Fix Committed Status in libglvnd source package in Focal: Fix Committed Status in llvm-toolchain-11 source package in Focal: Fix Committed Status in mesa source package in Focal: Fix Committed Status in xorg-server source package in Focal: Fix Committed Bug description: [Impact] These are needed for 20.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. [Regression potential] libdrm: very minimal chance for regressions llvm-11: a new package, no regression potential on it's own libclc: just a rebuild against the new llvm libglvnd: mostly just EGL headers sync from Khronos, needed by mesa mesa: a new major release, but we'll pull the final stable release of 20.2.x series, so there shouldn't be any regressions left at that point xserver: a new point-release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1902244/+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 1902244] Update Released
The verification of the Stable Release Update for libclc has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libglvnd in Ubuntu. https://bugs.launchpad.net/bugs/1902244 Title: Backport packages for 20.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libglvnd package in Ubuntu: Invalid Status in llvm-toolchain-11 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in libclc source package in Focal: Fix Released Status in libdrm source package in Focal: Fix Committed Status in libglvnd source package in Focal: Fix Committed Status in llvm-toolchain-11 source package in Focal: Fix Committed Status in mesa source package in Focal: Fix Committed Status in xorg-server source package in Focal: Fix Committed Bug description: [Impact] These are needed for 20.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. [Regression potential] libdrm: very minimal chance for regressions llvm-11: a new package, no regression potential on it's own libclc: just a rebuild against the new llvm libglvnd: mostly just EGL headers sync from Khronos, needed by mesa mesa: a new major release, but we'll pull the final stable release of 20.2.x series, so there shouldn't be any regressions left at that point xserver: a new point-release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1902244/+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 1904859] Re: [snap] cannot send file from Nautilus
This bug was fixed in the package nautilus-sendto - 3.8.6-3ubuntu0.20.04.1 --- nautilus-sendto (3.8.6-3ubuntu0.20.04.1) focal; urgency=medium * debian/patches/gitlab_thunderbird_cmd.patch: - remove an old workaround for thunderbird, it's not useful anymore and is creating problem with the snap cmd (lp: #1904859) -- Sebastien Bacher Mon, 23 Nov 2020 20:31:53 +0100 ** Changed in: nautilus-sendto (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus-sendto in Ubuntu. https://bugs.launchpad.net/bugs/1904859 Title: [snap] cannot send file from Nautilus Status in nautilus-sendto package in Ubuntu: Fix Released Status in nautilus-sendto source package in Focal: Fix Released Status in nautilus-sendto source package in Groovy: Fix Committed Bug description: * Impact Nautilus->sendto fails to use the thunderbird snap command * Test case On a Ubuntu default session $ snap install thunderbird $ nautilus $ right click on a file and select the sendto entry -> thunderbird should be started with a composer dialog and the selected attachment included * Regression potential The patch removes an old hack that parsed and changed the thunderbird command, verify that thunderbird is still correctly start using it from different source (snap, deb, flatpak?) - TB 78.5.0 snap Focal Nothing happens when I right-click on a file (using Nautilus) from my home and choose 'send to'. I did not have such a problem using TB deb. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus-sendto/+bug/1904859/+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 1910140] [NEW] Alignment of password field in 20.04 login screen not in centre
Public bug reported: ubuntu is now launching slowly for me it gives me a black screen at launch that shows the result of a system file check then it jumps to the login screen which seems strange as the alignment of the password field appears now on the left of the screen instead of in the centre as it used to be then ubuntu desktop starts, the screen seems to be shifting or 3 seconds then it adjusts itself to normal what should I reinstall to fix this please ? thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 4 19:35:37 2021 DisplayManager: lightdm InstallationDate: Installed on 2021-01-01 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1910140 Title: Alignment of password field in 20.04 login screen not in centre Status in gnome-shell package in Ubuntu: New Bug description: ubuntu is now launching slowly for me it gives me a black screen at launch that shows the result of a system file check then it jumps to the login screen which seems strange as the alignment of the password field appears now on the left of the screen instead of in the centre as it used to be then ubuntu desktop starts, the screen seems to be shifting or 3 seconds then it adjusts itself to normal what should I reinstall to fix this please ? thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 4 19:35:37 2021 DisplayManager: lightdm InstallationDate: Installed on 2021-01-01 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 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/1910140/+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 1846944] Re: Nextcloud client app indicator icon not visible in 19.10 Eoan Beta
*** This bug is a duplicate of bug 1897754 *** https://bugs.launchpad.net/bugs/1897754 Same as https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1897754 I could fix it by downgrading to Version 33-1 ** This bug has been marked a duplicate of bug 1897754 flameshot: The icon does not appear in the GNOME bar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1846944 Title: Nextcloud client app indicator icon not visible in 19.10 Eoan Beta Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: When running the Nextcloud Client (flatpak or PPA) in Eoan Beta, its app indicator icon is never displayed in the notification area. Other apps sch as Steam and Skype have their indicator icons displayed fine. Output from the command line when running the flatpak produces the following error: Qt: Session management error: None of the authentication protocols specified are supported I can duplicate this issue 100% of the time. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell-extension-appindicator 30-1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 6 13:35:44 2019 InstallationDate: Installed on 2019-09-23 (12 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: Upgraded to eoan on 2019-09-27 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1846944/+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 1907002] Re: Top bar Application Icons no longer appear
*** This bug is a duplicate of bug 1905370 *** https://bugs.launchpad.net/bugs/1905370 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1907002 Title: Top bar Application Icons no longer appear Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: I have lost the icons that appear in the top right corner of the Activities bar unexpectedly. I'm not entirely sure what happened other than the fact that I recently tested some fixes related to bug #1897224 and Groovy Proposed. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17 Uname: Linux 5.8.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Dec 6 13:41:15 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-15 (143 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 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-extension-appindicator/+bug/1907002/+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 1897754] Re: flameshot: The icon does not appear in the GNOME bar
I could fix it by downgrading to Version 33-1 I can also inform you, that also the nextcloud icon disappears and Nextcloud starts maximised instead of minimized -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1897754 Title: flameshot: The icon does not appear in the GNOME bar Status in flameshot package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: https://github.com/flameshot-org/flameshot/issues/1009 --- When upgrading from gnome-shell-extension-appindicator_33-3_all.deb to gnome-shell-extension-appindicator_34-1_all.deb the icon does not appear in the GNOME toolbar. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: flameshot 0.8.1-1 Uname: Linux 5.8.12-050812-generic x86_64 ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 29 11:55:57 2020 InstallationDate: Installed on 2020-06-19 (102 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609) SourcePackage: flameshot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flameshot/+bug/1897754/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
I can't seem to get the DG80 working correctly under PopOS 20.10. It works great for listening to music (though that worked directly on bluetooth without issues) but I can't seem to get the correct mode for talk. Since you say you have success with it, I will play with it some more before returning it and see if I can get it set up properly. It is probably some kind of configuration thing on my end, but I was hoping it would solve my microphone problems. As it stands, my best option is using the headset with my phone for Teams calls--the sound works perfectly there. If I find the right magic, I'll reply again here. -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 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: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1910135] [NEW] Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 5530 (aptd)
Public bug reported: 04/0833 Error report when att apply update: “E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 5530 (aptd) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? E: _cache->open() failed, please report. W: Be aware that removing the lock file is not a solution and may break your system.”04/0833 Error report when att apply update: “E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 5530 (aptd) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? E: _cache->open() failed, please report. W: Be aware that removing the lock file is not a solution and may break your system.”04/0833 Error report when att apply update: “E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 5530 (aptd) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? E: _cache->open() failed, please report. W: Be aware that removing the lock file is not a solution and may break your system.” ** Affects: ibus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1910135 Title: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 5530 (aptd) Status in ibus package in Ubuntu: New Bug description: 04/0833 Error report when att apply update: “E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 5530 (aptd) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? E: _cache->open() failed, please report. W: Be aware that removing the lock file is not a solution and may break your system.”04/0833 Error report when att apply update: “E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 5530 (aptd) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? E: _cache->open() failed, please report. W: Be aware that removing the lock file is not a solution and may break your system.”04/0833 Error report when att apply update: “E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 5530 (aptd) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? E: _cache->open() failed, please report. W: Be aware that removing the lock file is not a solution and may break your system.” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1910135/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
Avantree DG80 is an amazing device, it works out of box and it switches between HSP/A2DP profiles automatically - tested with AKG K371-BT and Denon GC-25w. -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 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: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1909946] Re: XWayland session starts, then quits.
Some more details: Using both gnome-wayland & ubuntu-wayland sessions, the common major errors are the following: 12:22:45 PM gnome-shell: Can't create a GtkStyleContext without a display connection 12:22:23 PM gdm-session-wor: gkr-pam: unable to locate daemon control file It happens when the desktop appears after about maybe 10 seconds or so. So I can't see PAM being involved as PAM is invoked during login — isn't it? Anyway hope this helps. Oh, I reinstalled from a backup image, (I have the system on a separate hard drive to my home directory) that was working correctly on Wayland. And with nothing added to the image, the same behaviour happened. So, I'm thinking this is probably a setting in my home directory — but which one? Suggestions to troubleshoot this are welcome — I'll put in the time to help figure this out. -- 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/1909946 Title: XWayland session starts, then quits. Status in xorg-server package in Ubuntu: New Bug description: So, this started about a week ago after an update from Ubuntu. I can initially login with XWayland, but something loading after the desktop appears, causes the session to exit. The only thing I can find relevant in the logs at the timestamp this occurred are the following: -gkr-pam: unable to locate daemon control file -Failed to start Process error reports when automatic reporting is enabled. -A start job for unit UNIT has failed I hope this helps track down the issue. Thanks for reading. BTW I have to submit this as a bug on something else, launchpad keeps telling me that XWayland doesn't exist. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xwayland 2:1.20.9-2ubuntu1.1 Uname: Linux 5.9.16-xanmod1 x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jan 3 19:33:28 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [148c:2356] InstallationDate: Installed on 2020-04-25 (253 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.9.16-xanmod1 root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1405 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:br5.14:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.103-1ubuntu1~g~mesarc0 version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.1+git2012290142.009e2aa5460~g~mesarc2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1909946/+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 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
** Branch linked: lp:~mozillateam/thunderbird/thunderbird.bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Bionic: Triaged Status in thunderbird source package in Focal: Fix Committed Status in thunderbird source package in Groovy: Fix Released Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+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 1908608] Re: Crash to login screen when plugging in/out external monitor
Hello and thank you for following up. Thank you for your suggestions. I will look into them. I will be on the lookout for new crashes and report them here. While uninstalling the unofficial desktop icon extension would seem like a good idea in the context of this bug report, that would result in an unusable system and therefore in no additional crashes or information. Hopefully they're not the source, but otherwise it may underline the apparent architectural problem of giving small utility extensions the power to crash the entire session along with every application on the system, or alternatively the apparent social problem of encouraging people to write trivial utilities as gnome extensions when it's not a suitable extension point for the task. (Assuming those problems are not already readily acknowledged in the community. I don't know much about people's attitudes towards that) (That the OS will become unusable is just a natural consequence of a desktop OS with subpar built-in support for desktop icons: I'm then forced to find a replacement extension that offers the minimum set of functionality that can reasonably be expected from any desktop OS. The default desktop icon extension simply does not deliver — with it I would need to use another OS) -- 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/1908608 Title: Crash to login screen when plugging in/out external monitor Status in gnome-shell package in Ubuntu: Incomplete Bug description: This matches the title of https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1717170 but I don't want to assume it is the same considering that was allegedly fixed three years ago. journal: dec 17 23:12:51 computer-name kernel: usb 3-1: USB disconnect, device number 8 dec 17 23:12:51 computer-name kernel: usb 3-1.1: USB disconnect, device number 10 dec 17 23:12:51 computer-name acpid[716]: input device has been disconnected, fd 7 dec 17 23:12:51 computer-name gnome-shell[2891]: libinput error: event6 - bcm5974: client bug: event processing lagging behind by 42ms, your system is too slow dec 17 23:12:51 computer-name acpid[716]: input device has been disconnected, fd 8 dec 17 23:12:51 computer-name acpid[716]: input device has been disconnected, fd 15 dec 17 23:12:51 computer-name kernel: usb 3-1.4: USB disconnect, device number 9 dec 17 23:12:53 computer-name gnome-shell[2891]: meta_display_get_monitor_in_fullscreen: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed dec 17 23:12:53 computer-name fwupd[3384]: 22:12:53:0711 FuEngine nitrokey failed to change udev device /sys/devices/pci:00/:00:02.0/drm/card0: cannot ensure ID: FuUdevDevice: dec 17 23:12:53 computer-name fwupd[3384]: Unknown Device dec 17 23:12:53 computer-name fwupd[3384]: Flags:none dec 17 23:12:53 computer-name gnome-shell[2891]: DING: GNOME nautilus 3.38.1 dec 17 23:12:53 computer-name gnome-shell[2891]: meta_display_get_monitor_in_fullscreen: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed dec 17 23:12:53 computer-name gnome-shell[2891]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed dec 17 23:12:53 computer-name gnome-shell[2891]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). dec 17 23:12:55 computer-name gnome-shell[2891]: GNOME Shell crashed with signal 11 dec 17 23:12:55 computer-name gnome-shell[2891]: == Stack trace for
[Desktop-packages] [Bug 1909970] Re: Fonts is not responding
Note: the problem does not occur sometimes starting from terminal - works about 1 of 10 also after cleaning cache/thumbnails as suggested by https://gitlab.gnome.org/GNOME/gnome-font-viewer/-/issues/29 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-font-viewer/-/issues #29 https://gitlab.gnome.org/GNOME/gnome-font-viewer/-/issues/29 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/1909970 Title: Fonts is not responding Status in gnome-font-viewer package in Ubuntu: New Bug description: Just started fonts, the window opens but mouse arrow is inoperative on the window. after some time a message appears saying 'fonts is not responding' corrado@corrado-n8-hh-0101:~$ apt policy gnome-font-viewer gnome-font-viewer: Installed: 3.34.0-2 Candidate: 3.34.0-2 Version table: *** 3.34.0-2 500 500 http://archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-n8-hh-0101:~$ inxi -SCGx System:Host: corrado-n8-hh-0101 Kernel: 5.8.0-25-generic x86_64 bits: 64 compiler: gcc v: 10.2.0 Desktop: GNOME 3.38.2 Distro: Ubuntu 21.04 (Hirsute Hippo) CPU: Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP arch: Ice Lake rev: 5 L2 cache: 6 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19046 Speed: 1000 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 1000 2: 967 3: 995 4: 872 5: 954 6: 961 7: 984 8: 717 Graphics: Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus ID: 1-6:3 Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 20.2.6 direct render: Yes corrado@corrado-n8-hh-0101:~$ ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-font-viewer 3.34.0-2 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 4 08:25:41 2021 ExecutablePath: /usr/bin/gnome-font-viewer InstallationDate: Installed on 2021-01-01 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210101) SourcePackage: gnome-font-viewer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1909970/+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 1821415] Re: pkexec fails in a non-graphical environment
Can we raise the importance please? It is quite essential to let unprivileged users run certain commands, even if there is not GUI. Also, it is very confusing when everything is configured correctly, plus the password is correct, and then to get the message "Not authorized", "This incident has been reported." -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1821415 Title: pkexec fails in a non-graphical environment Status in PolicyKit: New Status in apport package in Ubuntu: Triaged Status in policykit-1 package in Ubuntu: Triaged Bug description: The plymouth apport source package hooks wants to gather log files as the root user and apport provides a policy kit policy for collecting that information. This works fine in a graphical environment but not in a non-graphical one. N.B. you first need to create a /var/log/plymouth-debug.log file for the plymouth apport package hook to actually trigger this. ubuntu@disco:~$ ubuntu-bug plymouth *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .. AUTHENTICATING FOR com.ubuntu.apport.root-info === Authentication is required to collect system information for this problem report Authenticating as: Ubuntu (ubuntu) Password: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie AUTHENTICATION FAILED === Error executing command as another user: Not authorized This incident has been reported. Subsequently, bug reports from servers will contain less information. To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1821415/+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 1908992] Re: SYNA30B4:00 06CB:CE09 Mouse on HP EliteBook 850 G7 not working at all
Same problem here, the pointing stick/trackpoint does not work. MachineType: HP HP EliteBook 850 G7 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/vgxubuntu-root ro quiet splash psmouse.proto=bare SourcePackage: xserver-xorg-input-libinput Package: xserver-xorg-input-libinput 0.29.0-1 $ xinput ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ SYNA30B4:00 06CB:CE09 Mouse id=11 [slave pointer (2)] ⎜ ↳ SYNA30B4:00 06CB:CE09 Touchpad id=12 [slave pointer (2)] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1908992 Title: SYNA30B4:00 06CB:CE09 Mouse on HP EliteBook 850 G7 not working at all Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Bug description: $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SYNA30B4:00 06CB:CE09 Mouse id=11 [slave pointer (2)] ⎜ ↳ SYNA30B4:00 06CB:CE09 Touchpad id=12 [slave pointer (2)] The touchpad is working fine, but the pointing stick/trackpoint does not work at all. No input is registered with xinput and libinput device tests. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-input-libinput 0.29.0-1 ProcVersionSignature: Ubuntu 5.8.0-33.36~20.04.1-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Dec 22 10:13:13 2020 DistUpgraded: 2020-12-22 07:48:08,643 DEBUG /openCache(), new cache size 70584 DistroCodename: focal DistroVariant: ubuntu InstallationDate: Installed on 2020-12-11 (10 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP EliteBook 850 G7 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/vgxubuntu-root ro quiet splash psmouse.proto=bare SourcePackage: xserver-xorg-input-libinput UpgradeStatus: Upgraded to focal on 2020-12-22 (0 days ago) dmi.bios.date: 08/24/2020 dmi.bios.release: 1.7 dmi.bios.vendor: HP dmi.bios.version: S73 Ver. 01.01.07 dmi.board.name: 8724 dmi.board.vendor: HP dmi.board.version: KBC Version 06.34.00 dmi.chassis.asset.tag: 5CG0471SRC dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 6.52 dmi.modalias: dmi:bvnHP:bvrS73Ver.01.01.07:bd08/24/2020:br1.7:efr6.52:svnHP:pnHPEliteBook850G7NotebookPC:pvr:rvnHP:rn8724:rvrKBCVersion06.34.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 850 G7 Notebook PC dmi.product.sku: 1J6F3EA#ABD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1908992/+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 1880405] Re: High CPU and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9
Similar ERROR in /var/log/syslog for me on Ubuntu 20.10 with gnome-shell 3.38.1-1ubuntu1.1. Similar to comment #9 I have firefox with many tabs and dissenter (brave fork) with many tabs open. Jan 4 06:43:29 desktop01 gnome-shell[2096000]: JS ERROR: TypeError: null has no properties#012_onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9 Jan 4 06:43:30 desktop01 gnome-shell[2096000]: message repeated 35862 times: [ JS ERROR: TypeError: null has no properties#012_onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9] Jan 4 06:43:30 desktop01 gnome-shell[2096000]: JS ERROR: TypeError: windowActor is null#012_addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:90:28#012vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:162:14 ➜ ~ inxi -SMCG System:Host: desktop01 Kernel: 5.8.0-33-generic x86_64 bits: 64 Desktop: N/A Distro: Ubuntu 20.10 (Groovy Gorilla) Machine: Type: Desktop System: ASUS product: All Series v: N/A serial: Mobo: ASUSTeK model: X99-A v: Rev 1.xx serial: UEFI: American Megatrends v: 4101 date: 07/10/2019 CPU: Info: 6-Core model: Intel Core i7-5820K bits: 64 type: MT MCP L2 cache: 15.0 MiB Speed: 1765 MHz min/max: 1200/3600 MHz Core speeds (MHz): 1: 1626 2: 1243 3: 1387 4: 1291 5: 1379 6: 1316 7: 1329 8: 1300 9: 1288 10: 1247 11: 1356 12: 1282 Graphics: Device-1: NVIDIA GK208B [GeForce GT 710] driver: nvidia v: 455.38 Display: x11 server: X.Org 1.20.9 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa resolution: 1: 2560x1080~60Hz 2: 1680x1050~60Hz OpenGL: renderer: GeForce GT 710/PCIe/SSE2 v: 4.6.0 NVIDIA 455.38 -- 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/1880405 Title: High CPU and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9 Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: O.k. it is an old Lenovo thinkpad T410. However, in 18.04, 19.04 and 19.10 I did face these problems. The sometimes I have to wait 10 seconds to see if a window reacts or not. It is hard to use. Installiert: 3.36.1-5ubuntu2 Installationskandidat: 3.36.2-1ubuntu1~20.04.1 Versionstabelle: 3.36.2-1ubuntu1~20.04.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages *** 3.36.1-5ubuntu2 100 100 /var/lib/dpkg/status 3.36.1-5ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Sun May 24 15:43:34 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-05 (109 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-05-08 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1880405/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Problem has NOT been fixed for my setup: - Kernel: 5.4.0-58-generic #64 - OS: Ubuntu 20.04.1 LTS - Machine: Lenovo ThinkPad - Headset: JBL 500BT -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1908559] Re: Steam or discord: "pushModal: invocation of begin_modal failed"
It seems like disabling these plugins have made these particular log entries go away for me. Thank you for your assistance Daniel. -- 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/1908559 Title: Steam or discord: "pushModal: invocation of begin_modal failed" Status in gnome-shell package in Ubuntu: Incomplete Bug description: Roughly every 10 minutes two entries of the heading is printed to the logs ``` $ journalctl -b | grep "pushModal: invocation of begin_modal failed" des. 17 19:38:53 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:45:15 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:45:18 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:54:00 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:54:02 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 20:03:34 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 20:03:37 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed ``` I'm suspecting this is caused by either the discord snap, or steam missing some kind of permission ``` ps -ef | grep 8626 centx 86268293 3 19:18 ?00:01:38 /usr/bin/gnome-shell centx 86928626 0 19:18 ?00:00:00 ibus-daemon --panel disable --xim centx 184538626 0 19:39 ?00:00:13 /snap/discord/119/usr/share/discord/Discord --no-sandbox centx 192378626 0 19:41 ?00:00:00 /bin/sh -e /usr/games/steam ``` --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2018-12-30 (718 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: gnome-shell 3.38.1-1ubuntu1.1 PackageArchitecture: amd64 RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 Tags: third-party-packages groovy Uname: Linux 5.9.12-050912-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-12-12 (5 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1908559/+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 1908878] Re: [nvidia] gnome shell freezes for a couple of seconds, then it restarts (maybe it crashes?)
Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1908878 Title: [nvidia] gnome shell freezes for a couple of seconds, then it restarts (maybe it crashes?) Status in Mutter: Unknown Status in mutter package in Ubuntu: Incomplete Bug description: This is the line I always see in the log after the restart: Dec 21 09:33:55 ricsipontaz-home gsd-media-keys[5953]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shel l” on object at path /org/gnome/Shell ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 21 09:56:41 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-12-04 (17 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201203) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/usr/bin/zsh RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1908878/+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 1877135] Re: Failed to start Virtual filesystem service - Apple File Conduit monitor [libusbmuxd.so.4 not found]
If anyone is wondering what "properly removing it" actually means it's just literally rm /usr/local/lib/libimobiledevice.so.6. Don't worry since there should already be a similar system library in /usr/lib/x86_64-linux-gnu/. I also noticed there were other files with names starting with libimobiledevice.so.* in the same /usr/local/lib directory so I also removed them. For the record I tried to do a make uninstall from the source directory thinking that was the "proper way" but that didn't help. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1877135 Title: Failed to start Virtual filesystem service - Apple File Conduit monitor [libusbmuxd.so.4 not found] Status in gvfs package in Ubuntu: Invalid Bug description: After upgrading to Focal, /usr/libexec/gvfs-afc-volume-monitor fails with the message /usr/libexec/gvfs-afc-volume-monitor: error while loading shared libraries: libusbmuxd.so.4: cannot open shared object file: No such file or directory 1) lsb_release -rd: Description: Ubuntu 20.04 LTS Release: 20.04 2)apt-cache policy gvfs gvfs: Installed: 1.44.1-1ubuntu1 Candidate: 1.44.1-1ubuntu1 Version table: *** 1.44.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 4) What happens: many applications (nautilus, gedit, etc) take ~30 sec to open. When starting those via the command line, after after those 30 secs the app opens with the following printed to the terminal: "Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.AfcVolumeMonitor: Timeout was reached (g-io-error-quark, 24)" 3) What you expected to happen: applications to open without delay = Additional info: After calling 'journalctl -b', several instances like dbus-daemon[2031]: [session uid=1000 pid=2031] Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service' requested by ':1.25' (uid=1000 pid=2135 comm="/usr/bin/gnome-shell " label="unconfined") systemd[1964]: Starting Virtual filesystem service - Apple File Conduit monitor... gvfs-afc-volume-monitor[2279]: /usr/libexec/gvfs-afc-volume-monitor: error while loading shared libraries: libusbmuxd.so.4: cannot open shared object file: No such file or directory systemd[1964]: gvfs-afc-volume-monitor.service: Main process exited, code=exited, status=127/n/a systemd[1964]: gvfs-afc-volume-monitor.service: Failed with result 'exit-code'. systemd[1964]: Failed to start Virtual filesystem service - Apple File Conduit monitor. Also upowerd is affected: /usr/lib/upower/upowerd: error while loading shared libraries: libusbmuxd.so.4: cannot open shared object file: No such file or directory upower.service: Main process exited, code=exited, status=127/n/a upower.service: Failed with result 'exit-code'. Failed to start Daemon for power management. The package libusbmuxd6 is installed (and /usr/lib/x86_64-linux- gnu/libusbmuxd.so.6 is present), but when trying "sudo apt install libusbmuxd4", I get the error "E: Unable to locate package libusbmuxd4". It would appear to me that some dependencies *somewhere* are not properly updated (to libusbmuxd6 from libusbmuxd4). Unfortunately, the huge timeout significantly affects usability of the computer, as one has to wait a lot to perform many tasks (opening nautilus, gedit); one has to wait also before login screen appears after a reboot. Something that appears to be related: https://forum.manjaro.org/t/upower-fails-to-start-becuase-upowerd-is-not-running/117291 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gvfs-backends 1.44.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Wed May 6 13:45:53 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2015-03-18 (1875 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: gvfs UpgradeStatus: Upgraded to focal on 2020-04-24 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1877135/+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 1903986] Re: Ubuntu 20.04 freezes with remmina in full-screen
I have now disabled the HideTopBar extension, but it is going to be difficult to find out if this is the cause of the problem, because freezes happens sometimes one's per month. I don't know if I can live without it such a long time. :-) I have reported problem upstream to HideTopBar extension developer: https://github.com/mlutfy/hidetopbar/issues/266 hope to get some feedback soon. Daniel, thank you for looking into my problem. I really appreciate it. ** Bug watch added: github.com/mlutfy/hidetopbar/issues #266 https://github.com/mlutfy/hidetopbar/issues/266 -- 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/1903986 Title: Ubuntu 20.04 freezes with remmina in full-screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: On Ubuntu 20.04 using Remmina accessing remote Windows session to my work and everything was working fine for 5 hours and then suddenly Reminna freezes. Mouse pointer still working fine, but Remmina not responding and also keyboard not responding (maybe because all of the keys are controller by Remmina). This problem is now third time the problem appeared: - bug 1902051 - bug 1903710 with no response. :( Work-around: hard press power button to power off laptop and power on it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: remmina 1.4.2+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 12:38:25 2020 InstallationDate: Installed on 2019-10-23 (386 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: remmina UpgradeStatus: Upgraded to focal on 2020-08-14 (89 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: 2020-04-29T17:08:03.553351 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-23 (392 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-08-14 (95 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True 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: 2020-04-29T17:08:03.553351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903986/+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 1908878] Re: [nvidia] gnome shell freezes for a couple of seconds, then it restarts (maybe it crashes?)
Thanks. That crash is bug 1897765, which was fixed in 21.04 on 18 December. Remember to update your system: sudo apt update sudo apt full-upgrade and then tell us if any new crashes occur after that. -- 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/1908878 Title: [nvidia] gnome shell freezes for a couple of seconds, then it restarts (maybe it crashes?) Status in Mutter: Unknown Status in mutter package in Ubuntu: Incomplete Bug description: This is the line I always see in the log after the restart: Dec 21 09:33:55 ricsipontaz-home gsd-media-keys[5953]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shel l” on object at path /org/gnome/Shell ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 21 09:56:41 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-12-04 (17 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201203) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/usr/bin/zsh RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1908878/+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 1903986] Re: Ubuntu 20.04 freezes with remmina in full-screen
The log in comment #34 certainly mentions /home/igor/.local/share/gnome- shell/extensions/hidetop...@mathieu.bidon.ca so please uninstall it fully while investigating this bug. -- 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/1903986 Title: Ubuntu 20.04 freezes with remmina in full-screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: On Ubuntu 20.04 using Remmina accessing remote Windows session to my work and everything was working fine for 5 hours and then suddenly Reminna freezes. Mouse pointer still working fine, but Remmina not responding and also keyboard not responding (maybe because all of the keys are controller by Remmina). This problem is now third time the problem appeared: - bug 1902051 - bug 1903710 with no response. :( Work-around: hard press power button to power off laptop and power on it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: remmina 1.4.2+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 12:38:25 2020 InstallationDate: Installed on 2019-10-23 (386 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: remmina UpgradeStatus: Upgraded to focal on 2020-08-14 (89 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: 2020-04-29T17:08:03.553351 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-23 (392 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-08-14 (95 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True 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: 2020-04-29T17:08:03.553351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903986/+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 1908878] Re: [nvidia] gnome shell freezes for a couple of seconds, then it restarts (maybe it crashes?)
Maybe this is related: 2020-12-16 11:122020-12-16 10:12 UTCCrash gnome-shell https://errors.ubuntu.com/oops/1d1bb40c-3f8a-11eb-9246-fa163e983629 -- 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/1908878 Title: [nvidia] gnome shell freezes for a couple of seconds, then it restarts (maybe it crashes?) Status in Mutter: Unknown Status in mutter package in Ubuntu: Incomplete Bug description: This is the line I always see in the log after the restart: Dec 21 09:33:55 ricsipontaz-home gsd-media-keys[5953]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shel l” on object at path /org/gnome/Shell ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 21 09:56:41 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-12-04 (17 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201203) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/usr/bin/zsh RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1908878/+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 427168] Re: usb keyboard settings (repeat rate and delay) reset on plugin
Please can we re-open this issue? This regression may not get attention because the issue is currently marked as fixed. -- 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/427168 Title: usb keyboard settings (repeat rate and delay) reset on plugin Status in GNOME Settings Daemon: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Bug description: I like a fairly fast repeat rate and low delay when typing. In the course of using my laptop (Dell Vostro 1500), I sometimes plug in a USB keyboard. Every time I do this, I notice that the repeat rate and delay on the USB keyboard are way slow and high, while the built-in keyboard repeat rate and delay are as I like them (fast and low). To fix this, every time I plug in the USB keyboard, I have to go to System→Preferences→Keyboard, slightly move the Speed slider, then Close the dialog. (Note that the sliders haven't changed from the last invocation of this application, just that the settings apparently need to be reapplied internally.) I believe that at least these keyboard settings (repeat rate and delay) should be universal for all keyboards. Repeatable: always. How to reproduce: 1. plug in a USB keyboard 2. Note current repeat-rate and delay. 3. Change repeat-rate and delay via System->Preferences->Keyboard 4. Unplug and re-plugin the USB keyboard. 5. Return to step 2. Possibly related bugs: Bug #295990 Bug #426176 $ uname -a Linux hani 2.6.28-15-generic #49-Ubuntu SMP Tue Aug 18 19:25:34 UTC 2009 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 9.04 Release: 9.04 Codename: jaunty To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/427168/+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 1886728] Re: OpenVPN OTP replaces the ordinary password
** Also affects: network-manager via https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/97 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1886728 Title: OpenVPN OTP replaces the ordinary password Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Triaged Bug description: When OpenVPN has One-time password (OTP) enabled, and the user connects, a dialog asks the user to enter the One-time password (OTP) and press ok. This action replaces the ordinary "long term" password with the OTP. This causes annoyance as the next login will fail because the password is wrong and the user has to enter both the password and the OTP the next time they log in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-keyring 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 8 01:07:18 2020 InstallationDate: Installed on 2020-03-23 (106 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-keyring UpgradeStatus: Upgraded to focal on 2020-05-11 (57 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1886728/+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 1909352] Re: (1) video hangs or (2) screen goes blank and case fan turns on
It sounds like something is crashing or spinning. Also the attached Xorg logs seem to be from 2019, which is confusing. So those should be ignored... Please: 1. Run this command: journalctl -b0 > journal.txt and attach the resulting text file here. 2. Follow these instructions to check for crashes: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Tags added: nvidia ** Summary changed: - (1) video hangs or (2) screen goes blank and case fan turns on + [nvidia] (1) video hangs or (2) screen goes blank and case fan turns on ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-455 (Ubuntu) ** Changed in: nvidia-graphics-drivers-455 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1909352 Title: [nvidia] (1) video hangs or (2) screen goes blank and case fan turns on Status in nvidia-graphics-drivers-455 package in Ubuntu: Incomplete Bug description: Recover system by press and release reset switch. Log in again. Had these issues with Ubuntu 18.04. Updated to Nvidia drivers and issues resolved. Updated to 20.04.1 and issues have returned. Checked and see that Nvidia drivers newer than those packaged for use. Available at Nvidia / Newest package and in use: GeForce Game Ready Driver LINUX X64 (AMD64/EM64T) DISPLAY DRIVER Driver Version: 455.45 - Release Date: Tue Nov 17, 2020 GeForce Game Ready Driver LINUX X64 (AMD64/EM64T) DISPLAY DRIVER Driver Version: 455.38 - Release Date: Thu Oct 29, 2020 Hopefully the command ubuntu-bug xorg attached all the information you may need. $ lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.38 Thu Oct 22 06:06:59 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Dec 26 09:54:40 2020 DistUpgraded: 2020-10-02 13:11:28,665 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 455.38, 5.4.0-56-generic, x86_64: installed nvidia, 455.38, 5.4.0-58-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050] [10de:1c81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP107 [GeForce GTX 1050] [3842:6150] InstallationDate: Installed on 2018-03-03 (1029 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Gigabyte Technology Co., Ltd. AB350-Gaming 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=fc7c6eeb-fbb0-4f6c-8815-349d9ff6efd6 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-10-02 (84 days ago) dmi.bios.date: 08/18/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F8 dmi.board.asset.tag: Default string dmi.board.name: AB350-Gaming 3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF8:bd08/18/2017:svnGigabyteTechnologyCo.,Ltd.:pnAB350-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350-Gaming3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350-Gaming 3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx
[Desktop-packages] [Bug 1903986] Re: Ubuntu 20.04 freezes with remmina in full-screen
** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903986/+attachment/5449164/+files/lspci.txt -- 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/1903986 Title: Ubuntu 20.04 freezes with remmina in full-screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: On Ubuntu 20.04 using Remmina accessing remote Windows session to my work and everything was working fine for 5 hours and then suddenly Reminna freezes. Mouse pointer still working fine, but Remmina not responding and also keyboard not responding (maybe because all of the keys are controller by Remmina). This problem is now third time the problem appeared: - bug 1902051 - bug 1903710 with no response. :( Work-around: hard press power button to power off laptop and power on it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: remmina 1.4.2+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 12:38:25 2020 InstallationDate: Installed on 2019-10-23 (386 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: remmina UpgradeStatus: Upgraded to focal on 2020-08-14 (89 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: 2020-04-29T17:08:03.553351 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-23 (392 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-08-14 (95 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True 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: 2020-04-29T17:08:03.553351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903986/+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 1903986] Re: Ubuntu 20.04 freezes with remmina in full-screen
** Attachment added: "freshprevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903986/+attachment/5449163/+files/freshprevboot.txt -- 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/1903986 Title: Ubuntu 20.04 freezes with remmina in full-screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: On Ubuntu 20.04 using Remmina accessing remote Windows session to my work and everything was working fine for 5 hours and then suddenly Reminna freezes. Mouse pointer still working fine, but Remmina not responding and also keyboard not responding (maybe because all of the keys are controller by Remmina). This problem is now third time the problem appeared: - bug 1902051 - bug 1903710 with no response. :( Work-around: hard press power button to power off laptop and power on it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: remmina 1.4.2+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 12:38:25 2020 InstallationDate: Installed on 2019-10-23 (386 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: remmina UpgradeStatus: Upgraded to focal on 2020-08-14 (89 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: 2020-04-29T17:08:03.553351 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-23 (392 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-08-14 (95 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True 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: 2020-04-29T17:08:03.553351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903986/+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 1903986] Re: Ubuntu 20.04 freezes with remmina in full-screen
It may really be hidetop...@mathieu.bidon.ca Gnome Shell extension. Now that you mention it again I opened up Extension application and try playing with the extension and when pressing the new shortcut key (that was not set until now), whole screen froze and I was requested to hard reset the laptop (red rectangle on print-screen). I rebooted the laptop and I am playing again with extension keyboard shortcuts, but now everything works fine. I am playing it for a while setting all kind of setting and works fine. I still don't have reproducible steps, something just triggers the freeze, but I can't figure it out what that is. I have collected files like requested in #22 and I am attaching them. Maybe from the logs you can see if there is the same pattern. If yes, then this extension may cause freezes. ** Attachment added: "hide_top_bar.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903986/+attachment/5449162/+files/hide_top_bar.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1903986 Title: Ubuntu 20.04 freezes with remmina in full-screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: On Ubuntu 20.04 using Remmina accessing remote Windows session to my work and everything was working fine for 5 hours and then suddenly Reminna freezes. Mouse pointer still working fine, but Remmina not responding and also keyboard not responding (maybe because all of the keys are controller by Remmina). This problem is now third time the problem appeared: - bug 1902051 - bug 1903710 with no response. :( Work-around: hard press power button to power off laptop and power on it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: remmina 1.4.2+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 12:38:25 2020 InstallationDate: Installed on 2019-10-23 (386 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: remmina UpgradeStatus: Upgraded to focal on 2020-08-14 (89 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: 2020-04-29T17:08:03.553351 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-23 (392 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-08-14 (95 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True 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: 2020-04-29T17:08:03.553351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903986/+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 1908878] Re: gnome shell freezes for a couple of seconds, then it restarts (maybe it crashes?)
Try looking at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. ** Summary changed: - gnome shell freezes for a couple of seconds, then it restarts (maybe it crashes?) + [nvidia] gnome shell freezes for a couple of seconds, then it restarts (maybe it crashes?) ** Tags added: nvidia -- 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/1908878 Title: [nvidia] gnome shell freezes for a couple of seconds, then it restarts (maybe it crashes?) Status in Mutter: Unknown Status in mutter package in Ubuntu: Incomplete Bug description: This is the line I always see in the log after the restart: Dec 21 09:33:55 ricsipontaz-home gsd-media-keys[5953]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shel l” on object at path /org/gnome/Shell ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 21 09:56:41 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-12-04 (17 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201203) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/usr/bin/zsh RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1908878/+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 1909327] Re: Lenovo T450s trackpad doesn't work after sleep
*** This bug is a duplicate of bug 1901350 *** https://bugs.launchpad.net/bugs/1901350 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 1901350, 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) => ubuntu ** This bug has been marked a duplicate of bug 1901350 [Lenovo ThinkPad T450s] Touchpad stops working after sleep -- 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/1909327 Title: Lenovo T450s trackpad doesn't work after sleep Status in Ubuntu: New Bug description: After sleep, the Lenovo T450s trackpad stops working. I have to rmmod psmouse and modprobe psmouse to get it to work again, or just use an external mouse. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xserver-xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 25 12:29:17 2020 DistUpgraded: 2020-10-24 12:59:49,175 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5036] MachineType: LENOVO 20BWS1D61J ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=UUID=09cc0657-0a94-4a6c-9043-2df6132cd821 ro SourcePackage: xorg UpgradeStatus: Upgraded to groovy on 2020-10-24 (62 days ago) dmi.bios.date: 02/23/2019 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: JBET72WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS1D61J dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnLENOVO:bvrJBET72WW(1.36):bd02/23/2019:br1.36:efr1.4:svnLENOVO:pn20BWS1D61J:pvrThinkPadT450s:rvnLENOVO:rn20BWS1D61J:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS1D61J dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1909327/+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 1909347] Re: Keyboard layout used in the second place breaks keymap
** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1909347 Title: Keyboard layout used in the second place breaks keymap Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: It's hard to really summarize the issue here. If you use the Neo2 layout somewhere, the keymap becomes garbled in a very specific way (see below). I am not really sure if it affects other keyboard layouts or what happens internally. I have selected gnome-control-center as the affected package, because this is, where it all starts. There are two issues, which are somehow connected. Reproduction steps (first issue): 1. Open "Region & Language Settings" in gnome-control-center 2. In "Input Sources" use "German (no dead keys)" in the FIRST place and "German (Neo 2)" in the second place (order matters!) 3. Open your favorite text editor 4. Use Super+Alt+Backspace to change to the Neo2 layout 5. Press and hold the Mod4 key (right of Left Shift) and 3. 6. You get a 3, expected would be №. Reproduction steps (second issue): 1. Go back to the "Region & Language Settings" and now use "German (Neo 2)" in the FIRST place and "German (no dead keys)" in the SECOND place 2. Open Chromium and open any web page (it does not work with any other application) 3. Use Super+Alt+Backspace to change to "German (no dead keys)" layout 4. Press Ctrl+F 5. Instead of the In-Page-Search opening, you go to the search bar, which means that the input is interpreted as Ctrl+E instead of Ctrl+F. If you press Ctrl+I (which is Ctrl+F on Neo2), the search bar opens, which means that even though Neo2 is selected, the old keymap is still somehow active. Info: 1) Release: Ubuntu 20.04.1 LTS 2) gnome-control-center: Installed: 1:3.36.4-0ubuntu2 3/4) See reproduction steps above To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1909347/+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 1909351] Re: gnome shell cpu
*** This bug is a duplicate of bug 1880405 *** https://bugs.launchpad.net/bugs/1880405 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 1880405, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1880405 High CPU and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9 -- 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/1909351 Title: gnome shell cpu Status in gnome-shell package in Ubuntu: New Bug description: From time to time gnome-shell cpu percentage spikes on Ubuntu 20.10. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp nvidia_modeset zcommon znvpair nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Dec 26 08:11:11 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-29 (211 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-10-26 (60 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1909351/+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 1908878] Re: gnome shell freezes for a couple of seconds, then it restarts (maybe it crashes?)
Yes, I'm using the Nvidia 455.28 driver (GTX 960). /var/crash is empty, did something clean it periodically? Btw, should I open a new bug report? Or how can I attach the crash file to this bug? "Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself." -- 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/1908878 Title: gnome shell freezes for a couple of seconds, then it restarts (maybe it crashes?) Status in Mutter: Unknown Status in mutter package in Ubuntu: Incomplete Bug description: This is the line I always see in the log after the restart: Dec 21 09:33:55 ricsipontaz-home gsd-media-keys[5953]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shel l” on object at path /org/gnome/Shell ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 21 09:56:41 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-12-04 (17 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201203) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/usr/bin/zsh RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1908878/+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 1909194] Re: Intel driver not installed properly
The correct kernel driver for Intel graphics is 'i915'. And the correct Xorg driver for Intel graphics is 'modeset'. The attached files seem to show both are working. What exactly is the problem you are trying to solve? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1909194 Title: Intel driver not installed properly Status in Ubuntu: Incomplete Bug description: Intel driver not installed properly ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 24 14:14:13 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:2017] InstallationDate: Installed on 2020-12-23 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=a8184a82-57ed-4426-b8a0-55b2f2740603 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BEH6110H.86A.0044.2012.0531.1710 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH61WW dmi.board.vendor: Intel Corporation dmi.board.version: AAG23116-302 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBEH6110H.86A.0044.2012.0531.1710:bd05/31/2012:svn:pn:pvr:rvnIntelCorporation:rnDH61WW:rvrAAG23116-302:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1909194/+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 1909152] Re: color calibration fails when using gnome gui on 20.10
Sounds like bug 1719143. I wonder if your log contains the same "no sensor" message? ** Changed in: colord (Ubuntu) Status: New => Incomplete ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1909152 Title: color calibration fails when using gnome gui on 20.10 Status in colord package in Ubuntu: Incomplete Status in gnome-control-center package in Ubuntu: Incomplete Bug description: in the past, I've used DisplayCalGUI to calibrate my displays. however, that software hasn't been updated to use Python3 properly, so it doesn't run on recent Ubuntu releases. I thought I'd try the builtin gnome calibration, but it seems completely broken on 20.10. I've tried two difference systems with fresh minimal installs, each has a different display and a different brand of colour calibration hardware. in both cases, they get to testing the coloured swatches, and fail, with an error saying: "Calibration failed! An internal error occurred that could not be recovered. You can remove the calibration device." however, looking in the output from `journalctl`, colord seems to claim that it succeeded in generating a profile. So I'm guessing there's something broken in the integration between colord and gnome-settings? all I know is it reports that it failed, and gnome doesn't show any new profile to use. here's the `journalctl` output: Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: No of test patches = 64 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Omitted 0 zero measurements Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Find white & black points Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Initial white point = 1.051779 0.999535 0.796168 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Creating matrix... Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: [46B blob data] Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Matrix = 0.615651 0.622859 0.645454 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: 0.647113 0.653246 0.680660 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: 0.531396 0.531212 0.553325 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Creating matrix and single gamma curve... Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: [26B blob data] Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Matrix = 0.009811 0.389211 0.558809 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: 0.144281 0.347751 0.505066 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: 0.198306 0.283542 0.312788 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Gamma = -1.574397 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Doing White point fine tune: Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Before fine tune, rel WP = XYZ 0.95783065 0.99709777 0.79463644, Lab 99.887672 -0.619729 2.283133 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: After fine tune, rel WP = XYZ 0.96420288 1. 0.82490540, Lab 100.00 0.00 0.00 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: abs WP = XYZ 1.04542265 0.99666916 0.76687003, Lab 99.871064 14.218222 4.582465 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Black point XYZ = 1.04542265 0.99666916 0.76687003, Lab = 99.871064 14.218222 4.582465 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Scaling White Point by 1.003342 to make Y = 1.0 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Display Luminance = 0.940928 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: White point XYZ = 1.048916 1.00 0.769433 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Black point XYZ = 1.048916 1.00 0.769433 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Done gamma/shaper and matrix creation Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Profile done ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: colord 1.4.4-2build1 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Wed Dec 23 13:51:43 2020 SourcePackage: colord UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1909152/+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 1909241] Re: Unreadable text with two monitors
There doesn't seem to be any external monitor connected in the attached files. Please attach it and then run: xrandr --verbose > xrandr2.txt and attach the resulting text file to this bug. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Also affects: nvidia-graphics-drivers-450 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-450 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1909241 Title: Unreadable text with two monitors Status in nvidia-graphics-drivers-450 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: - Machine: Dell 15 Inspiron Gaming Laptop (7567) - External 1080p60 monitor connected (recognized by X as 1080i60). Changing resolution manually fixes the resolution until next reboot. When external monitor is already connected before boot, and turning system on, X calculates wrong resolution/dpi for the monitors, rendering fonts very small. On default Gnome3 desktop, only the window titles are affected. On Kubuntu, all SDDM items and several desktop resources are affected too, rendering Kubuntu desktop unusable. Running gome-tricks applet restore font size when clicking on "Fonts" and changing font sizes. On Kubuntu, changing font settings does not have any effect. One can run on a root terminal "xrandr --dpi 96" as a workaround. But it solves only for the next window opening of a program. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Dec 24 11:50:44 2020 DistUpgraded: 2020-08-23 11:50:00,001 DEBUG icon theme changed, re-reading DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 450.80.02, 5.4.0-48-generic, x86_64: installed nvidia, 450.80.02, 5.4.0-56-generic, x86_64: installed nvidia, 450.80.02, 5.4.0-58-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:0798] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0798] InstallationDate: Installed on 2020-03-22 (277 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 0c45:6a06 Microdia Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcEnviron: LANGUAGE=pt_BR: PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=0a93686d-0008-4b58-8574-fe382bc8eda1 ro locale=pt_BR quiet splash intel_iommu=on vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-08-23 (123 days ago) dmi.bios.date: 06/19/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0P84C9 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.asset.tag: H70NVN2 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Desktop-packages] [Bug 1873052] Re: Showing two cursors after login
** Tags added: groovy -- 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/1873052 Title: Showing two cursors after login Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: In Progress Status in gnome-shell source package in Focal: Confirmed Status in linux source package in Focal: Confirmed Status in mutter source package in Focal: Confirmed Status in xorg-server source package in Focal: Confirmed Bug description: Showing two cursors after login to ubuntu-desktop. One cursor moves and is scaled, and one is stationary mid screen and not scaled. The moving cursor does not appear on screenshots, making it difficult to upload a screenshot. Previously reported: https://gitlab.gnome.org/GNOME/mutter/issues/904 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428 Package: mutter 3.36.1-3ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 20:06:53 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-31 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873052/+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 1909108] Re: Second static mouse pointer on two screen setup
*** This bug is a duplicate of bug 1873052 *** https://bugs.launchpad.net/bugs/1873052 There are two known causes of this: 1. A bug in the 'amdgpu' kernel driver, supposedly fixed in future focal kernel 5.4.69. Not sure about the 5.8 kernel series you are using... 2. A bug in Ubuntu's fractional scaling support. Unfortunately you seem to be using both :( Still, bug 1873052 covers both. ** Package changed: xorg (Ubuntu) => ubuntu ** This bug has been marked a duplicate of bug 1873052 Showing two cursors after login -- 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/1909108 Title: Second static mouse pointer on two screen setup Status in Ubuntu: New Bug description: I have two screens and a Bluetooth mouse. When I wake PC up from the suspend the second frozen cursor is left on the screen. Screenshot tool does not see it. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 23 11:06:00 2020 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon Pro WX 4100] [1002:67e3] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon Pro WX 4100] [1002:0b0d] InstallationDate: Installed on 2020-12-15 (7 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Micro-Star International Co., Ltd. MS-7B89 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-33-generic root=UUID=2426cc97-af0d-4826-80aa-a05ec1ef1e8e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.70 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.70:bd04/21/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1909108/+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 1909132] Re: wavy diagonal line when scrolling in firefox
Does the problem only happen in full screen mode? Also, please attach a photo of the issue if you can. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1909132 Title: wavy diagonal line when scrolling in firefox Status in Ubuntu: Incomplete Bug description: Scrolling in Firefox moves the web page up and down, but also causes a wavy line to appear, that extends horizontally and diagonally across the page, and disappears once you stop scrolling. i use ubuntu20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 23 21:32:24 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-srv, 450.80.02, 5.4.0-58-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:1b10] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 930MX] [1043:1b10] InstallationDate: Installed on 2020-12-19 (4 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:3496 IMC Networks Bus 001 Device 003: ID 13d3:5a01 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless Keyboard/Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X542URV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-58-generic root=UUID=2b8aa80b-3a8c-4397-9c75-472b469e71ec ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X542URV.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X542URV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX542URV.308:bd05/21/2019:svnASUSTeKCOMPUTERINC.:pnX542URV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX542URV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X542URV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1909132/+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 1909006] Re: Split screen
Please: 1. Take a photo of the problem and attach it here. 2. Try selecting 'Ubuntu on Wayland' on the login screen just before you enter your password. Does a Wayland session have the same bug? ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1909006 Title: Split screen Status in xorg-server package in Ubuntu: Incomplete Bug description: My screen is split in 4 and forums have directed me to try and update my video graphics drivers ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 14:52:26 2020 DistUpgraded: 2020-08-03 22:59:11,316 DEBUG inhibit gnome-session idle DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [1179:fb30] InstallationDate: Installed on 2020-02-09 (316 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: TOSHIBA Satellite C850-F74T ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=ed9c77f9-c96b-4904-8ba9-1576f2c3a198 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-08-03 (140 days ago) dmi.bios.date: 08/31/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: PLCSF8 dmi.board.vendor: Intel dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr6.00:bd08/31/2012:svnTOSHIBA:pnSatelliteC850-F74T:pvrPSCBWF-011004F3:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite C850-F74T dmi.product.sku: PSCBWF dmi.product.version: PSCBWF-011004F3 dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1909006/+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 1908878] Re: gnome shell freezes for a couple of seconds, then it restarts (maybe it crashes?)
I think this is relevant: [ 7778.863305] ricsipontaz-home gnome-shell[5678]: Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? [ 7778.893251] ricsipontaz-home gnome-shell[5678]: Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? [ 7778.921755] ricsipontaz-home gnome-shell[5678]: Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? [ 7778.921980] ricsipontaz-home gnome-shell[5678]: Window manager warning: MetaSyncRing: Too many reboots -- disabling which I believe only happens with Nvidia (are you using Nvidia?). Most recently it was discussed in: https://gitlab.gnome.org/GNOME/mutter/-/issues/1561 but I also hoped I had fixed it in this proposed changed: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1309 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1561 https://gitlab.gnome.org/GNOME/mutter/-/issues/1561 ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/1561 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1908878 Title: gnome shell freezes for a couple of seconds, then it restarts (maybe it crashes?) Status in Mutter: Unknown Status in mutter package in Ubuntu: Incomplete Bug description: This is the line I always see in the log after the restart: Dec 21 09:33:55 ricsipontaz-home gsd-media-keys[5953]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shel l” on object at path /org/gnome/Shell ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 21 09:56:41 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-12-04 (17 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201203) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/usr/bin/zsh RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1908878/+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 1908878] Re: gnome shell freezes for a couple of seconds, then it restarts (maybe it crashes?)
Also the purple screen in your video in comment #2 does suggest a crash so please follow these steps: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1908878 Title: gnome shell freezes for a couple of seconds, then it restarts (maybe it crashes?) Status in Mutter: Unknown Status in mutter package in Ubuntu: Incomplete Bug description: This is the line I always see in the log after the restart: Dec 21 09:33:55 ricsipontaz-home gsd-media-keys[5953]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shel l” on object at path /org/gnome/Shell ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 21 09:56:41 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-12-04 (17 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201203) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/usr/bin/zsh RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1908878/+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 1909131] Re: [radeon] wayland - cursor is not affected by night light mode
** Summary changed: - wayland - cursor is not affected by night light mode + [radeon] wayland - cursor is not affected by night light mode ** Package changed: wayland (Ubuntu) => linux (Ubuntu) ** No longer affects: gnome-session (Ubuntu) ** Tags added: radeon -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1909131 Title: [radeon] wayland - cursor is not affected by night light mode Status in linux package in Ubuntu: New Bug description: Even with the night light mode activated, the cursor remains blue (the filter is not applied). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 23 14:54:37 2020 DistUpgraded: 2020-10-23 13:38:17,737 DEBUG /openCache(), new cache size 66390 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd RS780L [Radeon 3000] [1458:d000] InstallationDate: Installed on 2020-07-24 (151 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=b12510e7-1702-4d36-80bc-11251ef87185 ro quiet splash radeon.audio=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-10-23 (61 days ago) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: SEx dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909131/+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 1908801] Re: Acer Aspire E15 E5-511-POBM laptop internal keyboard & touchpad not working in kernel 5.4.0-54, but 5.4.0-42 works
*** This bug is a duplicate of bug 1895342 *** https://bugs.launchpad.net/bugs/1895342 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 1895342, 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. ** Summary changed: - Acer laptop internal keyboard & touchpad not working + Acer Aspire E15 E5-511-POBM laptop internal keyboard & touchpad not working in kernel 5.4.0-54, but 5.4.0-42 works ** Package changed: gdm3 (Ubuntu) => linux (Ubuntu) ** This bug has been marked a duplicate of bug 1895342 Acer Aspire E15 keyboard and trackpad non functional after update to vmlinuz-5.4.0-47-generic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1908801 Title: Acer Aspire E15 E5-511-POBM laptop internal keyboard & touchpad not working in kernel 5.4.0-54, but 5.4.0-42 works Status in linux package in Ubuntu: Confirmed Bug description: A fresh install of 20.04 from the live USB doesn't see internal keyboard or touchpad input on my Acer Aspire E15 E5-511-POBM. After much private investigation to no avail (https://askubuntu.com/questions/1275809/ubuntu-20-04-lts-laptop- internal-keyboard-and-touchpad-no-longer-work), I am prepared to assert this as a bug. I'll restate the relevant info here, but see the link for a more chronological account. And I guess, for what it's worth, I would also assert that this is reproducible by installing 20.04 on my specific laptop model. So, I boot up the laptop. I'm presented with GRUB boot menu. At this point the keyboard works, and if I choose advanced options and boot into a root shell I can type commands and do things that way as a last resort. However, all the problems seem to begin right from the start of the graphical session, even the login screen. This, in accordance with the instruction of https://wiki.ubuntu.com/Bugs/FindRightPackage#At_the_login_screen, is why I've filed this as a bug in gdm3. As I couldn't run the graphical bug program in Ubuntu, I ran the CLI in the root shell and attached the apport file here. I've tried to follow the relevant steps, but this is my first bug report so apologies if something is wrong. I first noticed this problem a few weeks after upgrading 18.04 to 20.04. Yes, for the first few weeks of using 20.04, there were no problems. And then, one day, I booted up and the keyboard and touchpad spontaneously stopped working. This was mysterious because to my memory I hadn't done any major upgrade or change to any part of the system the previous day. When the system is asleep / suspended, pressing a key or the touchpad easily wakes it up -- after which, they refuse to work again. The brightness key combos (Fn+←/→) and one that turns off the screen (Fn+F6) do work, but others such as volume (Fn+↑/↓) do not work. I see all expected key output when I run `sudo libinput debug-events --device /dev/input/event4 --show-keycodes` and type keys. When I plug in an external USB keyboard and mouse, they work correctly while the internal keyboard and touchpad remain the same. Outside of those specific situations, absolutely no internal keyboard input -- not even Ctrl+Alt+Del or Ctrl+Alt+F2 VT switching, let alone ordinary typing -- has any effect, and same with the touchpad. When I haven't had an external keyboard available I've used the on- screen keyboard to painstakingly run terminal commands by clicking each letter. However, sometimes the on-screen keyboard also stops sending keystrokes. The only concrete situation I can report is what I saw after resuming the system from sleep by opening the lid: at the login prompt on the lock screen, the onscreen keyboard came up, but didn't do anything when keys were clicked, forcing me to reboot. I had the following message in my `journalctl -b` logs: ``` The XKEYBOARD keymap compiler (xkbcomp) reports: Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: > Warning: Unsupported maximum keycode 569, clipping. Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: > X11 cannot support keycodes above 255. Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: > Internal error: Could not resolve keysym Invalid Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: Errors from xkbcomp are not fatal to the X server ``` This looks like it should have something to do with the keyboard issue. If it doesn't, then what is its significance? When I first investigated, I was on kernel
[Desktop-packages] [Bug 1892439] Re: [Lenovo ThinkPad T410s, Intel IbexPeak HDMI, Digital Out, HDMI] No sound at all
** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/1892439 Title: [Lenovo ThinkPad T410s, Intel IbexPeak HDMI, Digital Out, HDMI] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: ThinkPad T410s. No audio from DisplayPort. Can't even select it as the audio source. Video works fine ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: voorhees857 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 21:46:38 2020 InstallationDate: Installed on 2020-08-04 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: voorhees857 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [2901A3U, Intel IbexPeak HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET38WW (1.16 ) dmi.board.name: 2901A3U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET38WW(1.16):bd06/07/2010:svnLENOVO:pn2901A3U:pvrThinkPadT410s:rvnLENOVO:rn2901A3U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T410s dmi.product.name: 2901A3U dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1892439/+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 1908717] Re: Black screen with blinking cursor
You appear to have the 'oibaf' PPA installed which commonly causes graphics problems, and might be the problem here too. To remove all doubt, please uninstall that PPA using the 'ppa-purge' tool. Then if you experience any more problems please open a new bugs for them. ** Changed in: gdm3 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1908717 Title: Black screen with blinking cursor Status in gdm3 package in Ubuntu: Invalid Bug description: For some reason, since today GDM has ceased to work. No updates came through as last time I installed any updates was a week ago. Upon boot, gdm goes to a black screen with a cursor. This screen flickers to show the underlying tty and on each flicker the cursor position resets. I can start my window manager (sway) without issue from the console still and everything functions normally. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.36.3-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: sway Date: Fri Dec 18 13:44:09 2020 SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1908717/+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 1908758] Re: no more HDMI devices after upgrade to 20_04
*** This bug is a duplicate of bug 1892439 *** https://bugs.launchpad.net/bugs/1892439 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 1892439, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1892439 [Lenovo ThinkPad T410s, Intel IbexPeak HDMI, Digital Out, HDMI] No sound at all -- 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/1908758 Title: no more HDMI devices after upgrade to 20_04 Status in pulseaudio package in Ubuntu: New Bug description: Some two hours ago, I listened to audio through the extenal monitor, also used as display. Then I upgraded to 20_04 from 18_04. Now the display still works, but pulseaudio doesn't see nor offer the HDMI sink any longer on my lenovo T410s. What a bad mishap ... . And what to do now? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.8 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: udippel1690 F pulseaudio /dev/snd/pcmC0D0p: udippel1690 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Dec 18 22:35:06 2020 InstallationDate: Installed on 2018-08-30 (841 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-12-18 (0 days ago) dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET70WW (1.50 ) dmi.board.name: 2924WZ6 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2924WZ6:pvrThinkPadT410s:rvnLENOVO:rn2924WZ6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T410s dmi.product.name: 2924WZ6 dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908758/+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 1908758] Re: no more HDMI devices after upgrade to 20_04
*** This bug is a duplicate of bug 1892439 *** https://bugs.launchpad.net/bugs/1892439 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 1897965, 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. -- 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/1908758 Title: no more HDMI devices after upgrade to 20_04 Status in pulseaudio package in Ubuntu: New Bug description: Some two hours ago, I listened to audio through the extenal monitor, also used as display. Then I upgraded to 20_04 from 18_04. Now the display still works, but pulseaudio doesn't see nor offer the HDMI sink any longer on my lenovo T410s. What a bad mishap ... . And what to do now? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.8 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: udippel1690 F pulseaudio /dev/snd/pcmC0D0p: udippel1690 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Dec 18 22:35:06 2020 InstallationDate: Installed on 2018-08-30 (841 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-12-18 (0 days ago) dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET70WW (1.50 ) dmi.board.name: 2924WZ6 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2924WZ6:pvrThinkPadT410s:rvnLENOVO:rn2924WZ6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T410s dmi.product.name: 2924WZ6 dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908758/+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 1908608] Re: Crash to login screen when plugging in/out external monitor
Thanks. Unfortunately that crash report doesn't contain enough info, although it is from 17 December so that's good... To avoid those earlier assertions (which I assume are not the crash itself) please try deleting your monitor layout config: rm ~/.config/monitors.xml And to avoid confusion over earlier crash reports please also: sudo rm /var/crash/* Then tell us about any new crash reports that occur. Please also keep the extensions in comment #5 uninstalled to avoid any confusion. We don't support those extensions so finding out they are the cause of your crashes would not be useful information. -- 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/1908608 Title: Crash to login screen when plugging in/out external monitor Status in gnome-shell package in Ubuntu: Incomplete Bug description: This matches the title of https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1717170 but I don't want to assume it is the same considering that was allegedly fixed three years ago. journal: dec 17 23:12:51 computer-name kernel: usb 3-1: USB disconnect, device number 8 dec 17 23:12:51 computer-name kernel: usb 3-1.1: USB disconnect, device number 10 dec 17 23:12:51 computer-name acpid[716]: input device has been disconnected, fd 7 dec 17 23:12:51 computer-name gnome-shell[2891]: libinput error: event6 - bcm5974: client bug: event processing lagging behind by 42ms, your system is too slow dec 17 23:12:51 computer-name acpid[716]: input device has been disconnected, fd 8 dec 17 23:12:51 computer-name acpid[716]: input device has been disconnected, fd 15 dec 17 23:12:51 computer-name kernel: usb 3-1.4: USB disconnect, device number 9 dec 17 23:12:53 computer-name gnome-shell[2891]: meta_display_get_monitor_in_fullscreen: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed dec 17 23:12:53 computer-name fwupd[3384]: 22:12:53:0711 FuEngine nitrokey failed to change udev device /sys/devices/pci:00/:00:02.0/drm/card0: cannot ensure ID: FuUdevDevice: dec 17 23:12:53 computer-name fwupd[3384]: Unknown Device dec 17 23:12:53 computer-name fwupd[3384]: Flags:none dec 17 23:12:53 computer-name gnome-shell[2891]: DING: GNOME nautilus 3.38.1 dec 17 23:12:53 computer-name gnome-shell[2891]: meta_display_get_monitor_in_fullscreen: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed dec 17 23:12:53 computer-name gnome-shell[2891]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed dec 17 23:12:53 computer-name gnome-shell[2891]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). dec 17 23:12:55 computer-name gnome-shell[2891]: GNOME Shell crashed with signal 11 dec 17 23:12:55 computer-name gnome-shell[2891]: == Stack trace for context 0x55db60db91a0 == dec 17 23:13:06 computer-name nautilus[3814]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name unknown[3089]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name org.kde.kdeconnect.daemon.desktop[3092]: The Wayland connection broke. Did the Wayland compositor die? dec 17 23:13:06 computer-name gsd-power[3032]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name polkitd(authority=local)[738]: Unregistered Authentication Agent for unix-session:2 (system bus name :1.82, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale
