[Desktop-packages] [Bug 1916701] Re: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered)
I forced the warning to dump core and get: Feb 24 15:50:49 kab gnome-shell.bin[1006]: invalid (NULL) pointer instance Feb 24 15:50:49 kab org.gnome.Shell.desktop[1006]: GNOME Shell crashed with signal 5 Feb 24 15:50:49 kab org.gnome.Shell.desktop[1006]: == Stack trace for context 0x559976392170 == Feb 24 15:50:49 kab org.gnome.Shell.desktop[1006]: #0 5599765f6f18 i resource:///org/gnome/shell/ui/main.js:187 (3d80d9cbee70 @ 52) Feb 24 15:50:49 kab org.gnome.Shell.desktop[1006]: #1 5599765f6e68 i resource:///org/gnome/shell/ui/main.js:162 (3d80d9cbefb0 @ 324) Feb 24 15:50:49 kab org.gnome.Shell.desktop[1006]: #2 5599765f6de0 i :1 (3d80d9c84100 @ 48) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1916701 Title: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered) Status in glib2.0 package in Ubuntu: New Status in gnome-session package in Ubuntu: New Bug description: When I installed the glib2.0 2.67.4-1 packages I consistently encountered a black screen on boot. The login screen was missing/delayed but eventually comes up without Wayland support (only Xorg sessions offered). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1916701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915870] Re: gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]
** Patching together your own packages is not supported and can easily break your system ** With that said, the patch is here: https://gitlab.freedesktop.org/mesa/mesa/-/commit/58e43594fc4.patch -- 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/1915870 Title: gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so] Status in Mesa: Unknown Status in mesa package in Ubuntu: Triaged Status in mesa package in Fedora: Unknown Bug description: Graphical user interface is not coming up upon start. Only SSH is possible. lsb_release -rd: Description: Ubuntu 20.10 Release: 20.10 dmesg: [ 11.985343] gnome-session-c[1013]: segfault at 0 ip sp 7fff7679ca48 error 14 in gnome-session-check-accelerated-gl-helper[56020e238000+2000] [ 11.985352] Code: Unable to access opcode bytes at RIP 0xffd6. [ 14.216117] gnome-shell[1094]: segfault at 0 ip sp 7ffeddff9f88 error 14 [ 14.216122] Code: Unable to access opcode bytes at RIP 0xffd6. [ 15.316292] gnome-shell[1109]: segfault at 0 ip sp 7ffc70716198 error 14 [ 15.316297] Code: Unable to access opcode bytes at RIP 0xffd6. apt-cache policy: gnome-session: Installed: (none) Candidate: 3.38.0-1ubuntu1 Version table: 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages gnome-session-bin: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session-common: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages 100 /var/lib/dpkg/status /var/crash: see attachment To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916711] [NEW] 'Restart & Update' in 'Software' application does nothing in Xubuntu
Public bug reported: Release: Xubuntu dailybuilds ISO (currently 20210224 ISO) SW and Version: gnome-software, 3.38.0-3 How to reproduce: - Launch 'Software'. If available, it shows updates under 'Updates'. - Click on 'Download' it changes to 'Restart & Update' after a while (I did not see any progress bar, may be update was very small or it is normal) - Click on 'Restart & Update' button. Expected: System should reboot and during reboot the updates should be installed. Actual: Nothing happens. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-software 3.38.0-3 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Feb 24 13:10:53 2021 InstallationDate: Installed on 2021-02-24 (0 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210224) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.38.0-3 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- 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/1916711 Title: 'Restart & Update' in 'Software' application does nothing in Xubuntu Status in gnome-software package in Ubuntu: New Bug description: Release: Xubuntu dailybuilds ISO (currently 20210224 ISO) SW and Version: gnome-software, 3.38.0-3 How to reproduce: - Launch 'Software'. If available, it shows updates under 'Updates'. - Click on 'Download' it changes to 'Restart & Update' after a while (I did not see any progress bar, may be update was very small or it is normal) - Click on 'Restart & Update' button. Expected: System should reboot and during reboot the updates should be installed. Actual: Nothing happens. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-software 3.38.0-3 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Feb 24 13:10:53 2021 InstallationDate: Installed on 2021-02-24 (0 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210224) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.38.0-3 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1916711/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916550] Re: simple-scan chooses scanned image size improperly
Could you please paste the screenshot with the list of scanners which are available to choose? Is it is: * HP OfficeJet_4650_series * HP OfficeJet 4650 series [A67ED8] SSL * OfficeJet 4650 series [TH7B64F03Z0662] * HP OfficeJet 4650 series [A67ED8] ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1916550 Title: simple-scan chooses scanned image size improperly Status in simple-scan package in Ubuntu: Incomplete Bug description: I have an HP OfficeJet 4654 which the scanner recognized (after a while, but eventually it finds the OfficeJet). The scanner can do single pages on the platen and has a sheet feeder as well. When I scan single pages on the platen, the size is correctly set to Letter (It could do A4 but I don't use that). However, if I use the sheet feeder, the scan defaults to Legal size. If I change the Preference to Letter in the gear settings, I can get Letter sized scans with the feeder. However, with the Preference set to Letter, the single platen scanned documents come out Legal sized with the area below the Letter sized form blackened in. This is absurd. If I tell it to use Letter size, it should not override this and produce incorrect Legal sized scans, regardless of whether the source is on the platen or from the feeder. What I truly don't understand is why I get a Legal size scan on a Letter sized piece of paper in the sheet feeder at all (the default behavior). The app is clearly capable of producing letter sized scans when told to do so. I also don't understand why the scanning tool overrides my Preference setting for Letter size when I scan from the platen. The new interface also makes it more difficult to change the Preferences - there's no Save or OK button, just the upper-right- corner x which usually means don't save - very confusing and user unfriendly. Source: https://gitlab.gnome.org/GNOME/simple-scan Description: Ubuntu 20.04.2 LTS Release: 20.04 Simple-scan Version: 3.36.3 What I expected to happen: If I scan a letter sized document, I expect a letter sized scan. If I scan multiple sheets all letter sized, I expect all pages to scan at letter sized. What happens instead: If the paper size Preference is set to Automatic, the platen scans are correct but the sheet feeder scans are all legal sized. If the paper size Preference is set to Letter, the sheet feeder scans are all letter sized but the single page platen scans are all legal sized with a blackened 3" section at the bottom of the page. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Feb 22 18:04:51 2021 InstallationDate: Installed on 2020-10-01 (145 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=97168ae7-ec8a-49b7-8ef8-6b377b98a588 ro nosplash SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.20 dmi.board.name: Z97 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd05/12/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1916550/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916701] Re: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered)
Looks like gnome-shell is failing some basic GObject initialization. The only ABI/API break I can see in glib 2.67 is this: https://gitlab.gnome.org/GNOME/glib/-/commit/334f6953364680ddc6c0d3da13fda1d92bf5379d -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1916701 Title: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered) Status in glib2.0 package in Ubuntu: New Bug description: When I installed the glib2.0 2.67.4-1 packages I consistently encountered a black screen on boot. The login screen was missing/delayed but eventually comes up without Wayland support (only Xorg sessions offered). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1916701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916701] Re: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered)
** No longer affects: gnome-session (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1916701 Title: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered) Status in glib2.0 package in Ubuntu: New Bug description: When I installed the glib2.0 2.67.4-1 packages I consistently encountered a black screen on boot. The login screen was missing/delayed but eventually comes up without Wayland support (only Xorg sessions offered). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1916701/+subscriptions -- Mailing list: https://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 1915870] Re: gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]
Sure. Thanks a lot. Looks like this has worked for Mark. So I will give this a try as well... Regards,Santosh -- 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/1915870 Title: gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so] Status in Mesa: Unknown Status in mesa package in Ubuntu: Triaged Status in mesa package in Fedora: Unknown Bug description: Graphical user interface is not coming up upon start. Only SSH is possible. lsb_release -rd: Description: Ubuntu 20.10 Release: 20.10 dmesg: [ 11.985343] gnome-session-c[1013]: segfault at 0 ip sp 7fff7679ca48 error 14 in gnome-session-check-accelerated-gl-helper[56020e238000+2000] [ 11.985352] Code: Unable to access opcode bytes at RIP 0xffd6. [ 14.216117] gnome-shell[1094]: segfault at 0 ip sp 7ffeddff9f88 error 14 [ 14.216122] Code: Unable to access opcode bytes at RIP 0xffd6. [ 15.316292] gnome-shell[1109]: segfault at 0 ip sp 7ffc70716198 error 14 [ 15.316297] Code: Unable to access opcode bytes at RIP 0xffd6. apt-cache policy: gnome-session: Installed: (none) Candidate: 3.38.0-1ubuntu1 Version table: 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages gnome-session-bin: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session-common: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages 100 /var/lib/dpkg/status /var/crash: see attachment To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916722] [NEW] Pulseaudio fails to start after reboot if home partition is encrypted
Public bug reported: It seems that with Ubuntu 20.10, Pulseaudio now tries to start as main user too early, before user logs in and the home partition is decrypted. Probably pulseaudio should not start as main user before login of this user. Starting pulseaudio manually after login works. grep 'pulseaudio' /var/log/syslog Feb 24 10:52:31 aziber systemd[1451]: Not generating service for XDG autostart app-pulseaudio-autostart.service, startup phases are not supported. Feb 24 10:52:31 aziber dbus-daemon[972]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=123 pid=1497 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Feb 24 10:52:38 aziber systemd[3631]: Not generating service for XDG autostart app-pulseaudio-autostart.service, startup phases are not supported. Feb 24 10:52:38 aziber pulseaudio[3690]: Failed to create secure directory (/home/anton/.config/pulse): No such file or directory Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Failed with result 'exit-code'. Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Scheduled restart job, restart counter is at 1. Feb 24 10:52:38 aziber pulseaudio[3899]: Failed to create secure directory (/home/anton/.config/pulse): No such file or directory Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Failed with result 'exit-code'. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Scheduled restart job, restart counter is at 2. Feb 24 10:52:39 aziber pulseaudio[4128]: Failed to create secure directory (/home/anton/.config/pulse): No such file or directory Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Failed with result 'exit-code'. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Scheduled restart job, restart counter is at 3. Feb 24 10:52:39 aziber pulseaudio[4311]: Failed to create secure directory (/home/anton/.config/pulse): No such file or directory Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Failed with result 'exit-code'. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Scheduled restart job, restart counter is at 4. Feb 24 10:52:39 aziber pulseaudio[4493]: Failed to create secure directory (/home/anton/.config/pulse): No such file or directory Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Failed with result 'exit-code'. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Scheduled restart job, restart counter is at 5. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Start request repeated too quickly. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Failed with result 'exit-code'. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.socket: Failed with result 'service-start-limit-hit'. Feb 24 10:52:42 aziber pulseaudio.desktop[5720]: Connection failure: Connection refused Feb 24 10:52:42 aziber pulseaudio.desktop[5720]: pa_context_connect() failed: Connection refused Feb 24 10:52:42 aziber gnome-session[5663]: gnome-session-binary[5663]: WARNING: App 'pulseaudio.desktop' exited with code 1 Feb 24 10:52:42 aziber gnome-session-binary[5663]: WARNING: App 'pulseaudio.desktop' exited with code 1 Feb 24 10:52:42 aziber systemd[3609]: app-gnome-pulseaudio-5715.scope: Failed to add PIDs to scope's control group: No such process Feb 24 10:52:42 aziber systemd[3609]: app-gnome-pulseaudio-5715.scope: Failed with result 'resources'. Feb 24 10:52:45 aziber systemd[1432]: pulseaudio.service: Succeeded. Feb 24 10:52:55 aziber systemd[1432]: pulseaudio.socket: Succeeded. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.3 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Feb 24 10:57:51 2021 InstallationDate: Installed on 2019-11-29 (452 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416
[Desktop-packages] [Bug 1916701] Re: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered)
Building GNOME 40 from git has the same bug, surprisingly: * Wayland instances hang and never start properly; * Xorg instances start immediately without error. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1916701 Title: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered) Status in glib2.0 package in Ubuntu: New Bug description: When I installed the glib2.0 2.67.4-1 packages I consistently encountered a black screen on boot. The login screen was missing/delayed but eventually comes up without Wayland support (only Xorg sessions offered). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1916701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878351] Re: System shutdown directly by pressing power button and releasing immediately on Dell Vostro HW
** Changed in: oem-priority Importance: High => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1878351 Title: System shutdown directly by pressing power button and releasing immediately on Dell Vostro HW Status in OEM Priority Project: Incomplete Status in gnome-session package in Ubuntu: Triaged Status in linux package in Ubuntu: Confirmed Bug description: kchsieh@kchsieh-laptop:~$ lsb_release -rd Description: Ubuntu 20.04 LTS (fossa-bulbasaur X23) Release: 20.04 kchsieh@kchsieh-laptop:~$ apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3 Candidate: 245.4-4ubuntu3 Version table: *** 245.4-4ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Expect: When press the button, the endSeesionDialog should show up. Actual: The system shutdown directly. When the issue happend: endSessionDialog is not triggered immediately after the first power button event, but triggered after the second power button event. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X23 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-10 (3 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: systemd 245.4-4ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1010-oem root=UUID=b16fea1e-d8bc-4c71-a2e6-c43d269b40de ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 Tags: focal Uname: Linux 5.6.0-1010-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.1.12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.1.12:bd04/30/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5301 dmi.product.sku: 09FC dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916726] [NEW] NetworkManager fails on boot
Public bug reported: NetworkManager will fail on boot, and will leave me with a screen that says "Oops, something has gone wrong. Please contact your software vendor" "NetworkManager needs to be running" and a sad face picture. This has happened increasingly over the past month or two, and all I have done different is update my system periodically. If I try and start NetworkManager through systemctl, it will get stuck and provide absolutely no output at all. I have to do a complete reboot and hope to God it doesn't fail again. I cannot do anything Wi-Fi wise, so if my Ethernet fails, I cannot switch to Wi-Fi or anything because I have no manager to do it with. [ Description:Ubuntu 20.10 Release:20.10 gnome-control-center: Installed: 1:3.38.3-0ubuntu1 Candidate: 1:3.38.3-0ubuntu1 Version table: *** 1:3.38.3-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu groovy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.38.1-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu groovy/main amd64 Packages I could not get any details on NetworkManager because apparently it isn't installed (I know it is, as it was never removed) but my system is fully updated.. if that helps. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.38.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Wed Feb 24 09:13:21 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-08-06 (201 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to groovy on 2020-10-14 (132 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy third-party-packages ** Attachment added: "Error screen" https://bugs.launchpad.net/bugs/1916726/+attachment/5466552/+files/networkmanager.png -- 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/1916726 Title: NetworkManager fails on boot Status in gnome-control-center package in Ubuntu: New Bug description: NetworkManager will fail on boot, and will leave me with a screen that says "Oops, something has gone wrong. Please contact your software vendor" "NetworkManager needs to be running" and a sad face picture. This has happened increasingly over the past month or two, and all I have done different is update my system periodically. If I try and start NetworkManager through systemctl, it will get stuck and provide absolutely no output at all. I have to do a complete reboot and hope to God it doesn't fail again. I cannot do anything Wi-Fi wise, so if my Ethernet fails, I cannot switch to Wi-Fi or anything because I have no manager to do it with. [ Description: Ubuntu 20.10 Release: 20.10 gnome-control-center: Installed: 1:3.38.3-0ubuntu1 Candidate: 1:3.38.3-0ubuntu1 Version table: *** 1:3.38.3-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu groovy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.38.1-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu groovy/main amd64 Packages I could not get any details on NetworkManager because apparently it isn't installed (I know it is, as it was never removed) but my system is fully updated.. if that helps. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.38.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Wed Feb 24 09:13:21 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-08-06 (201 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to groovy on 2020-10-14 (132 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1916726/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916701] Re: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered)
Tracking in https://gitlab.gnome.org/GNOME/glib/-/issues/2332 although that one does not look familiar. One of its duplicates looks more familiar: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3744 ** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #2332 https://gitlab.gnome.org/GNOME/glib/-/issues/2332 ** Also affects: glib via https://gitlab.gnome.org/GNOME/glib/-/issues/2332 Importance: Unknown Status: Unknown ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3744 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3744 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1916701 Title: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered) Status in GLib: Unknown Status in glib2.0 package in Ubuntu: New Bug description: When I installed the glib2.0 2.67.4-1 packages I consistently encountered a black screen on boot. The login screen was missing/delayed but eventually comes up without Wayland support (only Xorg sessions offered). To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1916701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916701] Re: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered)
** Changed in: glib2.0 (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1916701 Title: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered) Status in GLib: Unknown Status in glib2.0 package in Ubuntu: Triaged Bug description: When I installed the glib2.0 2.67.4-1 packages I consistently encountered a black screen on boot. The login screen was missing/delayed but eventually comes up without Wayland support (only Xorg sessions offered). To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1916701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916594] Re: Xorg freeze
I reckon the display freezing issue is partially resolved with update of chrome brower(potentially having risk from other apps). I don't suffer from freezing issue in these days. Thus, it's hard to hand the attachment to you, sorry. However, the booting problem is not solved with your recent updates. I individually diagnoused the problem with dmesg, and I found that I can see a suspicious message 'lg_laptop: Cannot get handle' is continuously logged. -- 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/1916594 Title: Xorg freeze Status in xorg-server package in Ubuntu: Incomplete Bug description: I have several problems in usage of ubuntu and I guess it's a display server or grub problem. First, my system freezes sometimes and it required hard reboot and I used chrome and several programming tools in this moments(and i didn't run any hi performance computing jobs). Second, i have a continuous problem with booting in my machine. it means, my system cannot enter GUI session directly(The cursor just blinks in black screen). It requires to switch to console session and re-enter to GUI(with ALT F1, F2) and I am using LG laptop and I guess it's a problem from graphic driver. I hope it can be resolved soon. Thanks(from south Korea user). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] 디렉터리입니다: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] 디렉터리입니다: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 디렉터리입니다: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.32.03 Sun Dec 27 19:00:34 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] 허가 거부: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 23 20:40:22 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 460.32.03, 5.8.0-41-generic, x86_64: installed nvidia, 460.32.03, 5.8.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: LG Electronics, Inc. UHD Graphics 620 [1854:0304] InstallationDate: Installed on 2021-01-26 (27 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e300 Qualcomm Atheros Communications Bus 001 Device 003: ID 0408:50c0 Quanta Computer, Inc. USB HD Webcam Bus 001 Device 002: ID 25a7:fa67 CX 2.4G Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LG Electronics 15UD480-KX70K ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=c1380f53-21a5-44dd-811f-ca31d34355b0 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2018 dmi.bios.release: 2.24 dmi.bios.version: GP224 dmi.board.asset.tag: No Asset Tag dmi.board.name: 15U480 dmi.board.vendor: Quanta dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvn:bvrGP224:bd07/02/2018:br2.24:efr1.4:svnLGElectronics:pn15UD480-KX70K:pvr:rvnQuanta:rn15U480:rvr:cvn:ct10:cvr: dmi.product.family: U Series dmi.product.name: 15UD480-KX70K dmi.sys.vendor: LG Electronics version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1916594/+subs
[Desktop-packages] [Bug 1916701] Re: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered)
Verified the fix from upstream works: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/1958.patch It's coming in 2.67.5 ** Tags added: fixed-in-2.67.5 fixed-upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1916701 Title: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered) Status in GLib: Unknown Status in glib2.0 package in Ubuntu: Triaged Bug description: When I installed the glib2.0 2.67.4-1 packages I consistently encountered a black screen on boot. The login screen was missing/delayed but eventually comes up without Wayland support (only Xorg sessions offered). To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1916701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
Hi team, is there any news about this 3y old bug? It would be nice to know if it is something that will be worked on or not even if the timeline indicates towards not. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in KeePassXC Snap Builds: Unknown Status in chromium-browser package in Ubuntu: Triaged Status in goopg package in Ubuntu: Confirmed Status in kdeconnect package in Ubuntu: Confirmed Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/keepassxc-snap/+bug/1741074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Works fine after installing hwe kernel using apt.(5.8.0.44 Ubuntu 20.04
Lenovo R7000P)
--
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:
Fix Released
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:
Update (based on #296)
=
The latest kernel tree
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
has the complete solution to fix this bug. So we can expect kernel
v5.11 to fix this issue without any additional work.
Before the release of v5.11, you are suggested to use #189 to save your
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd
driver is built into the initramfs. So you have to rebuild the initramfs after
replacing the old module with new one.
On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs
-u`.
The complete solution is three patches,
- 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce
filter setting in IRQ type setting")
- 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way
to disable debounce filter")
- 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into
account debounce settings")
The first two patches has reached the stable tree. If the last one is
also backported to LTS kernel, you won't need to install kernel 5.11.
But I don't know when this will happen.
Original bug report
===
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-256
[Desktop-packages] [Bug 1904789] Re: [snap] Cannot confirm security exception for invalid certificate
Same issue here. I end up downloading the tar.bz2 package with the latest version and installing it myself. Will keep an eye to move back to snap once this is fixed :( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1904789 Title: [snap] Cannot confirm security exception for invalid certificate Status in thunderbird package in Ubuntu: Confirmed Bug description: Note: This bug is specific to the Snap version of Thunderbird, I can't reproduce it with the Ubuntu-packaged version for example (which I have installed on Ubuntu, used for multiple years and stopped using recently to get the more recent versions of TB available with Snap). When a certificate problem arrises with a server from which Thunderbird tries to retrieve emails, the "Add Security Exception" window gives you the option to "Confirm Security Exception" (meaning that Thunderbird will overlook the invalid certificate). The problem is that nothing happens when I click the "Confirm Security Exception" button. I've tried the usual workarounds, including removing the email account and adding it again, to no avail. The peculiar thing here is that I have had certificate problems before, when using a non-snap version of Thunderbird, and clicking the "Confirm Security Exception" button has always worked. Not with the Snap version it seems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1904789/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916469] Re: Apps don't use Wayland by default
** Description changed: The Ubuntu universe has a big Wayland problem! What does that mean? So a lot of packages in the Universe repository are not compiled with Wayland support which is really bad and would lead to bad performance after 21.04 comes out. Here are the following packages that I detected with wrong compilation: telegram-desktop (Wayland support work with snap version) - qdirstat - vlc kiwix firefox (everything works fine with this env variable set:"MOZ_ENABLE_WAYLAND=1") -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1916469 Title: Apps don't use Wayland by default Status in firefox package in Ubuntu: Confirmed Status in qdirstat package in Ubuntu: New Status in telegram-desktop package in Ubuntu: New Status in vlc package in Ubuntu: New Bug description: The Ubuntu universe has a big Wayland problem! What does that mean? So a lot of packages in the Universe repository are not compiled with Wayland support which is really bad and would lead to bad performance after 21.04 comes out. Here are the following packages that I detected with wrong compilation: telegram-desktop (Wayland support work with snap version) kiwix firefox (everything works fine with this env variable set:"MOZ_ENABLE_WAYLAND=1") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1916469/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883890] Re: [MIR] libinih
Override component to main libinih 50-1 in hirsute: universe/misc -> main libinih-dev 50-1 in hirsute amd64: universe/libdevel/optional/100% -> main libinih-dev 50-1 in hirsute arm64: universe/libdevel/optional/100% -> main libinih-dev 50-1 in hirsute armhf: universe/libdevel/optional/100% -> main libinih-dev 50-1 in hirsute i386: universe/libdevel/optional/100% -> main libinih-dev 50-1 in hirsute ppc64el: universe/libdevel/optional/100% -> main libinih-dev 50-1 in hirsute riscv64: universe/libdevel/optional/100% -> main libinih-dev 50-1 in hirsute s390x: universe/libdevel/optional/100% -> main libinih1 50-1 in hirsute amd64: universe/libs/optional/100% -> main libinih1 50-1 in hirsute arm64: universe/libs/optional/100% -> main libinih1 50-1 in hirsute armhf: universe/libs/optional/100% -> main libinih1 50-1 in hirsute i386: universe/libs/optional/100% -> main libinih1 50-1 in hirsute ppc64el: universe/libs/optional/100% -> main libinih1 50-1 in hirsute riscv64: universe/libs/optional/100% -> main libinih1 50-1 in hirsute s390x: universe/libs/optional/100% -> main libinireader0 50-1 in hirsute amd64: universe/libs/optional/100% -> main libinireader0 50-1 in hirsute arm64: universe/libs/optional/100% -> main libinireader0 50-1 in hirsute armhf: universe/libs/optional/100% -> main libinireader0 50-1 in hirsute i386: universe/libs/optional/100% -> main libinireader0 50-1 in hirsute ppc64el: universe/libs/optional/100% -> main libinireader0 50-1 in hirsute riscv64: universe/libs/optional/100% -> main libinireader0 50-1 in hirsute s390x: universe/libs/optional/100% -> main Override [y|N]? y 22 publications overridden. ** Changed in: libinih (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinih in Ubuntu. https://bugs.launchpad.net/bugs/1883890 Title: [MIR] libinih Status in libinih package in Ubuntu: Fix Released Bug description: * Availability Built for all supported architectures. In sync with Debian. https://launchpad.net/ubuntu/+source/libinih/48-1 * Rationale It's a depends from gamemode which currently bundles a copy version * Security No known security issues https://security-tracker.debian.org/tracker/source-package/libinih https://launchpad.net/ubuntu/+source/libinih/+cve https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=libinih * Quality assurance - The desktop-packages team is subscribed - No report downstream, one upstream only and it's from today https://bugs.launchpad.net/ubuntu/+source/libinih https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libinih https://github.com/benhoyt/inih/issues The unittests are run as an autopkgtest http://autopkgtest.ubuntu.com/packages/libi/libinih * Dependencies It Depends only on libc6 * Standards compliance Use current Standards-Version and dh13 * Maintenance The Debian maintainer is active, the package is in sync, the Desktop Team is subscribed in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinih/+bug/1883890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916469] Re: Apps don't use Wayland by default
** Changed in: vlc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1916469 Title: Apps don't use Wayland by default Status in firefox package in Ubuntu: Confirmed Status in qdirstat package in Ubuntu: New Status in telegram-desktop package in Ubuntu: New Status in vlc package in Ubuntu: Invalid Bug description: The Ubuntu universe has a big Wayland problem! What does that mean? So a lot of packages in the Universe repository are not compiled with Wayland support which is really bad and would lead to bad performance after 21.04 comes out. Here are the following packages that I detected with wrong compilation: telegram-desktop (Wayland support work with snap version) kiwix firefox (everything works fine with this env variable set:"MOZ_ENABLE_WAYLAND=1") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1916469/+subscriptions -- Mailing list: https://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
Hi Marton,
On Tue, Feb 23, 2021 at 05:00:30PM -, Marton Danko wrote:
>Hi Coiby,
>
>Did you find anything about why it still doesn't work properly on my
>machine?
>
Your GPIO pin register value for the touchpad is 0x51b00 which means the
root cause has been fixed. I've less certain about the evest result but
I don't find something suspicious when comparing it with my laptop. Can
you create another user and check if the problem still occurs after
logging in?
--
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:
Fix Released
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:
Update (based on #296)
=
The latest kernel tree
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
has the complete solution to fix this bug. So we can expect kernel
v5.11 to fix this issue without any additional work.
Before the release of v5.11, you are suggested to use #189 to save your
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd
driver is built into the initramfs. So you have to rebuild the initramfs after
replacing the old module with new one.
On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs
-u`.
The complete solution is three patches,
- 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce
filter setting in IRQ type setting")
- 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way
to disable debounce filter")
- 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into
account debounce settings")
The first two patches has reached the stable tree. If the last one is
also backported to LTS kernel, you won't need to install kernel 5.11.
But I don't know when this will happen.
Original bug report
===
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
[Desktop-packages] [Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
Now that the new version was released to the "updates" channel I tried a regular Update using the default Ubuntu update-manager GUI. I don't have tinyjsd or jsunit installed so I expected everything to go smoothly. Instead the update-manager proposes a partial system update to install the thunderbird version and REMOVE the enigmail package (see screenshot). I suspect, this would not migrate my enigmail keys. If I understood it right there should be a new version for the enigmail package as well, which handles the migration of the encryption keys to the new internal PGP implementation. Is the update for the enigmail package still stuck somewhere? @racb posted earlier that the two packages should be updated together: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/comments/33 ** Attachment added: "update-manager proposes to remove Enigmail" https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+attachment/5466601/+files/update-manager.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in thunderbird package in Ubuntu: Fix Released Status in jsunit source package in Bionic: Confirmed Status in thunderbird source package in Bionic: Confirmed Status in jsunit source package in Focal: Fix Released Status in thunderbird source package in Focal: Fix Released Status in tinyjsd source package in Focal: Fix Released Status in thunderbird source package in Groovy: Fix Released Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
(I'm running Ubuntu 20.04.2 LTS) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in thunderbird package in Ubuntu: Fix Released Status in jsunit source package in Bionic: Confirmed Status in thunderbird source package in Bionic: Confirmed Status in jsunit source package in Focal: Fix Released Status in thunderbird source package in Focal: Fix Released Status in tinyjsd source package in Focal: Fix Released Status in thunderbird source package in Groovy: Fix Released Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
Hi Anton, Sorry, I had not also released the enigmail update. I have done that now. Once this gets mirrored out, I think your problem should be fixed. Please let us know. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in thunderbird package in Ubuntu: Fix Released Status in jsunit source package in Bionic: Confirmed Status in thunderbird source package in Bionic: Confirmed Status in jsunit source package in Focal: Fix Released Status in thunderbird source package in Focal: Fix Released Status in tinyjsd source package in Focal: Fix Released Status in thunderbird source package in Groovy: Fix Released Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913333] Re: Calc auto-filter menu inaccessible with fractional scaling enabled
Same issue with snap 7.0.4.2 unfortunately. Strangely, as mentioned above: changing fractional scaling from 150% to 100% fixes the issue temporarily, even when changing back to 150%. -- 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/191 Title: Calc auto-filter menu inaccessible with fractional scaling enabled Status in libreoffice package in Ubuntu: Incomplete Bug description: PROBLEM The auto-filter pull-down menu becomes inaccessible the very moment I move the mouse down to access the filter menu. This happens most of the time, but not always, when fractional scaling is not 100% on my 4K monitor. The menu remains inaccessible for all other scaling factors but 100%. FREQUENCY This happens quite often, but not always, and makes working in CALC with fractional scaling on impossible. Sometimes changing fractional scaling back to 100% and then say to 150% fixes the issue. But most of the time the only way out is to switch the screen to 100%. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: libreoffice-core 1:7.0.3-0ubuntu0.20.10.1 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jan 26 18:19:16 2021 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin SourcePackage: libreoffice UpgradeStatus: Upgraded to groovy on 2020-10-24 (93 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908284] Re: [snap] chromium headless crashes at startup on non-desktop system
~/snap/chromium/common/.cache/fontconfig does not exist. After trying to run chromium headless the first time ~/snap/chromium/current/.config/fontconfig/ is created. Deleting this folder does not fix the crash. You can easily reproduce this error by setting up a clean Ubuntu Core 18 instance within a VM, install the chromium snap, and then run chromium --headless --remote-debugging-port=9222 --remote-debugging- address=[interface-address] https://www.chromium.org/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1908284 Title: [snap] chromium headless crashes at startup on non-desktop system Status in chromium-browser package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 20.04 and it looks like the current stable version of the Chromium snap has an issue running headless: ``` tjcravey@chromium:~$ chromium --headless --remote-debugging-port=9222 https://chromium.org [0100/00.240635:ERROR:zygote_linux.cc(607)] Zygote could not fork: process_type gpu-process numfds 3 child_pid -1 [0100/00.240882:ERROR:zygote_linux.cc(639)] write: Broken pipe (32) Trace/breakpoint trap (core dumped) ``` ``` tjcravey@chromium:~$ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: today at 15:33 UTC channels: latest/stable:87.0.4280.88 2020-12-10 (1424) 124MB - latest/candidate: 87.0.4280.88 2020-12-10 (1424) 124MB - latest/beta: 88.0.4324.41 2020-12-15 (1441) 144MB - latest/edge: 89.0.4350.4 2020-12-11 (1434) 257MB - installed: 87.0.4280.88(1424) 124MB - ``` I was able to revert back to snap 1421 on a different system and that command works fine there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1908284/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916640] Re: Nvidia 340.108 fails to install with kernels 5.11.x - new patches needeed
Update For those willing to be able to compile the above drivers there is a new patch at the following address: https://raw.githubusercontent.com/graysky2//minimyth2/master/script/nvidia/nvidia-340.108/files/nvidia-340.108-fix-5.11 -kernel-compile.patch If anyone makes the new drivers available, I will be grateful and happy to act as a tester... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1916640 Title: Nvidia 340.108 fails to install with kernels 5.11.x - new patches needeed Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: As usual I have opened this (no more) new bug report... As ALWAYS happened in the past, EVERY TWO MONTHS new patches are needed for old Nvidia 340.108 drivers, that is, with each release of a new kernel... Nvidia 340.108 fails to install with kernels 5.11.x - new patches needeed Just to inform develepers that a new patch for Nvidia 340.108 and kernel 5.11 is not yet available here: https://github.com/warpme/minimyth2/blob/master/script/nvidia/nvidia-340.108/files/ Anyway thanks for your great contribution to community and hope you publish new patched drivers without having to always report the same bug... Good day to all the developers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1916640/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916640] Re: Nvidia 340.108 fails to install with kernels 5.11.x - new patches needeed
Update 2 All patches for 340.108 are available here: https://github.com/warpme/minimyth2/tree/master/script/nvidia/nvidia-340.108/files -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1916640 Title: Nvidia 340.108 fails to install with kernels 5.11.x - new patches needeed Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: As usual I have opened this (no more) new bug report... As ALWAYS happened in the past, EVERY TWO MONTHS new patches are needed for old Nvidia 340.108 drivers, that is, with each release of a new kernel... Nvidia 340.108 fails to install with kernels 5.11.x - new patches needeed Just to inform develepers that a new patch for Nvidia 340.108 and kernel 5.11 is not yet available here: https://github.com/warpme/minimyth2/blob/master/script/nvidia/nvidia-340.108/files/ Anyway thanks for your great contribution to community and hope you publish new patched drivers without having to always report the same bug... Good day to all the developers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1916640/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916760] Re: dock badge icon doesn't show
This is when i have uninstall stable discord release. ** Attachment added: "Capture d’écran de 2021-02-24 15-50-41.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1916760/+attachment/5466613/+files/Capture%20d%E2%80%99%C3%A9cran%20de%202021-02-24%2015-50-41.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1916760 Title: dock badge icon doesn't show Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Hello when i use discord canary on ubuntu 20.10 the badge of unread message doesn't show but if i use discord stable release in the same time unread message of canary go on the icon of discord. Of course if i uninstall stable discord, canary doesn't show the badge. I have joined to image to show you. Thanks in advance for our reply and for considering my problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1916760/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916760] [NEW] dock badge icon doesn't show
Public bug reported: Hello when i use discord canary on ubuntu 20.10 the badge of unread message doesn't show but if i use discord stable release in the same time unread message of canary go on the icon of discord. Of course if i uninstall stable discord, canary doesn't show the badge. I have joined to image to show you. Thanks in advance for our reply and for considering my problem. ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Capture d’écran de 2021-02-24 15-48-48.png" https://bugs.launchpad.net/bugs/1916760/+attachment/5466612/+files/Capture%20d%E2%80%99%C3%A9cran%20de%202021-02-24%2015-48-48.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1916760 Title: dock badge icon doesn't show Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Hello when i use discord canary on ubuntu 20.10 the badge of unread message doesn't show but if i use discord stable release in the same time unread message of canary go on the icon of discord. Of course if i uninstall stable discord, canary doesn't show the badge. I have joined to image to show you. Thanks in advance for our reply and for considering my problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1916760/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
Now thunderbird v78.8.0 got available. I hope it gets also backportet. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in thunderbird package in Ubuntu: Fix Released Status in jsunit source package in Bionic: Confirmed Status in thunderbird source package in Bionic: Confirmed Status in jsunit source package in Focal: Fix Released Status in thunderbird source package in Focal: Fix Released Status in tinyjsd source package in Focal: Fix Released Status in thunderbird source package in Groovy: Fix Released Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893827] Re: autopkgtest fails in groovy
it should be fixed with 2.9.2 now ** Changed in: udisks2 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1893827 Title: autopkgtest fails in groovy Status in udisks2 package in Ubuntu: Fix Released Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest- groovy/groovy/arm64/u/udisks2/20200901_174238_f13fc@/log.gz ... == ERROR: test_loop_ro (__main__.Manager) loop device R/O -- Traceback (most recent call last): File "src/tests/integration-test", line 642, in test_loop_ro (path, out_fd_list) = self.manager.call_loop_setup_sync( gi.repository.GLib.GError: udisks-error-quark: GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error waiting for loop object after creating '/dev/loop0': Timed out waiting for object (0) -- Ran 31 tests in 371.897s FAILED (errors=1) Testing installed system binaries daemon path: /usr/libexec/udisks2/udisksd Set up test device: r/w: /dev/sda, r/o: /dev/sr0 autopkgtest [17:42:25]: test upstream-system: ---] autopkgtest [17:42:26]: test upstream-system: - - - - - - - - - - results - - - - - - - - - - upstream-system FAIL non-zero exit status 1 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1893827/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916763] [NEW] Night Light setting only working for a few seconds then It's gone
Public bug reported: 1. Ubuntu info is listed blow: ``` Description:Ubuntu 20.04.2 LTS Release:20.04 ``` 2. the `gnome-control-center` package version is ``` gnome-control-center: 已安装：1:3.36.5-0ubuntu1 候选： 1:3.36.5-0ubuntu1 版本列表： *** 1:3.36.5-0ubuntu1 500 500 http://mirrors.tuna.tsinghua.edu.cn/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1-1ubuntu5 500 500 http://mirrors.tuna.tsinghua.edu.cn/ubuntu focal/main amd64 Packages ``` 3. I expect when the Night Light settings are set, then it should be working as specified. 4. Instead the Night Light settings only work for a few seconds, and then it went back to the original display state as if Night Light is not enabled. This only happens when I'm booting with kernel 5.4.0-66-generic, and everything works like a charm when booting with kernel 5.4.0-65-generic. Please help looking into this. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 24 22:43:23 2021 DistUpgraded: 2020-08-01 23:39:12,134 DEBUG refresh of snap gtk-common-themes succeeded DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:5021] Subsystem: Lenovo Radeon R7 M260 [17aa:5021] InstallationDate: Installed on 2019-11-04 (478 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 20EH0001CD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=UUID=e96f932e-c0e2-496e-b84d-653876b6b3ea ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-08-01 (206 days ago) dmi.bios.date: 11/20/2015 dmi.bios.vendor: LENOVO dmi.bios.version: J5ET50WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EH0001CD dmi.board.vendor: LENOVO dmi.board.version: SDK0E50518 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJ5ET50WW(1.21):bd11/20/2015:svnLENOVO:pn20EH0001CD:pvrThinkPadE450c:rvnLENOVO:rn20EH0001CD:rvrSDK0E50518STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E450c dmi.product.name: 20EH0001CD dmi.product.sku: LENOVO_MT_20EH_BU_Think_FM_ThinkPad E450c dmi.product.version: ThinkPad E450c dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal gnome-control-center ubuntu ** Package changed: xorg (Ubuntu) => gnome-control-center (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/1916763 Title: Night Light setting only working for a few seconds then It's gone Status in gnome-control-center package in Ubuntu: New Bug description: 1. Ubuntu info is listed blow: ``` Description: Ubuntu 20.04.2 LTS Release: 20.04 ``` 2. the `gnome-control-center` package version is ``` gnome-control-center: 已安装：1:3.36.5-0ubuntu1 候选： 1:3.36.5-0ubuntu1 版本列表： *** 1:3.36.5-0ubuntu1 500 500 http://mirrors.tuna.tsinghua.edu.cn/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1-1ubuntu5 500 500 http://mirrors.tuna.tsinghua.edu.cn/ubuntu focal/main amd64 Packages ``` 3. I expect when the Night Light settings are set, then it should be working as specified. 4. Instead the Night Light settings only work for a few seconds, and then it went back to the original display state as if Night Light is not enabled. This only happens when I'm booting with kernel 5.4.0-66-generic, and everything works like a charm when booting with kernel 5.4.0-65-generic. Please help looking into this. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu
[Desktop-packages] [Bug 1890924] Re: Location services work with location services off, 20.04
Hello NoBugs!, or anyone else affected, Accepted geoclue-2.0 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/geoclue-2.0/2.5.6-0ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Description changed: * Impact Disabling the location service in settings isn't reflection on traditional deb applications * Test case - Log in an Ubuntu desktop session - install geoclue-2-demo - go to gnome-control-center, privacy, location and ensure the service is disabled - $ /usr/libexec/geoclue-2.0/demos/where-am-i the script should return a permission error and not a location * Regression potential + [racb] Users who are currently relying on a working location service + despite having a setting disabling it will find that the location + service will stop working because the setting will start to be honoured. + The change is in the client library, try a few applications, deb and snap or flatpak and make sure the status is correct respected - - Not sure if this is the right package, but in the privacy -> location settings, in 18.04 I had to have my application be approved by user to access location with Geoclue. Now it seems this is working without the location services "enabled"?? My application is repeater-START: https://sourceforge.net/projects /repeater-start/ Steps to see issue: 1) install Repeater-START and click the locate me button circle to the left. It goes to your rough location on map. 2) Go to settings, privacy, location, note that location is turned off!? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-settings-daemon 3.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Aug 8 19:38:12 2020 InstallationDate: Installed on 2017-07-29 (1106 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to focal on 2020-06-22 (47 days ago) ** Changed in: geoclue-2.0 (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal ** Also affects: geoclue-2.0 (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: geoclue-2.0 (Ubuntu Groovy) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geoclue-2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1890924 Title: Location services work with location services off, 20.04 Status in geoclue-2.0 package in Ubuntu: Fix Released Status in geoclue-2.0 source package in Focal: Fix Committed Status in geoclue-2.0 source package in Groovy: Triaged Bug description: * Impact Disabling the location service in settings isn't reflection on traditional deb applications * Test case - Log in an Ubuntu desktop session - install geoclue-2-demo - go to gnome-control-center, privacy, location and ensure the service is disabled - $ /usr/libexec/geoclue-2.0/demos/where-am-i the script should return a permission error and not a location * Regression potential [racb] Users who are currently relying on a working location service despite having a setting disabling it will find that the location service will stop working because the setting will start to be honoured. The change is in the client library, try a few applications, deb and snap or flatpak and make sure the status is correct respected - Not sure if this is the right package, but in the privacy -> location settings, in 18.04 I
[Desktop-packages] [Bug 1916765] [NEW] Xorg memory leak
Public bug reported: Ubuntu Version: 20.10 groovy Xorg Version: ii xorg 1:7.7+19ubuntu15 amd64X.Org X Window System xorg seems to have a memory leak - usage grows from 200mb of memory to fill all available memory (several GBs) ps -o pid,user,%mem,command ax | grep Xorg 1071 root 5.6 /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch 1071: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch 55bd3ad76000244K r Xorg 55bd3adb3000 1632K r-x-- Xorg 55bd3af4b000480K r Xorg 55bd3afc4000 16K r Xorg 55bd3afc8000 44K rw--- Xorg 55bd3afd3000128K rw--- [ anon ] 55bd3ba2b000 611340K rw--- [ anon ] 7f572dd68000 12288K rw-s- [ anon ] 7f572e968000 10240K rw-s- [ anon ] 7f5731468000 131072K rw-s- [ shmid=0x2c8018 ] 7f5739468000 24576K rw-s- [ anon ] 7f573ac68000 14336K rw-s- [ anon ] 7f573ba68000 14336K rw-s- [ anon ] 7f573c868000 24576K rw-s- [ anon ] 7f573e068000 24576K rw-s- [ anon ] 7f573f868000 24576K rw-s- [ anon ] 7f5742a68000 24576K rw-s- [ anon ] 7f5744368000 5120K rw-s- [ anon ] 7f5745af8000 24000K rw-s- memfd:xorg (deleted) 7f5747268000 131072K rw-s- [ shmid=0x1a8017 ] 7f574f268000 24576K rw-s- [ anon ] 7f5750a68000 24576K rw-s- [ anon ] 7f5752268000 262144K rw-s- [ shmid=0x28022 ] 7f5762e1e000 12020K rw-s- [ shmid=0xe000a ] 7f57639db000 12020K rw-s- [ shmid=0xe0009 ] 7f5765198000 11072K rw-s- [ shmid=0x9001e ] 7f5765d3 12288K rw-s- [ anon ] 7f576693 10240K rw-s- [ anon ] 7f576733 11072K rw-s- [ shmid=0x9001d ] 7f5767e0 10240K rw-s- [ anon ] 7f576900 8192K rw-s- [ anon ] 7f576980 4096K rw-s- [ shmid=0x90004 ] 7f5769d66000 6760K rw--- [ anon ] 7f576a40 12288K rw-s- [ anon ] 7f576b4d8000 5120K rw-s- [ anon ] 7f576c0d8000 12288K rw-s- [ anon ] 7f576cdd8000 12288K rw-s- [ anon ] 7f576e2d8000 8192K rw-s- [ anon ] 7f576ead8000800K rw-s- [ shmid=0x20032 ] 7f576ed8f000 2628K rw-s- [ shmid=0x130029 ] 7f576f80 262144K rw-s- [ shmid=0x2e ] 7f577f848000784K rw-s- [ shmid=0x2002f ] 7f577fa0 2560K rw-s- [ anon ] 7f578018 7168K rw-s- [ anon ] 7f578088 2560K rw-s- [ anon ] 7f5780b0 4096K rw-s- [ shmid=0x5003e ] 7f578100 24576K rw-s- [ anon ] 7f57828ef000 2628K rw-s- [ shmid=0x130027 ] 7f5782cd6000 1280K rw-s- [ anon ] 7f5782e16000 1280K rw-s- [ anon ] 7f57831b6000896K rw-s- [ anon ] 7f5783296000 6568K rw-s- memfd:xorg (deleted) 7f578390 7168K rw-s- [ anon ] 7f578400132K rw--- [ anon ] 7f5784021000 65404K - [ anon ] 7f578800132K rw--- [ anon ] 7f5788021000 65404K - [ anon ] 7f578c00132K rw--- [ anon ] 7f578c021000 65404K - [ anon ] 7f57900be000896K rw-s- [ anon ] 7f57901a8000 1280K rw-s- [ anon ] 7f57902e8000512K rw-s- [ shmid=0x9801a ] 7f57903e8000196K rw-s- [ shmid=0x98001 ] 7f5790469000212K rw-s- [ shmid=0x68036 ] 7f57905ca000196K rw-s- [ shmid=0x98002 ] 7f57905fb000220K rw-s- [ shmid=0x88016 ] 7f579066a000256K rw-s- [ anon ] 7f57906aa000784K rw-s- [ shmid=0x20030 ] 7f579077e000512K rw-s- [ shmid=0x58039 ] 7f57907fe000 4096K rw-s- [ shmid=0x15 ] 7f5790dae000512K rw-s- [ shmid=0x320006 ] 7f5790e6e000 2048K rw-s- [ shmid=0x23000e ] 7f579110e000800K rw-s- [ shmid=0x20031 ] 7f579126e000320K rw-s- [ anon ] 7f57913fe000 4096K rw-s- [ shmid=0x2d ] 7f579199d000 3584K rw-s- [ anon ] 7f5791d1d000640K rw-s- [ anon ] 7f5791e1d000 1024K rw-s- [ anon ] 7f5791f9d000512K rw-s- [ shmid=0x31001f ] 7f579201d000768K rw-s- [ anon ] 7f5792147000320K rw-s- [ anon ] 7f5792217000512K rw-s- [ anon ] 7f5792297000 8K rw-s- [ anon ] 7f579229d000512K rw-s- [ shmid=0x2c8011 ] 7f579232d000 64K rw-s- [ anon ] 7f579236d000896K rw-s- [ anon ] 7f579244e000732K rw-s- [ shmid=0x2f8010 ] 7f579252f000320K rw-s- [ anon ] 7f57925c5000384K rw-s- [ anon ] 7f5792675000388K rw-s- [ shmid=0x340044 ] 7f57926d6000320K rw-s- [ anon ] 7f5792726000 1280K rw-s- [ anon ] 7f5792866000 8K rw-s- [ anon ] 7f579288f000732K rw-s- [ shmid=0x2f8013 ] 7f5792964000320K rw-s- [ anon ] 7f57929b4000 8K rw-s- [ anon ] 7f57929b6000 8K rw-s- [ anon ] 7f5792a3 8K rw-s- [ anon ] 7f5792a32000 8K rw-s- [ anon ] 7f5792a34000 8K rw-s- [ ano
[Desktop-packages] [Bug 1916763] Re: Night Light setting only working for a few seconds then It's gone
Thanks, if it's happening with a kernel update then it's a kernel issue... ** Package changed: gnome-control-center (Ubuntu) => linux (Ubuntu) -- 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/1916763 Title: Night Light setting only working for a few seconds then It's gone Status in linux package in Ubuntu: New Bug description: 1. Ubuntu info is listed blow: ``` Description: Ubuntu 20.04.2 LTS Release: 20.04 ``` 2. the `gnome-control-center` package version is ``` gnome-control-center: 已安装：1:3.36.5-0ubuntu1 候选： 1:3.36.5-0ubuntu1 版本列表： *** 1:3.36.5-0ubuntu1 500 500 http://mirrors.tuna.tsinghua.edu.cn/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1-1ubuntu5 500 500 http://mirrors.tuna.tsinghua.edu.cn/ubuntu focal/main amd64 Packages ``` 3. I expect when the Night Light settings are set, then it should be working as specified. 4. Instead the Night Light settings only work for a few seconds, and then it went back to the original display state as if Night Light is not enabled. This only happens when I'm booting with kernel 5.4.0-66-generic, and everything works like a charm when booting with kernel 5.4.0-65-generic. Please help looking into this. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 24 22:43:23 2021 DistUpgraded: 2020-08-01 23:39:12,134 DEBUG refresh of snap gtk-common-themes succeeded DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:5021] Subsystem: Lenovo Radeon R7 M260 [17aa:5021] InstallationDate: Installed on 2019-11-04 (478 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 20EH0001CD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=UUID=e96f932e-c0e2-496e-b84d-653876b6b3ea ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-08-01 (206 days ago) dmi.bios.date: 11/20/2015 dmi.bios.vendor: LENOVO dmi.bios.version: J5ET50WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EH0001CD dmi.board.vendor: LENOVO dmi.board.version: SDK0E50518 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJ5ET50WW(1.21):bd11/20/2015:svnLENOVO:pn20EH0001CD:pvrThinkPadE450c:rvnLENOVO:rn20EH0001CD:rvrSDK0E50518STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E450c dmi.product.name: 20EH0001CD dmi.product.sku: LENOVO_MT_20EH_BU_Think_FM_ThinkPad E450c dmi.product.version: ThinkPad E450c dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916763/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
I've done it and it's still registered primary action for that user too,
it did not change anything.
--
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:
Fix Released
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:
Update (based on #296)
=
The latest kernel tree
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
has the complete solution to fix this bug. So we can expect kernel
v5.11 to fix this issue without any additional work.
Before the release of v5.11, you are suggested to use #189 to save your
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd
driver is built into the initramfs. So you have to rebuild the initramfs after
replacing the old module with new one.
On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs
-u`.
The complete solution is three patches,
- 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce
filter setting in IRQ type setting")
- 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way
to disable debounce filter")
- 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into
account debounce settings")
The first two patches has reached the stable tree. If the last one is
also backported to LTS kernel, you won't need to install kernel 5.11.
But I don't know when this will happen.
Original bug report
===
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:
[Desktop-packages] [Bug 1913453] Re: gnome-shell freeze
apport information ** Tags added: apport-collected ** Description changed: System Description: Ubuntu 20.04.1 LTS Release: 20.04 Description: Plugging in USB hub with peripherals while system is running causes gradual lag of a visual response, until freezing. usually takes < 1 min. Only work around is to sleep system between plugging in hub. I thought I fixed it by change DM but the issue has persisted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 27 14:27:12 2021 DistUpgraded: 2020-04-28 14:42:33,856 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-62-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-64-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-65-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] InstallationDate: Installed on 2018-12-25 (763 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 2324AS7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=957184f1-8feb-4ca9-ac97-3fb70937b4ac ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-04-28 (274 days ago) dmi.bios.date: 04/11/2018 dmi.bios.vendor: LENOVO dmi.bios.version: G2ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324AS7 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: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ETB2WW(2.72):bd04/11/2018:svnLENOVO:pn2324AS7:pvrThinkPadX230:rvnLENOVO:rn2324AS7:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2324AS7 dmi.product.sku: LENOVO_MT_2324 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~ppa1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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 xserver.bootTime: Tue Nov 24 16:32:27 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2.4 xserver.video_driver: modeset + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.16 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2018-12-25 (792 days ago) + InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) + Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 + RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 + Tags: third-party-packages focal wayland-session + Uname: Linux 5.4.0-65-generic x86_64 + UpgradeStatus: Upgraded to focal on 2020-04-28 (302 days ago) + UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo wireshark + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1913453/+attachment/5466682/+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/1913453 Title: gnome-shell freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: System Description: Ubuntu 20.04.1 LTS Release: 20.04 Description: Plugging in USB hub with peripherals while system is running causes gradual lag of a visual response, until freezing. usually takes <
[Desktop-packages] [Bug 1913453] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1913453/+attachment/5466684/+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/1913453 Title: gnome-shell freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: System Description: Ubuntu 20.04.1 LTS Release: 20.04 Description: Plugging in USB hub with peripherals while system is running causes gradual lag of a visual response, until freezing. usually takes < 1 min. Only work around is to sleep system between plugging in hub. I thought I fixed it by change DM but the issue has persisted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 27 14:27:12 2021 DistUpgraded: 2020-04-28 14:42:33,856 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-62-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-64-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-65-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] InstallationDate: Installed on 2018-12-25 (763 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 2324AS7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=957184f1-8feb-4ca9-ac97-3fb70937b4ac ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-04-28 (274 days ago) dmi.bios.date: 04/11/2018 dmi.bios.vendor: LENOVO dmi.bios.version: G2ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324AS7 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: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ETB2WW(2.72):bd04/11/2018:svnLENOVO:pn2324AS7:pvrThinkPadX230:rvnLENOVO:rn2324AS7:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2324AS7 dmi.product.sku: LENOVO_MT_2324 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~ppa1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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 xserver.bootTime: Tue Nov 24 16:32:27 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2.4 xserver.video_driver: modeset --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-12-25 (792 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 Tags: third-party-packages focal wayland-session Uname: Linux 5.4.0-65-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-28 (302 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913453/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~
[Desktop-packages] [Bug 1913453] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1913453/+attachment/5466683/+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/1913453 Title: gnome-shell freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: System Description: Ubuntu 20.04.1 LTS Release: 20.04 Description: Plugging in USB hub with peripherals while system is running causes gradual lag of a visual response, until freezing. usually takes < 1 min. Only work around is to sleep system between plugging in hub. I thought I fixed it by change DM but the issue has persisted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 27 14:27:12 2021 DistUpgraded: 2020-04-28 14:42:33,856 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-62-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-64-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-65-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] InstallationDate: Installed on 2018-12-25 (763 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 2324AS7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=957184f1-8feb-4ca9-ac97-3fb70937b4ac ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-04-28 (274 days ago) dmi.bios.date: 04/11/2018 dmi.bios.vendor: LENOVO dmi.bios.version: G2ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324AS7 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: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ETB2WW(2.72):bd04/11/2018:svnLENOVO:pn2324AS7:pvrThinkPadX230:rvnLENOVO:rn2324AS7:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2324AS7 dmi.product.sku: LENOVO_MT_2324 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~ppa1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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 xserver.bootTime: Tue Nov 24 16:32:27 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2.4 xserver.video_driver: modeset --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-12-25 (792 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 Tags: third-party-packages focal wayland-session Uname: Linux 5.4.0-65-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-28 (302 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913453/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desk
[Desktop-packages] [Bug 1913453] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1913453/+attachment/5466685/+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/1913453 Title: gnome-shell freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: System Description: Ubuntu 20.04.1 LTS Release: 20.04 Description: Plugging in USB hub with peripherals while system is running causes gradual lag of a visual response, until freezing. usually takes < 1 min. Only work around is to sleep system between plugging in hub. I thought I fixed it by change DM but the issue has persisted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 27 14:27:12 2021 DistUpgraded: 2020-04-28 14:42:33,856 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-62-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-64-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-65-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] InstallationDate: Installed on 2018-12-25 (763 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 2324AS7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=957184f1-8feb-4ca9-ac97-3fb70937b4ac ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-04-28 (274 days ago) dmi.bios.date: 04/11/2018 dmi.bios.vendor: LENOVO dmi.bios.version: G2ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324AS7 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: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ETB2WW(2.72):bd04/11/2018:svnLENOVO:pn2324AS7:pvrThinkPadX230:rvnLENOVO:rn2324AS7:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2324AS7 dmi.product.sku: LENOVO_MT_2324 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~ppa1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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 xserver.bootTime: Tue Nov 24 16:32:27 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2.4 xserver.video_driver: modeset --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-12-25 (792 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 Tags: third-party-packages focal wayland-session Uname: Linux 5.4.0-65-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-28 (302 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913453/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packag
[Desktop-packages] [Bug 1913453] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1913453/+attachment/5466686/+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/1913453 Title: gnome-shell freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: System Description: Ubuntu 20.04.1 LTS Release: 20.04 Description: Plugging in USB hub with peripherals while system is running causes gradual lag of a visual response, until freezing. usually takes < 1 min. Only work around is to sleep system between plugging in hub. I thought I fixed it by change DM but the issue has persisted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 27 14:27:12 2021 DistUpgraded: 2020-04-28 14:42:33,856 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-62-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-64-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-65-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] InstallationDate: Installed on 2018-12-25 (763 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 2324AS7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=957184f1-8feb-4ca9-ac97-3fb70937b4ac ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-04-28 (274 days ago) dmi.bios.date: 04/11/2018 dmi.bios.vendor: LENOVO dmi.bios.version: G2ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324AS7 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: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ETB2WW(2.72):bd04/11/2018:svnLENOVO:pn2324AS7:pvrThinkPadX230:rvnLENOVO:rn2324AS7:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2324AS7 dmi.product.sku: LENOVO_MT_2324 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~ppa1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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 xserver.bootTime: Tue Nov 24 16:32:27 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2.4 xserver.video_driver: modeset --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-12-25 (792 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 Tags: third-party-packages focal wayland-session Uname: Linux 5.4.0-65-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-28 (302 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913453/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-pack
[Desktop-packages] [Bug 1913453] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1913453/+attachment/5466687/+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/1913453 Title: gnome-shell freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: System Description: Ubuntu 20.04.1 LTS Release: 20.04 Description: Plugging in USB hub with peripherals while system is running causes gradual lag of a visual response, until freezing. usually takes < 1 min. Only work around is to sleep system between plugging in hub. I thought I fixed it by change DM but the issue has persisted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 27 14:27:12 2021 DistUpgraded: 2020-04-28 14:42:33,856 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-62-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-64-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-65-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] InstallationDate: Installed on 2018-12-25 (763 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 2324AS7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=957184f1-8feb-4ca9-ac97-3fb70937b4ac ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-04-28 (274 days ago) dmi.bios.date: 04/11/2018 dmi.bios.vendor: LENOVO dmi.bios.version: G2ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324AS7 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: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ETB2WW(2.72):bd04/11/2018:svnLENOVO:pn2324AS7:pvrThinkPadX230:rvnLENOVO:rn2324AS7:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2324AS7 dmi.product.sku: LENOVO_MT_2324 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~ppa1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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 xserver.bootTime: Tue Nov 24 16:32:27 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2.4 xserver.video_driver: modeset --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-12-25 (792 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 Tags: third-party-packages focal wayland-session Uname: Linux 5.4.0-65-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-28 (302 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913453/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-pack
[Desktop-packages] [Bug 1913453] Re: gnome-shell freeze
settings.txt ** Attachment added: "settings.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913453/+attachment/5466688/+files/settings.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/1913453 Title: gnome-shell freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: System Description: Ubuntu 20.04.1 LTS Release: 20.04 Description: Plugging in USB hub with peripherals while system is running causes gradual lag of a visual response, until freezing. usually takes < 1 min. Only work around is to sleep system between plugging in hub. I thought I fixed it by change DM but the issue has persisted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 27 14:27:12 2021 DistUpgraded: 2020-04-28 14:42:33,856 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-62-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-64-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-65-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] InstallationDate: Installed on 2018-12-25 (763 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 2324AS7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=957184f1-8feb-4ca9-ac97-3fb70937b4ac ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-04-28 (274 days ago) dmi.bios.date: 04/11/2018 dmi.bios.vendor: LENOVO dmi.bios.version: G2ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324AS7 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: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ETB2WW(2.72):bd04/11/2018:svnLENOVO:pn2324AS7:pvrThinkPadX230:rvnLENOVO:rn2324AS7:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2324AS7 dmi.product.sku: LENOVO_MT_2324 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~ppa1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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 xserver.bootTime: Tue Nov 24 16:32:27 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2.4 xserver.video_driver: modeset --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-12-25 (792 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 Tags: third-party-packages focal wayland-session Uname: Linux 5.4.0-65-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-28 (302 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913453/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/
[Desktop-packages] [Bug 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 onward
Hello, I have just installed Kubuntu 21.04 on my old Sony laptop (VGN-AW11M_H v: C6010CXT). As usual, the Nouveau driver was installed for my graphics card Device-1: NVIDIA G98M [GeForce 9300M GS] driver: nvidia v: 340.108. With the Nouveau driver the system tends to work kind of o.k., but freezes, eg. sometimes when moving a window to the upper edge of my KDE monitor, so as to make it "full screen". I used the backported NVIDIA driver o.k. under 20.10 (kernel 5.8.0-26-generic x86_64). Is there a backport already for 21.04 (vmlinuz-5.10.0-14-generic)? Thanks for your help H. Stoellinger -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1872950 Title: Nvidia 340.108 fails to install with kernels 5.5 onward Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Groovy: Fix Released Bug description: SRU request: [Impact] * Installing the 340 driver will fail when running Linux 5.7 or newer. [Test Case] * Install nvidia-340 from -proposed. * Check that the modules was built and installed, using the following command: dkms status [Regression Potential] * The driver once built and installed could be not working and lead to have the desktop not starting for example. Check that you get a desktop loaded and decent performances Hi developers, thanks for your great work on porting legacy drivers to Ubuntu. Anyway I have to complain in not seeing Nvidia 340.108 driver for kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4, because Nvidia 340.108 fails to install with kernels 5.5 and 5.6. Archlinux already has a driver for Kernel 5.6 via AUR (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has one for kernel 5.5. So, the question is: when will we see a new version in repositories? Bye and have a nice day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915712] Re: [snap] configure hook fails because the gnome-3-28-1804 platform snap isn't connected
** Changed in: snapcraft (Ubuntu) Status: New => In Progress ** Changed in: snapcraft (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: snapcraft (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1915712 Title: [snap] configure hook fails because the gnome-3-28-1804 platform snap isn't connected Status in Snapcraft: New Status in chromium-browser package in Ubuntu: Incomplete Status in snapcraft package in Ubuntu: In Progress Status in snapd package in Ubuntu: Incomplete Bug description: happened on do-release-upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 87.0.4280.66-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18 Uname: Linux 4.15.0-135-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-VGA-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAEcmOt9h4RchURAQMIJh546JrlplhJmSMRUFS/7wABAQEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAeC0RAAAe/QA4Sx5TDgAKICAgICAg/wBMNzgwQzA1NDQwNDQK/ABBTDE5MTYKICAgICAgAGE= modes: 1280x1024 1280x1024 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 720x400 Date: Mon Feb 15 13:26:20 2021 Desktop-Session: 'None' 'None' '/usr/local/share:/usr/share:/var/lib/snapd/desktop' Env: 'None' 'None' ErrorMessage: »neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück InstallationDate: Installed on 2017-06-27 (1328 days ago) InstallationMedia: Kubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) InstalledPlugins: Load-Avg-1min: 0.61 Load-Processes-Running-Percent: 0.2% MachineType: Hewlett-Packard HP Pro3500 Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-135-generic root=UUID=093e88ea-7b5e-4e39-b56c-03b28ad06dd2 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: chromium-browser Title: package chromium-browser 87.0.4280.66-0ubuntu0.18.04.1 failed to install/upgrade: »neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to focal on 2021-02-15 (0 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: AMI dmi.bios.version: 8.17 dmi.board.name: 2ABF dmi.board.vendor: Foxconn dmi.board.version: 3.20 dmi.chassis.asset.tag: CZC34935PY dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr8.17:bd10/25/2013:svnHewlett-Packard:pnHPPro3500Series:pvr:rvnFoxconn:rn2ABF:rvr3.20:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Pro3500 Series dmi.sys.vendor: Hewlett-Packard modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/snapcraft/+bug/1915712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916786] [NEW] weak dependency to libreoffice-sdbc-hsqldb
Public bug reported: The user can't create a new Base file with the wizard if the libreoffice-sdbc-hsqldb package isn't installed. The package libreoffice-base-drivers has only a "suggests" dependency to libreoffice-sdbc-hsqldb. It should have a "depends" dependency. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-base-drivers 1:6.4.6-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Feb 24 18:32:22 2021 InstallationDate: Installed on 2020-10-12 (134 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.logrotate.d.apport: 2021-02-03T16:41:54.752959 ** Affects: libreoffice (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 libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1916786 Title: weak dependency to libreoffice-sdbc-hsqldb Status in libreoffice package in Ubuntu: New Bug description: The user can't create a new Base file with the wizard if the libreoffice-sdbc-hsqldb package isn't installed. The package libreoffice-base-drivers has only a "suggests" dependency to libreoffice-sdbc-hsqldb. It should have a "depends" dependency. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-base-drivers 1:6.4.6-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Feb 24 18:32:22 2021 InstallationDate: Installed on 2020-10-12 (134 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.logrotate.d.apport: 2021-02-03T16:41:54.752959 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1916786/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903765] Re: Subwoofer mapped incorrectly on Macbook 2.1
This problem persists on the same system with all the latest updates. I
did however notice that in the "hardware" part of the GUI there is no
longer a "2.1" option, so defaulting to analogue stereo output.
I tried connecting an external speaker ("headphone") and it sounded as
it should.
--
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/1903765
Title:
Subwoofer mapped incorrectly on Macbook 2.1
Status in alsa-driver package in Ubuntu:
New
Bug description:
It seems the 2.0 speakers get mapped to Speaker and the subwoofer is
mapped to HEADPHONES, not LFE. I confirmed this by raising the volume
for "headphones" in alsamixer and getting the base to play along.
However, there seems to be no workaround in Ubuntu just using the
sound GUI. My guess is, if ALSA would do the mapping to LFE correctly,
I could use the 2.1 hardware map in the Ubuntu sound settings and all
would be well!
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: diskdoc3271 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Tue Nov 10 21:33:29 2020
InstallationDate: Installed on 2020-10-08 (33 days ago)
InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64
(20200423)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
Symptom_Card: Inbyggt ljud - HDA Intel
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: Only some of outputs are working
Title: [HDA-Intel - HDA Intel, playback] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/27/07
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MB21.88Z.00A5.B07.0706270922
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mac-F4208CAA
dmi.board.vendor: Apple Inc.
dmi.board.version: PVT
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F4208CAA
dmi.modalias:
dmi:bvnAppleInc.:bvrMB21.88Z.00A5.B07.0706270922:bd06/27/07:svnAppleInc.:pnMacBook2,1:pvr1.0:rvnAppleInc.:rnMac-F4208CAA:rvrPVT:cvnAppleInc.:ct10:cvrMac-F4208CAA:
dmi.product.family: MacBook
dmi.product.name: MacBook2,1
dmi.product.sku: System SKUNumber
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1903765/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1839068] Re: Wrong password every time after changing login password
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: seahorse (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1839068 Title: Wrong password every time after changing login password Status in seahorse package in Ubuntu: Confirmed Bug description: After changing password with "passwd" command it's not possible to open the keyring anymore. Each time I have the dialog that open asking me for the password. I've tried to enter the old password and the new password but nothing changes. I've changed back the login password to the old one but even in that case the seahorse password dialog opens saying that the login password doesn't matches the keyring password and asking me to enter it again. I need a procedure to change the keyring password without login into the seahorse, so that it can match the login password of Ubuntu. Ubuntu 18.04.2 LTS Seahorse 3.20.0-5 from http://ch.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1839068/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915712] Re: [snap] configure hook fails because the gnome-3-28-1804 platform snap isn't connected
I'm sorry but I'm afraid I can't help any further. I needed the machine back in the office so I just removed the chromium-browser debs (as firefox is the destined browser anyways). The machine originally had 16.04 installed and had an upgrade to 18.04 done in 2018, maybe there was some legacy stuff it stumbled over. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1915712 Title: [snap] configure hook fails because the gnome-3-28-1804 platform snap isn't connected Status in Snapcraft: New Status in chromium-browser package in Ubuntu: Incomplete Status in snapcraft package in Ubuntu: In Progress Status in snapd package in Ubuntu: Incomplete Bug description: happened on do-release-upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 87.0.4280.66-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18 Uname: Linux 4.15.0-135-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-VGA-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAEcmOt9h4RchURAQMIJh546JrlplhJmSMRUFS/7wABAQEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAeC0RAAAe/QA4Sx5TDgAKICAgICAg/wBMNzgwQzA1NDQwNDQK/ABBTDE5MTYKICAgICAgAGE= modes: 1280x1024 1280x1024 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 720x400 Date: Mon Feb 15 13:26:20 2021 Desktop-Session: 'None' 'None' '/usr/local/share:/usr/share:/var/lib/snapd/desktop' Env: 'None' 'None' ErrorMessage: »neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück InstallationDate: Installed on 2017-06-27 (1328 days ago) InstallationMedia: Kubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) InstalledPlugins: Load-Avg-1min: 0.61 Load-Processes-Running-Percent: 0.2% MachineType: Hewlett-Packard HP Pro3500 Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-135-generic root=UUID=093e88ea-7b5e-4e39-b56c-03b28ad06dd2 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: chromium-browser Title: package chromium-browser 87.0.4280.66-0ubuntu0.18.04.1 failed to install/upgrade: »neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to focal on 2021-02-15 (0 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: AMI dmi.bios.version: 8.17 dmi.board.name: 2ABF dmi.board.vendor: Foxconn dmi.board.version: 3.20 dmi.chassis.asset.tag: CZC34935PY dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr8.17:bd10/25/2013:svnHewlett-Packard:pnHPPro3500Series:pvr:rvnFoxconn:rn2ABF:rvr3.20:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Pro3500 Series dmi.sys.vendor: Hewlett-Packard modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/snapcraft/+bug/1915712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
Hi Robie, Thank's a lot – everything updated fine now! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in thunderbird package in Ubuntu: Fix Released Status in jsunit source package in Bionic: Confirmed Status in thunderbird source package in Bionic: Confirmed Status in jsunit source package in Focal: Fix Released Status in thunderbird source package in Focal: Fix Released Status in tinyjsd source package in Focal: Fix Released Status in thunderbird source package in Groovy: Fix Released Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913333] Re: Calc auto-filter menu inaccessible with fractional scaling enabled
** Tags added: rls-gg-incoming -- 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/191 Title: Calc auto-filter menu inaccessible with fractional scaling enabled Status in libreoffice package in Ubuntu: Incomplete Bug description: PROBLEM The auto-filter pull-down menu becomes inaccessible the very moment I move the mouse down to access the filter menu. This happens most of the time, but not always, when fractional scaling is not 100% on my 4K monitor. The menu remains inaccessible for all other scaling factors but 100%. FREQUENCY This happens quite often, but not always, and makes working in CALC with fractional scaling on impossible. Sometimes changing fractional scaling back to 100% and then say to 150% fixes the issue. But most of the time the only way out is to switch the screen to 100%. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: libreoffice-core 1:7.0.3-0ubuntu0.20.10.1 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jan 26 18:19:16 2021 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin SourcePackage: libreoffice UpgradeStatus: Upgraded to groovy on 2020-10-24 (93 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916550] Re: simple-scan chooses scanned image size improperly
I cant get a screenshot (apparently with the selection/list panel open, the system is ignoring the screenshot keystrokes). I've attached a photo of the list. Please note, none of the three E* entities on this list work at all, only the highlighted one at the bottom of the list (and not highlighted at the top). ** Attachment added: "Photo of the sreen with the scanner list" https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1916550/+attachment/5466738/+files/KIMG0898.JPG -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1916550 Title: simple-scan chooses scanned image size improperly Status in simple-scan package in Ubuntu: Incomplete Bug description: I have an HP OfficeJet 4654 which the scanner recognized (after a while, but eventually it finds the OfficeJet). The scanner can do single pages on the platen and has a sheet feeder as well. When I scan single pages on the platen, the size is correctly set to Letter (It could do A4 but I don't use that). However, if I use the sheet feeder, the scan defaults to Legal size. If I change the Preference to Letter in the gear settings, I can get Letter sized scans with the feeder. However, with the Preference set to Letter, the single platen scanned documents come out Legal sized with the area below the Letter sized form blackened in. This is absurd. If I tell it to use Letter size, it should not override this and produce incorrect Legal sized scans, regardless of whether the source is on the platen or from the feeder. What I truly don't understand is why I get a Legal size scan on a Letter sized piece of paper in the sheet feeder at all (the default behavior). The app is clearly capable of producing letter sized scans when told to do so. I also don't understand why the scanning tool overrides my Preference setting for Letter size when I scan from the platen. The new interface also makes it more difficult to change the Preferences - there's no Save or OK button, just the upper-right- corner x which usually means don't save - very confusing and user unfriendly. Source: https://gitlab.gnome.org/GNOME/simple-scan Description: Ubuntu 20.04.2 LTS Release: 20.04 Simple-scan Version: 3.36.3 What I expected to happen: If I scan a letter sized document, I expect a letter sized scan. If I scan multiple sheets all letter sized, I expect all pages to scan at letter sized. What happens instead: If the paper size Preference is set to Automatic, the platen scans are correct but the sheet feeder scans are all legal sized. If the paper size Preference is set to Letter, the sheet feeder scans are all letter sized but the single page platen scans are all legal sized with a blackened 3" section at the bottom of the page. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Feb 22 18:04:51 2021 InstallationDate: Installed on 2020-10-01 (145 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=97168ae7-ec8a-49b7-8ef8-6b377b98a588 ro nosplash SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.20 dmi.board.name: Z97 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd05/12/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1916550/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916786] Re: weak dependency to libreoffice-sdbc-hsqldb
** Tags added: packaging unmetdeps -- 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/1916786 Title: weak dependency to libreoffice-sdbc-hsqldb Status in libreoffice package in Ubuntu: New Bug description: The user can't create a new Base file with the wizard if the libreoffice-sdbc-hsqldb package isn't installed. The package libreoffice-base-drivers has only a "suggests" dependency to libreoffice-sdbc-hsqldb. It should have a "depends" dependency. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-base-drivers 1:6.4.6-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Feb 24 18:32:22 2021 InstallationDate: Installed on 2020-10-12 (134 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.logrotate.d.apport: 2021-02-03T16:41:54.752959 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1916786/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1705626] Re: Use GNOME Software for system upgrades
[Important] This must be able to perform as two separate tasks (not together); UI enhancement in update section may help to address that and classic terminal ways, software updater should remain as it -- 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/1705626 Title: Use GNOME Software for system upgrades Status in gnome-software package in Ubuntu: Triaged Bug description: Fedora can do it with a simple click, "Linux for humans beings" we have to continue make Ubuntu easy, also this will be better for developers without the need to maintain update-manager anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1705626/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767369] Re: Offer Ubuntu upgrades via Ubuntu Software
*** This bug is a duplicate of bug 1705626 *** https://bugs.launchpad.net/bugs/1705626 ** This bug has been marked a duplicate of bug 1705626 Use GNOME Software for system upgrades -- 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/1767369 Title: Offer Ubuntu upgrades via Ubuntu Software Status in gnome-software package in Ubuntu: Confirmed Bug description: Please include pages for new Ubuntu releases to download and install the latest updated OS right from the Software Center, see what's new, and learn more. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.26.1-0ubuntu2.17.10.1 ProcVersionSignature: Ubuntu 4.13.0-39.44-lowlatency 4.13.16 Uname: Linux 4.13.0-39-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 09:24:39 2018 InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.1-0ubuntu2.17.10.1 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1767369/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890924] Re: Location services work with location services off, 20.04
I upgraded my 20.04 with the proposed-updates, restarted, and I got an alert that I needed to accept location permissions upon hitting the lower left locate button on my app, initially. I open the privacy settings in location and my app is not listed?? However, location now works, at least every other time. I wonder if anyone else can run a similar test? I see no applications have asked for location access, in privacy settings. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geoclue-2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1890924 Title: Location services work with location services off, 20.04 Status in geoclue-2.0 package in Ubuntu: Fix Released Status in geoclue-2.0 source package in Focal: Fix Committed Status in geoclue-2.0 source package in Groovy: Triaged Bug description: * Impact Disabling the location service in settings isn't reflection on traditional deb applications * Test case - Log in an Ubuntu desktop session - install geoclue-2-demo - go to gnome-control-center, privacy, location and ensure the service is disabled - $ /usr/libexec/geoclue-2.0/demos/where-am-i the script should return a permission error and not a location * Regression potential [racb] Users who are currently relying on a working location service despite having a setting disabling it will find that the location service will stop working because the setting will start to be honoured. The change is in the client library, try a few applications, deb and snap or flatpak and make sure the status is correct respected - Not sure if this is the right package, but in the privacy -> location settings, in 18.04 I had to have my application be approved by user to access location with Geoclue. Now it seems this is working without the location services "enabled"?? My application is repeater-START: https://sourceforge.net/projects /repeater-start/ Steps to see issue: 1) install Repeater-START and click the locate me button circle to the left. It goes to your rough location on map. 2) Go to settings, privacy, location, note that location is turned off!? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-settings-daemon 3.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Aug 8 19:38:12 2020 InstallationDate: Installed on 2017-07-29 (1106 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to focal on 2020-06-22 (47 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1890924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1685754] Re: 'systemd --user' unduly forces umask=0022
> REGRESSION: With systemd 246.6-1ubuntu1 from Ubuntu 20.10 Beta (Groovy
Gorilla), the issue had reappeared
I just tested with groovy and can't reproduce the issue; umask is
correct under gnome-terminal
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1685754
Title:
'systemd --user' unduly forces umask=0022
Status in gedit:
Invalid
Status in gnome-session:
Invalid
Status in GNOME Terminal:
Confirmed
Status in Nautilus:
Invalid
Status in systemd:
Unknown
Status in dbus package in Ubuntu:
Invalid
Status in gnome-terminal package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Fix Released
Status in dbus source package in Bionic:
Invalid
Status in gnome-terminal source package in Bionic:
Invalid
Status in systemd source package in Bionic:
Confirmed
Bug description:
In order to set the default umask of my users to 027 or 007, I
followed the instructions provided in 'man pam_umask' :
In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
'umask=007' (for myself).
Then, MOST graphical applications systematically run with the correct
umask.
In particular, when I press Alt-F2, run 'xterm sh' and type 'umask',
it systematically displays 0007.
But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask',
it systematically displays 0022.
That is BAD, and is a security issue.
Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each
'~/.bashrc', add following content :
UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)"
if [ "$UMASK" ]; then
umask "${UMASK#$USER:*,umask=}"
fi
In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged.
Thank you in advance for a quick correction.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-terminal 3.20.2-1ubuntu8
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Mon Apr 24 08:36:58 2017
InstallationDate: Installed on 2017-03-28 (26 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913453] Re: gnome-shell freeze
Not sure if it's helpful but here's another crash from today. Pretty sure network-manager crashed which has happened before, as i lost connection to my SSH'd devices and could not connect back to my AP. Complete freeze happened promptly after. This happened after using a usb-hub switch. ** Attachment added: "prevboot3.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913453/+attachment/5466761/+files/prevboot3.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/1913453 Title: gnome-shell freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: System Description: Ubuntu 20.04.1 LTS Release: 20.04 Description: Plugging in USB hub with peripherals while system is running causes gradual lag of a visual response, until freezing. usually takes < 1 min. Only work around is to sleep system between plugging in hub. I thought I fixed it by change DM but the issue has persisted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 27 14:27:12 2021 DistUpgraded: 2020-04-28 14:42:33,856 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-62-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-64-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-65-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] InstallationDate: Installed on 2018-12-25 (763 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 2324AS7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=957184f1-8feb-4ca9-ac97-3fb70937b4ac ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-04-28 (274 days ago) dmi.bios.date: 04/11/2018 dmi.bios.vendor: LENOVO dmi.bios.version: G2ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324AS7 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: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ETB2WW(2.72):bd04/11/2018:svnLENOVO:pn2324AS7:pvrThinkPadX230:rvnLENOVO:rn2324AS7:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2324AS7 dmi.product.sku: LENOVO_MT_2324 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~ppa1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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 xserver.bootTime: Tue Nov 24 16:32:27 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2.4 xserver.video_driver: modeset --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-12-25 (792 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 Tags: third-party-packages focal wayland-session Uname: Linux 5.4.0-65-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-28 (302 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo wireshark _MarkForUpload: T
[Desktop-packages] [Bug 1685754] Re: 'systemd --user' unduly forces umask=0022
** Description changed:
+ [impact]
+
+ pam_umask, from /etc/passwd, is not honored in systemd --user instances
+
+ [test case]
+
+ on a desktop system, edit /etc/passwd to change the test user entry
+ (e.g. the 'ubuntu' user) to include 'umask=007' in the GECOS field (5th
+ field). For example change:
+
+ ubuntu:x:1000:1000:Ubuntu:/home/ubuntu:/bin/bash
+
+ to:
+
+ ubuntu:x:1000:1000:Ubuntu,umask=007:/home/ubuntu:/bin/bash
+
+ You may need to reboot for your X session to pick up the change.
+
+ Then, from the graphical desktop, open a terminal and run:
+
+ $ gnome-terminal -e sh
+
+ in the opened terminal, run:
+
+ $ umask
+
+ the number shown should be 0007, as set in the passwd file
+
+ [regression potential]
+
+ any regression would likely result in an incorrect umask for the user
+ whose passwd entry is modified.
+
+ [scope]
+
+ this is needed only for b
+
+ this is fixed in systemd upstream by commit
+ 5e37d1930b41b24c077ce37c6db0e36c745106c7 which was first included in
+ v246, so this is fixed in g and later. This commit was also picked up by
+ Debian and included in the v245 release for focal, so this is fixed in
+ focal already.
+
+ [original description]
+
In order to set the default umask of my users to 027 or 007, I followed
the instructions provided in 'man pam_umask' :
In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
'umask=007' (for myself).
Then, MOST graphical applications systematically run with the correct
umask.
In particular, when I press Alt-F2, run 'xterm sh' and type 'umask', it
systematically displays 0007.
But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask', it
systematically displays 0022.
That is BAD, and is a security issue.
-
Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each
'~/.bashrc', add following content :
UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)"
if [ "$UMASK" ]; then
- umask "${UMASK#$USER:*,umask=}"
+ umask "${UMASK#$USER:*,umask=}"
fi
-
- In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged.
+ In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask
+ unchanged.
Thank you in advance for a quick correction.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-terminal 3.20.2-1ubuntu8
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Mon Apr 24 08:36:58 2017
InstallationDate: Installed on 2017-03-28 (26 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1685754
Title:
'systemd --user' unduly forces umask=0022
Status in gedit:
Invalid
Status in gnome-session:
Invalid
Status in GNOME Terminal:
Confirmed
Status in Nautilus:
Invalid
Status in systemd:
Unknown
Status in dbus package in Ubuntu:
Invalid
Status in gnome-terminal package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Fix Released
Status in dbus source package in Bionic:
Invalid
Status in gnome-terminal source package in Bionic:
Invalid
Status in systemd source package in Bionic:
Confirmed
Bug description:
[impact]
pam_umask, from /etc/passwd, is not honored in systemd --user
instances
[test case]
on a desktop system, edit /etc/passwd to change the test user entry
(e.g. the 'ubuntu' user) to include 'umask=007' in the GECOS field
(5th field). For example change:
ubuntu:x:1000:1000:Ubuntu:/home/ubuntu:/bin/bash
to:
ubuntu:x:1000:1000:Ubuntu,umask=007:/home/ubuntu:/bin/bash
You may need to reboot for your X session to pick up the change.
Then, from the graphical desktop, open a terminal and run:
$ gnome-terminal -e sh
in the opened terminal, run:
$ umask
the number shown should be 0007, as set in the passwd file
[regression potential]
any regression would likely result in an incorrect umask for the user
whose passwd entry is modified.
[scope]
this is needed only for b
this is fixed in systemd upstream by commit
5e37d1930b41b24c077ce37c6db0e36c745106c7 which was first included in
v246, so this is fixed in g and later. This commit was also picked up
by Debian and included in the v245 release for focal, so this is fixed
in focal already.
[original description]
In order to set the default umask of my users to 027 or 007, I
followed the instructions provided in 'man pam_umask' :
In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
'umask=007' (for myself).
Then, MOST graphical applications systematically run with the correct
umask.
[Desktop-packages] [Bug 1855595] Re: CUPS fails to print to autodetected printers because of cups-browsed error
can confirm that am affected also with Epson Ecotank ET-4750 and Kubuntu 20.04 - error message for automatically added printer is "idle - no suitable destination host found by cups-browsed" printing was functioning on 18.04 - adding the printer manually fails to bring the printer to print - the workaround by @gerlosgm does not function here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1855595 Title: CUPS fails to print to autodetected printers because of cups-browsed error Status in cups-filters package in Ubuntu: Confirmed Bug description: When trying to autodetected IPP printers, print job stays in queue. lpstat -l: HP_LaserJet_CM1415fn_44A808_-23 erik 30720 So 08 Dez 2019 15:50:20 CET Status: No suitable destination host found by cups-browsed. Alarme: resources-are-not-ready in Warteschlange eingereiht für HP_LaserJet_CM1415fn_44A808_ Removing the print job, restarting cups-browsed with `service cups- browsed restart` followed by `service cups restart` enables printing for one print job; the next one fails again with the same issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups-browsed 1.25.13-1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: LXQt Date: Sun Dec 8 16:06:02 2019 InstallationDate: Installed on 2019-10-19 (50 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191019) Lpstat: device for HP_LaserJet_CM1415fn_44A808_: implicitclass://HP_LaserJet_CM1415fn_44A808_/ device for Samsung_C48x_Series_SEC84251900EE44_: implicitclass://Samsung_C48x_Series_SEC84251900EE44_/ MachineType: Dell Inc. Latitude E6530 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_LaserJet_CM1415fn_44A808_.ppd', '/etc/cups/ppd/Samsung_C48x_Series_SEC84251900EE44_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_LaserJet_CM1415fn_44A808_.ppd: Permission denied grep: /etc/cups/ppd/Samsung_C48x_Series_SEC84251900EE44_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_utwd0l@/vmlinuz-5.3.0-24-generic root=ZFS=rpool/ROOT/ubuntu_utwd0l ro quiet splash vt.handoff=1 SourcePackage: cups-filters UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A22 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA22:bd11/30/2018:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.sku: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1855595/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1685754] Re: 'systemd --user' unduly forces umask=0022
** Changed in: systemd (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu Bionic)
Status: Confirmed => In Progress
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Dan Streetman (ddstreet)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1685754
Title:
'systemd --user' unduly forces umask=0022
Status in gedit:
Invalid
Status in gnome-session:
Invalid
Status in GNOME Terminal:
Confirmed
Status in Nautilus:
Invalid
Status in systemd:
Unknown
Status in dbus package in Ubuntu:
Invalid
Status in gnome-terminal package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Fix Released
Status in dbus source package in Bionic:
Invalid
Status in gnome-terminal source package in Bionic:
Invalid
Status in systemd source package in Bionic:
In Progress
Bug description:
[impact]
pam_umask, from /etc/passwd, is not honored in systemd --user
instances
[test case]
on a desktop system, edit /etc/passwd to change the test user entry
(e.g. the 'ubuntu' user) to include 'umask=007' in the GECOS field
(5th field). For example change:
ubuntu:x:1000:1000:Ubuntu:/home/ubuntu:/bin/bash
to:
ubuntu:x:1000:1000:Ubuntu,umask=007:/home/ubuntu:/bin/bash
You may need to reboot for your X session to pick up the change.
Then, from the graphical desktop, open a terminal and run:
$ gnome-terminal -e sh
in the opened terminal, run:
$ umask
the number shown should be 0007, as set in the passwd file
[regression potential]
any regression would likely result in an incorrect umask for the user
whose passwd entry is modified.
[scope]
this is needed only for b
this is fixed in systemd upstream by commit
5e37d1930b41b24c077ce37c6db0e36c745106c7 which was first included in
v246, so this is fixed in g and later. This commit was also picked up
by Debian and included in the v245 release for focal, so this is fixed
in focal already.
[original description]
In order to set the default umask of my users to 027 or 007, I
followed the instructions provided in 'man pam_umask' :
In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
'umask=007' (for myself).
Then, MOST graphical applications systematically run with the correct
umask.
In particular, when I press Alt-F2, run 'xterm sh' and type 'umask',
it systematically displays 0007.
But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask',
it systematically displays 0022.
That is BAD, and is a security issue.
Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each
'~/.bashrc', add following content :
UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)"
if [ "$UMASK" ]; then
umask "${UMASK#$USER:*,umask=}"
fi
In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask
unchanged.
Thank you in advance for a quick correction.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-terminal 3.20.2-1ubuntu8
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Mon Apr 24 08:36:58 2017
InstallationDate: Installed on 2017-03-28 (26 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724098]
This bug is fixed on my Arch Linux since Gnome Shell 3.38.1. -- 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/1724098 Title: Panel menu icons are briefly way too big (when opened the first time) Status in GNOME Shell: Expired Status in gnome-shell package in Ubuntu: Triaged Bug description: On every fresh boot, the first time when you click the drop down menu for SOUND/WIRELESS/SHUT-DOWN, the sound icon jumps out very big in size...BUT ONLY THE FIRST TIME WHEN YOU RESTART the machine!! --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 GsettingsChanges: org.gnome.shell enabled-extensions ['ubuntu-appindicat...@ubuntu.com'] org.gnome.shell app-picker-view uint32 1 org.gnome.shell favorite-apps ['chromium-browser.desktop', 'firefox.desktop', 'org.gnome.Nautilus.desktop', 'rhythmbox.desktop', 'org.gnome.Software.desktop', 'yelp.desktop', 'ubuntu-amazon-default.desktop'] org.gnome.desktop.interface enable-animations false org.gnome.desktop.interface gtk-im-module 'gtk-im-context-simple' InstallationDate: Installed on 2017-08-31 (46 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) Package: gnome-shell 3.26.1-0ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1724098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724098] Re: Panel menu icons are briefly way too big (when opened the first time)
** Changed in: gnome-shell Status: Confirmed => Expired -- 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/1724098 Title: Panel menu icons are briefly way too big (when opened the first time) Status in GNOME Shell: Expired Status in gnome-shell package in Ubuntu: Triaged Bug description: On every fresh boot, the first time when you click the drop down menu for SOUND/WIRELESS/SHUT-DOWN, the sound icon jumps out very big in size...BUT ONLY THE FIRST TIME WHEN YOU RESTART the machine!! --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 GsettingsChanges: org.gnome.shell enabled-extensions ['ubuntu-appindicat...@ubuntu.com'] org.gnome.shell app-picker-view uint32 1 org.gnome.shell favorite-apps ['chromium-browser.desktop', 'firefox.desktop', 'org.gnome.Nautilus.desktop', 'rhythmbox.desktop', 'org.gnome.Software.desktop', 'yelp.desktop', 'ubuntu-amazon-default.desktop'] org.gnome.desktop.interface enable-animations false org.gnome.desktop.interface gtk-im-module 'gtk-im-context-simple' InstallationDate: Installed on 2017-08-31 (46 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) Package: gnome-shell 3.26.1-0ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1724098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916550] Re: simple-scan chooses scanned image size improperly
My apologies again. I have attached the log of four scans that show the problem. The scans themselves will follow. ** Attachment added: "Log for the four scans also attached." https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1916550/+attachment/5466791/+files/simple-scan.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1916550 Title: simple-scan chooses scanned image size improperly Status in simple-scan package in Ubuntu: Incomplete Bug description: I have an HP OfficeJet 4654 which the scanner recognized (after a while, but eventually it finds the OfficeJet). The scanner can do single pages on the platen and has a sheet feeder as well. When I scan single pages on the platen, the size is correctly set to Letter (It could do A4 but I don't use that). However, if I use the sheet feeder, the scan defaults to Legal size. If I change the Preference to Letter in the gear settings, I can get Letter sized scans with the feeder. However, with the Preference set to Letter, the single platen scanned documents come out Legal sized with the area below the Letter sized form blackened in. This is absurd. If I tell it to use Letter size, it should not override this and produce incorrect Legal sized scans, regardless of whether the source is on the platen or from the feeder. What I truly don't understand is why I get a Legal size scan on a Letter sized piece of paper in the sheet feeder at all (the default behavior). The app is clearly capable of producing letter sized scans when told to do so. I also don't understand why the scanning tool overrides my Preference setting for Letter size when I scan from the platen. The new interface also makes it more difficult to change the Preferences - there's no Save or OK button, just the upper-right- corner x which usually means don't save - very confusing and user unfriendly. Source: https://gitlab.gnome.org/GNOME/simple-scan Description: Ubuntu 20.04.2 LTS Release: 20.04 Simple-scan Version: 3.36.3 What I expected to happen: If I scan a letter sized document, I expect a letter sized scan. If I scan multiple sheets all letter sized, I expect all pages to scan at letter sized. What happens instead: If the paper size Preference is set to Automatic, the platen scans are correct but the sheet feeder scans are all legal sized. If the paper size Preference is set to Letter, the sheet feeder scans are all letter sized but the single page platen scans are all legal sized with a blackened 3" section at the bottom of the page. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Feb 22 18:04:51 2021 InstallationDate: Installed on 2020-10-01 (145 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=97168ae7-ec8a-49b7-8ef8-6b377b98a588 ro nosplash SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.20 dmi.board.name: Z97 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd05/12/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1916550/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916550] Re: simple-scan chooses scanned image size improperly
First scan - page size set to Automatic, scanned on the platen (single- sheet). ** Attachment added: "Letter-sized paper, set to Automatic, single-sheet on platen." https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1916550/+attachment/5466792/+files/scanL0224-AutoPlaten.pdf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1916550 Title: simple-scan chooses scanned image size improperly Status in simple-scan package in Ubuntu: Incomplete Bug description: I have an HP OfficeJet 4654 which the scanner recognized (after a while, but eventually it finds the OfficeJet). The scanner can do single pages on the platen and has a sheet feeder as well. When I scan single pages on the platen, the size is correctly set to Letter (It could do A4 but I don't use that). However, if I use the sheet feeder, the scan defaults to Legal size. If I change the Preference to Letter in the gear settings, I can get Letter sized scans with the feeder. However, with the Preference set to Letter, the single platen scanned documents come out Legal sized with the area below the Letter sized form blackened in. This is absurd. If I tell it to use Letter size, it should not override this and produce incorrect Legal sized scans, regardless of whether the source is on the platen or from the feeder. What I truly don't understand is why I get a Legal size scan on a Letter sized piece of paper in the sheet feeder at all (the default behavior). The app is clearly capable of producing letter sized scans when told to do so. I also don't understand why the scanning tool overrides my Preference setting for Letter size when I scan from the platen. The new interface also makes it more difficult to change the Preferences - there's no Save or OK button, just the upper-right- corner x which usually means don't save - very confusing and user unfriendly. Source: https://gitlab.gnome.org/GNOME/simple-scan Description: Ubuntu 20.04.2 LTS Release: 20.04 Simple-scan Version: 3.36.3 What I expected to happen: If I scan a letter sized document, I expect a letter sized scan. If I scan multiple sheets all letter sized, I expect all pages to scan at letter sized. What happens instead: If the paper size Preference is set to Automatic, the platen scans are correct but the sheet feeder scans are all legal sized. If the paper size Preference is set to Letter, the sheet feeder scans are all letter sized but the single page platen scans are all legal sized with a blackened 3" section at the bottom of the page. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Feb 22 18:04:51 2021 InstallationDate: Installed on 2020-10-01 (145 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=97168ae7-ec8a-49b7-8ef8-6b377b98a588 ro nosplash SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.20 dmi.board.name: Z97 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd05/12/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1916550/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916550] Re: simple-scan chooses scanned image size improperly
This is the (correct) scan o a letter-sized page done via the sheet feeder with the page Preference set to Letter. ** Attachment added: "Letter -sized paper scanned with Preference page size set to Letter, scanned from the sheet feeder." https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1916550/+attachment/5466795/+files/scanL0224-LetterSheetFeeder.pdf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1916550 Title: simple-scan chooses scanned image size improperly Status in simple-scan package in Ubuntu: Incomplete Bug description: I have an HP OfficeJet 4654 which the scanner recognized (after a while, but eventually it finds the OfficeJet). The scanner can do single pages on the platen and has a sheet feeder as well. When I scan single pages on the platen, the size is correctly set to Letter (It could do A4 but I don't use that). However, if I use the sheet feeder, the scan defaults to Legal size. If I change the Preference to Letter in the gear settings, I can get Letter sized scans with the feeder. However, with the Preference set to Letter, the single platen scanned documents come out Legal sized with the area below the Letter sized form blackened in. This is absurd. If I tell it to use Letter size, it should not override this and produce incorrect Legal sized scans, regardless of whether the source is on the platen or from the feeder. What I truly don't understand is why I get a Legal size scan on a Letter sized piece of paper in the sheet feeder at all (the default behavior). The app is clearly capable of producing letter sized scans when told to do so. I also don't understand why the scanning tool overrides my Preference setting for Letter size when I scan from the platen. The new interface also makes it more difficult to change the Preferences - there's no Save or OK button, just the upper-right- corner x which usually means don't save - very confusing and user unfriendly. Source: https://gitlab.gnome.org/GNOME/simple-scan Description: Ubuntu 20.04.2 LTS Release: 20.04 Simple-scan Version: 3.36.3 What I expected to happen: If I scan a letter sized document, I expect a letter sized scan. If I scan multiple sheets all letter sized, I expect all pages to scan at letter sized. What happens instead: If the paper size Preference is set to Automatic, the platen scans are correct but the sheet feeder scans are all legal sized. If the paper size Preference is set to Letter, the sheet feeder scans are all letter sized but the single page platen scans are all legal sized with a blackened 3" section at the bottom of the page. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Feb 22 18:04:51 2021 InstallationDate: Installed on 2020-10-01 (145 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=97168ae7-ec8a-49b7-8ef8-6b377b98a588 ro nosplash SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.20 dmi.board.name: Z97 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd05/12/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1916550/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916550] Re: simple-scan chooses scanned image size improperly
Paper size set to automatic, letter sized page scanned via the sheet feeder. Notice the scan is legal sized, not letter sized. ** Attachment added: "Scan of letter sized paper, paper size set to automatic, sheet feeder source." https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1916550/+attachment/5466793/+files/scanL0224-AutoSheetFeeder.pdf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1916550 Title: simple-scan chooses scanned image size improperly Status in simple-scan package in Ubuntu: Incomplete Bug description: I have an HP OfficeJet 4654 which the scanner recognized (after a while, but eventually it finds the OfficeJet). The scanner can do single pages on the platen and has a sheet feeder as well. When I scan single pages on the platen, the size is correctly set to Letter (It could do A4 but I don't use that). However, if I use the sheet feeder, the scan defaults to Legal size. If I change the Preference to Letter in the gear settings, I can get Letter sized scans with the feeder. However, with the Preference set to Letter, the single platen scanned documents come out Legal sized with the area below the Letter sized form blackened in. This is absurd. If I tell it to use Letter size, it should not override this and produce incorrect Legal sized scans, regardless of whether the source is on the platen or from the feeder. What I truly don't understand is why I get a Legal size scan on a Letter sized piece of paper in the sheet feeder at all (the default behavior). The app is clearly capable of producing letter sized scans when told to do so. I also don't understand why the scanning tool overrides my Preference setting for Letter size when I scan from the platen. The new interface also makes it more difficult to change the Preferences - there's no Save or OK button, just the upper-right- corner x which usually means don't save - very confusing and user unfriendly. Source: https://gitlab.gnome.org/GNOME/simple-scan Description: Ubuntu 20.04.2 LTS Release: 20.04 Simple-scan Version: 3.36.3 What I expected to happen: If I scan a letter sized document, I expect a letter sized scan. If I scan multiple sheets all letter sized, I expect all pages to scan at letter sized. What happens instead: If the paper size Preference is set to Automatic, the platen scans are correct but the sheet feeder scans are all legal sized. If the paper size Preference is set to Letter, the sheet feeder scans are all letter sized but the single page platen scans are all legal sized with a blackened 3" section at the bottom of the page. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Feb 22 18:04:51 2021 InstallationDate: Installed on 2020-10-01 (145 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=97168ae7-ec8a-49b7-8ef8-6b377b98a588 ro nosplash SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.20 dmi.board.name: Z97 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd05/12/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1916550/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916550] Re: simple-scan chooses scanned image size improperly
This is when the Preference page size is set to letter, a scan of a letter sized page done on the platen (single sheet). ** Attachment added: "Letter page scanned with paper size set to Letter, scanned from the platen." https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1916550/+attachment/5466794/+files/scanL0224-LetterPlaten.pdf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1916550 Title: simple-scan chooses scanned image size improperly Status in simple-scan package in Ubuntu: Incomplete Bug description: I have an HP OfficeJet 4654 which the scanner recognized (after a while, but eventually it finds the OfficeJet). The scanner can do single pages on the platen and has a sheet feeder as well. When I scan single pages on the platen, the size is correctly set to Letter (It could do A4 but I don't use that). However, if I use the sheet feeder, the scan defaults to Legal size. If I change the Preference to Letter in the gear settings, I can get Letter sized scans with the feeder. However, with the Preference set to Letter, the single platen scanned documents come out Legal sized with the area below the Letter sized form blackened in. This is absurd. If I tell it to use Letter size, it should not override this and produce incorrect Legal sized scans, regardless of whether the source is on the platen or from the feeder. What I truly don't understand is why I get a Legal size scan on a Letter sized piece of paper in the sheet feeder at all (the default behavior). The app is clearly capable of producing letter sized scans when told to do so. I also don't understand why the scanning tool overrides my Preference setting for Letter size when I scan from the platen. The new interface also makes it more difficult to change the Preferences - there's no Save or OK button, just the upper-right- corner x which usually means don't save - very confusing and user unfriendly. Source: https://gitlab.gnome.org/GNOME/simple-scan Description: Ubuntu 20.04.2 LTS Release: 20.04 Simple-scan Version: 3.36.3 What I expected to happen: If I scan a letter sized document, I expect a letter sized scan. If I scan multiple sheets all letter sized, I expect all pages to scan at letter sized. What happens instead: If the paper size Preference is set to Automatic, the platen scans are correct but the sheet feeder scans are all legal sized. If the paper size Preference is set to Letter, the sheet feeder scans are all letter sized but the single page platen scans are all legal sized with a blackened 3" section at the bottom of the page. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Feb 22 18:04:51 2021 InstallationDate: Installed on 2020-10-01 (145 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=97168ae7-ec8a-49b7-8ef8-6b377b98a588 ro nosplash SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.20 dmi.board.name: Z97 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd05/12/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1916550/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892377] Re: Please add LDAC support in pulseaudio-module-bluetooth
** Changed in: pulseaudio (Ubuntu) Status: Triaged => Fix Committed ** Tags added: fixed-in-15 fixed-upstream -- 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/1892377 Title: Please add LDAC support in pulseaudio-module-bluetooth Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Fix Committed Bug description: There is a project which enables these codecs in pulseaudio (by adding profiles for these): https://github.com/EHfive/pulseaudio-modules-bt For LDAC (codec) it uses libldac from the AOSP project: https://android.googlesource.com/platform/external/libldac There is a libldac dispatcher by the same author: https://github.com/EHfive/ldacBT It would be nice to have this functionality out-of-the-box in Ubuntu. This cannot be merged to PulseAudio upstream because the Android libldac library is under Apache License 2.0 which is incompatible with pulseaudio license LGPL 2.1: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/36#note_160736 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1892377/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870829] Re: AptX and AptX HD unavailable as Bluetooth audio quality options
** No longer affects: gnome-control-center (Ubuntu) ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Fix Committed ** Tags added: fixed-in-15 fixed-upstream -- 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/1870829 Title: AptX and AptX HD unavailable as Bluetooth audio quality options Status in pulseaudio package in Ubuntu: Fix Committed Bug description: Current situation: When one connects a Bluetooth audio device, at best one can choose between "Headset Head Unit (HSP/HFP)" and "High Fidelity Playback (A2DP Sink)". That is sad when the audio device supports AptX or AptX HD. Expected situation: One can select AptX or AptX HD as the Bluetooth audio output profile. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870829/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
** Tags added: fixed-in-15 fixed-upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Committed Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916760] Re: dock badge icon doesn't show
** Tags added: groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1916760 Title: dock badge icon doesn't show Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Hello when i use discord canary on ubuntu 20.10 the badge of unread message doesn't show but if i use discord stable release in the same time unread message of canary go on the icon of discord. Of course if i uninstall stable discord, canary doesn't show the badge. I have joined to image to show you. Thanks in advance for our reply and for considering my problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1916760/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913453] Re: gnome-shell freeze
More ideas: 1. Please check ~/.local/share/gnome-shell/ and ensure there is no subdirectory named 'extensions'. If there is one then remove it. 2. Your system logs seem to show you're using sleeping to work around the original problem, as mentioned in the bug description at the top of the page. Please reboot and then reproduce the bug without ever sleeping the system. Then once the lag and freezing starts happening, reboot again and run: journalctl -b-1 > cleanprevboot.txt and attach the resulting text file here. 3. If you can then please also answer the question from comment #2 - While the problem is happening, does 'top' show any process using high CPU? -- 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/1913453 Title: gnome-shell freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: System Description: Ubuntu 20.04.1 LTS Release: 20.04 Description: Plugging in USB hub with peripherals while system is running causes gradual lag of a visual response, until freezing. usually takes < 1 min. Only work around is to sleep system between plugging in hub. I thought I fixed it by change DM but the issue has persisted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 27 14:27:12 2021 DistUpgraded: 2020-04-28 14:42:33,856 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-62-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-64-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-65-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] InstallationDate: Installed on 2018-12-25 (763 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 2324AS7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=957184f1-8feb-4ca9-ac97-3fb70937b4ac ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-04-28 (274 days ago) dmi.bios.date: 04/11/2018 dmi.bios.vendor: LENOVO dmi.bios.version: G2ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324AS7 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: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ETB2WW(2.72):bd04/11/2018:svnLENOVO:pn2324AS7:pvrThinkPadX230:rvnLENOVO:rn2324AS7:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2324AS7 dmi.product.sku: LENOVO_MT_2324 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~ppa1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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 xserver.bootTime: Tue Nov 24 16:32:27 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2.4 xserver.video_driver: modeset --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-12-25 (792 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 Tags: third-party-
[Desktop-packages] [Bug 1916765] Re: Xorg memory leak
Thanks for the bug report. Since app windows' resources are all stored in the Xorg process I think this is most likely the result of an X11 resource leak in some application. To find out which one please test with no apps, and then with a smaller set of apps. You should be able to identify which application is triggering the leak. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1916765 Title: Xorg memory leak Status in xorg-server package in Ubuntu: Incomplete Bug description: Ubuntu Version: 20.10 groovy Xorg Version: ii xorg 1:7.7+19ubuntu15 amd64X.Org X Window System xorg seems to have a memory leak - usage grows from 200mb of memory to fill all available memory (several GBs) ps -o pid,user,%mem,command ax | grep Xorg 1071 root 5.6 /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch 1071: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch 55bd3ad76000244K r Xorg 55bd3adb3000 1632K r-x-- Xorg 55bd3af4b000480K r Xorg 55bd3afc4000 16K r Xorg 55bd3afc8000 44K rw--- Xorg 55bd3afd3000128K rw--- [ anon ] 55bd3ba2b000 611340K rw--- [ anon ] 7f572dd68000 12288K rw-s- [ anon ] 7f572e968000 10240K rw-s- [ anon ] 7f5731468000 131072K rw-s- [ shmid=0x2c8018 ] 7f5739468000 24576K rw-s- [ anon ] 7f573ac68000 14336K rw-s- [ anon ] 7f573ba68000 14336K rw-s- [ anon ] 7f573c868000 24576K rw-s- [ anon ] 7f573e068000 24576K rw-s- [ anon ] 7f573f868000 24576K rw-s- [ anon ] 7f5742a68000 24576K rw-s- [ anon ] 7f5744368000 5120K rw-s- [ anon ] 7f5745af8000 24000K rw-s- memfd:xorg (deleted) 7f5747268000 131072K rw-s- [ shmid=0x1a8017 ] 7f574f268000 24576K rw-s- [ anon ] 7f5750a68000 24576K rw-s- [ anon ] 7f5752268000 262144K rw-s- [ shmid=0x28022 ] 7f5762e1e000 12020K rw-s- [ shmid=0xe000a ] 7f57639db000 12020K rw-s- [ shmid=0xe0009 ] 7f5765198000 11072K rw-s- [ shmid=0x9001e ] 7f5765d3 12288K rw-s- [ anon ] 7f576693 10240K rw-s- [ anon ] 7f576733 11072K rw-s- [ shmid=0x9001d ] 7f5767e0 10240K rw-s- [ anon ] 7f576900 8192K rw-s- [ anon ] 7f576980 4096K rw-s- [ shmid=0x90004 ] 7f5769d66000 6760K rw--- [ anon ] 7f576a40 12288K rw-s- [ anon ] 7f576b4d8000 5120K rw-s- [ anon ] 7f576c0d8000 12288K rw-s- [ anon ] 7f576cdd8000 12288K rw-s- [ anon ] 7f576e2d8000 8192K rw-s- [ anon ] 7f576ead8000800K rw-s- [ shmid=0x20032 ] 7f576ed8f000 2628K rw-s- [ shmid=0x130029 ] 7f576f80 262144K rw-s- [ shmid=0x2e ] 7f577f848000784K rw-s- [ shmid=0x2002f ] 7f577fa0 2560K rw-s- [ anon ] 7f578018 7168K rw-s- [ anon ] 7f578088 2560K rw-s- [ anon ] 7f5780b0 4096K rw-s- [ shmid=0x5003e ] 7f578100 24576K rw-s- [ anon ] 7f57828ef000 2628K rw-s- [ shmid=0x130027 ] 7f5782cd6000 1280K rw-s- [ anon ] 7f5782e16000 1280K rw-s- [ anon ] 7f57831b6000896K rw-s- [ anon ] 7f5783296000 6568K rw-s- memfd:xorg (deleted) 7f578390 7168K rw-s- [ anon ] 7f578400132K rw--- [ anon ] 7f5784021000 65404K - [ anon ] 7f578800132K rw--- [ anon ] 7f5788021000 65404K - [ anon ] 7f578c00132K rw--- [ anon ] 7f578c021000 65404K - [ anon ] 7f57900be000896K rw-s- [ anon ] 7f57901a8000 1280K rw-s- [ anon ] 7f57902e8000512K rw-s- [ shmid=0x9801a ] 7f57903e8000196K rw-s- [ shmid=0x98001 ] 7f5790469000212K rw-s- [ shmid=0x68036 ] 7f57905ca000196K rw-s- [ shmid=0x98002 ] 7f57905fb000220K rw-s- [ shmid=0x88016 ] 7f579066a000256K rw-s- [ anon ] 7f57906aa000784K rw-s- [ shmid=0x20030 ] 7f579077e000512K rw-s- [ shmid=0x58039 ] 7f57907fe000 4096K rw-s- [ shmid=0x15 ] 7f5790dae000512K rw-s- [ shmid=0x320006 ] 7f5790e6e000 2048K rw-s- [ shmid=0x23000e ] 7f579110e000800K rw-s- [ shmid=0x20031 ] 7f579126e000320K rw-s- [ anon ] 7f57913fe000 4096K rw-s- [ shmid=0x2d ] 7f579199d000 3584K rw-s- [ anon ] 7f5791d1d000640K rw-s- [ anon ] 7f5791e1d000 1024K rw-s- [ anon ] 7f5791f9d000512K rw-s- [ shmid=0x31001f ] 7f579201d000768K rw-s-
[Desktop-packages] [Bug 1916765] Re: Xorg memory leak
This should also help identify the cause: sudo apt install xrestop xrestop -- 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/1916765 Title: Xorg memory leak Status in xorg-server package in Ubuntu: Incomplete Bug description: Ubuntu Version: 20.10 groovy Xorg Version: ii xorg 1:7.7+19ubuntu15 amd64X.Org X Window System xorg seems to have a memory leak - usage grows from 200mb of memory to fill all available memory (several GBs) ps -o pid,user,%mem,command ax | grep Xorg 1071 root 5.6 /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch 1071: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch 55bd3ad76000244K r Xorg 55bd3adb3000 1632K r-x-- Xorg 55bd3af4b000480K r Xorg 55bd3afc4000 16K r Xorg 55bd3afc8000 44K rw--- Xorg 55bd3afd3000128K rw--- [ anon ] 55bd3ba2b000 611340K rw--- [ anon ] 7f572dd68000 12288K rw-s- [ anon ] 7f572e968000 10240K rw-s- [ anon ] 7f5731468000 131072K rw-s- [ shmid=0x2c8018 ] 7f5739468000 24576K rw-s- [ anon ] 7f573ac68000 14336K rw-s- [ anon ] 7f573ba68000 14336K rw-s- [ anon ] 7f573c868000 24576K rw-s- [ anon ] 7f573e068000 24576K rw-s- [ anon ] 7f573f868000 24576K rw-s- [ anon ] 7f5742a68000 24576K rw-s- [ anon ] 7f5744368000 5120K rw-s- [ anon ] 7f5745af8000 24000K rw-s- memfd:xorg (deleted) 7f5747268000 131072K rw-s- [ shmid=0x1a8017 ] 7f574f268000 24576K rw-s- [ anon ] 7f5750a68000 24576K rw-s- [ anon ] 7f5752268000 262144K rw-s- [ shmid=0x28022 ] 7f5762e1e000 12020K rw-s- [ shmid=0xe000a ] 7f57639db000 12020K rw-s- [ shmid=0xe0009 ] 7f5765198000 11072K rw-s- [ shmid=0x9001e ] 7f5765d3 12288K rw-s- [ anon ] 7f576693 10240K rw-s- [ anon ] 7f576733 11072K rw-s- [ shmid=0x9001d ] 7f5767e0 10240K rw-s- [ anon ] 7f576900 8192K rw-s- [ anon ] 7f576980 4096K rw-s- [ shmid=0x90004 ] 7f5769d66000 6760K rw--- [ anon ] 7f576a40 12288K rw-s- [ anon ] 7f576b4d8000 5120K rw-s- [ anon ] 7f576c0d8000 12288K rw-s- [ anon ] 7f576cdd8000 12288K rw-s- [ anon ] 7f576e2d8000 8192K rw-s- [ anon ] 7f576ead8000800K rw-s- [ shmid=0x20032 ] 7f576ed8f000 2628K rw-s- [ shmid=0x130029 ] 7f576f80 262144K rw-s- [ shmid=0x2e ] 7f577f848000784K rw-s- [ shmid=0x2002f ] 7f577fa0 2560K rw-s- [ anon ] 7f578018 7168K rw-s- [ anon ] 7f578088 2560K rw-s- [ anon ] 7f5780b0 4096K rw-s- [ shmid=0x5003e ] 7f578100 24576K rw-s- [ anon ] 7f57828ef000 2628K rw-s- [ shmid=0x130027 ] 7f5782cd6000 1280K rw-s- [ anon ] 7f5782e16000 1280K rw-s- [ anon ] 7f57831b6000896K rw-s- [ anon ] 7f5783296000 6568K rw-s- memfd:xorg (deleted) 7f578390 7168K rw-s- [ anon ] 7f578400132K rw--- [ anon ] 7f5784021000 65404K - [ anon ] 7f578800132K rw--- [ anon ] 7f5788021000 65404K - [ anon ] 7f578c00132K rw--- [ anon ] 7f578c021000 65404K - [ anon ] 7f57900be000896K rw-s- [ anon ] 7f57901a8000 1280K rw-s- [ anon ] 7f57902e8000512K rw-s- [ shmid=0x9801a ] 7f57903e8000196K rw-s- [ shmid=0x98001 ] 7f5790469000212K rw-s- [ shmid=0x68036 ] 7f57905ca000196K rw-s- [ shmid=0x98002 ] 7f57905fb000220K rw-s- [ shmid=0x88016 ] 7f579066a000256K rw-s- [ anon ] 7f57906aa000784K rw-s- [ shmid=0x20030 ] 7f579077e000512K rw-s- [ shmid=0x58039 ] 7f57907fe000 4096K rw-s- [ shmid=0x15 ] 7f5790dae000512K rw-s- [ shmid=0x320006 ] 7f5790e6e000 2048K rw-s- [ shmid=0x23000e ] 7f579110e000800K rw-s- [ shmid=0x20031 ] 7f579126e000320K rw-s- [ anon ] 7f57913fe000 4096K rw-s- [ shmid=0x2d ] 7f579199d000 3584K rw-s- [ anon ] 7f5791d1d000640K rw-s- [ anon ] 7f5791e1d000 1024K rw-s- [ anon ] 7f5791f9d000512K rw-s- [ shmid=0x31001f ] 7f579201d000768K rw-s- [ anon ] 7f5792147000320K rw-s- [ anon ] 7f5792217000512K rw-s- [ anon ] 7f5792297000 8K rw-s- [ anon ] 7f579229d000512K rw-s- [ shmid=0x2c8011 ] 7f579232d000 64K rw-s- [ anon ] 7f579236d000896K rw-s- [ anon ] 7f579244e000732K rw-s- [ shmid=0x2f8010 ] 7f579252f000320K rw-s- [ anon ]
[Desktop-packages] [Bug 1916814] [NEW] gnome-shell crashed with SIGSEGV in meta_workspace_index() from meta_workspace_activate_with_focus() from ffi_call_unix64() from ffi_call_int() from gjs_invoke_c
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.2-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/28cc92eb593f6277a02bec4fba68d499e8a79f53 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: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: groovy hirsute -- 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/1916814 Title: gnome-shell crashed with SIGSEGV in meta_workspace_index() from meta_workspace_activate_with_focus() from ffi_call_unix64() from ffi_call_int() from gjs_invoke_c_function() Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.2-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/28cc92eb593f6277a02bec4fba68d499e8a79f53 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/gnome-shell/+bug/1916814/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916814] Re: gnome-shell crashed with SIGSEGV in meta_workspace_index() from meta_workspace_activate_with_focus() from ffi_call_unix64() from ffi_call_int() from gjs_invoke_c_f
Possibly related to https://gitlab.gnome.org/GNOME/mutter/-/issues/1661 ** Summary changed: - /usr/bin/gnome-shell:11:meta_workspace_index:meta_workspace_activate_with_focus:ffi_call_unix64:ffi_call_int:gjs_invoke_c_function + gnome-shell crashed with SIGSEGV in meta_workspace_index() from meta_workspace_activate_with_focus() from ffi_call_unix64() from ffi_call_int() from gjs_invoke_c_function() ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1661 https://gitlab.gnome.org/GNOME/mutter/-/issues/1661 -- 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/1916814 Title: gnome-shell crashed with SIGSEGV in meta_workspace_index() from meta_workspace_activate_with_focus() from ffi_call_unix64() from ffi_call_int() from gjs_invoke_c_function() Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.2-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/28cc92eb593f6277a02bec4fba68d499e8a79f53 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/gnome-shell/+bug/1916814/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906671] Re: [MIR] usrmerge
This bug was fixed in the package debootstrap - 1.0.123ubuntu4 --- debootstrap (1.0.123ubuntu4) hirsute; urgency=medium * No-change rebuild to drop the udeb package. -- Matthias Klose Mon, 22 Feb 2021 10:30:44 +0100 ** Changed in: debootstrap (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1906671 Title: [MIR] usrmerge Status in debootstrap package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in usrmerge package in Ubuntu: Fix Released Bug description: [Availability] In universe. [Rationale] Since Disco, Ubuntu has defaulted to merged usr systems, specifically that /lib is a symlink to /usr/lib. However, we have not yet completed this transition for systems that were installed pre-disco. This package performs such transition using maintainer scripts. It has been tested and improved thoroughly and has managed to work with all sorts of packages that happened to be installed on the system. For systems that were installed post disco, this package is effectively a no-op. Systems that use nfs mounting with split /usr care must be taken to ensure that initrd mounts nfs-backed /usr. The package aborts configuration if such rare configuration is detected to avoid potentially bracking reboot. For all other systems, we always provide a fallback initrd which has been mounting both / and /usr whenever possible. [Security] The package ships two perl scripts, which are executed by root from maintainer scripts. [Quality assurance] There is debconf question one can preseed to prevent the migration, there is README.Debian explaining what it does and how. It is a one- way / one-time migration, removing the package will not undo the migration. [Dependencies] Perl, and many documented conflicts to ensure that usrmerge compatible packages are on disk prior to migration. [Standards compliance] Adheres to Debian Policy. [Maintenance] Maintained in Debian, merged and supported by Foundations, foundations-bugs is subscribed. [Background information] This will complete usrmerge migration, and will allow to switch buildds to build packages with merged-usr by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1906671/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1898442] Re: Center new windows
The option is also configurable in: Gnome Tweaks > Windows > Center New windows ** Summary changed: - Center new windows + Center new windows by default ** Changed in: mutter (Ubuntu) Importance: Low => Wishlist ** Changed in: mutter (Ubuntu) Status: Opinion => Triaged ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1662 https://gitlab.gnome.org/GNOME/mutter/-/issues/1662 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/1662 Importance: Unknown Status: Unknown -- 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/1898442 Title: Center new windows by default Status in Mutter: Unknown Status in mutter package in Ubuntu: Triaged Bug description: Place new windows in the center, not in the top left corner. Can you imagine if this was happening on other operating systems? There was a bug report that there was no option to start windows centered - https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1298263 Yet this is not the end of the problem - the windows should open in the center *by default*, not as a hidden option in dconf -> org/gnome/mutter/center-new-windows. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1898442/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1734541] Re: encrypted home-directory is not unmounted on logout
** Changed in: ecryptfs-utils (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1734541 Title: encrypted home-directory is not unmounted on logout Status in gnome-session: New Status in ecryptfs-utils package in Ubuntu: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in ecryptfs-utils package in Debian: Fix Released Bug description: Current Situation: If you log out from an user account with an encrypted home directory, it is not automatically unmounted and encrypted again. Expected behaviour: If I log out from an user account with an encrypted home directory, Id expect the homedir to be unmounted and encrypted again. Stepts to reproduce: log into an account with encrypted home directory. (lets call it: user) Log out again log into another account (which has sudo rights, lets call it: user2) and now enter the following into a terminal: user2@ubuntu: sudo su user2@ubuntu: ls -la /home/user you can see the files of the user Reasons: This is a security issue, because as a user you can reasonable expect your data to be safe, if you log out. if you would simply log in as another user but keep your data accessable you would simply switch user, instead of loggin out. Many users only suspend their laptop while carrying it with them. Logging out and suspending the user expects to have at least the home directory encrypted. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.26.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 26 16:18:39 2017 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1734541/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874578] Re: [wayland] dock has very long load time when show-mounts is enabled
I confirm this issue, too. I have a disk mounted automatically via /etc/fstab when booting, and the disk icon shows up on dock by default. After this, the dock loads very slowly. After I remove the entry from /etc/fstab, the issue is gone. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1874578 Title: [wayland] dock has very long load time when show-mounts is enabled Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I just upgraded from Ubuntu 18.04 to 20.04. When I boot my system I have to wait at least 10 to 15 seconds for the application icons to load on dock. Meanwhile everything else seems to be working properly. I didn't experience this behavior in Ubuntu 18.04. Also the dock doesn't trigger when I move my cursor to the left of the screen. (I have set the docker to Auto-Hide mode and it's position is on the left of my screen). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2016-08-03 (1359 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Tags: focal third-party-packages wayland-session Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-23 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1874578/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874578] Re: [wayland] dock has very long load time when show-mounts is enabled
** Bug watch added: github.com/micheleg/dash-to-dock/issues #1217 https://github.com/micheleg/dash-to-dock/issues/1217 ** Also affects: dash-to-dock via https://github.com/micheleg/dash-to-dock/issues/1217 Importance: Unknown Status: Unknown ** Bug watch added: github.com/micheleg/dash-to-dock/issues #1239 https://github.com/micheleg/dash-to-dock/issues/1239 ** Changed in: dash-to-dock Remote watch: github.com/micheleg/dash-to-dock/issues #1217 => github.com/micheleg/dash-to-dock/issues #1239 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1874578 Title: [wayland] dock has very long load time when show-mounts is enabled Status in Dash to dock: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I just upgraded from Ubuntu 18.04 to 20.04. When I boot my system I have to wait at least 10 to 15 seconds for the application icons to load on dock. Meanwhile everything else seems to be working properly. I didn't experience this behavior in Ubuntu 18.04. Also the dock doesn't trigger when I move my cursor to the left of the screen. (I have set the docker to Auto-Hide mode and it's position is on the left of my screen). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2016-08-03 (1359 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Tags: focal third-party-packages wayland-session Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-23 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1874578/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Tried - 5.4.0-66.74, 5.8.0.44 and 5.11 kernels, nothing worked for me,
but i2c-hid and another one patches fixes problem. What can i do?
--
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:
Fix Released
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:
Update (based on #296)
=
The latest kernel tree
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
has the complete solution to fix this bug. So we can expect kernel
v5.11 to fix this issue without any additional work.
Before the release of v5.11, you are suggested to use #189 to save your
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd
driver is built into the initramfs. So you have to rebuild the initramfs after
replacing the old module with new one.
On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs
-u`.
The complete solution is three patches,
- 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce
filter setting in IRQ type setting")
- 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way
to disable debounce filter")
- 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into
account debounce settings")
The first two patches has reached the stable tree. If the last one is
also backported to LTS kernel, you won't need to install kernel 5.11.
But I don't know when this will happen.
Original bug report
===
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)
Machine
[Desktop-packages] [Bug 1874578] Re: [wayland] dock has very long load time when show-mounts is enabled
** Changed in: dash-to-dock Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1874578 Title: [wayland] dock has very long load time when show-mounts is enabled Status in Dash to dock: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I just upgraded from Ubuntu 18.04 to 20.04. When I boot my system I have to wait at least 10 to 15 seconds for the application icons to load on dock. Meanwhile everything else seems to be working properly. I didn't experience this behavior in Ubuntu 18.04. Also the dock doesn't trigger when I move my cursor to the left of the screen. (I have set the docker to Auto-Hide mode and it's position is on the left of my screen). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2016-08-03 (1359 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Tags: focal third-party-packages wayland-session Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-23 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1874578/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1034928] Re: Fontconfig warning: Having multiple values in isn't supported and may not works as expected
** Changed in: ttf-wqy-zenhei (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1034928 Title: Fontconfig warning: Having multiple values in isn't supported and may not works as expected Status in culmus package in Ubuntu: Fix Released Status in fonts-arphic-ukai package in Ubuntu: Fix Released Status in fonts-arphic-uming package in Ubuntu: Fix Released Status in fonts-baekmuk package in Ubuntu: Fix Released Status in fonts-droid package in Ubuntu: Fix Released Status in fonts-nanum package in Ubuntu: Fix Released Status in fonts-nanum-coding package in Ubuntu: Fix Released Status in fonts-sil-andika package in Ubuntu: Fix Released Status in fonts-tlwg package in Ubuntu: Fix Released Status in fonts-unfonts-core package in Ubuntu: Fix Released Status in fonts-unfonts-extra package in Ubuntu: Fix Released Status in language-selector package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in ttf-wqy-zenhei package in Ubuntu: Fix Released Status in culmus source package in Quantal: Fix Released Status in fonts-arphic-ukai source package in Quantal: Fix Released Status in fonts-arphic-uming source package in Quantal: Fix Released Status in fonts-baekmuk source package in Quantal: Fix Released Status in fonts-droid source package in Quantal: Fix Released Status in fonts-nanum source package in Quantal: Fix Released Status in fonts-nanum-coding source package in Quantal: Fix Released Status in fonts-sil-andika source package in Quantal: Fix Released Status in fonts-tlwg source package in Quantal: Fix Released Status in fonts-unfonts-core source package in Quantal: Fix Released Status in fonts-unfonts-extra source package in Quantal: Fix Released Status in language-selector source package in Quantal: Fix Released Status in ttf-wqy-zenhei source package in Quantal: Fix Released Status in fonts-arphic-ukai package in Debian: Fix Released Status in fonts-arphic-uming package in Debian: Fix Released Status in fonts-baekmuk package in Debian: Fix Released Status in fonts-droid package in Debian: Fix Released Status in fonts-nanum package in Debian: Fix Released Status in fonts-sil-andika package in Debian: Fix Released Status in fonts-unfonts-core package in Debian: Fix Released Status in fonts-unfonts-extra package in Debian: Fix Released Status in ttf-wqy-zenhei package in Debian: Fix Released Status in Fedora: Fix Released Bug description: In 12.10, fontconfig prints warnings similar to the following whenever fontconfig is invoked: Fontconfig warning: "/etc/fonts/conf.d/90-fonts-unfonts-core.conf", line 11: Having multiple values in isn't supported and may not works as expected This affects fonts from a number of packages: fonts-arphic-ukai: /etc/fonts/conf.d/41-arphic-ukai.conf fonts-arphic-uming: /etc/fonts/conf.d/41-arphic-uming.conf fonts-droid: /etc/fonts/conf.d/65-droid-sans-fonts.conf fonts-tlwg-garuda: /etc/fonts/conf.d/89-tlwg-garuda-synthetic.conf fonts-tlwg-kinnari: /etc/fonts/conf.d/89-tlwg-kinnari-synthetic.conf fonts-tlwg-loma: /etc/fonts/conf.d/89-tlwg-loma-synthetic.conf fonts-tlwg-umpush: /etc/fonts/conf.d/89-tlwg-umpush-synthetic.conf fonts-nanum: /etc/fonts/conf.d/90-fonts-nanum.conf fonts-unfonts-core: /etc/fonts/conf.d/90-fonts-unfonts-core.conf [Test Case] 1) Install the fonts in question 2) Open a terminal 3) Launch 'gedit' from the terminal Expected results: gedit launches, no fontconfig warnings in the terminal Actual results: gedit launches, fontconfig warnings are displayed in the terminal [Regression Potential] In case of a regression, the font in question can be affected. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: fonts-unfonts-core 1.0.3.is.1.0.2-080608-5ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0 Uname: Linux 3.5.0-8-generic x86_64 ApportVersion: 2.4-0ubuntu6 Architecture: amd64 Date: Thu Aug 9 10:02:59 2012 Dependencies: InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fonts-unfonts-core UpgradeStatus: Upgraded to quantal on 2012-08-07 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/culmus/+bug/1034928/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916827] [NEW] Update libgweather to v40
Public bug reported: Without the latest gweather v40, gnome-shell 40 fails to start: (gnome-shell:14525): Gjs-CRITICAL **: 14:24:49.987: JS ERROR: Error: No property application_id on GWeatherInfo WeatherClient@resource:///org/gnome/shell/misc/weather.js:75:29 _init@resource:///org/gnome/shell/ui/dateMenu.js:478:31 _init@resource:///org/gnome/shell/ui/dateMenu.js:872:29 _ensureIndicator@resource:///org/gnome/shell/ui/panel.js:1012:25 _updateBox@resource:///org/gnome/shell/ui/panel.js:1023:34 _updatePanel@resource:///org/gnome/shell/ui/panel.js:968:14 _init@resource:///org/gnome/shell/ui/panel.js:778:14 _initializeUI@resource:///org/gnome/shell/ui/main.js:228:13 start@resource:///org/gnome/shell/ui/main.js:169:5 @:1:47 ** Affects: libgweather (Ubuntu) Importance: Undecided Status: New ** Tags: upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1916827 Title: Update libgweather to v40 Status in libgweather package in Ubuntu: New Bug description: Without the latest gweather v40, gnome-shell 40 fails to start: (gnome-shell:14525): Gjs-CRITICAL **: 14:24:49.987: JS ERROR: Error: No property application_id on GWeatherInfo WeatherClient@resource:///org/gnome/shell/misc/weather.js:75:29 _init@resource:///org/gnome/shell/ui/dateMenu.js:478:31 _init@resource:///org/gnome/shell/ui/dateMenu.js:872:29 _ensureIndicator@resource:///org/gnome/shell/ui/panel.js:1012:25 _updateBox@resource:///org/gnome/shell/ui/panel.js:1023:34 _updatePanel@resource:///org/gnome/shell/ui/panel.js:968:14 _init@resource:///org/gnome/shell/ui/panel.js:778:14 _initializeUI@resource:///org/gnome/shell/ui/main.js:228:13 start@resource:///org/gnome/shell/ui/main.js:169:5 @:1:47 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/1916827/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916838] [NEW] /usr/bin/pipewire-media-session:11:refresh_auto_default_nodes:core_done:core_event_demarshal_done:process_remote:on_remote_data
*** This bug is a duplicate of bug 1916716 *** https://bugs.launchpad.net/bugs/1916716 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding pipewire. This problem was most recently seen with package version 0.3.22-1, the problem page at https://errors.ubuntu.com/problem/e118c16c7af628a69e39bc59672e7a25ecdc8e6e 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: pipewire (Ubuntu) Importance: Undecided Status: New ** Tags: hirsute kylin-21.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1916838 Title: /usr/bin/pipewire-media- session:11:refresh_auto_default_nodes:core_done:core_event_demarshal_done:process_remote:on_remote_data Status in pipewire package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pipewire. This problem was most recently seen with package version 0.3.22-1, the problem page at https://errors.ubuntu.com/problem/e118c16c7af628a69e39bc59672e7a25ecdc8e6e 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/pipewire/+bug/1916838/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
** Changed in: gdm3 (Ubuntu Groovy) Status: Confirmed => In Progress ** No longer affects: gdm3 (Ubuntu Groovy) ** No longer affects: gnome-settings-daemon (Ubuntu Groovy) ** Changed in: gdm3 (Ubuntu) Status: Confirmed => In Progress ** Changed in: gnome-settings-daemon (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1865226 Title: gdm-smartcard pam config needs to be updated for Ubuntu and installed Status in GNOME Settings Daemon: Unknown Status in gdm3 package in Ubuntu: In Progress Status in gnome-settings-daemon package in Ubuntu: Fix Committed Status in gdm3 source package in Bionic: Won't Fix Status in gdm3 source package in Focal: Confirmed Status in gnome-settings-daemon source package in Focal: New Status in gdm3 package in Debian: New Bug description: the pam profile for gdm-smartcard is missing. gdm refuses to login with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are pregenerated into debian/ and installed from there; gdm-smartcard is left out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 14:30:30 2020 InstallationDate: Installed on 2016-05-23 (1376 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.Xsession: 2018-04-27T11:41:04.766901 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1865226/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916716] Re: pipewire-media-session crashed with SIGSEGV in refresh_auto_default_nodes()
** Bug watch added: gitlab.freedesktop.org/pipewire/pipewire/-/issues #809 https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/809 ** Also affects: pipewire via https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/809 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1916716 Title: pipewire-media-session crashed with SIGSEGV in refresh_auto_default_nodes() Status in PipeWire: Unknown Status in pipewire package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/e118c16c7af628a69e39bc59672e7a25ecdc8e6e --- ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: pipewire-bin 0.3.22-1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Feb 24 13:34:26 2021 ExecutablePath: /usr/bin/pipewire-media-session InstallationDate: Installed on 2018-03-12 (1079 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310) ProcCmdline: /usr/bin/pipewire-media-session ProcEnviron: LANG=ru_RU.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x563fdf54ea83:mov0x10(%rdx),%rax PC (0x563fdf54ea83) ok source "0x10(%rdx)" (0x0010) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: pipewire StacktraceTop: ?? () ?? () ?? () from /usr/lib/x86_64-linux-gnu/pipewire-0.3/libpipewire-module-protocol-native.so ?? () from /usr/lib/x86_64-linux-gnu/pipewire-0.3/libpipewire-module-protocol-native.so ?? () from /usr/lib/x86_64-linux-gnu/pipewire-0.3/libpipewire-module-protocol-native.so Title: pipewire-media-session crashed with SIGSEGV UpgradeStatus: Upgraded to hirsute on 2020-11-22 (94 days ago) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/1916716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
