[Desktop-packages] [Bug 2055418] Re: autoinstall crashing on 24.04 desktop daily build
contents of /var/crash attached ** Attachment added: "crash.tgz" https://bugs.launchpad.net/subiquity/+bug/2055418/+attachment/5752934/+files/crash.tgz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/2055418 Title: autoinstall crashing on 24.04 desktop daily build Status in subiquity: New Status in tracker package in Ubuntu: New Bug description: Classis 24.04 Daily build 02-28-2024 AMD64 Using the following autoinstall user-data file, the installer crashes as soon as it loads in the GUI. ``` #cloud-config autoinstall: version: 1 apt: geoip: true preserve_sources_list: false primary: - arches: [amd64, i386] uri: http://archive.ubuntu.com/ubuntu - arches: [default] uri: http://ports.ubuntu.com/ubuntu-ports kernel: package: linux-generic-hwe-22.04 codecs: install: false drivers: install: false oem: install: auto source: id: ubuntu-desktop-minimal search_drivers: false timezone: America/Chicago updates: security identity: hostname: tiny password: $6$NtXwPsM/enBpRMOS$lxsTsJPuSzovFVWJdN3TF89yaqVzLTeqthUD8feRljnTs6EENgkOqttrkd3fiNWJFqRqi.5/m7RUi6.IgKkwb0 username: ubuntu keyboard: layout: us toggle: null variant: '' locale: en_US #refresh-installer: # update: yes storage: layout: name: hybrid encrypted: yes ssh: allow-pw: true install-server: true authorized-keys: - [key-1] - [key-2] ``` An ubuntu GUI crash report window appears, saying that the process /usr/libexec/tracker-extract-3 is what crashed. Attached is the entirety of the /var/log/installer directory. This same autoinstall file used in conjunction with a 23.10.1 ISO works perfectly fine. TPM+FDE and all. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2055418/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2055418] Re: autoinstall crashing on 24.04 desktop daily build
@crish it doesn't appear to like that command: $ sudo apport-cli -u 2055418 -c /var/crash/*.crash Usage: apport-cli [options] [symptom|pid|package|program path|.apport/.crash file] apport-cli: error: -u/--update-bug option cannot be used together with options for a new report -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/2055418 Title: autoinstall crashing on 24.04 desktop daily build Status in subiquity: New Status in tracker package in Ubuntu: New Bug description: Classis 24.04 Daily build 02-28-2024 AMD64 Using the following autoinstall user-data file, the installer crashes as soon as it loads in the GUI. ``` #cloud-config autoinstall: version: 1 apt: geoip: true preserve_sources_list: false primary: - arches: [amd64, i386] uri: http://archive.ubuntu.com/ubuntu - arches: [default] uri: http://ports.ubuntu.com/ubuntu-ports kernel: package: linux-generic-hwe-22.04 codecs: install: false drivers: install: false oem: install: auto source: id: ubuntu-desktop-minimal search_drivers: false timezone: America/Chicago updates: security identity: hostname: tiny password: $6$NtXwPsM/enBpRMOS$lxsTsJPuSzovFVWJdN3TF89yaqVzLTeqthUD8feRljnTs6EENgkOqttrkd3fiNWJFqRqi.5/m7RUi6.IgKkwb0 username: ubuntu keyboard: layout: us toggle: null variant: '' locale: en_US #refresh-installer: # update: yes storage: layout: name: hybrid encrypted: yes ssh: allow-pw: true install-server: true authorized-keys: - [key-1] - [key-2] ``` An ubuntu GUI crash report window appears, saying that the process /usr/libexec/tracker-extract-3 is what crashed. Attached is the entirety of the /var/log/installer directory. This same autoinstall file used in conjunction with a 23.10.1 ISO works perfectly fine. TPM+FDE and all. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2055418/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1729433]
I forgot to mention: the behavior observed in my comment #58 above is consistent across the apps, i.e. on my end it behaves the same in Draw like it does in Calc or Writer; I don't get minuscule windows on demaximizing, but the window size restoration is still a coin toss between "what it was" and "what is the width and height of the maximized window". -- 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/1729433 Title: LibreOffice doesn't remember window size when running under Wayland Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice package in Fedora: Confirmed Bug description: 1. Open any LibreOffice document, e.g., a Writer or Calc document. 2. Make the window a reasonable, non-maximized size. 3. Maximize the window. 4. Close LibreOffice. 5. Open the document again; it will open maximized. 6. Un-maximize the window. 7. Observe how the window has a ridiculously small size, not its previously unmaximized size. LibreOffice or gnome-shell bug? Not sure. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libreoffice-core 1:5.4.1-0ubuntu1 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.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 1 16:21:29 2017 InstallationDate: Installed on 2017-05-19 (166 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: libreoffice UpgradeStatus: Upgraded to artful on 2017-10-20 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1729433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1729433]
It partially works for me in version 24.2 from Flathub, on Wayland GNOME 45 / Fedora 39. What works: it doesn't become minuscule. What doesn't work optimally: it seems the maximization state is maybe not saved independently from width/height, because sometimes when you unmaximize it, either... * It unmaximizes to the previous window width/height (correct behavior), or; * It unmaximizes to the "maximized window's width/height" (incorrect behavior) See this demonstration video showing both situations with LibreOffice Calc 24.2: https://youtu.be/dv8gb1GljzU Further reference that might help as inspiration for implementation, i.e. how it works in GNOME apps at least: https://developer.gnome.org/documentation/tutorials/save-state.html (you can see there that the maximization state is saved independently from width/height, but also you need to infer that width/height shouldn't get saved while in maximized state, only in windowed state) --- Version: 24.2.0.3 (X86_64) / LibreOffice Community Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1 CPU threads: 8; OS: Linux 6.6; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Flatpak Calc: threaded -- 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/1729433 Title: LibreOffice doesn't remember window size when running under Wayland Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice package in Fedora: Confirmed Bug description: 1. Open any LibreOffice document, e.g., a Writer or Calc document. 2. Make the window a reasonable, non-maximized size. 3. Maximize the window. 4. Close LibreOffice. 5. Open the document again; it will open maximized. 6. Un-maximize the window. 7. Observe how the window has a ridiculously small size, not its previously unmaximized size. LibreOffice or gnome-shell bug? Not sure. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libreoffice-core 1:5.4.1-0ubuntu1 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.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 1 16:21:29 2017 InstallationDate: Installed on 2017-05-19 (166 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: libreoffice UpgradeStatus: Upgraded to artful on 2017-10-20 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1729433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949291]
With my marketing hat on: I believe the solution is not to try to make infobars thinner or try to space out the nags, but rather to combine those calls-to-action into one infobar (that is deferred if needed, to not be shown at the same time as the read-only document infobar). Infobars (at least in GTK) can have multiple action buttons, and the "Get involved" and "Donate" actions should be only one thing: "Contribute", pointing to a unified web landing page that takes care both of the "contribute by donating money" and "contribute by volunteering" scenarios. No need to make those separate messages. As such, if you're going to nag every user on every new release, then my recommendation would be a single nag infobar like this: > Welcome to LibreOffice XYZ! Discover what's new in this version, and help us future versions! [ Read the Release Notes] [ Contribute ] [X] Clicking the buttons other than X would not close the infobar, that way they can click both buttons. If you show three nags one after another (even on separate startups) instead, then you're just frustration-conditioning the user to close/dismiss anything shown there, and your nags lose their effectiveness. -- 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/1949291 Title: LibreOffice has started displaying a donation nag Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Triaged Bug description: I just opened up a spreadsheet (technically a CSV file, but who's counting), to discover LibreOffice displaying an eye-catching blue "Your donations support our worldwide community." banner just below the toolbars and about a toolbar and a half tall. This irritating nag is apparently supposed to display every 90 to 180 days with no in-application means to disable it permanently, and there's apparently also a "Help us make LibreOffice even better!" banner that can appear too. According to this blog post... https://www.remembertheusers.com/2019/11/0580-libreoffice-nag- notices.html ...it is not responsive to configuration overrides within the user profile and the only apparent solution that doesn't require patching the source and rebuilding is to create a file containing the following markup in `$BASEDIR/share/registry` (`/usr/lib/libreoffice/share/registry` as installed by the Ubuntu package): http://www.w3.org/2001/XMLSchema; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xmlns:oor="http://openoffice.org/2001/registry;> http://openoffice.org/2004/installation; oor:name="Setup" oor:package="org.openoffice"> 0 0 Regardless of how it's achieved, I think it's tasteless, irritating, and probably doesn't give a very good image to any office customers Ubuntu may have downstream for random employees to be receiving nag banners like that in IT-installed software. Please consider patching it out or otherwise ensuring it never triggers in distro-provided builds of LibreOffice. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice 1:6.4.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun Oct 31 04:32:03 2021 SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1949291/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046001] [NEW] PipeWire: Too many open files
Public bug reported: Starting with Ubuntu 23.10 , PipeWire regularly started running into a file descriptor limits likely to a known leak which is already fixed upstream, therefore either updating or fix backporting would be required. Symptoms vary: - Media playback may not start - Media playback may start but without sound - Media playback may suppress the audio output of another source Sample log output: ``` mod.access: 0x560d8eda5270: client 0x560d8f26fa50 sandbox check failed: Too many open files mod.access: 0x560d8eda5270: client 0x560d8f26fa50 sandbox check failed: Too many open files mod.client-node: can't create node: Too many open files mod.protocol-native: connection 0x560d8f270390: could not recvmsg on fd:0: Bad file descriptor mod.protocol-native: 0x560d8ed941a0: connection_data: client 0x560d8f26fa50 error -9 (Bad file descriptor) ``` More info: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3406 ** Affects: pipewire (Ubuntu) Importance: Undecided Status: New ** Package changed: ubuntu-release-upgrader (Ubuntu) => pipewire (Ubuntu) -- 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/2046001 Title: PipeWire: Too many open files Status in pipewire package in Ubuntu: New Bug description: Starting with Ubuntu 23.10 , PipeWire regularly started running into a file descriptor limits likely to a known leak which is already fixed upstream, therefore either updating or fix backporting would be required. Symptoms vary: - Media playback may not start - Media playback may start but without sound - Media playback may suppress the audio output of another source Sample log output: ``` mod.access: 0x560d8eda5270: client 0x560d8f26fa50 sandbox check failed: Too many open files mod.access: 0x560d8eda5270: client 0x560d8f26fa50 sandbox check failed: Too many open files mod.client-node: can't create node: Too many open files mod.protocol-native: connection 0x560d8f270390: could not recvmsg on fd:0: Bad file descriptor mod.protocol-native: 0x560d8ed941a0: connection_data: client 0x560d8f26fa50 error -9 (Bad file descriptor) ``` More info: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3406 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2046001/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2045948] [NEW] Incorrect time zone detected
Public bug reported: Ubuntu version: 22.04.3 LTS gnome-settings-daemon version: 42.1-1ubuntu2.2 My system is incorrectly setting the time zone to "MST (Denver, United States)" while I am currently in Austin, TX which is CST. geoclue shows the correct latitude/longitude: $ /usr/libexec/geoclue-2.0/demos/where-am-i Geolocation service in use Client object: /org/freedesktop/GeoClue2/Client/7 New location: Latitude:30.376800° Longitude: -97.893500° Accuracy:5000.00 meters Timestamp: Thu 07 Dec 2023 09:36:18 PM MST (1702010178 seconds since the Epoch) which corresponds to Austin, TX. My syslog shows 1000s of assertion errors in gsd-datetime: Dec 6 00:06:31 jnchase-thinkpad gsd-datetime[1964]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed Dec 6 00:06:31 jnchase-thinkpad gsd-datetime[1964]: message repeated 302 times: [ g_object_ref: assertion 'G_IS_OBJECT (object)' failed] Dec 6 00:06:31 jnchase-thinkpad gsd-datetime[1964]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed Dec 6 00:06:31 jnchase-thinkpad gsd-datetime[1964]: message repeated 1315 times: [ g_object_ref: assertion 'G_IS_OBJECT (object)' failed] Dec 6 00:06:31 jnchase-thinkpad gsd-datetime[1964]: gweather_location_has_coords: assertion 'loc != NULL' failed Dec 6 00:06:31 jnchase-thinkpad gsd-datetime[1964]: gweather_location_get_city_name: assertion 'loc != NULL' failed Dec 6 00:06:31 jnchase-thinkpad gsd-datetime[1964]: gweather_location_get_country: assertion 'loc != NULL' failed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-settings-daemon 42.1-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.14.0-1059.67-oem 5.14.21 Uname: Linux 5.14.0-1059-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Dec 7 23:57:53 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220425-68+sutton-focal-amd64+X02 InstallationDate: Installed on 2022-05-10 (576 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220425-07:09 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to jammy on 2023-06-15 (175 days ago) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages wayland-session -- 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/2045948 Title: Incorrect time zone detected Status in gnome-settings-daemon package in Ubuntu: New Bug description: Ubuntu version: 22.04.3 LTS gnome-settings-daemon version: 42.1-1ubuntu2.2 My system is incorrectly setting the time zone to "MST (Denver, United States)" while I am currently in Austin, TX which is CST. geoclue shows the correct latitude/longitude: $ /usr/libexec/geoclue-2.0/demos/where-am-i Geolocation service in use Client object: /org/freedesktop/GeoClue2/Client/7 New location: Latitude:30.376800° Longitude: -97.893500° Accuracy:5000.00 meters Timestamp: Thu 07 Dec 2023 09:36:18 PM MST (1702010178 seconds since the Epoch) which corresponds to Austin, TX. My syslog shows 1000s of assertion errors in gsd-datetime: Dec 6 00:06:31 jnchase-thinkpad gsd-datetime[1964]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed Dec 6 00:06:31 jnchase-thinkpad gsd-datetime[1964]: message repeated 302 times: [ g_object_ref: assertion 'G_IS_OBJECT (object)' failed] Dec 6 00:06:31 jnchase-thinkpad gsd-datetime[1964]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed Dec 6 00:06:31 jnchase-thinkpad gsd-datetime[1964]: message repeated 1315 times: [ g_object_ref: assertion 'G_IS_OBJECT (object)' failed] Dec 6 00:06:31 jnchase-thinkpad gsd-datetime[1964]: gweather_location_has_coords: assertion 'loc != NULL' failed Dec 6 00:06:31 jnchase-thinkpad gsd-datetime[1964]: gweather_location_get_city_name: assertion 'loc != NULL' failed Dec 6 00:06:31 jnchase-thinkpad gsd-datetime[1964]: gweather_location_get_country: assertion 'loc != NULL' failed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-settings-daemon 42.1-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.14.0-1059.67-oem 5.14.21 Uname: Linux 5.14.0-1059-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Dec 7 23:57:53 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
[Desktop-packages] [Bug 2027904] Re: LibreOffice Snap extremely slow to launch.
In general, snaps are noticeably faster than they used to be, but this one is particularly bad. It takes several seconds to start with an SSD and there is no launch feedback. It's still slow even after first launch. Native and flatpak versions perform much better on the same hardware. I'm on a ThinkPad X1 Extreme. -- 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/2027904 Title: LibreOffice Snap extremely slow to launch. Status in libreoffice package in Ubuntu: Confirmed Bug description: It takes around 3 to 4 seconds to launch even post start-up launching. Other snaps are snappy ! No logs indicate any errors or warnings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2027904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 576669] Re: Document Viewer has no support for common office document file formats
** Changed in: evince (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/576669 Title: Document Viewer has no support for common office document file formats Status in Evince: Expired Status in evince package in Ubuntu: Won't Fix Bug description: Binary package hint: evince Working on creating some new checkbox tests and I've discovered that evince, at least as shipped in 10.04 LTS has no support for MS Office formats. I've tried the .xls and .doc files that are shipped in /usr/share/example-content. In both cases, evince opens with an error that says: File type OLE2 compound document storage (application/x-ole-storage) is not supported. For kicks, I then tried .odt files and got this error: File type OpenDocument Text (application/vnd.oasis.opendocument.text) is not supported. Nor does it support .rtf documents: File type RTF document (application/rtf) is not supported. Nor does it like ods documents: File type OpenDocument Spreadsheet (application/vnd.oasis.opendocument.spreadsheet) is not supported It DOES open odp documents. at least... I did not have a pdf file on hand to try... BUT, in any case, it does not seem to support ANYTHING right now beyond Open Office Presentation files... ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: evince 2.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic i686 Architecture: i386 Date: Thu May 6 18:07:43 2010 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/576669/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 655713] Re: Logic needed to disable built in pointing devices when external devices are connected
** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Invalid ** Changed in: gnome-control-center Status: New => Invalid -- 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/655713 Title: Logic needed to disable built in pointing devices when external devices are connected Status in gnome-control-center: Invalid Status in gnome-control-center package in Ubuntu: Invalid Bug description: Binary package hint: xserver-xorg-input-mouse Just about every laptop and netbook these days comes with an built in trackpad. These are often very frustrating as just brushing against them, or in some cases even just moving a hand over them can trigger a mouse movement or click event. This is especially frustrating when the user is using an external pointing device such as a bluetooth or wireless mouse. Windows has provided the functionality to disable onboard pointing devices when an external mouse is connected/attached, Ubuntu should as well. This is a welcome feature in Windows that saves a lot of hassle. Currently, I have to manually disable my onboard trackpad, which leads to issues should my mouse drop connection for whatever reason. It would be awesome if Ubuntu could recognize that external mouse and turn off the trackpad, then turn the trackpad back on when the mouse has been detached. Just a wishlist item for Natty. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: xserver-xorg-input-mouse 1:1.5.0-2build1 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 260.19.06 Mon Sep 13 04:29:19 PDT 2010 GCC version: gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5) Architecture: amd64 Date: Wed Oct 6 09:18:10 2010 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MachineType: Alienware M15x ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=acc23352-13ab-4854-b1d7-a1099a5bf3a5 ro crashkernel=384M-2G:64M,2G-:128M quiet splash ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: xserver-xorg-input-mouse dmi.bios.date: 03/11/2010 dmi.bios.vendor: Alienware dmi.bios.version: A05 dmi.board.vendor: Alienware dmi.board.version: A05 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A05 dmi.modalias: dmi:bvnAlienware:bvrA05:bd03/11/2010:svnAlienware:pnM15x:pvrA05:rvnAlienware:rn:rvrA05:cvnAlienware:ct8:cvrA05: dmi.product.name: M15x dmi.product.version: A05 dmi.sys.vendor: Alienware system: distro: Ubuntu codename: maverick architecture: x86_64 kernel: 2.6.35-22-generic To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/655713/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 49579] Re: screen doesn't lock when some menu is open
Release EOL ** Changed in: gnome-screensaver (Ubuntu Quantal) Status: New => Won't Fix -- 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/49579 Title: screen doesn't lock when some menu is open Status in GNOME Screensaver: Expired Status in OEM Priority Project: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in X.Org X server: Invalid Status in gnome-screensaver package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in unity package in Ubuntu: Triaged Status in gnome-screensaver source package in Precise: Won't Fix Status in gnome-shell source package in Precise: Confirmed Status in unity source package in Precise: Won't Fix Status in gnome-screensaver source package in Quantal: Won't Fix Status in gnome-shell source package in Quantal: Won't Fix Status in unity source package in Quantal: Won't Fix Status in gnome-screensaver source package in Wily: Won't Fix Status in gnome-shell source package in Wily: Won't Fix Status in unity source package in Wily: Won't Fix Status in gnome-screensaver source package in Xenial: Triaged Status in gnome-shell source package in Xenial: Confirmed Status in unity source package in Xenial: Triaged Status in xorg-server package in Debian: Confirmed Bug description: Binary package hint: gnome-screensaver I'm running a fresh install of Dapper with screensaver set to 'blank screen', and 'lock screen when screensaver is active' enabled. If a panel menu (e.g. Applications) is open and the machine is left idle, the screen fails to lock. It fades out after the time period as expected, but the desktop reappears after a few seconds. Ben (comments / criticism welcome, this is my first bug report) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 49579] Re: screen doesn't lock when some menu is open
Release EOL ** Changed in: gnome-screensaver (Ubuntu Wily) Status: New => Won't Fix -- 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/49579 Title: screen doesn't lock when some menu is open Status in GNOME Screensaver: Expired Status in OEM Priority Project: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in X.Org X server: Invalid Status in gnome-screensaver package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in unity package in Ubuntu: Triaged Status in gnome-screensaver source package in Precise: Won't Fix Status in gnome-shell source package in Precise: Confirmed Status in unity source package in Precise: Won't Fix Status in gnome-screensaver source package in Quantal: Won't Fix Status in gnome-shell source package in Quantal: Won't Fix Status in unity source package in Quantal: Won't Fix Status in gnome-screensaver source package in Wily: Won't Fix Status in gnome-shell source package in Wily: Won't Fix Status in unity source package in Wily: Won't Fix Status in gnome-screensaver source package in Xenial: Triaged Status in gnome-shell source package in Xenial: Confirmed Status in unity source package in Xenial: Triaged Status in xorg-server package in Debian: Confirmed Bug description: Binary package hint: gnome-screensaver I'm running a fresh install of Dapper with screensaver set to 'blank screen', and 'lock screen when screensaver is active' enabled. If a panel menu (e.g. Applications) is open and the machine is left idle, the screen fails to lock. It fades out after the time period as expected, but the desktop reappears after a few seconds. Ben (comments / criticism welcome, this is my first bug report) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 49579] Re: screen doesn't lock when some menu is open
Release EOL ** Changed in: gnome-shell (Ubuntu Quantal) Status: New => Won't Fix -- 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/49579 Title: screen doesn't lock when some menu is open Status in GNOME Screensaver: Expired Status in OEM Priority Project: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in X.Org X server: Invalid Status in gnome-screensaver package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in unity package in Ubuntu: Triaged Status in gnome-screensaver source package in Precise: Won't Fix Status in gnome-shell source package in Precise: Confirmed Status in unity source package in Precise: Won't Fix Status in gnome-screensaver source package in Quantal: Won't Fix Status in gnome-shell source package in Quantal: Won't Fix Status in unity source package in Quantal: Won't Fix Status in gnome-screensaver source package in Wily: Won't Fix Status in gnome-shell source package in Wily: Won't Fix Status in unity source package in Wily: Won't Fix Status in gnome-screensaver source package in Xenial: Triaged Status in gnome-shell source package in Xenial: Confirmed Status in unity source package in Xenial: Triaged Status in xorg-server package in Debian: Confirmed Bug description: Binary package hint: gnome-screensaver I'm running a fresh install of Dapper with screensaver set to 'blank screen', and 'lock screen when screensaver is active' enabled. If a panel menu (e.g. Applications) is open and the machine is left idle, the screen fails to lock. It fades out after the time period as expected, but the desktop reappears after a few seconds. Ben (comments / criticism welcome, this is my first bug report) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 49579] Re: screen doesn't lock when some menu is open
Release EOL ** Changed in: gnome-shell (Ubuntu Wily) Status: New => Won't Fix -- 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/49579 Title: screen doesn't lock when some menu is open Status in GNOME Screensaver: Expired Status in OEM Priority Project: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in X.Org X server: Invalid Status in gnome-screensaver package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in unity package in Ubuntu: Triaged Status in gnome-screensaver source package in Precise: Won't Fix Status in gnome-shell source package in Precise: Confirmed Status in unity source package in Precise: Won't Fix Status in gnome-screensaver source package in Quantal: Won't Fix Status in gnome-shell source package in Quantal: Won't Fix Status in unity source package in Quantal: Won't Fix Status in gnome-screensaver source package in Wily: Won't Fix Status in gnome-shell source package in Wily: Won't Fix Status in unity source package in Wily: Won't Fix Status in gnome-screensaver source package in Xenial: Triaged Status in gnome-shell source package in Xenial: Confirmed Status in unity source package in Xenial: Triaged Status in xorg-server package in Debian: Confirmed Bug description: Binary package hint: gnome-screensaver I'm running a fresh install of Dapper with screensaver set to 'blank screen', and 'lock screen when screensaver is active' enabled. If a panel menu (e.g. Applications) is open and the machine is left idle, the screen fails to lock. It fades out after the time period as expected, but the desktop reappears after a few seconds. Ben (comments / criticism welcome, this is my first bug report) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 49579] Re: screen doesn't lock when some menu is open
Release EOL ** Changed in: unity (Ubuntu Wily) Status: New => Won't Fix -- 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/49579 Title: screen doesn't lock when some menu is open Status in GNOME Screensaver: Expired Status in OEM Priority Project: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in X.Org X server: Invalid Status in gnome-screensaver package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in unity package in Ubuntu: Triaged Status in gnome-screensaver source package in Precise: Won't Fix Status in gnome-shell source package in Precise: Confirmed Status in unity source package in Precise: Won't Fix Status in gnome-screensaver source package in Quantal: Won't Fix Status in gnome-shell source package in Quantal: Won't Fix Status in unity source package in Quantal: Won't Fix Status in gnome-screensaver source package in Wily: Won't Fix Status in gnome-shell source package in Wily: Won't Fix Status in unity source package in Wily: Won't Fix Status in gnome-screensaver source package in Xenial: Triaged Status in gnome-shell source package in Xenial: Confirmed Status in unity source package in Xenial: Triaged Status in xorg-server package in Debian: Confirmed Bug description: Binary package hint: gnome-screensaver I'm running a fresh install of Dapper with screensaver set to 'blank screen', and 'lock screen when screensaver is active' enabled. If a panel menu (e.g. Applications) is open and the machine is left idle, the screen fails to lock. It fades out after the time period as expected, but the desktop reappears after a few seconds. Ben (comments / criticism welcome, this is my first bug report) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 49579] Re: screen doesn't lock when some menu is open
Release EOL ** Also affects: gnome-screensaver (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: unity (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: gnome-screensaver (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: unity (Ubuntu Wily) Importance: Undecided Status: New ** Changed in: unity (Ubuntu Quantal) Status: New => Won't Fix -- 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/49579 Title: screen doesn't lock when some menu is open Status in GNOME Screensaver: Expired Status in OEM Priority Project: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in X.Org X server: Invalid Status in gnome-screensaver package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in unity package in Ubuntu: Triaged Status in gnome-screensaver source package in Precise: Won't Fix Status in gnome-shell source package in Precise: Confirmed Status in unity source package in Precise: Won't Fix Status in gnome-screensaver source package in Quantal: Won't Fix Status in gnome-shell source package in Quantal: Won't Fix Status in unity source package in Quantal: Won't Fix Status in gnome-screensaver source package in Wily: Won't Fix Status in gnome-shell source package in Wily: Won't Fix Status in unity source package in Wily: Won't Fix Status in gnome-screensaver source package in Xenial: Triaged Status in gnome-shell source package in Xenial: Confirmed Status in unity source package in Xenial: Triaged Status in xorg-server package in Debian: Confirmed Bug description: Binary package hint: gnome-screensaver I'm running a fresh install of Dapper with screensaver set to 'blank screen', and 'lock screen when screensaver is active' enabled. If a panel menu (e.g. Applications) is open and the machine is left idle, the screen fails to lock. It fades out after the time period as expected, but the desktop reappears after a few seconds. Ben (comments / criticism welcome, this is my first bug report) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10
** Also affects: nautilus via https://github.com/ibus/ibus/issues/2486 Importance: Unknown Status: Unknown ** Project changed: nautilus => ibus -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1996652 Title: Nautilus search is slow and jumbles keyboard input on 22.10 Status in ibus: Unknown Status in nautilus package in Ubuntu: Confirmed Bug description: Since my upgrade to 22.10, I've found the search box in Nautilus (files) essentially unusable. It is notably sluggish to launch and browse in general. But most detrimental to the usability is this: The characters do not appear in real time as I type. When they do appear, they are sometimes jumbled or in reverse (consistently reproducible). As I type in the file search box, the circular cursor spins intermittently, then the UI catches up and it's not what I typed. For example, I just typed "umbrella" into the search box, and Nautilus searched for: "umballer" Off-the-cuff test #2, searched for "Ubuntu" and I ended up with "Ubunut" ... you can't make this up. :-) Test #3, typed Launchpad, ended up with a search for "Laudaphcn". Keyboard input everywhere else on the system is otherwise normal and snappy. No pun intended, really. FWIW Nautilus files preferences are as default (Search in subfolders, Show thumbnails, File count == This computer only). $ apt-cache policy nautilus nautilus: Installed: 1:43.0-1ubuntu1 Candidate: 1:43.0-1ubuntu1 Version table: *** 1:43.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status $ uname -r 5.19.0-23-generic $ lsb_release -rd Description:Ubuntu 22.10 Release:22.10 $ snap list Name Version RevTracking Publisher Notes bare 1.0 5 latest/stable canonical✓ base core 16-2.57.2 13886 latest/stable canonical✓ core core18 20221027 2620 latest/stable canonical✓ base core20 20221027 1695 latest/stable canonical✓ base gnome-3-34-18040+git.3556cb3 77 latest/stable/… canonical✓ - gnome-3-38-20040+git.6f39565 119latest/stable canonical✓ - google-cloud-sdk 409.0.0 298latest/stable google-cloud-sdk✓ classic gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓ - snap-store 41.3-64-g512c0ff 599latest/stable/… canonical✓ - snapd 2.57.417336 latest/stable canonical✓ snapd snapd-desktop-integration 0.1 14 latest/stable/… canonical✓ - Side question: Since this system has transitioned across several upgrades from 20.04 to 22.10, do I really need all of these core* and gnome* snaps? To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1996652/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2018656] [NEW] login process frozen in between username and password
Public bug reported: MY SYSTEM No LSB modules are available. Description:Ubuntu 23.04 Release:23.04 gnome-online-accounts: Installed: 3.48.0-1 Candidate: 3.48.0-1 Version table: *** 3.48.0-1 500 500 http://us.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status I have tested this on my desktop running 23.04 on Intel I-9, and the second desktop running the same (23.04) but on Intel I-7, and both of them show the same problem. -PROBLEM--- When I entered my email address in my Google account, I could provide my email address, and after I clicked on the following form to enter my password. The form was able to pick up my email address and moved to the following form for password entry; it just froze in between. Sometimes, the password form could pick up the first keyboard character but never go past 2nd character. Sometimes, it just froze without being able to pick up the first keyboard character. Then a bit later, the whole box of gnome-online-accounts blacks out. Closing with X didn't work, so I had to xkill the app. -TYPICAL BEHAVIOR--- Usually, on 22.04, I never had a problem adding online accounts, particularly for Google accounts. The first form asked for my email address, and quickly moved on to the following form asking for a password. Once the password is accepted, it will move on to the next form requesting my authorization for GNOME to connect to my account on Google before adding it to my Ubuntu system (I'd see the drive folder on the bar on Nautilus). ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-online-accounts 3.48.0-1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 6 13:51:07 2023 InstallationDate: Installed on 2023-05-04 (2 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2018656 Title: login process frozen in between username and password Status in gnome-online-accounts package in Ubuntu: New Bug description: MY SYSTEM No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 gnome-online-accounts: Installed: 3.48.0-1 Candidate: 3.48.0-1 Version table: *** 3.48.0-1 500 500 http://us.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status I have tested this on my desktop running 23.04 on Intel I-9, and the second desktop running the same (23.04) but on Intel I-7, and both of them show the same problem. -PROBLEM--- When I entered my email address in my Google account, I could provide my email address, and after I clicked on the following form to enter my password. The form was able to pick up my email address and moved to the following form for password entry; it just froze in between. Sometimes, the password form could pick up the first keyboard character but never go past 2nd character. Sometimes, it just froze without being able to pick up the first keyboard character. Then a bit later, the whole box of gnome-online-accounts blacks out. Closing with X didn't work, so I had to xkill the app. -TYPICAL BEHAVIOR--- Usually, on 22.04, I never had a problem adding online accounts, particularly for Google accounts. The first form asked for my email address, and quickly moved on to the following form asking for a password. Once the password is accepted, it will move on to the next form requesting my authorization for GNOME to connect to my account on Google before adding it to my Ubuntu system (I'd see the drive folder on the bar on Nautilus). ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-online-accounts 3.48.0-1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 6 13:51:07 2023 InstallationDate: Installed on 2023-05-04 (2 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color
[Desktop-packages] [Bug 362359] Re: Focus gets stuck to a window - impossible to select other windows
Yep, repro works for me: Video: https://www.youtube.com/watch?v=Rr2bWccOUu4 Steps: - Open Google Chrome - Right-click to open a context menu - Use the keyboard shortcut to trigger the gnome screenshot area UI - For me, that's CTRL-ALT-PrintScreen, but I my keybindings may be customized That's it, and it may take a couple tries, but these steps 100% reproduces it for me. Please let me know if it reproduces for you, and if I can provide more info. Notes: - It must be a Google Chrome window. Context menus on gnome-terminal and gimp block my keyboard shortcuts entirely, so I cannot screenshot those context menus, and cannot trigger the issue. - Using "shutter" to take the screenshot instead of gnome screenshot works. I have SHIFT-PrintScreen bound to `shutter -s` -- 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/362359 Title: Focus gets stuck to a window - impossible to select other windows Status in xorg-server package in Ubuntu: Fix Released Bug description: Alright, terribly annoying bug that gets me to reboot several times a day, but very hard to understand how to trigger it. What happens: after some time of usage, you get "stuck" in a window. Idem est, you can not select another window. You can still click, select and drag in the window that has the focus, but clicking on other windows, or on the panel, just doesn't work. Notes: - With window I don't mean "application window". For example it can only be the page view in firefox, and you won't be able to click the buttons or the URL field. It can also be the main text window in xchat, and you wont be able to click in the user list or to change the chatroom. - The click seems to be grabbed by the window having the focus, even if you click outside of it. For example, using xchat, if the main text window has focus, clicking and dragging in the user list will actually select text in the main text window. - Using xev, it seems that clics do not get passed to the correct window at all (nothing received) - I have no idea what triggers this as sometimes it will trigger alone - pc works, I leave it for an hour, I come back, the problem is triggered - Curious effect now: dragging and dropping to another window gives focus to the window, and seems to be the only way to do so. For example if in firefox the main page view window has the focus and I cant click the buttons, drag and dropping text to the buttons gives the focus to the buttons, and I can't clic the page view window anymore. Drag and dropping a button to the page view window gives it its focus back Additional info: * Compiz disabled * Intel graphic card * Ubuntu jaunty - latest patches * Using a laptop, with an USB mouse HAL, xserver, I have no idea where to file this bug into. I hope it will be fixed before the release, it is really terribly annoying :s Please tell me if there is any other detail I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/362359/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 362359] Re: Focus gets stuck to a window - impossible to select other windows
This is happening to me now with Gnome on Ubuntu 22.04.3. I'm going to document all the behaviors I see, and I think I have reproduction steps (taking a screenshot when a context menu is open, maybe specifically with shutter), but I need to reboot to verify the exact steps. Observations while it is stuck: - Core issue: Window focus cannot be changed with the mouse. - But it can with the keyboard. Alt-Tab still works. - On the focused window: All mouse functions work: left / right / middle / wheel / hover - On other windows: ONLY hover and wheel (scroll) DO WORK. No clicks whatsoever - On the upper or lower gnome toolbars: nothing works. No clicks, no hovers. But the clock time is still correct, so they're "working" - If I tap META, it opens the activities ui, but no mouse functions work (click/hover/wheel), but I can hit TAB or start typing to search for an app to launch / use arrow keys to navigate the interface. - Regarding window adjustments (resize by borders, drag by title, close/maximize buttons) - Google Chrome responds differently than all other windows. I assume this is due to Chrome's custom window decorations. - Google Chrome can still be resized and dragged by title and closed / maximized / etc - Non-custom window decorations (gnome-terminal, gimp, shutter, vscode, Chrome's debug tools, etc) cannot be dragged, resized, or closed by their window decorations. - META-click to drag and resize does not work for any windows, Google Chrome included. - Changing workspaces with keyboard still works. When you do so, as always, one window in the new workspace is focused, so it's the only working window. - Running xev (and then closing it) did not fix it - Killing shutter did not fix it - Taking a second screenshot with shutter does not fix it. I think that's all I can observe, I'll reboot now, and edit / update if I can reproduce it. -- 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/362359 Title: Focus gets stuck to a window - impossible to select other windows Status in xorg-server package in Ubuntu: Fix Released Bug description: Alright, terribly annoying bug that gets me to reboot several times a day, but very hard to understand how to trigger it. What happens: after some time of usage, you get "stuck" in a window. Idem est, you can not select another window. You can still click, select and drag in the window that has the focus, but clicking on other windows, or on the panel, just doesn't work. Notes: - With window I don't mean "application window". For example it can only be the page view in firefox, and you won't be able to click the buttons or the URL field. It can also be the main text window in xchat, and you wont be able to click in the user list or to change the chatroom. - The click seems to be grabbed by the window having the focus, even if you click outside of it. For example, using xchat, if the main text window has focus, clicking and dragging in the user list will actually select text in the main text window. - Using xev, it seems that clics do not get passed to the correct window at all (nothing received) - I have no idea what triggers this as sometimes it will trigger alone - pc works, I leave it for an hour, I come back, the problem is triggered - Curious effect now: dragging and dropping to another window gives focus to the window, and seems to be the only way to do so. For example if in firefox the main page view window has the focus and I cant click the buttons, drag and dropping text to the buttons gives the focus to the buttons, and I can't clic the page view window anymore. Drag and dropping a button to the page view window gives it its focus back Additional info: * Compiz disabled * Intel graphic card * Ubuntu jaunty - latest patches * Using a laptop, with an USB mouse HAL, xserver, I have no idea where to file this bug into. I hope it will be fixed before the release, it is really terribly annoying :s Please tell me if there is any other detail I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/362359/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016066] Re: Gnome Network Manager GUI does not save routes
I'm affected as well, Ubuntu 22.04.2 and network-manager-gnome
(1.24.0-1ubuntu3)
I also happen to use network-manager-openconnect-gnome (1.2.6-4) but I
don't think it's relevant.
Thank you for providing the nmcli alternative (glad it accepts CIDR
input compared to gnome-client)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/2016066
Title:
Gnome Network Manager GUI does not save routes
Status in network-manager-applet package in Ubuntu:
Confirmed
Bug description:
As in the title. I enclosed the recording adding the route to the
connection via GUI. Does not matter whether that is Ethernet, VPN.
Fails everytime.
On the other hand adding via CLI works perfectly
mastier@drakkar:/etc/NetworkManager$ nmcli connection modify netplan-eno1
+ipv4.routes 123.123.123.123/32
mastier@drakkar:/etc/NetworkManager$ echo $?
0
mastier@drakkar:/etc/NetworkManager$ nmcli con show netplan-eno1|grep
ipv4.routes
ipv4.routes:{ ip = 123.123.123.123/32 }
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: network-manager-gnome 1.24.0-1ubuntu3
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-38-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon
znvpair
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 13 10:12:00 2023
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: network-manager-applet
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.36.6 connected started full enabled enabled
disabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/2016066/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1981163]
It's been 6 months since this bug was assigned. Perhaps it could be reassigned to someone who has the time to look at the bug and fix it? Much appreciated. (This was not a problem until T-bird > 63, I believe). -- 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/1981163 Title: [upstream] In Compose window, if a PDf is joined and clicked to open, Thunderbird launches Firefox instead of Evince Status in Mozilla Thunderbird: In Progress Status in thunderbird package in Ubuntu: Confirmed Bug description: In Thunderbird on Ubuntu Gnome, I set Evince as default program to open pdf files from Thunderbird. In received messages, and those saved on "Sent" folder, it works perfectly. But in the "Compose" window: if I add a pdf file to the message, and double-click on it to open and verify it, Thunderbird always uses Firefox to show it. In case Firefox is not installed (has been removed), I have an error message telling there is not associated application for pdf files and to go to Preferences - where Evince is already and still defined as default. It happens since many months and bug is still present in Thunderbird 102 / Ubuntu 22.10 beta. It's not the same as bug 234349 as here, it's not an URL file but directly a pdf joined in a mail. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1981163/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993308] Re: Update gnome-calendar to 43.1
Hi Jeremy, we keep getting users reporting bugs on 43.0 upstream. Why does 43.1 not show up in https://packages.ubuntu.com/search?keywords=gnome- calendar=names=kinetic=all ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1993308 Title: Update gnome-calendar to 43.1 Status in gnome-calendar package in Ubuntu: Fix Released Status in gnome-calendar source package in Kinetic: Fix Released Bug description: Impact -- There is a new bugfix release in the stable 43 series. https://gitlab.gnome.org/GNOME/gnome-calendar/-/blob/43.1/NEWS This includes several fixes for recurring calendar events. These bugs were considered a release blocker for Fedora 37. https://qa.fedoraproject.org/blockerbugs/milestone/37/final/buglist Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Calendar What Could Go Wrong --- GNOME Calendar is included by default only in the Ubuntu Desktop flavor. If there are bugs in GNOME Calendar, Evolution (not installed by default) could be used instead. GNOME Calendar can sync with Google or Microsoft online calendars. Therefore, bugs in editing calendar events can by synced to those services. GNOME Calendar is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1993308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2008532] Re: Typing a filename in a nautilus window, and the letters are not in the order I typed them.
This is not strictly a Nautilus bug, it's way bigger than that, it potentially affects all GTK4 applications when the system is under stress. I was told it's an ibus bug rather than GTK, so I filed it here, and I would really appreciate it if your team can help investigate or fix it: https://github.com/ibus/ibus/issues/2486 ** Bug watch added: github.com/ibus/ibus/issues #2486 https://github.com/ibus/ibus/issues/2486 ** Also affects: nautilus via https://github.com/ibus/ibus/issues/2486 Importance: Unknown Status: Unknown ** Project changed: nautilus => ibus -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2008532 Title: Typing a filename in a nautilus window, and the letters are not in the order I typed them. Status in ibus: Unknown Status in nautilus package in Ubuntu: New Bug description: On my Lenovo Yoga 260 I have this annoying problem. At first I thought it was just my typing, but after carefully testing it, I find it is not my typing. You need to type the characters fairly quickly, but often when you do, they come on the search bar in a different order than you typed them. For example, I have a directory called LaserTag and so when I want to find it among all the others in my directory, I open the nautilus window and start typing Laser, but what is printed in the search bar is Lsaer. This may happen in some other programs. I am not sure about that, but it is at least most apparent in nautilus, and reproducible. For example, I did the test twice and got Lsaer twice just now. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Feb 24 15:26:45 2023 InstallationDate: Installed on 2019-04-19 (1407 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-10-25 (122 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 python3-nautilus 4.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/2008532/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972790] Re: Can't connect to hotspot created on ubuntu
Also affected. Downgrading to 2.9 worked. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1972790 Title: Can't connect to hotspot created on ubuntu Status in wpa package in Ubuntu: Confirmed Bug description: We currently have older systems (18.04) with hotspot's and we will migrate to 22.04. Anything work's fine, expect the hotspot. The Hotspot will be created and is visible in the WLAN-List, but if the security is set to "WPA & WPA2 Personal" we get the error message "Failed to connect to the network". If we change the Security to "WPA3 Personal" we get the error message "Invalid Password", even if the password is correct. As soon we remove the security (change it to "none"), we can connect with out any problems. We can reproduce it with a fresh installtion of the Ubuntu Server 22.04 and the following two commands: apt install network-manager nmcli c add type wifi ifname wlp3s0 con-name Hotspot autoconnect yes ssid test-ap 802-11-wireless.mode ap 802-11-wireless.band bg 802-11-wireless.mac-address "80:45:dd:f0:27:ba" wifi-sec.group ccmp wifi-sec.key-mgmt wpa-psk wifi-sec.pairwise ccmp wifi-sec.proto rsn wifi-sec.psk "test12345" ipv4.addresses 192.168.60.1/24 ipv4.method shared && nmcli connection up Hotspot We thought it could be similar to this issue: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267 Because if we test it with 20.04 it worked fine, because 20.04 uses the Version 2:2.9.0-21build1 as described in the Ticket. As @Sebastian Bacher suggested (https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/58), i created a own report. In the attachment is the requested log file. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-6 [modified: lib/systemd/system/wpa_supplicant.service] ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 10 07:24:15 2022 InstallationDate: Installed on 2022-05-10 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1972790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1943488] Re: when typeing too fast in the search line searching stops to work
If this is related to the bug I had filed upstream (linked above), then this should be fixed in Nautilus 43.1 or later. ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #1731 https://gitlab.gnome.org/GNOME/nautilus/-/issues/1731 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/-/issues/1731 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1943488 Title: when typeing too fast in the search line searching stops to work Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Confirmed Bug description: 1. $ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 2. $ apt-cache policy nautilus nautilus: Installed: 1:3.36.3-0ubuntu1 Candidate: 1:3.36.3-0ubuntu1 Version table: *** 1:3.36.3-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1.1-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 3. When I try to find a file/directory in nautilus I start to type some letters (or press CTRL-f befor typing). Normally nautilus tries to find the files and shows the result. 4. When I am typing too fast (or normal speed?) the searching hangs up, a small blue circle goes around in the left bottom corner and nothing happens for long time. If I cut (CTRL-a CTRL-x) the searched text and paste it back (CTRL-f CTRL-v) the searching is successful, and the result appears immidietly. The situation is same e.g. in gnome-software, so I think this problem is globally exists in gnome. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1943488/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1935070] Re: Traceback during 'ubuntu-drivers list'
** Tags added: servcert-565 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1935070 Title: Traceback during 'ubuntu-drivers list' Status in Ubuntu Drivers Common: Unknown Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Bug description: ubuntu@doubletusk:~$ sudo ubuntu-drivers list ERROR:root:could not open aplay -l Traceback (most recent call last): File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in detect aplay = subprocess.Popen( File "/usr/lib/python3.8/subprocess.py", line 858, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.8/subprocess.py", line 1704, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'aplay' nvidia-driver-418-server, (kernel modules provided by nvidia-dkms-418-server) nvidia-driver-470, (kernel modules provided by nvidia-dkms-470) nvidia-driver-460-server, (kernel modules provided by nvidia-dkms-460-server) nvidia-driver-465, (kernel modules provided by nvidia-dkms-465) nvidia-driver-450-server, (kernel modules provided by nvidia-dkms-450-server) nvidia-driver-460, (kernel modules provided by nvidia-dkms-460) ubuntu@doubletusk:~$ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.9.0~0.20.04.1 Candidate: 1:0.9.0~0.20.04.1 Version table: *** 1:0.9.0~0.20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:0.8.6.5~0.20.04.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 1:0.8.1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ubuntu@doubletusk:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-drivers-common/+bug/1935070/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1935070] Re: Traceback during 'ubuntu-drivers list'
** Bug watch added: github.com/tseliot/ubuntu-drivers-common/issues #78 https://github.com/tseliot/ubuntu-drivers-common/issues/78 ** Also affects: ubuntu-drivers-common via https://github.com/tseliot/ubuntu-drivers-common/issues/78 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1935070 Title: Traceback during 'ubuntu-drivers list' Status in Ubuntu Drivers Common: Unknown Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Bug description: ubuntu@doubletusk:~$ sudo ubuntu-drivers list ERROR:root:could not open aplay -l Traceback (most recent call last): File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in detect aplay = subprocess.Popen( File "/usr/lib/python3.8/subprocess.py", line 858, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.8/subprocess.py", line 1704, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'aplay' nvidia-driver-418-server, (kernel modules provided by nvidia-dkms-418-server) nvidia-driver-470, (kernel modules provided by nvidia-dkms-470) nvidia-driver-460-server, (kernel modules provided by nvidia-dkms-460-server) nvidia-driver-465, (kernel modules provided by nvidia-dkms-465) nvidia-driver-450-server, (kernel modules provided by nvidia-dkms-450-server) nvidia-driver-460, (kernel modules provided by nvidia-dkms-460) ubuntu@doubletusk:~$ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.9.0~0.20.04.1 Candidate: 1:0.9.0~0.20.04.1 Version table: *** 1:0.9.0~0.20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:0.8.6.5~0.20.04.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 1:0.8.1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ubuntu@doubletusk:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-drivers-common/+bug/1935070/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1935070] Re: Traceback during 'ubuntu-drivers list'
I made a PR on github to address the exception handling which I think is the best course here. Adding a dependency on alsa-utils will result in adding further unwanted desktop packages on systems where they don't really belong (anything with Ubuntu Server installed). Just removing the traceback to clean the output and providing a helpful error message is sufficient, IMO. ** Changed in: ubuntu-drivers-common (Ubuntu) Status: Confirmed => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu) Assignee: (unassigned) => Jeff Lane (bladernr) ** Changed in: ubuntu-drivers-common (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1935070 Title: Traceback during 'ubuntu-drivers list' Status in Ubuntu Drivers Common: Unknown Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Bug description: ubuntu@doubletusk:~$ sudo ubuntu-drivers list ERROR:root:could not open aplay -l Traceback (most recent call last): File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in detect aplay = subprocess.Popen( File "/usr/lib/python3.8/subprocess.py", line 858, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.8/subprocess.py", line 1704, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'aplay' nvidia-driver-418-server, (kernel modules provided by nvidia-dkms-418-server) nvidia-driver-470, (kernel modules provided by nvidia-dkms-470) nvidia-driver-460-server, (kernel modules provided by nvidia-dkms-460-server) nvidia-driver-465, (kernel modules provided by nvidia-dkms-465) nvidia-driver-450-server, (kernel modules provided by nvidia-dkms-450-server) nvidia-driver-460, (kernel modules provided by nvidia-dkms-460) ubuntu@doubletusk:~$ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.9.0~0.20.04.1 Candidate: 1:0.9.0~0.20.04.1 Version table: *** 1:0.9.0~0.20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:0.8.6.5~0.20.04.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 1:0.8.1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ubuntu@doubletusk:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-drivers-common/+bug/1935070/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password
It's seemingly much less bad if I disable suspend when plugged into power, and maybe the remaining problems come from plugging in power before resume. -- 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/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 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:
[Desktop-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password
This one seemed like it refused to wake even enough to draw a black scree, just stayed asleep. I've no idea if this is hlepful ** Attachment added: "refuses_to_wake.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5579458/+files/refuses_to_wake.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/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 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:
[Desktop-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password
Another purple screen lockup. It's now also more common the system runs how while closed. ** Attachment added: "purple_screen_lockup-8_april.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5578017/+files/purple_screen_lockup-8_april.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/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 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:
[Desktop-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password
I've still not tried other kernels, in part because ubuntu keeps pushing out new OEM kernels, so I give them all a try, but the same basic problem persist, either gnome-shell gives only a black screen, or else the whole system hangs on the purple screen. I've far more diverse crashes with the latest kernels and the bolt upgrade: https://errors.ubuntu.com/user/f1e063bb5e8c4439fa13d51f06f02ce6ad03d098946e7597fd170a17325d98a76475f94a90f27677619cb85b6c0bd1cc406eece2601001754138f20d7209c37a -- 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/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
[Desktop-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password
It's growing kinda worst with 5.14.0-1031-oem in that gnome-shell now more reliably fails unsleep, but I've not yet seen any real crash under 5.14.0-1031-oem. I've still not tried non OWM kernels. ** Attachment added: "black_screen_with_mouse-29_march-b.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5574448/+files/black_screen_with_mouse-29_march-b.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/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 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
[Desktop-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password
I'd another crash with a purple screen and no mouse movement, but this time only a 10 minute lid close caused the crash. Awful lot of gdm and gnome-shell errors this time, but not clear the source. ** Attachment added: "purple_no_mouse-23_march.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5572272/+files/purple_no_mouse-23_march.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/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 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:
[Desktop-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password
It's again waking with a black screen in which only mouse and Fn+Ctrl+Alt+F?? keys work. I've attached the jountalctl -b0 output from prior to reboot, probably more relevant than grabbing the actual reboot. Mär 23 07:09:16 aletheia kernel: Restarting tasks ... done. Mär 23 07:09:16 aletheia systemd-logind[1556]: Lid opened. Mär 23 07:09:16 aletheia Tor[1683]: Tor has been idle for 26589 seconds; assuming established circuits no longer work. Mär 23 07:09:16 aletheia rtkit-daemon[1766]: The canary thread is apparently starving. Taking action. Mär 23 07:09:16 aletheia rtkit-daemon[1766]: Demoting known real-time threads. Mär 23 07:09:16 aletheia rtkit-daemon[1766]: Demoted 0 threads. Mär 23 07:09:16 aletheia Tor[1683]: Heartbeat: Tor's uptime is 0:00 hours, with 0 circuits open. I've sent 0 kB and received 0 kB. Mär 23 07:09:16 aletheia systemd[1]: NetworkManager-dispatcher.service: Succeeded. Mär 23 07:09:16 aletheia kernel: mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound :00:02.0 (ops i915_hdcp_component_ops [i915]) Mär 23 07:09:16 aletheia kernel: thermal thermal_zone6: failed to read out thermal zone (-61) Mär 23 07:09:16 aletheia systemd[1]: Starting Daily apt download activities... Mär 23 07:09:16 aletheia systemd[1]: Starting Refresh fwupd metadata and update motd... Mär 23 07:09:16 aletheia systemd[1]: Starting Message of the Day... Mär 23 07:09:16 aletheia systemd[1]: Starting Ubuntu Advantage Timer for running repeated jobs... Mär 23 07:09:16 aletheia systemd[1]: motd-news.service: Succeeded. Mär 23 07:09:16 aletheia systemd[1]: Finished Message of the Day. Mär 23 07:09:16 aletheia upowerd[1864]: treating change event as add on /sys/devices/pci:00/:00:14.0/usb3/3-3 Mär 23 07:09:16 aletheia upowerd[1864]: treating change event as add on /sys/devices/pci:00/:00:14.0/usb3/3-3 Mär 23 07:09:16 aletheia systemd-sleep[34855]: System resumed. Mär 23 07:09:16 aletheia kernel: PM: suspend exit Mär 23 07:09:16 aletheia gsd-power[2839]: Error calling suspend action: GDBus.Error:org.freedesktop.login1.OperationInProgress: There's already a shutdown or sleep operation in progress Mär 23 07:09:16 aletheia fwupd[3148]: 06:09:16:0867 FuEngine failed to record HSI attributes: failed to get historical attr: json-glib version too old Mär 23 07:09:16 aletheia systemd[1]: systemd-suspend.service: Succeeded. Mär 23 07:09:16 aletheia systemd[1]: Finished Suspend. We compare this semi-locked gnome-shell with a working unsleep from a brief lid close: Mär 23 07:42:19 aletheia kernel: Restarting tasks ... Mär 23 07:42:19 aletheia kernel: mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound :00:02.0 (ops i915_hdcp_component_ops [i915]) Mär 23 07:42:19 aletheia systemd-logind[1529]: Lid opened. Mär 23 07:42:19 aletheia kernel: done. Mär 23 07:42:19 aletheia upowerd[1838]: treating change event as add on /sys/devices/pci:00/:00:14.0/usb3/3-3 Mär 23 07:42:19 aletheia kernel: thermal thermal_zone6: failed to read out thermal zone (-61) Mär 23 07:42:19 aletheia upowerd[1838]: treating change event as add on /sys/devices/pci:00/:00:14.0/usb3/3-3 Mär 23 07:09:16 aletheia systemd-sleep[34855]: System resumed. Mär 23 07:42:19 aletheia kernel: PM: suspend exit Mär 23 07:42:19 aletheia systemd[1]: systemd-suspend.service: Succeeded. Mär 23 07:42:19 aletheia systemd[1]: Finished Suspend. I wind up with gnome-shell being stuck when "kernel: done" never appears, the "upowerd" line appears twice, and we get the error: Mär 23 07:09:16 aletheia gsd-power[2839]: Error calling suspend action: GDBus.Error:org.freedesktop.login1.OperationInProgress: There's already a shutdown or sleep operation in progress I've maybe some early unsleep phase not finishing correctly, which then convinces gsd-power believing that sleep continues? * Irrelevant looking differences: The mei_hdcp comes before the lid opened line. Activities like tor and rt-kit-daemon have not been asleep long enough to be doing restart work. ** Attachment added: "black_screen_with_mouse.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5572108/+files/black_screen_with_mouse.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/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen
[Desktop-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password
Appears nope I've purely a sleep problem, unless all this fwupd playing turnned off hibernate: ``` root@aletheia:/home/jeff/Downloads# systemctl status hibernate.target ● hibernate.target - Hibernate Loaded: loaded (/lib/systemd/system/hibernate.target; static; vendor prese> Active: inactive (dead) Docs: man:systemd.special(7) root@aletheia:/home/jeff/Downloads# systemctl status hybrid-sleep.target ● hybrid-sleep.target - Hybrid Suspend+Hibernate Loaded: loaded (/lib/systemd/system/hybrid-sleep.target; static; vendor pr> Active: inactive (dead) Docs: man:systemd.special(7) ``` -- 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/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: l
[Desktop-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password
I've found some lenovo firmware oddities too https://github.com/fwupd/firmware-lenovo/issues/210 so I'll poke around there too. ** Bug watch added: github.com/fwupd/firmware-lenovo/issues #210 https://github.com/fwupd/firmware-lenovo/issues/210 -- 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/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 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
[Desktop-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password
It's related to during being suspended: It does not trigger on pressing suspend from the menu bar, waiting briefly, and then pressing keys to wake. It also does not trigger if I close and open the lid less than a minute later. It can now trigger if I close the lid and then reopen the lid 10 minutes later. At this point it arrives at a purple ubuntu login screen, but no responses to keyboard or mouse, and not network presence. Could this be caused by the system changing sleep/suspend mode while sleeping/suspended? Could this be related to /swapfile being only 4 gigs, while main memory is 16 gigs? It's a ThinkPad X1 Carbon Gen 11 running a kernel 5.14.0-1027-oem for a Gen 9 (nothing else exists afaik). I've no idea what OEM kernels change of course, but I can try to figure out changing the kernel. I'll likely need to change something in /etc/default/grub to get access to a grub boot menu to choose kernels. ** Attachment added: "purple_no_mouse_two.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5571706/+files/purple_no_mouse_two.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/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias:
[Desktop-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password
I've also found folks fixed similar issues by downgrading the kernel to 5.11.0.38: https://askubuntu.com/questions/1384450/ubuntu-20-04-wont-wake-from-suspend-or-completely-shutdown -- 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/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 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:
[Desktop-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password
I've also found folks fixed similar issues by downgrading the kernel to 5.11.0.38: https://askubuntu.com/questions/1384450/ubuntu-20-04-wont-wake-from-suspend-or-completely-shutdown -- 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/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Incomplete Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 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:
[Desktop-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password
Also the Fn+Ctrl+Alt+F?? keys no longer worked here. -- 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/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Incomplete Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 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/gnome-shell/+bug/1965219/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password
I'd something new this time, after sleep/suspend it returned to the purple login screen, but now nothing worked, no mouse or keyboard. It ran the fan for a little while, so I give it some time to return, but no luck. ** Attachment added: "purple_no_mouse.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5571532/+files/purple_no_mouse.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/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Incomplete Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 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
[Desktop-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password
oops alright. I've no gnome-shell reports in /var/crash only another systemd-timesyncd report. I don't think gnome-ghell is crashing, but sometimes just stuck when emerging from suspend. -- 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/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Incomplete Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 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:
[Desktop-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password
Is it normal that gnome-session-bin is installed but gnome-session is not installed? I believe this black screen version is different because when switching back with Fn+Ctrl+Alt+F1 it simply returns to the black screen, without any purple password prompt. I suppose another problem must be causing both versions. -- 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/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Incomplete Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 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
[Desktop-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password
It now manifests as a black screen with the same behavior, mouse works but no keyboard, except for Fn+Alt+Ctrl+F?? working. I've attacked the output of journalctl but from the current boot since I used killall -HUP gnome-shell, which yes leave some applications running, but not firefox (or tor browser). It's much less common now but this one happened on suspend trigger by the lid being closed. Thanks! :) ** Attachment added: "black_screen_killall_hup_gnomeshell.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5570958/+files/black_screen_killall_hup_gnomeshell.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/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Incomplete Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core
[Desktop-packages] [Bug 1905519] Re: Syslog is flooded with Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object havi
Sorry I don't check this forum often. I'm on 20.04.3. When I try to update + upgrade that package, apt tells me I'm stuck with version 68 gnome-shell-extension-ubuntu-dock is already the newest version (68ubuntu1~20.04.1). -- 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/1905519 Title: Syslog is flooded with Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Status in Dash to dock: Fix Released Status in gnome-shell-extension-dashtodock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: The syslog is full of these messages, continuously written all day long Nov 25 07:46:42 pc1 gnome-shell[2980]: Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Nov 25 07:46:42 pc1 gnome-shell[2980]: == Stack trace for context 0x56541fffb220 == Nov 25 07:46:42 pc1 gnome-shell[2980]: #0 7ffddbfa1940 b /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:2051 (1839cb6a2420 @ 208) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 25 07:42:45 2020 InstallationDate: Installed on 2014-06-03 (2366 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1905519/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password
It's only the three built in extensions installed. Thanks I'll run journalctl -b-1 > prevboot.txt next time. ls /var/crash/ says _usr_lib_systemd_systemd-timesyncd.102.crash _usr_lib_systemd_systemd-timesyncd.102.upload _usr_lib_systemd_systemd-timesyncd.102.uploaded I only see a similar error on https://errors.ubuntu.com/user/f1e063bb5e8c4439fa13d51f06f02ce6ad03d098946e7597fd170a17325d98a76475f94a90f27677619cb85b6c0bd1cc406eece2601001754138f20d7209c37a Is the lock screen handled by gnome-shell itself or some outside process like gdm3? If there some signal or whatever I can send to gnome-shell -- 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/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Incomplete Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core
[Desktop-packages] [Bug 1905519] Re: Syslog is flooded with Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object havi
Need fix in Ubuntu 20.04, gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1 Patch in #7 failed 4/4 hunks -- 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/1905519 Title: Syslog is flooded with Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Status in Dash to dock: Fix Released Status in gnome-shell-extension-dashtodock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: The syslog is full of these messages, continuously written all day long Nov 25 07:46:42 pc1 gnome-shell[2980]: Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Nov 25 07:46:42 pc1 gnome-shell[2980]: == Stack trace for context 0x56541fffb220 == Nov 25 07:46:42 pc1 gnome-shell[2980]: #0 7ffddbfa1940 b /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:2051 (1839cb6a2420 @ 208) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 25 07:42:45 2020 InstallationDate: Installed on 2014-06-03 (2366 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1905519/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1936679] Re: ubuntu-drivers --gpgpu is not installing -server packages
https://pastebin.ubuntu.com/p/nzxSG3DMVF/ This remains broken in ubuntu-drivers. There is absolutely no difference between what is installed when doing ubuntu-drivers install and ubuntu-drivers install --gpgpu but significant difference when using ubuntu-drivers install nvidia:470-server the first two install exactly the same package set and the latter installs a much smaller subset. If you actually expect that the first two install the exact same package set, why does --gpgpu exist in the first place? If the expectation is that --gpgpu means VER-server, then this remains broken since last year. And if the expectation exists in the middle, then perhaps we need a --gpgpu-server to install the packages from the last example? I guess the first question for this bug is "What EXACTLY is expected when installing using --gpgpu" and then "how do we resolve this bug" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1936679 Title: ubuntu-drivers --gpgpu is not installing -server packages Status in ubuntu-drivers-common package in Ubuntu: New Bug description: Discovered while testing the ubuntu-drivers-common package in -proposed for bug LP:1898601 While waiting on bionic to deploy for verification, something was bugging me about Focal verification from the other day so I re- deployed a DL380 with 4x T4 GPGPUs with Focal and added u-d-c from proposed. What I missed when verifying the other day was that it actually isn't installing the -server package on my server in gpgpu mode. After chatting a bit with Alberto, --gpgpu is supposed to install the nvidia-driver-VER-server package. Instead, the version in -proposed is actually installing nvidia-driver-VER which is incorrect. Attached is a tarball from a fresh focal install that includes the output when doing 'ubuntu-drivers --gpgpu install' and 'ubuntu-drivers --gpgpu debug' after installing the driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1936679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949156] [NEW] firefox often slows to a crawl on page request
Public bug reported: When opening a URL in a new tab/window, firefox frequently slows to a crawl. This lasts for several seconds, then recovers. It does not seem to be related to time since launch. The behaviour is new. When this happens, other machine processes appear unaffected. I can continue working with other applications, just not firefox. Top (/usr/bin/top) shows that GeckoMain is using the majority of CPU at times like this (approx 20%-30% load on an 8 core system), but this is not the only time I see this. I've attached an image of the window title. There appears to be an animation that starts at the left and sweeps across the tab towards the right that also feezes / slows to a crawl at these times. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 93.0+build1-0ubuntu0.21.04.1 ProcVersionSignature: Ubuntu 5.11.0-38.42-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jeff 3090 F pulseaudio /dev/snd/pcmC1D0p: jeff 3090 F...m pulseaudio /dev/snd/controlC0: jeff 3090 F pulseaudio BuildID: 20210927210923 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: i3 Date: Fri Oct 29 07:56:16 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:360 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing EcryptfsInUse: Yes ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-10-23 (2197 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IpRoute: default via 192.168.2.1 dev eth1 proto dhcp metric 100 169.254.0.0/16 dev eth1 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.2.0/24 dev eth1 proto kernel scope link src 192.168.2.157 metric 100 MostRecentCrashID: bp-a0847816-1a40-4e81-8110-dc8171180221 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:360 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1Plugins: iTunes Application Detector - /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:360 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profile2Extensions: extensions.sqlite corrupt or missing Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile2Locales: extensions.sqlite corrupt or missing Profile2Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so Profile2PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:360 Profile2PrefSources: prefs.js Profile2Themes: extensions.sqlite corrupt or missing Profile4Extensions: extensions.sqlite corrupt or missing Profile4IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile4Locales: extensions.sqlite corrupt or missing Profile4PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:360 Profile4PrefSources: prefs.js Profile4Themes: extensions.sqlite corrupt or missing Profile5Extensions: extensions.sqlite corrupt or missing Profile5IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile5Locales: extensions.sqlite corrupt or missing Profile5PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:360 Profile5PrefSources: prefs.js Profile5Themes: extensions.sqlite corrupt or missing Profile6Extensions: extensions.sqlite corrupt or missing Profile6IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile6Locales: extensions.sqlite corrupt or missing Profile6
[Desktop-packages] [Bug 1936679] Re: ubuntu-drivers --gpgpu is not installing -server packages
This is still broken as of 1:0.8.6.3~0.18.04.2 $ ubuntu-drivers --gpgpu devices This is gpgpu mode == /sys/devices/pci:c9/:c9:02.0/:ca:00.0/:cb:01.0/:cd:00.0 == modalias : pci:v10DEd20B5sv10DEsd1533bc03sc02i00 vendor : NVIDIA Corporation driver : nvidia-driver-470-server - distro non-free driver : nvidia-driver-470 - distro non-free recommended driver : xserver-xorg-video-nouveau - distro free builtin This system has 8x A100 compute GPUs, is running Ubuntu Server, and I specified --gpgpu because I want the server compute drivers. But U/D is still insisting on installing the desktop graphics driver instead -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1936679 Title: ubuntu-drivers --gpgpu is not installing -server packages Status in ubuntu-drivers-common package in Ubuntu: New Bug description: Discovered while testing the ubuntu-drivers-common package in -proposed for bug LP:1898601 While waiting on bionic to deploy for verification, something was bugging me about Focal verification from the other day so I re- deployed a DL380 with 4x T4 GPGPUs with Focal and added u-d-c from proposed. What I missed when verifying the other day was that it actually isn't installing the -server package on my server in gpgpu mode. After chatting a bit with Alberto, --gpgpu is supposed to install the nvidia-driver-VER-server package. Instead, the version in -proposed is actually installing nvidia-driver-VER which is incorrect. Attached is a tarball from a fresh focal install that includes the output when doing 'ubuntu-drivers --gpgpu install' and 'ubuntu-drivers --gpgpu debug' after installing the driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1936679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1936679] Re: ubuntu-drivers --gpgpu is not installing -server packages
$ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.8.6.3~0.18.04.2 Candidate: 1:0.8.6.3~0.18.04.2 Version table: *** 1:0.8.6.3~0.18.04.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:0.5.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1936679 Title: ubuntu-drivers --gpgpu is not installing -server packages Status in ubuntu-drivers-common package in Ubuntu: New Bug description: Discovered while testing the ubuntu-drivers-common package in -proposed for bug LP:1898601 While waiting on bionic to deploy for verification, something was bugging me about Focal verification from the other day so I re- deployed a DL380 with 4x T4 GPGPUs with Focal and added u-d-c from proposed. What I missed when verifying the other day was that it actually isn't installing the -server package on my server in gpgpu mode. After chatting a bit with Alberto, --gpgpu is supposed to install the nvidia-driver-VER-server package. Instead, the version in -proposed is actually installing nvidia-driver-VER which is incorrect. Attached is a tarball from a fresh focal install that includes the output when doing 'ubuntu-drivers --gpgpu install' and 'ubuntu-drivers --gpgpu debug' after installing the driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1936679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1898601] Re: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server
Added Hirsute before I realized it is fixed in Hirsute: ubuntu-drivers-common | 1:0.9.0~0.21.04.1 | hirsute-updates | source, amd64, arm64, armhf, ppc64el, riscv64, s390x So I just set it to fix-released for H as well, ignore me. ** Changed in: ubuntu-drivers-common (Ubuntu Bionic) Status: Won't Fix => Confirmed ** Also affects: ubuntu-drivers-common (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: ubuntu-drivers-common (Ubuntu Hirsute) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1898601 Title: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Confirmed Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Groovy: Won't Fix Status in ubuntu-drivers-common source package in Hirsute: Fix Released Bug description: SRU Request [Impact] * ubuntu-drivers installs unnecessary packages when using the "-- gpgpu" argument. Also, it should not depend on alsa-utils, its relevant test should. [Fix] * Passing in "--no-install-recommends" by default with the "--gpgpu" argument will solve the problem. Also, moving the alsa-utils dependency into the test avoids installing an unneeded dependency on servers. [Test Case] * Install ubuntu-drivers-common from -proposed. * Make sure it doesn't pull in alsa-utils. * Install the nvidia driver using "sudo ubuntu-drivers install --gpgpu", and check that the desktop related dependencies are not pulled in. [Regression Risk] Low, since it changes the amount of dependencies we install on servers. +++Update+++ I am in a position where I need to run regression testing using the nVidia drivers on systems configured for GPU compute. This bug prevents me from using ubuntu-drivers to ensure I have the latest Ubuntu Signed drivers. To resolve this, ubuntu-drivers would need to honor --no-install-recommends and not install all those unnecessary desktop environment packages that make no sense on a headless server - When I install the packaged nVidia drivers using --gpgpu, I expect that I am getting compute related GPGPU drivers. Instead, I find that on a fresh Focal installation of Ubuntu Server, I also get a full desktop environment. This sets us up nicely for this bug: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559 because this pulls in gdm3 and a whole host of unnecessary desktop packages but does nothing to mitigate the gdm3 propensity to autosuspend, which makes the server become unresponsive when there is no user activity (even when it's running workloads on the GPGPU, the server can still autosuspend). Additionally, this adds a software stack that causes unnecessary CPU and memory usage on a machine that is meant to run headless and devote all resources to handling GPGPU compute activities. This is gpgpu mode Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: apg aptdaemon aptdaemon-data aspell aspell-en avahi-daemon avahi-utils bluez bubblewrap colord colord-data cracklib-runtime cups-pk-helper dbus-x11 dconf-cli desktop-file-utils dictionaries-common docbook-xml emacsen-common enchant-2 evolution-data-server evolution-data-server-common fprintd gcr gdm3 geoclue-2.0 gir1.2-accountsservice-1.0 gir1.2-atspi-2.0 gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdesktopenums-3.0 gir1.2-gdm-1.0 gir1.2-geoclue-2.0 gir1.2-gnomebluetooth-1.0 gir1.2-gnomedesktop-3.0 gir1.2-graphene-1.0 gir1.2-gweather-3.0 gir1.2-ibus-1.0 gir1.2-mutter-6 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-notify-0.7 gir1.2-polkit-1.0 gir1.2-rsvg-2.0 gir1.2-secret-1 gir1.2-soup-2.4 gir1.2-upowerglib-1.0 gir1.2-vte-2.91 gjs gkbd-capplet gnome-control-center gnome-control-center-data gnome-control-center-faces gnome-desktop3-data gnome-keyring gnome-keyring-pkcs11 gnome-menus gnome-online-accounts gnome-session-bin gnome-session-common gnome-settings-daemon gnome-settings-daemon-common gnome-shell gnome-shell-common gnome-startup-applications gnome-user-docs gstreamer1.0-clutter-3.0 hunspell-en-us ibus ibus-data ibus-gtk ibus-gtk3 iio-sensor-proxy im-config ippusbxd language-selector-gnome libappindicator3-1 libasound2-plugins libaspell15 libavahi-core7 libavahi-glib1 libcamel-1.2-62 libcanberra-gtk3-0 libcanberra-gtk3-module libcanberra-pulse libcheese-gtk25 libclutter-gtk-1.0-0 libcolord-gtk1 libcolorhug2 libcrack2 libdaemon0 libdbusmenu-glib4 libdbusmenu-gtk3-4 libebackend-1.2-10
[Desktop-packages] [Bug 1941932] [NEW] Reverting to nouveau driver leaves dead nvidia links causing suspend and shutdown to fail
Public bug reported: After having problems with the nvidia driver 470, I reverted to the nouveau driver, only to find that using suspend or shutdown in the XFCE4 menu just returned to the login page. However, I found that using the 'shutdown' or 'pm-suspend' commands worked OK. Checking syslog after a failed suspend lead me to /etc/systemd/system directory: lrwxrwxrwx 1 root root9 Aug 25 15:04 nvidia-hibernate.service -> /dev/null lrwxrwxrwx 1 root root9 Aug 25 15:04 nvidia-resume.service -> /dev/null lrwxrwxrwx 1 root root9 Aug 25 15:04 nvidia-suspend.service -> /dev/null Also, there were two directories containing links to the above 'masked' services. Deleting those links restored suspend and shutdown functionality. drwxr-xr-x 2 root root 4096 Aug 26 18:14 systemd-hibernate.service.requires/ drwxr-xr-x 2 root root 4096 Aug 26 18:08 systemd-suspend.service.requires/ Obviously a problem in removing all the nvidia settings. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: 20.04.2 software-properties xubuntu ** Tags added: 20.04.2 software-properties xubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1941932 Title: Reverting to nouveau driver leaves dead nvidia links causing suspend and shutdown to fail Status in software-properties package in Ubuntu: New Bug description: After having problems with the nvidia driver 470, I reverted to the nouveau driver, only to find that using suspend or shutdown in the XFCE4 menu just returned to the login page. However, I found that using the 'shutdown' or 'pm-suspend' commands worked OK. Checking syslog after a failed suspend lead me to /etc/systemd/system directory: lrwxrwxrwx 1 root root9 Aug 25 15:04 nvidia-hibernate.service -> /dev/null lrwxrwxrwx 1 root root9 Aug 25 15:04 nvidia-resume.service -> /dev/null lrwxrwxrwx 1 root root9 Aug 25 15:04 nvidia-suspend.service -> /dev/null Also, there were two directories containing links to the above 'masked' services. Deleting those links restored suspend and shutdown functionality. drwxr-xr-x 2 root root 4096 Aug 26 18:14 systemd-hibernate.service.requires/ drwxr-xr-x 2 root root 4096 Aug 26 18:08 systemd-suspend.service.requires/ Obviously a problem in removing all the nvidia settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1941932/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1940779] [NEW] has_options missing so ssh-agent doesn't start
Public bug reported: The file /etc/X11/Xsession.d/20x11-common_process-args is missing the definition of the function has_option() in the 21.04 distribution. As a result, when lightdm starts X11, even though use-ssh-agent is specified in Xsession.options, the test fails and so the agent is not started. This is in the context of using the i3 window manager, which shouldn't matter except that maybe gnome does stuff on its own that makes the problem not apparent there. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: i3 Date: Sun Aug 22 20:14:49 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: 2021-08-21 20:57:39,784 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.11.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:060d] Subsystem: Dell GK107GLM [Quadro K1100M] [1028:060d] InstallationDate: Installed on 2015-12-17 (2075 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Dell Precision M3800 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-31-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to hirsute on 2021-08-21 (0 days ago) dmi.bios.date: 08/17/2015 dmi.bios.release: 65.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A10 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/17/2015:br65.10:svnDellInc.:pnDellPrecisionM3800:pvrA10:rvnDellInc.:rnDellPrecisionM3800:rvrA10:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Dell Precision M3800 dmi.product.sku: Dell Precision M3800 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.X11.Xsession.d.20x11-common_process-args: 2021-08-22T20:12:04.931804 version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute 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/1940779 Title: has_options missing so ssh-agent doesn't start Status in xorg package in Ubuntu: New Bug description: The file /etc/X11/Xsession.d/20x11-common_process-args is missing the definition of the function has_option() in the 21.04 distribution. As a result, when lightdm starts X11, even though use-ssh-agent is specified in Xsession.options, the test fails and so the agent is not started. This is in the context of using the i3 window manager, which shouldn't matter except that maybe gnome does stuff on its own that makes the problem not apparent there. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: i3 Date: Sun Aug 22 20:14:49 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: 2021-08-21 20:57:39,784 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.11.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical
[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
After two years of waiting on this, and seeing how disappointing the progress has been both in Ubuntu and PulseAudio, I am happy to say that I believe PipeWire is the future and I would hope that Ubuntu moves forward with switching to PipeWire (while keeping PulseAudio as an alternative). I was able to follow these directions to switch to PipeWire and have found it to be acceptable with Bose NC700s and mSBC/HFP: From: https://www.reddit.com/r/pop_os/comments/ofdalv/replaced_pulseaudio_with_pipewire_on_popos_2104_i/h4c5p6u/ # Add ppa for latest build sudo add-apt-repository ppa:pipewire-debian/pipewire-upstream && sudo apt update # Install components sudo apt install gstreamer1.0-pipewire pipewire-media-session libspa-0.2-bluetooth libspa-0.2-jack pipewire pipewire-audio-client-libraries # If you get unmet dependencies, you can run: sudo apt --fix-broken install # Reload new services systemctl --user daemon-reload # Disable PulseAudio service systemctl --user --now disable pulseaudio.service pulseaudio.socket # If you update from previous version of PopOS systemctl --user mask pulseaudio # Enable Pipewire services systemctl --user --now enable pipewire pipewire-pulse # Enable Pipewire media session systemctl --user --now enable pipewire-media-session.service # I ran into an issue with a couple dependencies and needed to do the following before everything worked: sudo apt install libspa-0.2-bluetooth libfdk-aac2 systemctl --user restart pipewire.service pipewire-pulse.service Hope this helps. -- 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: Fix Released 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:
[Desktop-packages] [Bug 1936679] [NEW] ubuntu-drivers --gpgpu is not installing -server packages
Public bug reported: Discovered while testing the ubuntu-drivers-common package in -proposed for bug LP:1898601 While waiting on bionic to deploy for verification, something was bugging me about Focal verification from the other day so I re-deployed a DL380 with 4x T4 GPGPUs with Focal and added u-d-c from proposed. What I missed when verifying the other day was that it actually isn't installing the -server package on my server in gpgpu mode. After chatting a bit with Alberto, --gpgpu is supposed to install the nvidia- driver-VER-server package. Instead, the version in -proposed is actually installing nvidia-driver-VER which is incorrect. Attached is a tarball from a fresh focal install that includes the output when doing 'ubuntu-drivers --gpgpu install' and 'ubuntu-drivers --gpgpu debug' after installing the driver. ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** Attachment added: "ubuntu-drivers-gpgpu-focal-logs.tar" https://bugs.launchpad.net/bugs/1936679/+attachment/5511458/+files/ubuntu-drivers-gpgpu-focal-logs.tar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1936679 Title: ubuntu-drivers --gpgpu is not installing -server packages Status in ubuntu-drivers-common package in Ubuntu: New Bug description: Discovered while testing the ubuntu-drivers-common package in -proposed for bug LP:1898601 While waiting on bionic to deploy for verification, something was bugging me about Focal verification from the other day so I re- deployed a DL380 with 4x T4 GPGPUs with Focal and added u-d-c from proposed. What I missed when verifying the other day was that it actually isn't installing the -server package on my server in gpgpu mode. After chatting a bit with Alberto, --gpgpu is supposed to install the nvidia-driver-VER-server package. Instead, the version in -proposed is actually installing nvidia-driver-VER which is incorrect. Attached is a tarball from a fresh focal install that includes the output when doing 'ubuntu-drivers --gpgpu install' and 'ubuntu-drivers --gpgpu debug' after installing the driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1936679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1898601] Re: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server
** Tags removed: verification-needed-bionic verification-needed-groovy ** Tags added: verification-done-bionic verification-done-groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1898601 Title: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Fix Committed Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Groovy: Fix Committed Bug description: SRU Request [Impact] * ubuntu-drivers installs unnecessary packages when using the "-- gpgpu" argument. Also, it should not depend on alsa-utils, its relevant test should. [Fix] * Passing in "--no-install-recommends" by default with the "--gpgpu" argument will solve the problem. Also, moving the alsa-utils dependency into the test avoids installing an unneeded dependency on servers. [Test Case] * Install ubuntu-drivers-common from -proposed. * Make sure it doesn't pull in alsa-utils. * Install the nvidia driver using "sudo ubuntu-drivers install --gpgpu", and check that the desktop related dependencies are not pulled in. [Regression Risk] Low, since it changes the amount of dependencies we install on servers. +++Update+++ I am in a position where I need to run regression testing using the nVidia drivers on systems configured for GPU compute. This bug prevents me from using ubuntu-drivers to ensure I have the latest Ubuntu Signed drivers. To resolve this, ubuntu-drivers would need to honor --no-install-recommends and not install all those unnecessary desktop environment packages that make no sense on a headless server - When I install the packaged nVidia drivers using --gpgpu, I expect that I am getting compute related GPGPU drivers. Instead, I find that on a fresh Focal installation of Ubuntu Server, I also get a full desktop environment. This sets us up nicely for this bug: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559 because this pulls in gdm3 and a whole host of unnecessary desktop packages but does nothing to mitigate the gdm3 propensity to autosuspend, which makes the server become unresponsive when there is no user activity (even when it's running workloads on the GPGPU, the server can still autosuspend). Additionally, this adds a software stack that causes unnecessary CPU and memory usage on a machine that is meant to run headless and devote all resources to handling GPGPU compute activities. This is gpgpu mode Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: apg aptdaemon aptdaemon-data aspell aspell-en avahi-daemon avahi-utils bluez bubblewrap colord colord-data cracklib-runtime cups-pk-helper dbus-x11 dconf-cli desktop-file-utils dictionaries-common docbook-xml emacsen-common enchant-2 evolution-data-server evolution-data-server-common fprintd gcr gdm3 geoclue-2.0 gir1.2-accountsservice-1.0 gir1.2-atspi-2.0 gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdesktopenums-3.0 gir1.2-gdm-1.0 gir1.2-geoclue-2.0 gir1.2-gnomebluetooth-1.0 gir1.2-gnomedesktop-3.0 gir1.2-graphene-1.0 gir1.2-gweather-3.0 gir1.2-ibus-1.0 gir1.2-mutter-6 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-notify-0.7 gir1.2-polkit-1.0 gir1.2-rsvg-2.0 gir1.2-secret-1 gir1.2-soup-2.4 gir1.2-upowerglib-1.0 gir1.2-vte-2.91 gjs gkbd-capplet gnome-control-center gnome-control-center-data gnome-control-center-faces gnome-desktop3-data gnome-keyring gnome-keyring-pkcs11 gnome-menus gnome-online-accounts gnome-session-bin gnome-session-common gnome-settings-daemon gnome-settings-daemon-common gnome-shell gnome-shell-common gnome-startup-applications gnome-user-docs gstreamer1.0-clutter-3.0 hunspell-en-us ibus ibus-data ibus-gtk ibus-gtk3 iio-sensor-proxy im-config ippusbxd language-selector-gnome libappindicator3-1 libasound2-plugins libaspell15 libavahi-core7 libavahi-glib1 libcamel-1.2-62 libcanberra-gtk3-0 libcanberra-gtk3-module libcanberra-pulse libcheese-gtk25 libclutter-gtk-1.0-0 libcolord-gtk1 libcolorhug2 libcrack2 libdaemon0 libdbusmenu-glib4 libdbusmenu-gtk3-4 libebackend-1.2-10 libebook-1.2-20 libebook-contacts-1.2-3 libecal-2.0-1 libedata-book-1.2-26 libedata-cal-2.0-1 libedataserver-1.2-24 libedataserverui-1.2-2 libenchant-2-2 libexif12 libfontenc1 libfprint-2-2 libgail-common libgail18 libgck-1-0 libgcr-base-3-1 libgcr-ui-3-1 libgd3 libgdata-common libgdata22 libgdm1 libgee-0.8-2 libgeoclue-2-0 libgeocode-glib0 libgjs0g libgles2 libgnome-autoar-0-0 libgnome-bluetooth13 libgnome-desktop-3-19
[Desktop-packages] [Bug 1898601] Re: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server
Also on Groovy, trying to install the -server package fails: $ ubuntu-drivers --gpgpu list This is gpgpu mode ERROR:root:could not open aplay -l Traceback (most recent call last): File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in detect aplay = subprocess.Popen( File "/usr/lib/python3.8/subprocess.py", line 854, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.8/subprocess.py", line 1702, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'aplay' nvidia-driver-460-server, (kernel modules provided by linux-modules-nvidia-460-server-generic) nvidia-driver-460, (kernel modules provided by linux-modules-nvidia-460-generic) nvidia-driver-450-server, (kernel modules provided by linux-modules-nvidia-450-server-generic) ubuntu@torchtusk:~$ sudo ubuntu-drivers --gpgpu install nvidia-driver-460-server |tee -a install-server.log This is gpgpu mode ERROR:root:could not open aplay -l Traceback (most recent call last): File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in detect aplay = subprocess.Popen( File "/usr/lib/python3.8/subprocess.py", line 854, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.8/subprocess.py", line 1702, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'aplay' No drivers found for installation. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1898601 Title: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Fix Committed Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Groovy: Fix Committed Bug description: SRU Request [Impact] * ubuntu-drivers installs unnecessary packages when using the "-- gpgpu" argument. Also, it should not depend on alsa-utils, its relevant test should. [Fix] * Passing in "--no-install-recommends" by default with the "--gpgpu" argument will solve the problem. Also, moving the alsa-utils dependency into the test avoids installing an unneeded dependency on servers. [Test Case] * Install ubuntu-drivers-common from -proposed. * Make sure it doesn't pull in alsa-utils. * Install the nvidia driver using "sudo ubuntu-drivers install --gpgpu", and check that the desktop related dependencies are not pulled in. [Regression Risk] Low, since it changes the amount of dependencies we install on servers. +++Update+++ I am in a position where I need to run regression testing using the nVidia drivers on systems configured for GPU compute. This bug prevents me from using ubuntu-drivers to ensure I have the latest Ubuntu Signed drivers. To resolve this, ubuntu-drivers would need to honor --no-install-recommends and not install all those unnecessary desktop environment packages that make no sense on a headless server - When I install the packaged nVidia drivers using --gpgpu, I expect that I am getting compute related GPGPU drivers. Instead, I find that on a fresh Focal installation of Ubuntu Server, I also get a full desktop environment. This sets us up nicely for this bug: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559 because this pulls in gdm3 and a whole host of unnecessary desktop packages but does nothing to mitigate the gdm3 propensity to autosuspend, which makes the server become unresponsive when there is no user activity (even when it's running workloads on the GPGPU, the server can still autosuspend). Additionally, this adds a software stack that causes unnecessary CPU and memory usage on a machine that is meant to run headless and devote all resources to handling GPGPU compute activities. This is gpgpu mode Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: apg aptdaemon aptdaemon-data aspell aspell-en avahi-daemon avahi-utils bluez bubblewrap colord colord-data cracklib-runtime cups-pk-helper dbus-x11 dconf-cli desktop-file-utils dictionaries-common docbook-xml emacsen-common enchant-2 evolution-data-server evolution-data-server-common fprintd gcr gdm3 geoclue-2.0 gir1.2-accountsservice-1.0 gir1.2-atspi-2.0 gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdesktopenums-3.0 gir1.2-gdm-1.0 gir1.2-geoclue-2.0 gir1.2-gnomebluetooth-1.0 gir1.2-gnomedesktop-3.0 gir1.2-graphene-1.0 gir1.2-gweather-3.0
[Desktop-packages] [Bug 1898601] Re: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server
Groovy: $ ubuntu-drivers --gpgpu list This is gpgpu mode ERROR:root:could not open aplay -l Traceback (most recent call last): File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in detect aplay = subprocess.Popen( File "/usr/lib/python3.8/subprocess.py", line 854, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.8/subprocess.py", line 1702, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'aplay' nvidia-driver-460-server, (kernel modules provided by linux-modules-nvidia-460-server-generic) nvidia-driver-460, (kernel modules provided by linux-modules-nvidia-460-generic) nvidia-driver-450-server, (kernel modules provided by linux-modules-nvidia-450-server-generic) This is gpgpu mode Reading package lists... Building dependency tree... Reading state information... The following additional packages will be installed: libfontenc1 libice6 libjansson4 libnvidia-cfg1-460 libnvidia-common-460 libnvidia-compute-460 libnvidia-decode-460 libnvidia-encode-460 libnvidia-extra-460 libnvidia-fbc1-460 libnvidia-gl-460 libnvidia-ifr1-460 libsm6 libvdpau1 libxaw7 libxfont2 libxkbfile1 libxmu6 libxpm4 libxt6 linux-image-5.8.0-61-generic linux-modules-5.8.0-61-generic linux-modules-nvidia-460-5.8.0-61-generic linux-objects-nvidia-460-5.8.0-61-generic linux-signatures-nvidia-5.8.0-61-generic mesa-vdpau-drivers nvidia-compute-utils-460 nvidia-kernel-common-460 nvidia-kernel-source-460 nvidia-prime nvidia-settings nvidia-utils-460 pkg-config policykit-1-gnome screen-resolution-extra vdpau-driver-all x11-xkb-utils xfonts-base xfonts-encodings xfonts-utils xserver-common xserver-xorg-core xserver-xorg-video-nvidia-460 Suggested packages: fdutils linux-doc | linux-source-5.8.0 linux-tools linux-headers-5.8.0-61-generic libvdpau-va-gl1 xfs | xserver xfonts-100dpi | xfonts-75dpi xfonts-scalable Recommended packages: libnvidia-compute-460:i386 libnvidia-decode-460:i386 libnvidia-encode-460:i386 libnvidia-ifr1-460:i386 libnvidia-fbc1-460:i386 libnvidia-gl-460:i386 The following NEW packages will be installed: libfontenc1 libice6 libjansson4 libnvidia-cfg1-460 libnvidia-common-460 libnvidia-compute-460 libnvidia-decode-460 libnvidia-encode-460 libnvidia-extra-460 libnvidia-fbc1-460 libnvidia-gl-460 libnvidia-ifr1-460 libsm6 libvdpau1 libxaw7 libxfont2 libxkbfile1 libxmu6 libxpm4 libxt6 linux-image-5.8.0-61-generic linux-modules-5.8.0-61-generic linux-modules-nvidia-460-5.8.0-61-generic linux-modules-nvidia-460-generic linux-objects-nvidia-460-5.8.0-61-generic linux-signatures-nvidia-5.8.0-61-generic mesa-vdpau-drivers nvidia-compute-utils-460 nvidia-driver-460 nvidia-kernel-common-460 nvidia-kernel-source-460 nvidia-prime nvidia-settings nvidia-utils-460 pkg-config policykit-1-gnome screen-resolution-extra vdpau-driver-all x11-xkb-utils xfonts-base xfonts-encodings xfonts-utils xserver-common xserver-xorg-core xserver-xorg-video-nvidia-460 0 upgraded, 45 newly installed, 0 to remove and 38 not upgraded. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1898601 Title: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Fix Committed Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Groovy: Fix Committed Bug description: SRU Request [Impact] * ubuntu-drivers installs unnecessary packages when using the "-- gpgpu" argument. Also, it should not depend on alsa-utils, its relevant test should. [Fix] * Passing in "--no-install-recommends" by default with the "--gpgpu" argument will solve the problem. Also, moving the alsa-utils dependency into the test avoids installing an unneeded dependency on servers. [Test Case] * Install ubuntu-drivers-common from -proposed. * Make sure it doesn't pull in alsa-utils. * Install the nvidia driver using "sudo ubuntu-drivers install --gpgpu", and check that the desktop related dependencies are not pulled in. [Regression Risk] Low, since it changes the amount of dependencies we install on servers. +++Update+++ I am in a position where I need to run regression testing using the nVidia drivers on systems configured for GPU compute. This bug prevents me from using ubuntu-drivers to ensure I have the latest Ubuntu Signed drivers. To resolve this, ubuntu-drivers would need to honor --no-install-recommends and not install all those unnecessary desktop environment packages that make no sense on a headless
[Desktop-packages] [Bug 1898601] Re: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server
Tested Bionic, and the spirit of this bug is resolved, I think? However, it couldn't be completely verified since ubuntu-drivers doesn't install the -server package when --gpgpu is being called: This is gpgpu mode Reading package lists... Building dependency tree... Reading state information... The following additional packages will be installed: libfontenc1 libice6 libjansson4 libnvidia-cfg1-460 libnvidia-common-460 libnvidia-compute-460 libnvidia-decode-460 libnvidia-encode-460 libnvidia-extra-460 libnvidia-fbc1-460 libnvidia-gl-460 libnvidia-ifr1-460 libsm6 libvdpau1 libxaw7 libxfont2 libxkbfile1 libxmu6 libxnvctrl0 libxpm4 libxt6 mesa-vdpau-drivers nvidia-compute-utils-460 nvidia-kernel-common-460 nvidia-kernel-source-460 nvidia-prime nvidia-settings nvidia-utils-460 pkg-config policykit-1-gnome screen-resolution-extra vdpau-driver-all x11-xkb-utils xfonts-base xfonts-encodings xfonts-utils xserver-common xserver-xorg-core-hwe-18.04 xserver-xorg-video-nvidia-460 Suggested packages: libvdpau-va-gl1 nvidia-vdpau-driver nvidia-legacy-340xx-vdpau-driver xfs | xserver xfonts-100dpi | xfonts-75dpi xfonts-scalable Recommended packages: libnvidia-compute-460:i386 libnvidia-decode-460:i386 libnvidia-encode-460:i386 libnvidia-ifr1-460:i386 libnvidia-fbc1-460:i386 libnvidia-gl-460:i386 The following NEW packages will be installed: libfontenc1 libice6 libjansson4 libnvidia-cfg1-460 libnvidia-common-460 libnvidia-compute-460 libnvidia-decode-460 libnvidia-encode-460 libnvidia-extra-460 libnvidia-fbc1-460 libnvidia-gl-460 libnvidia-ifr1-460 libsm6 libvdpau1 libxaw7 libxfont2 libxkbfile1 libxmu6 libxnvctrl0 libxpm4 libxt6 mesa-vdpau-drivers nvidia-compute-utils-460 nvidia-dkms-460 nvidia-driver-460 nvidia-kernel-common-460 nvidia-kernel-source-460 nvidia-prime nvidia-settings nvidia-utils-460 pkg-config policykit-1-gnome screen-resolution-extra vdpau-driver-all x11-xkb-utils xfonts-base xfonts-encodings xfonts-utils xserver-common xserver-xorg-core-hwe-18.04 xserver-xorg-video-nvidia-460 0 upgraded, 41 newly installed, 0 to remove and 0 not upgraded. I'm not sure if that is correct. When I install manually, I look for these: linux-modules-nvidia-$NVDRV_MJR_VER-server-generic nvidia-kernel-common-$NVDRV_MJR_VER-server datacenter-gpu-manager libnvidia-nscq-$NVDRV_MJR_VER ca-certificates curl software-properties-common nvidia-container-toolkit nvidia-docker2 unzip libgfortran4 swig autotools-dev bison gfortran automake libnl-route-3-200 quilt tcl tk libnl-route-3-dev chrpath m4 debhelper dpatch libltdl-dev libnl-3-dev graphviz flex autoconf sosreport nvidia-utils-$NVDRV_MJR_VER-server nvidia-compute-utils-$NVDRV_MJR_VER-server libnvidia-cfg1-$NVDRV_MJR_VER-server which is the minimal set to run the nVidia GPGPU tests. What I don't see being installed on Bionic when I run 'ubuntu-drivers --gpgpu install' is the -server package. I haven't run this on Bionic in ages, but ISTR previously it DID install the -server package. I'm not sure if the *compute* packages installed are being pulled in due to a -server package, or because --gpgpu was called. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1898601 Title: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Fix Committed Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Groovy: Fix Committed Bug description: SRU Request [Impact] * ubuntu-drivers installs unnecessary packages when using the "-- gpgpu" argument. Also, it should not depend on alsa-utils, its relevant test should. [Fix] * Passing in "--no-install-recommends" by default with the "--gpgpu" argument will solve the problem. Also, moving the alsa-utils dependency into the test avoids installing an unneeded dependency on servers. [Test Case] * Install ubuntu-drivers-common from -proposed. * Make sure it doesn't pull in alsa-utils. * Install the nvidia driver using "sudo ubuntu-drivers install --gpgpu", and check that the desktop related dependencies are not pulled in. [Regression Risk] Low, since it changes the amount of dependencies we install on servers. +++Update+++ I am in a position where I need to run regression testing using the nVidia drivers on systems configured for GPU compute. This bug prevents me from using ubuntu-drivers to ensure I have the latest Ubuntu Signed drivers. To resolve this, ubuntu-drivers would need to honor --no-install-recommends and not install all those unnecessary desktop environment packages that make no sense on a headless server
[Desktop-packages] [Bug 1898601] Re: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1898601 Title: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Fix Committed Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in ubuntu-drivers-common source package in Groovy: Fix Committed Bug description: SRU Request [Impact] * ubuntu-drivers installs unnecessary packages when using the "-- gpgpu" argument. Also, it should not depend on alsa-utils, its relevant test should. [Fix] * Passing in "--no-install-recommends" by default with the "--gpgpu" argument will solve the problem. Also, moving the alsa-utils dependency into the test avoids installing an unneeded dependency on servers. [Test Case] * Install ubuntu-drivers-common from -proposed. * Make sure it doesn't pull in alsa-utils. * Install the nvidia driver using "sudo ubuntu-drivers install --gpgpu", and check that the desktop related dependencies are not pulled in. [Regression Risk] Low, since it changes the amount of dependencies we install on servers. +++Update+++ I am in a position where I need to run regression testing using the nVidia drivers on systems configured for GPU compute. This bug prevents me from using ubuntu-drivers to ensure I have the latest Ubuntu Signed drivers. To resolve this, ubuntu-drivers would need to honor --no-install-recommends and not install all those unnecessary desktop environment packages that make no sense on a headless server - When I install the packaged nVidia drivers using --gpgpu, I expect that I am getting compute related GPGPU drivers. Instead, I find that on a fresh Focal installation of Ubuntu Server, I also get a full desktop environment. This sets us up nicely for this bug: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559 because this pulls in gdm3 and a whole host of unnecessary desktop packages but does nothing to mitigate the gdm3 propensity to autosuspend, which makes the server become unresponsive when there is no user activity (even when it's running workloads on the GPGPU, the server can still autosuspend). Additionally, this adds a software stack that causes unnecessary CPU and memory usage on a machine that is meant to run headless and devote all resources to handling GPGPU compute activities. This is gpgpu mode Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: apg aptdaemon aptdaemon-data aspell aspell-en avahi-daemon avahi-utils bluez bubblewrap colord colord-data cracklib-runtime cups-pk-helper dbus-x11 dconf-cli desktop-file-utils dictionaries-common docbook-xml emacsen-common enchant-2 evolution-data-server evolution-data-server-common fprintd gcr gdm3 geoclue-2.0 gir1.2-accountsservice-1.0 gir1.2-atspi-2.0 gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdesktopenums-3.0 gir1.2-gdm-1.0 gir1.2-geoclue-2.0 gir1.2-gnomebluetooth-1.0 gir1.2-gnomedesktop-3.0 gir1.2-graphene-1.0 gir1.2-gweather-3.0 gir1.2-ibus-1.0 gir1.2-mutter-6 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-notify-0.7 gir1.2-polkit-1.0 gir1.2-rsvg-2.0 gir1.2-secret-1 gir1.2-soup-2.4 gir1.2-upowerglib-1.0 gir1.2-vte-2.91 gjs gkbd-capplet gnome-control-center gnome-control-center-data gnome-control-center-faces gnome-desktop3-data gnome-keyring gnome-keyring-pkcs11 gnome-menus gnome-online-accounts gnome-session-bin gnome-session-common gnome-settings-daemon gnome-settings-daemon-common gnome-shell gnome-shell-common gnome-startup-applications gnome-user-docs gstreamer1.0-clutter-3.0 hunspell-en-us ibus ibus-data ibus-gtk ibus-gtk3 iio-sensor-proxy im-config ippusbxd language-selector-gnome libappindicator3-1 libasound2-plugins libaspell15 libavahi-core7 libavahi-glib1 libcamel-1.2-62 libcanberra-gtk3-0 libcanberra-gtk3-module libcanberra-pulse libcheese-gtk25 libclutter-gtk-1.0-0 libcolord-gtk1 libcolorhug2 libcrack2 libdaemon0 libdbusmenu-glib4 libdbusmenu-gtk3-4 libebackend-1.2-10 libebook-1.2-20 libebook-contacts-1.2-3 libecal-2.0-1 libedata-book-1.2-26 libedata-cal-2.0-1 libedataserver-1.2-24 libedataserverui-1.2-2 libenchant-2-2 libexif12 libfontenc1 libfprint-2-2 libgail-common libgail18 libgck-1-0 libgcr-base-3-1 libgcr-ui-3-1 libgd3 libgdata-common libgdata22 libgdm1 libgee-0.8-2 libgeoclue-2-0 libgeocode-glib0 libgjs0g libgles2 libgnome-autoar-0-0 libgnome-bluetooth13 libgnome-desktop-3-19 libgnomekbd-common libgnomekbd8 libgoa-1.0-0b libgoa-1.0-common
[Desktop-packages] [Bug 1935070] [NEW] Traceback during 'ubuntu-drivers list'
Public bug reported: ubuntu@doubletusk:~$ sudo ubuntu-drivers list ERROR:root:could not open aplay -l Traceback (most recent call last): File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in detect aplay = subprocess.Popen( File "/usr/lib/python3.8/subprocess.py", line 858, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.8/subprocess.py", line 1704, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'aplay' nvidia-driver-418-server, (kernel modules provided by nvidia-dkms-418-server) nvidia-driver-470, (kernel modules provided by nvidia-dkms-470) nvidia-driver-460-server, (kernel modules provided by nvidia-dkms-460-server) nvidia-driver-465, (kernel modules provided by nvidia-dkms-465) nvidia-driver-450-server, (kernel modules provided by nvidia-dkms-450-server) nvidia-driver-460, (kernel modules provided by nvidia-dkms-460) ubuntu@doubletusk:~$ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.9.0~0.20.04.1 Candidate: 1:0.9.0~0.20.04.1 Version table: *** 1:0.9.0~0.20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:0.8.6.5~0.20.04.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 1:0.8.1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ubuntu@doubletusk:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1935070 Title: Traceback during 'ubuntu-drivers list' Status in ubuntu-drivers-common package in Ubuntu: New Bug description: ubuntu@doubletusk:~$ sudo ubuntu-drivers list ERROR:root:could not open aplay -l Traceback (most recent call last): File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in detect aplay = subprocess.Popen( File "/usr/lib/python3.8/subprocess.py", line 858, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.8/subprocess.py", line 1704, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'aplay' nvidia-driver-418-server, (kernel modules provided by nvidia-dkms-418-server) nvidia-driver-470, (kernel modules provided by nvidia-dkms-470) nvidia-driver-460-server, (kernel modules provided by nvidia-dkms-460-server) nvidia-driver-465, (kernel modules provided by nvidia-dkms-465) nvidia-driver-450-server, (kernel modules provided by nvidia-dkms-450-server) nvidia-driver-460, (kernel modules provided by nvidia-dkms-460) ubuntu@doubletusk:~$ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.9.0~0.20.04.1 Candidate: 1:0.9.0~0.20.04.1 Version table: *** 1:0.9.0~0.20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:0.8.6.5~0.20.04.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 1:0.8.1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ubuntu@doubletusk:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1935070/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1898601] Re: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server
dpuble post -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1898601 Title: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Triaged Status in ubuntu-drivers-common source package in Focal: Triaged Status in ubuntu-drivers-common source package in Groovy: Triaged Bug description: +++Update+++ I am in a position where I need to run regression testing using the nVidia drivers on systems configured for GPU compute. This bug prevents me from using ubuntu-drivers to ensure I have the latest Ubuntu Signed drivers. To resolve this, ubuntu-drivers would need to honor --no-install-recommends and not install all those unnecessary desktop environment packages that make no sense on a headless server - When I install the packaged nVidia drivers using --gpgpu, I expect that I am getting compute related GPGPU drivers. Instead, I find that on a fresh Focal installation of Ubuntu Server, I also get a full desktop environment. This sets us up nicely for this bug: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559 because this pulls in gdm3 and a whole host of unnecessary desktop packages but does nothing to mitigate the gdm3 propensity to autosuspend, which makes the server become unresponsive when there is no user activity (even when it's running workloads on the GPGPU, the server can still autosuspend). Additionally, this adds a software stack that causes unnecessary CPU and memory usage on a machine that is meant to run headless and devote all resources to handling GPGPU compute activities. This is gpgpu mode Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: apg aptdaemon aptdaemon-data aspell aspell-en avahi-daemon avahi-utils bluez bubblewrap colord colord-data cracklib-runtime cups-pk-helper dbus-x11 dconf-cli desktop-file-utils dictionaries-common docbook-xml emacsen-common enchant-2 evolution-data-server evolution-data-server-common fprintd gcr gdm3 geoclue-2.0 gir1.2-accountsservice-1.0 gir1.2-atspi-2.0 gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdesktopenums-3.0 gir1.2-gdm-1.0 gir1.2-geoclue-2.0 gir1.2-gnomebluetooth-1.0 gir1.2-gnomedesktop-3.0 gir1.2-graphene-1.0 gir1.2-gweather-3.0 gir1.2-ibus-1.0 gir1.2-mutter-6 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-notify-0.7 gir1.2-polkit-1.0 gir1.2-rsvg-2.0 gir1.2-secret-1 gir1.2-soup-2.4 gir1.2-upowerglib-1.0 gir1.2-vte-2.91 gjs gkbd-capplet gnome-control-center gnome-control-center-data gnome-control-center-faces gnome-desktop3-data gnome-keyring gnome-keyring-pkcs11 gnome-menus gnome-online-accounts gnome-session-bin gnome-session-common gnome-settings-daemon gnome-settings-daemon-common gnome-shell gnome-shell-common gnome-startup-applications gnome-user-docs gstreamer1.0-clutter-3.0 hunspell-en-us ibus ibus-data ibus-gtk ibus-gtk3 iio-sensor-proxy im-config ippusbxd language-selector-gnome libappindicator3-1 libasound2-plugins libaspell15 libavahi-core7 libavahi-glib1 libcamel-1.2-62 libcanberra-gtk3-0 libcanberra-gtk3-module libcanberra-pulse libcheese-gtk25 libclutter-gtk-1.0-0 libcolord-gtk1 libcolorhug2 libcrack2 libdaemon0 libdbusmenu-glib4 libdbusmenu-gtk3-4 libebackend-1.2-10 libebook-1.2-20 libebook-contacts-1.2-3 libecal-2.0-1 libedata-book-1.2-26 libedata-cal-2.0-1 libedataserver-1.2-24 libedataserverui-1.2-2 libenchant-2-2 libexif12 libfontenc1 libfprint-2-2 libgail-common libgail18 libgck-1-0 libgcr-base-3-1 libgcr-ui-3-1 libgd3 libgdata-common libgdata22 libgdm1 libgee-0.8-2 libgeoclue-2-0 libgeocode-glib0 libgjs0g libgles2 libgnome-autoar-0-0 libgnome-bluetooth13 libgnome-desktop-3-19 libgnomekbd-common libgnomekbd8 libgoa-1.0-0b libgoa-1.0-common libgoa-backend-1.0-1 libgphoto2-6 libgphoto2-l10n libgphoto2-port12 libgsound0 libgssdp-1.2-0 libgtk2.0-0 libgtk2.0-bin libgtk2.0-common libgtop-2.0-11 libgtop2-common libgupnp-1.2-0 libgupnp-av-1.0-2 libgupnp-dlna-2.0-3 libgweather-3-16 libgweather-common libharfbuzz-icu0 libhunspell-1.7-0 libhyphen0 libibus-1.0-5 libical3 libice6 libieee1284-3 libimobiledevice6 libjavascriptcoregtk-4.0-18 libldb2 libmediaart-2.0-0 libmozjs-68-0 libmutter-6-0 libnma0 libnotify4 libnss-mdns libnvidia-cfg1-435 libnvidia-common-435 libnvidia-compute-435 libnvidia-decode-435 libnvidia-encode-435 libnvidia-fbc1-435 libnvidia-gl-435 libnvidia-ifr1-435 libopenjp2-7 libpam-fprintd libpam-gnome-keyring libphonenumber7 libplist3 libprotobuf17 libpulse-mainloop-glib0 libpulsedsp libpwquality-common libpwquality1 librygel-core-2.6-2 librygel-db-2.6-2
[Desktop-packages] [Bug 1898601] Re: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server
When can this be finally pulled back at least as far as Focal? We are not going to be doing nVidia testing on Bionic, so that task can be dropped I think, unless it's worthwhile, but for Focal - Hirsute, this would be very helpful to cut down on the amount of stuff being installed, as well as speed up installation time. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1898601 Title: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Triaged Status in ubuntu-drivers-common source package in Focal: Triaged Status in ubuntu-drivers-common source package in Groovy: Triaged Bug description: +++Update+++ I am in a position where I need to run regression testing using the nVidia drivers on systems configured for GPU compute. This bug prevents me from using ubuntu-drivers to ensure I have the latest Ubuntu Signed drivers. To resolve this, ubuntu-drivers would need to honor --no-install-recommends and not install all those unnecessary desktop environment packages that make no sense on a headless server - When I install the packaged nVidia drivers using --gpgpu, I expect that I am getting compute related GPGPU drivers. Instead, I find that on a fresh Focal installation of Ubuntu Server, I also get a full desktop environment. This sets us up nicely for this bug: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559 because this pulls in gdm3 and a whole host of unnecessary desktop packages but does nothing to mitigate the gdm3 propensity to autosuspend, which makes the server become unresponsive when there is no user activity (even when it's running workloads on the GPGPU, the server can still autosuspend). Additionally, this adds a software stack that causes unnecessary CPU and memory usage on a machine that is meant to run headless and devote all resources to handling GPGPU compute activities. This is gpgpu mode Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: apg aptdaemon aptdaemon-data aspell aspell-en avahi-daemon avahi-utils bluez bubblewrap colord colord-data cracklib-runtime cups-pk-helper dbus-x11 dconf-cli desktop-file-utils dictionaries-common docbook-xml emacsen-common enchant-2 evolution-data-server evolution-data-server-common fprintd gcr gdm3 geoclue-2.0 gir1.2-accountsservice-1.0 gir1.2-atspi-2.0 gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdesktopenums-3.0 gir1.2-gdm-1.0 gir1.2-geoclue-2.0 gir1.2-gnomebluetooth-1.0 gir1.2-gnomedesktop-3.0 gir1.2-graphene-1.0 gir1.2-gweather-3.0 gir1.2-ibus-1.0 gir1.2-mutter-6 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-notify-0.7 gir1.2-polkit-1.0 gir1.2-rsvg-2.0 gir1.2-secret-1 gir1.2-soup-2.4 gir1.2-upowerglib-1.0 gir1.2-vte-2.91 gjs gkbd-capplet gnome-control-center gnome-control-center-data gnome-control-center-faces gnome-desktop3-data gnome-keyring gnome-keyring-pkcs11 gnome-menus gnome-online-accounts gnome-session-bin gnome-session-common gnome-settings-daemon gnome-settings-daemon-common gnome-shell gnome-shell-common gnome-startup-applications gnome-user-docs gstreamer1.0-clutter-3.0 hunspell-en-us ibus ibus-data ibus-gtk ibus-gtk3 iio-sensor-proxy im-config ippusbxd language-selector-gnome libappindicator3-1 libasound2-plugins libaspell15 libavahi-core7 libavahi-glib1 libcamel-1.2-62 libcanberra-gtk3-0 libcanberra-gtk3-module libcanberra-pulse libcheese-gtk25 libclutter-gtk-1.0-0 libcolord-gtk1 libcolorhug2 libcrack2 libdaemon0 libdbusmenu-glib4 libdbusmenu-gtk3-4 libebackend-1.2-10 libebook-1.2-20 libebook-contacts-1.2-3 libecal-2.0-1 libedata-book-1.2-26 libedata-cal-2.0-1 libedataserver-1.2-24 libedataserverui-1.2-2 libenchant-2-2 libexif12 libfontenc1 libfprint-2-2 libgail-common libgail18 libgck-1-0 libgcr-base-3-1 libgcr-ui-3-1 libgd3 libgdata-common libgdata22 libgdm1 libgee-0.8-2 libgeoclue-2-0 libgeocode-glib0 libgjs0g libgles2 libgnome-autoar-0-0 libgnome-bluetooth13 libgnome-desktop-3-19 libgnomekbd-common libgnomekbd8 libgoa-1.0-0b libgoa-1.0-common libgoa-backend-1.0-1 libgphoto2-6 libgphoto2-l10n libgphoto2-port12 libgsound0 libgssdp-1.2-0 libgtk2.0-0 libgtk2.0-bin libgtk2.0-common libgtop-2.0-11 libgtop2-common libgupnp-1.2-0 libgupnp-av-1.0-2 libgupnp-dlna-2.0-3 libgweather-3-16 libgweather-common libharfbuzz-icu0 libhunspell-1.7-0 libhyphen0 libibus-1.0-5 libical3 libice6 libieee1284-3 libimobiledevice6 libjavascriptcoregtk-4.0-18 libldb2 libmediaart-2.0-0 libmozjs-68-0 libmutter-6-0 libnma0 libnotify4 libnss-mdns libnvidia-cfg1-435 libnvidia-common-435 libnvidia-compute-435
[Desktop-packages] [Bug 1933878] [NEW] Traceback when trying to install drivers as normal user
Public bug reported:
Forgot to use sudo and discovered an ugly traceback.
ubuntu@doubletusk:~$ ubuntu-drivers --gpgpu install
This is gpgpu mode
Traceback (most recent call last):
File "/usr/bin/ubuntu-drivers", line 480, in
greet()
File "/usr/lib/python3/dist-packages/click/core.py", line 829, in __call__
return self.main(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 782, in main
rv = self.invoke(ctx)
File "/usr/lib/python3/dist-packages/click/core.py", line 1259, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/lib/python3/dist-packages/click/core.py", line 1066, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/usr/lib/python3/dist-packages/click/core.py", line 610, in invoke
return callback(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/decorators.py", line 73, in
new_func
return ctx.invoke(f, obj, *args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 610, in invoke
return callback(*args, **kwargs)
File "/usr/bin/ubuntu-drivers", line 399, in install
command_install(config)
File "/usr/bin/ubuntu-drivers", line 160, in command_install
pm_fd = open('/run/nvidia_runtimepm_supported', 'w')
PermissionError: [Errno 13] Permission denied: '/run/nvidia_runtimepm_supported'
This is because I forgot to use sudo to do the install
ubuntu-drivers can do somethings as a non-privileged driver but other
things (install) requires root escalation.
ubuntu-drivers should either always require root via sudo, or "ubuntu-
drivers install" should do a user check and exit with a simple helpful
message like "You must use sudo when installing drivers".
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubuntu-drivers-common 1:0.8.6.3~0.20.10.1
ProcVersionSignature: User Name 5.8.0-60.67-generic 5.8.18
Uname: Linux 5.8.0-60-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu50.7
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Jun 28 20:06:09 2021
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-drivers-common
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: ubuntu-drivers-common (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug groovy uec-images
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1933878
Title:
Traceback when trying to install drivers as normal user
Status in ubuntu-drivers-common package in Ubuntu:
New
Bug description:
Forgot to use sudo and discovered an ugly traceback.
ubuntu@doubletusk:~$ ubuntu-drivers --gpgpu install
This is gpgpu mode
Traceback (most recent call last):
File "/usr/bin/ubuntu-drivers", line 480, in
greet()
File "/usr/lib/python3/dist-packages/click/core.py", line 829, in __call__
return self.main(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 782, in main
rv = self.invoke(ctx)
File "/usr/lib/python3/dist-packages/click/core.py", line 1259, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/lib/python3/dist-packages/click/core.py", line 1066, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/usr/lib/python3/dist-packages/click/core.py", line 610, in invoke
return callback(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/decorators.py", line 73, in
new_func
return ctx.invoke(f, obj, *args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 610, in invoke
return callback(*args, **kwargs)
File "/usr/bin/ubuntu-drivers", line 399, in install
command_install(config)
File "/usr/bin/ubuntu-drivers", line 160, in command_install
pm_fd = open('/run/nvidia_runtimepm_supported', 'w')
PermissionError: [Errno 13] Permission denied:
'/run/nvidia_runtimepm_supported'
This is because I forgot to use sudo to do the install
ubuntu-drivers can do somethings as a non-privileged driver but other
things (install) requires root escalation.
ubuntu-drivers should either always require root via sudo, or "ubuntu-
drivers install" should do a user check and exit with a simple helpful
message like "You must use sudo when installing drivers".
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubuntu-drivers-common 1:0.8.6.3~0.20.10.1
ProcVersionSignature: User Name 5.8.0-60.67-generic 5.8.18
Uname: Linux 5.8.0-60-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu50.7
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Jun 28 20:06:09 2021
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
[Desktop-packages] [Bug 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)
I noticed this issue with Kubuntu (Plasma) host and Ubuntu (GNOME) guest. I thought I was the only one affected since this makes almost impossible to use VMs with GUI (desktop). Not that you wouldn't be able to run them but that you realize that you use Ctrl+c/Ctrl+v so often that when it doesn't work 100% it sooo bad experience that you rather not to use VMs at all. And VirtualBox is not an answer ;-). Btw. Windows 10 guest is all right. Thank you Christian for asking and investigating. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/1872527 Title: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests) Status in qemu package in Ubuntu: Invalid Status in spice package in Ubuntu: Invalid Status in spice-gtk package in Ubuntu: Fix Released Status in spice-protocol package in Ubuntu: Fix Released Status in spice-vdagent package in Ubuntu: Fix Released Status in virt-manager package in Ubuntu: Invalid Status in spice-gtk source package in Focal: Triaged Status in spice-protocol source package in Focal: Triaged Status in spice-vdagent source package in Focal: Invalid Status in spice-vdagent package in Debian: Fix Released Status in spice package in Fedora: Unknown Bug description: https://gitlab.freedesktop.org/spice/linux/vd_agent/issues/9 --- I'm testing Ubuntu 20.04 LTS (Focal Fossa) Beta. I installed Kubuntu 20.04 and virt-manager as I did many times on Ubuntu 18.04. Unfortunatelly when I run a VM (QEMU-KVM, libvirt, libspice-server1 and spice-vdagent) with another Kubuntu 20.04 guest or with Ubuntu 20.04 guest then clipboard doesn't work right. To test it, please install Kubuntu 20.04 and then install Kubuntu / Ubuntu 20.04 as VM (guest). Open some simple text editor and start Ctrl + C and Ctrl + V plain text. 90% of time it will work and 10% of time it won't. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: virt-manager 1:2.2.1-3ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 13 15:02:22 2020 InstallationDate: Installed on 2020-04-09 (4 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: virt-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1872527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1898601] Re: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server
** Description changed: + +++Update+++ + I am in a position where I need to run regression testing using the nVidia drivers on systems configured for GPU compute. This bug prevents me from using ubuntu-drivers to ensure I have the latest Ubuntu Signed drivers. + + To resolve this, ubuntu-drivers would need to honor --no-install-recommends and not install all those unnecessary desktop environment packages that make no sense on a headless server + - + When I install the packaged nVidia drivers using --gpgpu, I expect that I am getting compute related GPGPU drivers. Instead, I find that on a fresh Focal installation of Ubuntu Server, I also get a full desktop environment. This sets us up nicely for this bug: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559 because this pulls in gdm3 and a whole host of unnecessary desktop packages but does nothing to mitigate the gdm3 propensity to autosuspend, which makes the server become unresponsive when there is no user activity (even when it's running workloads on the GPGPU, the server can still autosuspend). Additionally, this adds a software stack that causes unnecessary CPU and memory usage on a machine that is meant to run headless and devote all resources to handling GPGPU compute activities. - This is gpgpu mode - Reading package lists... Done - Building dependency tree - Reading state information... Done - The following additional packages will be installed: - apg aptdaemon aptdaemon-data aspell aspell-en avahi-daemon avahi-utils bluez bubblewrap colord colord-data cracklib-runtime cups-pk-helper dbus-x11 dconf-cli desktop-file-utils dictionaries-common docbook-xml emacsen-common enchant-2 - evolution-data-server evolution-data-server-common fprintd gcr gdm3 geoclue-2.0 gir1.2-accountsservice-1.0 gir1.2-atspi-2.0 gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdesktopenums-3.0 gir1.2-gdm-1.0 gir1.2-geoclue-2.0 gir1.2-gnomebluetooth-1.0 - gir1.2-gnomedesktop-3.0 gir1.2-graphene-1.0 gir1.2-gweather-3.0 gir1.2-ibus-1.0 gir1.2-mutter-6 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-notify-0.7 gir1.2-polkit-1.0 gir1.2-rsvg-2.0 gir1.2-secret-1 gir1.2-soup-2.4 gir1.2-upowerglib-1.0 - gir1.2-vte-2.91 gjs gkbd-capplet gnome-control-center gnome-control-center-data gnome-control-center-faces gnome-desktop3-data gnome-keyring gnome-keyring-pkcs11 gnome-menus gnome-online-accounts gnome-session-bin gnome-session-common - gnome-settings-daemon gnome-settings-daemon-common gnome-shell gnome-shell-common gnome-startup-applications gnome-user-docs gstreamer1.0-clutter-3.0 hunspell-en-us ibus ibus-data ibus-gtk ibus-gtk3 iio-sensor-proxy im-config ippusbxd - language-selector-gnome libappindicator3-1 libasound2-plugins libaspell15 libavahi-core7 libavahi-glib1 libcamel-1.2-62 libcanberra-gtk3-0 libcanberra-gtk3-module libcanberra-pulse libcheese-gtk25 libclutter-gtk-1.0-0 libcolord-gtk1 - libcolorhug2 libcrack2 libdaemon0 libdbusmenu-glib4 libdbusmenu-gtk3-4 libebackend-1.2-10 libebook-1.2-20 libebook-contacts-1.2-3 libecal-2.0-1 libedata-book-1.2-26 libedata-cal-2.0-1 libedataserver-1.2-24 libedataserverui-1.2-2 - libenchant-2-2 libexif12 libfontenc1 libfprint-2-2 libgail-common libgail18 libgck-1-0 libgcr-base-3-1 libgcr-ui-3-1 libgd3 libgdata-common libgdata22 libgdm1 libgee-0.8-2 libgeoclue-2-0 libgeocode-glib0 libgjs0g libgles2 - libgnome-autoar-0-0 libgnome-bluetooth13 libgnome-desktop-3-19 libgnomekbd-common libgnomekbd8 libgoa-1.0-0b libgoa-1.0-common libgoa-backend-1.0-1 libgphoto2-6 libgphoto2-l10n libgphoto2-port12 libgsound0 libgssdp-1.2-0 libgtk2.0-0 - libgtk2.0-bin libgtk2.0-common libgtop-2.0-11 libgtop2-common libgupnp-1.2-0 libgupnp-av-1.0-2 libgupnp-dlna-2.0-3 libgweather-3-16 libgweather-common libharfbuzz-icu0 libhunspell-1.7-0 libhyphen0 libibus-1.0-5 libical3 libice6 - libieee1284-3 libimobiledevice6 libjavascriptcoregtk-4.0-18 libldb2 libmediaart-2.0-0 libmozjs-68-0 libmutter-6-0 libnma0 libnotify4 libnss-mdns libnvidia-cfg1-435 libnvidia-common-435 libnvidia-compute-435 libnvidia-decode-435 - libnvidia-encode-435 libnvidia-fbc1-435 libnvidia-gl-435 libnvidia-ifr1-435 libopenjp2-7 libpam-fprintd libpam-gnome-keyring libphonenumber7 libplist3 libprotobuf17 libpulse-mainloop-glib0 libpulsedsp libpwquality-common libpwquality1 - librygel-core-2.6-2 librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2 libsane libsane-common libsbc1 libsecret-1-0 libsecret-common libsm6 libsmbclient libsnapd-glib1 libsoxr0
[Desktop-packages] [Bug 1920232] Re: ubuntu-drivers --gpgpu installs hundreds of unnecessary and unwanted packages
*** This bug is a duplicate of bug 1898601 *** https://bugs.launchpad.net/bugs/1898601 ** This bug has been marked a duplicate of bug 1898601 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1920232 Title: ubuntu-drivers --gpgpu installs hundreds of unnecessary and unwanted packages Status in ubuntu-drivers-common package in Ubuntu: New Bug description: when I use --gpgpu mode to install gpgpu drivers using ubuntu-drivers, I want ONLY apropriate drivers for GPU compute functions. I do NOT need, nor want, desktop packages that I have no need for to be installed. Start-Date: 2021-03-19 15:43:24 Commandline: apt-get install -o DPkg::options::=--force-confnew -y nvidia-driver-460 linux-modules-nvidia-460-generic Requested-By: ubuntu (1000) Install: libmpc3:amd64 (1.1.0-1, automatic), gkbd-capplet:amd64 (3.26.1-1, automatic), libgoa-backend-1.0-1:amd64 (3.36.0-1ubuntu1, automatic), xserver-xorg-input-all:amd64 (1:7.7+19ubuntu14, automatic), hunspel l-en-us:amd64 (1:2018.04.16-1, automatic), libqmi-proxy:amd64 (1.24.8-1, automatic), network-manager-pptp:amd64 (1.2.8-2, automatic), libsoup-gnome2.4-1:amd64 (2.70.0-1, automatic), bluez:amd64 (5.53-0ubuntu3, a utomatic), python3-defer:amd64 (1.0.6-2.1, automatic), gnome-control-center-data:amd64 (1:3.36.5-0ubuntu1, automatic), evolution-data-server-common:amd64 (3.36.4-0ubuntu1, automatic), libgdata-common:amd64 (0.17 .12-1, automatic), libwebp6:amd64 (0.6.1-2, automatic), gnome-keyring:amd64 (3.36.0-1ubuntu1, automatic), libldb2:amd64 (2:2.0.10-0ubuntu0.20.04.2, automatic), gnome-settings-daemon-common:amd64 (3.36.1-0ubuntu1 , automatic), xserver-xorg:amd64 (1:7.7+19ubuntu14, automatic), libnl-route-3-200:amd64 (3.4.0-1, automatic), libteamdctl0:amd64 (1.30-1, automatic), libcogl20:amd64 (1.22.6-1, automatic), xserver-xorg-video-qxl :amd64 (0.1.5+git20200331-1, automatic), python3-cupshelpers:amd64 (1.5.12-0ubuntu1.1, automatic), python3-ibus-1.0:amd64 (1.5.22-2ubuntu2.1, automatic), xserver-xorg-video-vesa:amd64 (1:2.4.0-2, automatic), lib openjp2-7:amd64 (2.3.1-1ubuntu4.20.04.1, automatic), libpangoft2-1.0-0:amd64 (1.44.7-2ubuntu4, automatic), dbus-x11:amd64 (1.12.16-2ubuntu2.1, automatic), libaa1:amd64 (1.4p5-46, automatic), libgphoto2-port12:am d64 (2.5.25-0ubuntu0.1, automatic), libcrack2:amd64 (2.9.6-3.2, automatic), libraw1394-11:amd64 (2.1.2-1, automatic), libieee1284-3:amd64 (0.2.11-13build1, automatic), libfontenc1:amd64 (1:1.1.4-0ubuntu1, automa tic), libclutter-1.0-0:amd64 (1.26.4+dfsg-1, automatic), libxcb-icccm4:amd64 (0.4.1-1.1, automatic), gir1.2-nm-1.0:amd64 (1.22.10-1ubuntu2.2, automatic), libplist3:amd64 (2.1.0-4build2, automatic), libvte-2.91-0 :amd64 (0.60.3-0ubuntu1~20.04, automatic), libedataserverui-1.2-2:amd64 (3.36.4-0ubuntu1, automatic), libcups2:amd64 (2.3.1-9ubuntu1.1, automatic), libvulkan1:amd64 (1.2.131.2-1, automatic), libwayland-egl1:amd6 4 (1.18.0-1, automatic), libgtop2-common:amd64 (2.40.0-2, automatic), xserver-xorg-video-nouveau:amd64 (1:1.0.16-1, automatic), libclutter-gst-3.0-0:amd64 (3.0.27-1, automatic), mobile-broadband-provider-info:am d64 (20190618-3, automatic), libdrm-nouveau2:amd64 (2.4.102-1ubuntu1~20.04.1, automatic), xserver-xorg-video-amdgpu:amd64 (19.1.0-1, automatic), gnome-session-common:amd64 (3.36.0-2ubuntu1, automatic), gir1.2-gt k-3.0:amd64 (3.24.20-0ubuntu1, automatic), system-config-printer:amd64 (1.5.12-0ubuntu1.1, automatic), gir1.2-mutter-6:amd64 (3.36.7+git20201123-0.20.04.1, automatic), libpcsclite1:amd64 (1.8.26-3, automatic), l ibxklavier16:amd64 (5.4-4, automatic), gnome-control-center:amd64 (1:3.36.5-0ubuntu1, automatic), session-migration:amd64 (0.3.5, automatic), libgcr-base-3-1:amd64 (3.36.0-2build1, automatic), gir1.2-notify-0.7: amd64 (0.7.9-1ubuntu2, automatic), xserver-common:amd64 (2:1.20.9-2ubuntu1.2~20.04.1, automatic), gir1.2-secret-1:amd64 (0.20.3-0ubuntu1, automatic), libxcb-xfixes0:amd64 (1.14-2, automatic), libwacom-common:amd 64 (1.3-2ubuntu1, automatic), gir1.2-soup-2.4:amd64 (2.70.0-1, automatic), libgtk2.0-bin:amd64 (2.24.32-4ubuntu4, automatic), libnvidia-compute-460:amd64 (460.39-0ubuntu0.20.04.1, automatic), libegl1:amd64 (1.3. 2-1~ubuntu0.20.04.1, automatic), gcc-9-base:amd64 (9.3.0-17ubuntu1~20.04, automatic), sgml-base:amd64 (1.29.1, automatic), xserver-xorg-core:amd64 (2:1.20.9-2ubuntu1.2~20.04.1, automatic), libdv4:amd64 (1.0.0-12 , automatic), libgphoto2-6:amd64 (2.5.25-0ubuntu0.1, automatic), gir1.2-gdkpixbuf-2.0:amd64 (2.40.0+dfsg-3ubuntu0.2, automatic), libcogl-path20:amd64 (1.22.6-1, automatic), libgdk-pixbuf2.0-0:amd64 (2.40.0+dfsg- 3ubuntu0.2, automatic), sane-utils:amd64 (1.0.29-0ubuntu5.2,
[Desktop-packages] [Bug 1920225] [NEW] ubuntu-drivers should not run unless user is root
Public bug reported: one cannot install drivers unless one is root (or has root priv escalation via sudo). For that reason, ubuntu-drivers should not run without a priv check. ubuntu@doubletusk:~$ ubuntu-drivers --gpgpu autoinstall This is gpgpu mode E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you root? This shouldn't trigger the apt privilege error, ubuntu-drivers itself should check to see if it's running as root and then prompt the user. ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1920225 Title: ubuntu-drivers should not run unless user is root Status in ubuntu-drivers-common package in Ubuntu: New Bug description: one cannot install drivers unless one is root (or has root priv escalation via sudo). For that reason, ubuntu-drivers should not run without a priv check. ubuntu@doubletusk:~$ ubuntu-drivers --gpgpu autoinstall This is gpgpu mode E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you root? This shouldn't trigger the apt privilege error, ubuntu-drivers itself should check to see if it's running as root and then prompt the user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1920225/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920232] [NEW] ubuntu-drivers --gpgpu installs hundreds of unnecessary and unwanted packages
Public bug reported: when I use --gpgpu mode to install gpgpu drivers using ubuntu-drivers, I want ONLY apropriate drivers for GPU compute functions. I do NOT need, nor want, desktop packages that I have no need for to be installed. Start-Date: 2021-03-19 15:43:24 Commandline: apt-get install -o DPkg::options::=--force-confnew -y nvidia-driver-460 linux-modules-nvidia-460-generic Requested-By: ubuntu (1000) Install: libmpc3:amd64 (1.1.0-1, automatic), gkbd-capplet:amd64 (3.26.1-1, automatic), libgoa-backend-1.0-1:amd64 (3.36.0-1ubuntu1, automatic), xserver-xorg-input-all:amd64 (1:7.7+19ubuntu14, automatic), hunspel l-en-us:amd64 (1:2018.04.16-1, automatic), libqmi-proxy:amd64 (1.24.8-1, automatic), network-manager-pptp:amd64 (1.2.8-2, automatic), libsoup-gnome2.4-1:amd64 (2.70.0-1, automatic), bluez:amd64 (5.53-0ubuntu3, a utomatic), python3-defer:amd64 (1.0.6-2.1, automatic), gnome-control-center-data:amd64 (1:3.36.5-0ubuntu1, automatic), evolution-data-server-common:amd64 (3.36.4-0ubuntu1, automatic), libgdata-common:amd64 (0.17 .12-1, automatic), libwebp6:amd64 (0.6.1-2, automatic), gnome-keyring:amd64 (3.36.0-1ubuntu1, automatic), libldb2:amd64 (2:2.0.10-0ubuntu0.20.04.2, automatic), gnome-settings-daemon-common:amd64 (3.36.1-0ubuntu1 , automatic), xserver-xorg:amd64 (1:7.7+19ubuntu14, automatic), libnl-route-3-200:amd64 (3.4.0-1, automatic), libteamdctl0:amd64 (1.30-1, automatic), libcogl20:amd64 (1.22.6-1, automatic), xserver-xorg-video-qxl :amd64 (0.1.5+git20200331-1, automatic), python3-cupshelpers:amd64 (1.5.12-0ubuntu1.1, automatic), python3-ibus-1.0:amd64 (1.5.22-2ubuntu2.1, automatic), xserver-xorg-video-vesa:amd64 (1:2.4.0-2, automatic), lib openjp2-7:amd64 (2.3.1-1ubuntu4.20.04.1, automatic), libpangoft2-1.0-0:amd64 (1.44.7-2ubuntu4, automatic), dbus-x11:amd64 (1.12.16-2ubuntu2.1, automatic), libaa1:amd64 (1.4p5-46, automatic), libgphoto2-port12:am d64 (2.5.25-0ubuntu0.1, automatic), libcrack2:amd64 (2.9.6-3.2, automatic), libraw1394-11:amd64 (2.1.2-1, automatic), libieee1284-3:amd64 (0.2.11-13build1, automatic), libfontenc1:amd64 (1:1.1.4-0ubuntu1, automa tic), libclutter-1.0-0:amd64 (1.26.4+dfsg-1, automatic), libxcb-icccm4:amd64 (0.4.1-1.1, automatic), gir1.2-nm-1.0:amd64 (1.22.10-1ubuntu2.2, automatic), libplist3:amd64 (2.1.0-4build2, automatic), libvte-2.91-0 :amd64 (0.60.3-0ubuntu1~20.04, automatic), libedataserverui-1.2-2:amd64 (3.36.4-0ubuntu1, automatic), libcups2:amd64 (2.3.1-9ubuntu1.1, automatic), libvulkan1:amd64 (1.2.131.2-1, automatic), libwayland-egl1:amd6 4 (1.18.0-1, automatic), libgtop2-common:amd64 (2.40.0-2, automatic), xserver-xorg-video-nouveau:amd64 (1:1.0.16-1, automatic), libclutter-gst-3.0-0:amd64 (3.0.27-1, automatic), mobile-broadband-provider-info:am d64 (20190618-3, automatic), libdrm-nouveau2:amd64 (2.4.102-1ubuntu1~20.04.1, automatic), xserver-xorg-video-amdgpu:amd64 (19.1.0-1, automatic), gnome-session-common:amd64 (3.36.0-2ubuntu1, automatic), gir1.2-gt k-3.0:amd64 (3.24.20-0ubuntu1, automatic), system-config-printer:amd64 (1.5.12-0ubuntu1.1, automatic), gir1.2-mutter-6:amd64 (3.36.7+git20201123-0.20.04.1, automatic), libpcsclite1:amd64 (1.8.26-3, automatic), l ibxklavier16:amd64 (5.4-4, automatic), gnome-control-center:amd64 (1:3.36.5-0ubuntu1, automatic), session-migration:amd64 (0.3.5, automatic), libgcr-base-3-1:amd64 (3.36.0-2build1, automatic), gir1.2-notify-0.7: amd64 (0.7.9-1ubuntu2, automatic), xserver-common:amd64 (2:1.20.9-2ubuntu1.2~20.04.1, automatic), gir1.2-secret-1:amd64 (0.20.3-0ubuntu1, automatic), libxcb-xfixes0:amd64 (1.14-2, automatic), libwacom-common:amd 64 (1.3-2ubuntu1, automatic), gir1.2-soup-2.4:amd64 (2.70.0-1, automatic), libgtk2.0-bin:amd64 (2.24.32-4ubuntu4, automatic), libnvidia-compute-460:amd64 (460.39-0ubuntu0.20.04.1, automatic), libegl1:amd64 (1.3. 2-1~ubuntu0.20.04.1, automatic), gcc-9-base:amd64 (9.3.0-17ubuntu1~20.04, automatic), sgml-base:amd64 (1.29.1, automatic), xserver-xorg-core:amd64 (2:1.20.9-2ubuntu1.2~20.04.1, automatic), libdv4:amd64 (1.0.0-12 , automatic), libgphoto2-6:amd64 (2.5.25-0ubuntu0.1, automatic), gir1.2-gdkpixbuf-2.0:amd64 (2.40.0+dfsg-3ubuntu0.2, automatic), libcogl-path20:amd64 (1.22.6-1, automatic), libgdk-pixbuf2.0-0:amd64 (2.40.0+dfsg- 3ubuntu0.2, automatic), sane-utils:amd64 (1.0.29-0ubuntu5.2, automatic), gnome-user-docs:amd64 (3.36.2+git20200704-0ubuntu0.1, automatic), liblcms2-2:amd64 (2.9-4, automatic), libgoa-1.0-0b:amd64 (3.36.0-1ubuntu 1, automatic), cracklib-runtime:amd64 (2.9.6-3.2, automatic), libnvidia-encode-460:amd64 (460.39-0ubuntu0.20.04.1, automatic), libegl-mesa0:amd64 (20.2.6-0ubuntu0.20.04.1, automatic), libcairo-gobject2:amd64 (1. 16.0-4ubuntu1, automatic), python3-macaroonbakery:amd64 (1.3.1-1, automatic), libgoa-1.0-common:amd64 (3.36.0-1ubuntu1, automatic), nvidia-kernel-common-460:amd64 (460.39-0ubuntu0.20.04.1, automatic), libcdparan oia0:amd64 (3.10.2+debian-13, automatic), libfprint-2-2:amd64
[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
For those following along - it appears that the future of Linux audio servers will likely be PipeWire: https://lwn.net/SubscriberLink/847412/d7826b1353e33734/ -- 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 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
I am suffering from this problem as well (2020 Dell XPS 13", Ubuntu LTS 20.04), even after applying the fix at https://www.displaylink.org/forum/showthread.php?t=67148. HOWEVER - I have found that if I mirror my displays (laptop built-in + external HP2511X vis DVI), the lag disappears. This is true even when connected via an external USB 3.0 hub, so at least I can use my external mouse/KB at the same time as enjoying the larger desktop. -- 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/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Confirmed Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1875015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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).
>Jean- (jean-helou) wrote 6 hours ago: #87 >the next step to get a full fix and improved sound quality for voip calls over >BT headset is >coming in >https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/254 This is good news! Proper support for mSBC is critical for me to consider this bug resolved. It was the original intention of opening the bug in the first place :) -- 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 1887804] Re: chromium-browser does not follow XDG base directory specification
Thank you, Olivier. After spending an afternoon analyzing backups, I arrived at a similar conclusion and decided that adding an exclude pattern */chromium/*/*Cache in addition to the one that excludes */.cache is going to be the right thing to do to solve our immediate problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1887804 Title: chromium-browser does not follow XDG base directory specification Status in Chromium Browser: Invalid Status in chromium-browser package in Ubuntu: Opinion Bug description: Currently Chromium does not follow the XDG base directory specification which means that the cache and configuration folder aren't properly used. This causes the issue that it's nearly impossible to properly migrate or back up Chromium configuration (between computers) and it makes for example mounting cache as tmpfs or wiping it very very difficult. I felt those both immensely when trying to migrate my home folder, gigabytes of cache in ~/snap/chromium/[id]/.config/chromium/[folder] (and ~/snap itself is also not XDG base directory specification compliant, shame!). There's also the issue that the previous configuration that is located properly, isn't migrated by the migrational package. In order to fix this bug, it would require making the snap package follow the XDG base directory specification. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1887804/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887804] Re: chromium-browser does not follow XDG base directory specification
Please see comment #20. My online backup set specifically excludes $HOME/.cache (the default or unset value of $XDG_CACHE_HOME) to avoid churning backup snapshots with transient application cache data. I don't know if chromium ever respected $XDG_CACHE_HOME (it would appear from the bug report mentioned in comment #8 that it does not), but in previous packages, it used to store cached data under $HOME/.cache/chromium and now it no longer does. Although it could have been a change in chromium's behavior, the change of location appears to be co-incidental with the transition from deb to snap packaging. Please note that in the snap packaged version of chromium (build 88.0.4324.96), there is a $HOME/snap/chromium/common/.cache directory, but chromium does not store the bulk of its cache data in that location. Most of the cached data is found in 86 or so various directories under $HOME/snap/chromium/common/chromium/Default . It is not clear to me that I can reasonably exclude either or both of $HOME/snap/chromium/common/.cache/ or $HOME/snap/chromium/common/chromium/Default/ to achieve the desired result of limiting transient disk cached data from entering the backup snapshots while keeping chromium user configurations backed up. Since the previous deb packaged version of chromium did store its cached data in the XDG default location (although perhaps only by accident? maybe the deb package maintainer configured it?), and the current snap packaged version does not, I am looking for current package maintainer's guidance on the best way for our backup system to handle this change in behavior. -- 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/1887804 Title: chromium-browser does not follow XDG base directory specification Status in Chromium Browser: Invalid Status in chromium-browser package in Ubuntu: Opinion Bug description: Currently Chromium does not follow the XDG base directory specification which means that the cache and configuration folder aren't properly used. This causes the issue that it's nearly impossible to properly migrate or back up Chromium configuration (between computers) and it makes for example mounting cache as tmpfs or wiping it very very difficult. I felt those both immensely when trying to migrate my home folder, gigabytes of cache in ~/snap/chromium/[id]/.config/chromium/[folder] (and ~/snap itself is also not XDG base directory specification compliant, shame!). There's also the issue that the previous configuration that is located properly, isn't migrated by the migrational package. In order to fix this bug, it would require making the snap package follow the XDG base directory specification. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1887804/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1136644] Re: gedit search function is not practical anymore
While it won't address your UX annoyances, I have filed an issue upstream proposing an approach to make live search faster for big files: https://gitlab.gnome.org/GNOME/gedit/-/issues/398 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1136644 Title: gedit search function is not practical anymore Status in gedit: Unknown Status in gedit package in Ubuntu: Invalid Bug description: i use gedit a lot, and i find it comfortable in general. the new small search window is extremely impractical. FOCUS PROBLEM: CTRL+F > type a search (search of longer strings FAR TOO SLOW) > find and now, typing ESC brings one back to the former place! when trying to use CTRL-F again, the search string is replaced by new text. if one wants to stay in the found passage, one must use the mouse/touchpad to click into the text. this is an extremely annoying feature/behavior. i simply would like to have the old search window + its behavior back. i am working very quickly and mostly using shortcuts. gedit now completely interrupts my way of working. additionally, where are the other search functions such as case- sensitive search? additionally, i do not want the search function to slow down so much. for me it is ok to start the search after i have finished typing my search string :-) this new energy-consuming ZEITGEIST-etc-fashion is not good for quick workers with serious amounts of data. best wishes, vollmanr To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1136644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1136644] Re: gedit search function is not practical anymore
** Bug watch added: gitlab.gnome.org/GNOME/gedit/-/issues #398 https://gitlab.gnome.org/GNOME/gedit/-/issues/398 ** Also affects: gedit via https://gitlab.gnome.org/GNOME/gedit/-/issues/398 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1136644 Title: gedit search function is not practical anymore Status in gedit: Unknown Status in gedit package in Ubuntu: Invalid Bug description: i use gedit a lot, and i find it comfortable in general. the new small search window is extremely impractical. FOCUS PROBLEM: CTRL+F > type a search (search of longer strings FAR TOO SLOW) > find and now, typing ESC brings one back to the former place! when trying to use CTRL-F again, the search string is replaced by new text. if one wants to stay in the found passage, one must use the mouse/touchpad to click into the text. this is an extremely annoying feature/behavior. i simply would like to have the old search window + its behavior back. i am working very quickly and mostly using shortcuts. gedit now completely interrupts my way of working. additionally, where are the other search functions such as case- sensitive search? additionally, i do not want the search function to slow down so much. for me it is ok to start the search after i have finished typing my search string :-) this new energy-consuming ZEITGEIST-etc-fashion is not good for quick workers with serious amounts of data. best wishes, vollmanr To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1136644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170353] Re: Host names intermittently resolve to 0.0.0.0
It's happened to me a few times on 20.04.1: $ host support.coinjar.com support.coinjar.com has address 0.0.0.0 support.coinjar.com has IPv6 address :: support.coinjar.com is an alias for coinjar.zendesk.com. coinjar.zendesk.com mail is handled by 10 mail-pod-25.int.zendesk.com. $ sudo resolvectl flush-caches $ host support.coinjar.com support.coinjar.com has address 0.0.0.0 support.coinjar.com has IPv6 address :: support.coinjar.com is an alias for coinjar.zendesk.com. coinjar.zendesk.com mail is handled by 10 mail-pod-25.int.zendesk.com. $ dig support.coinjar.com ; <<>> DiG 9.16.1-Ubuntu <<>> support.coinjar.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12759 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;support.coinjar.com. IN A ;; ANSWER SECTION: support.coinjar.com.34 IN A 0.0.0.0 ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Wed Jan 06 20:23:28 AEDT 2021 ;; MSG SIZE rcvd: 64 Then 2 minutes later the problem resolves itself: $ dig support.coinjar.com ; <<>> DiG 9.16.1-Ubuntu <<>> support.coinjar.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64605 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;support.coinjar.com. IN A ;; ANSWER SECTION: support.coinjar.com.151 IN CNAME coinjar.zendesk.com. coinjar.zendesk.com.900 IN A 104.16.51.111 coinjar.zendesk.com.900 IN A 104.16.53.111 ;; Query time: 68 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Wed Jan 06 20:25:31 AEDT 2021 ;; MSG SIZE rcvd: 110 Nothing in /var/log/syslog or systemd-resolved's systemd log. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1170353 Title: Host names intermittently resolve to 0.0.0.0 Status in network-manager package in Ubuntu: Invalid Bug description: About 5% of DNS queries resolve to 0.0.0.0. A couple of times an hour during normal browsing, Firefox resolves a domain to 0.0.0.0. Opening the same site in Chrome has a 50% chance of it working, then it normally works after a few reloads. Thunderbird has also occasionally resolved googlemail.com to 0.0.0.0. Domains include google.com, wikipedia.org, harvestapp.com and many more. I couldn't reproduce this with dig/nslookup for a while, but after 5 minutes of (re)trying random domains) did: $ dig mail.google.com ; <<>> DiG 9.8.1-P1 <<>> mail.google.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22905 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;mail.google.com. IN A ;; ANSWER SECTION: mail.google.com. 60 IN A 0.0.0.0 ;; Query time: 0 msec ;; SERVER: 127.0.1.1#53(127.0.1.1) ;; WHEN: Thu Apr 18 13:57:04 2013 ;; MSG SIZE rcvd: 49 Note the "0 msec", so I'm pretty sure this is dnsmasq's local cache. Using Xubuntu 12.10, NetworkManager 0.9.6.0, Dnsmasq 2.63rc6. NetworkManager has DNS servers set to "8.8.8.8, 8.8.4.4" (also tried setting it to my router's DNS server, with no effect). /etc/resolve.conf just has "nameserver 127.0.1.1" dnsmasq is currently running: /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind- interfaces --pid-file=/var/run/sendsigs.omit.d/network- manager.dnsmasq.pid --listen-address=127.0.1.1 --conf-file=/var/run /nm-dns-dnsmasq.conf --cache-size=0 --proxy-dnssec --enable- dbus=org.freedesktop.NetworkManager.dnsmasq --conf- dir=/etc/NetworkManager/dnsmasq.d ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Apr 18 14:27:33 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-01-11 (97 days ago) InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) IpRoute: default via 10.0.0.1 dev eth0 proto static 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.10 metric 1 169.254.0.0/16 dev eth0 scope link
[Desktop-packages] [Bug 1902580] Re: [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall pulseaudio after every reboot.
It appears that one of the recent updates fixed this problem. -- 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/1902580 Title: [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall pulseaudio after every reboot. Status in pulseaudio package in Ubuntu: Confirmed Bug description: My Xubuntu 20.10 installation has no sound (Dummy Output) unless I reinstall pulseaudio after every reboot. pulseaudio does survive a suspend. Just a hard reset or power cycle causes it to fail. How I re-install pulseaudio: sudo apt-get install --reinstall pulseaudio I have tried just killing the pulseaudio service, and letting it restart on it's own. It restarts, but no audio. Reinstalling seems to do the trick though. Note: File samples are after reinstalling. (working state) Thank You, Jeff ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Nov 2 13:42:36 2020 InstallationDate: Installed on 2020-11-02 (0 days ago) InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902580/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902580] Re: [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall pulseaudio after every reboot.
systemctl --user status pulseaudio.service ** Attachment added: "systemctl --user status pulseaudio.service" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902580/+attachment/5438826/+files/systemctl_--user_status_pulseaudio.service.txt -- 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/1902580 Title: [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall pulseaudio after every reboot. Status in pulseaudio package in Ubuntu: Confirmed Bug description: My Xubuntu 20.10 installation has no sound (Dummy Output) unless I reinstall pulseaudio after every reboot. pulseaudio does survive a suspend. Just a hard reset or power cycle causes it to fail. How I re-install pulseaudio: sudo apt-get install --reinstall pulseaudio I have tried just killing the pulseaudio service, and letting it restart on it's own. It restarts, but no audio. Reinstalling seems to do the trick though. Note: File samples are after reinstalling. (working state) Thank You, Jeff ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Nov 2 13:42:36 2020 InstallationDate: Installed on 2020-11-02 (0 days ago) InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902580/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905513] [NEW] Mouse does not respect primary/secondary button settings after being disconnected and reconnected.
Public bug reported: After installing 20.04, in the gnome control center I selected the right mouse button to be the primary button. When I unplug the mouse and replug it in, the right mouse button is no longer the primary button. When I look at the gnome control center, the setting says that the right mouse button is the primary button. To get the right button as the primary button I need to click on the GUI control to make the left button primary and then on the same control a second time to make the right button primary. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-7630.32~1605108853~20.04~8bcf10e~dev-generic 5.8.17 Uname: Linux 5.8.0-7630-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 24 20:43:26 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2014-10-04 (2244 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-11-12 (12 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- 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/1905513 Title: Mouse does not respect primary/secondary button settings after being disconnected and reconnected. Status in gnome-control-center package in Ubuntu: New Bug description: After installing 20.04, in the gnome control center I selected the right mouse button to be the primary button. When I unplug the mouse and replug it in, the right mouse button is no longer the primary button. When I look at the gnome control center, the setting says that the right mouse button is the primary button. To get the right button as the primary button I need to click on the GUI control to make the left button primary and then on the same control a second time to make the right button primary. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-7630.32~1605108853~20.04~8bcf10e~dev-generic 5.8.17 Uname: Linux 5.8.0-7630-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 24 20:43:26 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2014-10-04 (2244 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-11-12 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1905513/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893481] Re: UnicodeEncodeError when logging improperly encoded filenames
Thank you!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1893481
Title:
UnicodeEncodeError when logging improperly encoded filenames
Status in Duplicity:
Fix Released
Status in duplicity package in Ubuntu:
Fix Committed
Bug description:
Attempts to log messages which contain unicode surrogate characters cause
exceptions.
(These surrogate characters arise, for example, when handling files whose
names are not properly encoded as UTF-8.)
NOTE: I have no idea whether this is an issue when running on python
2. (If it is, the fixes suggested below probably won't work.)
Duplicity version: 0.8.15
Python version: 3.8.5
Target filesystem: Linux
Example log output:
--- Logging error ---
Traceback (most recent call last):
File "/opt/Python-3.8.5/lib/python3.8/logging/__init__.py", line 1084, in
emit
stream.write(msg + self.terminator)
UnicodeEncodeError: 'utf-8' codec can't encode character '\udcc4' in position
45: surrogates not allowed
Call stack:
File "/root/.local/pipx/venvs/duplicity/bin/duplicity", line 104, in
with_tempdir(main)
File "/root/.local/pipx/venvs/duplicity/bin/duplicity", line 90, in
with_tempdir
fn()
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/dup_main.py",
line 1531, in main
do_backup(action)
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/dup_main.py",
line 1655, in do_backup
full_backup(col_stats)
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/dup_main.py",
line 559, in full_backup
bytes_written = write_multivol(u"full", tarblock_iter,
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/dup_main.py",
line 417, in write_multivol
at_end = gpg.GPGWriteFile(tarblock_iter, tdp.name, config.gpg_profile,
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/gpg.py",
line 390, in GPGWriteFile
data = block_iter.__next__().data
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/diffdir.py",
line 544, in __next__
result = self.process(next(self.input_iter)) # pylint:
disable=assignment-from-no-return
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/diffdir.py",
line 238, in get_delta_iter
log_delta_path(delta_path, new_path, stats)
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/diffdir.py",
line 181, in log_delta_path
log.Info(_(u"A %s") %
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/log.py",
line 128, in Info
Log(s, INFO, code, extra)
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/log.py",
line 91, in Log
_logger.log(DupToLoggerLevel(verb_level), s,
Message: 'A home/dairiki/PRCS/junk-changelog/22_Senaste\udcc4nd,v'
Arguments: ()
Steps to reproduce:
- Have a file with funny characters in its name, encoded in latin-1 encoding.
E.g. a file whose name is "Fü" encoded to latin-1 (b'F\xfc'). When duplicity
handles this file, the improperly encoded character will be replaced with a
unicode surrogate character.
- Attempt to create an archive containing this file, with verbosity set to 5.
Duplicity will try to log each file processed. When it gets to this file, an
exception will be reported (and the file will not make it into the archive.)
Alternative steps to produce:
- If the archive is created with verbosity less than 5, the file will make it
into the archive. However, if an attempt is made to list files using
'duplicity list-current-files', an exception will be reported when it gets to
the file with the funny name.
Workaround
==
A simple workaround is to set the environment variable
PYTHONIOENCODING="utf-8:surrogateescape" before running duplicity.
This will set the encoding error mode for stdout and stderr to
'surrogateescape' (by default it is 'strict') with the effect that any
surrogates will be replaced with the unicode replacement character
(U+FFFD: "�").
Possible Fix
A possible fix, at least for Py3K, is probably for duplicity to explicitly
set the encoding error strategy for stdin and stdout.
For python >= 3.7 this is simple:
sys.stdin.reconfigure(errors='surrogateescape')
sys.stderr.reconfigure(errors='surrogateescape')
For earlier pythons (>= 3), the best option might be:
sys.stdin = codecs.getwriter('utf-8')(sys.stdin.detach(),
'surrogateescape')
(and similarly for stderr)
Note that python 2 doesn't know about errors='surrogateescape'.
Errors='replace' would probably work as an alternative, but it's not
ideal as it replaces the surrogates with a plain question mark rather
than a
[Desktop-packages] [Bug 1902580] Re: [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall pulseaudio after every reboot.
** Description changed: My Xubuntu 20.10 installation has no sound (Dummy Output) unless I reinstall pulseaudio after every reboot. pulseaudio does survive a suspend. Just a hard reset or power cycle causes it to fail. How I re-install pulseaudio: sudo apt-get install --reinstall pulseaudio I have tried just killing the pulseaudio service, and letting it restart on it's own. It restarts, but no audio. Reinstalling seems to do the trick though. + + + Note: File samples are after reinstalling. (working state) Thank You, Jeff ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Nov 2 13:42:36 2020 InstallationDate: Installed on 2020-11-02 (0 days ago) InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. -- 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/1902580 Title: [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall pulseaudio after every reboot. Status in pulseaudio package in Ubuntu: Confirmed Bug description: My Xubuntu 20.10 installation has no sound (Dummy Output) unless I reinstall pulseaudio after every reboot. pulseaudio does survive a suspend. Just a hard reset or power cycle causes it to fail. How I re-install pulseaudio: sudo apt-get install --reinstall pulseaudio I have tried just killing the pulseaudio service, and letting it restart on it's own. It restarts, but no audio. Reinstalling seems to do the trick though. Note: File samples are after reinstalling. (working state) Thank You, Jeff ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Nov 2 13:42:36 2020 InstallationDate: Installed on 2020-11-02 (0 days ago) InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902580/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902580] Re: Xubuntu 20.10 has no sound (Dummy Output) unless I reinstall pulseaudio after every reboot.
** Summary changed: - Xubuntu 20.10 has No Sound (Dummy Output) unless I reinstall pulseaudio after every reboot. + Xubuntu 20.10 has no sound (Dummy Output) unless I reinstall pulseaudio after every reboot. ** Description changed: - My Xubuntu 20.10 instsallation has No Sound (Dummy Output) unless I + My Xubuntu 20.10 installation has no sound (Dummy Output) unless I reinstall pulseaudio after every reboot. pulseaudio does survive a suspend. Just a hard reset or power cycle causes it to fail. How I re-install pulseaudio: sudo apt-get install --reinstall pulseaudio I have tried just killing the pulseaudio service, and letting it restart on it's own. It restarts, but no audio. Reinstalling seems to do the trick though. Thank You, Jeff ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Nov 2 13:42:36 2020 InstallationDate: Installed on 2020-11-02 (0 days ago) InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. -- 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/1902580 Title: Xubuntu 20.10 has no sound (Dummy Output) unless I reinstall pulseaudio after every reboot. Status in pulseaudio package in Ubuntu: New Bug description: My Xubuntu 20.10 installation has no sound (Dummy Output) unless I reinstall pulseaudio after every reboot. pulseaudio does survive a suspend. Just a hard reset or power cycle causes it to fail. How I re-install pulseaudio: sudo apt-get install --reinstall pulseaudio I have tried just killing the pulseaudio service, and letting it restart on it's own. It restarts, but no audio. Reinstalling seems to do the trick though. Thank You, Jeff ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Nov 2 13:42:36 2020 InstallationDate: Installed on 2020-11-02 (0 days ago) InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902580/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902580] [NEW] Xubuntu 20.10 has No Sound (Dummy Output) unless I reinstall pulseaudio after every reboot.
Public bug reported: My Xubuntu 20.10 instsallation has No Sound (Dummy Output) unless I reinstall pulseaudio after every reboot. pulseaudio does survive a suspend. Just a hard reset or power cycle causes it to fail. How I re-install pulseaudio: sudo apt-get install --reinstall pulseaudio I have tried just killing the pulseaudio service, and letting it restart on it's own. It restarts, but no audio. Reinstalling seems to do the trick though. Thank You, Jeff ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Nov 2 13:42:36 2020 InstallationDate: Installed on 2020-11-02 (0 days ago) InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ** Description changed: My Xubuntu 20.10 instsallation has No Sound (Dummy Output) unless I reinstall pulseaudio after every reboot. pulseaudio does survive a suspend. Just a hard reset or power cycle causes it to fail. - How I re-install pulseaudio (obvious but just in case) Xubuntu 20.10 has - No Sound (Dummy Output) unless I reinstall pulseaudio after every - reboot. + How I re-install pulseaudio: sudo apt-get install --reinstall pulseaudio I have tried just killing the pulseaudio service, and letting it restart on it's own. It restarts, but no audio. Reinstalling seems to do the trick though. - Thank You, Jeff ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Nov 2 13:42:36 2020 InstallationDate: Installed on 2020-11-02 (0 days ago) InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. -- 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/1902580 Title: Xubuntu 20.10 has No Sound (Dummy Output) unless I reinstall pulseaudio after every reboot. Status in pulseaudio package in Ubuntu: New Bug description: My Xubuntu 20.10 instsallation has No Sound (Dummy Output) unless I reinstall pulseaudio after every reboot. pulseaudio does survive a suspend. Just a hard reset or power cycle causes it to fail. How I re-install pulseaudio: sudo apt-get install --reinstall pulseaudio I have tried just killing the pulseaudio service, and letting it restart on it's own. It restarts, but no audio. Reinstalling seems to do the trick though. Thank You, Jeff ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip Current
[Desktop-packages] [Bug 1616332] Re: gnome-software using hundreds of MB of memory when not in use
** Also affects: gnome-software via https://gitlab.gnome.org/GNOME/gnome-software/-/issues/191 Importance: Unknown Status: Unknown -- 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/1616332 Title: gnome-software using hundreds of MB of memory when not in use Status in GNOME Software: Unknown Status in gnome-software package in Ubuntu: Triaged Bug description: It seems gnome-software is running in the background all the time. Not a big deal if it was lightweight, but it seems to use hundreds of MB (from smem output): PID User Command Swap USS PSS RSS 2291 jan /usr/bin/gnome-software --g 285436 112576 117982 134036 A total of over 400MB in RAM and swap combined. After killing and restarting, it takes "only" a bit over 100MB. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Aug 24 09:45:53 2016 InstallationDate: Installed on 2012-11-10 (1382 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: gnome-software UpgradeStatus: Upgraded to xenial on 2016-06-19 (65 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1616332/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1374403] Re: EOG - CMYK jpg colors are saturated and not correct
This bug still exist, 2020 here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1374403 Title: EOG - CMYK jpg colors are saturated and not correct Status in Eye of GNOME: New Status in eog package in Ubuntu: Triaged Bug description: images with CMYK colors are over saturated when viewed from EOG (image viewer) To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/1374403/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893481] Re: UnicodeEncodeError when logging improperly encoded filenames
The short answer is "en_US.UTF-8". Here's the long answer: dairiki@hairball$ locale LANG=en_US.UTF-8 LANGUAGE= LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1893481 Title: UnicodeEncodeError when logging improperly encoded filenames Status in Duplicity: Fix Committed Status in duplicity package in Ubuntu: Fix Committed Bug description: Attempts to log messages which contain unicode surrogate characters cause exceptions. (These surrogate characters arise, for example, when handling files whose names are not properly encoded as UTF-8.) NOTE: I have no idea whether this is an issue when running on python 2. (If it is, the fixes suggested below probably won't work.) Duplicity version: 0.8.15 Python version: 3.8.5 Target filesystem: Linux Example log output: --- Logging error --- Traceback (most recent call last): File "/opt/Python-3.8.5/lib/python3.8/logging/__init__.py", line 1084, in emit stream.write(msg + self.terminator) UnicodeEncodeError: 'utf-8' codec can't encode character '\udcc4' in position 45: surrogates not allowed Call stack: File "/root/.local/pipx/venvs/duplicity/bin/duplicity", line 104, in with_tempdir(main) File "/root/.local/pipx/venvs/duplicity/bin/duplicity", line 90, in with_tempdir fn() File "/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/dup_main.py", line 1531, in main do_backup(action) File "/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/dup_main.py", line 1655, in do_backup full_backup(col_stats) File "/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/dup_main.py", line 559, in full_backup bytes_written = write_multivol(u"full", tarblock_iter, File "/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/dup_main.py", line 417, in write_multivol at_end = gpg.GPGWriteFile(tarblock_iter, tdp.name, config.gpg_profile, File "/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/gpg.py", line 390, in GPGWriteFile data = block_iter.__next__().data File "/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/diffdir.py", line 544, in __next__ result = self.process(next(self.input_iter)) # pylint: disable=assignment-from-no-return File "/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/diffdir.py", line 238, in get_delta_iter log_delta_path(delta_path, new_path, stats) File "/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/diffdir.py", line 181, in log_delta_path log.Info(_(u"A %s") % File "/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/log.py", line 128, in Info Log(s, INFO, code, extra) File "/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/log.py", line 91, in Log _logger.log(DupToLoggerLevel(verb_level), s, Message: 'A home/dairiki/PRCS/junk-changelog/22_Senaste\udcc4nd,v' Arguments: () Steps to reproduce: - Have a file with funny characters in its name, encoded in latin-1 encoding. E.g. a file whose name is "Fü" encoded to latin-1 (b'F\xfc'). When duplicity handles this file, the improperly encoded character will be replaced with a unicode surrogate character. - Attempt to create an archive containing this file, with verbosity set to 5. Duplicity will try to log each file processed. When it gets to this file, an exception will be reported (and the file will not make it into the archive.) Alternative steps to produce: - If the archive is created with verbosity less than 5, the file will make it into the archive. However, if an attempt is made to list files using 'duplicity list-current-files', an exception will be reported when it gets to the file with the funny name. Workaround == A simple workaround is to set the environment variable PYTHONIOENCODING="utf-8:surrogateescape" before running duplicity. This will set the encoding error mode for stdout and stderr to 'surrogateescape' (by default it is 'strict') with the effect that any surrogates will be replaced with the unicode replacement character (U+FFFD: "�"). Possible Fix A possible fix, at least for Py3K, is probably for duplicity to explicitly set the encoding error strategy for stdin and stdout. For python >= 3.7 this is simple: sys.stdin.reconfigure(errors='surrogateescape')
[Desktop-packages] [Bug 1898601] Re: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server
+1 Dann's suggestion works great when manually installing the packages via apt. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1898601 Title: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server Status in ubuntu-drivers-common package in Ubuntu: New Bug description: When I install the packaged nVidia drivers using --gpgpu, I expect that I am getting compute related GPGPU drivers. Instead, I find that on a fresh Focal installation of Ubuntu Server, I also get a full desktop environment. This sets us up nicely for this bug: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559 because this pulls in gdm3 and a whole host of unnecessary desktop packages but does nothing to mitigate the gdm3 propensity to autosuspend, which makes the server become unresponsive when there is no user activity (even when it's running workloads on the GPGPU, the server can still autosuspend). Additionally, this adds a software stack that causes unnecessary CPU and memory usage on a machine that is meant to run headless and devote all resources to handling GPGPU compute activities. This is gpgpu mode Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: apg aptdaemon aptdaemon-data aspell aspell-en avahi-daemon avahi-utils bluez bubblewrap colord colord-data cracklib-runtime cups-pk-helper dbus-x11 dconf-cli desktop-file-utils dictionaries-common docbook-xml emacsen-common enchant-2 evolution-data-server evolution-data-server-common fprintd gcr gdm3 geoclue-2.0 gir1.2-accountsservice-1.0 gir1.2-atspi-2.0 gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdesktopenums-3.0 gir1.2-gdm-1.0 gir1.2-geoclue-2.0 gir1.2-gnomebluetooth-1.0 gir1.2-gnomedesktop-3.0 gir1.2-graphene-1.0 gir1.2-gweather-3.0 gir1.2-ibus-1.0 gir1.2-mutter-6 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-notify-0.7 gir1.2-polkit-1.0 gir1.2-rsvg-2.0 gir1.2-secret-1 gir1.2-soup-2.4 gir1.2-upowerglib-1.0 gir1.2-vte-2.91 gjs gkbd-capplet gnome-control-center gnome-control-center-data gnome-control-center-faces gnome-desktop3-data gnome-keyring gnome-keyring-pkcs11 gnome-menus gnome-online-accounts gnome-session-bin gnome-session-common gnome-settings-daemon gnome-settings-daemon-common gnome-shell gnome-shell-common gnome-startup-applications gnome-user-docs gstreamer1.0-clutter-3.0 hunspell-en-us ibus ibus-data ibus-gtk ibus-gtk3 iio-sensor-proxy im-config ippusbxd language-selector-gnome libappindicator3-1 libasound2-plugins libaspell15 libavahi-core7 libavahi-glib1 libcamel-1.2-62 libcanberra-gtk3-0 libcanberra-gtk3-module libcanberra-pulse libcheese-gtk25 libclutter-gtk-1.0-0 libcolord-gtk1 libcolorhug2 libcrack2 libdaemon0 libdbusmenu-glib4 libdbusmenu-gtk3-4 libebackend-1.2-10 libebook-1.2-20 libebook-contacts-1.2-3 libecal-2.0-1 libedata-book-1.2-26 libedata-cal-2.0-1 libedataserver-1.2-24 libedataserverui-1.2-2 libenchant-2-2 libexif12 libfontenc1 libfprint-2-2 libgail-common libgail18 libgck-1-0 libgcr-base-3-1 libgcr-ui-3-1 libgd3 libgdata-common libgdata22 libgdm1 libgee-0.8-2 libgeoclue-2-0 libgeocode-glib0 libgjs0g libgles2 libgnome-autoar-0-0 libgnome-bluetooth13 libgnome-desktop-3-19 libgnomekbd-common libgnomekbd8 libgoa-1.0-0b libgoa-1.0-common libgoa-backend-1.0-1 libgphoto2-6 libgphoto2-l10n libgphoto2-port12 libgsound0 libgssdp-1.2-0 libgtk2.0-0 libgtk2.0-bin libgtk2.0-common libgtop-2.0-11 libgtop2-common libgupnp-1.2-0 libgupnp-av-1.0-2 libgupnp-dlna-2.0-3 libgweather-3-16 libgweather-common libharfbuzz-icu0 libhunspell-1.7-0 libhyphen0 libibus-1.0-5 libical3 libice6 libieee1284-3 libimobiledevice6 libjavascriptcoregtk-4.0-18 libldb2 libmediaart-2.0-0 libmozjs-68-0 libmutter-6-0 libnma0 libnotify4 libnss-mdns libnvidia-cfg1-435 libnvidia-common-435 libnvidia-compute-435 libnvidia-decode-435 libnvidia-encode-435 libnvidia-fbc1-435 libnvidia-gl-435 libnvidia-ifr1-435 libopenjp2-7 libpam-fprintd libpam-gnome-keyring libphonenumber7 libplist3 libprotobuf17 libpulse-mainloop-glib0 libpulsedsp libpwquality-common libpwquality1 librygel-core-2.6-2 librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2 libsane libsane-common libsbc1 libsecret-1-0 libsecret-common libsm6 libsmbclient libsnapd-glib1 libsoxr0 libspeexdsp1
[Desktop-packages] [Bug 1898601] [NEW] 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server
Public bug reported: When I install the packaged nVidia drivers using --gpgpu, I expect that I am getting compute related GPGPU drivers. Instead, I find that on a fresh Focal installation of Ubuntu Server, I also get a full desktop environment. This sets us up nicely for this bug: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559 because this pulls in gdm3 and a whole host of unnecessary desktop packages but does nothing to mitigate the gdm3 propensity to autosuspend, which makes the server become unresponsive when there is no user activity (even when it's running workloads on the GPGPU, the server can still autosuspend). Additionally, this adds a software stack that causes unnecessary CPU and memory usage on a machine that is meant to run headless and devote all resources to handling GPGPU compute activities. This is gpgpu mode Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: apg aptdaemon aptdaemon-data aspell aspell-en avahi-daemon avahi-utils bluez bubblewrap colord colord-data cracklib-runtime cups-pk-helper dbus-x11 dconf-cli desktop-file-utils dictionaries-common docbook-xml emacsen-common enchant-2 evolution-data-server evolution-data-server-common fprintd gcr gdm3 geoclue-2.0 gir1.2-accountsservice-1.0 gir1.2-atspi-2.0 gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdesktopenums-3.0 gir1.2-gdm-1.0 gir1.2-geoclue-2.0 gir1.2-gnomebluetooth-1.0 gir1.2-gnomedesktop-3.0 gir1.2-graphene-1.0 gir1.2-gweather-3.0 gir1.2-ibus-1.0 gir1.2-mutter-6 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-notify-0.7 gir1.2-polkit-1.0 gir1.2-rsvg-2.0 gir1.2-secret-1 gir1.2-soup-2.4 gir1.2-upowerglib-1.0 gir1.2-vte-2.91 gjs gkbd-capplet gnome-control-center gnome-control-center-data gnome-control-center-faces gnome-desktop3-data gnome-keyring gnome-keyring-pkcs11 gnome-menus gnome-online-accounts gnome-session-bin gnome-session-common gnome-settings-daemon gnome-settings-daemon-common gnome-shell gnome-shell-common gnome-startup-applications gnome-user-docs gstreamer1.0-clutter-3.0 hunspell-en-us ibus ibus-data ibus-gtk ibus-gtk3 iio-sensor-proxy im-config ippusbxd language-selector-gnome libappindicator3-1 libasound2-plugins libaspell15 libavahi-core7 libavahi-glib1 libcamel-1.2-62 libcanberra-gtk3-0 libcanberra-gtk3-module libcanberra-pulse libcheese-gtk25 libclutter-gtk-1.0-0 libcolord-gtk1 libcolorhug2 libcrack2 libdaemon0 libdbusmenu-glib4 libdbusmenu-gtk3-4 libebackend-1.2-10 libebook-1.2-20 libebook-contacts-1.2-3 libecal-2.0-1 libedata-book-1.2-26 libedata-cal-2.0-1 libedataserver-1.2-24 libedataserverui-1.2-2 libenchant-2-2 libexif12 libfontenc1 libfprint-2-2 libgail-common libgail18 libgck-1-0 libgcr-base-3-1 libgcr-ui-3-1 libgd3 libgdata-common libgdata22 libgdm1 libgee-0.8-2 libgeoclue-2-0 libgeocode-glib0 libgjs0g libgles2 libgnome-autoar-0-0 libgnome-bluetooth13 libgnome-desktop-3-19 libgnomekbd-common libgnomekbd8 libgoa-1.0-0b libgoa-1.0-common libgoa-backend-1.0-1 libgphoto2-6 libgphoto2-l10n libgphoto2-port12 libgsound0 libgssdp-1.2-0 libgtk2.0-0 libgtk2.0-bin libgtk2.0-common libgtop-2.0-11 libgtop2-common libgupnp-1.2-0 libgupnp-av-1.0-2 libgupnp-dlna-2.0-3 libgweather-3-16 libgweather-common libharfbuzz-icu0 libhunspell-1.7-0 libhyphen0 libibus-1.0-5 libical3 libice6 libieee1284-3 libimobiledevice6 libjavascriptcoregtk-4.0-18 libldb2 libmediaart-2.0-0 libmozjs-68-0 libmutter-6-0 libnma0 libnotify4 libnss-mdns libnvidia-cfg1-435 libnvidia-common-435 libnvidia-compute-435 libnvidia-decode-435 libnvidia-encode-435 libnvidia-fbc1-435 libnvidia-gl-435 libnvidia-ifr1-435 libopenjp2-7 libpam-fprintd libpam-gnome-keyring libphonenumber7 libplist3 libprotobuf17 libpulse-mainloop-glib0 libpulsedsp libpwquality-common libpwquality1 librygel-core-2.6-2 librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2 libsane libsane-common libsbc1 libsecret-1-0 libsecret-common libsm6 libsmbclient libsnapd-glib1 libsoxr0 libspeexdsp1 libstartup-notification0 libtalloc2 libtevent0 libupower-glib3 libusbmuxd6 libvdpau1 libwbclient0 libwebkit2gtk-4.0-37 libwebrtc-audio-processing1 libwhoopsie-preferences0 libwhoopsie0 libwoff1 libxatracker2 libxaw7 libxcb-icccm4 libxcb-image0 libxcb-keysyms1 libxcb-render-util0 libxcb-res0 libxcb-shape0 libxcb-util1 libxcb-xkb1 libxcb-xv0 libxfont2 libxkbcommon-x11-0 libxkbfile1 libxklavier16 libxmu6 libxpm4 libxss1 libxt6 libxvmc1 libyelp0 linux-modules-nvidia-435-5.4.0-48-generic mesa-vdpau-drivers
[Desktop-packages] [Bug 1872034] Re: [Focal] No HDMI output through thunderbolt docking station
** Tags added: ubuntu-certified -- 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/1872034 Title: [Focal] No HDMI output through thunderbolt docking station Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Invalid Bug description: I can find monitor in display list, but no output from it. Also, I can't switch to extend mode, it failed to apply the setting and switched back to mirror mode. [Steps] 1. Connect a thunderbolt docking station to thunderbolt port. 2. Connect HDMI monitor to HDMI port on the docking station. 3. Switch mode in display setting ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 16:44:40 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2020-04-09 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=98c0c28f-278e-442b-8fc9-6d663bacd68d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd01/08/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1872034/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Toshiba Satellite Radius 12 C-720 same problem ubuntu 20.04 -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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.
Great to see traction on this, thank you for all your efforts Daniel! And to everyone else, this is a far more complex problem than you can imagine However it can and will be solved :) -- 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. Status in PulseAudio: New Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed 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 1874964] [NEW] Secondary display in portrait mode renders incorrectly
Public bug reported: Using the Ubuntu 20.04 settings app to setup multiple monitors creates broken xrandr settings. Using the app to set a 3840x2160 primary monitor in Landscape and 1920x1080 in Right Portrait, the primary monitor ends up with a "virtual resolution" of 4680x2160 which creates a horizontal panning effect at the monitor boundary and pushes the secondary monitor's content far off to the side. Running xrandr shows the following (truncated for readability - screenshot attached) Screen 0: minimum 8 x 8, current 5760 x 2160, maximum 32767 x 32767 DVI-D-0 disconnected (normal left inverted right x axis y axis) HDMI-0 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 connected 1080x1920+3840+0 left (normal left inverted right x axis y axis) 527mm x 296mm panning 1920x1920+3840+0 tracking 5760x2160+0+0 border 0/0/0/0 1920x1080 60.00 + 60.00* 59.9450.0023.98 ... DP-3 disconnected (normal left inverted right x axis y axis) DP-4 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 697mm x 392mm panning 4680x2160+0+0 tracking 5760x2160+0+0 border 0/0/0/0 The correct result for DP-4 would be 3840x2160. I will set this manually but wanted to report the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..42.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:42: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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 22:53:21 2020 DistUpgraded: 2020-04-24 21:48:22,001 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP102 [GeForce GTX 1080 Ti] [3842:6696] InstallationDate: Installed on 2019-07-30 (270 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Micro-Star International Co., Ltd. MS-7B09 ProcEnviron: LC_COLLATE=C PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-26-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-25 (0 days ago) dmi.bios.date: 11/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.C0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X399 GAMING PRO CARBON AC (MS-7B09) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.C0:bd11/14/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B09:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX399GAMINGPROCARBONAC(MS-7B09):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B09 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal possible-manual-nvidia-install resolution ubuntu ** Attachment added: "Screenshot from 2020-04-24 23-02-48.png" https://bugs.launchpad.net/bugs/1874964/+attachment/5360022/+files/Screenshot%20from%202020-04-24%2023-02-48.png -- You received this bug notification because you are a member of Desktop Packages, which is
[Desktop-packages] [Bug 1845046] Re: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected
YEAH!!! Finally Fixed!!! I just tested the bluez proposed update and my headphones connected in A2DP mode the first time (without having to go through all the tricks of connecting/disconnecting bluetooth, etc, etc). I did try powering off and on my headphones several times and it continues to work as expected. I'm a "good-to-go" for this fix. -- 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/1845046 Title: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected Status in bluez package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Invalid Status in bluez source package in Bionic: Fix Committed Status in bluez source package in Eoan: Fix Committed Status in bluez source package in Focal: Fix Released Bug description: [Impact] Whenever I turn on my headphones they'll connect to my computer but I'm able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. [Test Case] 0. Set up your Bluetooth headphones with Ubuntu. 1. Turn off the headphones. 2. Turn on the headphones. 3. In Settings>Sound verify they have reconnected in A2DP mode (stereo, high quality, no microphone support). [Regression Potential] Low. Only the headset code path is affected and the fix has already been released for some time in BlueZ 5.51 onward. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860622] Re: Dependency error installing pulseaudio-esound-compat
Do you know when 1:11.1-1ubuntu7.5 will be re-released? My update Ubuntu installation has the last version installed on Nov 22, 2019. Also, my apt package manager doesn't seem to know about "withdrawals" so the rest of my pulseaudio files remain from 1:11.1-1ubuntu7.5 BTW, I was able to install pulseaudio-esound-compate 11.1-1ubuntu7.5 manually from the site you linked above so your diagnosis seems right. -- 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/1860622 Title: Dependency error installing pulseaudio-esound-compat Status in pulseaudio package in Ubuntu: Fix Committed Bug description: Running: apt-get install pulseaudio-esound-compat I get the following error: The following packages have unmet dependencies: pulseaudio-esound-compat : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is to be installed Depends: pulseaudio (= 1:11.1-1ubuntu7.4) Seems like pulseaudio-esound-compat has not been updated for the latest package versions of libpulse0 and pulseaudio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1860622/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860622] [NEW] Dependency error installing pulseaudio-esound-compat
Public bug reported: Running: apt-get install pulseaudio-esound-compat I get the following error: The following packages have unmet dependencies: pulseaudio-esound-compat : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is to be installed Depends: pulseaudio (= 1:11.1-1ubuntu7.4) Seems like pulseaudio-esound-compat has not been updated for the latest package versions of libpulse0 and pulseaudio. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1860622 Title: Dependency error installing pulseaudio-esound-compat Status in pulseaudio package in Ubuntu: New Bug description: Running: apt-get install pulseaudio-esound-compat I get the following error: The following packages have unmet dependencies: pulseaudio-esound-compat : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is to be installed Depends: pulseaudio (= 1:11.1-1ubuntu7.4) Seems like pulseaudio-esound-compat has not been updated for the latest package versions of libpulse0 and pulseaudio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1860622/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792085] Re: MTP not working/very slow on Bionic
I was able to fix this on Ubuntu 18.04 (bionic), which comes with libmtp-common=1.1.13 by installing a newer version of libmtp 1.1.16. Now Ubuntu transfers huge numbers of songs between my phone and laptop by simply drag-and-drop in Nautilus. sudo apt install build-essential pkg-config wget libusb-1.0-0-dev libusb-dev wget http://downloads.sourceforge.net/project/libmtp/libmtp/1.1.16/libmtp-1.1.16.tar.gz tar xzf libmtp-1.1.16.tar.gz cd libmtp-1.1.16 ./configure make sudo make install I didn't even have to uninstall the old version, and also no need for android-file-transfer or jmtpfs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1792085 Title: MTP not working/very slow on Bionic Status in libmtp: New Status in gvfs package in Ubuntu: Incomplete Bug description: Hi, unfortunately (for me) MTP android devices no more work on Ubuntu 18.04. I have used MTP on 16.04 without problems, but on 18.04 it does not work. When I connect my Android devices (Samsung A5 and Samsung J3) and I try to list directories with many files (e.g. /DCIM/Camera) the window hangs until I disconnect the device. Same issue if I try to post the command "ls /var/run/1000/gvfs/". I have installed Ubuntu 18.04 on two different machines - an older HP laptop and a recent DELL laptop - and the issue is present on the all of them. I suspect a defect on the "libmtp". I tried many alternative solutions suggested by the net (e.g. jmtpfs and so on) but anyone worked. That's all! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs-fuse 1.36.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 12 06:20:07 2018 LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libmtp/+bug/1792085/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
