[Desktop-packages] [Bug 2003357] Re: Nautilus crash up on renaming a local folder
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- 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/2003357 Title: Nautilus crash up on renaming a local folder Status in nautilus package in Ubuntu: Expired Bug description: On my system either I press F2 or Right Click > Rename a folder... It freezes for a seconds and then crash I would say 80-90% of the times. System data: OS: Description: Ubuntu 22.10 Release: 22.10 Package: nautilus: Instalados: 1:43.0-1ubuntu2.1 Candidato: 1:43.0-1ubuntu2.1 Tabla de versión: *** 1:43.0-1ubuntu2.1 500 500 http://archive.ubuntu.com/ubuntu kinetic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu kinetic-security/main amd64 Packages 100 /var/lib/dpkg/status 1:43.0-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.19.0-30.31-generic 5.19.17 Uname: Linux 5.19.0-30-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Thu Jan 19 11:07:14 2023 InstallationDate: Installed on 2022-03-24 (301 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-10-23 (88 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 python3-nautilus 4.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2003357/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1787343] Re: libsane-hpaio and other hplip packages leave cruft behind even after purge
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: hplip (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/1787343
Title:
libsane-hpaio and other hplip packages leave cruft behind even after
purge
Status in hplip package in Ubuntu:
Confirmed
Bug description:
Some time ago I installed hplip packages. Today I purged those
packages. Some cruft was left behind on my bionic system.
$ sudo aptitude purge hplip hplip-data hplip-gui
The following packages will be REMOVED:
hplip{p} hplip-data{pu} hplip-gui{p} libsane-hpaio{u}
python3-dbus.mainloop.pyqt5{u} python3-pexpect{u} python3-ptyprocess{u}
python3-reportlab{u} python3-reportlab-accel{u}
0 packages upgraded, 0 newly installed, 9 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 16,2 MB will be freed.
Do you want to continue? [Y/n/?]
(Reading database ... 220944 files and directories currently installed.)
Removing hplip-gui (3.17.10+repack0-5) ...
Removing hplip (3.17.10+repack0-5) ...
Removing hplip-data (3.17.10+repack0-5) ...
dpkg: warning: while removing hplip-data, directory '/usr/share/hplip/ui5'
not empty so not removed
dpkg: warning: while removing hplip-data, directory '/usr/share/hplip/scan'
not empty so not removed
dpkg: warning: while removing hplip-data, directory '/usr/share/hplip/prnt'
not empty so not removed
dpkg: warning: while removing hplip-data, directory '/usr/share/hplip/pcard'
not empty so not removed
dpkg: warning: while removing hplip-data, directory
'/usr/share/hplip/installer' not empty so not removed
dpkg: warning: while removing hplip-data, directory '/usr/share/hplip/fax'
not empty so not removed
dpkg: warning: while removing hplip-data, directory '/usr/share/hplip/copier'
not empty so not removed
dpkg: warning: while removing hplip-data, directory
'/usr/share/hplip/base/pexpect' not empty so not removed
Removing libsane-hpaio:amd64 (3.17.10+repack0-5) ...
Removing python3-dbus.mainloop.pyqt5 (5.10.1+dfsg-1ubuntu2) ...
Removing python3-pexpect (4.2.1-1) ...
Removing python3-ptyprocess (0.5.2-1) ...
Removing python3-reportlab (3.4.0-3build1) ...
Removing python3-reportlab-accel:amd64 (3.4.0-3build1) ...
Processing triggers for mime-support (3.60ubuntu1) ...
Processing triggers for desktop-file-utils (0.23-1ubuntu3.18.04.1) ...
Processing triggers for bamfdaemon (0.5.3+18.04.20180207.2-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for man-db (2.8.3-2) ...
Processing triggers for gnome-menus (3.13.3-11ubuntu1.1) ...
Processing triggers for dbus (1.12.2-1ubuntu1) ...
(Reading database ... 220072 files and directories currently installed.)
Purging configuration files for hplip (3.17.10+repack0-5) ...
Purging configuration files for hplip-gui (3.17.10+repack0-5) ...
Processing triggers for dbus (1.12.2-1ubuntu1) ...
$ sudo aptitude purge libsane-hpaio
The following packages will be REMOVED:
libsane-hpaio{p}
0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
Do you want to continue? [Y/n/?]
(Reading database ... 220070 files and directories currently installed.)
Purging configuration files for libsane-hpaio:amd64 (3.17.10+repack0-5) ...
dpkg: warning: while removing libsane-hpaio:amd64, directory
'/usr/share/hplip' not empty so not removed
$ sudo find /usr/share/hplip/
/usr/share/hplip/
/usr/share/hplip/base
/usr/share/hplip/base/pexpect
/usr/share/hplip/base/pexpect/__pycache__
/usr/share/hplip/base/__pycache__
/usr/share/hplip/copier
/usr/share/hplip/copier/__pycache__
/usr/share/hplip/fax
/usr/share/hplip/fax/__pycache__
/usr/share/hplip/installer
/usr/share/hplip/installer/__pycache__
/usr/share/hplip/pcard
/usr/share/hplip/pcard/__pycache__
/usr/share/hplip/prnt
/usr/share/hplip/prnt/__pycache__
/usr/share/hplip/scan
/usr/share/hplip/scan/__pycache__
/usr/share/hplip/ui5
/usr/share/hplip/ui5/__pycache__
/usr/share/hplip/__pycache__
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1787343/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2001922] Re: Xorg crash
*** This bug is a duplicate of bug 2000649 *** https://bugs.launchpad.net/bugs/2000649 The fix for bug 2000649 has been requested for inclusion in a future 22.04 update. Other than waiting, the only options are: * Use regular Ubuntu rather than Xubuntu, and you will get a Wayland session by default so won't experience Xorg bugs. * Use Xubuntu 22.10 instead of 22.04. -- 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/2001922 Title: Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: My Ubuntu 22.04.1 LTS installation crashes, but I was not able to figure out how to reproducibly trigger the crash. The last time it happened was with firefox and zoom running, the display suddenly went black and after a few seconds the X login screen appeared, my session gone. There are files in /var/crash/ -rw-r--r-- 1 root whoopsie0 Jan 5 14:09 _usr_lib_xorg_Xorg.0.upload -rw-r- 1 root whoopsie 12792518 Jan 5 14:09 _usr_lib_xorg_Xorg.0.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:09 _usr_lib_xorg_Xorg.0.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _usr_bin_xfsettingsd.1000.upload -rw-r- 1 petr whoopsie 516897 Jan 5 14:13 _usr_bin_xfsettingsd.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _usr_bin_xfsettingsd.1000.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _opt_zoom_zoom.1000.upload -rw-r- 1 petr whoopsie 46590288 Jan 5 14:13 _opt_zoom_zoom.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _opt_zoom_zoom.1000.uploaded and .xsession-errors.old ends with (xfwm4:8122): xfwm4-WARNING **: 14:11:00.736: unmanaged net_wm_state (window 0x649, atom "_NET_WM_STATE_STAYS_ON_TOP") (xfwm4:10847): Gtk-WARNING **: 14:13:01.216: cannot open display: :0.0 Exiting due to channel error. Failed to parse arguments: Cannot open display: :0.0 Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfsettingsd:10849): xfsettingsd-ERROR **: 14:13:01.239: Unable to open display. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfwm4:10854): Gtk-WARNING **: 14:13:01.244: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10860): Gtk-WARNING **: 14:13:01.264: cannot open display: :0.0 (xfwm4:10863): Gtk-WARNING **: 14:13:01.280: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10865): Gtk-WARNING **: 14:13:01.293: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Is it safe and useful to upload the files from /var/crash/? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Thu Jan 5 14:17:42 2023 DistUpgraded: 2022-12-25 11:03:07,557 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.13.0-35-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-56-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:3f96] InstallationDate: Installed on 2021-11-07 (424 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20YA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to jammy on 2022-12-25 (11 days ago) dmi.bios.date: 09/23/2021 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: GMCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: ThinkBook 13s G3 ACN dmi.ec.firmware.release: 1.19 dmi.modalias:
[Desktop-packages] [Bug 2012288] Re: Ubuntu Gnome Settings / Chrome / CUPS (printing) communications
** Package changed: xorg (Ubuntu) => cups (Ubuntu) -- 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/2012288 Title: Ubuntu Gnome Settings / Chrome / CUPS (printing) communications Status in cups package in Ubuntu: New Bug description: I am trying to print. Context :: printer - The network printer I have "HP LaserJet Professional M1217nfw MFP" announces itself via Bonjour, supports SLP Config, LPD Printing and WS-Discovery. The printer is wired to ethernet, and receives it's IP address in IPV4 and IPV6 from the router, set statically at the router. Client - The client machine, Ubuntu 22.10 , is either on wireless (192.168.2.X - DHCP assigned randomly) or wired ethernet (192.168.2.Y - DHCP assigned statically). Sometimes the machine has both interfaces as well as receiving IPV6 addresses for both of these interfaces. It's unclear how printing occurs for discovery, but for comparison - Android "just works", iPhone "just works" , and Windows 10 "just works". Only Ubuntu is the outlier here. When printing a PDF from Chrome, I see there is a mismatch between the printers that Chrome sees, and the printers that are registered with the gnome(?) printers configuration settings. This leads me to believe that these 2 parts of printing are not in sync with one another(!!). Additional, possibly related behavior: When I remove all printers listed. And simply watch the Gnome(?) Printers settings section then a new printer is added automatically exactly this text, yes the duplicate 'HP': "HP HP Laserjet Professional M1217nfw MFP, driverless". This may be a cause of issues since I have not configured an additional printer, yet it appears. When I DO attempt to print to this auto-added printer I receive a vague error after some kind of timeout "Stopped Please restart when the problem is resolved" --- what problem ? What is causing the issue ? This error does not help identify the issue. Can you help me understand what is happening here and how this can be resolved ? If auto-adding a printer is going to magically work , then please include detailed, actionable error messages. Attached -- screenshot of printer subsystems mismatch. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.85.05 Sat Jan 14 00:49:50 UTC 2023 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1) ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 20 11:54:41 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.19.0-31-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-35-generic, x86_64: installed nvidia/525.85.05, 5.19.0-35-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-31-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (70 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-01-15 (64 days ago) dmi.bios.date: 02/09/2023 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET83W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None
[Desktop-packages] [Bug 2003168] Re: Dash-to-dock and Ubuntu Dock may accidentally call each other
** Summary changed: - Dock becomes unresponsive after unlocking the screen: JS ERROR: TypeError: dockManager is null + Dash-to-dock and Ubuntu Dock may accidentally call each other ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => Triaged ** Summary changed: - Dash-to-dock and Ubuntu Dock may accidentally call each other + Dash-to-dock and Ubuntu Dock may accidentally call each other [JS ERROR: TypeError: dockManager is null] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2003168 Title: Dash-to-dock and Ubuntu Dock may accidentally call each other [JS ERROR: TypeError: dockManager is null] Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Bug description: SIdebar, files gets unresponsive after unlocking locked season. Clicking on search bar also freezes the whole season. Issue requires Restarting GTK3 or restarting the season. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-59.65-generic 5.15.78 Uname: Linux 5.15.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 18 13:35:36 2023 InstallationDate: Installed on 2021-06-20 (576 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2003168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999688] Re: toggle on/off not displaying in yaru shell color themes
** Bug watch added: github.com/ubuntu/yaru/issues #3850 https://github.com/ubuntu/yaru/issues/3850 ** Also affects: yaru via https://github.com/ubuntu/yaru/issues/3850 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1999688 Title: toggle on/off not displaying in yaru shell color themes Status in Yaru Theme: Unknown Status in yaru-theme package in Ubuntu: New Bug description: The toggle button is not displaying in yaru color(bark/blue/magenta/olive...) gnome shell themes in both light and dark modes. Looking into the logs, found these: gnome-shell[2064]: Failed to load resource:///org/gnome/shell/theme/toggle-on-bark.svg: The resource at “/org/gnome/shell/theme/toggle-on-bark.svg” does not exist Check this with any gnome shell extension with toggle button (e.g. CPU power manager). Someone please check if it is happening for checkbox too which is using svg resource. To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1999688/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011790] Re: Night Light doesn't work in gnome-shell 44.rc
** Changed in: mutter (Ubuntu) Status: Confirmed => Fix Committed ** No longer affects: gnome-shell (Ubuntu) ** Tags added: fixed-in-mutter-44.0 fixed-upstream -- 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/2011790 Title: Night Light doesn't work in gnome-shell 44.rc Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Committed Bug description: Night Light doesn't work in gnome-shell 44.rc To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2011790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012282] Re: [gnome-shell 44~rc-1ubuntu2, Ubuntu 23.04 (development branch)] Wrong background color in application folders
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: yaru-theme (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/2012282 Title: [gnome-shell 44~rc-1ubuntu2, Ubuntu 23.04 (development branch)] Wrong background color in application folders Status in Yaru Theme: Unknown Status in yaru-theme package in Ubuntu: Fix Committed Bug description: Problem summary: After upgrading from Ubuntu 22.10 to Ubuntu 23.04 (development branch) the gnome-shell application folders background is shown in white color instead of dark grey color making impossible to read it's contents. I'm using the default Ubuntu theming. I've attached two screenshots: - Ubuntu_22_10_OK.png: where you can see that application folder background is dark grey as expected. - Ubuntu_23_04_BAD.png: where you can see that application folder background is white and content is unreadable. Additional data: System Model: Raspberry Pi 4 Model B Rev 1.4 8Gb Kernel: Linux fpgrpi 5.19.0-1015-raspi #22-Ubuntu SMP PREEMPT Mon Mar 6 10:35:33 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -rd No LSB modules are available. Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 # apt-cache policy gnome-shell gnome-shell: Instalados: 44~rc-1ubuntu2 Candidato: 44~rc-1ubuntu2 Tabla de versión: *** 44~rc-1ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/2012282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012282] Re: [gnome-shell 44~rc-1ubuntu2, Ubuntu 23.04 (development branch)] Wrong background color in application folders
** Tags added: lunar ** Bug watch added: github.com/ubuntu/yaru/issues #3856 https://github.com/ubuntu/yaru/issues/3856 ** Also affects: yaru via https://github.com/ubuntu/yaru/issues/3856 Importance: Unknown Status: Unknown ** No longer affects: gnome-shell (Ubuntu) ** Changed in: yaru-theme (Ubuntu) Assignee: (unassigned) => Paul (jupiter007) ** Changed in: yaru-theme (Ubuntu) Status: Confirmed => Fix Committed ** Tags added: fixed-in-yaru-23.04.2 fixed-upstream ** Changed in: yaru-theme (Ubuntu) Importance: Undecided => High -- 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/2012282 Title: [gnome-shell 44~rc-1ubuntu2, Ubuntu 23.04 (development branch)] Wrong background color in application folders Status in Yaru Theme: Unknown Status in yaru-theme package in Ubuntu: Fix Committed Bug description: Problem summary: After upgrading from Ubuntu 22.10 to Ubuntu 23.04 (development branch) the gnome-shell application folders background is shown in white color instead of dark grey color making impossible to read it's contents. I'm using the default Ubuntu theming. I've attached two screenshots: - Ubuntu_22_10_OK.png: where you can see that application folder background is dark grey as expected. - Ubuntu_23_04_BAD.png: where you can see that application folder background is white and content is unreadable. Additional data: System Model: Raspberry Pi 4 Model B Rev 1.4 8Gb Kernel: Linux fpgrpi 5.19.0-1015-raspi #22-Ubuntu SMP PREEMPT Mon Mar 6 10:35:33 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -rd No LSB modules are available. Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 # apt-cache policy gnome-shell gnome-shell: Instalados: 44~rc-1ubuntu2 Candidato: 44~rc-1ubuntu2 Tabla de versión: *** 44~rc-1ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/2012282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012282] Re: [gnome-shell 44~rc-1ubuntu2, Ubuntu 23.04 (development branch)] Wrong background color in application folders
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/2012282 Title: [gnome-shell 44~rc-1ubuntu2, Ubuntu 23.04 (development branch)] Wrong background color in application folders Status in Yaru Theme: Unknown Status in yaru-theme package in Ubuntu: Fix Committed Bug description: Problem summary: After upgrading from Ubuntu 22.10 to Ubuntu 23.04 (development branch) the gnome-shell application folders background is shown in white color instead of dark grey color making impossible to read it's contents. I'm using the default Ubuntu theming. I've attached two screenshots: - Ubuntu_22_10_OK.png: where you can see that application folder background is dark grey as expected. - Ubuntu_23_04_BAD.png: where you can see that application folder background is white and content is unreadable. Additional data: System Model: Raspberry Pi 4 Model B Rev 1.4 8Gb Kernel: Linux fpgrpi 5.19.0-1015-raspi #22-Ubuntu SMP PREEMPT Mon Mar 6 10:35:33 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -rd No LSB modules are available. Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 # apt-cache policy gnome-shell gnome-shell: Instalados: 44~rc-1ubuntu2 Candidato: 44~rc-1ubuntu2 Tabla de versión: *** 44~rc-1ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/2012282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956111] Re: Colord's colorhug no longer exists but a URI and library do as a required dependency.
** Summary changed: - Colord's colorhug no longer exists but a URI and library do. + Colord's colorhug no longer exists but a URI and library do as a required dependency. ** Summary changed: - Colord's colorhug no longer exists but a URI and library do as a required dependency. + Colord's colorhug no longer exists but the URI and library do as a required dependency. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1956111 Title: Colord's colorhug no longer exists but the URI and library do as a required dependency. Status in colord package in Ubuntu: New Status in colord package in Debian: New Bug description: https://github.com/hughsie/colord/commit/98f83acc910f527496fc149511c9dfa35f954be9 The domain listed in the upload URI in the gschema has been taken over by spammers. The library libcolorhug2 is still installed by default as a dependency of colord. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1956111/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012313] [NEW] Unable to close tabs when running in sudo mode
Public bug reported:
When I'm running gnome-text-editor package via terminal in "sudo" mode
(for example to open some configuration files), I am not able to close
any of the tabs already opened ("Restore session" option is enabled and
I cannot disable it). Instead of closing the tab, whole application is
closed and the Terminal shows a lot of error messages
Also I noticed that if I open a settings window and try to close it -
the same happens, application is instantly closed.
Ubuntu Release:
Description:Ubuntu 22.10
Release:22.10
Application version: 43.1
** Affects: gnome-text-editor (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "Gnome-text-editor_IssueSudo.txt"
https://bugs.launchpad.net/bugs/2012313/+attachment/5656112/+files/Gnome-text-editor_IssueSudo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-text-editor in Ubuntu.
https://bugs.launchpad.net/bugs/2012313
Title:
Unable to close tabs when running in sudo mode
Status in gnome-text-editor package in Ubuntu:
New
Bug description:
When I'm running gnome-text-editor package via terminal in "sudo" mode
(for example to open some configuration files), I am not able to close
any of the tabs already opened ("Restore session" option is enabled
and I cannot disable it). Instead of closing the tab, whole
application is closed and the Terminal shows a lot of error messages
Also I noticed that if I open a settings window and try to close it -
the same happens, application is instantly closed.
Ubuntu Release:
Description: Ubuntu 22.10
Release: 22.10
Application version: 43.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/2012313/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012309] Re: gdm3: autostart folder for .desktop files is not working in Ubuntu 23.04
** Changed in: gdm3 (Ubuntu) Status: New => Opinion -- 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/2012309 Title: gdm3: autostart folder for .desktop files is not working in Ubuntu 23.04 Status in gdm3 package in Ubuntu: Opinion Bug description: Problem summary: After upgrading from Ubuntu 22.10 to Ubuntu 23.04 (development branch) gdm3 doesn't autostart the applications (.desktop files) placed in the folder /usr/share/gdm/greeter/autostart/ Notice that gdm3 documentation states that the official autostart folder is /usr/share/gdm/autostart/LoginWindow/ but placing desktop files in this folder never worked for me in any Ubuntu release. However, placing desktop files in the folder /usr/share/gdm/greeter/autostart/ worked in Ubuntu 22.10 and previous releases, but it's broken in Ubuntu 23.04. So it may be correct that /usr/share/gdm/greeter/autostart/ don't work anymore as the documented folder is /usr/share/gdm/autostart/LoginWindow/ ... but that one didn't work either. There are several packages that rely in the correct working of these autostart folders. E.g. the package spice-vdagent creates these two .desktop files: /usr/share/gdm/autostart/LoginWindow/spice-vdagent.desktop /usr/share/gdm/greeter/autostart/spice-vdagent.desktop One in each autostart folder... just in case. But none of these works in Ubuntu 23.04. Additional data: System Model: Raspberry Pi 4 Model B Rev 1.4 8Gb Kernel: Linux fpgrpi 5.19.0-1015-raspi #22-Ubuntu SMP PREEMPT Mon Mar 6 10:35:33 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -rd No LSB modules are available. Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 # apt-cache policy gdm3 gdm3: Instalados: 43.0-3ubuntu2 Candidato: 43.0-3ubuntu2 Tabla de versión: *** 43.0-3ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2012309/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913977] Re: Bad sound quality (no bass) on Thinkpad T490s
I am having the same issue on my ThinkPad T460 (Ubuntu 22.04 LTS). Is there any update or workaround related to this issue? -- 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/1913977 Title: Bad sound quality (no bass) on Thinkpad T490s Status in alsa-driver package in Ubuntu: Confirmed Bug description: Sound works on with 20.04 on the Thinkpad T490s, but sound quality is noticeably worse than on Windows. It looks like the same bug here: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hmahmood 1360 F pulseaudio /dev/snd/pcmC0D0p: hmahmood 1360 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 31 19:14:57 2021 InstallationDate: Installed on 2021-01-30 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [20NYS83800, Realtek ALC257, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2020 dmi.bios.release: 1.70 dmi.bios.vendor: LENOVO dmi.bios.version: N2JET92W (1.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NYS83800 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrN2JET92W(1.70):bd08/31/2020:br1.70:efr1.20:svnLENOVO:pn20NYS83800:pvrThinkPadT490s:rvnLENOVO:rn20NYS83800:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T490s dmi.product.name: 20NYS83800 dmi.product.sku: LENOVO_MT_20NY_BU_Think_FM_ThinkPad T490s dmi.product.version: ThinkPad T490s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1913977/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913977] Re: Bad sound quality (no bass) on Thinkpad T490s
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/1913977 Title: Bad sound quality (no bass) on Thinkpad T490s Status in alsa-driver package in Ubuntu: Confirmed Bug description: Sound works on with 20.04 on the Thinkpad T490s, but sound quality is noticeably worse than on Windows. It looks like the same bug here: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hmahmood 1360 F pulseaudio /dev/snd/pcmC0D0p: hmahmood 1360 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 31 19:14:57 2021 InstallationDate: Installed on 2021-01-30 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [20NYS83800, Realtek ALC257, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2020 dmi.bios.release: 1.70 dmi.bios.vendor: LENOVO dmi.bios.version: N2JET92W (1.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NYS83800 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrN2JET92W(1.70):bd08/31/2020:br1.70:efr1.20:svnLENOVO:pn20NYS83800:pvrThinkPadT490s:rvnLENOVO:rn20NYS83800:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T490s dmi.product.name: 20NYS83800 dmi.product.sku: LENOVO_MT_20NY_BU_Think_FM_ThinkPad T490s dmi.product.version: ThinkPad T490s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1913977/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006460] Re: hp-toolbox fails on load due to call to undefined "get_distro_std_name' function
I can't download hp plugin (kubuntu 23.04) HP Linux Imaging and Printing System (ver. 3.22.10) Plugin Download and Install Utility ver. 2.1 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. HP Linux Imaging and Printing System (ver. 3.22.10) Plugin Download and Install Utility ver. 2.1 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Checking for network connection... Downloading plug-in from: Traceback (most recent call last): File "/usr/share/hplip/ui5/plugindialog.py", line 248, in NextButton_clicked status, download_plugin_file, error_str = self.pluginObj.download(self.plugin_path,self.plugin_download_callback) ^^^ File "/usr/share/hplip/installer/pluginhandler.py", line 257, in download core = core_install.CoreInstall() ^^ File "/usr/share/hplip/installer/core_install.py", line 240, in __init__ self.passwordObj = password.Password(ui_mode) ^^ File "/usr/share/hplip/base/password.py", line 94, in __init__ self.__readAuthType() # self.__authType ^ File "/usr/share/hplip/base/password.py", line 119, in __readAuthType distro_name = get_distro_std_name(os_name) ^^^ NameError: name 'get_distro_std_name' is not defined. Did you mean: 'get_distro_name'? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/2006460 Title: hp-toolbox fails on load due to call to undefined "get_distro_std_name' function Status in hplip package in Ubuntu: Confirmed Bug description: When starting hp-toolbox from the GUI, nothing happens. From the CLI I get the information : HP Linux Imaging and Printing System (ver. 3.22.10) HP Device Manager ver. 15.0 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Traceback (most recent call last): File "/usr/bin/hp-toolbox", line 280, in toolbox = ui.DevMgr5(__version__, device_uri, None) ^^ File "/usr/share/hplip/ui5/devmgr5.py", line 238, in __init__ core = CoreInstall(MODE_CHECK) ^^^ File "/usr/share/hplip/installer/core_install.py", line 240, in __init__ self.passwordObj = password.Password(ui_mode) ^^ File "/usr/share/hplip/base/password.py", line 94, in __init__ self.__readAuthType() # self.__authType ^ File "/usr/share/hplip/base/password.py", line 119, in __readAuthType distro_name = get_distro_std_name(os_name) ^^^ Changing the instances of get_distro_std_name(os_name) to get_distro_name() as suggested resolved the bug. When installing the plugin for the scanner, the same issue crops up again, here at line 322. An identical substitution allows the plugin installer to complete successfully. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: hplip-data 3.22.10+dfsg0-1 [modified: usr/share/hplip/base/password.py] ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CupsErrorLog: W [07/Feb/2023:11:47:17 +0100] Printer drivers are deprecated and will stop working in a future version of CUPS. See https://github.com/OpenPrinting/cups/issues/103 W [07/Feb/2023:11:47:23 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M281fdw_5543F1-Gray..\' already exists W [07/Feb/2023:11:47:23 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M281fdw_5543F1-DeviceN..\' already exists E [07/Feb/2023:11:47:24 +0100] [Client 17] Returning IPP client-error-not-possible for CUPS-Create-Local-Printer (ipp://localhost/) from localhost. CurrentDesktop: ubuntu:GNOME Date: Tue Feb 7 12:10:42 2023 InstallationDate: Installed on 2020-06-20 (961 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609) Lpstat: device for HP_Color_LaserJet_MFP_M281fdw_5543F1:
[Desktop-packages] [Bug 2006460] Re: hp-toolbox fails on load due to call to undefined "get_distro_std_name' function
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: hplip (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/2006460 Title: hp-toolbox fails on load due to call to undefined "get_distro_std_name' function Status in hplip package in Ubuntu: Confirmed Bug description: When starting hp-toolbox from the GUI, nothing happens. From the CLI I get the information : HP Linux Imaging and Printing System (ver. 3.22.10) HP Device Manager ver. 15.0 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Traceback (most recent call last): File "/usr/bin/hp-toolbox", line 280, in toolbox = ui.DevMgr5(__version__, device_uri, None) ^^ File "/usr/share/hplip/ui5/devmgr5.py", line 238, in __init__ core = CoreInstall(MODE_CHECK) ^^^ File "/usr/share/hplip/installer/core_install.py", line 240, in __init__ self.passwordObj = password.Password(ui_mode) ^^ File "/usr/share/hplip/base/password.py", line 94, in __init__ self.__readAuthType() # self.__authType ^ File "/usr/share/hplip/base/password.py", line 119, in __readAuthType distro_name = get_distro_std_name(os_name) ^^^ Changing the instances of get_distro_std_name(os_name) to get_distro_name() as suggested resolved the bug. When installing the plugin for the scanner, the same issue crops up again, here at line 322. An identical substitution allows the plugin installer to complete successfully. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: hplip-data 3.22.10+dfsg0-1 [modified: usr/share/hplip/base/password.py] ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CupsErrorLog: W [07/Feb/2023:11:47:17 +0100] Printer drivers are deprecated and will stop working in a future version of CUPS. See https://github.com/OpenPrinting/cups/issues/103 W [07/Feb/2023:11:47:23 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M281fdw_5543F1-Gray..\' already exists W [07/Feb/2023:11:47:23 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M281fdw_5543F1-DeviceN..\' already exists E [07/Feb/2023:11:47:24 +0100] [Client 17] Returning IPP client-error-not-possible for CUPS-Create-Local-Printer (ipp://localhost/) from localhost. CurrentDesktop: ubuntu:GNOME Date: Tue Feb 7 12:10:42 2023 InstallationDate: Installed on 2020-06-20 (961 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609) Lpstat: device for HP_Color_LaserJet_MFP_M281fdw_5543F1: implicitclass://HP_Color_LaserJet_MFP_M281fdw_5543F1/ device for HP_ColorLaserJet_MFP_M278-M281: hp:/net/HP_ColorLaserJet_MFP_M278-M281?ip=192.168.0.102 device for HP_ColorLaserJet_MFP_M278-M281_fax: hpfax:/net/HP_ColorLaserJet_MFP_M278-M281?ip=192.168.0.102 MachineType: System manufacturer System Product Name PackageArchitecture: all Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M281fdw_5543F1.ppd', '/etc/cups/ppd/HP_ColorLaserJet_MFP_M278-M281.ppd', '/etc/cups/ppd/HP_ColorLaserJet_MFP_M278-M281_fax.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M281fdw_5543F1.ppd: Permission denied grep: /etc/cups/ppd/HP_ColorLaserJet_MFP_M278-M281.ppd: Permission denied grep: /etc/cups/ppd/HP_ColorLaserJet_MFP_M278-M281_fax.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=05f71b34-3a5a-42e5-adb6-8a11af401188 ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 SourcePackage: hplip UpgradeStatus: Upgraded to lunar on 2022-12-21 (47 days ago) dmi.bios.date: 10/27/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4408 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X570-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Desktop-packages] [Bug 2012311] [NEW] gdm3: Restart and Shutdown options doesn't work in Ubuntu 23.04
Public bug reported: Problem summary: After upgrading from Ubuntu 22.10 to Ubuntu 23.04 (development branch) the options to Restart and Shutdown the system are not working anymore. In Ubuntu 22.10 when you are in the gdm3 login screen and choose Restart or Shutdown it presents a dialog box saying that the action will be auto performed in 60 seconds, with two buttons, one to cancel and another to perform the action at once. In Ubuntu 23.04 choosing Restart or Shutdown does nothing at all... Additional data: System Model: Raspberry Pi 4 Model B Rev 1.4 8Gb Kernel: Linux fpgrpi 5.19.0-1015-raspi #22-Ubuntu SMP PREEMPT Mon Mar 6 10:35:33 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -rd No LSB modules are available. Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 # apt-cache policy gdm3 gdm3: Instalados: 43.0-3ubuntu2 Candidato: 43.0-3ubuntu2 Tabla de versión: *** 43.0-3ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/main arm64 Packages 100 /var/lib/dpkg/status ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- 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/2012311 Title: gdm3: Restart and Shutdown options doesn't work in Ubuntu 23.04 Status in gdm3 package in Ubuntu: New Bug description: Problem summary: After upgrading from Ubuntu 22.10 to Ubuntu 23.04 (development branch) the options to Restart and Shutdown the system are not working anymore. In Ubuntu 22.10 when you are in the gdm3 login screen and choose Restart or Shutdown it presents a dialog box saying that the action will be auto performed in 60 seconds, with two buttons, one to cancel and another to perform the action at once. In Ubuntu 23.04 choosing Restart or Shutdown does nothing at all... Additional data: System Model: Raspberry Pi 4 Model B Rev 1.4 8Gb Kernel: Linux fpgrpi 5.19.0-1015-raspi #22-Ubuntu SMP PREEMPT Mon Mar 6 10:35:33 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -rd No LSB modules are available. Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 # apt-cache policy gdm3 gdm3: Instalados: 43.0-3ubuntu2 Candidato: 43.0-3ubuntu2 Tabla de versión: *** 43.0-3ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2012311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012309] [NEW] gdm3: autostart folder for .desktop files is not working in Ubuntu 23.04
Public bug reported: Problem summary: After upgrading from Ubuntu 22.10 to Ubuntu 23.04 (development branch) gdm3 doesn't autostart the applications (.desktop files) placed in the folder /usr/share/gdm/greeter/autostart/ Notice that gdm3 documentation states that the official autostart folder is /usr/share/gdm/autostart/LoginWindow/ but placing desktop files in this folder never worked for me in any Ubuntu release. However, placing desktop files in the folder /usr/share/gdm/greeter/autostart/ worked in Ubuntu 22.10 and previous releases, but it's broken in Ubuntu 23.04. So it may be correct that /usr/share/gdm/greeter/autostart/ don't work anymore as the documented folder is /usr/share/gdm/autostart/LoginWindow/ ... but that one didn't work either. There are several packages that rely in the correct working of these autostart folders. E.g. the package spice-vdagent creates these two .desktop files: /usr/share/gdm/autostart/LoginWindow/spice-vdagent.desktop /usr/share/gdm/greeter/autostart/spice-vdagent.desktop One in each autostart folder... just in case. But none of these works in Ubuntu 23.04. Additional data: System Model: Raspberry Pi 4 Model B Rev 1.4 8Gb Kernel: Linux fpgrpi 5.19.0-1015-raspi #22-Ubuntu SMP PREEMPT Mon Mar 6 10:35:33 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -rd No LSB modules are available. Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 # apt-cache policy gdm3 gdm3: Instalados: 43.0-3ubuntu2 Candidato: 43.0-3ubuntu2 Tabla de versión: *** 43.0-3ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/main arm64 Packages 100 /var/lib/dpkg/status ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- 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/2012309 Title: gdm3: autostart folder for .desktop files is not working in Ubuntu 23.04 Status in gdm3 package in Ubuntu: New Bug description: Problem summary: After upgrading from Ubuntu 22.10 to Ubuntu 23.04 (development branch) gdm3 doesn't autostart the applications (.desktop files) placed in the folder /usr/share/gdm/greeter/autostart/ Notice that gdm3 documentation states that the official autostart folder is /usr/share/gdm/autostart/LoginWindow/ but placing desktop files in this folder never worked for me in any Ubuntu release. However, placing desktop files in the folder /usr/share/gdm/greeter/autostart/ worked in Ubuntu 22.10 and previous releases, but it's broken in Ubuntu 23.04. So it may be correct that /usr/share/gdm/greeter/autostart/ don't work anymore as the documented folder is /usr/share/gdm/autostart/LoginWindow/ ... but that one didn't work either. There are several packages that rely in the correct working of these autostart folders. E.g. the package spice-vdagent creates these two .desktop files: /usr/share/gdm/autostart/LoginWindow/spice-vdagent.desktop /usr/share/gdm/greeter/autostart/spice-vdagent.desktop One in each autostart folder... just in case. But none of these works in Ubuntu 23.04. Additional data: System Model: Raspberry Pi 4 Model B Rev 1.4 8Gb Kernel: Linux fpgrpi 5.19.0-1015-raspi #22-Ubuntu SMP PREEMPT Mon Mar 6 10:35:33 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -rd No LSB modules are available. Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 # apt-cache policy gdm3 gdm3: Instalados: 43.0-3ubuntu2 Candidato: 43.0-3ubuntu2 Tabla de versión: *** 43.0-3ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2012309/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012282] Re: [gnome-shell 44~rc-1ubuntu2, Ubuntu 23.04 (development branch)] Wrong background color in application folders
Hi, a patch just has been sent :) See: https://github.com/ubuntu/yaru/pull/3857 -- 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/2012282 Title: [gnome-shell 44~rc-1ubuntu2, Ubuntu 23.04 (development branch)] Wrong background color in application folders Status in gnome-shell package in Ubuntu: New Status in yaru-theme package in Ubuntu: New Bug description: Problem summary: After upgrading from Ubuntu 22.10 to Ubuntu 23.04 (development branch) the gnome-shell application folders background is shown in white color instead of dark grey color making impossible to read it's contents. I'm using the default Ubuntu theming. I've attached two screenshots: - Ubuntu_22_10_OK.png: where you can see that application folder background is dark grey as expected. - Ubuntu_23_04_BAD.png: where you can see that application folder background is white and content is unreadable. Additional data: System Model: Raspberry Pi 4 Model B Rev 1.4 8Gb Kernel: Linux fpgrpi 5.19.0-1015-raspi #22-Ubuntu SMP PREEMPT Mon Mar 6 10:35:33 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -rd No LSB modules are available. Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 # apt-cache policy gnome-shell gnome-shell: Instalados: 44~rc-1ubuntu2 Candidato: 44~rc-1ubuntu2 Tabla de versión: *** 44~rc-1ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012305] [NEW] 2.39 opengles issue on armhf
Public bug reported: Reported also to Debian on https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1033230 ** Affects: webkit2gtk (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2012305 Title: 2.39 opengles issue on armhf Status in webkit2gtk package in Ubuntu: New Bug description: Reported also to Debian on https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1033230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/2012305/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012021] Re: gnome-shell crashed with SIGSEGV in __strcmp_avx2() from update_current_theme() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist()
Upstream fix at https://gitlab.gnome.org/GNOME/gnome- shell/-/merge_requests/2711 -- 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/2012021 Title: gnome-shell crashed with SIGSEGV in __strcmp_avx2() from update_current_theme() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() Status in gnome-shell package in Ubuntu: In Progress 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 44~rc-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/82b0f1ff6e7b5a65a89c6ddc7050de18f30fa23d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011782] Re: gnome-shell crashed with SIGSEGV in g_hash_table_remove_all() from do_theme_change() from update_current_theme() from g_closure_invoke() from signal_emit_unlocked_
*** This bug is a duplicate of bug 2012021 *** https://bugs.launchpad.net/bugs/2012021 ** This bug has been marked a duplicate of bug 2012021 gnome-shell crashed with SIGSEGV in __strcmp_avx2() from update_current_theme() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() -- 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/2011782 Title: gnome-shell crashed with SIGSEGV in g_hash_table_remove_all() from do_theme_change() from update_current_theme() from g_closure_invoke() from signal_emit_unlocked_R() 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 44~rc-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/379c8c7c360c033e3135ef22242fd198891cbb2d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011782/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012021] Re: gnome-shell crashed with SIGSEGV in __strcmp_avx2() from update_current_theme() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist()
** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => In Progress ** Changed in: gnome-shell (Ubuntu) Importance: Medium => High -- 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/2012021 Title: gnome-shell crashed with SIGSEGV in __strcmp_avx2() from update_current_theme() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() Status in gnome-shell package in Ubuntu: In Progress 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 44~rc-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/82b0f1ff6e7b5a65a89c6ddc7050de18f30fa23d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011790] Re: Night Light doesn't work in gnome-shell 44.rc
Nvidia dGPU only mode, Lunar, GS 44 rc 1) run night light, external monitor only 2) activate the laptop screen (joined monitors mode) 3) laptop screen is not nightlighted Workaround: turn off then on night light. -- 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/2011790 Title: Night Light doesn't work in gnome-shell 44.rc Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Night Light doesn't work in gnome-shell 44.rc To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2011790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-aws-5.15/5.15.0-1032.36~20.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-aws-5.15 (5.15.0-1032.36~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-restricted-modules-aws-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-aws/5.4.0-1098.106)
All autopkgtests for the newly accepted linux-restricted-modules-aws (5.4.0-1098.106) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-restricted-modules-aws [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012294] evolution-alarm-notify crashed with SIGSEGV in g_closure_invoke()
StacktraceTop: ?? () g_closure_invoke (closure=0x564dafb6e6d0, return_value=0x0, n_param_values=2, param_values=0x7ffe7baf0340, invocation_hint=0x7ffe7baf02c0) at ../../../gobject/gclosure.c:832 signal_emit_unlocked_R.isra.0 (node=node@entry=0x564dafa40b80, detail=detail@entry=552, instance=instance@entry=0x564dafac44a0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffe7baf0340) at ../../../gobject/gsignal.c:3802 g_signal_emit_valist (instance=, signal_id=, detail=, var_args=var_args@entry=0x7ffe7baf0500) at ../../../gobject/gsignal.c:3555 g_signal_emit (instance=, signal_id=, detail=) at ../../../gobject/gsignal.c:3612 ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/2012294 Title: evolution-alarm-notify crashed with SIGSEGV in g_closure_invoke() Status in evolution-data-server package in Ubuntu: New Bug description: crashed when login to x11 session ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: evolution-data-server 3.47.3-1 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 00:27:25 2023 Disassembly: => 0x7f7332a444b0: Cannot access memory at address 0x7f7332a444b0 ExecutablePath: /usr/libexec/evolution-data-server/evolution-alarm-notify InstallationDate: Installed on 2020-06-25 (997 days ago) InstallationMedia: JournalErrors: Mar 21 00:27:22 hostname gnome-control-c[178036]: No gedit is installed here. Colors won't be updated. Please fix your installation. Mar 21 00:27:25 hostname kernel: show_signal_msg: 1 callbacks suppressed ProcCmdline: /usr/libexec/evolution-data-server/evolution-alarm-notify SegvAnalysis: Segfault happened at: 0x7f7332a444b0:Cannot access memory at address 0x7f7332a444b0 PC (0x7f7332a444b0) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: evolution-alarm-notify crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to lunar on 2022-09-30 (170 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/2012294/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012295] ibus-extension-gtk3 crashed with SIGSEGV in g_closure_invoke()
StacktraceTop: ?? () g_closure_invoke (closure=0x560fe51cf560, return_value=0x0, n_param_values=2, param_values=0x7fffa6f160c0, invocation_hint=0x7fffa6f16040) at ../../../gobject/gclosure.c:832 signal_emit_unlocked_R.isra.0 (node=node@entry=0x560fe50a70f0, detail=detail@entry=795, instance=instance@entry=0x560fe515d2f0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fffa6f160c0) at ../../../gobject/gsignal.c:3802 g_signal_emit_valist (instance=, signal_id=, detail=, var_args=var_args@entry=0x7fffa6f16280) at ../../../gobject/gsignal.c:3555 g_signal_emit (instance=, signal_id=, detail=) at ../../../gobject/gsignal.c:3612 ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2012295 Title: ibus-extension-gtk3 crashed with SIGSEGV in g_closure_invoke() Status in ibus package in Ubuntu: New Bug description: crashed when login to x11 session ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: ibus 1.5.28-2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 00:27:39 2023 Disassembly: => 0x7f4f395714b0: Cannot access memory at address 0x7f4f395714b0 ExecutablePath: /usr/libexec/ibus-extension-gtk3 InstallationDate: Installed on 2020-06-25 (997 days ago) InstallationMedia: JournalErrors: -- No entries -- ProcCmdline: /usr/libexec/ibus-extension-gtk3 SegvAnalysis: Segfault happened at: 0x7f4f395714b0:Cannot access memory at address 0x7f4f395714b0 PC (0x7f4f395714b0) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ibus-extension-gtk3 crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to lunar on 2022-09-30 (170 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2012295/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956109] Re: printer-driver-ptouch is included with metapackages for the minimal install
** Description changed: A label printer driver is a recommended dependency of many desktop, core, and minimal ubuntu metapackages. It is installed with the minimal - Ubuntu option. + Ubuntu option. Should this hardware be included with the minimal install + and should it be in multiple, overlapping metapackages? If so, why? ** Summary changed: - printer-driver-ptouch is included with metapackages for the minimal install + printer-driver-ptouch is included with multiple metapackages for the minimal install ** Also affects: xubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-mate-meta (Ubuntu) Importance: Undecided Status: New ** Description changed: A label printer driver is a recommended dependency of many desktop, - core, and minimal ubuntu metapackages. It is installed with the minimal - Ubuntu option. Should this hardware be included with the minimal install - and should it be in multiple, overlapping metapackages? If so, why? + core, and minimal ubuntu and spin metapackages. It is also installed + with the minimal Ubuntu ISO option. Should this hardware be included + with the minimal install and should it be in multiple, overlapping + metapackages? If so, why? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1956109 Title: printer-driver-ptouch is included with multiple metapackages for the minimal install Status in ubuntu-mate-meta package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Status in xubuntu-meta package in Ubuntu: New Bug description: A label printer driver is a recommended dependency of many desktop, core, and minimal ubuntu and spin metapackages. It is also installed with the minimal Ubuntu ISO option. Should this hardware be included with the minimal install and should it be in multiple, overlapping metapackages? If so, why? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-meta/+bug/1956109/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012282] Re: [gnome-shell 44~rc-1ubuntu2, Ubuntu 23.04 (development branch)] Wrong background color in application folders
** Package changed: gnome-shell (Ubuntu) => yaru-theme (Ubuntu) ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2012282 Title: [gnome-shell 44~rc-1ubuntu2, Ubuntu 23.04 (development branch)] Wrong background color in application folders Status in gnome-shell package in Ubuntu: New Status in yaru-theme package in Ubuntu: New Bug description: Problem summary: After upgrading from Ubuntu 22.10 to Ubuntu 23.04 (development branch) the gnome-shell application folders background is shown in white color instead of dark grey color making impossible to read it's contents. I'm using the default Ubuntu theming. I've attached two screenshots: - Ubuntu_22_10_OK.png: where you can see that application folder background is dark grey as expected. - Ubuntu_23_04_BAD.png: where you can see that application folder background is white and content is unreadable. Additional data: System Model: Raspberry Pi 4 Model B Rev 1.4 8Gb Kernel: Linux fpgrpi 5.19.0-1015-raspi #22-Ubuntu SMP PREEMPT Mon Mar 6 10:35:33 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -rd No LSB modules are available. Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 # apt-cache policy gnome-shell gnome-shell: Instalados: 44~rc-1ubuntu2 Candidato: 44~rc-1ubuntu2 Tabla de versión: *** 44~rc-1ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012295] [NEW] ibus-extension-gtk3 crashed with SIGSEGV in g_closure_invoke()
Public bug reported: crashed when login to x11 session ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: ibus 1.5.28-2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 00:27:39 2023 Disassembly: => 0x7f4f395714b0: Cannot access memory at address 0x7f4f395714b0 ExecutablePath: /usr/libexec/ibus-extension-gtk3 InstallationDate: Installed on 2020-06-25 (997 days ago) InstallationMedia: JournalErrors: -- No entries -- ProcCmdline: /usr/libexec/ibus-extension-gtk3 SegvAnalysis: Segfault happened at: 0x7f4f395714b0: Cannot access memory at address 0x7f4f395714b0 PC (0x7f4f395714b0) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ibus-extension-gtk3 crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to lunar on 2022-09-30 (170 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo separator: ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash lunar ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2012295 Title: ibus-extension-gtk3 crashed with SIGSEGV in g_closure_invoke() Status in ibus package in Ubuntu: New Bug description: crashed when login to x11 session ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: ibus 1.5.28-2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 00:27:39 2023 Disassembly: => 0x7f4f395714b0: Cannot access memory at address 0x7f4f395714b0 ExecutablePath: /usr/libexec/ibus-extension-gtk3 InstallationDate: Installed on 2020-06-25 (997 days ago) InstallationMedia: JournalErrors: -- No entries -- ProcCmdline: /usr/libexec/ibus-extension-gtk3 SegvAnalysis: Segfault happened at: 0x7f4f395714b0:Cannot access memory at address 0x7f4f395714b0 PC (0x7f4f395714b0) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ibus-extension-gtk3 crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to lunar on 2022-09-30 (170 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2012295/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012294] [NEW] evolution-alarm-notify crashed with SIGSEGV in g_closure_invoke()
Public bug reported: crashed when login to x11 session ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: evolution-data-server 3.47.3-1 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 00:27:25 2023 Disassembly: => 0x7f7332a444b0: Cannot access memory at address 0x7f7332a444b0 ExecutablePath: /usr/libexec/evolution-data-server/evolution-alarm-notify InstallationDate: Installed on 2020-06-25 (997 days ago) InstallationMedia: JournalErrors: Mar 21 00:27:22 hostname gnome-control-c[178036]: No gedit is installed here. Colors won't be updated. Please fix your installation. Mar 21 00:27:25 hostname kernel: show_signal_msg: 1 callbacks suppressed ProcCmdline: /usr/libexec/evolution-data-server/evolution-alarm-notify SegvAnalysis: Segfault happened at: 0x7f7332a444b0: Cannot access memory at address 0x7f7332a444b0 PC (0x7f7332a444b0) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: evolution-alarm-notify crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to lunar on 2022-09-30 (170 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo separator: ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash lunar need-amd64-retrace ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/2012294 Title: evolution-alarm-notify crashed with SIGSEGV in g_closure_invoke() Status in evolution-data-server package in Ubuntu: New Bug description: crashed when login to x11 session ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: evolution-data-server 3.47.3-1 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 00:27:25 2023 Disassembly: => 0x7f7332a444b0: Cannot access memory at address 0x7f7332a444b0 ExecutablePath: /usr/libexec/evolution-data-server/evolution-alarm-notify InstallationDate: Installed on 2020-06-25 (997 days ago) InstallationMedia: JournalErrors: Mar 21 00:27:22 hostname gnome-control-c[178036]: No gedit is installed here. Colors won't be updated. Please fix your installation. Mar 21 00:27:25 hostname kernel: show_signal_msg: 1 callbacks suppressed ProcCmdline: /usr/libexec/evolution-data-server/evolution-alarm-notify SegvAnalysis: Segfault happened at: 0x7f7332a444b0:Cannot access memory at address 0x7f7332a444b0 PC (0x7f7332a444b0) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: evolution-alarm-notify crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to lunar on 2022-09-30 (170 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/2012294/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012293] [NEW] package libgl1-mesa-dri 22.3.6-1ubuntu2 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libg
Public bug reported: unexpected crashed when login to x11 session ProblemType: Package DistroRelease: Ubuntu 23.04 Package: libgl1-mesa-dri 22.3.6-1ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Mar 7 23:00:26 2023 DistroCodename: lunar DistroVariant: ubuntu ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 InstallationDate: Installed on 2020-06-25 (997 days ago) InstallationMedia: Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: mesa Title: package libgl1-mesa-dri 22.3.6-1ubuntu2 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 UpgradeStatus: Upgraded to lunar on 2022-09-30 (170 days ago) ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2012293 Title: package libgl1-mesa-dri 22.3.6-1ubuntu2 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 Status in mesa package in Ubuntu: New Bug description: unexpected crashed when login to x11 session ProblemType: Package DistroRelease: Ubuntu 23.04 Package: libgl1-mesa-dri 22.3.6-1ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Mar 7 23:00:26 2023 DistroCodename: lunar DistroVariant: ubuntu ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 InstallationDate: Installed on 2020-06-25 (997 days ago) InstallationMedia: Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: mesa Title: package libgl1-mesa-dri 22.3.6-1ubuntu2 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 UpgradeStatus: Upgraded to lunar on 2022-09-30 (170 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2012293/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012288] [NEW] Ubuntu Gnome Settings / Chrome / CUPS (printing) communications
Public bug reported: I am trying to print. Context :: printer - The network printer I have "HP LaserJet Professional M1217nfw MFP" announces itself via Bonjour, supports SLP Config, LPD Printing and WS-Discovery. The printer is wired to ethernet, and receives it's IP address in IPV4 and IPV6 from the router, set statically at the router. Client - The client machine, Ubuntu 22.10 , is either on wireless (192.168.2.X - DHCP assigned randomly) or wired ethernet (192.168.2.Y - DHCP assigned statically). Sometimes the machine has both interfaces as well as receiving IPV6 addresses for both of these interfaces. It's unclear how printing occurs for discovery, but for comparison - Android "just works", iPhone "just works" , and Windows 10 "just works". Only Ubuntu is the outlier here. When printing a PDF from Chrome, I see there is a mismatch between the printers that Chrome sees, and the printers that are registered with the gnome(?) printers configuration settings. This leads me to believe that these 2 parts of printing are not in sync with one another(!!). Additional, possibly related behavior: When I remove all printers listed. And simply watch the Gnome(?) Printers settings section then a new printer is added automatically exactly this text, yes the duplicate 'HP': "HP HP Laserjet Professional M1217nfw MFP, driverless". This may be a cause of issues since I have not configured an additional printer, yet it appears. When I DO attempt to print to this auto-added printer I receive a vague error after some kind of timeout "Stopped Please restart when the problem is resolved" --- what problem ? What is causing the issue ? This error does not help identify the issue. Can you help me understand what is happening here and how this can be resolved ? If auto-adding a printer is going to magically work , then please include detailed, actionable error messages. Attached -- screenshot of printer subsystems mismatch. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.85.05 Sat Jan 14 00:49:50 UTC 2023 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1) ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 20 11:54:41 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.19.0-31-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-35-generic, x86_64: installed nvidia/525.85.05, 5.19.0-35-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-31-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (70 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-01-15 (64 days ago) dmi.bios.date: 02/09/2023 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET83W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET83W(1.59):bd02/09/2023:br1.59:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO nvidia-settings: ERROR: An internal
[Desktop-packages] [Bug 2012268] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all
** Package changed: ubuntu => alsa-driver (Ubuntu) -- 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/2012268 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: I was using WINDOWS operating system. The speakers worked very well there. first I used Linux Mint, when the sound didn't work, I installed ubuntu but it didn't work in any way. on first install dummy output was written on the sound panel in the settings. I searched on Google why this problem was caused, but many people with similar problems could not find a solution. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kadir 1563 F pulseaudio /dev/snd/controlC1: kadir 1563 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 20 14:56:06 2023 InstallationDate: Installed on 2023-03-20 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: BKX-Usb2.0 2MP Camera - BKX-Usb2.0 2MP Camera Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kadir 1563 F pulseaudio /dev/snd/controlC1: kadir 1563 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/28/2021 dmi.bios.release: 87.176 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: TN1V7.10_Monster dmi.board.asset.tag: Board Asset Tag dmi.board.name: Huma H5 V3.2 dmi.board.vendor: Monster dmi.board.version: V20 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Monster dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 6.6 dmi.modalias: dmi:bvnINSYDECorp.:bvrTN1V7.10_Monster:bd12/28/2021:br87.176:efr6.6:svnMONSTER:pnHumaH5V3.2:pvrV10:rvnMonster:rnHumaH5V3.2:rvrV20:cvnMonster:ct10:cvrChassisVersion:skuH5V32TN1156MSCD: dmi.product.family: HUMA dmi.product.name: Huma H5 V3.2 dmi.product.sku: H5V32TN1156MSCD dmi.product.version: V10 dmi.sys.vendor: MONSTER mtime.conffile..etc.modprobe.d.alsa-base.conf: 2023-03-20T11:22:39.676675 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2012268/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012268] [NEW] [HDA-Intel - HDA Intel PCH, playback] No sound at all
You have been subscribed to a public bug: I was using WINDOWS operating system. The speakers worked very well there. first I used Linux Mint, when the sound didn't work, I installed ubuntu but it didn't work in any way. on first install dummy output was written on the sound panel in the settings. I searched on Google why this problem was caused, but many people with similar problems could not find a solution. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kadir 1563 F pulseaudio /dev/snd/controlC1: kadir 1563 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 20 14:56:06 2023 InstallationDate: Installed on 2023-03-20 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: BKX-Usb2.0 2MP Camera - BKX-Usb2.0 2MP Camera Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kadir 1563 F pulseaudio /dev/snd/controlC1: kadir 1563 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/28/2021 dmi.bios.release: 87.176 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: TN1V7.10_Monster dmi.board.asset.tag: Board Asset Tag dmi.board.name: Huma H5 V3.2 dmi.board.vendor: Monster dmi.board.version: V20 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Monster dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 6.6 dmi.modalias: dmi:bvnINSYDECorp.:bvrTN1V7.10_Monster:bd12/28/2021:br87.176:efr6.6:svnMONSTER:pnHumaH5V3.2:pvrV10:rvnMonster:rnHumaH5V3.2:rvrV20:cvnMonster:ct10:cvrChassisVersion:skuH5V32TN1156MSCD: dmi.product.family: HUMA dmi.product.name: Huma H5 V3.2 dmi.product.sku: H5V32TN1156MSCD dmi.product.version: V10 dmi.sys.vendor: MONSTER mtime.conffile..etc.modprobe.d.alsa-base.conf: 2023-03-20T11:22:39.676675 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- [HDA-Intel - HDA Intel PCH, playback] No sound at all https://bugs.launchpad.net/bugs/2012268 You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver 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 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share
So, I was investigating this issue for a while and after some debugging of journalctl --user and dbus, it's possible to see that the gvfs-daemon.service was being started too early due to another tracker: "tracker-extract-3.service", which has WantedBy=default.target. This default value of default.target is graphical.target, and that is also too early for gvfsd to be able to get the correct environment. So, after disabling tracker-extract-3.service, changing its Wantedby to gnome-session.target and then reenabling it, the gvfsd service is now started with the right environment. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: Nautilus does not use a valid Kerberos ticket when accessing Samba share Status in gvfs: New Status in gvfs package in Ubuntu: Triaged Bug description: Nautilus prompts for username and password when accessing a Samba share on a network drive, despite having a perfectly valid unexpired Kerberos ticket. The Kerberos ticket is obtained automatically at logon by authentication against a Samba Active Directory server (Samba AD-DC). Accessing the same Samba share with the same Kerberos ticket via "smbclient //host/sharename -k" works fine. One known workaround is: "nautilus -q", and then "killall gvfsd". After that, accessing the Samba share with Nautilus works normally as it should. I did not experience this issue in Ubuntu 16.04. It appears that a regression was introduced somewhere between 16.04 and 18.04. The issue is quite annoying and confusing for the users who are used to accessing Samba shares on the network drive without being prompted for their username and password. The issue appears to manifest itself usually not on the first access to a Samba share, but on subsequent accesses after a system reboot or upon user logout/login. Strangely, removing ~/.cache/ibus/bus/registry file before user login appears to fix the issue for the current user session, but then the problem reappears upon subsequent user logins or after a system reboot. Nemo appears to have the same problem as Nautilus. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs-daemons 1.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 3 11:12:06 2018 ExecutablePath: /usr/lib/gvfs/gvfsd InstallationDate: Installed on 2018-04-27 (66 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=en_CA.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1779890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011823] Re: Update mouse accents for Yaru color styles
Oh, actually it's not properly fixed... :( ** Changed in: gnome-control-center (Ubuntu) Status: Fix Released => In Progress -- 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/2011823 Title: Update mouse accents for Yaru color styles Status in gnome-control-center package in Ubuntu: In Progress Bug description: gnome-control-center 44 introduced some additional graphics on the Mouse & Touchpad panels. (Note that there is a switcher on the top of the page to toggle between Mouse or Touchpad.) Since this blue line art is similar to that seen on the Multitasking page, I think it would be nice if these graphics were patched to support the Yaru accent color styles too. Marco pointed out that these are actually webm files so it's more work for the different colors. https://gitlab.gnome.org/Teams/Design/settings-mockups/-/blob/master/mouse-and-touchpad/src/mouse-touchpad-v2.blend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011823/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993621] Re: Force update keyboard LEDs after calling EnableDevice to fix its hardware state after VT switching
This bug was fixed in the package xorg-server - 2:21.1.3-2ubuntu2.8 --- xorg-server (2:21.1.3-2ubuntu2.8) jammy; urgency=medium * patches: Force update LEDs after device state update. (LP: #1993621) -- Timo Aaltonen Tue, 21 Feb 2023 18:01:37 +0200 ** Changed in: xorg-server (Ubuntu Jammy) Status: Fix Committed => Fix Released -- 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/1993621 Title: Force update keyboard LEDs after calling EnableDevice to fix its hardware state after VT switching Status in OEM Priority Project: New Status in X.Org X server: New Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Fix Released Status in xorg-server source package in Kinetic: Fix Released Bug description: [ Impact ] * This change will force update keyboard LED status after calling EnableDevice, in order to resolve LED status not syncing after switching VT to a X session. * This also fixes the issue with NVIDIA driver and Xorg, that after resuming from suspend the keyboard LED is always off. [ Test Plan ] 1. Log onto an GNOME Xorg session (KDE Kwin worked this issue around) 2. Turn on NumLock on the keyboard 3. Use Ctrl-Alt-F3 to switch to a text console, then Ctrl-Alt-F2 to switch back to desktop NumLock LED should be on after switching back to the desktop [ Where problems could occur ] * The changes are to push status to the device when enabling it regardless of actual keyboard state change, therefore switching between VTs and adding/removing keyboard/mouse/xinput devices should be affected by this change. [ Original Report ] Switching virtual terminals [Ctrl-Alt-F1 - F7] to a X session turns off keyboard LEDs. This issue is reproducible on 2:21.1.3-2ubuntu2.1 (on 22.04) To reproduce: 1. Log on a X session desktop (GNOME Xorg for example) 2. Turn on NumLock 3. Use Ctrl-Alt-F3 to switch to a text console, then Ctrl-Alt-F2 to switch back to desktop Expected: NumLock LED should be on Actual: NumLock LED is off, but functions like NumLock is on. If NumLock is pressed the LED turns off as well as the function. If CapsLock is pressed the LED states sync back (LED turns back on). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1993621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993621] Update Released
The verification of the Stable Release Update for xorg-server has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1993621 Title: Force update keyboard LEDs after calling EnableDevice to fix its hardware state after VT switching Status in OEM Priority Project: New Status in X.Org X server: New Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Fix Released Status in xorg-server source package in Kinetic: Fix Released Bug description: [ Impact ] * This change will force update keyboard LED status after calling EnableDevice, in order to resolve LED status not syncing after switching VT to a X session. * This also fixes the issue with NVIDIA driver and Xorg, that after resuming from suspend the keyboard LED is always off. [ Test Plan ] 1. Log onto an GNOME Xorg session (KDE Kwin worked this issue around) 2. Turn on NumLock on the keyboard 3. Use Ctrl-Alt-F3 to switch to a text console, then Ctrl-Alt-F2 to switch back to desktop NumLock LED should be on after switching back to the desktop [ Where problems could occur ] * The changes are to push status to the device when enabling it regardless of actual keyboard state change, therefore switching between VTs and adding/removing keyboard/mouse/xinput devices should be affected by this change. [ Original Report ] Switching virtual terminals [Ctrl-Alt-F1 - F7] to a X session turns off keyboard LEDs. This issue is reproducible on 2:21.1.3-2ubuntu2.1 (on 22.04) To reproduce: 1. Log on a X session desktop (GNOME Xorg for example) 2. Turn on NumLock 3. Use Ctrl-Alt-F3 to switch to a text console, then Ctrl-Alt-F2 to switch back to desktop Expected: NumLock LED should be on Actual: NumLock LED is off, but functions like NumLock is on. If NumLock is pressed the LED turns off as well as the function. If CapsLock is pressed the LED states sync back (LED turns back on). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1993621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993621] Re: Force update keyboard LEDs after calling EnableDevice to fix its hardware state after VT switching
This bug was fixed in the package xorg-server - 2:21.1.4-2ubuntu1.6 --- xorg-server (2:21.1.4-2ubuntu1.6) kinetic; urgency=medium * patches: Force update LEDs after device state update. (LP: #1993621) -- Timo Aaltonen Tue, 21 Feb 2023 17:17:27 +0200 ** Changed in: xorg-server (Ubuntu Kinetic) Status: Fix Committed => Fix Released -- 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/1993621 Title: Force update keyboard LEDs after calling EnableDevice to fix its hardware state after VT switching Status in OEM Priority Project: New Status in X.Org X server: New Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Fix Released Status in xorg-server source package in Kinetic: Fix Released Bug description: [ Impact ] * This change will force update keyboard LED status after calling EnableDevice, in order to resolve LED status not syncing after switching VT to a X session. * This also fixes the issue with NVIDIA driver and Xorg, that after resuming from suspend the keyboard LED is always off. [ Test Plan ] 1. Log onto an GNOME Xorg session (KDE Kwin worked this issue around) 2. Turn on NumLock on the keyboard 3. Use Ctrl-Alt-F3 to switch to a text console, then Ctrl-Alt-F2 to switch back to desktop NumLock LED should be on after switching back to the desktop [ Where problems could occur ] * The changes are to push status to the device when enabling it regardless of actual keyboard state change, therefore switching between VTs and adding/removing keyboard/mouse/xinput devices should be affected by this change. [ Original Report ] Switching virtual terminals [Ctrl-Alt-F1 - F7] to a X session turns off keyboard LEDs. This issue is reproducible on 2:21.1.3-2ubuntu2.1 (on 22.04) To reproduce: 1. Log on a X session desktop (GNOME Xorg for example) 2. Turn on NumLock 3. Use Ctrl-Alt-F3 to switch to a text console, then Ctrl-Alt-F2 to switch back to desktop Expected: NumLock LED should be on Actual: NumLock LED is off, but functions like NumLock is on. If NumLock is pressed the LED turns off as well as the function. If CapsLock is pressed the LED states sync back (LED turns back on). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1993621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003168] Re: Dock becomes unresponsive after unlocking the screen: JS ERROR: TypeError: dockManager is null
Okay thank you i will delete dash-to-d...@micxgx.gmail.com -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2003168 Title: Dock becomes unresponsive after unlocking the screen: JS ERROR: TypeError: dockManager is null Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: SIdebar, files gets unresponsive after unlocking locked season. Clicking on search bar also freezes the whole season. Issue requires Restarting GTK3 or restarting the season. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-59.65-generic 5.15.78 Uname: Linux 5.15.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 18 13:35:36 2023 InstallationDate: Installed on 2021-06-20 (576 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2003168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2010561] Re: The Netplan Everywhere NetworkManager fails to supply Netplan with networking information until a connection is deleted and re-created
Maybe something like this pseudo-code in network-manager preinst maintainer script: foreach UUID in $(cat /etc/NetworkManager/system-connections/* | grep "^uuid=") ORIG_ID=$(nmcli --get-values connection.id con show $UUID) nmcli con mod $UUID con-name $ORIG_ID".NETPLAN" nmcli con reload nmcli con mod $UUID con-name $ORIG_ID While on it, we should probably also make the network-manager package install a /etc/NetworkManager/system-connections/README file after migration, which states that the existing connection profiles have been migrated to /etc/netplan (and where a backup can be found). -- 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/2010561 Title: The Netplan Everywhere NetworkManager fails to supply Netplan with networking information until a connection is deleted and re-created Status in netplan: Triaged Status in network-manager package in Ubuntu: New Bug description: Steps to reproduce: 1. Install Ubuntu Lunar or a flavor thereof onto physical hardware with a WiFi adapter. (I used Lubuntu Lunar.) 2. Connect to WiFi and install all updates. 3. Enable the Netplan Everywhere PPA and install the updated NetworkManager from it (further details at https://discourse.ubuntu.com/t/call-for-testing-networkmanager-yaml-settings/32420?u=arraybolt3) 4. When the installation finishes, run "sudo netplan get". Expected result: Networking information related to the WiFi connection should appear in the "sudo netplan get" output. Actual result: "sudo netplan get" returns the following: ** (process:4088): WARNING **: 12:41:41.394; Permissions for /etc/netplan/01-network-manager-all.yaml are too open. Netplan configuration should NOT be accessible by others. network: version: 2 renderer: NetworkManager End of output. Additionally, the /etc/netplan folder does not contain files that I would expect to be there that would contain the networking info. Additional information: If I disconnect from WiFi, then delete my WiFi connection entirely in nmtui, and *then* reconnect to the same WiFi network, "sudo netplan get" returns the expected networking information. /etc/netplan is also properly populated after doing this. This bug seems like it will probably cause unintended behavior after an upgrade from 23.04 (which uses normal NetworkManager) to 23.10 (which is supposed to be using the Netplan Everywhere NetworkManager). People probably won't know to entirely delete the WiFi and other connections and then reconnect them in order for the netplan output to be usable. To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2010561/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012282] Re: [gnome-shell 44~rc-1ubuntu2, Ubuntu 23.04 (development branch)] Wrong background color in application folders
** Attachment added: "Ubuntu 23.04 BAD" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012282/+attachment/5655905/+files/Ubuntu_23_04_BAD.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2012282 Title: [gnome-shell 44~rc-1ubuntu2, Ubuntu 23.04 (development branch)] Wrong background color in application folders Status in gnome-shell package in Ubuntu: New Bug description: Problem summary: After upgrading from Ubuntu 22.10 to Ubuntu 23.04 (development branch) the gnome-shell application folders background is shown in white color instead of dark grey color making impossible to read it's contents. I'm using the default Ubuntu theming. I've attached two screenshots: - Ubuntu_22_10_OK.png: where you can see that application folder background is dark grey as expected. - Ubuntu_23_04_BAD.png: where you can see that application folder background is white and content is unreadable. Additional data: System Model: Raspberry Pi 4 Model B Rev 1.4 8Gb Kernel: Linux fpgrpi 5.19.0-1015-raspi #22-Ubuntu SMP PREEMPT Mon Mar 6 10:35:33 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -rd No LSB modules are available. Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 # apt-cache policy gnome-shell gnome-shell: Instalados: 44~rc-1ubuntu2 Candidato: 44~rc-1ubuntu2 Tabla de versión: *** 44~rc-1ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012282] Re: [gnome-shell 44~rc-1ubuntu2, Ubuntu 23.04 (development branch)] Wrong background color in application folders
** Attachment added: "Ubuntu 22.10 OK" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012282/+attachment/5655904/+files/Ubuntu_22_10_OK.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2012282 Title: [gnome-shell 44~rc-1ubuntu2, Ubuntu 23.04 (development branch)] Wrong background color in application folders Status in gnome-shell package in Ubuntu: New Bug description: Problem summary: After upgrading from Ubuntu 22.10 to Ubuntu 23.04 (development branch) the gnome-shell application folders background is shown in white color instead of dark grey color making impossible to read it's contents. I'm using the default Ubuntu theming. I've attached two screenshots: - Ubuntu_22_10_OK.png: where you can see that application folder background is dark grey as expected. - Ubuntu_23_04_BAD.png: where you can see that application folder background is white and content is unreadable. Additional data: System Model: Raspberry Pi 4 Model B Rev 1.4 8Gb Kernel: Linux fpgrpi 5.19.0-1015-raspi #22-Ubuntu SMP PREEMPT Mon Mar 6 10:35:33 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -rd No LSB modules are available. Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 # apt-cache policy gnome-shell gnome-shell: Instalados: 44~rc-1ubuntu2 Candidato: 44~rc-1ubuntu2 Tabla de versión: *** 44~rc-1ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012282] [NEW] [gnome-shell 44~rc-1ubuntu2, Ubuntu 23.04 (development branch)] Wrong background color in application folders
Public bug reported: Problem summary: After upgrading from Ubuntu 22.10 to Ubuntu 23.04 (development branch) the gnome-shell application folders background is shown in white color instead of dark grey color making impossible to read it's contents. I'm using the default Ubuntu theming. I've attached two screenshots: - Ubuntu_22_10_OK.png: where you can see that application folder background is dark grey as expected. - Ubuntu_23_04_BAD.png: where you can see that application folder background is white and content is unreadable. Additional data: System Model: Raspberry Pi 4 Model B Rev 1.4 8Gb Kernel: Linux fpgrpi 5.19.0-1015-raspi #22-Ubuntu SMP PREEMPT Mon Mar 6 10:35:33 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -rd No LSB modules are available. Description:Ubuntu Lunar Lobster (development branch) Release:23.04 # apt-cache policy gnome-shell gnome-shell: Instalados: 44~rc-1ubuntu2 Candidato: 44~rc-1ubuntu2 Tabla de versión: *** 44~rc-1ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/main arm64 Packages 100 /var/lib/dpkg/status ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2012282 Title: [gnome-shell 44~rc-1ubuntu2, Ubuntu 23.04 (development branch)] Wrong background color in application folders Status in gnome-shell package in Ubuntu: New Bug description: Problem summary: After upgrading from Ubuntu 22.10 to Ubuntu 23.04 (development branch) the gnome-shell application folders background is shown in white color instead of dark grey color making impossible to read it's contents. I'm using the default Ubuntu theming. I've attached two screenshots: - Ubuntu_22_10_OK.png: where you can see that application folder background is dark grey as expected. - Ubuntu_23_04_BAD.png: where you can see that application folder background is white and content is unreadable. Additional data: System Model: Raspberry Pi 4 Model B Rev 1.4 8Gb Kernel: Linux fpgrpi 5.19.0-1015-raspi #22-Ubuntu SMP PREEMPT Mon Mar 6 10:35:33 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -rd No LSB modules are available. Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 # apt-cache policy gnome-shell gnome-shell: Instalados: 44~rc-1ubuntu2 Candidato: 44~rc-1ubuntu2 Tabla de versión: *** 44~rc-1ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2010561] Re: The Netplan Everywhere NetworkManager fails to supply Netplan with networking information until a connection is deleted and re-created
Hi Aaron, thank you very much for testing and spotting this "issue". What you see is currently the "expected behavior", as described in https://netplan.readthedocs.io/en/latest/netplan-everywhere/#how-connections-are-managed-from-now-on I.e. connection profiles not being imported into /etc/netplan by default (on installation), but only once (re-)created or modified through NetworkManager. But maybe it's not the way that users would intuitively expect it to be and the NetworkManager package should automatically re-create and import all current connection profiles from /etc/NetworkManager/system- connections/ into /etc/netplan on installation time. ** Changed in: netplan Status: New => Triaged ** Changed in: netplan Importance: Undecided => Medium ** Tags added: netplan-everywhere ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/2010561 Title: The Netplan Everywhere NetworkManager fails to supply Netplan with networking information until a connection is deleted and re-created Status in netplan: Triaged Status in network-manager package in Ubuntu: New Bug description: Steps to reproduce: 1. Install Ubuntu Lunar or a flavor thereof onto physical hardware with a WiFi adapter. (I used Lubuntu Lunar.) 2. Connect to WiFi and install all updates. 3. Enable the Netplan Everywhere PPA and install the updated NetworkManager from it (further details at https://discourse.ubuntu.com/t/call-for-testing-networkmanager-yaml-settings/32420?u=arraybolt3) 4. When the installation finishes, run "sudo netplan get". Expected result: Networking information related to the WiFi connection should appear in the "sudo netplan get" output. Actual result: "sudo netplan get" returns the following: ** (process:4088): WARNING **: 12:41:41.394; Permissions for /etc/netplan/01-network-manager-all.yaml are too open. Netplan configuration should NOT be accessible by others. network: version: 2 renderer: NetworkManager End of output. Additionally, the /etc/netplan folder does not contain files that I would expect to be there that would contain the networking info. Additional information: If I disconnect from WiFi, then delete my WiFi connection entirely in nmtui, and *then* reconnect to the same WiFi network, "sudo netplan get" returns the expected networking information. /etc/netplan is also properly populated after doing this. This bug seems like it will probably cause unintended behavior after an upgrade from 23.04 (which uses normal NetworkManager) to 23.10 (which is supposed to be using the Netplan Everywhere NetworkManager). People probably won't know to entirely delete the WiFi and other connections and then reconnect them in order for the netplan output to be usable. To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2010561/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2009687] Re: [lunar] Nvidia GPU unused but still powered
I do not experience this issue anymore (GS 44rc, 6.2 kernel, 525 Ubuntu main driver). Using powertop does not seem to be reliable but looking at GNOME's energy panel, estimated remaining time seems ok. But it varies often with a 0.5 factor (without any visible reason). -- 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/2009687 Title: [lunar] Nvidia GPU unused but still powered Status in GNOME Shell: Unknown Status in The Ubuntu Power Consumption Project: Triaged Status in gnome-shell package in Ubuntu: Triaged Bug description: Hi, Lenovo Legion 5 16" i7 12700H RTX 3070 Ti Nvidia 525 proprietary driver (official Ubuntu packages) Nvidia on-demand mode Ubuntu Wayland or Xorg sessions Ubuntu Lunar up to date I noticed a high power usage using powertop (or simply remaining time in g-c-c...). Nvidia driver seems offloaded but gpu power usage still shows ~ 9W -> 23W, random. uname -a Linux ** 6.1.0-16-generic #16-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 24 14:37:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux nvidia-smi Wed Mar 8 10:59:21 2023 +-+ | NVIDIA-SMI 525.85.05Driver Version: 525.85.05CUDA Version: 12.0 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===+==+==| | 0 NVIDIA GeForce ... Off | :01:00.0 Off | N/A | | N/A 34CP8 9W / 50W | 4MiB / 8192MiB | 0% Default | | | | N/A | +---+--+--+ +-+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |=| |0 N/A N/A 5445 G /usr/bin/gnome-shell3MiB | +-+ glxinfo -B name of display: :1 display: :1 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: Intel (0x8086) Device: Mesa Intel(R) Graphics (ADL GT2) (0x46a6) Version: 22.3.6 Accelerated: yes Video memory: 31821MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.6 Max compat profile version: 4.6 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) Graphics (ADL GT2) OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.3.6 OpenGL core profile shading language version string: 4.60 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.3.6 OpenGL shading language version string: 4.60 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL ES profile version string: OpenGL ES 3.2 Mesa 22.3.6 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 lspci 00:00.0 Host bridge: Intel Corporation 12th Gen Core Processor Host Bridge/DRAM Registers (rev 02) 00:01.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x16 Controller #1 (rev 02) 00:02.0 VGA compatible controller: Intel Corporation Alder Lake-P Integrated Graphics Controller (rev 0c) 00:04.0 Signal processing controller: Intel Corporation Alder Lake Innovation Platform Framework Processor Participant (rev 02) 00:06.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x4 Controller #0 (rev 02) 00:06.2 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x4 Controller #2 (rev 02) 00:07.0 PCI bridge: Intel Corporation Alder Lake-P Thunderbolt 4 PCI Express Root Port #0 (rev 02) 00:0a.0 Signal processing controller: Intel Corporation Platform Monitoring Technology (rev 01) 00:0d.0 USB controller: Intel Corporation Alder Lake-P Thunderbolt 4 USB Controller (rev 02) 00:0d.2 USB controller: Intel Corporation Alder Lake-P Thunderbolt 4 NHI #0 (rev 02)
[Desktop-packages] [Bug 2001922] Re: Xorg crash
*** This bug is a duplicate of bug 2000649 *** https://bugs.launchpad.net/bugs/2000649 Is there something I can do to trigger this bugfix to incorporated into regular ubuntu updates? It's really annoying to work on unstable system, and knowing it has been fixed already, sigh..? -- 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/2001922 Title: Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: My Ubuntu 22.04.1 LTS installation crashes, but I was not able to figure out how to reproducibly trigger the crash. The last time it happened was with firefox and zoom running, the display suddenly went black and after a few seconds the X login screen appeared, my session gone. There are files in /var/crash/ -rw-r--r-- 1 root whoopsie0 Jan 5 14:09 _usr_lib_xorg_Xorg.0.upload -rw-r- 1 root whoopsie 12792518 Jan 5 14:09 _usr_lib_xorg_Xorg.0.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:09 _usr_lib_xorg_Xorg.0.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _usr_bin_xfsettingsd.1000.upload -rw-r- 1 petr whoopsie 516897 Jan 5 14:13 _usr_bin_xfsettingsd.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _usr_bin_xfsettingsd.1000.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _opt_zoom_zoom.1000.upload -rw-r- 1 petr whoopsie 46590288 Jan 5 14:13 _opt_zoom_zoom.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _opt_zoom_zoom.1000.uploaded and .xsession-errors.old ends with (xfwm4:8122): xfwm4-WARNING **: 14:11:00.736: unmanaged net_wm_state (window 0x649, atom "_NET_WM_STATE_STAYS_ON_TOP") (xfwm4:10847): Gtk-WARNING **: 14:13:01.216: cannot open display: :0.0 Exiting due to channel error. Failed to parse arguments: Cannot open display: :0.0 Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfsettingsd:10849): xfsettingsd-ERROR **: 14:13:01.239: Unable to open display. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfwm4:10854): Gtk-WARNING **: 14:13:01.244: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10860): Gtk-WARNING **: 14:13:01.264: cannot open display: :0.0 (xfwm4:10863): Gtk-WARNING **: 14:13:01.280: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10865): Gtk-WARNING **: 14:13:01.293: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Is it safe and useful to upload the files from /var/crash/? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Thu Jan 5 14:17:42 2023 DistUpgraded: 2022-12-25 11:03:07,557 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.13.0-35-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-56-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:3f96] InstallationDate: Installed on 2021-11-07 (424 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20YA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to jammy on 2022-12-25 (11 days ago) dmi.bios.date: 09/23/2021 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: GMCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: ThinkBook 13s G3 ACN dmi.ec.firmware.release: 1.19 dmi.modalias:
[Desktop-packages] [Bug 1998207] Re: netplan network-manager plugin tries to save temporary connections
** Changed in: netplan Status: Triaged => Invalid -- 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/1998207 Title: netplan network-manager plugin tries to save temporary connections Status in netplan: Invalid Status in network-manager package in Ubuntu: Triaged Bug description: *** Note: This bug is mostly about comment #10, now *** When creating an OpenVPN connection, a temporal connection called tunN is created. For instance, after activating a connection called vpntest, I have: NAME UUID TYPE DEVICE vpntest 458856e6-8f0f-4dc6-82f2-dd72868252a0 vpn ens3 tun0 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 tun tun0 tun0 is created/removed after activating/deactivating vpntest and should not really be saved, but I see netplan adding it in /etc/netplan. And while doing so the plugin also reports some errors (I see these when stopping the connection): Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920] BUG: the profile cannot be stored in keyfile format without becoming unusable: cannot access file: No such file or directory Nov 28 16:16:57 ubuntu NetworkManager[11752]: ((src/libnm-core-impl/nm-connection.c:342)): assertion '' failed Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920] keyfile: commit: failure to write 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 ((null)) to "/run/NetworkManager/system-connections/tun0-1eb1dbe8-5678-4818-9adf-fb2dc01ed132.nmconnection": keyfile writer produces an invalid connection: cannot access file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1998207/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012146] Re: very high cpu usage, system unresponsive
Sorry, that comment was incorrect, obviously; for some reason my eyes betrayed me 8-( Still have the same problem but clearly not related to this 8-( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2012146 Title: very high cpu usage, system unresponsive Status in ibus package in Ubuntu: New Bug description: may be related to Ardour 7.3, when I start ardour and start working with the app, the system slows down and htop shows 100% cpu usage for ibus-daemon ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ibus 1.5.28-2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 18 15:21:55 2023 InstallationDate: Installed on 2022-05-13 (308 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: ibus UpgradeStatus: Upgraded to lunar on 2023-03-17 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2012146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012146] Re: very high cpu usage, system unresponsive
Not sure it is related, but I have what seems to be the same issue but I'm still on 22.10. I see the following in dpkg.log: 2023-02-15 10:48:53 upgrade libusb-1.0-0-dev:amd64 2:1.0.25-1ubuntu2 2:1.0.26-1 I had no problems before, so to me it looks like that update might have caused it. I will revert that back and see if the issues are gone. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2012146 Title: very high cpu usage, system unresponsive Status in ibus package in Ubuntu: New Bug description: may be related to Ardour 7.3, when I start ardour and start working with the app, the system slows down and htop shows 100% cpu usage for ibus-daemon ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ibus 1.5.28-2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 18 15:21:55 2023 InstallationDate: Installed on 2022-05-13 (308 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: ibus UpgradeStatus: Upgraded to lunar on 2023-03-17 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2012146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011281] Re: chromium snap upgrade "lost" my passwords
Actually only the minor part of your problem has been fixed, the password notice. Still, the passwords, of course, should not disappear. And in my tests in the Ubuntu GNOME desktop they really don't. However, I just tested in my simplified dwm environment and I can confirm that, although the keyring is running and unlocked, the passwords aren't displayed in Chromium, but they are there in `Login Data`. So Chromium has been failing to detect[1] that Gnome keyring is available. When you observed that behavior, were you perchance in such a minimal environment — for which I filed LP: 2011474 —, or were you on default Ubuntu? Also you can verify whether or not Chromium is detecting that the Gnome Keyring is available by enabling logging and grepping for OSCrypt. E.g.: ---> % chromium --password-store= --enable-logging=stderr --v=1 |& grep 'backend for OSCrypt' [...] Selected backend for OSCrypt: BASIC_TEXT % chromium --password-store=gnome --enable-logging=stderr --v=1 |& grep 'backend for OSCrypt' [...] Selected backend for OSCrypt: GNOME_ANY <--- [1] https://chromium.googlesource.com/chromium/src/+/master/docs/linux/password_storage.md ** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Incomplete -- 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/2011281 Title: chromium snap upgrade "lost" my passwords Status in chromium-browser package in Ubuntu: Incomplete Bug description: On upgrade to chromium snap revision 2333 (now since upgraded to 2367), I received a window with a notice about password migration: "Password storage via the Gnome keyring has been fixed, but for it to work, you have to rename your old ~/snap/chromium/common/chromium/Default/Login Data file so that a new, working one can replace it." I don't remember if I did this or not. However, when I went to use my saved passwords in chromium today, I found that they were absent. Tracking down the data in the chromium profile, I found that there was a ~/snap/chromium/common/chromium/Default/Login Data.old containing all of my passwords, and a ~/snap/chromium/common/chromium/Default/Login Data containing a single password entry for a site that I happened to have created a new login for in the past few days. That's not a very user-friendly experience on upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2011281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2008798] Re: webkit2gtk 2.39.90 fails to build on riscv64
The issue is fixed now in the current revision ** Changed in: webkit2gtk (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2008798 Title: webkit2gtk 2.39.90 fails to build on riscv64 Status in Webkit: Unknown Status in webkit2gtk package in Ubuntu: Fix Released Bug description: webkit2gtk fails to build on riscv64. Debian's experimental build logs suggest that 2.39.3 built fine on riscv64, but this error has occurred since 2.39.5. https://launchpad.net/ubuntu/+source/webkit2gtk/2.39.90-1ubuntu1 There are more details on the upstream bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/2008798/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1891338] Re: apparmor misconfigured for evince
This bug appears again in the package evince 42.3-0ubuntu3 in Xubuntu 22.04.2 It looks the same as described by Kenneth Zadeck in the original report, except the message says: 'Failed to execute child process "/usr/bin/xfce4-mime-helper"(Permission denied).' In the dmesg logs I see the following: [ 804.143236] audit: type=1400 audit(1679303089.957:269): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/bin/xfce4-mime-helper" pid=16286 comm="exo-open" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 I edited /etc/apparmor.d/usr.bin.evince # For Xubuntu to launch the browser #include /usr/bin/xfce4-mime-helper ixr, # < adding this line A new message appeared in dmesg logs: [ 838.828241] audit: type=1400 audit(1679303124.641:304): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/bin/snap" pid=16706 comm="xfce4-mime-help" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 I have two browsers Brave and Firefox; and both installed from snap. So I edited /etc/apparmor.d/usr.bin.evince again: # For Xubuntu to launch the browser #include /usr/bin/xfce4-mime-helper ixr, /usr/bin/snap ixr, # < adding this line And it complained again: [ 1268.978351] audit: type=1400 audit(1679303554.790:432): apparmor="DENIED" operation="connect" profile="/usr/bin/evince" name="/run/snapd.socket" pid=20462 comm="brave" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=0 And I edited /etc/apparmor.d/usr.bin.evince again: # For Xubuntu to launch the browser #include /usr/bin/xfce4-mime-helper ixr, /usr/bin/snap ixr, /run/snapd.socket wr, # < adding this line And then I was overwhelmed by the following messages. [ 1817.693397] audit: type=1400 audit(1679304103.502:3198): apparmor="DENIED" operation="open" profile="/usr/bin/evince" name="/snap/brave/216/meta/snap.yaml" pid=25949 comm="brave" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 1822.942739] audit: type=1400 audit(1679304108.750:3199): apparmor="DENIED" operation="open" profile="/usr/bin/evince" name="/sys/kernel/mm/transparent_hugepage/hpage_pmd_size" pid=26810 comm="brave" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 1822.947632] audit: type=1400 audit(1679304108.754:3200): apparmor="DENIED" operation="open" profile="/usr/bin/evince" name="/proc/cgroups" pid=26810 comm="brave" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 1822.949047] audit: type=1400 audit(1679304108.758:3201): apparmor="DENIED" operation="open" profile="/usr/bin/evince" name="/proc/cmdline" pid=26810 comm="brave" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 1822.949070] audit: type=1400 audit(1679304108.758:3202): apparmor="DENIED" operation="open" profile="/usr/bin/evince" name="/snap/snapd/18357/usr/lib/snapd/info" pid=26810 comm="brave" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 1822.950430] audit: type=1400 audit(1679304108.758:3203): apparmor="DENIED" operation="open" profile="/usr/bin/evince" name="/proc/sys/kernel/seccomp/actions_avail" pid=26810 comm="brave" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 1822.950649] audit: type=1400 audit(1679304108.758:3204): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/snapd/snap-seccomp" pid=26816 comm="brave" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 [ 1822.950883] audit: type=1400 audit(1679304108.758:3205): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/bin/systemctl" pid=26817 comm="brave" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 [ 1822.951929] audit: type=1400 audit(1679304108.758:3206): apparmor="DENIED" operation="open" profile="/usr/bin/evince" name="/snap/brave/216/meta/snap.yaml" pid=26810 comm="brave" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 1868.523506] audit: type=1400 audit(1679304154.330:3207): apparmor="DENIED" operation="open" profile="/usr/bin/evince" name="/sys/kernel/mm/transparent_hugepage/hpage_pmd_size" pid=27098 comm="brave" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 1868.528801] audit: type=1400 audit(1679304154.338:3208): apparmor="DENIED" operation="open" profile="/usr/bin/evince" name="/proc/cgroups" pid=27098 comm="brave" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 1868.530290] audit: type=1400 audit(1679304154.338:3209): apparmor="DENIED" operation="open" profile="/usr/bin/evince" name="/proc/cmdline" pid=27098 comm="brave" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 1868.530325] audit: type=1400 audit(1679304154.338:3210): apparmor="DENIED" operation="open" profile="/usr/bin/evince" name="/snap/snapd/18357/usr/lib/snapd/info" pid=27098 comm="brave" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 1868.531868] audit: type=1400 audit(1679304154.338:3211): apparmor="DENIED" operation="open" profile="/usr/bin/evince"
[Desktop-packages] [Bug 2011770] Re: [gsd-rfkill] WwanEnabled never get synced
@seb128, Could you help review it or have someone help it? This issue will block our OEM schedule on 31th Mar. Thanks for your time. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2011770 Title: [gsd-rfkill] WwanEnabled never get synced Status in OEM Priority Project: Triaged Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: [ Impact ] * Sometimes on devices with WWAN card, whenever user presses the wireless function key (Fn+F8) or turn on the airplane mode radio button in Settings, the airplane mode will not be enabled, and the airplane mode icon is not shown in the status bar. * There is a unmerged upstream merge request that delivers the fix: https://gitlab.gnome.org/GNOME/gnome-settings- daemon/-/merge_requests/310 It works perfectly well on several Lenovo laptops with WWAN cards. The root causes is that the value of "WwanEnabled" under "org.freedesktop.NetworkManager" is not synced correctly, gsd-rfkill should listen to "g-properties-changed" instead of "g-signal" now. [ Test Plan ] 1. Find a machine which has WWAN card. 2. Boot the machine, and run rfkill list to see if WWAN is unblocked. if not use rfkill to unblock the WWAN, and reboot. 3. Press the wireless media key (Fn+F8) or turn on the airplane mode radio button in Settings. 4. The airplane mode should be enabled, but actually not. [ Where problems could occur ] * When user is using a very low version network-manager that still broadcasting DBUS "PropertiesChanged" events on "g-signal" instead of the concurrent "g-properties-changed", the airplane mode will sometimes not be able to enable. [ Other Info ] 1. About Ubuntu Description:Ubuntu 22.04.2 LTS Release:22.04 Kernel: 6.1.0-1007-oem 2. The version of packages: gnome-settings-daemon: Installed: 42.1-1ubuntu2.1 network-manager: Installed: 1.36.6-0ubuntu2 3. Expect: The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is called, and manager->wwan_enabled is set to the correct value. 4. Actual: The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is never called, so manager->wwan_enabled is not synced, If machine has WWAN device(s), and the initial value of manager->wwan_enabled is true, it will never be able to switch to airplane mode. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2011770/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012237] Re: Laptop freeze when trying to unlock session
Thanks for the bug report. Please: 1. Check for crashes: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment 2. Try disabling Ubuntu Dock and tell us if that prevents the bug: gnome-extensions disable ubuntu-d...@ubuntu.com ** Package changed: gnome-shell (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2012237 Title: Laptop freeze when trying to unlock session Status in Ubuntu: Incomplete Bug description: After locking the screen for sometime and then try to unlock, the whole laptop freeze and I have to hard reset. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 20 09:58:17 2023 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2023-01-04 (74 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2012237/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2000739] Re: Window actions (like maximize) no more work in wayland for QEMU using GTK backend once the guest UI is intialized.
** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2000739 Title: Window actions (like maximize) no more work in wayland for QEMU using GTK backend once the guest UI is intialized. Status in gtk+3.0 package in Ubuntu: New Status in qemu package in Ubuntu: Confirmed Bug description: Window actions (like maximize) no more work in wayland for QEMU using GTK backend once the guest UI is intialized. This can be seen by running an installed or even a trial Ubuntu from an ISO like: $ qemu-system-x86_64 \ -boot d \ -cdrom ubuntu-22.04.1-desktop-amd64.iso \ -m 4096M \ -machine type=q35,accel=kvm \ -cpu host \ -smp 2 \ -device qxl-vga The GTK UI of qemu has a feature called "fullscreen" which disables the screen decorations and sets the window to maximize. The decorations go away, but maximize doesn't work. The following details were found so far: - running with GDK_BACKEND=x11 works - using sdl instead of gtk backend works - using the old qemu of Focal, or the newest from upstream git in jammy all fails (no qemu change AFAICS) - host UI widgets (the square at the window top) do not work either - hotkeys (super-up) do not work either It seems that once the guest has enabled the desktop something changes and the maximize/minimize/... actions are no more processed. Not sure were to debug next in regard to the gnome/wayland UI handling of this - any idea? P.S. We can reproduce this in git builds of qemu, so we can debug of modify the code as needed. The code for this is mostly in [1] [1]: https://gitlab.com/qemu-project/qemu/-/blob/master/ui/gtk.c --- original report --- Running QEMU version 4.2.1 on Ubuntu 20.04 via qemu-system-x86_64 \ -boot d \ -cdrom ubuntu-22.04.1-desktop-amd64.iso \ -m 4096M \ -machine type=q35,accel=kvm \ -cpu host \ -smp 2 \ -device qxl-vga and pressing ctrl+alt+f after booting the Ubuntu 22.04 live ISO and adjusting the display resolution to match the native resolution, works as expected, i.e., the VM screen is correctly displayed in fullscreen. However, after running the same command for QEMU version 6.2.0 on Ubuntu 22.04 and pressing ctrl+alt+f after making the resolution adjustment, yields a fullscreen view where the space occupied by the GNOME top bar (top panel with date in center) of the host is not used. The top bar itself is not visible but instead the purple background is shown where the top bar resides. The problem also occurs when replacing '-device qxl-vga' by '-device VGA,vgamem_mb=64'. The problem however does not occur when using '-device virtio-vga'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2000739/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012237] [NEW] Laptop freeze when trying to unlock session
Public bug reported: After locking the screen for sometime and then try to unlock, the whole laptop freeze and I have to hard reset. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 20 09:58:17 2023 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2023-01-04 (74 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic -- 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/2012237 Title: Laptop freeze when trying to unlock session Status in gnome-shell package in Ubuntu: New Bug description: After locking the screen for sometime and then try to unlock, the whole laptop freeze and I have to hard reset. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 20 09:58:17 2023 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2023-01-04 (74 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012237/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003168] Re: Dock becomes unresponsive after unlocking the screen: JS ERROR: TypeError: dockManager is null
It looks dangerous that dash-to-dock is calling into ubuntu-dock. That's probably by accident. Please either: * Delete /home/yash/.local/share/gnome-shell/extensions/dash-to- d...@micxgx.gmail.com or * Run: gnome-extensions disable ubuntu-d...@ubuntu.com and then log in again. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2003168 Title: Dock becomes unresponsive after unlocking the screen: JS ERROR: TypeError: dockManager is null Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: SIdebar, files gets unresponsive after unlocking locked season. Clicking on search bar also freezes the whole season. Issue requires Restarting GTK3 or restarting the season. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-59.65-generic 5.15.78 Uname: Linux 5.15.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 18 13:35:36 2023 InstallationDate: Installed on 2021-06-20 (576 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2003168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003168] Re: Dock becomes unresponsive after unlocking the screen: JS ERROR: TypeError: dockManager is null
Thanks. The recurring issue seems to be: JS ERROR: TypeError: dockManager is null getApps@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js:1266:9 getRunningApps@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js:1276:12 _ensureLocations/<@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1728:55 _create/object[name]@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/utils.js:290:68 _doCheckOverlap@/home/yash/.local/share/gnome-shell/extensions/dash-to-d...@micxgx.gmail.com/intellihide.js:214:46 _checkOverlap@/home/yash/.local/share/gnome-shell/extensions/dash-to-d...@micxgx.gmail.com/intellihide.js:174:14 ** Summary changed: - SIdebar, files gets unresponsive after unlocking locked season. + Dock becomes unresponsive after unlocking the screen: JS ERROR: TypeError: dockManager is null ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2003168 Title: Dock becomes unresponsive after unlocking the screen: JS ERROR: TypeError: dockManager is null Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: SIdebar, files gets unresponsive after unlocking locked season. Clicking on search bar also freezes the whole season. Issue requires Restarting GTK3 or restarting the season. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-59.65-generic 5.15.78 Uname: Linux 5.15.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 18 13:35:36 2023 InstallationDate: Installed on 2021-06-20 (576 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2003168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2009506] Re: Input from an external mic can be barely noticeable, or not hearable at all
Resolved -- 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/2009506 Title: Input from an external mic can be barely noticeable, or not hearable at all Status in alsa-driver package in Ubuntu: New Bug description: The microphone from an external device not working. Input from an external mic can be barely noticeable, or not hearable at all. The headset is connected by a jack port. No option to adjust gain level for external Microphone(headset). Checked with different working headset. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maryna 1598 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 6 17:26:30 2023 InstallationDate: Installed on 2023-02-03 (31 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0GGCMJ dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd09/06/2022:br1.19:svnDellInc.:pnVostro3500:pvr:rvnDellInc.:rn0GGCMJ:rvrA01:cvnDellInc.:ct10:cvr:sku0A24: dmi.product.family: Vostro dmi.product.name: Vostro 3500 dmi.product.sku: 0A24 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2023-02-13T11:13:28.057933 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2009506/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003168] Re: SIdebar, files gets unresponsive after unlocking locked season.
I have attached Journal.txt ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2003168/+attachment/5655794/+files/journal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2003168 Title: SIdebar, files gets unresponsive after unlocking locked season. Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Expired Bug description: SIdebar, files gets unresponsive after unlocking locked season. Clicking on search bar also freezes the whole season. Issue requires Restarting GTK3 or restarting the season. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-59.65-generic 5.15.78 Uname: Linux 5.15.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 18 13:35:36 2023 InstallationDate: Installed on 2021-06-20 (576 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2003168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003168] Re: SIdebar, files gets unresponsive after unlocking locked season.
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2003168/+attachment/5655793/+files/journal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2003168 Title: SIdebar, files gets unresponsive after unlocking locked season. Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Expired Bug description: SIdebar, files gets unresponsive after unlocking locked season. Clicking on search bar also freezes the whole season. Issue requires Restarting GTK3 or restarting the season. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-59.65-generic 5.15.78 Uname: Linux 5.15.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 18 13:35:36 2023 InstallationDate: Installed on 2021-06-20 (576 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2003168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003168] Re: SIdebar, files gets unresponsive after unlocking locked season.
I have attached Journal.txt ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2003168/+attachment/5655792/+files/journal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2003168 Title: SIdebar, files gets unresponsive after unlocking locked season. Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Expired Bug description: SIdebar, files gets unresponsive after unlocking locked season. Clicking on search bar also freezes the whole season. Issue requires Restarting GTK3 or restarting the season. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-59.65-generic 5.15.78 Uname: Linux 5.15.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 18 13:35:36 2023 InstallationDate: Installed on 2021-06-20 (576 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2003168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007331] Re: Fix HFP mSBC support on Realtek Bluetooth USB controller
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2007331 Title: Fix HFP mSBC support on Realtek Bluetooth USB controller Status in HWE Next: New Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in pulseaudio source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in pulseaudio source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in pulseaudio source package in Lunar: Fix Released Bug description: [Impact] When a BT headset is connected Realtek BT USB controller, HFP profile can't play or record sound when mSBC codec is used. [Fix] At Linux kernel side, add a Realtek specific quirk to support mSBC. At PulseAudio side, send more data frames until the connected device sends response. [Test] Connect different headsets to the said controller, HFP can play and record sounds now. Also verified A2DP profile is unaffected. [Where problems could occur] The kernel part is Realtek specific, so the regression risk is very limited. The pulseaudio side only affects HFP profile, since the codeflow only changes when a mic is present. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2007331/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007331] Re: Fix HFP mSBC support on Realtek Bluetooth USB controller
this is missing verification of oem-6.1 kernel ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2007331 Title: Fix HFP mSBC support on Realtek Bluetooth USB controller Status in HWE Next: New Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in pulseaudio source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in pulseaudio source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in pulseaudio source package in Lunar: Fix Released Bug description: [Impact] When a BT headset is connected Realtek BT USB controller, HFP profile can't play or record sound when mSBC codec is used. [Fix] At Linux kernel side, add a Realtek specific quirk to support mSBC. At PulseAudio side, send more data frames until the connected device sends response. [Test] Connect different headsets to the said controller, HFP can play and record sounds now. Also verified A2DP profile is unaffected. [Where problems could occur] The kernel part is Realtek specific, so the regression risk is very limited. The pulseaudio side only affects HFP profile, since the codeflow only changes when a mic is present. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2007331/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2009948] Re: Problem with xorg
Thanks for the bug report. I can't see anything obviously wrong in the attached files so please explain in more detail what the problem is. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2009948 Title: Problem with xorg Status in Ubuntu: Incomplete Bug description: Is not working. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.85.05 Sat Jan 14 00:49:50 UTC 2023 GCC version: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: fail CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 10 09:08:31 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.19.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell CometLake-U GT2 [UHD Graphics] [1028:0959] Subsystem: Dell GP108M [GeForce MX230] [1028:0959] InstallationDate: Installed on 2023-03-10 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Dell Inc. Vostro 5490 ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm-256color PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=b6242c65-c3ec-45af-912f-e70f66a54868 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2022 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.name: 0M9F58 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd07/08/2022:br1.20:svnDellInc.:pnVostro5490:pvr:rvnDellInc.:rn0M9F58:rvrA04:cvnDellInc.:ct10:cvr:sku0959: dmi.product.family: Vostro dmi.product.name: Vostro 5490 dmi.product.sku: 0959 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2009948/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012118] Re: Black screen after unplugging external monitor
Thanks for the bug report. Please:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.
2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.
3. Next time the problem happens, after rebooting run:
journalctl -b-1 > prevboot.txt
and attach the resulting text file here.
** Tags added: amdgpu hybrid multigpu nvidia
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2012118
Title:
Black screen after unplugging external monitor
Status in Ubuntu:
Incomplete
Bug description:
Steps to reproduce:
1. Plugin laptop into external monitor (HDMI).
2. Leave laptop idle until it sleeps.
3. Unplug laptop from monitor.
At this point the laptop is stuck with a black screen and I cannot
regain control using any of the Ctrl + Alt + F{N} chords. I am forced
to reboot.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.85.12 Sat Jan 28
02:10:06 UTC 2023
GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04)
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 18 01:17:24 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
nvidia/525.85.12, 5.19.0-32-generic, x86_64: installed
nvidia/525.85.12, 5.19.0-35-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation GA104M [GeForce RTX 3070 Mobile / Max-Q] [10de:249d] (rev
a1) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. GA104M [GeForce RTX 3070 Mobile / Max-Q]
[1043:118c]
Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c4) (prog-if
00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Cezanne [1043:118c]
InstallationDate: Installed on 2022-08-16 (213 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus G15 GA503QR_GA503QR
ProcEnviron:
LANGUAGE=en_CA:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_CA.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic
root=UUID=cd0d16fc-2228-479b-a09a-e7a1f8e6ea1e ro quiet splash
mem_sleep_default=deep vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/03/2021
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: GA503QR.413
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GA503QR
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 3.9
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrGA503QR.413:bd11/03/2021:br5.19:efr3.9:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG15GA503QR_GA503QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA503QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: ROG Zephyrus G15
dmi.product.name: ROG Zephyrus G15 GA503QR_GA503QR
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
[Desktop-packages] [Bug 2012230] Re: /usr/bin/gnome-shell:11:meta_wayland_compositor_get_context:display_from_offer:destroy_data_offer:destroy_resource:for_each_helper
*** This bug is a duplicate of bug 2012100 *** https://bugs.launchpad.net/bugs/2012100 ** This bug has been marked a duplicate of private bug 2012100 -- 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/2012230 Title: /usr/bin/gnome- shell:11:meta_wayland_compositor_get_context:display_from_offer:destroy_data_offer:destroy_resource:for_each_helper Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44~beta-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/6ed60191b7b581604728fdae19728667e22ec160 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012230] [NEW] /usr/bin/gnome-shell:11:meta_wayland_compositor_get_context:display_from_offer:destroy_data_offer:destroy_resource:for_each_helper
*** This bug is a duplicate of bug 2012100 *** https://bugs.launchpad.net/bugs/2012100 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 44~beta-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/6ed60191b7b581604728fdae19728667e22ec160 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: lunar -- 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/2012230 Title: /usr/bin/gnome- shell:11:meta_wayland_compositor_get_context:display_from_offer:destroy_data_offer:destroy_resource:for_each_helper Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44~beta-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/6ed60191b7b581604728fdae19728667e22ec160 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
