[Desktop-packages] [Bug 1772542] Re: after waking from sleep i get text radeon error message then return login screen (18.04 & 18.10)
hi I am also facing GPU lockup while playing videos in loop while true ; do mpv 'http://youtu.be/9J5CHTFWnTc' ; sleep 10 ; done [ 170.265582] radeon :01:00.0: ring 5 stalled for more than 10079msec [ 170.265590] radeon :01:00.0: GPU lockup (current fence id 0x03fb last fence id 0x03ff on ring 5) [ 170.272641] radeon :01:00.0: couldn't schedule ib [ 170.272689] [drm:radeon_uvd_suspend [radeon]] *ERROR* Error destroying UVD (-22)! [ 170.288733] radeon :01:00.0: Saved 729 dwords of commands on ring 0. [ 170.288740] radeon :01:00.0: GPU softreset: 0x0008 [ 170.288742] radeon :01:00.0: R_008010_GRBM_STATUS = 0xA0003028 For more details, check the other bug I submitted to linux package: https://bugs.launchpad.net/linux/+bug/1900854 -- 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/1772542 Title: after waking from sleep i get text radeon error message then return login screen (18.04 & 18.10) Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Triaged Bug description: // this bug was reported for 18.04. // I had just had it occur (first time) on 18.10 // new details will be comment @ end my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE desktops added) I sleep my XFCE (xubuntu) machine rather than turning it off at night. Today as with yesterday morning, instead of getting the locker-screen after hitting the power-button to wake my machine, i get a blank screen with a RADEON two-line text message top left on screen which appear only momentarily as screen is erased and I get the login/greeter screen. (it's happened 4-5 times, but does NOT happen every time) I can login fine, but my xfce session is new. I have grep'd for the message I see (yesterday & today), but can't find it as i usually recall little but the radeon word... sudo lshw -C video *-display description: VGA compatible controller product: Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:30 memory:e000-efff memory:f7de-f7df ioport:dc00(size=256) memory:c-d guiverc@d960-ubu2:/var/crash$ pwd /var/crash guiverc@d960-ubu2:/var/crash$ ls -la total 35332 drwxrwsrwt 2 rootwhoopsie 4096 May 22 09:41 . drwxr-xr-x 15 rootroot 4096 Nov 16 2017 .. -rw-r- 1 guiverc whoopsie50003 May 21 10:32 _usr_bin_caffeine.1000.crash -rw-r- 1 guiverc whoopsie 880121 May 21 10:33 _usr_bin_light-locker.1000.crash -rw-rw-r-- 1 guiverc whoopsie0 May 21 10:33 _usr_bin_light-locker.1000.upload -rw-r- 1 guiverc whoopsie 35234566 May 21 10:32 _usr_lib_xorg_Xorg.1000.crash (these files are dated yesteday - i didn't find anything for today) extract of /var/log/auth.log (copied from `view` hence line numbers) // last-night 48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) 49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) // overnight 52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session opened for user root by (uid=0) 53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session closed for user root 54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) 57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' finished. 58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): session closed for user guiverc 59 May 22 09:36:24 d960-ubu2 sudo: pam_unix(sudo:session): session closed for user root 60 May 22 09:36:26 d960-ubu2 sshd[1276]: Received SIGHUP; restarting. 61
[Desktop-packages] [Bug 1897934] Re: The initial sound level is set to zero (muted)
** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Low ** Summary changed: - The initial sound level is set to zero (muted) + [Intel HDA] The initial sound level is set to zero (muted) -- 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/1897934 Title: [Intel HDA] The initial sound level is set to zero (muted) Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: On boot into the live session - or on first install the sound level is muted. I have to use GNOME Control Center - Sounds to change to an appropriate level. Once changed the level chosen is correctly retained between reboots. This appears to be a regression from 20.04 where the sound level was set to - I guess - 80% on the live-session/first install ProblemType: BugDistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-budgie 5041 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: Budgie:GNOME Date: Wed Sep 30 16:03:08 2020 LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2016 dmi.bios.release: 15.31 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.22 dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897934/+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 1813441] Re: Can no longer drag and drop files between desktop and applications
You can't move around multiple icons on the desktop, only one by one. What's the bug number for that? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1813441 Title: Can no longer drag and drop files between desktop and applications Status in gnome-shell-extension-desktop-icons: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: Triaged Bug description: In releases before 19.04, you could drag and drop files from the desktop into applications. This no longer works. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-desktop-icons 19.01-1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 26 21:47:14 2019 InstallationDate: Installed on 2019-01-02 (24 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+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 1897934] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1897934 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1897934 Title: The initial sound level is set to zero (muted) Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: On boot into the live session - or on first install the sound level is muted. I have to use GNOME Control Center - Sounds to change to an appropriate level. Once changed the level chosen is correctly retained between reboots. This appears to be a regression from 20.04 where the sound level was set to - I guess - 80% on the live-session/first install ProblemType: BugDistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-budgie 5041 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: Budgie:GNOME Date: Wed Sep 30 16:03:08 2020 LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2016 dmi.bios.release: 15.31 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.22 dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897934/+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 1897934] Re: The initial sound level is set to zero (muted)
** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Invalid => New -- 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/1897934 Title: The initial sound level is set to zero (muted) Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: On boot into the live session - or on first install the sound level is muted. I have to use GNOME Control Center - Sounds to change to an appropriate level. Once changed the level chosen is correctly retained between reboots. This appears to be a regression from 20.04 where the sound level was set to - I guess - 80% on the live-session/first install ProblemType: BugDistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-budgie 5041 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: Budgie:GNOME Date: Wed Sep 30 16:03:08 2020 LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2016 dmi.bios.release: 15.31 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.22 dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897934/+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 1854912] Re: Installation stuck at 0%
[Expired for pinta (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pinta (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1854912 Title: Installation stuck at 0% Status in gnome-software package in Ubuntu: Expired Status in pinta package in Ubuntu: Expired Bug description: 1) Ubuntu 19.10 2) 3.30.6-2ubuntu10.19.10.0 3) I searched for "Pinta" in Unbuntu Software. I clicked the installation button, I expected it to install. 4) The install got stuck at 0% for several minutes. I was able to load a webpage, so my internet connection was good. I cancelled the installation of Pinta. Launch and Remove buttons appeared. If I click the launch button, nothing happens. Pinta is listed on the install screen. If I click the Remove button, I get a removal confirmation message. If I click the Remove button, there is a "Unable to remove Pinta" notification. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-28 (36 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.30.6-2ubuntu10.19.10.0 Package: gnome-software 3.30.6-2ubuntu10.19.10.0 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Tags: wayland-session eoan Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1854912/+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 1854912] Re: Installation stuck at 0%
[Expired for gnome-software (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-software (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1854912 Title: Installation stuck at 0% Status in gnome-software package in Ubuntu: Expired Status in pinta package in Ubuntu: Expired Bug description: 1) Ubuntu 19.10 2) 3.30.6-2ubuntu10.19.10.0 3) I searched for "Pinta" in Unbuntu Software. I clicked the installation button, I expected it to install. 4) The install got stuck at 0% for several minutes. I was able to load a webpage, so my internet connection was good. I cancelled the installation of Pinta. Launch and Remove buttons appeared. If I click the launch button, nothing happens. Pinta is listed on the install screen. If I click the Remove button, I get a removal confirmation message. If I click the Remove button, there is a "Unable to remove Pinta" notification. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-28 (36 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.30.6-2ubuntu10.19.10.0 Package: gnome-software 3.30.6-2ubuntu10.19.10.0 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Tags: wayland-session eoan Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1854912/+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 1900910] Re: Xorg freeze after closing lid and Suspend
This is probably due to the open source 'nouveau' driver the system is using. Please open the 'Additional Drivers' app and use it to install the Nvidia driver it recommends. If the problem continues to happen after that then next time the freeze occurs: 1. Wait for 10 seconds. 2. Reboot. 3. Run these commands: journalctl -b-1 > prevboot.txt lspci -kv > newlspci.txt and attach the resulting text files here. ** Tags added: nouveau ** Summary changed: - Xorg freeze after closing lid and Suspend + Screen freeze after closing lid and suspend ** 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/1900910 Title: Screen freeze after closing lid and suspend Status in Ubuntu: Incomplete Bug description: Starting a few days ago, after I close my laptop lid and Ubuntu suspends, I get only a black screen (and the power light is on) when I open the laptop lid. I tried various 3-finger salutes, and nothing changes. There is no cursor. I cannot get to the console screens. The only thing that works is holding the power button until the laptop shuts off. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-7642.46~1598628707~20.04~040157c~dev-generic 5.4.44 Uname: Linux 5.4.0-7642-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: [core,composite,opengl,decor,grid,move,compiztoolbox,gnomecompat,imgpng,resize,imgjpeg,regex,vpswitch,unitymtgrabhandles,snap,place,mousepoll,session,screenshot,resizeinfo,thumbnail,wall,animation,workarounds,expo,ezoom,staticswitcher,fade,scale,unityshell,dbus] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 21 14:25:22 2020 DistUpgraded: 2020-05-01 18:43:33,860 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: NVIDIA Corporation GM204M [GeForce GTX 980M] [10de:1617] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 980M] [1558:7703] InstallationDate: Installed on 2017-11-01 (1085 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: System76, Inc. Serval WS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-7642-generic root=UUID=fbf9e88e-c136-41b5-91a1-0848d0d8427a ro acpi_sleep=nonvs quiet splash snd_hda_intel.probe_mask=1 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-05-02 (172 days ago) dmi.bios.date: 07/11/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.10RSA1 dmi.board.asset.tag: Tag 12345 dmi.board.name: Serval WS dmi.board.vendor: System76, Inc. dmi.board.version: serw9 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.10RSA1:bd07/11/2016:svnSystem76,Inc.:pnServalWS:pvrserw9:rvnSystem76,Inc.:rnServalWS:rvrserw9:cvnSystem76,Inc.:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Serval WS dmi.product.sku: Not Applicable dmi.product.version: serw9 dmi.sys.vendor: System76, Inc. 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 20.0.8-0ubuntu1~20.04.1 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/+bug/1900910/+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 1900906] Re: Can't input accents in GNOME shell
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1900906 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Tags added: focal ** Also affects: ibus (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Changed in: ibus (Ubuntu) Status: New => Incomplete ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2046 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2046 -- 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/1900906 Title: Can't input accents in GNOME shell Status in gnome-shell package in Ubuntu: Incomplete Status in ibus package in Ubuntu: Incomplete Bug description: I'm running an up-to-date Ubuntu Focal. I have a standard Spanish keyboard. Under X, if I try to input an accentuated character, such as á or ü, in places like the search field in the overview or when writing a folder name in the app grid, nothing appears. Under Wayland, it fails each time on the first input of an accentuated character, then it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1900906/+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 1900906] Re: Can't input accents in GNOME shell
Possibly related: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2046 https://github.com/ibus/ibus/pull/2195 -- 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/1900906 Title: Can't input accents in GNOME shell Status in gnome-shell package in Ubuntu: Incomplete Status in ibus package in Ubuntu: Incomplete Bug description: I'm running an up-to-date Ubuntu Focal. I have a standard Spanish keyboard. Under X, if I try to input an accentuated character, such as á or ü, in places like the search field in the overview or when writing a folder name in the app grid, nothing appears. Under Wayland, it fails each time on the first input of an accentuated character, then it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1900906/+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 1900908] Re: Mutter doesn't apply gsettings appropriately to Wacom tablet
** Tags added: wacom ** Summary changed: - Mutter doesn't apply gsettings appropriately to Wacom tablet + Mutter doesn't apply gsettings appropriately to Wacom tablet on Xorg, but Wayland works ** Tags added: focal ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1476 https://gitlab.gnome.org/GNOME/mutter/-/issues/1476 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/1476 Importance: Unknown Status: Unknown ** Changed in: mutter (Ubuntu) Status: New => Confirmed ** Changed in: mutter (Ubuntu) Importance: Undecided => Medium -- 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/1900908 Title: Mutter doesn't apply gsettings appropriately to Wacom tablet on Xorg, but Wayland works Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: I have a Wacom Intuos VT M tablet in a setting with two monitors (laptop + external). Under an up-to-date Ubuntu Focal running X, if I map the tablet to a single monitor it fails to map it more often than not. A reliable way of getting failure is first connecting the tablet via bluetooth and then via USB. The only way to revert to a correct behavior is reseting X (ALT+F2 r). This is necessary even after rebooting. I've noticed that, when not working well, the problem is that Mutter sends the mapping data to the "Wacom Intuos BT M Pad pad" device, while it should be sending them to "Wacom Intuos BT M Pad stylus" (this is what it does when it works well). Under Wayland it works well (well, the tablet buttons don't work under Wayland but this is unrelated). PS I reported this bug against the Wacom X driver but was told it's really related to mutter (https://github.com/linuxwacom/xf86-input- wacom/issues/148). To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1900908/+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 1900873] Re: dual display scaling broken at 4k
Please run these commands: gsettings get org.gnome.mutter experimental-features > experimental.txt lspci -kv > lspci.txt journalctl -b0 > journal.txt xrandr --verbose > xrandr.txt and then attach the resulting text files here, along with a copy of your ~/.config/monitors.xml file. ** Tags added: xrandr-scaling ** Tags added: hybrid nvidia ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (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/1900873 Title: dual display scaling broken at 4k Status in gnome-control-center package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: I have to 4k monitors. 15" on the dell xps 3840/2160/60 40" philips external BDM4065 3840/2160/30 Obviously i need different scale factors to use them properly. This feature DOES NOT WORK. It seems the scaling is not handled separately per monitor as the UI suggests. The fractional scaling also does not seem to work. any change to the scaling ends seems to be rounded to full. Which meens a compromise scale of 125% is effectively 200% on the large monitor. I havent found any config which would make this useful. So basically when I use the external 40" I cannot use the builtin anymore without an external fresnell magnifier lens (which I dont have ;) updated Ubuntu 20.04.1 LTS on DELL XPS 7590 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz 32GB SODIMM DDR4 Synchronous 2667 (0.4ns) PCI bridge: NVIDIA TU117M [GeForce GTX 1650 Mobile / Max-Q] Hostbridge: Intel UHD Graphics 630 (Mobile) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 21 17:35:12 2020 InstallationDate: Installed on 2020-04-22 (181 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1900873/+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 1900760] Re: gnome-shell very high %CPU usage while moving mouse on Ubuntu 20.04
Thanks for all that. It appears the main CPU hog here is bug 1849142, which has a fix coming soon. So to exclude that bug and see if it is the main problem, please: 1. Open the Extensions app 2. Disable 'Ubuntu AppIndicators' 3. Reboot. 4. If the problem happens after that then please again run: apport-collect 1900760 -- 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/1900760 Title: gnome-shell very high %CPU usage while moving mouse on Ubuntu 20.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: After upgrade from 18.04 to 20.04 I discovered that gnome-shell occasionally starts eating up unreasonably large CPU %. After some head scratching why on earth i thappens, it was clear that moving my mouse energetically I can get it as close to 100% as I want. If this is relevant, the mouse model is Corsair Harpoon wireless BT. I am reading some speculation that the cause of the problem is high polling rate for mouse location (?). It is suggested in this bug entry (https://bugs.launchpad.net/bugs/1848951) that this issue is fixed on late march. But this is october and I still experience this problem on an updated PC. gnome-shell version on my system: 3.36.4-1ubuntu1~20.04.2 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-08-18 (794 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: lkp_Ubuntu_5_4_0_48_52_generic_72 nvidia_modeset nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-04 (16 days ago) UserGroups: adm cdrom dialout dip docker kvm lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1900760/+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 1899953] Re: Crackling audio on Raspberry Pi Desktop
** Also affects: pulseaudio via https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/762 Importance: Unknown Status: Unknown ** Also affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Changed in: pulseaudio (Ubuntu) Status: New => Invalid ** Also affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New -- 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/1899953 Title: Crackling audio on Raspberry Pi Desktop Status in PulseAudio: Unknown Status in linux-raspi package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: New Status in pulseaudio package in Ubuntu: Invalid Bug description: Attempting to play audio (e.g. from rhythmbox) on the raspberry pi desktop image, results in broken up / crackling audio. The "tsched=0" workaround noted in https://wiki.ubuntu.com/Audio/PositionReporting#Turning_off_PulseAudio_timer_scheduling successfully avoids the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1899953/+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 1813441] Re: Can no longer drag and drop files between desktop and applications
> I was quite surprised to find the icons on the Desktop not navigable with arrow keys. That's bug 1855711. > Also, I couldn't cut and paste files to and from the Desktop. That's bug 1857014. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1813441 Title: Can no longer drag and drop files between desktop and applications Status in gnome-shell-extension-desktop-icons: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: Triaged Bug description: In releases before 19.04, you could drag and drop files from the desktop into applications. This no longer works. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-desktop-icons 19.01-1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 26 21:47:14 2019 InstallationDate: Installed on 2019-01-02 (24 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+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 1857014] Re: Unable to paste files from Nautilus to the desktop
** Tags removed: eoan ** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1857014 Title: Unable to paste files from Nautilus to the desktop Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Bug description: 1) Ubuntu 19.10 2) Files app 1:3.34.1-1ubuntu1 3) Open Files app. Copy file. Right click on Desktop. Select paste. 4) Unable to paste the file to the desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1857014/+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 1897185] Re: Laptop docked with lid closed, goes to sleep immediately on login
No fix for bug 1872159 has been released yet, so I think it's just pure luck at the moment. -- 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/1897185 Title: Laptop docked with lid closed, goes to sleep immediately on login Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Ubuntu 20.04's software updater just applied quite a few updates affecting grub and nvidia. The modules should show in the report just submitted. Also, updates to initramfs had just installed a few days ago. Kudos in that these updates fixed two login/startup issues: I'd been affected by the compression change for initramfs and had started getting the spinning ubuntu circle on the logon splash screen, apparently due to an nvidia driver conflict. I'd turned the splash screen to nosplash, and have now been able to set it back to splash. Both of those issues now appear to be fixed. BUT now when I start Ubuntu with the T570 laptop docked, lid closed, external display and keyboard via the dock: as soon as I enter the login password and press enter, the system goes into suspend. If I then press the dock power button again, the system will resume and proceed normally. It seems that the new startup modules don't realize that the machine is docked; and/or that it erroneously now "detects" the closed lid as a change in lid state during startup, triggering suspend. Prior to today's updates, this was not an issue. I would appreciate seeing this corrected. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.25 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Sep 24 18:15:31 2020 InstallationDate: Installed on 2020-06-22 (94 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: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897185/+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 1897934] Re: The initial sound level is set to zero (muted)
** Summary changed: - The initial sound level is set to zero (mute) + The initial sound level is set to zero (muted) -- 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/1897934 Title: The initial sound level is set to zero (muted) Status in Release Notes for Ubuntu: New Status in alsa-driver package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Bug description: On boot into the live session - or on first install the sound level is muted. I have to use GNOME Control Center - Sounds to change to an appropriate level. Once changed the level chosen is correctly retained between reboots. This appears to be a regression from 20.04 where the sound level was set to - I guess - 80% on the live-session/first install ProblemType: BugDistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-budgie 5041 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: Budgie:GNOME Date: Wed Sep 30 16:03:08 2020 LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2016 dmi.bios.release: 15.31 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.22 dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897934/+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 1899962] Re: Wrong audio output device selected on Raspberry Pi Desktop
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1899962 ** Tags added: iso-testing -- 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/1899962 Title: Wrong audio output device selected on Raspberry Pi Desktop Status in pulseaudio package in Ubuntu: New Bug description: On each boot, an incorrect audio output device is selected, at least when HDMI audio output is in use (still need to test the TV/aux output; will update the bug when done). Specifically, the settings application lists "Multichannel Output - Built-in Audio" as the selected output device. However, for audio to play through the connected HDMI device, "Analog Output - Built-in Audio" must be selected instead. Unfortunately, this setting will be lost on subsequent boots. A workaround is to remove the following lines from /etc/pulse/default.pa: ### Use hot-plugged devices like Bluetooth or USB automatically (LP: #1702794) .ifexists module-switch-on-connect.so load-module module-switch-on-connect .endif However, removal of these lines will (as the comment suggests) result in hot-plugged USB devices *not* being automatically selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1899962/+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 1900910] Re: Xorg freeze after closing lid and Suspend
The same thing happens when I lock my screen. When I come back, the power has shut off. Pressing the power button starts what looks like a power-up, but it ends up with just a black screen. None of the keys seem to do anything. I have to power-cycle my laptop to get it to work again. -- 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/1900910 Title: Xorg freeze after closing lid and Suspend Status in xorg package in Ubuntu: New Bug description: Starting a few days ago, after I close my laptop lid and Ubuntu suspends, I get only a black screen (and the power light is on) when I open the laptop lid. I tried various 3-finger salutes, and nothing changes. There is no cursor. I cannot get to the console screens. The only thing that works is holding the power button until the laptop shuts off. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-7642.46~1598628707~20.04~040157c~dev-generic 5.4.44 Uname: Linux 5.4.0-7642-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: [core,composite,opengl,decor,grid,move,compiztoolbox,gnomecompat,imgpng,resize,imgjpeg,regex,vpswitch,unitymtgrabhandles,snap,place,mousepoll,session,screenshot,resizeinfo,thumbnail,wall,animation,workarounds,expo,ezoom,staticswitcher,fade,scale,unityshell,dbus] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 21 14:25:22 2020 DistUpgraded: 2020-05-01 18:43:33,860 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: NVIDIA Corporation GM204M [GeForce GTX 980M] [10de:1617] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 980M] [1558:7703] InstallationDate: Installed on 2017-11-01 (1085 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: System76, Inc. Serval WS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-7642-generic root=UUID=fbf9e88e-c136-41b5-91a1-0848d0d8427a ro acpi_sleep=nonvs quiet splash snd_hda_intel.probe_mask=1 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-05-02 (172 days ago) dmi.bios.date: 07/11/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.10RSA1 dmi.board.asset.tag: Tag 12345 dmi.board.name: Serval WS dmi.board.vendor: System76, Inc. dmi.board.version: serw9 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.10RSA1:bd07/11/2016:svnSystem76,Inc.:pnServalWS:pvrserw9:rvnSystem76,Inc.:rnServalWS:rvrserw9:cvnSystem76,Inc.:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Serval WS dmi.product.sku: Not Applicable dmi.product.version: serw9 dmi.sys.vendor: System76, Inc. 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 20.0.8-0ubuntu1~20.04.1 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/xorg/+bug/1900910/+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 1872230] Re: The left Ctrl key does not work when using pointer location
I recently updated to 20.04.1 and experienced a similar issue as described in comment #3. To reproduce the issue: 1) Enable "Locate Pointer" in Settings -> Universal Access -> Pointing & Clicking 2) Open Firefox, go to https://duckduckgo.com 3) Enter search text, e.g. "test test test" 4) Click in the search textbox after results are returned 5) Use Ctrl-Left and Ctrl-Right to jump between words in the search textbox 6) Disable "Locate Pointer" to see the problem go away. -- 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/1872230 Title: The left Ctrl key does not work when using pointer location Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: I am using 20.04 Focal. I am using a US international keyboard layout with dead keys, so that I can enter text in many different languages. After I had rebooted my system today and so loaded the newest GNOME Shell, the left Ctrl key stopped working in the terminal windows and also in emacs, while the right Ctrl still works. To get the left Ctrl working again I have to switch to a plain US English keyboard layout, without dead keys. I have also tried the different alternatives of US International keyboard layouts, each of them seems to work as intended but the left Ctrl key is not working. Only with plain US English layout I get the left Ctrl working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872230/+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 1897934] Re: The initial sound level is set to zero (mute)
Just an FYI. I noticed this first 09-25 (that I can see from comments on IRC) with a Xubuntu QA-test (most will be in comments in QA-test reports on iso.qa.ubuntu.com), only recently added a much later report is (now a duplicate of this). I got the impression the value (sound volume) wasn't always consistent (I mainly test Lubuntu) and seemed box specific.. It'd changed mid-late September, but I never considered this a big concern (no responses whenever I asked on IRC, or to my lp bug report) so I never explored it much. It was easily worked around I felt. -- 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/1897934 Title: The initial sound level is set to zero (mute) Status in Release Notes for Ubuntu: New Status in alsa-driver package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Bug description: On boot into the live session - or on first install the sound level is muted. I have to use GNOME Control Center - Sounds to change to an appropriate level. Once changed the level chosen is correctly retained between reboots. This appears to be a regression from 20.04 where the sound level was set to - I guess - 80% on the live-session/first install ProblemType: BugDistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-budgie 5041 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: Budgie:GNOME Date: Wed Sep 30 16:03:08 2020 LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2016 dmi.bios.release: 15.31 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.22 dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897934/+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 1870795] Re: Appindicator not showing under wayland
On a fully up to date install of Ubuntu focal, I confirmed that the bug still existing using the current version gnome-shell-extension- appindicator/33.1. I then installed and tested the new version gnome- shell-extension-appindicator/33.1-0ubuntu0.20.04.1 and can confirm the bug no longer occurs with the steps outlined in the top description. Thanks for the fix. -- 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/1870795 Title: Appindicator not showing under wayland Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator source package in Focal: Fix Committed Bug description: [ Impact ] An app-indicator icon does not show when I login using the default gnome session (wayland). If I choose the xorg session, the icon shows as normal. Under wayland, the icon does appear if I lock my session then log back in. [ Test case ] Run a desktop session (better if Ubuntu wayland), ensure that all the startup-launched appindicators are showing in the status area. One affected indicator seems to be https://github.com/juliagoda/antimicroX/ [ Regression potential ] Indicators may not load at all, wrong icons are shown instead. --- Upstream change: https://github.com/ubuntu/gnome-shell-extension- appindicator/pull/231 $ lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 $ apt-cache policy gnome-session-wayland gnome-session-wayland: Installed: (none) Candidate: 3.36.0-2ubuntu1 Version table: 3.36.0-2ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu focal/universe i386 Packages ProblemType: BugDistroRelease: Ubuntu 20.04 Package: gnome-session-wayland (not installed) ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Apr 4 15:30:40 2020 InstallationDate: Installed on 2019-12-15 (111 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)SourcePackage: gnome-session UpgradeStatus: Upgraded to focal on 2020-03-10 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1870795/+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 1897934] Re: The initial sound level is set to zero (mute)
The alsa-driver package hasn't changed since 2015. This is almost certainly either a pulseaudio bug or a kernel bug. ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Invalid -- 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/1897934 Title: The initial sound level is set to zero (mute) Status in Release Notes for Ubuntu: New Status in alsa-driver package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Bug description: On boot into the live session - or on first install the sound level is muted. I have to use GNOME Control Center - Sounds to change to an appropriate level. Once changed the level chosen is correctly retained between reboots. This appears to be a regression from 20.04 where the sound level was set to - I guess - 80% on the live-session/first install ProblemType: BugDistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-budgie 5041 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: Budgie:GNOME Date: Wed Sep 30 16:03:08 2020 LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2016 dmi.bios.release: 15.31 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.22 dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897934/+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 1900908] Re: Mutter doesn't apply gsettings appropriately to Wacom tablet
** Description changed: I have a Wacom Intuos VT M tablet in a setting with two monitors (laptop + external). Under an up-to-date Ubuntu Focal running X, if I map the tablet to a single monitor it fails to map it more often than not. A reliable way of getting failure is first connecting the tablet via bluetooth and then via USB. The only way to revert to a correct behavior is reseting X (ALT+F2 r). This is necessary even after rebooting. I've noticed that, when not working well, the problem is that Mutter sends the mapping data to the "Wacom Intuos BT M Pad pad" device, while it should be sending them to "Wacom Intuos BT M Pad stylus" (this is what it does when it works well). Under Wayland it works well (well, the tablet buttons don't work under Wayland but this is unrelated). + + PS I reported this bug agains the Wacom X driver but was told it's + really related to mutter (https://github.com/linuxwacom/xf86-input- + wacom/issues/148). ** Description changed: I have a Wacom Intuos VT M tablet in a setting with two monitors (laptop + external). Under an up-to-date Ubuntu Focal running X, if I map the tablet to a single monitor it fails to map it more often than not. A reliable way of getting failure is first connecting the tablet via bluetooth and then via USB. The only way to revert to a correct behavior is reseting X (ALT+F2 r). This is necessary even after rebooting. I've noticed that, when not working well, the problem is that Mutter sends the mapping data to the "Wacom Intuos BT M Pad pad" device, while it should be sending them to "Wacom Intuos BT M Pad stylus" (this is what it does when it works well). Under Wayland it works well (well, the tablet buttons don't work under Wayland but this is unrelated). - PS I reported this bug agains the Wacom X driver but was told it's + PS I reported this bug against the Wacom X driver but was told it's really related to mutter (https://github.com/linuxwacom/xf86-input- wacom/issues/148). -- 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/1900908 Title: Mutter doesn't apply gsettings appropriately to Wacom tablet Status in mutter package in Ubuntu: New Bug description: I have a Wacom Intuos VT M tablet in a setting with two monitors (laptop + external). Under an up-to-date Ubuntu Focal running X, if I map the tablet to a single monitor it fails to map it more often than not. A reliable way of getting failure is first connecting the tablet via bluetooth and then via USB. The only way to revert to a correct behavior is reseting X (ALT+F2 r). This is necessary even after rebooting. I've noticed that, when not working well, the problem is that Mutter sends the mapping data to the "Wacom Intuos BT M Pad pad" device, while it should be sending them to "Wacom Intuos BT M Pad stylus" (this is what it does when it works well). Under Wayland it works well (well, the tablet buttons don't work under Wayland but this is unrelated). PS I reported this bug against the Wacom X driver but was told it's really related to mutter (https://github.com/linuxwacom/xf86-input- wacom/issues/148). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1900908/+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 1899953] Re: Crackling audio on Raspberry Pi Desktop
Hmm, this looks like someone reported exactly this about a year ago: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/762 Unfortunately it's closed with "approach the driver maintainer". ** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #762 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/762 -- 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/1899953 Title: Crackling audio on Raspberry Pi Desktop Status in pulseaudio package in Ubuntu: New Bug description: Attempting to play audio (e.g. from rhythmbox) on the raspberry pi desktop image, results in broken up / crackling audio. The "tsched=0" workaround noted in https://wiki.ubuntu.com/Audio/PositionReporting#Turning_off_PulseAudio_timer_scheduling successfully avoids the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1899953/+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 1900910] [NEW] Xorg freeze after closing lid and Suspend
Public bug reported: Starting a few days ago, after I close my laptop lid and Ubuntu suspends, I get only a black screen (and the power light is on) when I open the laptop lid. I tried various 3-finger salutes, and nothing changes. There is no cursor. I cannot get to the console screens. The only thing that works is holding the power button until the laptop shuts off. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-7642.46~1598628707~20.04~040157c~dev-generic 5.4.44 Uname: Linux 5.4.0-7642-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: [core,composite,opengl,decor,grid,move,compiztoolbox,gnomecompat,imgpng,resize,imgjpeg,regex,vpswitch,unitymtgrabhandles,snap,place,mousepoll,session,screenshot,resizeinfo,thumbnail,wall,animation,workarounds,expo,ezoom,staticswitcher,fade,scale,unityshell,dbus] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 21 14:25:22 2020 DistUpgraded: 2020-05-01 18:43:33,860 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: NVIDIA Corporation GM204M [GeForce GTX 980M] [10de:1617] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 980M] [1558:7703] InstallationDate: Installed on 2017-11-01 (1085 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: System76, Inc. Serval WS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-7642-generic root=UUID=fbf9e88e-c136-41b5-91a1-0848d0d8427a ro acpi_sleep=nonvs quiet splash snd_hda_intel.probe_mask=1 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-05-02 (172 days ago) dmi.bios.date: 07/11/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.10RSA1 dmi.board.asset.tag: Tag 12345 dmi.board.name: Serval WS dmi.board.vendor: System76, Inc. dmi.board.version: serw9 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.10RSA1:bd07/11/2016:svnSystem76,Inc.:pnServalWS:pvrserw9:rvnSystem76,Inc.:rnServalWS:rvrserw9:cvnSystem76,Inc.:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Serval WS dmi.product.sku: Not Applicable dmi.product.version: serw9 dmi.sys.vendor: System76, Inc. 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 20.0.8-0ubuntu1~20.04.1 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze possible-manual-nvidia-install third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1900910 Title: Xorg freeze after closing lid and Suspend Status in xorg package in Ubuntu: New Bug description: Starting a few days ago, after I close my laptop lid and Ubuntu suspends, I get only a black screen (and the power light is on) when I open the laptop lid. I tried various 3-finger salutes, and nothing changes. There is no cursor. I cannot get to the console screens. The only thing that works is holding the power button until the laptop shuts off. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-7642.46~1598628707~20.04~040157c~dev-generic 5.4.44 Uname: Linux 5.4.0-7642-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: [core,composite,opengl,decor,grid,move,compiztoolbox,gnomecompat,imgpng,resize,imgjpeg,regex,vpswitch,unitymtgrabhandles,snap,place,mousepoll,session,screenshot,resizeinfo,thumbnail,wall,animation,workarounds,expo,ezoom,staticswitcher,fade,scale,unityshell,dbus] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 21 14:25:22 2020 DistUpgraded: 2020-05-01 18:43:33,860 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py'
[Desktop-packages] [Bug 1900906] Re: Can't input accents in GNOME shell
** Description changed: - I have a standard Spanish keyboard. If I try to input an accentuated - character, such as á or ü, in places like the search field in the - overview or when writing a folder name in the app grid, nothing appears. + I'm running an up-to-date Ubuntu Focal. I have a standard Spanish + keyboard. Under X, if I try to input an accentuated character, such as á + or ü, in places like the search field in the overview or when writing a + folder name in the app grid, nothing appears. Under Wayland, it fails + each time on the first input of an accentuated character, then it works. -- 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/1900906 Title: Can't input accents in GNOME shell Status in gnome-shell package in Ubuntu: New Bug description: I'm running an up-to-date Ubuntu Focal. I have a standard Spanish keyboard. Under X, if I try to input an accentuated character, such as á or ü, in places like the search field in the overview or when writing a folder name in the app grid, nothing appears. Under Wayland, it fails each time on the first input of an accentuated character, then it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1900906/+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 1900908] [NEW] Mutter doesn't apply gsettings appropriately to Wacom tablet
Public bug reported: I have a Wacom Intuos VT M tablet in a setting with two monitors (laptop + external). Under an up-to-date Ubuntu Focal running X, if I map the tablet to a single monitor it fails to map it more often than not. A reliable way of getting failure is first connecting the tablet via bluetooth and then via USB. The only way to revert to a correct behavior is reseting X (ALT+F2 r). This is necessary even after rebooting. I've noticed that, when not working well, the problem is that Mutter sends the mapping data to the "Wacom Intuos BT M Pad pad" device, while it should be sending them to "Wacom Intuos BT M Pad stylus" (this is what it does when it works well). Under Wayland it works well (well, the tablet buttons don't work under Wayland but this is unrelated). ** Affects: mutter (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/1900908 Title: Mutter doesn't apply gsettings appropriately to Wacom tablet Status in mutter package in Ubuntu: New Bug description: I have a Wacom Intuos VT M tablet in a setting with two monitors (laptop + external). Under an up-to-date Ubuntu Focal running X, if I map the tablet to a single monitor it fails to map it more often than not. A reliable way of getting failure is first connecting the tablet via bluetooth and then via USB. The only way to revert to a correct behavior is reseting X (ALT+F2 r). This is necessary even after rebooting. I've noticed that, when not working well, the problem is that Mutter sends the mapping data to the "Wacom Intuos BT M Pad pad" device, while it should be sending them to "Wacom Intuos BT M Pad stylus" (this is what it does when it works well). Under Wayland it works well (well, the tablet buttons don't work under Wayland but this is unrelated). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1900908/+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 1900906] [NEW] Can't input accents in GNOME shell
Public bug reported: I have a standard Spanish keyboard. If I try to input an accentuated character, such as á or ü, in places like the search field in the overview or when writing a folder name in the app grid, nothing appears. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1900906 Title: Can't input accents in GNOME shell Status in gnome-shell package in Ubuntu: New Bug description: I have a standard Spanish keyboard. If I try to input an accentuated character, such as á or ü, in places like the search field in the overview or when writing a folder name in the app grid, nothing appears. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1900906/+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 1897934] Re: The initial sound level is set to zero (mute)
** Also affects: ubuntu-release-notes Importance: Undecided Status: New -- 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/1897934 Title: The initial sound level is set to zero (mute) Status in Release Notes for Ubuntu: New Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: On boot into the live session - or on first install the sound level is muted. I have to use GNOME Control Center - Sounds to change to an appropriate level. Once changed the level chosen is correctly retained between reboots. This appears to be a regression from 20.04 where the sound level was set to - I guess - 80% on the live-session/first install ProblemType: BugDistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-budgie 5041 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: Budgie:GNOME Date: Wed Sep 30 16:03:08 2020 LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2016 dmi.bios.release: 15.31 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.22 dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897934/+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 1781049] Re: WiFi hard blocked after resuming laptop from suspend
I can confirm this behavior on an HP 340s G7. Ubuntu 20.04 5.4.0-51-generic Network controller: Intel Corporation Killer Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW) (rev 30) -- 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/1781049 Title: WiFi hard blocked after resuming laptop from suspend Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: I installed a fresh copy of Ubuntu 18.04 and everything seems to work fine, till I suspended and resumed the laptop. After resume, the wifi is hard blocked is rfkill. Reinstalling drivers, different drivers, nothing helped. All this was done under Secure Boot disabled under Ubuntu and BIOS (UEFI). The WiFI card is Realtek 8723BE. laptop is HP AB035TX Pavilion 15. If any further info is required, I'll add it on notification. I am familiar with Linux, any help will be really appreciated. P.S: If this wifi card is the issue, please suggest some PCI-mini card that will work with my Ubuntu, even after suspend and resume (Ideally a 2.4/5G + BT 5.0) Thank you all! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mythreya 1281 F pulseaudio /dev/snd/controlC1: mythreya 1281 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-06-26 (16 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.1.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.6 metric 600 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. Bus 001 Device 002: ID 05c8:0379 Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Pavilion Notebook NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=300b2c4a-387a-49b5-9cb6-93de471ebbdb ro quiet splash nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/26/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.87 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8096 dmi.board.vendor: Hewlett-Packard dmi.board.version: 89.33 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.87:bd02/26/2018:svnHewlett-Packard:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8096:rvr89.33:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2018-06-30T14:39:45.608645 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2018-06-28T16:23:51.596655 nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NETGEAR71 1a9d81bf-e7f5-4f8a-956f-96180dc493e1 wifi 1531450229 Thu 12 Jul 2018 09:50:29 PM CDT yes 0 no /org/freedesktop/NetworkManager/Settings/2 yes wlo1activated /org/freedesktop/NetworkManager/ActiveConnection/2 -- Ethernet 81087af0-5c8d-451f-84c0-1a95c6034098 ethernet 1530214661 Thu 28 Jun 2018 02:37:41 PM CDT yes 0 no /org/freedesktop/NetworkManager/Settings/1 no -- -- --
[Desktop-packages] [Bug 1813441] Re: Can no longer drag and drop files between desktop and applications
I was quite surprised to find the icons on the Desktop not navigable with arrow keys. Also, I couldn't cut and paste files to and from the Desktop. For many years, I have always replaced Nautilus with Nemo, it's so much more flexible. I managed to get the Desktop in a great state using Nemo, following the steps outlined here: https://askubuntu.com/questions/1066752/how-to-set-nemo-as-the-default- file-manager-in-ubuntu-18-04/1173861#1173861 I would suggest the Ubuntu software managers to replace Nautilus with Nemo, it seems like the logical choice, by far. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1813441 Title: Can no longer drag and drop files between desktop and applications Status in gnome-shell-extension-desktop-icons: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: Triaged Bug description: In releases before 19.04, you could drag and drop files from the desktop into applications. This no longer works. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-desktop-icons 19.01-1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 26 21:47:14 2019 InstallationDate: Installed on 2019-01-02 (24 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+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 1897934] Re: The initial sound level is set to zero (mute)
I'm not entirely certain this is a great test case but given that the sound is not 0% with Ubuntu 20.04 LTS, I believe it is. kvm -m 4096 -boot d -cdrom ubuntu-20.04-desktop-amd64.iso -nic none -soundhw hda -hda /srv/vms/groovy.qcow2 Sound is not at 0. kvm -m 4096 -boot d -cdrom groovy-desktop-amd64.iso -nic none -soundhw hda -hda /srv/vms/groovy.qcow2 Sound is at 0, with both of these I was using the Ubuntu Desktop iso. -- 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/1897934 Title: The initial sound level is set to zero (mute) Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: On boot into the live session - or on first install the sound level is muted. I have to use GNOME Control Center - Sounds to change to an appropriate level. Once changed the level chosen is correctly retained between reboots. This appears to be a regression from 20.04 where the sound level was set to - I guess - 80% on the live-session/first install ProblemType: BugDistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-budgie 5041 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: Budgie:GNOME Date: Wed Sep 30 16:03:08 2020 LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2016 dmi.bios.release: 15.31 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.22 dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1897934/+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 1897934] Re: [HP 14-ac100na N9S73EA#ABU] The initial sound level is set to zero (mute)
Tested the Ubuntu and Ubuntu MATE 20201021.2 ISOs on Lenovo SL500. This bug breaks whole LiveDVD experience. The installer does not play greeting sound. The sound can be unmuted from `alsamixer`, but it is unexpected at all. Should be fixed before final release. ** Summary changed: - [HP 14-ac100na N9S73EA#ABU] The initial sound level is set to zero (mute) + The initial sound level is set to zero (mute) -- 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/1897934 Title: The initial sound level is set to zero (mute) Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: On boot into the live session - or on first install the sound level is muted. I have to use GNOME Control Center - Sounds to change to an appropriate level. Once changed the level chosen is correctly retained between reboots. This appears to be a regression from 20.04 where the sound level was set to - I guess - 80% on the live-session/first install ProblemType: BugDistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-budgie 5041 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: Budgie:GNOME Date: Wed Sep 30 16:03:08 2020 LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2016 dmi.bios.release: 15.31 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.22 dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1897934/+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 1897784] Re: /usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Re
This looks similar to https://bugs.documentfoundation.org/show_bug.cgi?id=131083, which the reporter could originally trigger fairly reliably, but ended up marking resolved because after installing updates the crash went away for them. The steps to reproduce were to simply open libreoffice calc, use the mouse to create a vertical selection of two or more consecutive cells, and then click the cross in the window decorations to close calc. This would trigger the crash at least once in every ten runs, according to the reporter. I tested this a good number of times in a fully up-to-date Kubuntu 20.04 amd64 VM, without triggering any crash. According to the crash report on errors.ubuntu.com, the crash is still being reported on a daily basis with libreoffice 1:6.4.6-0ubuntu0.20.04.1. ** Bug watch added: Document Foundation Bugzilla #131083 https://bugs.documentfoundation.org/show_bug.cgi?id=131083 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1897784 Title: /usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Reference:Qt5MimeData::~Qt5MimeData:Qt5MimeData::~Qt5MimeData Status in LibreOffice: New Status in libreoffice package in Ubuntu: Triaged Status in libreoffice source package in Focal: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding libreoffice. This problem was most recently seen with package version 1:6.4.6-0ubuntu0.20.04.1, the problem page at https://errors.ubuntu.com/problem/cfc41540ed80c870e8fb93c32ad7df0b7391f1b7 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/df-libreoffice/+bug/1897784/+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 1897934] Re: [HP 14-ac100na N9S73EA#ABU] The initial sound level is set to zero (mute)
** Description changed: On boot into the live session - or on first install the sound level is muted. I have to use GNOME Control Center - Sounds to change to an appropriate level. Once changed the level chosen is correctly retained between reboots. - This appears to be a regression from 18.04 where the sound level was set + This appears to be a regression from 20.04 where the sound level was set to - I guess - 80% on the live-session/first install - ProblemType: Bug - DistroRelease: Ubuntu 20.10 + ProblemType: BugDistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: ubuntu-budgie 5041 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: ubuntu-budgie 5041 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: Budgie:GNOME Date: Wed Sep 30 16:03:08 2020 LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash - SourcePackage: pulseaudio + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bashSourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2016 dmi.bios.release: 15.31 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.22 dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1897934 Title: [HP 14-ac100na N9S73EA#ABU] The initial sound level is set to zero (mute) Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: On boot into the live session - or on first install the sound level is muted. I have to use GNOME Control Center - Sounds to change to an appropriate level. Once changed the level chosen is correctly retained between reboots. This appears to be a regression from 20.04 where the sound level was set to - I guess - 80% on the live-session/first install ProblemType: BugDistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-budgie 5041 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: Budgie:GNOME Date: Wed Sep 30 16:03:08 2020 LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2016 dmi.bios.release: 15.31 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.22 dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1897934/+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 1897934] Re: [HP 14-ac100na N9S73EA#ABU] The initial sound level is set to zero (mute)
This breaks Screen Reader installs for Visually impaired users and breaks testcase #1305 -- 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/1897934 Title: [HP 14-ac100na N9S73EA#ABU] The initial sound level is set to zero (mute) Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: On boot into the live session - or on first install the sound level is muted. I have to use GNOME Control Center - Sounds to change to an appropriate level. Once changed the level chosen is correctly retained between reboots. This appears to be a regression from 18.04 where the sound level was set to - I guess - 80% on the live-session/first install ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-budgie 5041 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: Budgie:GNOME Date: Wed Sep 30 16:03:08 2020 LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2016 dmi.bios.release: 15.31 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.22 dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1897934/+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 1897185] Re: Laptop docked with lid closed, goes to sleep immediately on login
NOTE that I'm not seeing this since today's fix for 1872159 (the spinning logo splash hang on startup). Are these related? Something has changed; but I'm not sure whether it's truly fixed? Thanks... -- 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/1897185 Title: Laptop docked with lid closed, goes to sleep immediately on login Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Ubuntu 20.04's software updater just applied quite a few updates affecting grub and nvidia. The modules should show in the report just submitted. Also, updates to initramfs had just installed a few days ago. Kudos in that these updates fixed two login/startup issues: I'd been affected by the compression change for initramfs and had started getting the spinning ubuntu circle on the logon splash screen, apparently due to an nvidia driver conflict. I'd turned the splash screen to nosplash, and have now been able to set it back to splash. Both of those issues now appear to be fixed. BUT now when I start Ubuntu with the T570 laptop docked, lid closed, external display and keyboard via the dock: as soon as I enter the login password and press enter, the system goes into suspend. If I then press the dock power button again, the system will resume and proceed normally. It seems that the new startup modules don't realize that the machine is docked; and/or that it erroneously now "detects" the closed lid as a change in lid state during startup, triggering suspend. Prior to today's updates, this was not an issue. I would appreciate seeing this corrected. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.25 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Sep 24 18:15:31 2020 InstallationDate: Installed on 2020-06-22 (94 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: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897185/+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 1897934] Re: [HP 14-ac100na N9S73EA#ABU] The initial sound level is set to zero (mute)
This is occurring on 20.10 Ubuntu MATE 20201021.2 -- 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/1897934 Title: [HP 14-ac100na N9S73EA#ABU] The initial sound level is set to zero (mute) Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: On boot into the live session - or on first install the sound level is muted. I have to use GNOME Control Center - Sounds to change to an appropriate level. Once changed the level chosen is correctly retained between reboots. This appears to be a regression from 18.04 where the sound level was set to - I guess - 80% on the live-session/first install ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-budgie 5041 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: Budgie:GNOME Date: Wed Sep 30 16:03:08 2020 LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2016 dmi.bios.release: 15.31 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.22 dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1897934/+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 1895839] Re: CVE-2020-24977
** Changed in: libxml2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1895839 Title: CVE-2020-24977 Status in libxml2 package in Ubuntu: Confirmed Status in libxml2 package in Debian: Unknown Bug description: GNOME project libxml2 v2.9.10 and earlier have a global buffer over- read vulnerability in xmlEncodeEntitiesInternal at libxml2/entities.c. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-24977 Upstream patch: https://gitlab.gnome.org/GNOME/libxml2/-/commit/50f06b3efb638efb0abd95dc62dca05ae67882c2 Bug report: https://gitlab.gnome.org/GNOME/libxml2/-/issues/178 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1895839/+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 1900873] [NEW] dual display scaling broken at 4k
Public bug reported: I have to 4k monitors. 15" on the dell xps 3840/2160/60 40" philips external BDM4065 3840/2160/30 Obviously i need different scale factors to use them properly. This feature DOES NOT WORK. It seems the scaling is not handled separately per monitor as the UI suggests. The fractional scaling also does not seem to work. any change to the scaling ends seems to be rounded to full. Which meens a compromise scale of 125% is effectively 200% on the large monitor. I havent found any config which would make this useful. So basically when I use the external 40" I cannot use the builtin anymore without an external fresnell magnifier lens (which I dont have ;) updated Ubuntu 20.04.1 LTS on DELL XPS 7590 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz 32GB SODIMM DDR4 Synchronous 2667 (0.4ns) PCI bridge: NVIDIA TU117M [GeForce GTX 1650 Mobile / Max-Q] Hostbridge: Intel UHD Graphics 630 (Mobile) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 21 17:35:12 2020 InstallationDate: Installed on 2020-04-22 (181 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1900873 Title: dual display scaling broken at 4k Status in gnome-control-center package in Ubuntu: New Bug description: I have to 4k monitors. 15" on the dell xps 3840/2160/60 40" philips external BDM4065 3840/2160/30 Obviously i need different scale factors to use them properly. This feature DOES NOT WORK. It seems the scaling is not handled separately per monitor as the UI suggests. The fractional scaling also does not seem to work. any change to the scaling ends seems to be rounded to full. Which meens a compromise scale of 125% is effectively 200% on the large monitor. I havent found any config which would make this useful. So basically when I use the external 40" I cannot use the builtin anymore without an external fresnell magnifier lens (which I dont have ;) updated Ubuntu 20.04.1 LTS on DELL XPS 7590 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz 32GB SODIMM DDR4 Synchronous 2667 (0.4ns) PCI bridge: NVIDIA TU117M [GeForce GTX 1650 Mobile / Max-Q] Hostbridge: Intel UHD Graphics 630 (Mobile) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 21 17:35:12 2020 InstallationDate: Installed on 2020-04-22 (181 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1900873/+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 1900870] [NEW] maybe nvidia drivers should pick the highest one with lrm, if more than one is available
Public bug reported: nvidia-graphics-drivers-455 got introduced without matching lrm build but 450 is available with lrm. Currently ubiquity / ubuntu-drivers picks the highest matching drivers, irrespective if they need dkms or lrm. It would be nice if it could pick highest one with lrm; if none found, highest one with dkms. ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1900870 Title: maybe nvidia drivers should pick the highest one with lrm, if more than one is available Status in ubuntu-drivers-common package in Ubuntu: New Bug description: nvidia-graphics-drivers-455 got introduced without matching lrm build but 450 is available with lrm. Currently ubiquity / ubuntu-drivers picks the highest matching drivers, irrespective if they need dkms or lrm. It would be nice if it could pick highest one with lrm; if none found, highest one with dkms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1900870/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
On Tue, Oct 20, 2020 at 09:28:54AM -, Benjamin Rogoll wrote: >Hey there guy, can anyone tell me what im doing wrong with the patch >provided in #217. The tutorial in #211 doesnt work for me. > >p_$$/tmp.o; mkdir -p >/home/benjamin/Downloads/i2c-hid_standalone(1)/i2c-hid_standalone/.tmp_$$; >trap "rm -rf >/home/benjamin/Downloads/i2c-hid_standalone(1)/i2c-hid_standalone/.tmp_$$" >EXIT; if ( echo "int main() {}" | gcc -xc -o /dev/null -lelf -) >/dev/null >2>&1; then echo "1"; else echo "0"; fi' >/bin/sh: -c: line 0: syntax error near unexpected token `(' >/bin/sh: -c: line 0: `make -f ./scripts/Makefile.build >obj=/home/benjamin/Downloads/i2c-hid_standalone(1)/i2c-hid_standalone \' >make: *** [Makefile:1752: >/home/benjamin/Downloads/i2c-hid_standalone(1)/i2c-hid_standalone] Error 1 >make: Leaving directory '/usr/lib/modules/5.8.16-2-MANJARO/build' > >help much appreciated > Can you run "make V=1" to have more verbose output? Btw, I would suggest you to try #189 instead because polling could consume a little more power than interrupting. -- 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/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
[Desktop-packages] [Bug 1899955] Re: FFe: Replace default wallpaper in Groovy
As there was no further discussion and we already have (hopefully) final release candidates for 20.10, marking as 'Won't Fix' for the wallpaper. ** Changed in: ubuntu-wallpapers (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1899955 Title: FFe: Replace default wallpaper in Groovy Status in ubiquity-slideshow-ubuntu package in Ubuntu: Fix Released Status in ubuntu-wallpapers package in Ubuntu: Won't Fix Bug description: Changing the default wallpaper from the existing Groovy Gorilla illustration to the one featuring Raspberry Pi tinted sunglasses. For the default desktop wallpaper we'll need to revert https://launchpad.net/ubuntu/+source/ubuntu-settings/20.10.2 and https://launchpad.net/ubuntu/+source/ubuntu- wallpapers/20.10.2-0ubuntu1 and update the warty-final-ubuntu.png and also include the with the plain sunglasses mascot wallpaper as an option. The background wallpaper for Ubiquity slideshow should also be changed to use the version featuring the mascot wearing Raspberry Pi tinted sunglasses. The benefit is to pay homage to the work various teams have been doing with the Raspberry Pi foundation and to their product. It's a way to signal our commitment to making their platform great and deepen our relationship with the Pi foundation. Any additional information which would be helpful in considering the decision The concerns people have are of product placement and forcing something onto peoples machines. There are several arguments against this, the option to change to the default easily, that there is no direct link to Raspberry Pi anything and its quite subtle. But ultimately the reason is we want to make a splash with the Raspberry Pi and arm in general and this is a very good way to do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity-slideshow-ubuntu/+bug/1899955/+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 1900760] Re: gnome-shell very high %CPU usage while moving mouse on Ubuntu 20.04
Whoa, there's a lot of info in those apport files. I hope those are relevant. I don't use any fancy Gnome shell extensions. Here's an output of `ls /usr/share/gnome-shell/extensions/`: desktop-icons@csoriano ubuntu-appindicat...@ubuntu.com ubuntu- d...@ubuntu.com That's about it. It's hard to tell right now if the problem surfaces only after locking/unlocking routine. I can confirm that when I was submitting this bug report, the system has indeed went through several sleep and wake-up cycles, and, of course, there was a lock screen every time a wake-up happened. -- 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/1900760 Title: gnome-shell very high %CPU usage while moving mouse on Ubuntu 20.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: After upgrade from 18.04 to 20.04 I discovered that gnome-shell occasionally starts eating up unreasonably large CPU %. After some head scratching why on earth i thappens, it was clear that moving my mouse energetically I can get it as close to 100% as I want. If this is relevant, the mouse model is Corsair Harpoon wireless BT. I am reading some speculation that the cause of the problem is high polling rate for mouse location (?). It is suggested in this bug entry (https://bugs.launchpad.net/bugs/1848951) that this issue is fixed on late march. But this is october and I still experience this problem on an updated PC. gnome-shell version on my system: 3.36.4-1ubuntu1~20.04.2 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-08-18 (794 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: lkp_Ubuntu_5_4_0_48_52_generic_72 nvidia_modeset nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-04 (16 days ago) UserGroups: adm cdrom dialout dip docker kvm lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1900760/+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 1900760] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1900760/+attachment/5425029/+files/GsettingsChanges.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/1900760 Title: gnome-shell very high %CPU usage while moving mouse on Ubuntu 20.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: After upgrade from 18.04 to 20.04 I discovered that gnome-shell occasionally starts eating up unreasonably large CPU %. After some head scratching why on earth i thappens, it was clear that moving my mouse energetically I can get it as close to 100% as I want. If this is relevant, the mouse model is Corsair Harpoon wireless BT. I am reading some speculation that the cause of the problem is high polling rate for mouse location (?). It is suggested in this bug entry (https://bugs.launchpad.net/bugs/1848951) that this issue is fixed on late march. But this is october and I still experience this problem on an updated PC. gnome-shell version on my system: 3.36.4-1ubuntu1~20.04.2 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-08-18 (794 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: lkp_Ubuntu_5_4_0_48_52_generic_72 nvidia_modeset nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-04 (16 days ago) UserGroups: adm cdrom dialout dip docker kvm lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1900760/+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 1900760] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1900760/+attachment/5425033/+files/monitors.xml.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/1900760 Title: gnome-shell very high %CPU usage while moving mouse on Ubuntu 20.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: After upgrade from 18.04 to 20.04 I discovered that gnome-shell occasionally starts eating up unreasonably large CPU %. After some head scratching why on earth i thappens, it was clear that moving my mouse energetically I can get it as close to 100% as I want. If this is relevant, the mouse model is Corsair Harpoon wireless BT. I am reading some speculation that the cause of the problem is high polling rate for mouse location (?). It is suggested in this bug entry (https://bugs.launchpad.net/bugs/1848951) that this issue is fixed on late march. But this is october and I still experience this problem on an updated PC. gnome-shell version on my system: 3.36.4-1ubuntu1~20.04.2 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-08-18 (794 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: lkp_Ubuntu_5_4_0_48_52_generic_72 nvidia_modeset nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-04 (16 days ago) UserGroups: adm cdrom dialout dip docker kvm lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1900760/+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 1900760] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1900760/+attachment/5425032/+files/ShellJournal.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/1900760 Title: gnome-shell very high %CPU usage while moving mouse on Ubuntu 20.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: After upgrade from 18.04 to 20.04 I discovered that gnome-shell occasionally starts eating up unreasonably large CPU %. After some head scratching why on earth i thappens, it was clear that moving my mouse energetically I can get it as close to 100% as I want. If this is relevant, the mouse model is Corsair Harpoon wireless BT. I am reading some speculation that the cause of the problem is high polling rate for mouse location (?). It is suggested in this bug entry (https://bugs.launchpad.net/bugs/1848951) that this issue is fixed on late march. But this is october and I still experience this problem on an updated PC. gnome-shell version on my system: 3.36.4-1ubuntu1~20.04.2 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-08-18 (794 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: lkp_Ubuntu_5_4_0_48_52_generic_72 nvidia_modeset nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-04 (16 days ago) UserGroups: adm cdrom dialout dip docker kvm lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1900760/+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 1900760] Re: gnome-shell very high %CPU usage while moving mouse on Ubuntu 20.04
apport information ** Tags added: apport-collected ** Description changed: After upgrade from 18.04 to 20.04 I discovered that gnome-shell occasionally starts eating up unreasonably large CPU %. After some head scratching why on earth i thappens, it was clear that moving my mouse energetically I can get it as close to 100% as I want. If this is relevant, the mouse model is Corsair Harpoon wireless BT. I am reading some speculation that the cause of the problem is high polling rate for mouse location (?). It is suggested in this bug entry (https://bugs.launchpad.net/bugs/1848951) that this issue is fixed on late march. But this is october and I still experience this problem on an updated PC. gnome-shell version on my system: 3.36.4-1ubuntu1~20.04.2 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.9 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2018-08-18 (794 days ago) + InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) + NonfreeKernelModules: lkp_Ubuntu_5_4_0_48_52_generic_72 nvidia_modeset nvidia + Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 + RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 + Tags: focal + Uname: Linux 5.4.0-48-generic x86_64 + UpgradeStatus: Upgraded to focal on 2020-10-04 (16 days ago) + UserGroups: adm cdrom dialout dip docker kvm lpadmin plugdev sambashare sudo vboxusers + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1900760/+attachment/5425028/+files/Dependencies.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/1900760 Title: gnome-shell very high %CPU usage while moving mouse on Ubuntu 20.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: After upgrade from 18.04 to 20.04 I discovered that gnome-shell occasionally starts eating up unreasonably large CPU %. After some head scratching why on earth i thappens, it was clear that moving my mouse energetically I can get it as close to 100% as I want. If this is relevant, the mouse model is Corsair Harpoon wireless BT. I am reading some speculation that the cause of the problem is high polling rate for mouse location (?). It is suggested in this bug entry (https://bugs.launchpad.net/bugs/1848951) that this issue is fixed on late march. But this is october and I still experience this problem on an updated PC. gnome-shell version on my system: 3.36.4-1ubuntu1~20.04.2 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-08-18 (794 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: lkp_Ubuntu_5_4_0_48_52_generic_72 nvidia_modeset nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-04 (16 days ago) UserGroups: adm cdrom dialout dip docker kvm lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1900760/+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 1900760] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1900760/+attachment/5425030/+files/ProcCpuinfoMinimal.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/1900760 Title: gnome-shell very high %CPU usage while moving mouse on Ubuntu 20.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: After upgrade from 18.04 to 20.04 I discovered that gnome-shell occasionally starts eating up unreasonably large CPU %. After some head scratching why on earth i thappens, it was clear that moving my mouse energetically I can get it as close to 100% as I want. If this is relevant, the mouse model is Corsair Harpoon wireless BT. I am reading some speculation that the cause of the problem is high polling rate for mouse location (?). It is suggested in this bug entry (https://bugs.launchpad.net/bugs/1848951) that this issue is fixed on late march. But this is october and I still experience this problem on an updated PC. gnome-shell version on my system: 3.36.4-1ubuntu1~20.04.2 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-08-18 (794 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: lkp_Ubuntu_5_4_0_48_52_generic_72 nvidia_modeset nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-04 (16 days ago) UserGroups: adm cdrom dialout dip docker kvm lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1900760/+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 1900760] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1900760/+attachment/5425031/+files/ProcEnviron.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/1900760 Title: gnome-shell very high %CPU usage while moving mouse on Ubuntu 20.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: After upgrade from 18.04 to 20.04 I discovered that gnome-shell occasionally starts eating up unreasonably large CPU %. After some head scratching why on earth i thappens, it was clear that moving my mouse energetically I can get it as close to 100% as I want. If this is relevant, the mouse model is Corsair Harpoon wireless BT. I am reading some speculation that the cause of the problem is high polling rate for mouse location (?). It is suggested in this bug entry (https://bugs.launchpad.net/bugs/1848951) that this issue is fixed on late march. But this is october and I still experience this problem on an updated PC. gnome-shell version on my system: 3.36.4-1ubuntu1~20.04.2 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-08-18 (794 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: lkp_Ubuntu_5_4_0_48_52_generic_72 nvidia_modeset nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-04 (16 days ago) UserGroups: adm cdrom dialout dip docker kvm lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1900760/+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 1872159] Re: Boot animation never finishes when external monitors (or just more than one) are connected
** No longer affects: gdm3 (Ubuntu) ** No longer affects: gdm3 (Ubuntu Focal) ** No longer affects: gdm3 (Ubuntu Groovy) -- 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/1872159 Title: Boot animation never finishes when external monitors (or just more than one) are connected Status in Plymouth: Unknown Status in plymouth package in Ubuntu: In Progress Status in plymouth source package in Focal: Triaged Status in plymouth source package in Groovy: In Progress Bug description: I think this is a problem with the splash boot loader. This problem is not reproduced if using nosplash. I have installed 20.04 to this laptop. Thinkpad T480, i7, intel graphics. Clean install of 20.04 beta, not an upgrade. When booting from the install, the greeter screen is never reached if external monitors are connected at startup. I get the spinning ubuntu logo, and nothing more. I can not change to virtual terminals. The fsck step does not commence. In recovery mood, I can log in. With no external monitors attached, it works. I am used to having such problems with Nvidia graphics is involved, but this is not the case on this laptop. It has been happily running 18.04. External displays are recognised if they are connected after login. Also, when I edit /etc/default/grub so that it reads GRUB_CMDLINE_LINUX_DEFAULT="" (that is, splash disabled) it works fine with two external monitors attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 13:58:19 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 20L5S00F00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=/dev/mapper/myvg-root ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5S00F00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5S00F00 dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/plymouth/+bug/1872159/+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 1897934] Re: [HP 14-ac100na N9S73EA#ABU] The initial sound level is set to zero (mute)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (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/1897934 Title: [HP 14-ac100na N9S73EA#ABU] The initial sound level is set to zero (mute) Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: On boot into the live session - or on first install the sound level is muted. I have to use GNOME Control Center - Sounds to change to an appropriate level. Once changed the level chosen is correctly retained between reboots. This appears to be a regression from 18.04 where the sound level was set to - I guess - 80% on the live-session/first install ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-budgie 5041 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: Budgie:GNOME Date: Wed Sep 30 16:03:08 2020 LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2016 dmi.bios.release: 15.31 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.22 dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1897934/+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 1897934] Re: [HP 14-ac100na N9S73EA#ABU] The initial sound level is set to zero (mute)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1897934 Title: [HP 14-ac100na N9S73EA#ABU] The initial sound level is set to zero (mute) Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: On boot into the live session - or on first install the sound level is muted. I have to use GNOME Control Center - Sounds to change to an appropriate level. Once changed the level chosen is correctly retained between reboots. This appears to be a regression from 18.04 where the sound level was set to - I guess - 80% on the live-session/first install ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-budgie 5041 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: Budgie:GNOME Date: Wed Sep 30 16:03:08 2020 LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2016 dmi.bios.release: 15.31 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.22 dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1897934/+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 1875845] Re: keyring cannot be unlocked if used fingerprint to login gnome session
Same bug since yesterday's update ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1875845 Title: keyring cannot be unlocked if used fingerprint to login gnome session Status in GNOME Keyring: Unknown Status in gnome-keyring package in Ubuntu: Triaged Bug description: I upgraded to Ubuntu 20.04 and setup the fingerprint login. Today when I tried to launch remmina it didn't show up for a long time. I launch Gnome Password and Keys > Passwords > Login I see there's a button to click to unlock. Clicking the unlock button is still waiting forever. A moment later I logout current session and type in the user password to login. Then I could launch remmina and unlock the Gnome Password and Keys. System info ❯ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 ~ ❯ apt-cache policy gnome-keyring gnome-keyring: Installed: 3.36.0-1ubuntu1 Candidate: 3.36.0-1ubuntu1 Version table: *** 3.36.0-1ubuntu1 500 500 http://ftp.cuhk.edu.hk/pub/Linux/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/1875845/+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 1872159] Re: Boot animation never finishes when external monitors (or just more than one) are connected
I now know enough to be sure it's a plymouth bug, not gdm: https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/118#note_668662 ** Changed in: gdm3 (Ubuntu Focal) Status: Confirmed => Invalid ** Changed in: gdm3 (Ubuntu Groovy) Status: In Progress => 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/1872159 Title: Boot animation never finishes when external monitors (or just more than one) are connected Status in Plymouth: Unknown Status in gdm3 package in Ubuntu: Invalid Status in plymouth package in Ubuntu: In Progress Status in gdm3 source package in Focal: Invalid Status in plymouth source package in Focal: Triaged Status in gdm3 source package in Groovy: Invalid Status in plymouth source package in Groovy: In Progress Bug description: I think this is a problem with the splash boot loader. This problem is not reproduced if using nosplash. I have installed 20.04 to this laptop. Thinkpad T480, i7, intel graphics. Clean install of 20.04 beta, not an upgrade. When booting from the install, the greeter screen is never reached if external monitors are connected at startup. I get the spinning ubuntu logo, and nothing more. I can not change to virtual terminals. The fsck step does not commence. In recovery mood, I can log in. With no external monitors attached, it works. I am used to having such problems with Nvidia graphics is involved, but this is not the case on this laptop. It has been happily running 18.04. External displays are recognised if they are connected after login. Also, when I edit /etc/default/grub so that it reads GRUB_CMDLINE_LINUX_DEFAULT="" (that is, splash disabled) it works fine with two external monitors attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 13:58:19 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 20L5S00F00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=/dev/mapper/myvg-root ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5S00F00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5S00F00 dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/plymouth/+bug/1872159/+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 1900263] Re: In Hebrew environment, clock is reversed: minutes are shown before hours
This bug was fixed in the package language-pack-gnome-he - 1:20.10+20201015build1 --- language-pack-gnome-he (1:20.10+20201015build1) groovy; urgency=medium * Backport a fix for clocks being displayed reversed (lp: #1900263) -- Sebastien Bacher Tue, 20 Oct 2020 10:23:17 +0200 ** Changed in: language-pack-gnome-he (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1900263 Title: In Hebrew environment, clock is reversed: minutes are shown before hours Status in gnome-desktop: Unknown Status in gnome-desktop3 package in Ubuntu: Fix Committed Status in language-pack-gnome-he package in Ubuntu: Fix Released Bug description: * Impact Ubuntu 20.10, normal gnome session. After recent updates, using right-to-left environment, such as Hebrew, the clock on top of the screen shows the time in reverse. For example, instead of showing 17:59,it shows 59:17. See attached screenshot. * Test case - install the hebrew language packs - select the locale - restart the session the clock on the top panel should display the hours on the left * Regression potential Check the clock in some of the other gnome-desktop API users (gnome- clocks, gnome-control-center, etc) -- ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14 Uname: Linux 5.8.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sat Oct 17 19:02:30 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-05 (773 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-09-17 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/1900263/+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 1900263] Re: In Hebrew environment, clock is reversed: minutes are shown before hours
Thanks for confirming, I uploaded the change now and it got accepted so should be in before release -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1900263 Title: In Hebrew environment, clock is reversed: minutes are shown before hours Status in gnome-desktop: Unknown Status in gnome-desktop3 package in Ubuntu: Fix Committed Status in language-pack-gnome-he package in Ubuntu: Fix Committed Bug description: * Impact Ubuntu 20.10, normal gnome session. After recent updates, using right-to-left environment, such as Hebrew, the clock on top of the screen shows the time in reverse. For example, instead of showing 17:59,it shows 59:17. See attached screenshot. * Test case - install the hebrew language packs - select the locale - restart the session the clock on the top panel should display the hours on the left * Regression potential Check the clock in some of the other gnome-desktop API users (gnome- clocks, gnome-control-center, etc) -- ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14 Uname: Linux 5.8.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sat Oct 17 19:02:30 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-05 (773 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-09-17 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/1900263/+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 1900812] Re: pulseaudio crashed with SIGSEGV in pa_sink_move_streams_to_default_sink() from report_jack_state() from mixer_class_event() from hctl_elem_event_handler() from snd
** Summary changed: - /usr/bin/pulseaudio:11:pa_sink_move_streams_to_default_sink:report_jack_state:mixer_class_event:hctl_elem_event_handler:snd_hctl_elem_throw_event + pulseaudio crashed with SIGSEGV in pa_sink_move_streams_to_default_sink() from report_jack_state() from mixer_class_event() from hctl_elem_event_handler() from snd_hctl_elem_throw_event() -- 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/1900812 Title: pulseaudio crashed with SIGSEGV in pa_sink_move_streams_to_default_sink() from report_jack_state() from mixer_class_event() from hctl_elem_event_handler() from snd_hctl_elem_throw_event() Status in pulseaudio package in Ubuntu: Fix Committed Bug description: * Impact There is a segfault issue started with the recent update * Test case We don't have specific steps to trigger the issue so test for regression and verify that reports stop on https://errors.ubuntu.com/problem/31c6bfaf0ac65939a763307ca3d3a4f27f38e9f0 * Regression potential The regression was created by a fix for gnome-control-center device selection issues, check that the settings still work correctly, allowing to change devices and showing the active one as selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1900812/+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 1900812] Re: /usr/bin/pulseaudio:11:pa_sink_move_streams_to_default_sink:report_jack_state:mixer_class_event:hctl_elem_event_handler:snd_hctl_elem_throw_event
** Changed in: pulseaudio (Ubuntu) Importance: Undecided => High ** Changed in: pulseaudio (Ubuntu) Status: New => Fix Committed ** Description changed: - The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:13.99.2-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/31c6bfaf0ac65939a763307ca3d3a4f27f38e9f0 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/. + * Impact + + There is a segfault issue started with the recent update + + * Test case + + We don't have specific steps to trigger the issue so test for regression and verify that reports stop on + https://errors.ubuntu.com/problem/31c6bfaf0ac65939a763307ca3d3a4f27f38e9f0 + + * Regression potential + + The regression was created by a fix for gnome-control-center device + selection issues, check that the settings still work correctly, allowing + to change devices and showing the active one as selected -- 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/1900812 Title: /usr/bin/pulseaudio:11:pa_sink_move_streams_to_default_sink:report_jack_state:mixer_class_event:hctl_elem_event_handler:snd_hctl_elem_throw_event Status in pulseaudio package in Ubuntu: Fix Committed Bug description: * Impact There is a segfault issue started with the recent update * Test case We don't have specific steps to trigger the issue so test for regression and verify that reports stop on https://errors.ubuntu.com/problem/31c6bfaf0ac65939a763307ca3d3a4f27f38e9f0 * Regression potential The regression was created by a fix for gnome-control-center device selection issues, check that the settings still work correctly, allowing to change devices and showing the active one as selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1900812/+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 1900812] [NEW] /usr/bin/pulseaudio:11:pa_sink_move_streams_to_default_sink:report_jack_state:mixer_class_event:hctl_elem_event_handler:snd_hctl_elem_throw_event
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:13.99.2-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/31c6bfaf0ac65939a763307ca3d3a4f27f38e9f0 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: pulseaudio (Ubuntu) Importance: High Status: Fix Committed ** Tags: groovy -- 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/1900812 Title: /usr/bin/pulseaudio:11:pa_sink_move_streams_to_default_sink:report_jack_state:mixer_class_event:hctl_elem_event_handler:snd_hctl_elem_throw_event Status in pulseaudio package in Ubuntu: Fix Committed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:13.99.2-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/31c6bfaf0ac65939a763307ca3d3a4f27f38e9f0 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/pulseaudio/+bug/1900812/+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 1900263] Re: In Hebrew environment, clock is reversed: minutes are shown before hours
** Also affects: language-pack-gnome-he (Ubuntu) Importance: Undecided Status: New ** Changed in: language-pack-gnome-he (Ubuntu) Importance: Undecided => High ** Changed in: language-pack-gnome-he (Ubuntu) Status: New => Fix Committed ** Description changed: + * Impact + Ubuntu 20.10, normal gnome session. After recent updates, using right-to-left environment, such as Hebrew, the clock on top of the screen shows the time in reverse. For example, instead of showing 17:59,it shows 59:17. See attached screenshot. + + * Test case + - install the hebrew language packs + - select the locale + - restart the session + + the clock on the top panel should display the hours on the left + + * Regression potential + + Check the clock in some of the other gnome-desktop API users (gnome- + clocks, gnome-control-center, etc) + + -- ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14 Uname: Linux 5.8.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sat Oct 17 19:02:30 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-05 (773 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-09-17 (30 days ago) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1900263 Title: In Hebrew environment, clock is reversed: minutes are shown before hours Status in gnome-desktop: Unknown Status in gnome-desktop3 package in Ubuntu: Fix Committed Status in language-pack-gnome-he package in Ubuntu: Fix Committed Bug description: * Impact Ubuntu 20.10, normal gnome session. After recent updates, using right-to-left environment, such as Hebrew, the clock on top of the screen shows the time in reverse. For example, instead of showing 17:59,it shows 59:17. See attached screenshot. * Test case - install the hebrew language packs - select the locale - restart the session the clock on the top panel should display the hours on the left * Regression potential Check the clock in some of the other gnome-desktop API users (gnome- clocks, gnome-control-center, etc) -- ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14 Uname: Linux 5.8.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sat Oct 17 19:02:30 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-05 (773 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-09-17 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/1900263/+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 1900797] Re: The triangle at the top of the calendar, system tray pop up doesn't go away when the pop is closed
*** This bug is a duplicate of bug 1870523 *** https://bugs.launchpad.net/bugs/1870523 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 1870523, 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 1870523 [llvm] Top bar - residual BoxPointer arrows -- 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/1900797 Title: The triangle at the top of the calendar, system tray pop up doesn't go away when the pop is closed Status in gnome-shell package in Ubuntu: New Bug description: On the Ubuntu Groovy installation inside a VirtualBox 6.1.16 virtual machine, using the latest Groovy ISO, the following issue happens: * Click on the date/time indicator at the center of the top panel. * The date/time, calendar popup opens. * Click outside the popup and the popup closes. * However, the white triangle at the top of the popup stays in the screen even after the popup is closed. * Clicking once more on the desktop makes it go away. * The same behaviour can be seen even on the system tray/notification area popup. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 21 11:37:15 2020 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'gtk-theme' b"'Yaru-dark'" b'org.gnome.desktop.privacy' b'report-technical-problems' b'true' InstallationDate: Installed on 2020-10-21 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 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/1900797/+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 1870523] Re: [llvm] Top bar - residual BoxPointer arrows (triangles) when using software rendering (virtual machines)
** Summary changed: - [llvm] Top bar - residual BoxPointer arrows + [llvm] Top bar - residual BoxPointer arrows (triangles) when using software rendering (virtual machines) -- 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/1870523 Title: [llvm] Top bar - residual BoxPointer arrows (triangles) when using software rendering (virtual machines) Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Hello, Ubuntu 20.04 beta (Apr 2nd 2020) 1. Click the top bar date section and click again to close As a result you have a white arrow beneath the date section. Use mouse over or click to desktop to fix and remove the arrow 2. The same applies to Activities and the right top bar section If you click to open a menu and then click to close. The white arrow remains. See the attached screenshot --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 GsettingsChanges: b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.notifications' b'application-children' b"['update-manager']" b'org.gnome.desktop.peripherals.keyboard' b'numlock-state' b'true' b'org.gnome.desktop.privacy' b'report-technical-problems' b'true' InstallationDate: Installed on 2020-04-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) Package: gnome-shell 3.36.0-2ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1870523/+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 1900798] Re: Dark theme not applied in the calendar, system tray and desktop right click menus which are still light
*** This bug is a duplicate of bug 1842886 *** https://bugs.launchpad.net/bugs/1842886 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 1842886, 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 1842886 Yaru-dark shell menus and dialogs are not dark -- 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/1900798 Title: Dark theme not applied in the calendar, system tray and desktop right click menus which are still light Status in gnome-shell package in Ubuntu: New Bug description: On a fresh installation of Ubuntu Groovy inside a VirtualBox 6.1.16 VM, installed using the latest Groovy ISO and all packages up-to-date, when the dark theme is chosen for the desktop, the calendar, system tray/notification area menu and the desktop right-click menu all still use the light color instead of the expected dark color. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 21 11:42:40 2020 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'gtk-theme' b"'Yaru-dark'" b'org.gnome.desktop.privacy' b'report-technical-problems' b'true' InstallationDate: Installed on 2020-10-21 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 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/1900798/+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 1900797] Re: The triangle at the top of the calendar, system tray pop up doesn't go away when the pop is closed
*** This bug is a duplicate of bug 1870523 *** https://bugs.launchpad.net/bugs/1870523 ** Package changed: 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/1900797 Title: The triangle at the top of the calendar, system tray pop up doesn't go away when the pop is closed Status in gnome-shell package in Ubuntu: New Bug description: On the Ubuntu Groovy installation inside a VirtualBox 6.1.16 virtual machine, using the latest Groovy ISO, the following issue happens: * Click on the date/time indicator at the center of the top panel. * The date/time, calendar popup opens. * Click outside the popup and the popup closes. * However, the white triangle at the top of the popup stays in the screen even after the popup is closed. * Clicking once more on the desktop makes it go away. * The same behaviour can be seen even on the system tray/notification area popup. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 21 11:37:15 2020 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'gtk-theme' b"'Yaru-dark'" b'org.gnome.desktop.privacy' b'report-technical-problems' b'true' InstallationDate: Installed on 2020-10-21 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 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/1900797/+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 1900798] Re: Dark theme not applied in the calendar, system tray and desktop right click menus which are still light
*** This bug is a duplicate of bug 1842886 *** https://bugs.launchpad.net/bugs/1842886 ** Package changed: 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/1900798 Title: Dark theme not applied in the calendar, system tray and desktop right click menus which are still light Status in gnome-shell package in Ubuntu: New Bug description: On a fresh installation of Ubuntu Groovy inside a VirtualBox 6.1.16 VM, installed using the latest Groovy ISO and all packages up-to-date, when the dark theme is chosen for the desktop, the calendar, system tray/notification area menu and the desktop right-click menu all still use the light color instead of the expected dark color. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 21 11:42:40 2020 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'gtk-theme' b"'Yaru-dark'" b'org.gnome.desktop.privacy' b'report-technical-problems' b'true' InstallationDate: Installed on 2020-10-21 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 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/1900798/+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 1900797] [NEW] The triangle at the top of the calendar, system tray pop up doesn't go away when the pop is closed
You have been subscribed to a public bug: On the Ubuntu Groovy installation inside a VirtualBox 6.1.16 virtual machine, using the latest Groovy ISO, the following issue happens: * Click on the date/time indicator at the center of the top panel. * The date/time, calendar popup opens. * Click outside the popup and the popup closes. * However, the white triangle at the top of the popup stays in the screen even after the popup is closed. * Clicking once more on the desktop makes it go away. * The same behaviour can be seen even on the system tray/notification area popup. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 21 11:37:15 2020 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'gtk-theme' b"'Yaru-dark'" b'org.gnome.desktop.privacy' b'report-technical-problems' b'true' InstallationDate: Installed on 2020-10-21 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- The triangle at the top of the calendar, system tray pop up doesn't go away when the pop is closed https://bugs.launchpad.net/bugs/1900797 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900798] [NEW] Dark theme not applied in the calendar, system tray and desktop right click menus which are still light
You have been subscribed to a public bug: On a fresh installation of Ubuntu Groovy inside a VirtualBox 6.1.16 VM, installed using the latest Groovy ISO and all packages up-to-date, when the dark theme is chosen for the desktop, the calendar, system tray/notification area menu and the desktop right-click menu all still use the light color instead of the expected dark color. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 21 11:42:40 2020 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'gtk-theme' b"'Yaru-dark'" b'org.gnome.desktop.privacy' b'report-technical-problems' b'true' InstallationDate: Installed on 2020-10-21 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- Dark theme not applied in the calendar, system tray and desktop right click menus which are still light https://bugs.launchpad.net/bugs/1900798 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896098] Re: Lenovo P1G3 - unable to select system speakers when headset plugged into audio jack
@hui, Thanks for the feedback. Linux machine and Windows machine shall use common BIOS/EC version for the test. I'll ask BIOS team to get some input from them. BTW, Could you help to check if you can see the same phenomena with corresponding EC version 1.05 (N2VHT16W)? https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-p-series-laptops/thinkpad-p1-gen-3-type-20th-20tj/downloads/driver-list/component?name=BIOS%2FUEFI Thanks. LO-627 for our internal tracking. -- 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/1896098 Title: Lenovo P1G3 - unable to select system speakers when headset plugged into audio jack Status in pulseaudio package in Ubuntu: New Bug description: I suspect this is a pulseaudio or alsa bug. Our test team reported this: 1. Prepare Padme-3 machine and Install Ubuntu_20.04 OS . 2. Boot system. 3. Play audio or video file. 4. Open Settings > Sound. 5. Hot attach headset. 6. Notice that headset is selected as output device in sound settings and sound can be heard from headset => EXPECTED 7. While playback, select Internal Speaker as output device => KEYPOINT 9. Notice:SUT havo no sound from Internal Speakers => PROBLEM I was able to confirm this - it seems with the headphones connected that I can't select the system speakers. If I don't have headphones connected I can switch between dock audio and system speakers correctly - so it's just related to the audio jack Thanks Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1896098/+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 1900640] Re: Ubuntu 20.04 has no capability of surrounding-text feature
** Also affects: ibus via https://github.com/ibus/ibus/issues/2271 Importance: Unknown Status: Unknown -- 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/1900640 Title: Ubuntu 20.04 has no capability of surrounding-text feature Status in ibus: Unknown Status in ibus package in Ubuntu: Confirmed Bug description: I recently upgrade my Ubuntu LTS from 18.04 to 20.04. After the upgrade, I failed to type Thai text with any combining character in some apps. The log contains this error message: `gnome-shell[2076]: (google-chrome-stable:2069): IBUS-WARNING **: 09:07:10.843: google-chrome-stable has no capability of surrounding-text feature` `gnome-terminal-[2589]: gnome-terminal-server has no capability of surrounding-text feature` Expected behavior: Capable of typing any Thai character in any app. Actual behavior: Only few apps support typing Thai character, e.g. Firefox, Gnome Text Editor. Step to reproduce: 1. Boot up the machine. 2. Open Google Chrome. 3. Switch keyboard layout to `Thai (LibThai)` 4. Type Thai text "กิน" which is equals to following keystroke "dbo" but with Thai keyboard layout. Current workaround: Whenever you want to type Thai switch 1. Open `Gnome Text Editor` 2. Switch keyboard layout to `Thai (LibThai)` 3. Switch to Chrome 4. Type Thai To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1900640/+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 1899089] Re: Ubuntu 20.04 file browser showing all zfs mounts explicitly in side-panel
it's discussed upstream on https://gitlab.gnome.org/GNOME/nautilus/-/issues/1074 ** Changed in: nautilus (Ubuntu) Status: Incomplete => New ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #1074 https://gitlab.gnome.org/GNOME/nautilus/-/issues/1074 -- 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/1899089 Title: Ubuntu 20.04 file browser showing all zfs mounts explicitly in side- panel Status in nautilus package in Ubuntu: New Bug description: I have installed Ubuntu 20.04 on zfs. I had previously had zfs datasets mounted into my 18.04 system. Those mounts are all working in the new system, but they are displaying as mounts in my file browser with unmount buttons next to them. I certainly don't want this function. it is also cluttering my display. It appears similar to Bug 1691908. My zfs mounts are not removable volumes, they are not in fstab. I was advised to report the output of `gio mount -li`: ``` Volume(0): efi Type: GUnixVolume ids: uuid: '8799-8F8E' themed icons: [drive-removable-media] symbolic themed icons: [drive-removable-media-symbolic] can_mount=1 can_eject=0 should_automount=1 Mount(0): efi -> file:///boot/efi Type: GUnixMount default_location=file:///boot/efi themed icons: [drive-harddisk] symbolic themed icons: [drive-harddisk-symbolic] can_unmount=1 can_eject=0 is_shadowed=0 Mount(1): SPACE -> file:///media/peterg/SPACE Type: GUnixMount default_location=file:///media/peterg/SPACE themed icons: [drive-harddisk] symbolic themed icons: [drive-harddisk-symbolic] can_unmount=1 can_eject=0 is_shadowed=0 ``` I tried Ask-Ubuntu. No answers at this time: https://askubuntu.com/questions/1280941/ubuntu-20-04-file-browser-showing-all-zfs-mounts-explicitly-in-side-panel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Oct 9 08:41:22 2020 GsettingsChanges: InstallationDate: Installed on 2020-10-01 (6 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20201001) ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1899089/+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 1893719] Re: Request for adding support for Synaptics fingerprint reader sensors: 0xE9 and 0xDF
** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1893719 Title: Request for adding support for Synaptics fingerprint reader sensors: 0xE9 and 0xDF Status in OEM Priority Project: Fix Released Status in libfprint package in Ubuntu: Fix Released Status in libfprint source package in Focal: Fix Released Bug description: [Impact] * We were advised by Synaptics to upgrade the existing libfprint in the archive to include sensor support for 0xE9 and 0xDF as highlighted in the following commits: https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/8b64312f4bfee84c8be1eb9763f7fe87ec078a1a [Test Case] * We have several OEM platforms with these Synaptics sensors enabled with Focal and they can be used to validate these changes. [Regression Potential] * Regression potential for an updated libfprint with these new PIDs is low [Other Info] None To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1893719/+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 1873184] Re: Wired and wireless connection details have not enough height and items overlap
** Tags added: originate-from-1898665 stella -- 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/1873184 Title: Wired and wireless connection details have not enough height and items overlap Status in gnome-control-center: Unknown Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Focal: Fix Committed Status in gnome-control-center source package in Groovy: Fix Released Bug description: * Impact The details of the connection settings sometime overlap * Test case Connect the computer to a wired ethernet, go to settings and check the connection details, the items should be displayed separated and not overlapping * Regression potential Check that the connection details dialog is correctly displayed on different typo of connections, the change is in the layout of the elements so it could impact the layout in other cases To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1873184/+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 1876219] Re: iris driver for old cpu
there is no mechanism to detect that you're using the non-supported -intel driver ** Package changed: mesa (Ubuntu) => xserver-xorg-video-intel (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1876219 Title: iris driver for old cpu Status in Mesa: Confirmed Status in ring package in Ubuntu: New Status in vlc package in Ubuntu: Invalid Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I am not completely sure where I should file the bug. I am using Lubuntu 20.04 with lxqt, and since the upgrade to 20.04 iris is the default graphics driver, which results in crashes in multiple apps including guvcview and calibre. Setting MESA_LOADER_DRIVER_OVERRIDE=i965 fixed the problem. I am not sure but is it true that iris does not support older generations of Intel CPUs? If it is the case would it be possible to revert to i965 in those circumstances? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1876219/+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