[Desktop-packages] [Bug 1933913] Re: "Xorg -configure" results in "modprobe: FATAL: Module fbcon not found in directory /lib/modules/5.10.0-7-amd64"
Thanks for the bug report. That actually appears to be a kernel problem, and you appear to be using Debian rather than Ubuntu. So please report the bug to Debian: https://www.debian.org/Bugs/Reporting ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- 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/1933913 Title: "Xorg -configure" results in "modprobe: FATAL: Module fbcon not found in directory /lib/modules/5.10.0-7-amd64" Status in Ubuntu: Invalid Bug description: With x11 not running, this was executed: "Xorg -configure". It should simply build a configuration file. The output below appears in the terminal with an error. It manages to create a config file anyway, but what it creates causes "startx" to fall over. So I am forced to run x11 without a config file (which is a problem for me because I have two displays and need to change the RightOf/LeftOf setting). OUTPUT: X.Org X Server 1.20.11 X Protocol Version 11, Revision 0 Build Operating System: linux Debian Current Operating System: Linux billyikes 5.10.0-7-amd64 #1 SMP Debian 5.10.40-1 (2021-05-28) x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-7-amd64 root=/dev/mapper/grp-root ro rd.luks.name=UUID=279a24dc-1014-6495-38cc-75ce88144f44=cryptdisk quiet Build Date: 13 April 2021 04:07:31PM xorg-server 2:1.20.11-1 (https://www.debian.org/support) Current version of pixman: 0.40.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jun 29 02:19:12 2021 List of video drivers: amdgpu ati intel nouveau qxl radeon vmware modesetting fbdev vesa (++) Using config file: "/root/xorg.conf.new" (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" modprobe: FATAL: Module fbcon not found in directory /lib/modules/5.10.0-7-amd64 intel: waited 2020 ms for i915.ko driver to load Number of created screens does not match number of detected devices. Configuration failed. (EE) Server terminated with error (2). Closing log file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1933913/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933921] [NEW] gnome-system-monitor doesn't show all processes even in "All processes" mode
Public bug reported: As you can see on the attached screenshot, I have two app.asap processes (spawned by gitkraken) which doesn't show in the system monitor process tree ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-system-monitor 3.36.1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-78.87-generic 5.4.124 Uname: Linux 5.4.0-78-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 29 10:11:46 2021 InstallationDate: Installed on 2020-11-24 (216 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to focal on 2020-11-25 (215 days ago) ** Affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Attachment added: "ProcessMonitor.png" https://bugs.launchpad.net/bugs/1933921/+attachment/5507806/+files/ProcessMonitor.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1933921 Title: gnome-system-monitor doesn't show all processes even in "All processes" mode Status in gnome-system-monitor package in Ubuntu: New Bug description: As you can see on the attached screenshot, I have two app.asap processes (spawned by gitkraken) which doesn't show in the system monitor process tree ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-system-monitor 3.36.1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-78.87-generic 5.4.124 Uname: Linux 5.4.0-78-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 29 10:11:46 2021 InstallationDate: Installed on 2020-11-24 (216 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to focal on 2020-11-25 (215 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1933921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1325775] Re: Make it possible to copy command line and other information from process treetable and properties dialog
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-system-monitor (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1325775 Title: Make it possible to copy command line and other information from process treetable and properties dialog Status in gnome-system-monitor package in Ubuntu: Confirmed Bug description: The information provided in columns of the process tree table can no be copied (which would especially interesting for the process command line, but also for PID) as well as the information in the properties dialog of a process. This has no reason and it shouldn't be confusing to add a copy button (for the UI it would be nicer to have a cell based highlighting, but for instance copying the cell value based on the context menu position should be sufficient). version information depend on https://bugs.launchpad.net/ubuntu/+source/gnome-system- monitor/+bug/1325776 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1325775/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881180] Re: drop suru-icon-theme (and use UBports' suru-icon-theme as upstream)
** Project changed: ubuntu-themes => ubuntu-themes (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1881180
Title:
drop suru-icon-theme (and use UBports' suru-icon-theme as upstream)
Status in ubuntu-themes package in Ubuntu:
New
Bug description:
As part of the initiative of packaging Lomiri (former Unity8) for
Debian, I have just created a standalone source project for suru-icon-
theme [1]. This will soon be packaged for and uploaded to Debian
unstable.
The UBports developers have added several changes to "their" suru-
icon-theme which makes it impossible to use suru-icon-theme from the
ubuntu-theme src:pkg on Ubuntu Touch. On the other hand, UBports'
suru-icon-theme should still be good to go with on Ubuntu.
Furthermore, for Debian upload, I preferred not to package the ubuntu
specific artwork as a whole. The solution at UBports upstream was
providing suru-icon-theme as a standalone upstream project.
Thus, I'd like to suggest dropping suru-icon-theme from Ubuntu Theme
(at least the bin:pkg) and use the suru-icon-theme package being
available in Debian soon('ish (dependening on NEW queue processing)).
The UBports devs are open to merge requests if that is required from
time to time.
Thanks+Greets,
Mike (aka sunweaver at debian.org)
[1] https://gitlab.com/ubports/core/suru-icon-theme
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1881180/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881180] [NEW] drop suru-icon-theme (and use UBports' suru-icon-theme as upstream)
You have been subscribed to a public bug:
As part of the initiative of packaging Lomiri (former Unity8) for
Debian, I have just created a standalone source project for suru-icon-
theme [1]. This will soon be packaged for and uploaded to Debian
unstable.
The UBports developers have added several changes to "their" suru-icon-
theme which makes it impossible to use suru-icon-theme from the ubuntu-
theme src:pkg on Ubuntu Touch. On the other hand, UBports' suru-icon-
theme should still be good to go with on Ubuntu.
Furthermore, for Debian upload, I preferred not to package the ubuntu
specific artwork as a whole. The solution at UBports upstream was
providing suru-icon-theme as a standalone upstream project.
Thus, I'd like to suggest dropping suru-icon-theme from Ubuntu Theme (at
least the bin:pkg) and use the suru-icon-theme package being available
in Debian soon('ish (dependening on NEW queue processing)).
The UBports devs are open to merge requests if that is required from
time to time.
Thanks+Greets,
Mike (aka sunweaver at debian.org)
[1] https://gitlab.com/ubports/core/suru-icon-theme
** Affects: ubuntu-themes (Ubuntu)
Importance: Undecided
Status: New
--
drop suru-icon-theme (and use UBports' suru-icon-theme as upstream)
https://bugs.launchpad.net/bugs/1881180
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-themes in Ubuntu.
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933913] [NEW] "Xorg -configure" results in "modprobe: FATAL: Module fbcon not found in directory /lib/modules/5.10.0-7-amd64"
Public bug reported: With x11 not running, this was executed: "Xorg -configure". It should simply build a configuration file. The output below appears in the terminal with an error. It manages to create a config file anyway, but what it creates causes "startx" to fall over. So I am forced to run x11 without a config file (which is a problem for me because I have two displays and need to change the RightOf/LeftOf setting). OUTPUT: X.Org X Server 1.20.11 X Protocol Version 11, Revision 0 Build Operating System: linux Debian Current Operating System: Linux billyikes 5.10.0-7-amd64 #1 SMP Debian 5.10.40-1 (2021-05-28) x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-7-amd64 root=/dev/mapper/grp-root ro rd.luks.name=UUID=279a24dc-1014-6495-38cc-75ce88144f44=cryptdisk quiet Build Date: 13 April 2021 04:07:31PM xorg-server 2:1.20.11-1 (https://www.debian.org/support) Current version of pixman: 0.40.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jun 29 02:19:12 2021 List of video drivers: amdgpu ati intel nouveau qxl radeon vmware modesetting fbdev vesa (++) Using config file: "/root/xorg.conf.new" (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" modprobe: FATAL: Module fbcon not found in directory /lib/modules/5.10.0-7-amd64 intel: waited 2020 ms for i915.ko driver to load Number of created screens does not match number of detected devices. Configuration failed. (EE) Server terminated with error (2). Closing log file. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- 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/1933913 Title: "Xorg -configure" results in "modprobe: FATAL: Module fbcon not found in directory /lib/modules/5.10.0-7-amd64" Status in xorg package in Ubuntu: New Bug description: With x11 not running, this was executed: "Xorg -configure". It should simply build a configuration file. The output below appears in the terminal with an error. It manages to create a config file anyway, but what it creates causes "startx" to fall over. So I am forced to run x11 without a config file (which is a problem for me because I have two displays and need to change the RightOf/LeftOf setting). OUTPUT: X.Org X Server 1.20.11 X Protocol Version 11, Revision 0 Build Operating System: linux Debian Current Operating System: Linux billyikes 5.10.0-7-amd64 #1 SMP Debian 5.10.40-1 (2021-05-28) x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-7-amd64 root=/dev/mapper/grp-root ro rd.luks.name=UUID=279a24dc-1014-6495-38cc-75ce88144f44=cryptdisk quiet Build Date: 13 April 2021 04:07:31PM xorg-server 2:1.20.11-1 (https://www.debian.org/support) Current version of pixman: 0.40.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jun 29 02:19:12 2021 List of video drivers: amdgpu ati intel nouveau qxl radeon vmware modesetting fbdev vesa (++) Using config file: "/root/xorg.conf.new" (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" modprobe: FATAL: Module fbcon not found in directory /lib/modules/5.10.0-7-amd64 intel: waited 2020 ms for i915.ko driver to load Number of created screens does not match number of detected devices. Configuration failed. (EE) Server terminated with error (2). Closing log file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1933913/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933890] Re: No wacom tablet or stylus discovered, Fujitsu T935
Please try logging into both 'Ubuntu' and 'Ubuntu on Xorg', and tell us if both have the same bug. You can select the session type using the button in the bottom right corner of the login screen. ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete ** Tags added: wacom -- 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/1933890 Title: No wacom tablet or stylus discovered, Fujitsu T935 Status in gnome-control-center package in Ubuntu: Incomplete Bug description: I installed Ubuntu 21.04 on my Fujitsu T935, which has a Wacom stylus and screen. The command line seems to find it, and it works fine, but I cannot calibrate it without the gnome-control-center. $ xsetwacom --list devices Wacom MultiTouch Sensor Finger touch id: 10 type: TOUCH Wacom MultiTouch Sensor Pen stylusid: 11 type: STYLUS Wacom MultiTouch Sensor Pen eraserid: 15 type: ERASER Any ideas what to do? Thanks, Rob ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-control-center 1:3.38.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 28 17:45:08 2021 InstallationDate: Installed on 2021-05-25 (34 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1933890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933724] Re: Screen goes blank after login to Wayland session (Aspeed graphics)
Oh, are you saying both Wayland and Xorg logins work now? ** Changed in: mutter (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1933724 Title: Screen goes blank after login to Wayland session (Aspeed graphics) Status in mutter package in Ubuntu: Invalid Bug description: Server with Aspeed built-in graphics system and driver ast. Used to work, but since a few weeks scfeen goes blank after login. Login screen with lightdm works only after boot. User is logged in properly, just screen is left blank. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jun 26 14:35:50 2021 DistUpgraded: ProcessLookupError: [Errno 3] Kein passender Prozess gefunden DistroCodename: focal DistroVariant: ubuntu GraphicsCard: ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 30) (prog-if 00 [VGA controller]) Subsystem: Super Micro Computer Inc ASPEED Graphics Family [15d9:0895] MachineType: Supermicro Super Server ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-59-generic root=UUID=ceb2127b-bad8-4e5a-a9bc-104bde7e6b93 ro rootflags=subvol=@ gfxpayload=true nomdmonddf nomdmonisw intel_iommu=on SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-08-21 (308 days ago) dmi.bios.date: 09/18/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11SAE-F dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd09/18/2020:br5.12:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SAE-F:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: Super Server dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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 xserver.bootTime: Sat Jun 26 14:24:46 2021 xserver.configfile: default xserver.errors: ast: module ABI major version (23) doesn't match the server's version (24) Failed to load module "ast" (module requirement mismatch, 0) ast: module ABI major version (23) doesn't match the server's version (24) Failed to load module "ast" (module requirement mismatch, 0) modeset(0): glamor initialization failed xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.9-2ubuntu1.2~20.04.2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1933724/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933888] Re: Login screen displays unknown user when coming back from blank screen
** Bug watch added: gitlab.gnome.org/GNOME/gdm/-/issues #709 https://gitlab.gnome.org/GNOME/gdm/-/issues/709 ** Also affects: gdm via https://gitlab.gnome.org/GNOME/gdm/-/issues/709 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1933888 Title: Login screen displays unknown user when coming back from blank screen Status in gdm: Unknown Status in gdm3 package in Ubuntu: New Bug description: After updating to Ubuntu 21.04, sometimes after my screen is blanked and locked automatically and I wake it up, the login screen doesn't show my name or picture. It just shows a generic new user photo. If I enter my password, the spinning circle appears next to the password text box and gets stuck that way indefinitely. If instead I press Esc twice, I get back to a login screen with my name and picture and am able to unlock normally. The issue doesn't happen all of the time; I think that the longer I leave my machine idle, the more likely I am to run into it, though. Here's the issue in the GNOME bug tracker, which advised me to file here: https://gitlab.gnome.org/GNOME/gdm/-/issues/709 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gdm3 3.38.2.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 28 16:45:40 2021 InstallationDate: Installed on 2016-01-18 (1988 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: gdm3 UpgradeStatus: Upgraded to hirsute on 2021-06-07 (21 days ago) mtime.conffile..etc.gdm3.custom.conf: 2020-09-09T20:54:43.309931 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1933888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925375] Re: settings goes after work some times into Ubuntu 20.04 LTS 64 bit Desktop
Please explain in more detail what the problem is you are experiencing. If it helps to explain the problem then please also attach photos or a video. ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1925375 Title: settings goes after work some times into Ubuntu 20.04 LTS 64 bit Desktop Status in gnome-control-center package in Ubuntu: Incomplete Bug description: my settings goes after work some times into Ubuntu 20.04 LTS 64 bit Desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1925375/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886732] Re: reports read permission as "photo library folder was not writable"
** Project changed: ubuntuone-shotwell-plugin => shotwell -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1886732 Title: reports read permission as "photo library folder was not writable" Status in Shotwell: Unknown Status in shotwell package in Ubuntu: Triaged Bug description: 1) Ubuntu version: Ubuntu 20.04 LTS 2) shotwell package version: 0.30.10-0ubuntu0.1 3) a. I'm performing "Import from folder" from an external drive. b. This external drive is formatted as HFS+, comes from a Mac, and by default it's mounted as read-only, which is OK. c. As result of the import, some files (both photos and videos) are imported ok, while some others don't. d. For those which are not imported, the error reported in the UI is "953 photos/videos failed to import because the photo library folder was not writable", which doesn't make sense, as some others were imported. Looking further, I came to found in ~/.cache/shotwell/shotwell.log the following pattern: L 3733 2020-07-07 20:47:09 [WRN] BatchImport.vala:1840: Unable to perform MD5 checksum on file : Error opening file : Permission denied L 3733 2020-07-07 20:47:09 [WRN] BatchImport.vala:1405: Import failure : File write error By checking the code, I see convert_error method maps several different error codes to ImportResult.FILE_WRITE_ERROR In particular, lines 124 and 125 map IOError.PERMISSION_DENIED to ImportResult.FILE_WRITE_ERROR else if (ioerr is IOError.PERMISSION_DENIED) return ImportResult.FILE_WRITE_ERROR; But in this case, the permission denied came from the read, and not from the write. BTW: Permission denied has to do with different permissions for those files, so it's ok to not have been imported. 4) It's ok for Shotwell to fail importing files without read permission, but the error message confuses the user, which may understand Shotwell library got corrupted (as on same operation some files were imported and some others don't). A better error message could be "953 photos/videos failed to import because permission was denied to read the source files" To manage notifications about this bug go to: https://bugs.launchpad.net/shotwell/+bug/1886732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925375] Re: settings goes after work some times into Ubuntu 20.04 LTS 64 bit Desktop
** Project changed: payclient => gnome-control-center (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1925375 Title: settings goes after work some times into Ubuntu 20.04 LTS 64 bit Desktop Status in gnome-control-center package in Ubuntu: New Bug description: my settings goes after work some times into Ubuntu 20.04 LTS 64 bit Desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1925375/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933890] [NEW] No wacom tablet or stylus discovered, Fujitsu T935
Public bug reported: I installed Ubuntu 21.04 on my Fujitsu T935, which has a Wacom stylus and screen. The command line seems to find it, and it works fine, but I cannot calibrate it without the gnome-control-center. $ xsetwacom --list devices Wacom MultiTouch Sensor Finger touchid: 10 type: TOUCH Wacom MultiTouch Sensor Pen stylus id: 11 type: STYLUS Wacom MultiTouch Sensor Pen eraser id: 15 type: ERASER Any ideas what to do? Thanks, Rob ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-control-center 1:3.38.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 28 17:45:08 2021 InstallationDate: Installed on 2021-05-25 (34 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- 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/1933890 Title: No wacom tablet or stylus discovered, Fujitsu T935 Status in gnome-control-center package in Ubuntu: New Bug description: I installed Ubuntu 21.04 on my Fujitsu T935, which has a Wacom stylus and screen. The command line seems to find it, and it works fine, but I cannot calibrate it without the gnome-control-center. $ xsetwacom --list devices Wacom MultiTouch Sensor Finger touch id: 10 type: TOUCH Wacom MultiTouch Sensor Pen stylusid: 11 type: STYLUS Wacom MultiTouch Sensor Pen eraserid: 15 type: ERASER Any ideas what to do? Thanks, Rob ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-control-center 1:3.38.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 28 17:45:08 2021 InstallationDate: Installed on 2021-05-25 (34 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1933890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925375] [NEW] settings goes after work some times into Ubuntu 20.04 LTS 64 bit Desktop
You have been subscribed to a public bug: my settings goes after work some times into Ubuntu 20.04 LTS 64 bit Desktop ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- settings goes after work some times into Ubuntu 20.04 LTS 64 bit Desktop https://bugs.launchpad.net/bugs/1925375 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933889] [NEW] Unmounted SD card does not show it is unmounted
Public bug reported: Normally, I unmount an SD card by clicking on the little arrow symbol beside it in the left panel of nautilus. Normally, the little symbol disappears when I do that. Today, I went to do that, and it is still there. If I click on it again, it complains "No object for D-Bus interface." Before first clicking to unmount it, I find it in /media/username/ but after first clicking to unmount it it is gone from there, which seems to indicate that it did actually unmount. This is confusing. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Jun 28 17:32:59 2021 GsettingsChanges: InstallationDate: Installed on 2021-05-25 (34 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince40.1-1 file-roller 3.38.1-1 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1 nautilus-share0.7.3-2ubuntu3 python3-nautilus 1.2.3-3build1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1933889 Title: Unmounted SD card does not show it is unmounted Status in nautilus package in Ubuntu: New Bug description: Normally, I unmount an SD card by clicking on the little arrow symbol beside it in the left panel of nautilus. Normally, the little symbol disappears when I do that. Today, I went to do that, and it is still there. If I click on it again, it complains "No object for D-Bus interface." Before first clicking to unmount it, I find it in /media/username/ but after first clicking to unmount it it is gone from there, which seems to indicate that it did actually unmount. This is confusing. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Jun 28 17:32:59 2021 GsettingsChanges: InstallationDate: Installed on 2021-05-25 (34 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince40.1-1 file-roller 3.38.1-1 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1 nautilus-share0.7.3-2ubuntu3 python3-nautilus 1.2.3-3build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1933889/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933717] Re: Backup messages in wrong language
This looks to be an Ubuntu translation error. The current package of language-pack-gnome-en-base has some German phrases in its en_GB translations for deja-dup! Looks like they were fixed in May in the Ubuntu translation sources: https://translations.launchpad.net/ubuntu/hirsute/+source/deja-dup/+pots /deja-dup/en_GB/+translate But that hasn't made it back into 21.04 yet. :-/ ** Project changed: deja-dup => deja-dup (Ubuntu) ** Changed in: deja-dup (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1933717 Title: Backup messages in wrong language Status in deja-dup package in Ubuntu: Confirmed Bug description: My system is set to use UK English, and has never used German. When a backup completes I get the mixed language message: Backup Finished Aber nicht alle Dateien wurden erfolgreich gesichert See the attached screenshot. Ubuntu 21.04 Deja dup version 42.7 $ dconf dump /org/gnome/deja-dup/ [/] backend='google' delete-after=182 last-backup='2021-06-26T10:00:30Z' last-run='2021-06-26T09:12:53Z' nag-check='2021-06-16T10:40:36Z' periodic=true periodic-period=1 prompt-check='disabled' [file] migrated=true [gcs] folder='anthony-System-Product-Name' [goa] type='google' [google] folder='Ubuntu-backups' [local] folder='anthony-System-Product-Name' [openstack] container='anthony-System-Product-Name' [rackspace] container='anthony-System-Product-Name' [remote] folder='anthony-System-Product-Name' [s3] folder='anthony-System-Product-Name' $ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1933717/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933717] [NEW] Backup messages in wrong language
You have been subscribed to a public bug: My system is set to use UK English, and has never used German. When a backup completes I get the mixed language message: Backup Finished Aber nicht alle Dateien wurden erfolgreich gesichert See the attached screenshot. Ubuntu 21.04 Deja dup version 42.7 $ dconf dump /org/gnome/deja-dup/ [/] backend='google' delete-after=182 last-backup='2021-06-26T10:00:30Z' last-run='2021-06-26T09:12:53Z' nag-check='2021-06-16T10:40:36Z' periodic=true periodic-period=1 prompt-check='disabled' [file] migrated=true [gcs] folder='anthony-System-Product-Name' [goa] type='google' [google] folder='Ubuntu-backups' [local] folder='anthony-System-Product-Name' [openstack] container='anthony-System-Product-Name' [rackspace] container='anthony-System-Product-Name' [remote] folder='anthony-System-Product-Name' [s3] folder='anthony-System-Product-Name' $ ** Affects: deja-dup (Ubuntu) Importance: Undecided Status: Confirmed -- Backup messages in wrong language https://bugs.launchpad.net/bugs/1933717 You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933888] [NEW] Login screen displays unknown user when coming back from blank screen
Public bug reported: After updating to Ubuntu 21.04, sometimes after my screen is blanked and locked automatically and I wake it up, the login screen doesn't show my name or picture. It just shows a generic new user photo. If I enter my password, the spinning circle appears next to the password text box and gets stuck that way indefinitely. If instead I press Esc twice, I get back to a login screen with my name and picture and am able to unlock normally. The issue doesn't happen all of the time; I think that the longer I leave my machine idle, the more likely I am to run into it, though. Here's the issue in the GNOME bug tracker, which advised me to file here: https://gitlab.gnome.org/GNOME/gdm/-/issues/709 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gdm3 3.38.2.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 28 16:45:40 2021 InstallationDate: Installed on 2016-01-18 (1988 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: gdm3 UpgradeStatus: Upgraded to hirsute on 2021-06-07 (21 days ago) mtime.conffile..etc.gdm3.custom.conf: 2020-09-09T20:54:43.309931 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1933888 Title: Login screen displays unknown user when coming back from blank screen Status in gdm3 package in Ubuntu: New Bug description: After updating to Ubuntu 21.04, sometimes after my screen is blanked and locked automatically and I wake it up, the login screen doesn't show my name or picture. It just shows a generic new user photo. If I enter my password, the spinning circle appears next to the password text box and gets stuck that way indefinitely. If instead I press Esc twice, I get back to a login screen with my name and picture and am able to unlock normally. The issue doesn't happen all of the time; I think that the longer I leave my machine idle, the more likely I am to run into it, though. Here's the issue in the GNOME bug tracker, which advised me to file here: https://gitlab.gnome.org/GNOME/gdm/-/issues/709 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gdm3 3.38.2.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 28 16:45:40 2021 InstallationDate: Installed on 2016-01-18 (1988 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: gdm3 UpgradeStatus: Upgraded to hirsute on 2021-06-07 (21 days ago) mtime.conffile..etc.gdm3.custom.conf: 2020-09-09T20:54:43.309931 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1933888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1932990] Re: cannot create user data directory: /opt/appserver/snap/chromium/1646: Permission denied
I am investigating whether I can fix the error by using an option, '--user-data-dir=/tmp', when I launch the chromiumdriver. First, snap has made the use of this simple tool, chromiumdriver, much more complex. Second, I have tried to uninstall the snap version of the tool and I cannot now install a non-snap version. Somehow snap has soured the soup. If it is going to cause these kinds of problems, I am certainly not going to be trying to use snap for other tools unless I have to. If the install requirements are very complex, such as with installing certificates, snap is a good thing. But when the install process is simple, one should not use snap? Is that the solution? -- 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/1932990 Title: cannot create user data directory: /opt/appserver/snap/chromium/1646: Permission denied Status in chromium-browser package in Ubuntu: New Bug description: All I am getting is: cannot create user data directory: /opt/appserver/snap/chromium/1646: Permission denied Jun 18, 2021 9:11:36 PM org.openqa.selenium.os.OsProcess checkForError But: # ls -ld /opt/appserver/snap/chromium/1646 drwxr-xr-x 2 appserver appserveradm 4096 Jun 18 20:46 /opt/appserver/snap/chromium/1646 The application (a java app) that is making the call to selenium is owned by appserver. So what could the problem be? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1932990/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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 1933724] Re: Screen goes blank after login to Wayland session (Aspeed graphics)
Using "ubuntu" at log-in did not solve it. A full power-cycle of the server did now resolve it. Before I did only reboots. Looks like the BMC/Aspeed required a full power off to reset properly. Ticket can be closed, please. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1933724 Title: Screen goes blank after login to Wayland session (Aspeed graphics) Status in mutter package in Ubuntu: Triaged Bug description: Server with Aspeed built-in graphics system and driver ast. Used to work, but since a few weeks scfeen goes blank after login. Login screen with lightdm works only after boot. User is logged in properly, just screen is left blank. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jun 26 14:35:50 2021 DistUpgraded: ProcessLookupError: [Errno 3] Kein passender Prozess gefunden DistroCodename: focal DistroVariant: ubuntu GraphicsCard: ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 30) (prog-if 00 [VGA controller]) Subsystem: Super Micro Computer Inc ASPEED Graphics Family [15d9:0895] MachineType: Supermicro Super Server ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-59-generic root=UUID=ceb2127b-bad8-4e5a-a9bc-104bde7e6b93 ro rootflags=subvol=@ gfxpayload=true nomdmonddf nomdmonisw intel_iommu=on SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-08-21 (308 days ago) dmi.bios.date: 09/18/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11SAE-F dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd09/18/2020:br5.12:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SAE-F:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: Super Server dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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 xserver.bootTime: Sat Jun 26 14:24:46 2021 xserver.configfile: default xserver.errors: ast: module ABI major version (23) doesn't match the server's version (24) Failed to load module "ast" (module requirement mismatch, 0) ast: module ABI major version (23) doesn't match the server's version (24) Failed to load module "ast" (module requirement mismatch, 0) modeset(0): glamor initialization failed xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.9-2ubuntu1.2~20.04.2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1933724/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933864] [NEW] Bluetooth sound card not detected.
Public bug reported: When the laptop starts then i can not turn bluetooth on, it remains off. To make bluetooth work i need to disable wifi and bluetooth hardware for a few minutes then enable it. 90 percent time it works. if this didn't start the service then enabling and disabling airplane mode works. Some times it really frustrates. kindly look at this bug. I have this old laptop through which i study. thanks in advance. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: overlord 1464 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 28 23:35:37 2021 InstallationDate: Installed on 2021-06-22 (6 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2011 dmi.bios.release: 15.4 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.04 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1668 dmi.board.vendor: Hewlett-Packard dmi.board.version: 08.10 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.ec.firmware.release: 8.16 dmi.modalias: dmi:bvnHewlett-Packard:bvrF.04:bd02/11/2011:br15.4:efr8.16:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr059F100046100:rvnHewlett-Packard:rn1668:rvr08.10:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: LN246EA#A2N dmi.product.version: 059F100046100 dmi.sys.vendor: Hewlett-Packard ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1933864 Title: Bluetooth sound card not detected. Status in alsa-driver package in Ubuntu: New Bug description: When the laptop starts then i can not turn bluetooth on, it remains off. To make bluetooth work i need to disable wifi and bluetooth hardware for a few minutes then enable it. 90 percent time it works. if this didn't start the service then enabling and disabling airplane mode works. Some times it really frustrates. kindly look at this bug. I have this old laptop through which i study. thanks in advance. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: overlord 1464 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 28 23:35:37 2021 InstallationDate: Installed on 2021-06-22 (6 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2011 dmi.bios.release: 15.4 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.04 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1668 dmi.board.vendor: Hewlett-Packard dmi.board.version: 08.10 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.ec.firmware.release: 8.16 dmi.modalias: dmi:bvnHewlett-Packard:bvrF.04:bd02/11/2011:br15.4:efr8.16:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr059F100046100:rvnHewlett-Packard:rn1668:rvr08.10:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: LN246EA#A2N dmi.product.version: 059F100046100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1933864/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931301] Re: NIC unavailable after suspend to RAM
> Trying to ifconfig it down/up results in: > SIOCSIFFLAGS: No such device that likely means the kernel driver had some problem waking the device back up, but there's no dmesg attached to the bug so i don't know. This is probably a bug in the 'alx' kernel driver (or, problem with the hardware), not network-manager. ** Package changed: network-manager (Ubuntu) => linux (Ubuntu) -- 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/1931301 Title: NIC unavailable after suspend to RAM Status in linux package in Ubuntu: Confirmed Bug description: Upgraded to 21.04 (hirsute) and now the network card is unavailable after suspend to RAM (sleep state S3). It worked flawlessly up until 20.10. My workaround for now is unloading and reloading the kernel module, but that won't work for normal users, hence this report. NIC in its unavailable state: 2: enp4s0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether d0:50:99:27:02:11 brd ff:ff:ff:ff:ff:ff NIC (from lspci): 04:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 10) Trying to ifconfig it down/up results in: SIOCSIFFLAGS: No such device journalctl shows (right after recovering from suspend): NetworkManager[1911]: [1623181236.9371] manager: sleep: wake requested (sleeping: yes enabled: yes) NetworkManager[1911]: [1623181236.9372] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') NetworkManager[1911]: [1623181236.9382] manager: NetworkManager state is now CONNECTED_LOCAL ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Jun 8 21:59:15 2021 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-25 (1748 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to hirsute on 2021-06-04 (4 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931301/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906741] Re: Firefox sometimes causes garbled audio
Also, disabled media.webspeech.synth.enabled in Firefox, but that did not solve the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1906741 Title: Firefox sometimes causes garbled audio Status in firefox package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Opening certain applications/websites at the same time as Firefox causes the audio to become garbled. The audio sounds distorted with an echo. Certain actions are guaranteed to cause this, but it can also happening when only running instances of Firefox. I've been able to consistently cause this by launching Zoom from a link within Firefox. This does not occur when using Chrome. The only way to fix the issue is to shut down all audio-related programs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 83.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rdevans 55475 F pulseaudio /dev/snd/controlC0: rdevans 55475 F pulseaudio /dev/snd/controlC3: rdevans 55475 F pulseaudio /dev/snd/controlC1: rdevans 55475 F pulseaudio BuildID: 20201112153044 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Dec 3 16:55:36 2020 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-10-20 (1140 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 10.0.0.1 dev enp7s0 proto dhcp metric 100 10.0.0.0/24 dev enp7s0 proto kernel scope link src 10.0.0.7 metric 100 169.254.0.0/16 dev enp7s0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:354 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=83.0/20201112153044 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2020-11-12 (21 days ago) dmi.bios.date: 02/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.40 dmi.board.name: H67M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd02/18/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH67M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1906741/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906741] Re: Firefox sometimes causes garbled audio
Same issue here. Garbled noises are being heard on top of my music (playing in the background via Rhythmbox) after starting Firefox and visiting some random website. My desktop is an AMD Ryzen on a Gigabyte X570 mobo with an nVidia GeForce GTX 1060 3GB GPU. Like others noted, the noises seem stop for a while when I change the Output Device from "Line Out - Starship/Matisse" to "HDMI / DisplayPort X - GP106 High Definition Audio Controller". But after some minutes playback (or perhaps visiting some other page with firefox?), the garbled noises appear again... Also, like others, the noises disappear if I close Firefox... uname -a Linux ryzen 5.8.0-59-generic #66~20.04.1-Ubuntu SMP Thu Jun 17 11:14:10 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux sudo dmidecode -t 2 # dmidecode 3.2 Getting SMBIOS data from sysfs. SMBIOS 3.3.0 present. # SMBIOS implementations newer than version 3.2.0 are not # fully supported by this version of dmidecode. Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: Gigabyte Technology Co., Ltd. Product Name: X570 GAMING X Version: Default string Serial Number: Default string Asset Tag: Default string Features: Board is a hosting board Board is replaceable Location In Chassis: Default string Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 sudo lshw -C sound [sudo] password for dimitris: *-multimedia description: Audio device product: GP106 High Definition Audio Controller vendor: NVIDIA Corporation physical id: 0.1 bus info: pci@:08:00.1 version: a1 width: 32 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=snd_hda_intel latency=0 resources: irq:127 memory:fc08-fc083fff *-usb:0 description: Video product: Webcam C270 vendor: Logitech, Inc. physical id: 3 bus info: usb@5:3 version: 0.12 serial: 212F66E0 capabilities: usb-2.00 configuration: driver=snd-usb-audio maxpower=500mA speed=480Mbit/s *-multimedia description: Audio device product: Starship/Matisse HD Audio Controller vendor: Advanced Micro Devices, Inc. [AMD] physical id: 0.4 bus info: pci@:0a:00.4 version: 00 width: 32 bits clock: 33MHz capabilities: pm pciexpress msi bus_master cap_list configuration: driver=snd_hda_intel latency=0 resources: irq:129 memory:fc90-fc907fff lspci | grep Audio 08:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev a1) 0a:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller dpkg -l | grep firefox ii firefox89.0.1+build1-0ubuntu0.20.04.1 amd64Safe and easy web browser from Mozilla -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1906741 Title: Firefox sometimes causes garbled audio Status in firefox package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Opening certain applications/websites at the same time as Firefox causes the audio to become garbled. The audio sounds distorted with an echo. Certain actions are guaranteed to cause this, but it can also happening when only running instances of Firefox. I've been able to consistently cause this by launching Zoom from a link within Firefox. This does not occur when using Chrome. The only way to fix the issue is to shut down all audio-related programs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 83.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rdevans 55475 F pulseaudio /dev/snd/controlC0: rdevans 55475 F pulseaudio /dev/snd/controlC3: rdevans 55475 F pulseaudio /dev/snd/controlC1: rdevans 55475 F pulseaudio BuildID: 20201112153044 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Dec 3 16:55:36 2020 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-10-20 (1140 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release
[Desktop-packages] [Bug 1930937] Re: Default dependency resolution in Focal pulls in full GNOME Desktop
@SRU team: please accept screen-resolution-extra 0.18.0.21.04.1, 0.18.0.20.10.1, and 0.18.0.20.04.1 into -proposed. ** Description changed: In Bionic, screen-resolution-extra has a dependency on policykit-1-gnome | polkit-1-auth-agent. Focal replaces this with a dependency on gnome- shell | policykit-1-gnome | polkit-1-auth-agent. As a result, when install screen-resolution-extra (e.g. as a dependency of nvidia- settings) on a system that doesn't already have GNOME or another polkit auth agent installed, the default dependency resolution pulls in a full GNOME desktop in Focal, while it does not do so under the same circumstances in Bionic. This can be worked around by explicitly installing policykit-1-gnome (or another package which provides the polkit-1-auth-agent virtual package), but it would be nice to not pull in GNOME by default on a system that doesn't already have it. + + [Impact] + + * Installing the nvidia-settings package causes gnome-shell to be + installed. This is less than ideal on servers. + + [Fix] + + * Moving policykit-1-gnome ahead as the first of the polkit dependencies + will solve the problem. + + [Test Case] + + * Install screen-resolution-extra from proposed on a system where no + polkit-1-auth-agent provider is installed, and check that gnome-shell is + not installed as a dependency. + + [Regression Risk] + Low, as the change will still allow the dependency to be satisfied. ** Summary changed: - Default dependency resolution in Focal pulls in full GNOME Desktop + SRU: Default dependency resolution in Focal pulls in full GNOME Desktop -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to screen-resolution-extra in Ubuntu. https://bugs.launchpad.net/bugs/1930937 Title: SRU: Default dependency resolution in Focal pulls in full GNOME Desktop Status in screen-resolution-extra package in Ubuntu: Triaged Status in screen-resolution-extra source package in Focal: Triaged Status in screen-resolution-extra source package in Groovy: Triaged Status in screen-resolution-extra source package in Hirsute: Triaged Bug description: In Bionic, screen-resolution-extra has a dependency on policykit-1-gnome | polkit-1-auth-agent. Focal replaces this with a dependency on gnome-shell | policykit-1-gnome | polkit-1-auth-agent. As a result, when install screen-resolution-extra (e.g. as a dependency of nvidia-settings) on a system that doesn't already have GNOME or another polkit auth agent installed, the default dependency resolution pulls in a full GNOME desktop in Focal, while it does not do so under the same circumstances in Bionic. This can be worked around by explicitly installing policykit-1-gnome (or another package which provides the polkit-1-auth-agent virtual package), but it would be nice to not pull in GNOME by default on a system that doesn't already have it. [Impact] * Installing the nvidia-settings package causes gnome-shell to be installed. This is less than ideal on servers. [Fix] * Moving policykit-1-gnome ahead as the first of the polkit dependencies will solve the problem. [Test Case] * Install screen-resolution-extra from proposed on a system where no polkit-1-auth-agent provider is installed, and check that gnome-shell is not installed as a dependency. [Regression Risk] Low, as the change will still allow the dependency to be satisfied. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1930937/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930937] Re: Default dependency resolution in Focal pulls in full GNOME Desktop
** No longer affects: screen-resolution-extra (Ubuntu Bionic) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to screen-resolution-extra in Ubuntu. https://bugs.launchpad.net/bugs/1930937 Title: Default dependency resolution in Focal pulls in full GNOME Desktop Status in screen-resolution-extra package in Ubuntu: Triaged Status in screen-resolution-extra source package in Focal: Triaged Status in screen-resolution-extra source package in Groovy: Triaged Status in screen-resolution-extra source package in Hirsute: Triaged Bug description: In Bionic, screen-resolution-extra has a dependency on policykit-1-gnome | polkit-1-auth-agent. Focal replaces this with a dependency on gnome-shell | policykit-1-gnome | polkit-1-auth-agent. As a result, when install screen-resolution-extra (e.g. as a dependency of nvidia-settings) on a system that doesn't already have GNOME or another polkit auth agent installed, the default dependency resolution pulls in a full GNOME desktop in Focal, while it does not do so under the same circumstances in Bionic. This can be worked around by explicitly installing policykit-1-gnome (or another package which provides the polkit-1-auth-agent virtual package), but it would be nice to not pull in GNOME by default on a system that doesn't already have it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1930937/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930721] Re: Issue after update Ubuntu on version 21. Firefox often freeze
Firefox 89.0.2 was published to all supported Ubuntu releases, so I'm tentatively marking this fixed. Please re-open if this isn't the case. ** Changed in: firefox (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1930721 Title: Issue after update Ubuntu on version 21. Firefox often freeze Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Bug report: I have the same issue on both versions of Firefox. On deb. and snap version I have issue after update Ubuntu on version 21. Firefox often freeze. Can you please help me and repair it? Is possible automatically send diagnostic data for Ubuntu and Firefox developers during freeze? I am sorry, I am not IT expert ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 89.0+build2-0ubuntu0.21.04.1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BuildID: 20210527174632 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jun 3 15:20:50 2021 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sk_SK.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: Upgraded to hirsute on 2021-05-14 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1930721/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933828] Re: NTP servers from DCHP are not propagated to timesyncd
Updates version of the script. ** Attachment added: "10-update-timesyncd" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1933828/+attachment/5507668/+files/10-update-timesyncd -- 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/1933828 Title: NTP servers from DCHP are not propagated to timesyncd Status in network-manager package in Ubuntu: New Bug description: Network manager gets NTP servers from DHCP but do not update timesyncd to use it which keeps using ntp.ubuntu.com. This is a problem on private networks which do not have access to public internet. On this type of network the configuration of timesyncd must be updated manually instead of inheriting the conf from the dhcp servers. This can be integrated with a NM dispatcher script such as below: etc/NetworkManager/dispatcher.d/10-update-timesyncd for example: ==8<=8<=8<=8<=8<== #! /usr/bin/bash [ -n "$CONNECTION_UUID" ] || exit INTERFACE=$1 ACTION=$2 case $ACTION in up | dhcp4-change | dhcp6-change) [ -n "$DHCP4_NTP_SERVERS" ] || exit mkdir -p /etc/systemd/timesyncd.conf.d/ cat< /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf [Time] NTP=$DHCP4_NTP_SERVERS RootDistanceMaxSec=15 EOF systemctl restart systemd-timesyncd ;; down) rm -f /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf systemctl restart systemd-timesyncd ;; esac ==8<=8<=8<=8<=8<== ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 28 14:08:52 2021 InstallationDate: Installed on 2020-05-31 (393 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) RebootRequiredPkgs: linux-image-5.11.0-20-generic linux-base SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1933828/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1909297] Re: cups missing write permission (for sendmessage operation) in apparmor
Hi, I got fed up and figured out how to configure apparmor to allow it. I added # *** Added by rew. /run/systemd/notify rw, near line 108 of /etc/apparmor.d/usr.sbin.cupsd That solves it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1909297 Title: cups missing write permission (for sendmessage operation) in apparmor Status in cups package in Ubuntu: Confirmed Bug description: After updating recent version of cups (2.3.3op1-3ubuntu1) : I have started to get errors about its missing permissions on journal audit[29527]: AVC apparmor="DENIED" operation="sendmsg" profile="/usr/sbin/cupsd" name="/run/systemd/notify" pid=29527 comm="cupsd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 kernel: audit: type=1400 audit(1608880333.084:56): apparmor="DENIED" operation="sendmsg" profile="/usr/sbin/cupsd" name="/run/systemd/notify" pid=29527 comm="cupsd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: E [25/Dec/2020:10:11:15 +0300] [CGI] ippfind (PID 12144) stopped with status 1! CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-12-25 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201224) KernLog: Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: LENOVO INVALID NonfreeKernelModules: nvidia_modeset nvidia Package: cups 2.3.3op1-3ubuntu1 PackageArchitecture: amd64 Papersize: a4 ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-34-generic root=UUID=b42aef37-b541-43bb-bef8-2dcb8f34df09 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-34-generic root=UUID=b42aef37-b541-43bb-bef8-2dcb8f34df09 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-34.37+21.04.1-generic 5.8.18 Tags: hirsute package-from-proposed Uname: Linux 5.8.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/11/2019 dmi.bios.release: 1.45 dmi.bios.vendor: LENOVO dmi.bios.version: 4KCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: INVALID dmi.ec.firmware.release: 1.45 dmi.modalias: dmi:bvnLENOVO:bvr4KCN45WW:bd01/11/2019:br1.45:efr1.45:svnLENOVO:pnINVALID:pvrINVALID:rvnLENOVO:rnVIUU4:rvrNODPK:cvnLENOVO:ct10:cvrINVALID: dmi.product.family: IDEAPAD dmi.product.name: INVALID dmi.product.sku: LENOVO_BI_IDEAPAD4K_BU_idea_FM_ dmi.product.version: INVALID dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1909297/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows
I'm seeing the same thing after the recent update to Thunderbird 78.11. Ubuntu 21.04 on Wayland. x11 is ok. In my case it appears to be related to the Reminder dialogue opening. Some more details: Start Thunderbird and make sure the Reminder dialogue does not open (eg by snoozing any reminders in a previous session). Open a few emails in new windows - everything works as normal. Now set a calendar entry for a few minutes and wait for the reminder dialogue to pop up. Icon on dock shows indicator showing two open window Open an email in a new window Icon on dock shows indicator showing three open windows Close email Icon on dock still shows indicator showing three open windows Icon on dock is now unresponsive to left click. Right-click shows the menu listing all the windows you have opened, but is unresponsive and stays on the screen. It goes if you press "Super" twice. Then switch to Thunderbird using Alt-tab Repeat until more than 4 windows have been opened - icon show the maximum 4 indicators. Close Thunderbird using Quit from the menu (ps shows no running Thunderbird processes) Dock still shows icon with 4 indicators Left or right click no longer does anything. A middle-click starts a new instance of Thunderbird. -- 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/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows Status in thunderbird package in Ubuntu: Confirmed Bug description: Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default. Thunderbird version: 78.11.0 with "gnome-support" package. Same problem in safe mode. Description: By default in this context, TB is a Wayland task. When opening a compose windows (or reply or transfer), sending mail apparently close the windows, but gnome shell continue to show multiple "points", as if multiple windows are still active. And after closing TB, it seems maintained in the same state, so it becomes impossible to relaunch it from the desk. But task manager of "looking glass" do not show it and it is possible to launch from terminal. Provisional solution: Modify .desktop file to launch with --display=:0 option, that force to use XWayland interface, as shown by xlsclients (for example). But it is actually a bug under Wayland context, that also badly interfer with many add-ons or extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1932328/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: thunderbird (Ubuntu) Status: New => Confirmed -- 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/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows Status in thunderbird package in Ubuntu: Confirmed Bug description: Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default. Thunderbird version: 78.11.0 with "gnome-support" package. Same problem in safe mode. Description: By default in this context, TB is a Wayland task. When opening a compose windows (or reply or transfer), sending mail apparently close the windows, but gnome shell continue to show multiple "points", as if multiple windows are still active. And after closing TB, it seems maintained in the same state, so it becomes impossible to relaunch it from the desk. But task manager of "looking glass" do not show it and it is possible to launch from terminal. Provisional solution: Modify .desktop file to launch with --display=:0 option, that force to use XWayland interface, as shown by xlsclients (for example). But it is actually a bug under Wayland context, that also badly interfer with many add-ons or extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1932328/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933828] [NEW] NTP servers from DCHP are not propagated to timesyncd
Public bug reported: Network manager gets NTP servers from DHCP but do not update timesyncd to use it which keeps using ntp.ubuntu.com. This is a problem on private networks which do not have access to public internet. On this type of network the configuration of timesyncd must be updated manually instead of inheriting the conf from the dhcp servers. This can be integrated with a NM dispatcher script such as below: etc/NetworkManager/dispatcher.d/10-update-timesyncd for example: ==8<=8<=8<=8<=8<== #! /usr/bin/bash [ -n "$CONNECTION_UUID" ] || exit INTERFACE=$1 ACTION=$2 case $ACTION in up | dhcp4-change | dhcp6-change) [ -n "$DHCP4_NTP_SERVERS" ] || exit mkdir -p /etc/systemd/timesyncd.conf.d/ cat< /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf [Time] NTP=$DHCP4_NTP_SERVERS RootDistanceMaxSec=15 EOF systemctl restart systemd-timesyncd ;; down) rm -f /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf systemctl restart systemd-timesyncd ;; esac ==8<=8<=8<=8<=8<== ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 28 14:08:52 2021 InstallationDate: Installed on 2020-05-31 (393 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) RebootRequiredPkgs: linux-image-5.11.0-20-generic linux-base SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled disabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: High Status: New ** Tags: amd64 apport-bug impish ** Changed in: network-manager (Ubuntu) Importance: Undecided => High -- 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/1933828 Title: NTP servers from DCHP are not propagated to timesyncd Status in network-manager package in Ubuntu: New Bug description: Network manager gets NTP servers from DHCP but do not update timesyncd to use it which keeps using ntp.ubuntu.com. This is a problem on private networks which do not have access to public internet. On this type of network the configuration of timesyncd must be updated manually instead of inheriting the conf from the dhcp servers. This can be integrated with a NM dispatcher script such as below: etc/NetworkManager/dispatcher.d/10-update-timesyncd for example: ==8<=8<=8<=8<=8<== #! /usr/bin/bash [ -n "$CONNECTION_UUID" ] || exit INTERFACE=$1 ACTION=$2 case $ACTION in up | dhcp4-change | dhcp6-change) [ -n "$DHCP4_NTP_SERVERS" ] || exit mkdir -p /etc/systemd/timesyncd.conf.d/ cat< /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf [Time] NTP=$DHCP4_NTP_SERVERS RootDistanceMaxSec=15 EOF systemctl restart systemd-timesyncd ;; down) rm -f /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf systemctl restart systemd-timesyncd ;; esac ==8<=8<=8<=8<=8<== ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 28 14:08:52 2021 InstallationDate: Installed on 2020-05-31 (393 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) RebootRequiredPkgs: linux-image-5.11.0-20-generic linux-base SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1933828/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931547] Re: DisplayLink displays are black after Mesa update
@vanvugt What's the ETA for the point release? -- 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/1931547 Title: DisplayLink displays are black after Mesa update Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Triaged Status in xorg-server source package in Focal: New Status in xorg-server source package in Hirsute: New Bug description: Please incorporate xorg-server fix for issue: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1183 It was already merged in to xserver master and xserver-1.20-branch branches. https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/681 https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/683 This is reported by our users reports on Ubuntu 20.10 with Xserver-1.20.9 and on Ubuntu 21.04 with XServer-1.20.11 If it is required i am willing to help with anything. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1931547/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914374] Re: Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image
** Changed in: ubiquity (Ubuntu) Assignee: jean fourie (jeanjpfmainten2) => (unassigned) -- 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/1914374 Title: Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image Status in OEM Priority Project: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubiquity source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubiquity source package in Groovy: Won't Fix Status in ubuntu-drivers-common source package in Groovy: Won't Fix Bug description: I've installed the focal-desktop-amd64.iso image with SHA-256 sum b928163990d9e148605c230c5d3e7bc563bb67269d551f741abc804553f3477c from http://cdimage.ubuntu.com/focal/daily-live/20210202.1/ on the HP ZBook 15 G7 laptop (CID 202009-28216). There are multiple issues: * The graphical desktop isn't launched. The screen remains black except for a cursor blinking erratically in the top left corner of the screen. If I hammer Control+Alt+F[12345] for a while, the graphical desktop starts eventually. * The screen resolution is 3840x2160 but there is no scaling, so everything is tiny. * The touchpad does not work. * WLAN does not work. * Ethernet does not work. I tried two dongles (a USB A as well as a USB C dongle). * No sound. $ cat /proc/version_signature Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 $ lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1914374/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866473] Re: [ZenBook UX431FAC_UX431FA, Realtek ALC294, Speaker, Internal] Playback problem
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1866473 Title: [ZenBook UX431FAC_UX431FA, Realtek ALC294, Speaker, Internal] Playback problem Status in alsa-driver package in Ubuntu: Confirmed Bug description: Speakers not sound, only headphones work in alsamixer everything seem to be ok speakers has enough gain and turn off when connect minijack. Headphones sound but when i disconect them speaker not sound if i open pauvcontrol is playing sound but cant hear it. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mariajo1534 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Mar 7 16:05:00 2020 InstallationDate: Installed on 2020-03-06 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Audio Interno - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: Only some of outputs are working Title: [ZenBook UX431FAC_UX431FA, Realtek ALC294, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX431FAC.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX431FAC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX431FAC.204:bd10/18/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FAC_UX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FAC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX431FAC_UX431FA 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/alsa-driver/+bug/1866473/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933803] [NEW] No notifications on events of Gnome Calendar on XUbuntu
Public bug reported: To reproduce: 1. Create an event 2. Add a 5 minute before the event reminder 3. Wait 5 minutes until the event What happens: * Nothing What i expect to happen: * Some sort of notification, preferably with sound Gnome Calendar version: 3.36.2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-calendar 3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114 Uname: Linux 5.4.0-74-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Jun 28 11:00:14 2021 InstallationDate: Installed on 2021-01-13 (165 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-calendar (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-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1933803 Title: No notifications on events of Gnome Calendar on XUbuntu Status in gnome-calendar package in Ubuntu: New Bug description: To reproduce: 1. Create an event 2. Add a 5 minute before the event reminder 3. Wait 5 minutes until the event What happens: * Nothing What i expect to happen: * Some sort of notification, preferably with sound Gnome Calendar version: 3.36.2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-calendar 3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114 Uname: Linux 5.4.0-74-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Jun 28 11:00:14 2021 InstallationDate: Installed on 2021-01-13 (165 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1933803/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933799] Re: /usr/bin/gnome-shell:11:rescan_icon_theme:installed_changed:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4420 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4420 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4420 Importance: Unknown Status: Unknown ** Summary changed: - /usr/bin/gnome-shell:11:rescan_icon_theme:installed_changed:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist + gnome-shell crashed with SIGSEGV in rescan_icon_theme() from installed_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1933799 Title: gnome-shell crashed with SIGSEGV in rescan_icon_theme() from installed_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.4-1ubuntu3, the problem page at https://errors.ubuntu.com/problem/0743486472675f657b0ac6603c8e0fda941d5c40 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1933799/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933799] [NEW] gnome-shell crashed with SIGSEGV in rescan_icon_theme() from installed_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist(
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.4-1ubuntu3, the problem page at https://errors.ubuntu.com/problem/0743486472675f657b0ac6603c8e0fda941d5c40 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell Importance: Unknown Status: Unknown ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: hirsute impish -- 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/1933799 Title: gnome-shell crashed with SIGSEGV in rescan_icon_theme() from installed_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.4-1ubuntu3, the problem page at https://errors.ubuntu.com/problem/0743486472675f657b0ac6603c8e0fda941d5c40 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1933799/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
