[Desktop-packages] [Bug 1970921] Re: Drag and drop does not work
After resizing the windows "drag-n-drop file to web-browser" randomly works. But ux is a pain in a production environment. -- 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/1970921 Title: Drag and drop does not work Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Triaged Bug description: After upgrading Ubuntu to 22.04 drag and dropping files from nautilus to web browser (chromium, google chrome / apps like seafile, etc.) do not work. Also drag & drop from nautilus to slack desktop app does not work. If making several attempts, it might suddenly work with nth attempt. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 13:32:48 2022 InstallationDate: Installed on 2016-11-22 (1983 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: nautilus UpgradeStatus: Upgraded to jammy on 2022-04-29 (0 days ago) usr_lib_nautilus: evince42.1-3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1970921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1978905] Re: Reverse PRIME support for Wayland (Nvidia as primary GPU outputting to Intel GPU display ports)
** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1978905 Title: Reverse PRIME support for Wayland (Nvidia as primary GPU outputting to Intel GPU display ports) Status in Mutter: New Status in mutter package in Ubuntu: In Progress Bug description: Reverse PRIME support for Wayland (Nvidia as primary GPU outputting to Intel GPU display ports) This is different to the usual dual GPU setup where Intel is primary and Nvidia is secondary. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1978905/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1978905] Re: Reverse PRIME support for Wayland (Nvidia as primary GPU outputting to Intel GPU display ports)
Still failing in mantic and in upstream mutter. More details are in https://gitlab.gnome.org/GNOME/mutter/-/issues/2295 ** Changed in: mutter (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1978905 Title: Reverse PRIME support for Wayland (Nvidia as primary GPU outputting to Intel GPU display ports) Status in Mutter: New Status in mutter package in Ubuntu: Triaged Bug description: Reverse PRIME support for Wayland (Nvidia as primary GPU outputting to Intel GPU display ports) This is different to the usual dual GPU setup where Intel is primary and Nvidia is secondary. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1978905/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1978905] Re: Reverse PRIME support for Wayland (Nvidia as primary GPU outputting to Intel GPU display ports)
** Changed in: mutter (Ubuntu) Status: Incomplete => Triaged ** Tags added: mantic ** Changed in: mutter (Ubuntu) Importance: Wishlist => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1978905 Title: Reverse PRIME support for Wayland (Nvidia as primary GPU outputting to Intel GPU display ports) Status in Mutter: New Status in mutter package in Ubuntu: Triaged Bug description: Reverse PRIME support for Wayland (Nvidia as primary GPU outputting to Intel GPU display ports) This is different to the usual dual GPU setup where Intel is primary and Nvidia is secondary. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1978905/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990000] Re: gnome-shell crashed with SIGSEGV in getenv("STEMD_DEVICE_VERIFY_SYSFS")
** Package changed: mutter (Ubuntu) => gnome-shell (Ubuntu)
** No longer affects: udev (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/199
Title:
gnome-shell crashed with SIGSEGV in
getenv("STEMD_DEVICE_VERIFY_SYSFS")
Status in Mutter:
New
Status in gnome-shell package in Ubuntu:
Confirmed
Bug description:
sudden crashed
ProblemType: Crash
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43~rc-1ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-16.16-generic 5.19.7
Uname: Linux 5.19.0-16-generic x86_64
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME-Greeter:GNOME
Date: Sat Sep 17 01:24:15 2022
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
InstallationDate: Installed on 2020-06-25 (812 days ago)
InstallationMedia:
JournalErrors: -- No entries --
ProcCmdline: /usr/bin/gnome-shell
RelatedPackageVersions: mutter-common 43~rc-2ubuntu2
SegvAnalysis:
Segfault happened at: 0x7fb42e23f13d <__GI_getenv+173>: cmp
(%rbx),%r12w
PC (0x7fb42e23f13d) ok
source "(%rbx)" (0x556030920c76) not located in a known VMA region (needed
readable region)!
destination "%r12w" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
__GI_getenv (name=0x7fb42b5af43b "STEMD_DEVICE_VERIFY_SYSFS") at
./stdlib/getenv.c:84
?? () from /lib/x86_64-linux-gnu/libudev.so.1
?? () from /lib/x86_64-linux-gnu/libudev.so.1
?? () from /lib/x86_64-linux-gnu/libudev.so.1
?? () from /lib/x86_64-linux-gnu/libudev.so.1
Title: gnome-shell crashed with SIGSEGV in __GI_getenv()
UpgradeStatus: Upgraded to kinetic on 2022-04-25 (144 days ago)
UserGroups: N/A
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/199/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044190] Re: Lockscreen shows black background in user login section
*** This bug is a duplicate of bug 2013042 *** https://bugs.launchpad.net/bugs/2013042 I guess one of the monitors is experiencing a soft hotplug and is redetected. Then bug 2013042 occurs. ** This bug has been marked a duplicate of bug 2013042 Lock screen wallpaper vanishes (goes black) if a second monitor is plugged in/out -- 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/2044190 Title: Lockscreen shows black background in user login section Status in gnome-shell package in Ubuntu: New Bug description: Unlike my laptop, my desktop, has issues with the lockscreen background, which disappears and goes black after trying to unlock the lockscreen only after the login section (after you click or type something in the screen to put the password) Didn't happen on Ubuntu 23.04 or 22.04 LTS Happens even on a fresh 23.10 install. Wayland session. Tried MUTTER_DEBUG_KMS_THREAD_TYPE=user but did not make any effect. After some tests, it looks like it happens only when a double monitor is used. The second monitor is not affected. Changing the primary monitor for the dock didn't make any effect The monitor having the issue: Gigabyte M27Q 2560x1440 170hz, using Displayport with FreeSync enabled Second monitor, not having the issue: Zowie XL2411Z 1080p with DVI input. There are no other symptoms or useful logs somewhere. The session works fine overall. Disabling the gnome extensions didn't make any effect. Picture attached. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 21 22:22:19 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-11-19 (2 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 45.0-3ubuntu3.1 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/2044190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013042] Re: Lock screen wallpaper vanishes (goes black) if a second monitor is plugged in/out
** Tags removed: rls-ll-incoming ** Tags added: mantic -- 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/2013042 Title: Lock screen wallpaper vanishes (goes black) if a second monitor is plugged in/out Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: Lock screen's blurry wallpaper vanishes on the primary monitor if a second monitor is plugged in/out. I'm left with just the lock screen text on a black background. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2013042/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044217] [NEW] package libreoffice-common 1:6.0.7-0ubuntu0.18.04.13 failed to install/upgrade: conflicting packages - not installing libreoffice-common
Public bug reported: ... ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-common 1:6.0.7-0ubuntu0.18.04.13 ProcVersionSignature: Ubuntu 5.4.0-167.184-generic 5.4.252 Uname: Linux 5.4.0-167-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 22 13:44:28 2023 ErrorMessage: conflicting packages - not installing libreoffice-common InstallationDate: Installed on 2017-05-23 (2373 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.10 SourcePackage: libreoffice Title: package libreoffice-common 1:6.0.7-0ubuntu0.18.04.13 failed to install/upgrade: conflicting packages - not installing libreoffice-common UpgradeStatus: Upgraded to focal on 2023-11-22 (0 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2044217 Title: package libreoffice-common 1:6.0.7-0ubuntu0.18.04.13 failed to install/upgrade: conflicting packages - not installing libreoffice- common Status in libreoffice package in Ubuntu: New Bug description: ... ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-common 1:6.0.7-0ubuntu0.18.04.13 ProcVersionSignature: Ubuntu 5.4.0-167.184-generic 5.4.252 Uname: Linux 5.4.0-167-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 22 13:44:28 2023 ErrorMessage: conflicting packages - not installing libreoffice-common InstallationDate: Installed on 2017-05-23 (2373 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.10 SourcePackage: libreoffice Title: package libreoffice-common 1:6.0.7-0ubuntu0.18.04.13 failed to install/upgrade: conflicting packages - not installing libreoffice-common UpgradeStatus: Upgraded to focal on 2023-11-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2044217/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2030947] Re: gnome-shell spams journal with `g_closure_add_invalidate_notifier: assertion 'closure->n_inotifiers < CLOSURE_MAX_N_INOTIFIERS' failed` when 'Zoom' a11y feature en
** Changed in: gnome-shell Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2030947 Title: gnome-shell spams journal with `g_closure_add_invalidate_notifier: assertion 'closure->n_inotifiers < CLOSURE_MAX_N_INOTIFIERS' failed` when 'Zoom' a11y feature enabled Status in GNOME Shell: New Status in gjs package in Ubuntu: New Bug description: gnome-shell logs gnome-shell[4537]: g_closure_add_invalidate_notifier: assertion 'closure->n_inotifiers < CLOSURE_MAX_N_INOTIFIERS' failed multiple times per second for weeks now. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 44.3-1ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Thu Aug 10 10:38:23 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-11-26 (256 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) RelatedPackageVersions: mutter-common 44.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2030947/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
This bug was fixed in the package apparmor - 3.0.4-2ubuntu2.3 --- apparmor (3.0.4-2ubuntu2.3) jammy; urgency=medium * Add support for applications like evince opening browsers distributed as snaps (LP: #1794064) - d/p/u/add-snap-browsers-profile-lp1794064.patch: add a snap-browsers abstraction profile to let applications like evince spawn browsers distributed as snaps - d/p/u/update-snap-browsers-permissions-lp1794064.patch: update snap-browsers abstraction with missing permissions -- Georgia Garcia Mon, 05 Jun 2023 15:58:43 -0300 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Fix Released Status in evince package in Ubuntu: Fix Released Status in apparmor source package in Jammy: Fix Released Status in evince source package in Jammy: Fix Released Status in apparmor source package in Lunar: Fix Released Status in evince source package in Lunar: Fix Released Status in apparmor package in Debian: Fix Released Status in evince package in Debian: Confirmed Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
This bug was fixed in the package evince - 42.3-0ubuntu3.1 --- evince (42.3-0ubuntu3.1) jammy; urgency=medium * Allow evince to spawn browsers distributed as snaps (LP: #1794064) - debian/apparmor-profile: include snap-browsers abstracted profile and allow transitions to them in evince. -- Georgia Garcia Thu, 19 Oct 2023 16:01:41 -0300 ** Changed in: evince (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: apparmor (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Fix Released Status in evince package in Ubuntu: Fix Released Status in apparmor source package in Jammy: Fix Released Status in evince source package in Jammy: Fix Released Status in apparmor source package in Lunar: Fix Released Status in evince source package in Lunar: Fix Released Status in apparmor package in Debian: Fix Released Status in evince package in Debian: Confirmed Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
Ah, jbicha had already retriggered the autopkgtests, and they now pass. Huzzah! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Fix Released Status in evince package in Ubuntu: Fix Released Status in apparmor source package in Jammy: Fix Released Status in evince source package in Jammy: Fix Released Status in apparmor source package in Lunar: Fix Released Status in evince source package in Lunar: Fix Released Status in apparmor package in Debian: Fix Released Status in evince package in Debian: Confirmed Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991901] Re: JS ERROR: Failed to initialize fprintd service: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available
** Tags removed: kinetic ** Tags added: mantic -- 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/1991901 Title: JS ERROR: Failed to initialize fprintd service: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available Status in gnome-shell package in Ubuntu: Confirmed Bug description: This error is too noisy and also not an error. Many systems and most desktops won't have fingerprint devices. JS ERROR: Failed to initialize fprintd service: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1991901/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991901] Re: JS ERROR: Failed to initialize fprintd service: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available
Also noticed in Ubuntu 23.10 in every boot: nov 22 04:10:54 fpgrpi gnome-shell[2402]: JS ERROR: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23 @resource:///org/gnome/shell/ui/init.js:21:20 ... nov 22 04:10:59 fpgrpi gnome-shell[2402]: JS ERROR: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23 @resource:///org/gnome/shell/ui/init.js:21:20 nov 22 04:11:04 fpgrpi gdm-password][8229]: gkr-pam: unable to locate daemon control file nov 22 04:11:04 fpgrpi gnome-shell[2402]: JS ERROR: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Failed: Set global engine failed: Se canceló la operación _promisify/proto[asyncFunc]/ @resource:///org/gnome/shell/ui/init.js:21:20 ### Promise created here: ### _setEngine@resource:///org/gnome/shell/misc/ibusManager.js:303:30 setEngine@resource:///org/gnome/shell/misc/ibusManager.js:326:24 activateInputSource@resource:///org/gnome/shell/ui/status/keyboard.js:499:31 _callHandlers@resource:///org/gnome/gjs/modules/core/_signals.js:130:42 _emit@resource:///org/gnome/gjs/modules/core/_signals.js:119:10 activate@resource:///org/gnome/shell/ui/status/keyboard.js:68:14 _inputSourcesChanged@resource:///org/gnome/shell/ui/status/keyboard.js:633:33 reload@resource:///org/gnome/shell/ui/status/keyboard.js:373:14 _ibusSetContentType@resource:///org/gnome/shell/ui/status/keyboard.js:708:14 _callHandlers@resource:///org/gnome/gjs/modules/core/_signals.js:130:42 _emit@resource:///org/gnome/gjs/modules/core/_signals.js:119:10 _setContentType@resource:///org/gnome/shell/misc/ibusManager.js:278:14 @resource:///org/gnome/shell/ui/init.js:21:20 -- 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/1991901 Title: JS ERROR: Failed to initialize fprintd service: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available Status in gnome-shell package in Ubuntu: Confirmed Bug description: This error is too noisy and also not an error. Many systems and most desktops won't have fingerprint devices. JS ERROR: Failed to initialize fprintd service: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1991901/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993370] Re: Cannot install proprietary Broadcom WiFi drivers on Ubuntu Studio Jammy 22.04.2 and Kinetic
This bug was fixed in the package software-properties - 0.99.22.8 --- software-properties (0.99.22.8) jammy; urgency=medium * softwareproperties/qt/SoftwarePropertiesQt.py: Don't crash if the driver package does not have a matching modules package (LP: #1993370) -- Brian Murray Thu, 10 Aug 2023 15:08:33 -0700 ** Changed in: software-properties (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1993370 Title: Cannot install proprietary Broadcom WiFi drivers on Ubuntu Studio Jammy 22.04.2 and Kinetic Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Jammy: Fix Released Status in software-properties source package in Kinetic: Won't Fix Bug description: [Impact] software-properties-qt will crash when a user tries to install drivers for Broadcom wireless devices. This same change has been made in the software-properties-gtk frontend (see bug 1969460) without any issues. There are also problems in the Error Tracker for this crash: https://errors.ubuntu.com/problem/1c41600298c08b5dfc2d86ee90ad27ef56cd4524 https://errors.ubuntu.com/problem/49f4156af6d9d2367fc480105e19064da3575269 [Test Plan] 1) Install Ubuntu Studio 22.04.3 on a system with Broadcom WiFi 2) Reboot into the installed sytem 3) Open a terminal and run 'sudo software-properties-kde' 4) Click the 'Additional Drivers' tab 5) Click "Using Broadcom 802.11 Linux STA wireless driver source from bcmwl-kernel-source (proprietary)". With the version of the package in -updates you'll observe the following Traceback in the terminal: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", line 1061, in on_driver_selection_changed modules_package_obj = self.apt_cache[modules_package] TypeError: Expected a string or a pair of strings With the version of the package in -proposed you will not. [ Where problems could occur ] It's possible we'll hide a real error as we are catching all TypeErrors, but given we haven't heard of any issues with other stable releases and that this was fixed in software-properties-gtk in the same way I think it is safe. Hardware: HP Elitebook 8570p, 16 GB RAM, 120 GB SSD, 3rd Gen Intel Core i5, UEFI, no secure boot, Broadcom WiFi. OS: Ubuntu Studio Kinetic, Final ISO Steps to reproduce: 1. Boot the Ubuntu Studio ISO on a system with Broadcom WiFi, and install the system normally. (No encryption, allow Internet access during installation using some method of connectivity other than WiFi.) 2. Reboot and log into the newly installed system. 3. Open a terminal and run "sudo software-properties-kde". 4. Click "Additional Drivers" in the window that pops up. 5. Click "Using Broadcom 802.11 Linux STA wireless driver source from bcmwl-kernel-source (proprietary)". Expected result: The Apply Changes button should become clickable, allowing the user to install the driver. Actual result: The button remains grayed out, and the following error message is printed in the terminal: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", line 1063, in on_driver_selection_changed modules_package_obj = self.apt_cache[modules_package] TypeError: Expected a string or a pair of strings ProblemType: BugDistroRelease: Ubuntu 22.10 Package: software-properties-qt 0.99.27 ProcVersionSignature: Ubuntu 5.19.0-1007.7-lowlatency 5.19.7 Uname: Linux 5.19.0-1007-lowlatency x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Oct 18 21:33:51 2022 InstallationDate: Installed on 2022-10-19 (0 days ago) InstallationMedia: Ubuntu-Studio 22.10 "Kinetic Kudu" - Release amd64 (20221017.1) PackageArchitecture: allSourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1993370/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
Retriggered the autopkgtest to use the correct apparmor version; let's see if that fixes things. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Fix Released Status in evince package in Ubuntu: Fix Released Status in apparmor source package in Jammy: Fix Committed Status in evince source package in Jammy: Fix Committed Status in apparmor source package in Lunar: Fix Released Status in evince source package in Lunar: Fix Released Status in apparmor package in Debian: Fix Released Status in evince package in Debian: Confirmed Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
Yes the solution in comment 10 is indirectly mentioned above in [Workarounds], but it's not very obvious: https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend Status in GNOME Shell: New Status in Mutter: Fix Released Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-460 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-470 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-525 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-535 package in Ubuntu: Triaged Bug description: [Impact] The Nvidia driver corrupts and/or forgets its textures when resuming from suspend, by design. Documented here: https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt Although it's so awkward to implement everywhere that realistically compositors will never support it fully. Instead we're waiting for an Nvidia driver fix. *NOTE* that this is actually not a common problem because the system must be using Nvidia as the primary GPU to be affected. So generally only desktop users will encounter the bug, not laptops. And even then, only desktops that use suspend/resume and VT switching may trigger it, if ever. Even in development the bug cannot be reproduced reliably. [Workarounds] * Always log into a Xorg session and if corruption occurs then type: Alt+F2, R, Enter * https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0 [Test Plan] [Where problems could occur] [Original Bug Report] I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370
[Desktop-packages] [Bug 2044191] Re: the sound of my pc crashes when i install a background changer
** Changed in: pulseaudio (Ubuntu) Status: New => Invalid -- 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/2044191 Title: the sound of my pc crashes when i install a background changer Status in pulseaudio package in Ubuntu: Invalid Bug description: every thing is ok and the no problem about the package pulseaudio is occured just the problem is in my hardware of my device and not from the system (software) "left side in my speaker is not working on my hardware" sorry about that you can delete this report To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2044191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044191] Re: the sound of my pc crashes when i install a background changer
** Description changed: - Question and Report about the thing that happens: - - this is what i found on syslog : - - Nov 21 23:33:17 oem-Satellite-A505 dbus-daemon[906]: [session uid=1000 pid=906] Successfully activated service 'org.freedesktop.FileManager1' - Nov 21 23:33:18 oem-Satellite-A505 pulseaudio[859]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. - Nov 21 23:33:19 oem-Satellite-A505 systemd[1]: systemd-timedated.service: Succeeded. - Nov 21 23:33:19 oem-Satellite-A505 colord[1400]: failed to get session [pid 1246]: No data available - Nov 21 23:33:20 oem-Satellite-A505 gnome-shell[1155]: Could not load a pixbuf from icon theme.#012This may indicate that pixbuf loaders or the mime database could not be found. - Nov 21 23:33:21 oem-Satellite-A505 ubuntu-report[863]: level=error msg="data were not delivered successfully to metrics server, retrying in 60s" - Nov 21 23:33:22 oem-Satellite-A505 gnome-shell[1155]: [xcb] Unknown sequence number while processing queue - Nov 21 23:33:22 oem-Satellite-A505 gnome-shell[1155]: [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called - Nov 21 23:33:22 oem-Satellite-A505 gnome-shell[1155]: [xcb] Aborting, sorry about that. - Nov 21 23:33:22 oem-Satellite-A505 gnome-shell[1155]: gnome-shell: ../../src/xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. - Nov 21 23:33:22 oem-Satellite-A505 gnome-shell[1155]: GNOME Shell crashed with signal 6 - Nov 21 23:33:22 oem-Satellite-A505 gnome-shell[1155]: == Stack trace for context 0x557abcbdf540 == - Nov 21 23:33:25 oem-Satellite-A505 systemd[838]: Starting Notification regarding a crash report... - Nov 21 23:33:25 oem-Satellite-A505 update-notifier-crash[1467]: /usr/bin/whoopsie - Nov 21 23:33:26 oem-Satellite-A505 systemd[838]: update-notifier-crash.service: Succeeded. - Nov 21 23:33:26 oem-Satellite-A505 systemd[838]: Finished Notification regarding a crash report. - Nov 21 23:33:32 oem-Satellite-A505 tracker-store[1076]: OK - Nov 21 23:33:32 oem-Satellite-A505 systemd[838]: tracker-store.service: Succeeded. - Nov 21 23:33:36 oem-Satellite-A505 systemd[838]: Starting Notification regarding a crash report... - Nov 21 23:33:36 oem-Satellite-A505 update-notifier-crash[1472]: /usr/bin/whoopsie - Nov 21 23:33:36 oem-Satellite-A505 ibus-daemon[1179]: GChildWatchSource: Exit status of a child process was requested but ECHILD was received by waitpid(). See the documentation of g_child_watch_source_new() for possible causes. - Nov 21 23:33:36 oem-Satellite-A505 systemd[838]: gnome-shell-x11.service: Main process exited, code=dumped, status=6/ABRT - Nov 21 23:33:36 oem-Satellite-A505 systemd[838]: gnome-shell-x11.service: Failed with result 'core-dump'. - - When i install a script from https://www.omgubuntu.co.uk/2022/01/change-ubuntu-login-screen-background the - wget https://github.com/PRATAP-KUMAR/ubuntu-gdm-set-background/archive/main.tar.gz it facilitates the sound from the build in device .. - resulting in nolonger the hearing of any sound including sys sound (system) - - fix this for me to hear the sounds of my microcomputer - - ProblemType: Bug - DistroRelease: Ubuntu 20.04 - Package: pulseaudio 1:13.99.1-1ubuntu3.13 - ProcVersionSignature: Ubuntu 5.15.0-88.98~20.04.1-generic 5.15.126 - Uname: Linux 5.15.0-88-generic x86_64 - ApportVersion: 2.20.11-0ubuntu27.27 - Architecture: amd64 - AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: oem 859 F pulseaudio - CasperMD5CheckResult: skip - Date: Tue Nov 21 23:41:24 2023 - InstallationDate: Installed on 2023-11-20 (1 days ago) - InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) - ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash - PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. - SourcePackage: pulseaudio - Symptom: audio - UpgradeStatus: No upgrade log present (probably fresh install) - dmi.bios.date: 09/03/2009 - dmi.bios.vendor: INSYDE - dmi.bios.version: 1.60 - dmi.board.asset.tag: Base Board Asset Tag - dmi.board.name: Portable PC - dmi.board.vendor: TOSHIBA - dmi.board.version: Base Board Version - dmi.chassis.asset.tag: No Asset Tag - dmi.chassis.type: 10 - dmi.chassis.vendor: Chassis Manufacturer - dmi.chassis.version: Chassis Version - dmi.modalias: dmi:bvnINSYDE:bvr1.60:bd09/03/2009:svnTOSHIBA:pnSatelliteA505:pvrPSAT0U-00M001B:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:skuMontevina_Fab: - dmi.product.family: Intel_Mobile - dmi.product.name: Satellite A505 -
[Desktop-packages] [Bug 2044191] [NEW] the sound of my pc crashes when i install a background changer
Public bug reported: dd ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: Question and Report about the thing that happens: this is what i found on syslog : Nov 21 23:33:17 oem-Satellite-A505 dbus-daemon[906]: [session uid=1000 pid=906] Successfully activated service 'org.freedesktop.FileManager1' Nov 21 23:33:18 oem-Satellite-A505 pulseaudio[859]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Nov 21 23:33:19 oem-Satellite-A505 systemd[1]: systemd-timedated.service: Succeeded. Nov 21 23:33:19 oem-Satellite-A505 colord[1400]: failed to get session [pid 1246]: No data available Nov 21 23:33:20 oem-Satellite-A505 gnome-shell[1155]: Could not load a pixbuf from icon theme.#012This may indicate that pixbuf loaders or the mime database could not be found. Nov 21 23:33:21 oem-Satellite-A505 ubuntu-report[863]: level=error msg="data were not delivered successfully to metrics server, retrying in 60s" Nov 21 23:33:22 oem-Satellite-A505 gnome-shell[1155]: [xcb] Unknown sequence number while processing queue Nov 21 23:33:22 oem-Satellite-A505 gnome-shell[1155]: [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called Nov 21 23:33:22 oem-Satellite-A505 gnome-shell[1155]: [xcb] Aborting, sorry about that. Nov 21 23:33:22 oem-Satellite-A505 gnome-shell[1155]: gnome-shell: ../../src/xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. Nov 21 23:33:22 oem-Satellite-A505 gnome-shell[1155]: GNOME Shell crashed with signal 6 Nov 21 23:33:22 oem-Satellite-A505 gnome-shell[1155]: == Stack trace for context 0x557abcbdf540 == Nov 21 23:33:25 oem-Satellite-A505 systemd[838]: Starting Notification regarding a crash report... Nov 21 23:33:25 oem-Satellite-A505 update-notifier-crash[1467]: /usr/bin/whoopsie Nov 21 23:33:26 oem-Satellite-A505 systemd[838]: update-notifier-crash.service: Succeeded. Nov 21 23:33:26 oem-Satellite-A505 systemd[838]: Finished Notification regarding a crash report. Nov 21 23:33:32 oem-Satellite-A505 tracker-store[1076]: OK Nov 21 23:33:32 oem-Satellite-A505 systemd[838]: tracker-store.service: Succeeded. Nov 21 23:33:36 oem-Satellite-A505 systemd[838]: Starting Notification regarding a crash report... Nov 21 23:33:36 oem-Satellite-A505 update-notifier-crash[1472]: /usr/bin/whoopsie Nov 21 23:33:36 oem-Satellite-A505 ibus-daemon[1179]: GChildWatchSource: Exit status of a child process was requested but ECHILD was received by waitpid(). See the documentation of g_child_watch_source_new() for possible causes. Nov 21 23:33:36 oem-Satellite-A505 systemd[838]: gnome-shell-x11.service: Main process exited, code=dumped, status=6/ABRT Nov 21 23:33:36 oem-Satellite-A505 systemd[838]: gnome-shell-x11.service: Failed with result 'core-dump'. - When i install a script from https://www.omgubuntu.co.uk/2022/01/change-ubuntu-login-screen-background the + When i install a script from https://www.omgubuntu.co.uk/2022/01/change-ubuntu-login-screen-background the wget https://github.com/PRATAP-KUMAR/ubuntu-gdm-set-background/archive/main.tar.gz it facilitates the sound from the build in device .. - resulting in nolonger the hearing of any sound including sys sound (system) + resulting in nolonger the hearing of any sound including sys sound (system) fix this for me to hear the sounds of my microcomputer ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.15.0-88.98~20.04.1-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: oem 859 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: oem 859 F pulseaudio CasperMD5CheckResult: skip Date: Tue Nov 21 23:41:24 2023 InstallationDate: Installed on 2023-11-20 (1 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2009 dmi.bios.vendor: INSYDE dmi.bios.version: 1.60 dmi.board.asset.tag: Base Board Asset Tag dmi
[Desktop-packages] [Bug 2042973] Re: Desktop becomes unusable after changing window from fullscreen games on Wayland Only
Hello, the extensions were already disabled, anyway I can't reproduce the symptoms anymore on a fresh installed system with the same extensions configuration. Will update if the issue comes back somehow. -- 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/2042973 Title: Desktop becomes unusable after changing window from fullscreen games on Wayland Only Status in gnome-shell package in Ubuntu: Incomplete Bug description: Description: Ubuntu 23.10 Release: 23.10 gnome-shell 45.0-1ubuntu2 Steps to reproduce: 1)Open certain games (Like An Anime Game Launcher, or Shadow Warrior 2 from steam, both using DXVK) 2)Wait for them to fully load 3)Press the Super button in order to go back to the desktop What should happen: A list of windows, the gnome desktop overview, is shown What happened: All the screen section from above the gnome taskbar became grey like the activity overview accent color and nothing else can be done, the desktop functionality is broken - Since I upgraded from 23.04 to 23.10 the desktop becomes unusable (video attached) 80% of the times when I switch from certain fullscreen games to the desktop using the super button. The gray color of the activity overview is shown above the shell taskbar on both screens and nothing else can be done. - The issue does not happen on an X11 session. - The notifications still work correctly, as clicking the gnome shell bar or even locking and unlocking the screen. - Right clicking and closing apps work. However, only the buttons from the shell itself only - Everything involving actively changing windows does not. - No matter the screen configuration the issue still persist. Tried to upgrade mesa drivers, switching from 2 screens to 1, no luck. No workaround is discovered. Session can be terminated from the taskbar, as it works correctly. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 7 19:47:42 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-12 (87 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-10-13 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2042973/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044190] [NEW] Lockscreen shows black background in user login section
Public bug reported: Unlike my laptop, my desktop, has issues with the lockscreen background, which disappears and goes black after trying to unlock the lockscreen only after the login section (after you click or type something in the screen to put the password) Didn't happen on Ubuntu 23.04 or 22.04 LTS Happens even on a fresh 23.10 install. Wayland session. Tried MUTTER_DEBUG_KMS_THREAD_TYPE=user but did not make any effect. After some tests, it looks like it happens only when a double monitor is used. The second monitor is not affected. Changing the primary monitor for the dock didn't make any effect The monitor having the issue: Gigabyte M27Q 2560x1440 170hz, using Displayport with FreeSync enabled Second monitor, not having the issue: Zowie XL2411Z 1080p with DVI input. There are no other symptoms or useful logs somewhere. The session works fine overall. Disabling the gnome extensions didn't make any effect. Picture attached. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 21 22:22:19 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-11-19 (2 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 45.0-3ubuntu3.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session ** Attachment added: "Schermata del 2023-11-21 22-31-05.png" https://bugs.launchpad.net/bugs/2044190/+attachment/5721953/+files/Schermata%20del%202023-11-21%2022-31-05.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/2044190 Title: Lockscreen shows black background in user login section Status in gnome-shell package in Ubuntu: New Bug description: Unlike my laptop, my desktop, has issues with the lockscreen background, which disappears and goes black after trying to unlock the lockscreen only after the login section (after you click or type something in the screen to put the password) Didn't happen on Ubuntu 23.04 or 22.04 LTS Happens even on a fresh 23.10 install. Wayland session. Tried MUTTER_DEBUG_KMS_THREAD_TYPE=user but did not make any effect. After some tests, it looks like it happens only when a double monitor is used. The second monitor is not affected. Changing the primary monitor for the dock didn't make any effect The monitor having the issue: Gigabyte M27Q 2560x1440 170hz, using Displayport with FreeSync enabled Second monitor, not having the issue: Zowie XL2411Z 1080p with DVI input. There are no other symptoms or useful logs somewhere. The session works fine overall. Disabling the gnome extensions didn't make any effect. Picture attached. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 21 22:22:19 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-11-19 (2 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 45.0-3ubuntu3.1 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/2044190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044014] Re: networkmanager crashes on configuring wireguard connection via nm-connection-editor
Hi, I can't find anything wrong in your configuration. And that makes me wonder if you have another YAML with the same wg0 interface in it. We recently fixed a bug in Network Manager that was leading to duplication in the configuration. You might have been affected by this bug when you upgraded to Mantic. If you grep /etc/netplan by the interface name, do you see more than one file? Something like this "sudo grep wg0 /etc/netplan/*". If you find the same interface in more than one file, try to remove them and create the connection again using the GUI. The problem might be that you have multiple YAMLs with the same interface. Netplan will merge them in a single configuration and the result might be a broken config. Let me know if it helps. Thanks! -- 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/2044014 Title: networkmanager crashes on configuring wireguard connection via nm- connection-editor Status in network-manager package in Ubuntu: Triaged Bug description: when configuring a new wireguard connection both via nm-connection-editor and the settings app, NetworkManager crashes and restarts, with the error message "Message recipient disconnected from message bus without replying". Currently, I'm unable to add wireguard connections at all. Also, I have netplan.io/now 0.107-5ubuntu1~ppa3 installed to outrule https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2039821 Ubuntu 23.10 network-manager/mantic-updates,now 1.44.2-1ubuntu1.2 amd64 netplan.io/now 0.107-5ubuntu1~ppa3 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1.2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Nov 20 20:10:40 2023 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-15 (2015 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via dev enp0s31f6 proto dhcp src metric 100 /24 dev enp0s31f6 proto kernel scope link src metric 100 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=false ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: network-manager UpgradeStatus: Upgraded to mantic on 2023-11-05 (15 days ago) http_proxy: http://:3128 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled enabled disabled missing disabled no_proxy: 127.0.0.1,172.16.0.0/12,10.0.0.0/8,192.168.0.0/16, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
The autopkgtests for apparmor failed for the evince update because the test requires the apparmor update which is also in proposed https://launchpad.net/ubuntu/+source/apparmor/3.0.4-2ubuntu2.3 but it is not a regression. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Fix Released Status in evince package in Ubuntu: Fix Released Status in apparmor source package in Jammy: Fix Committed Status in evince source package in Jammy: Fix Committed Status in apparmor source package in Lunar: Fix Released Status in evince source package in Lunar: Fix Released Status in apparmor package in Debian: Fix Released Status in evince package in Debian: Confirmed Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2027904] Re: LibreOffice Snap extremely slow to launch.
I suspect related to the startup speed, actual movement around in the apps is much slower in the snap than in the Flatpak or deb (ex. movement between cells or scrolling a sheet in Calc visibly lags behind the keystrokes or mouse movement). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2027904 Title: LibreOffice Snap extremely slow to launch. Status in libreoffice package in Ubuntu: Confirmed Bug description: It takes around 3 to 4 seconds to launch even post start-up launching. Other snaps are snappy ! No logs indicate any errors or warnings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2027904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971168] Re: [snap] Files on local network shares are not opened / written
The patch has been merged, and also has been backported to GNOME 45, so it is possible that it can make it to Mantic. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1971168 Title: [snap] Files on local network shares are not opened / written Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Status in xdg-desktop-portal package in Ubuntu: Triaged Status in xdg-desktop-portal-gnome package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome source package in Jammy: Triaged Status in xdg-desktop-portal-gnome source package in Lunar: Triaged Bug description: [ Impact ] When the user is running a containerized application (like the snapped Firefox or Chromium), and tries to save a document, the xdg-desktop- portal-gnome backend does show remote drives (like SMB or SFTP ones), and allows to choose them, but then the save operation fails. The previous backend, xdg-desktop-portal-gtk, did work fine in these cases, because it returned the local path that corresponded to the local file exported by Gvfs using FUSE, so this behaviour is not only a serious bug, but also a regression. [ Test plan] Steps to reproduce: 1. Run Firefox or Chromium as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable 4. Open any website containing images in Firefox / Chromium 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown [ Where problems could occur ] - If the remote drives aren't exported as local files by Gvfs using FUSE, the patch won't work and the behaviour will be the same than now. - Any hidden bug in g_file_get_path() when managing remote drives could be triggered by this patch. [ Additional information ] * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share * Similar situation when trying to open a file with Ctrl + O on a network share from Firefox / Chromium. After double-clicking e.g. an image file in the file dialog, the file dialog closes but nothing happens otherwise. Opening an image on a local folder works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044014] Re: networkmanager crashes on configuring wireguard connection via nm-connection-editor
actually, it doesn't matter if any dns setting is set or left empty => the message stays the same. -- 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/2044014 Title: networkmanager crashes on configuring wireguard connection via nm- connection-editor Status in network-manager package in Ubuntu: Triaged Bug description: when configuring a new wireguard connection both via nm-connection-editor and the settings app, NetworkManager crashes and restarts, with the error message "Message recipient disconnected from message bus without replying". Currently, I'm unable to add wireguard connections at all. Also, I have netplan.io/now 0.107-5ubuntu1~ppa3 installed to outrule https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2039821 Ubuntu 23.10 network-manager/mantic-updates,now 1.44.2-1ubuntu1.2 amd64 netplan.io/now 0.107-5ubuntu1~ppa3 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1.2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Nov 20 20:10:40 2023 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-15 (2015 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via dev enp0s31f6 proto dhcp src metric 100 /24 dev enp0s31f6 proto kernel scope link src metric 100 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=false ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: network-manager UpgradeStatus: Upgraded to mantic on 2023-11-05 (15 days ago) http_proxy: http://:3128 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled enabled disabled missing disabled no_proxy: 127.0.0.1,172.16.0.0/12,10.0.0.0/8,192.168.0.0/16, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044014] Re: networkmanager crashes on configuring wireguard connection via nm-connection-editor
** Attachment added: "unitlog.log.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+attachment/5721831/+files/unitlog.log.txt -- 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/2044014 Title: networkmanager crashes on configuring wireguard connection via nm- connection-editor Status in network-manager package in Ubuntu: Triaged Bug description: when configuring a new wireguard connection both via nm-connection-editor and the settings app, NetworkManager crashes and restarts, with the error message "Message recipient disconnected from message bus without replying". Currently, I'm unable to add wireguard connections at all. Also, I have netplan.io/now 0.107-5ubuntu1~ppa3 installed to outrule https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2039821 Ubuntu 23.10 network-manager/mantic-updates,now 1.44.2-1ubuntu1.2 amd64 netplan.io/now 0.107-5ubuntu1~ppa3 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1.2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Nov 20 20:10:40 2023 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-15 (2015 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via dev enp0s31f6 proto dhcp src metric 100 /24 dev enp0s31f6 proto kernel scope link src metric 100 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=false ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: network-manager UpgradeStatus: Upgraded to mantic on 2023-11-05 (15 days ago) http_proxy: http://:3128 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled enabled disabled missing disabled no_proxy: 127.0.0.1,172.16.0.0/12,10.0.0.0/8,192.168.0.0/16, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044014] Re: networkmanager crashes on configuring wireguard connection via nm-connection-editor
** Attachment added: "Bildschirmfoto vom 2023-11-21 19-48-26.png" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+attachment/5721830/+files/Bildschirmfoto%20vom%202023-11-21%2019-48-26.png -- 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/2044014 Title: networkmanager crashes on configuring wireguard connection via nm- connection-editor Status in network-manager package in Ubuntu: Triaged Bug description: when configuring a new wireguard connection both via nm-connection-editor and the settings app, NetworkManager crashes and restarts, with the error message "Message recipient disconnected from message bus without replying". Currently, I'm unable to add wireguard connections at all. Also, I have netplan.io/now 0.107-5ubuntu1~ppa3 installed to outrule https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2039821 Ubuntu 23.10 network-manager/mantic-updates,now 1.44.2-1ubuntu1.2 amd64 netplan.io/now 0.107-5ubuntu1~ppa3 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1.2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Nov 20 20:10:40 2023 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-15 (2015 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via dev enp0s31f6 proto dhcp src metric 100 /24 dev enp0s31f6 proto kernel scope link src metric 100 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=false ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: network-manager UpgradeStatus: Upgraded to mantic on 2023-11-05 (15 days ago) http_proxy: http://:3128 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled enabled disabled missing disabled no_proxy: 127.0.0.1,172.16.0.0/12,10.0.0.0/8,192.168.0.0/16, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044014] Re: networkmanager crashes on configuring wireguard connection via nm-connection-editor
** Attachment added: "Bildschirmfoto vom 2023-11-21 19-45-58.png" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+attachment/5721829/+files/Bildschirmfoto%20vom%202023-11-21%2019-45-58.png -- 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/2044014 Title: networkmanager crashes on configuring wireguard connection via nm- connection-editor Status in network-manager package in Ubuntu: Triaged Bug description: when configuring a new wireguard connection both via nm-connection-editor and the settings app, NetworkManager crashes and restarts, with the error message "Message recipient disconnected from message bus without replying". Currently, I'm unable to add wireguard connections at all. Also, I have netplan.io/now 0.107-5ubuntu1~ppa3 installed to outrule https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2039821 Ubuntu 23.10 network-manager/mantic-updates,now 1.44.2-1ubuntu1.2 amd64 netplan.io/now 0.107-5ubuntu1~ppa3 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1.2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Nov 20 20:10:40 2023 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-15 (2015 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via dev enp0s31f6 proto dhcp src metric 100 /24 dev enp0s31f6 proto kernel scope link src metric 100 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=false ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: network-manager UpgradeStatus: Upgraded to mantic on 2023-11-05 (15 days ago) http_proxy: http://:3128 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled enabled disabled missing disabled no_proxy: 127.0.0.1,172.16.0.0/12,10.0.0.0/8,192.168.0.0/16, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044014] Re: networkmanager crashes on configuring wireguard connection via nm-connection-editor
** Attachment added: "Bildschirmfoto vom 2023-11-21 19-46-12.png" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+attachment/5721828/+files/Bildschirmfoto%20vom%202023-11-21%2019-46-12.png -- 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/2044014 Title: networkmanager crashes on configuring wireguard connection via nm- connection-editor Status in network-manager package in Ubuntu: Triaged Bug description: when configuring a new wireguard connection both via nm-connection-editor and the settings app, NetworkManager crashes and restarts, with the error message "Message recipient disconnected from message bus without replying". Currently, I'm unable to add wireguard connections at all. Also, I have netplan.io/now 0.107-5ubuntu1~ppa3 installed to outrule https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2039821 Ubuntu 23.10 network-manager/mantic-updates,now 1.44.2-1ubuntu1.2 amd64 netplan.io/now 0.107-5ubuntu1~ppa3 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1.2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Nov 20 20:10:40 2023 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-15 (2015 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via dev enp0s31f6 proto dhcp src metric 100 /24 dev enp0s31f6 proto kernel scope link src metric 100 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=false ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: network-manager UpgradeStatus: Upgraded to mantic on 2023-11-05 (15 days ago) http_proxy: http://:3128 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled enabled disabled missing disabled no_proxy: 127.0.0.1,172.16.0.0/12,10.0.0.0/8,192.168.0.0/16, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044014] Re: networkmanager crashes on configuring wireguard connection via nm-connection-editor
Hello Danilo, yes I am aware of that; actually I can't tell from where this is set as actually I did not set any dns configuration. Please see attached log and screenshots. Yes, a netplan file has been created. I just retracted all the sensible information. Quotes and double quotes were set correctly, have just been "overwritten" by my retraction. If you need any further logs just give me a hint how I can create them. Thanks a lot! ** Attachment added: "Bildschirmfoto vom 2023-11-21 19-46-03.png" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+attachment/5721826/+files/Bildschirmfoto%20vom%202023-11-21%2019-46-03.png -- 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/2044014 Title: networkmanager crashes on configuring wireguard connection via nm- connection-editor Status in network-manager package in Ubuntu: Triaged Bug description: when configuring a new wireguard connection both via nm-connection-editor and the settings app, NetworkManager crashes and restarts, with the error message "Message recipient disconnected from message bus without replying". Currently, I'm unable to add wireguard connections at all. Also, I have netplan.io/now 0.107-5ubuntu1~ppa3 installed to outrule https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2039821 Ubuntu 23.10 network-manager/mantic-updates,now 1.44.2-1ubuntu1.2 amd64 netplan.io/now 0.107-5ubuntu1~ppa3 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1.2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Nov 20 20:10:40 2023 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-15 (2015 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via dev enp0s31f6 proto dhcp src metric 100 /24 dev enp0s31f6 proto kernel scope link src metric 100 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=false ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: network-manager UpgradeStatus: Upgraded to mantic on 2023-11-05 (15 days ago) http_proxy: http://:3128 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled enabled disabled missing disabled no_proxy: 127.0.0.1,172.16.0.0/12,10.0.0.0/8,192.168.0.0/16, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044014] Re: networkmanager crashes on configuring wireguard connection via nm-connection-editor
** Attachment added: "Bildschirmfoto vom 2023-11-21 19-46-08.png" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+attachment/5721827/+files/Bildschirmfoto%20vom%202023-11-21%2019-46-08.png -- 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/2044014 Title: networkmanager crashes on configuring wireguard connection via nm- connection-editor Status in network-manager package in Ubuntu: Triaged Bug description: when configuring a new wireguard connection both via nm-connection-editor and the settings app, NetworkManager crashes and restarts, with the error message "Message recipient disconnected from message bus without replying". Currently, I'm unable to add wireguard connections at all. Also, I have netplan.io/now 0.107-5ubuntu1~ppa3 installed to outrule https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2039821 Ubuntu 23.10 network-manager/mantic-updates,now 1.44.2-1ubuntu1.2 amd64 netplan.io/now 0.107-5ubuntu1~ppa3 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1.2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Nov 20 20:10:40 2023 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-15 (2015 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via dev enp0s31f6 proto dhcp src metric 100 /24 dev enp0s31f6 proto kernel scope link src metric 100 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=false ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: network-manager UpgradeStatus: Upgraded to mantic on 2023-11-05 (15 days ago) http_proxy: http://:3128 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled enabled disabled missing disabled no_proxy: 127.0.0.1,172.16.0.0/12,10.0.0.0/8,192.168.0.0/16, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044014] Re: networkmanager crashes on configuring wireguard connection via nm-connection-editor
Hi Sebastian, thanks for your bug report. I can see the following error in your syslog.log: [1700508393.5530] BUG: the profile cannot be stored in keyfile format without becoming unusable: invalid connection: ipv4.dns: This property is not allowed for "method=disabled" What steps did you follow to setup the connection? I want to understand how you managed to set the ipv4.dns property with ipv4.method set to disabled using the GUI interface. May I ask you to watch the Network Manager's journal while you reproduce the crash and add the relevant part of the logs here? journalctl -u NetworkManager.service -f Also, you will probably find a YAML in /etc/netplan that was created for the problematic connection. Can you find it, remove all the keys and IPs from it, and paste it here? I'm running netplan.io 0.107-5ubuntu0.1 and I can create Wireguard connections just fine. But maybe you are using some settings that's triggering another bug that we are not aware of. Thank you. ** Changed in: network-manager (Ubuntu) Status: New => Triaged ** Changed in: network-manager (Ubuntu) Importance: Undecided => Medium -- 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/2044014 Title: networkmanager crashes on configuring wireguard connection via nm- connection-editor Status in network-manager package in Ubuntu: Triaged Bug description: when configuring a new wireguard connection both via nm-connection-editor and the settings app, NetworkManager crashes and restarts, with the error message "Message recipient disconnected from message bus without replying". Currently, I'm unable to add wireguard connections at all. Also, I have netplan.io/now 0.107-5ubuntu1~ppa3 installed to outrule https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2039821 Ubuntu 23.10 network-manager/mantic-updates,now 1.44.2-1ubuntu1.2 amd64 netplan.io/now 0.107-5ubuntu1~ppa3 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1.2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Nov 20 20:10:40 2023 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-15 (2015 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via dev enp0s31f6 proto dhcp src metric 100 /24 dev enp0s31f6 proto kernel scope link src metric 100 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=false ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: network-manager UpgradeStatus: Upgraded to mantic on 2023-11-05 (15 days ago) http_proxy: http://:3128 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled enabled disabled missing disabled no_proxy: 127.0.0.1,172.16.0.0/12,10.0.0.0/8,192.168.0.0/16, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044170] [NEW] File copy progress bar on nautilus dock icon does not show
Public bug reported: Ubuntu-desktop 24.04 development branch @ 21/11/2023 with kernel 6.5.0-10-generic When copying files with nautilus, a circle indicator shows progress in left upper corner in nautilus But the nautilus dock icon does not show the progress bar any longer like on Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:45~rc-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Nov 21 18:48:10 2023 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small-plus'" b'org.gnome.nautilus.preferences' b'click-policy' b"'single'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1523, 836)' InstallationDate: Installed on 2023-11-09 (12 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=nl_NL.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: Upgraded to noble on 2023-11-09 (12 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble third-party-packages wayland-session -- 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/2044170 Title: File copy progress bar on nautilus dock icon does not show Status in nautilus package in Ubuntu: New Bug description: Ubuntu-desktop 24.04 development branch @ 21/11/2023 with kernel 6.5.0-10-generic When copying files with nautilus, a circle indicator shows progress in left upper corner in nautilus But the nautilus dock icon does not show the progress bar any longer like on Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:45~rc-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Nov 21 18:48:10 2023 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small-plus'" b'org.gnome.nautilus.preferences' b'click-policy' b"'single'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1523, 836)' InstallationDate: Installed on 2023-11-09 (12 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=nl_NL.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: Upgraded to noble on 2023-11-09 (12 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2044170/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
Daniel, I tried setting that threshold to zero but it made the desktop apps unstable after coming back from resume (Nvidia 3080Ti). Maybe it doesn't work on desktop GPUs. So I went back to the solution I wrote about in comment 10. Maybe that solution should be used to solve this problem? It looks like it is already used in e.g. Tumbleweed. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend Status in GNOME Shell: New Status in Mutter: Fix Released Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-460 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-470 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-525 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-535 package in Ubuntu: Triaged Bug description: [Impact] The Nvidia driver corrupts and/or forgets its textures when resuming from suspend, by design. Documented here: https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt Although it's so awkward to implement everywhere that realistically compositors will never support it fully. Instead we're waiting for an Nvidia driver fix. *NOTE* that this is actually not a common problem because the system must be using Nvidia as the primary GPU to be affected. So generally only desktop users will encounter the bug, not laptops. And even then, only desktops that use suspend/resume and VT switching may trigger it, if ever. Even in development the bug cannot be reproduced reliably. [Workarounds] * Always log into a Xorg session and if corruption occurs then type: Alt+F2, R, Enter * https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0 [Test Plan] [Where problems could occur] [Original Bug Report] I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTec
[Desktop-packages] [Bug 2044157] [NEW] Firefox 120.0+build2-0ubuntu0.18.04.1~mt1 - Unity Global Menu Missing
Public bug reported: Upon upgrade from Firefox 119 to 120 noticed that the Unity Global Menu no longer works. Rolling back the package to 119 and installing FireFox ESR global menu works as expected. This is the package that is on the mozillateam PPA. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2044157 Title: Firefox 120.0+build2-0ubuntu0.18.04.1~mt1 - Unity Global Menu Missing Status in firefox package in Ubuntu: New Bug description: Upon upgrade from Firefox 119 to 120 noticed that the Unity Global Menu no longer works. Rolling back the package to 119 and installing FireFox ESR global menu works as expected. This is the package that is on the mozillateam PPA. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2044157/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044156] [NEW] Firefox "window" freezes visuals after tiling
Public bug reported: The firefox window view freezes, the window is actually still taking input as I can press ctrl+L and type something in the address bar, minimize and maximize to see the view _refreshed_. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell-extension-ubuntu-tiling-assistant 44-1ubuntu1 ProcVersionSignature: Ubuntu 6.1.0-1025.25-oem 6.1.57 Uname: Linux 6.1.0-1025-oem x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 21 13:19:40 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220504-33 InstallationDate: Installed on 2023-07-09 (136 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 PackageArchitecture: all SourcePackage: gnome-shell-extension-tiling-assistant UpgradeStatus: Upgraded to mantic on 2023-11-17 (5 days ago) ** Affects: gnome-shell-extension-tiling-assistant (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-tiling-assistant in Ubuntu. https://bugs.launchpad.net/bugs/2044156 Title: Firefox "window" freezes visuals after tiling Status in gnome-shell-extension-tiling-assistant package in Ubuntu: New Bug description: The firefox window view freezes, the window is actually still taking input as I can press ctrl+L and type something in the address bar, minimize and maximize to see the view _refreshed_. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell-extension-ubuntu-tiling-assistant 44-1ubuntu1 ProcVersionSignature: Ubuntu 6.1.0-1025.25-oem 6.1.57 Uname: Linux 6.1.0-1025-oem x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 21 13:19:40 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220504-33 InstallationDate: Installed on 2023-07-09 (136 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 PackageArchitecture: all SourcePackage: gnome-shell-extension-tiling-assistant UpgradeStatus: Upgraded to mantic on 2023-11-17 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2044156/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043264] Re: [amdgpu] External monitor keeps blinking and not connected, with Kubuntu Linux (KDE)
Can you please try to reproduce using a mainline upstream build? https://kernel.ubuntu.com/mainline/v6.7-rc2/ If you can reproduce please share a new kernel log from a boot it occurs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/2043264 Title: [amdgpu] External monitor keeps blinking and not connected, with Kubuntu Linux (KDE) Status in linux package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: --- en Always, almost every time I turn on my notebook, my LG external monitor keeps blinking and it takes a while to actually connect to the notebook and the external monitor screen to turn on. For the external monitor to work I change the video settings using Ctrl + P and turn the monitor off/on several times. In Kubuntu it is recognized but when it blinks the system thinks the monitor is off. I'm using Kubuntu 23.04, I've used other distributions on the same hardware and this problem hasn't happened. I believe it's something with KDE. --- pt-br Sempre, quase toda vez que ligo meu notebook, meu monitor externo LG fica piscando e demora para realmente conectar ao notebook e a tela do monitor externo ligar. Para o monitor externo funcionar eu mudo as configurações de vídeo usando Ctrl + P e desligo/ligo o monitor várias vezes. No Kubuntu ele é reconhecido mas quando fica piscando o sistema acha que o monitor está desligado. Estou usando o Kubuntu 23.04, já usei outras distribuições no mesmo hardware e esse problema não aconteceu. Eu acredito que seja algo com o KDE. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-36.37-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE Date: Sat Nov 11 07:52:24 2023 DistUpgraded: 2023-11-02 07:28:00,578 DEBUG /openCache(), new cache size 78921 DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] [17aa:3804] InstallationDate: Installed on 2022-10-23 (383 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 81V7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic root=UUID=d72b8a6b-953f-4b38-8b0a-d1e9b6899ad2 ro quiet splash iommu=soft vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-11-02 (9 days ago) dmi.bios.date: 05/19/2020 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: BUCN25WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15API dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrBUCN25WW:bd05/19/2020:br1.25:efr1.25:svnLENOVO:pn81V7:pvrLenovoIdeaPadS145-15API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15API:skuLENOVO_MT_81V7_BU_idea_FM_IdeaPadS145-15API: dmi.product.family: IdeaPad S145-15API dmi.product.name: 81V7 dmi.product.sku: LENOVO_MT_81V7_BU_idea_FM_IdeaPad S145-15API dmi.product.version: Lenovo IdeaPad S145-15API dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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/+source/linux/+bug/2043264/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044151] [NEW] Audio device underrun detected (but sound works with firefox)
Public bug reported: Terminal Radio has started not working using Mantic. It dies within the first few seconds of streaming: ``` TERA SEARCH SUBMENU: 1) Play 2) Save 3) Go back to the Search menu 4) Go back to the Main menu 0) Exit Choose an option: 1 (+) Audio --aid=1 (mp3 2ch 44100Hz) AO: [pipewire] 44100Hz stereo 2ch floatp A: 00:00:00 / 00:00:12 (8%) Cache: 11s/397KB File tags: icy-title: DJ Mikey T A: 00:00:15 / 00:00:15 (100%) Cache: 0.0s Audio device underrun detected. (Buffering) A: 00:00:15 / 00:00:15 (100%) Cache: 0.0s Exiting... (Quit) Not able to play your station. ``` Sound works using regular web browser and media files. TeRa can be found @ https://github.com/shinokada/tera ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pipewire 0.3.79-2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue Nov 21 10:53:51 2023 InstallationDate: Installed on 2023-04-14 (221 days ago) InstallationMedia: Ubuntu-MATE 22.10 "Kinetic Kudu" - Release amd64 (20221018) SourcePackage: pipewire UpgradeStatus: Upgraded to mantic on 2023-10-13 (39 days ago) ** Affects: pipewire (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/2044151 Title: Audio device underrun detected (but sound works with firefox) Status in pipewire package in Ubuntu: New Bug description: Terminal Radio has started not working using Mantic. It dies within the first few seconds of streaming: ``` TERA SEARCH SUBMENU: 1) Play 2) Save 3) Go back to the Search menu 4) Go back to the Main menu 0) Exit Choose an option: 1 (+) Audio --aid=1 (mp3 2ch 44100Hz) AO: [pipewire] 44100Hz stereo 2ch floatp A: 00:00:00 / 00:00:12 (8%) Cache: 11s/397KB File tags: icy-title: DJ Mikey T A: 00:00:15 / 00:00:15 (100%) Cache: 0.0s Audio device underrun detected. (Buffering) A: 00:00:15 / 00:00:15 (100%) Cache: 0.0s Exiting... (Quit) Not able to play your station. ``` Sound works using regular web browser and media files. TeRa can be found @ https://github.com/shinokada/tera ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pipewire 0.3.79-2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue Nov 21 10:53:51 2023 InstallationDate: Installed on 2023-04-14 (221 days ago) InstallationMedia: Ubuntu-MATE 22.10 "Kinetic Kudu" - Release amd64 (20221018) SourcePackage: pipewire UpgradeStatus: Upgraded to mantic on 2023-10-13 (39 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2044151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038783] Re: Exit code of locations mount script is not respecting error
** Description changed: [ Impact ] When mounting an external location a script is used to get the current default app for a type, its return error is parsed by the dock to provide users a feedback, but the returned code is not valid in case of error. [ Test case ] Run: - gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js /foo/bar/baz - echo $? + gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js handler /foo/bar/baz + echo $? An error should be shown and the return code should be 15 Doing instead - gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js $HOME - echo $? + gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js handler $HOME + echo $? The file manager desktop-id should be printed and the script should return 0. [ Regression Potential ] Some locations may not have a default handler and so not being launched ** Description changed: [ Impact ] When mounting an external location a script is used to get the current default app for a type, its return error is parsed by the dock to provide users a feedback, but the returned code is not valid in case of error. [ Test case ] Run: - gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js handler /foo/bar/baz + gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js handler file:///foo/bar/baz echo $? An error should be shown and the return code should be 15 Doing instead - gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js handler $HOME + gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js handler file://$HOME echo $? The file manager desktop-id should be printed and the script should return 0. [ Regression Potential ] Some locations may not have a default handler and so not being launched -- 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/2038783 Title: Exit code of locations mount script is not respecting error Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Mantic: Fix Committed Bug description: [ Impact ] When mounting an external location a script is used to get the current default app for a type, its return error is parsed by the dock to provide users a feedback, but the returned code is not valid in case of error. [ Test case ] Run: gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js handler file:///foo/bar/baz echo $? An error should be shown and the return code should be 15 Doing instead gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js handler file://$HOME echo $? The file manager desktop-id should be printed and the script should return 0. [ Regression Potential ] Some locations may not have a default handler and so not being launched To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2038783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
** Changed in: oem-priority
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1990341
Title:
[SRU] Support to install nvidia driver by allowing list
Status in OEM Priority Project:
Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common source package in Jammy:
Fix Released
Status in ubuntu-drivers-common source package in Lunar:
Fix Released
Bug description:
[ Impact ]
* In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at
the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
[ Test Plan ]
* Steps to make sure it works:
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool by removing restricted in jammy-updates and
jammy-security
3. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
4. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
5. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
[ Where problems could occur ]
* This feature only impact target system has a custom file
"/etc/custom_supported_gpus.json". And it won't generate automatically
which should not impact normal users
[ Other Info ]
* the patches are picked from
-
https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
-
https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
-
https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
* Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044089] Re: Raspberry Pi 5 --> Settings --> About doesnt display all the information
*** This bug is a duplicate of bug 1964601 *** https://bugs.launchpad.net/bugs/1964601 Thank you for your bug report, that was already reported as bug #1964601 ** This bug has been marked a duplicate of bug 1964601 incorrect cpu/graphics/disks information on raspi -- 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/2044089 Title: Raspberry Pi 5 --> Settings --> About doesnt display all the information Status in gnome-control-center package in Ubuntu: New Bug description: Raspberry Pi 5, Running the latest 23.10. About section is missing two items: - Processor - Disk Capacity $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:45.0-1ubuntu3 Candidate: 1:45.0-1ubuntu3 Version table: *** 1:45.0-1ubuntu3 500 500 http://ports.ubuntu.com/ubuntu-ports mantic-updates/main arm64 Packages 100 /var/lib/dpkg/status 1:45.0-1ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports mantic/main arm64 Packages # System Details Report --- ## Report details - **Date generated:** 2023-11-21 09:04:13 ## Hardware Information: - **Hardware Model:** (null) - **Memory:** 7.8 GiB - **Processor:** - **Graphics:**V3D 7.1 - **Disk Capacity:** (null) ## Software Information: - **Firmware Version:**(null) - **OS Name:** Ubuntu 23.10 - **OS Build:**(null) - **OS Type:** 64-bit - **GNOME Version:** 45.0 - **Windowing System:**Wayland - **Kernel Version:** Linux 6.5.0-1006-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2044089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043376] Re: adsys cant fetch gpos ubuntu 22.04.3
Hey, thanks for your bug report. Given that smbclient fails in a similar manner, this suggests that the issue is not limited to adsys but other programs interacting with AD too. Unfortunately NT_STATUS_INVALID_PARAMETER is a very common catch- all error and the root cause could be very environment-dependent. Can you paste the output of `klist` after running the `export KRB5CCNAME...` command? Also, what Windows version are you running on the domain controller? Additionally, to confirm, did you join the domain using the `realm join` command? It may be worth it to leave and rejoin the domain. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2043376 Title: adsys cant fetch gpos ubuntu 22.04.3 Status in adsys package in Ubuntu: New Bug description: VERSIONS: ubuntu 22.04.3 libsmbclient 2:4.15.13+dfsg-0ubuntu1.5 adsysctl 0.9.2~22.04.2 adsysd 0.9.2~22.04.2 Hi when i try the command adsysctl update -m or --all i receive this error: Error from server: error while updating policy: cant get policies for "ubuntuvm": failed to retrieve the list of GPO (exited with -1): signal: killed Failed to bind - LDAP client internal error: NT_STATUS_INVALID_PARAMETER Failed to connect to 'ldap://addc01.domain.com' with backend 'ldap': LDAP client internal error: NT_STATUS_INVALID_PARAMETER Failed to open session: (1, 'LDAP client internal error: NT_STATUS_INVALID_PARAMETER'). Result of adsysctl service cat -vvv NFO github.com/ubuntu/adsys/internal/config/config.go:73 Init() No configuration file: Config File "adsys" Not Found in "[/home/ubuntuvm /etc /usr/sbin]". We will only use the defaults, env variables or flags. DEBUG Connecting as [[41753:876951]] DEBUG github.com/ubuntu/adsys/internal/grpc/logconnections/logconnections.go:27 StreamServerInterceptor.func1() New request /service/Cat DEBUG github.com/ubuntu/adsys/internal/grpc/logconnections/logconnections.go:60 loggedServerStream.RecvMsg() Requesting with parameters: DEBUG github.com/ubuntu/adsys/internal/authorizer/authorizer.go:111 Authorizer.IsAllowedFromContext() Check if grpc request peer is authorized DEBUG github.com/ubuntu/adsys/internal/authorizer/authorizer.go:191 Authorizer.isAllowed() Polkit call result, authorized: true DEBUG github.com/ubuntu/adsys/internal/ad/ad.go:397 (*AD).ListActiveUsers() [[41745:695267]] ListActiveUsers INFO github.com/ubuntu/adsys/internal/grpc/logconnections/logconnections.go:39 StreamServerInterceptor.func1() Error sent to client: error while updating policy: can't get policies for "ubuntuvm": failed to retrieve the list of GPO (exited with -1): signal: killed DEBUG github.com/ubuntu/adsys/internal/grpc/logconnections/logconnections.go:33 StreamServerInterceptor.func1.1() Request /service/UpdatePolicy done INFO github.com/ubuntu/adsys/internal/grpc/interceptorschain/chainer.go:16 StreamServer.func1.1.1() New connection from client [[41768:773422]] DEBUG github.com/ubuntu/adsys/internal/grpc/logconnections/logconnections.go:27 StreamServerInterceptor.func1() [[41768:773422]] New request /service/UpdatePolicy DEBUG github.com/ubuntu/adsys/internal/grpc/logconnections/logconnections.go:60 loggedServerStream.RecvMsg() [[41768:773422]] Requesting with parameters: IsComputer: false, All: true, Target: , Krb5Cc: DEBUG github.com/ubuntu/adsys/internal/ad/ad.go:571 (*AD).NormalizeTargetName() [[41768:773422]] NormalizeTargetName for "", type "computer" DEBUG github.com/ubuntu/adsys/internal/authorizer/authorizer.go:111 Authorizer.IsAllowedFromContext() [[41768:773422]] Check if grpc request peer is authorized DEBUG github.com/ubuntu/adsys/internal/authorizer/authorizer.go:150 Authorizer.isAllowed() [[41768:773422]] Authorized as being administrator DEBUG github.com/ubuntu/adsys/internal/ad/ad.go:225 (*AD).GetPolicies() [[41768:773422]] GetPolicies for "ubuntuvm", type "computer" DEBUG github.com/ubuntu/adsys/internal/ad/ad.go:293 (*AD).GetPolicies() [[41768:773422]] Getting gpo list with arguments: "--objectclass computer ldap://addc01.domain.com ubuntuvm" DEBUG github.com/ubuntu/adsys/internal/ad/ad.go:397 (*AD).ListActiveUsers() [[41768:773422]] ListActiveUsers INFO github.com/ubuntu/adsys/internal/grpc/logconnections/logconnections.go:39 StreamServerInterceptor.func1() Error sent to client: error while updating policy: can't get policies for "ubuntuvm": failed to retrieve the list of GPO (exited with -1): signal: killed When I run the commands: export KRB5CCNAME=/var/run/adsys/krb5cc/$(hostname) adsysctl policy debug gpolist-script chmod +x adsys-gpolist ./adsys-gpolist --objectclass computer ldap:// $(hostname) adsys-gpolist script get this error: Failed to bind - LDAP client internal error: NT_STATUS_INVALID_PARAMETER Failed to connect to 'ldap://addc01.domain.com' with backend 'ldap': LDAP clien
[Desktop-packages] [Bug 2044112] [NEW] Add dependency on nfs-common
Public bug reported: The nfs-common package is required if NFS shares are to be mounted on the client. Unlike cifs-utils, this package is not installed by default on Ubuntu Desktop. Given that we declare the former as a dependency we should do the same with nfs-common. ** Affects: adsys (Ubuntu) Importance: Undecided Status: Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2044112 Title: Add dependency on nfs-common Status in adsys package in Ubuntu: Fix Committed Bug description: The nfs-common package is required if NFS shares are to be mounted on the client. Unlike cifs-utils, this package is not installed by default on Ubuntu Desktop. Given that we declare the former as a dependency we should do the same with nfs-common. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2044112/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884759] Re: [snap] U2f yubikey not recognized until unplugged and plugged back in
** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Fix Released -- 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/1884759 Title: [snap] U2f yubikey not recognized until unplugged and plugged back in Status in chromium-browser package in Ubuntu: Fix Released Bug description: I was previously using u2f from yubikey in chromium snap, but now it doesn't work. No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced. U2f still works in firefox installed as deb. # snap connections chromium | grep u2f u2f-devices chromium:u2f-devices :u2f-devices manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884759/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879137] Re: The snap-store is using hundreds of MiBs of RAM.
@waveform (Dave Jones) The issue is still reproducible for me on 23.10 (see the new attached picture). Snap-store used 2GB RAM my laptop with 1 day uptime only (and the RAM usage is growing over the time, please check my screenshot in https://bugs.launchpad.net/snap-store-desktop/+bug/1879137/comments/36 26GB RAM used by snap-store there !!!) Happy to help with tracing it, feel free to ping me in MM! ** Attachment added: "snap-store.png" https://bugs.launchpad.net/snap-store-desktop/+bug/1879137/+attachment/5721584/+files/snap-store.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1879137 Title: The snap-store is using hundreds of MiBs of RAM. Status in GNOME Software: New Status in snap-store-desktop: Confirmed Status in gnome-software package in Ubuntu: Confirmed Bug description: The snap-store process is intermittently using hundreds of megabytes of RAM. Is this normal? Is there a solution? Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1879137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044089] [NEW] Raspberry Pi 5 --> Settings --> About doesnt display all the information
Public bug reported: Raspberry Pi 5, Running the latest 23.10. About section is missing two items: - Processor - Disk Capacity $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:45.0-1ubuntu3 Candidate: 1:45.0-1ubuntu3 Version table: *** 1:45.0-1ubuntu3 500 500 http://ports.ubuntu.com/ubuntu-ports mantic-updates/main arm64 Packages 100 /var/lib/dpkg/status 1:45.0-1ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports mantic/main arm64 Packages # System Details Report --- ## Report details - **Date generated:** 2023-11-21 09:04:13 ## Hardware Information: - **Hardware Model:** (null) - **Memory:** 7.8 GiB - **Processor:** - **Graphics:**V3D 7.1 - **Disk Capacity:** (null) ## Software Information: - **Firmware Version:**(null) - **OS Name:** Ubuntu 23.10 - **OS Build:**(null) - **OS Type:** 64-bit - **GNOME Version:** 45.0 - **Windowing System:**Wayland - **Kernel Version:** Linux 6.5.0-1006-raspi ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Attachment added: "2023-11-21_09-09-04.png" https://bugs.launchpad.net/bugs/2044089/+attachment/5721581/+files/2023-11-21_09-09-04.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2044089 Title: Raspberry Pi 5 --> Settings --> About doesnt display all the information Status in gnome-control-center package in Ubuntu: New Bug description: Raspberry Pi 5, Running the latest 23.10. About section is missing two items: - Processor - Disk Capacity $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:45.0-1ubuntu3 Candidate: 1:45.0-1ubuntu3 Version table: *** 1:45.0-1ubuntu3 500 500 http://ports.ubuntu.com/ubuntu-ports mantic-updates/main arm64 Packages 100 /var/lib/dpkg/status 1:45.0-1ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports mantic/main arm64 Packages # System Details Report --- ## Report details - **Date generated:** 2023-11-21 09:04:13 ## Hardware Information: - **Hardware Model:** (null) - **Memory:** 7.8 GiB - **Processor:** - **Graphics:**V3D 7.1 - **Disk Capacity:** (null) ## Software Information: - **Firmware Version:**(null) - **OS Name:** Ubuntu 23.10 - **OS Build:**(null) - **OS Type:** 64-bit - **GNOME Version:** 45.0 - **Windowing System:**Wayland - **Kernel Version:** Linux 6.5.0-1006-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2044089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967488] Re: [nvidia] Chromium stable snap doesn't display anything on Wayland with Nvidia as primary GPU
** Summary changed: - [nvidia] Chromium stable snap don't work on Wayland with Nvidia as primary GPU + [nvidia] Chromium stable snap doesn't display anything on Wayland with Nvidia as primary GPU -- 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/1967488 Title: [nvidia] Chromium stable snap doesn't display anything on Wayland with Nvidia as primary GPU Status in chromium-browser package in Ubuntu: Triaged Bug description: Hi I'm testing the Ubuntu 22.04 beta with wayland and when I try to open the Chromium browser (stable snap package), only see a black/transparent window. If I switch from Wayland to Xorg, everything is normal again. I tried to delete the profile folder , but I have the same result. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1967488/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1978905] Re: Reverse PRIME support for Wayland (Nvidia as primary GPU outputting to Intel GPU display ports)
It's been a while so this needs retesting. ** Changed in: mutter (Ubuntu) Status: Triaged => Incomplete ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1978905 Title: Reverse PRIME support for Wayland (Nvidia as primary GPU outputting to Intel GPU display ports) Status in Mutter: New Status in mutter package in Ubuntu: Incomplete Bug description: Reverse PRIME support for Wayland (Nvidia as primary GPU outputting to Intel GPU display ports) This is different to the usual dual GPU setup where Intel is primary and Nvidia is secondary. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1978905/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967488] Re: [nvidia] Chromium stable snap don't work on Wayland with Nvidia as primary GPU
^^^ Suspiciously like bug 2023322 now -- 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/1967488 Title: [nvidia] Chromium stable snap doesn't display anything on Wayland with Nvidia as primary GPU Status in chromium-browser package in Ubuntu: Triaged Bug description: Hi I'm testing the Ubuntu 22.04 beta with wayland and when I try to open the Chromium browser (stable snap package), only see a black/transparent window. If I switch from Wayland to Xorg, everything is normal again. I tried to delete the profile folder , but I have the same result. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1967488/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967488] Re: Chromium stable snap don't work on Wayland
It's still broken on mantic with chromium snap 119.0.6045.159. The console seems to repeat: KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied ... But Google Chrome (deb version 119.0.6045.159-1) works perfectly. So this sounds like a confinement problem. ** Summary changed: - Chromium stable snap don't work on Wayland (NVIDIA 510.60.02 driver) + Chromium stable snap don't work on Wayland ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Triaged ** Tags added: mantic ** Description changed: Hi - I'm testing the Ubuntu 22.04 beta with wayland and when I try to open the Chromium browser (stable snap package), only see a black window. If I switch from Wayland to Xorg, everything is normal again. + I'm testing the Ubuntu 22.04 beta with wayland and when I try to open the Chromium browser (stable snap package), only see a black/transparent window. If I switch from Wayland to Xorg, everything is normal again. I tried to delete the profile folder , but I have the same result. ** Summary changed: - Chromium stable snap don't work on Wayland + [nvidia] Chromium stable snap don't work on Wayland ** Summary changed: - [nvidia] Chromium stable snap don't work on Wayland + [nvidia] Chromium stable snap don't work on Wayland with Nvidia as primary GPU -- 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/1967488 Title: [nvidia] Chromium stable snap don't work on Wayland with Nvidia as primary GPU Status in chromium-browser package in Ubuntu: Triaged Bug description: Hi I'm testing the Ubuntu 22.04 beta with wayland and when I try to open the Chromium browser (stable snap package), only see a black/transparent window. If I switch from Wayland to Xorg, everything is normal again. I tried to delete the profile folder , but I have the same result. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1967488/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
This sounds relevant: > This threshold can be set to 0 in order to prevent the video memory from being turned off. https://download.nvidia.com/XFree86/Linux-x86_64/535.129.03/README/dynamicpowermanagement.html#VidMemThreshold -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend Status in GNOME Shell: New Status in Mutter: Fix Released Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-460 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-470 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-525 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-535 package in Ubuntu: Triaged Bug description: [Impact] The Nvidia driver corrupts and/or forgets its textures when resuming from suspend, by design. Documented here: https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt Although it's so awkward to implement everywhere that realistically compositors will never support it fully. Instead we're waiting for an Nvidia driver fix. *NOTE* that this is actually not a common problem because the system must be using Nvidia as the primary GPU to be affected. So generally only desktop users will encounter the bug, not laptops. And even then, only desktops that use suspend/resume and VT switching may trigger it, if ever. Even in development the bug cannot be reproduced reliably. [Workarounds] * Always log into a Xorg session and if corruption occurs then type: Alt+F2, R, Enter * https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0 [Test Plan] [Where problems could occur] [Original Bug Report] I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.pro
