[Desktop-packages] [Bug 2044336] Re: Lots of error message filling disk
Thanks for the swift answer. It happens upon every boot, when Wayland is started. Here's the file attached. ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2044336/+attachment/5722640/+files/journal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2044336 Title: Lots of error message filling disk Status in gnome-shell package in Ubuntu: Incomplete Bug description: Since I upgraded to Ubuntu 23.10 the GUI is unresponsive during, maybe 30 seconds, then it works perfectly fine. I connected via SSH to see what was happening in the logs when that happens and it may be the logs collected, e.g.: 2023-11-23T08:01:07.113135+01:00 enfants-ecole gnome-shell[1234]: Attempting to call back into JSAPI during the sweepin g phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals conne cted, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the applicat ion, it has been blocked and the JS callback not invoked.#012The offending signal was notify on Gjs_ubuntu-dock_ubuntu_ com_docking_DashToDock 0x55a9a71d3fb0.#012== Stack trace for context 0x55a9a45f9d40 ==#012#0 55a9a46bc888 i resourc e:///org/gnome/shell/ui/init.js:21 (6ea76470ba0 @ 48) 2023-11-23T08:01:07.113227+01:00 enfants-ecole gnome-shell[1234]: Can't update stage views actor [:0x55a9a738ab20] is on because it needs an allocation. 2023-11-23T08:01:07.113319+01:00 enfants-ecole gnome-shell[1234]: Can't update stage views actor [:0x55a9a738b8f0] is on because it needs an allocation. 2023-11-23T08:01:07.113407+01:00 enfants-ecole gnome-shell[1234]: Can't update stage views actor [:0x55a9a71d58d0] is on because it needs an allocation. 2023-11-23T08:01:07.113495+01:00 enfants-ecole gnome-shell[1234]: Can't update stage views actor [:0 x55a9a7385880] is on because it needs an allocation. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3 Uname: Linux 6.5.0-13-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Nov 23 08:06:45 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-11-22 (0 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) RelatedPackageVersions: mutter-common 45.0-3ubuntu3.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-11-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2044336/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044339] [NEW] Audio output doesnt work if laptop gets shut down with a headset plugged in
Public bug reported: Apologies if this is the wrong package. I am experiencing an issue with Ubuntu 22.04.1 LTS where the audio output doesnt work if previously device was shut down with a headset plugged in. Steps: - Device is up and running - Plug in headset (aux jack) - Turn off device - Plug out headset - Turn on device - No audio output In order to fix it, I have to plug the headset back in. Once plugged in, I get audio output on both the headset. While laptop is running, if I plug the headset out again, I get audio on the laptop's speakers too. I end up without any audio output. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2044339 Title: Audio output doesnt work if laptop gets shut down with a headset plugged in Status in pulseaudio package in Ubuntu: New Bug description: Apologies if this is the wrong package. I am experiencing an issue with Ubuntu 22.04.1 LTS where the audio output doesnt work if previously device was shut down with a headset plugged in. Steps: - Device is up and running - Plug in headset (aux jack) - Turn off device - Plug out headset - Turn on device - No audio output In order to fix it, I have to plug the headset back in. Once plugged in, I get audio output on both the headset. While laptop is running, if I plug the headset out again, I get audio on the laptop's speakers too. I end up without any audio output. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2044339/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044336] Re: Lots of error message filling disk
Those types of errors are not unusual and don't usually lead to an unresponsive GUI. So we might be conflating the GUI issue with unrelated log messages. Although this repeating: The offending signal was g-properties-changed on GDBusProxy 0x55a9a6ea0c60. might be related. Next time a freeze happens and recovers, please then run: journalctl -b0 > journal.txt and attach the resulting text file here. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2044336 Title: Lots of error message filling disk Status in gnome-shell package in Ubuntu: Incomplete Bug description: Since I upgraded to Ubuntu 23.10 the GUI is unresponsive during, maybe 30 seconds, then it works perfectly fine. I connected via SSH to see what was happening in the logs when that happens and it may be the logs collected, e.g.: 2023-11-23T08:01:07.113135+01:00 enfants-ecole gnome-shell[1234]: Attempting to call back into JSAPI during the sweepin g phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals conne cted, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the applicat ion, it has been blocked and the JS callback not invoked.#012The offending signal was notify on Gjs_ubuntu-dock_ubuntu_ com_docking_DashToDock 0x55a9a71d3fb0.#012== Stack trace for context 0x55a9a45f9d40 ==#012#0 55a9a46bc888 i resourc e:///org/gnome/shell/ui/init.js:21 (6ea76470ba0 @ 48) 2023-11-23T08:01:07.113227+01:00 enfants-ecole gnome-shell[1234]: Can't update stage views actor [:0x55a9a738ab20] is on because it needs an allocation. 2023-11-23T08:01:07.113319+01:00 enfants-ecole gnome-shell[1234]: Can't update stage views actor [:0x55a9a738b8f0] is on because it needs an allocation. 2023-11-23T08:01:07.113407+01:00 enfants-ecole gnome-shell[1234]: Can't update stage views actor [:0x55a9a71d58d0] is on because it needs an allocation. 2023-11-23T08:01:07.113495+01:00 enfants-ecole gnome-shell[1234]: Can't update stage views actor [:0 x55a9a7385880] is on because it needs an allocation. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3 Uname: Linux 6.5.0-13-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Nov 23 08:06:45 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-11-22 (0 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) RelatedPackageVersions: mutter-common 45.0-3ubuntu3.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-11-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2044336/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044336] [NEW] Lots of error message filling disk
Public bug reported: Since I upgraded to Ubuntu 23.10 the GUI is unresponsive during, maybe 30 seconds, then it works perfectly fine. I connected via SSH to see what was happening in the logs when that happens and it may be the logs collected, e.g.: 2023-11-23T08:01:07.113135+01:00 enfants-ecole gnome-shell[1234]: Attempting to call back into JSAPI during the sweepin g phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals conne cted, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the applicat ion, it has been blocked and the JS callback not invoked.#012The offending signal was notify on Gjs_ubuntu-dock_ubuntu_ com_docking_DashToDock 0x55a9a71d3fb0.#012== Stack trace for context 0x55a9a45f9d40 ==#012#0 55a9a46bc888 i resourc e:///org/gnome/shell/ui/init.js:21 (6ea76470ba0 @ 48) 2023-11-23T08:01:07.113227+01:00 enfants-ecole gnome-shell[1234]: Can't update stage views actor [:0x55a9a738ab20] is on because it needs an allocation. 2023-11-23T08:01:07.113319+01:00 enfants-ecole gnome-shell[1234]: Can't update stage views actor [:0x55a9a738b8f0] is on because it needs an allocation. 2023-11-23T08:01:07.113407+01:00 enfants-ecole gnome-shell[1234]: Can't update stage views actor [:0x55a9a71d58d0] is on because it needs an allocation. 2023-11-23T08:01:07.113495+01:00 enfants-ecole gnome-shell[1234]: Can't update stage views actor [:0 x55a9a7385880] is on because it needs an allocation. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3 Uname: Linux 6.5.0-13-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Nov 23 08:06:45 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-11-22 (0 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) RelatedPackageVersions: mutter-common 45.0-3ubuntu3.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-11-22 (0 days ago) ** Affects: gnome-shell (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 in Ubuntu. https://bugs.launchpad.net/bugs/2044336 Title: Lots of error message filling disk Status in gnome-shell package in Ubuntu: New Bug description: Since I upgraded to Ubuntu 23.10 the GUI is unresponsive during, maybe 30 seconds, then it works perfectly fine. I connected via SSH to see what was happening in the logs when that happens and it may be the logs collected, e.g.: 2023-11-23T08:01:07.113135+01:00 enfants-ecole gnome-shell[1234]: Attempting to call back into JSAPI during the sweepin g phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals conne cted, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the applicat ion, it has been blocked and the JS callback not invoked.#012The offending signal was notify on Gjs_ubuntu-dock_ubuntu_ com_docking_DashToDock 0x55a9a71d3fb0.#012== Stack trace for context 0x55a9a45f9d40 ==#012#0 55a9a46bc888 i resourc e:///org/gnome/shell/ui/init.js:21 (6ea76470ba0 @ 48) 2023-11-23T08:01:07.113227+01:00 enfants-ecole gnome-shell[1234]: Can't update stage views actor [:0x55a9a738ab20] is on because it needs an allocation. 2023-11-23T08:01:07.113319+01:00 enfants-ecole gnome-shell[1234]: Can't update stage views actor [:0x55a9a738b8f0] is on because it needs an allocation. 2023-11-23T08:01:07.113407+01:00 enfants-ecole gnome-shell[1234]: Can't update stage views actor [:0x55a9a71d58d0] is on because it needs an allocation. 2023-11-23T08:01:07.113495+01:00 enfants-ecole gnome-shell[1234]: Can't update stage views actor [:0 x55a9a7385880] is on because it needs an allocation. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3 Uname: Linux 6.5.0-13-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Nov 23 08:06:45 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-11-22 (0 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) RelatedPackageVersions: mutter-common 45.0-3ubuntu3.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-11-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2044336/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1971168]
(In reply to Sergio Costas from comment #52) > The patch has landed in upstream today. I mean: it has been merged today. -- 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 1971168]
The patch has landed in upstream today. -- 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 2016217] Re: gnome-shell crashed with SIGSEGV in clutter_actor_remove_effect() from st_scroll_view_dispose() from g_object_unref() from GjsAutoPointer() from GjsAutoPointer()
Officially the fix is now released. And we're not receiving any crash
reports for this in 45.1. But please continue to report all crashes you
encounter.
** Changed in: gnome-shell (Ubuntu)
Status: Fix Committed => Fix Released
** Also affects: gnome-shell (Ubuntu Noble)
Importance: High
Assignee: Jeremy Bícha (jbicha)
Status: Fix Released
** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Noble)
Importance: High
Status: Won't Fix
** Also affects: gnome-shell (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Mantic)
Status: New => Won't Fix
** Changed in: gnome-shell (Ubuntu Mantic)
Status: New => Fix Committed
** Changed in: gnome-shell (Ubuntu Mantic)
Assignee: (unassigned) => Jeremy Bícha (jbicha)
** Changed in: gnome-shell (Ubuntu Mantic)
Importance: Undecided => High
--
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/2016217
Title:
gnome-shell crashed with SIGSEGV in clutter_actor_remove_effect() from
st_scroll_view_dispose() from g_object_unref() from GjsAutoPointer()
from GjsAutoPointer()
Status in GNOME Shell:
Fix Released
Status in gnome-shell package in Ubuntu:
Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
Won't Fix
Status in gnome-shell source package in Mantic:
Fix Committed
Status in gnome-shell-extension-ubuntu-dock source package in Mantic:
Won't Fix
Status in gnome-shell source package in Noble:
Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Noble:
Won't Fix
Status in gnome-shell package in Fedora:
Confirmed
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-shell. This problem was most recently seen with package version
44.0-2ubuntu3, the problem page at
https://errors.ubuntu.com/problem/677a794c2788cd0244c8fc6d7d34780a85127bc9
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
#0 0x7f3aa429dd82 in clutter_actor_remove_effect
(self=self@entry=0x55d60fa59e90, effect=0x55d6101c48a0) at
../clutter/clutter/clutter-actor.c:14830
__inst = 0x55d6101c48a0
__t = 94377826055744
__r =
_g_boolean_var_274 =
__func__ = "clutter_actor_remove_effect"
#1 0x7f3aa3f9d27f in st_scroll_view_dispose (object=0x55d60fa59e90) at
../src/st/st-scroll-view.c:246
priv = 0x55d60fa59a00
#2 0x7f3aa4aeada0 in g_object_unref (_object=0x55d60fa59e90) at
../../../gobject/gobject.c:3891
_pp =
gaig_temp =
gaig_temp =
weak_locations =
nqueue = 0x55d60fa6da60
_ptr =
object = 0x55d60fa59e90
old_ref =
retry_atomic_decrement1 =
__func__ = "g_object_unref"
#3 0x7f3aa43b4b2c in GjsAutoPointer<_GObject, void, &g_object_unref,
&g_object_ref>::reset (ptr=0x0, this=) at ../gjs/jsapi-util.h:229
old_ptr =
#4 GjsAutoPointer<_GObject, void, &g_object_unref,
&g_object_ref>::~GjsAutoPointer (this=, this=) at
../gjs/jsapi-util.h:172
No locals.
#5 GjsSmartPointer<_GObject>::~GjsSmartPointer (this=,
this=) at ../gjs/jsapi-util.h:349
No locals.
#6 ObjectInstance::release_native_object (this=0x55d60fa0ce80) at
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gi/object.cpp:1524
No locals.
#7 ObjectInstance::release_native_object (this=0x55d60fa0ce80) at
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gi/object.cpp:1500
No locals.
#8 0x7f3aa43c9ec0 in ObjectInstance::~ObjectInstance (this=, this=) at
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gi/object.cpp:1945
was_using_toggle_refs = false
had_toggle_up = false
had_toggle_down =
had_toggle_up =
had_toggle_down =
was_using_toggle_refs =
#9 GIWrapperInstance::finalize_impl (this=0x55d60fa0ce80) at ../gi/wrapperutils.h:1113
No locals.
#10 ObjectInstance::finalize_impl (gcx=, obj=0x35b1abd24820,
this=0x55d60fa0ce80) at
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gi/object.cpp:1912
query = {type = 94377830362416, type_name = 0x7f3aa3fdcda6
"StScrollView", class_size = 664, instance_size = 48}
query =
_g_boolean_var_74 =
#11 GIWrapperBase::finalize
(gcx=, obj=0x35b1abd24820) at ../gi/wrapperutils.h:411
priv = 0x55d60fa0ce80
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2016217/+
[Desktop-packages] [Bug 592661] Re: "File" menu in shotwell violates HIG
** Changed in: shotwell Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/592661 Title: "File" menu in shotwell violates HIG Status in Shotwell: Fix Released Status in shotwell package in Ubuntu: Triaged Bug description: Binary package hint: shotwell According to Gnome HIG : http://library.gnome.org/devel/hig-book/stable/menus-standard.html.en#the-file-menu "If your application does not operate on documents, name this item for the type of object it displays. For example, many games should have a Game instead of a File menu. However, place the Quit menu item last on this menu nonetheless." The "Photos" and "File" menu need to be merged and the edit functions in "Photos" menu moved to the "Edit" Menu. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: shotwell 0.5.0+dfsg-1.1 Uname: Linux 2.6.34-020634-generic i686 Architecture: i386 Date: Fri Jun 11 15:10:44 2010 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20091209) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: shotwell To manage notifications about this bug go to: https://bugs.launchpad.net/shotwell/+bug/592661/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973467] Re: [Wayland] Backlight stays on with black screen when monitor should be sleeping
*** This bug is a duplicate of bug 1971434 *** https://bugs.launchpad.net/bugs/1971434 ** This bug has been marked a duplicate of bug 1971434 Display powersave only blanks, but does not turn off -- 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/1973467 Title: [Wayland] Backlight stays on with black screen when monitor should be sleeping Status in mutter package in Ubuntu: Confirmed Bug description: In Power -> Power Saving Options -> Screen Blank - the option states that the screen will be turned off after some period, which is what I'd expect from a sleep mode. I have a hybrid system. I have disabled the internal display and I use the external connected via HDMI (and I believe it is connected to the NVIDIA GPU). When the screen goes blank the external monitor is not turned off really. It goes blank but it is still turned on and glows, so no power is saved. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 15 19:16:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:0798] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0798] InstallationDate: Installed on 2022-05-01 (14 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=19e3ad11-d1ce-49ce-8809-80fc68612eb3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 065C71 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrX02:cvnDellInc.:ct10:cvr:sku0798: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.product.sku: 0798 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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/mutter/+bug/1973467/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003237] Re: Backlight stays on with black screen when monitor should be sleeping
*** This bug is a duplicate of bug 1971434 *** https://bugs.launchpad.net/bugs/1971434 ** This bug is no longer a duplicate of bug 1973467 [Wayland] Backlight stays on with black screen when monitor should be sleeping ** This bug has been marked a duplicate of bug 1971434 Display powersave only blanks, but does not turn off -- 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/2003237 Title: Backlight stays on with black screen when monitor should be sleeping Status in mutter package in Ubuntu: Confirmed Bug description: My Screen Blank setting is set to 15 minutes. My Lock Screen settings are also set to automatically lock the system after the blank screen timeout is reached. After 15 minutes Ubuntu does lock me out, but the monitor does not power off as it's supposed to - the screen is simply black. Please see the attached video. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 18 23:48:13 2023 DistUpgraded: 2022-06-02 20:38:07,324 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Radeon RX 570 Pulse 4GB [1da2:e353] InstallationDate: Installed on 2018-03-17 (1768 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=19f4e829-52cc-4c6f-8221-24750af577f9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-06-02 (230 days ago) dmi.bios.date: 05/29/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4211 dmi.board.asset.tag: Default string dmi.board.name: H110M-D dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4211:bd05/29/2019:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-D:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003237/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007268] Re: Backlight does not turn off during screen blanking
*** This bug is a duplicate of bug 1971434 *** https://bugs.launchpad.net/bugs/1971434 ** This bug is no longer a duplicate of bug 1973467 [Wayland] Backlight stays on with black screen when monitor should be sleeping ** This bug has been marked a duplicate of bug 1971434 Display powersave only blanks, but does not turn off -- 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/2007268 Title: Backlight does not turn off during screen blanking Status in mutter package in Ubuntu: Incomplete Bug description: In the 2022/2023 energy crisis era, this shall not happen. But... I haven't found solution other than "switch to X", which is not an options with my scaling settings for both 4K screens I'm using. On idle when the system blanks screen backlight remains on, wasting energy and burning LEDs in my screens. Please provide solution that would let Gnome set DPMS properly and actually send screens to proper sleep when OS goes idle (enables screen saver). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libwayland-bin 1.20.0-1ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 14 11:59:59 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: v4l2loopback/0.12.5, 5.15.0-58-generic, x86_64: installed v4l2loopback/0.12.5, 5.15.0-60-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [1002:1681] (rev d1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2023-01-04 (40 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 21CKCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_zrhf1w@/vmlinuz-5.15.0-58-generic root=ZFS=rpool/ROOT/ubuntu_zrhf1w ro quiet splash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: wayland UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2022 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET62W (1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CKCTO1WW dmi.board.vendor: LENOVO dmi.board.version: ThinkPad dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrR23ET62W(1.32):bd11/11/2022:br1.32:efr1.23:svnLENOVO:pn21CKCTO1WW:pvrThinkPadP16sGen1:rvnLENOVO:rn21CKCTO1WW:rvrThinkPad:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CK_BU_Think_FM_ThinkPadP16sGen1: dmi.product.family: ThinkPad P16s Gen 1 dmi.product.name: 21CKCTO1WW dmi.product.sku: LENOVO_MT_21CK_BU_Think_FM_ThinkPad P16s Gen 1 dmi.product.version: ThinkPad P16s Gen 1 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2007268/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034664] Re: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
It was blocked waiting on bug 2038783 verification but is unblocked now. -- 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/2034664 Title: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Status in gnome-shell-extension-tiling-assistant package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-tiling-assistant source package in Mantic: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Mantic: Fix Committed Bug description: [ Impact ] The gnome-shell 45.rc log fills with: Meta.Rectangle is deprecated, use Mtk.Rectangle instead [ Test case ] Run ubuntu with ubuntu extensions enabled (only). journalctl /usr/bin/gnome-shell should not contain any reference to Meta.Rectangle deprecation [ Regression potential ] Introspected types are not defined and so extensions may try to use undefined code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2034664/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872594] Re: Ubuntu logo shifts vertically when the login screen appears
** Tags added: jammy 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/1872594 Title: Ubuntu logo shifts vertically when the login screen appears Status in gnome-shell package in Ubuntu: Triaged Status in plymouth package in Ubuntu: Triaged Bug description: Ubuntu logo shifts upward about 1px when the purple login screen appears. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872594/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2024377] Re: Adsys can't fetch GPOs
This bug was fixed in the package adsys - 0.13.2
---
adsys (0.13.2) noble; urgency=medium
[ Denison Barbosa ]
[ Didier Roche ]
[ Gabriel Nagy ]
[ Jean-Baptiste Lallement ]
* Ensure GPO URLs contain the FQDN of the domain controller (LP: #2024377)
* Add runtime dependency on nfs-common (LP: #2044112)
* Documentation changes:
- Switch to Read the Docs for project documentation
- Generate documentation from policy definitions
- Fix installation path of adwatchd
* CI and quality of life changes not impacting package functionality:
- Bump go version to 1.21.4
- Fix docker stop behavior on integration tests
- Add e2e tests provisioning workflow
- Reduce the amount of workflows to be run
- Remove scopes from dependabot config
* Update dependencies to latest:
- github.com/charmbracelet/lipgloss
- github.com/fatih/color
- github.com/fsnotify/fsnotify
- github.com/golangci/golangci-lint
- github.com/google/uuid
- github.com/maruel/natural
- github.com/pkg/sftp
- github.com/spf13/cobra
- github.com/spf13/viper
- golang.org/x/crypto
- golang.org/x/net
- golang.org/x/sync
- golang.org/x/sys
- golang.org/x/text
- google.golang.org/grpc
-- Gabriel Nagy Tue, 21 Nov 2023 12:53:10
+0200
** Changed in: adsys (Ubuntu)
Status: Triaged => Fix Released
--
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/2024377
Title:
Adsys can't fetch GPOs
Status in adsys package in Ubuntu:
Fix Released
Bug description:
Bad, maybe no understandable english ahead.
Can't find anything related to this on Github, Canonical Forums,
Reddit or StackOverflow.
On Ubuntu 22.04, I've followed the Wiki tutorial and verified all
steps on Integration Ubuntu Desktop whitepaper. Currently using SSSD
backend, I can log with Active Directory users however when adsys is
installed I can't fetch GPOs. In this version the error is:
ERROR Error from server: error while updating policy: can't get
policies for "ubuntu": can't download all gpos and assets: one or more
error while fetching GPOs and assets: can't download "ubuntuRoot":
can't check if ubuntuRoot needs refreshing: no GPT.INI file: cannot
open
smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}/GPT.INI:
invalid argument
It happens when using "adsysctl update -m" or "adsysctl update
usern...@domain.com.br /tmp/krb5c_getentId_randomdnumber" and just
"adsysctl update" too.
I've upgrade the machine to 22.10 and the error changed to:
ERROR Error from server: error while updating policy: can't get policies for
"ubuntu": failed to retrieve the list of GPO (exited with 1): exit status 1
Failed to bind - LDAP client internal error: NT_STATUS_INVALID_PARAMETER
Failed to connect to 'ldap://addc01.domain.com.br' with backend 'ldap': LDAP
client internal error: NT_STATUS_INVALID_PARAMETER
Failed to open session: (1, 'LDAP client internal error:
NT_STATUS_INVALID_PARAMETER').
After upgrade to 23.04 the error persist same as the above.
Full info 22.04 (- verbose):
INFO No configuration file: Config File "adsys" Not Found in "[/home/jzprates
/root /etc /usr/sbin]".
We will only use the defaults, env variables or flags.
DEBUG Connecting as [[2504:109556]]
DEBUG New request /service/UpdatePolicy
DEBUG Requesting with parameters: IsComputer: true, All: false, Target:
ubuntu, Krb5Cc:
DEBUG NormalizeTargetName for "ubuntu", type "computer"
DEBUG Check if grpc request peer is authorized
DEBUG Authorized as being administrator
DEBUG GetPolicies for "ubuntu", type "computer"
DEBUG Getting gpo list with arguments: "--objectclass computer
ldap://addc01.domain.com.br ubuntu"
DEBUG GPO "ubuntuRoot" for "ubuntu" available at
"smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}"
DEBUG Analyzing "assets"
DEBUG Analyzing "ubuntuRoot"
INFO No assets directory with GPT.INI file found on AD, skipping assets
download
ERROR Error from server: error while updating policy: can't get policies for
"ubuntu": can't download all gpos and assets: one or more error while fetching
GPOs and assets: can't download "ubuntuRoot": can't check if ubuntuRoot needs
refreshing: no GPT.INI file: cannot open
smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}/GPT.INI:
invalid argument
Full info 23.04 (- verbose):
INFO No configuration file: Config File "adsys" Not Found in "[/home/jzprates
/root /etc /usr/sbin]".
DEBUG Connecting as [[58811:006019]]
DEBUG New request /service/UpdatePolicy
DEBUG Requesting with parameters: IsComputer: true, All: false, Target:
ubuntu, Krb5Cc:
DEBUG NormalizeTargetName for "ubuntu", type "computer"
DEBUG Check if grpc request peer is a
[Desktop-packages] [Bug 2044112] Re: Add dependency on nfs-common
This bug was fixed in the package adsys - 0.13.2 --- adsys (0.13.2) noble; urgency=medium [ Denison Barbosa ] [ Didier Roche ] [ Gabriel Nagy ] [ Jean-Baptiste Lallement ] * Ensure GPO URLs contain the FQDN of the domain controller (LP: #2024377) * Add runtime dependency on nfs-common (LP: #2044112) * Documentation changes: - Switch to Read the Docs for project documentation - Generate documentation from policy definitions - Fix installation path of adwatchd * CI and quality of life changes not impacting package functionality: - Bump go version to 1.21.4 - Fix docker stop behavior on integration tests - Add e2e tests provisioning workflow - Reduce the amount of workflows to be run - Remove scopes from dependabot config * Update dependencies to latest: - github.com/charmbracelet/lipgloss - github.com/fatih/color - github.com/fsnotify/fsnotify - github.com/golangci/golangci-lint - github.com/google/uuid - github.com/maruel/natural - github.com/pkg/sftp - github.com/spf13/cobra - github.com/spf13/viper - golang.org/x/crypto - golang.org/x/net - golang.org/x/sync - golang.org/x/sys - golang.org/x/text - google.golang.org/grpc -- Gabriel Nagy Tue, 21 Nov 2023 12:53:10 +0200 ** Changed in: adsys (Ubuntu) Status: Fix Committed => Fix Released -- 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 Released 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 2044300] [NEW] Please merge zeitgeist 1.0.4-5 (universe) from Debian unstable (main)
Public bug reported: Please merge zeitgeist 1.0.4-5 (universe) from Debian unstable (main) Explanation of the Ubuntu delta: ** Affects: zeitgeist (Ubuntu) Importance: Undecided Assignee: Sudip Mukherjee (sudipmuk) Status: In Progress ** Changed in: zeitgeist (Ubuntu) Assignee: (unassigned) => Sudip Mukherjee (sudipmuk) ** Changed in: zeitgeist (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/2044300 Title: Please merge zeitgeist 1.0.4-5 (universe) from Debian unstable (main) Status in zeitgeist package in Ubuntu: In Progress Bug description: Please merge zeitgeist 1.0.4-5 (universe) from Debian unstable (main) Explanation of the Ubuntu delta: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/2044300/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034664] Re: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
Hi, should gnome-shell-extension-ubuntu-dock 87ubuntu2 have already migrated from mantic-proposed? I'm assuming this process is automatic. Thanks. -- 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/2034664 Title: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Status in gnome-shell-extension-tiling-assistant package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-tiling-assistant source package in Mantic: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Mantic: Fix Committed Bug description: [ Impact ] The gnome-shell 45.rc log fills with: Meta.Rectangle is deprecated, use Mtk.Rectangle instead [ Test case ] Run ubuntu with ubuntu extensions enabled (only). journalctl /usr/bin/gnome-shell should not contain any reference to Meta.Rectangle deprecation [ Regression potential ] Introspected types are not defined and so extensions may try to use undefined code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2034664/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
I successfully completed the test case with gnome-shell-extension- ubuntu-dock 87ubuntu2 on Ubuntu 23.10. ** Tags removed: verification-needed verification-needed-mantic ** Tags added: verification-done verification-done-mantic -- 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 1 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 2007702] Re: [SRU] Deb version numbering is misleading
Thanks, Nathan. Would you mind filing the SRU paperwork as per the template at https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template ? I am unsure if this would be suitable for an SRU, but that's for the SRU team to assess and decide. Moreover, I see that you are using the same version for all the proposed patches. If you check item 4.1 in https://wiki.ubuntu.com/StableReleaseUpdates#Procedure, it states that, for SRUs, the version number should not conflict with any later and future version in other Ubuntu releases. Could you please fix the version numbers for each release? Check the versions in jammy and focal for an example of how this could be done. -- 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/2007702 Title: [SRU] Deb version numbering is misleading Status in chromium-browser package in Ubuntu: Fix Released Status in chromium-browser source package in Focal: New Status in chromium-browser source package in Jammy: New Status in chromium-browser source package in Lunar: New Status in chromium-browser source package in Mantic: New Bug description: For Ubuntu >= Focal the transitional debs are frozen at the version number 1:85... This might make one think[1][2] that it will install a critically outdated Chromium while it does not, because it installs the snap. [Test plan] Install the package and confirm the version change with e.g. dpkg -l | grep '^ii *chromium-browser *2:1snap1-0ubuntu1' [Regression potential] If the version were incorrectly constructed the deb build could fail. [1] https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/702591 [2] https://askubuntu.com/q/1420925 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007702/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1978368] Re: package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1
** Changed in: firefox (Ubuntu) Status: Confirmed => In Progress -- 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/1978368 Title: package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 Status in snapd: New Status in firefox package in Ubuntu: In Progress Bug description: Upgrading to 22.04 from 20.04 ProblemType: Package DistroRelease: Ubuntu 22.04 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat Jun 11 11:34:34 2022 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-12-07 (550 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.5 Snap: firefox 101.0.1-1 (stable) Snap.Changes: ID Status Spawn Ready Summary 63 Error 2022-06-11T11:33:42+08:00 2022-06-11T11:34:34+08:00 Install "firefox" snap 64 Done2022-06-11T11:37:18+08:00 2022-06-11T11:37:23+08:00 Install "firefox" snap Title: package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1978368/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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 handler file:///foo/bar/baz echo $? - An error should be shown and the return code should be 15 + An error should be shown and the return code should be 1 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 -- 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 1 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 2044270] Re: Wi-Fi connection lost and reestablished every 3 minutes after upgrade from Lubuntu 22.10 to 23.10
Now over an hour after turning my laptop on network interruptions have ceased. Seems like the cause of the problem is in my laptop itself. -- 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/2044270 Title: Wi-Fi connection lost and reestablished every 3 minutes after upgrade from Lubuntu 22.10 to 23.10 Status in network-manager package in Ubuntu: Triaged Bug description: In Lubuntu 22.10 (Kinetic) Wi-Fi connection on my laptop was stable. A couple of days ago I upgraded Lubuntu (installed it afresh) to 23.10 (Mantic Minotaur). Now the connection is lost every couple of minutes and reestablished again in 3-20 seconds automatically. The same issue with two different internet providers (two different routers). Network manager version as told by command "apt-cache policy network- manager" is 1.44.2-1ubuntu1.2. My laptop model is Digma CITI E401. sudo lshw -class network *-network description: Wireless interface physical id: e bus info: mmc@2:0001:1 logical name: wlan0 serial: 80:5e:4f:02:97:70 capabilities: ethernet physical wireless configuration: broadcast=yes driver=rtl8723bs driverversion=6.5.0-13-generic ip=192.168.0.13 multicast=yes wireless=IEEE 802.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044270/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2041496] Re: btmgmt --index broken in Mantic
This bug was fixed in the package bluez - 5.70-0ubuntu2 --- bluez (5.70-0ubuntu2) noble; urgency=medium * Fix btmgmt --index option (thanks to Juerg Haefliger) (LP: #2041496) -- Dimitri John Ledkov Tue, 21 Nov 2023 11:08:37 + ** Changed in: bluez (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2041496 Title: btmgmt --index broken in Mantic Status in Bluez Utilities: Unknown Status in bluez package in Ubuntu: Fix Released Bug description: On Mantic: $ btmgmt --index 1 info Unable to open 1: No such file or directory (2) Index list with 1 item hci0: Primary controller addr B8:27:EB:CB:F8:8D version 9 manufacturer 305 class 0x6c supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr le advertising secure-conn debug-keys privacy configuration static-addr phy-configuration current settings: powered ssp br/edr le secure-conn name rpi-5b-rev1d0-f88b short name hci0: Configuration options supported options: public-address missing options: Note the error 'Unable to open...' above. The machine has only a single hci so index 1 is invalid. The correct result should be: $ btmgmt --index 1 info Reading hci1 info failed with status 0x11 (Invalid Index) To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/2041496/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971434] Re: Display powersave only blanks, but does not turn off
The AtomicKms workaround did it for me. I'm on Manjaro gnome 45. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1971434 Title: Display powersave only blanks, but does not turn off Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Recently upgraded to Ubuntu 22.04, and it seems like the power-saving feature in Gnome 42 does not actually turn off the screen(s) after X minutes, but just blanks them. When I manually run `xset dpms force off`, they do properly turn off and go to powersave mode. 1) Description: Ubuntu 22.04 LTS Release: 22.04 2) gnome-settings-daemon: Installed: 42.1-1ubuntu2 Candidate: 42.1-1ubuntu2 3) In Settings -> Power -> Screen Blank, set the inactivity period to 5 minutes. After 5 minutes, the screens should turn off. 4) Screens go black, but remain active and consume (too much) power. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-07-04 (667 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: gnome-settings-daemon 42.1-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-30 (3 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers video wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044276] [NEW] libsane fails to load
Public bug reported: Since Oct'23 while running gscan2pdf, libsane fails to load automatically. The program fails with the following error message: Can't load '/usr/lib/x86_64-linux- gnu/perl5/5.30/auto/Image/Sane/Sane.so' for module Image::Sane: /usr/lib/x86_64-linux-gnu/libsane.so.1: undefined symbol: libusb_set_option at /usr/share/perl/5.30/XSLoader.pm line 93. I can run the program by setting the path from command line as LD_LIBRARY_PATH=/lib/x86_64-linux-gnu/ gscan2pdf Looks like the LD_LIBRARY_PATH variable is not set correctly in some recent upgrade. I am using Kubuntu 20.04 ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/2044276 Title: libsane fails to load Status in sane-backends package in Ubuntu: New Bug description: Since Oct'23 while running gscan2pdf, libsane fails to load automatically. The program fails with the following error message: Can't load '/usr/lib/x86_64-linux- gnu/perl5/5.30/auto/Image/Sane/Sane.so' for module Image::Sane: /usr/lib/x86_64-linux-gnu/libsane.so.1: undefined symbol: libusb_set_option at /usr/share/perl/5.30/XSLoader.pm line 93. I can run the program by setting the path from command line as LD_LIBRARY_PATH=/lib/x86_64-linux-gnu/ gscan2pdf Looks like the LD_LIBRARY_PATH variable is not set correctly in some recent upgrade. I am using Kubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/2044276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044270] Re: Wi-Fi connection lost and reestablished every 3 minutes after upgrade from Lubuntu 22.10 to 23.10
Yes. See the attachment. ** Attachment added: "network-manager.log" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044270/+attachment/5722324/+files/network-manager.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2044270 Title: Wi-Fi connection lost and reestablished every 3 minutes after upgrade from Lubuntu 22.10 to 23.10 Status in network-manager package in Ubuntu: Triaged Bug description: In Lubuntu 22.10 (Kinetic) Wi-Fi connection on my laptop was stable. A couple of days ago I upgraded Lubuntu (installed it afresh) to 23.10 (Mantic Minotaur). Now the connection is lost every couple of minutes and reestablished again in 3-20 seconds automatically. The same issue with two different internet providers (two different routers). Network manager version as told by command "apt-cache policy network- manager" is 1.44.2-1ubuntu1.2. My laptop model is Digma CITI E401. sudo lshw -class network *-network description: Wireless interface physical id: e bus info: mmc@2:0001:1 logical name: wlan0 serial: 80:5e:4f:02:97:70 capabilities: ethernet physical wireless configuration: broadcast=yes driver=rtl8723bs driverversion=6.5.0-13-generic ip=192.168.0.13 multicast=yes wireless=IEEE 802.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044270/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044270] Re: Wi-Fi connection lost and reestablished every 3 minutes after upgrade from Lubuntu 22.10 to 23.10
In Lubuntu 22.10 there was another issue with Wi-Fi connection: if it had not been established at boot, there was no way to turn it on, you had to reboot the laptop. I don't know if it was a bug of Lubuntu or a defect of the laptop. -- 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/2044270 Title: Wi-Fi connection lost and reestablished every 3 minutes after upgrade from Lubuntu 22.10 to 23.10 Status in network-manager package in Ubuntu: Triaged Bug description: In Lubuntu 22.10 (Kinetic) Wi-Fi connection on my laptop was stable. A couple of days ago I upgraded Lubuntu (installed it afresh) to 23.10 (Mantic Minotaur). Now the connection is lost every couple of minutes and reestablished again in 3-20 seconds automatically. The same issue with two different internet providers (two different routers). Network manager version as told by command "apt-cache policy network- manager" is 1.44.2-1ubuntu1.2. My laptop model is Digma CITI E401. sudo lshw -class network *-network description: Wireless interface physical id: e bus info: mmc@2:0001:1 logical name: wlan0 serial: 80:5e:4f:02:97:70 capabilities: ethernet physical wireless configuration: broadcast=yes driver=rtl8723bs driverversion=6.5.0-13-generic ip=192.168.0.13 multicast=yes wireless=IEEE 802.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044270/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044270] Re: Wi-Fi connection lost and reestablished every 3 minutes after upgrade from Lubuntu 22.10 to 23.10
Hello, thanks for your bug report. Can you collect and attach the Network Manager's systemd journal? You can get it with "journalctl -u NetworkManager > network-manager.log" It will help us to identify the problem. Thank you! ** Changed in: network-manager (Ubuntu) Status: New => Triaged -- 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/2044270 Title: Wi-Fi connection lost and reestablished every 3 minutes after upgrade from Lubuntu 22.10 to 23.10 Status in network-manager package in Ubuntu: Triaged Bug description: In Lubuntu 22.10 (Kinetic) Wi-Fi connection on my laptop was stable. A couple of days ago I upgraded Lubuntu (installed it afresh) to 23.10 (Mantic Minotaur). Now the connection is lost every couple of minutes and reestablished again in 3-20 seconds automatically. The same issue with two different internet providers (two different routers). Network manager version as told by command "apt-cache policy network- manager" is 1.44.2-1ubuntu1.2. My laptop model is Digma CITI E401. sudo lshw -class network *-network description: Wireless interface physical id: e bus info: mmc@2:0001:1 logical name: wlan0 serial: 80:5e:4f:02:97:70 capabilities: ethernet physical wireless configuration: broadcast=yes driver=rtl8723bs driverversion=6.5.0-13-generic ip=192.168.0.13 multicast=yes wireless=IEEE 802.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044270/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044270] [NEW] Wi-Fi connection lost and reestablished every 3 minutes after upgrade from Lubuntu 22.10 to 23.10
Public bug reported: In Lubuntu 22.10 (Kinetic) Wi-Fi connection on my laptop was stable. A couple of days ago I upgraded Lubuntu (installed it afresh) to 23.10 (Mantic Minotaur). Now the connection is lost every couple of minutes and reestablished again in 3-20 seconds automatically. The same issue with two different internet providers (two different routers). Network manager version as told by command "apt-cache policy network- manager" is 1.44.2-1ubuntu1.2. My laptop model is Digma CITI E401. sudo lshw -class network *-network description: Wireless interface physical id: e bus info: mmc@2:0001:1 logical name: wlan0 serial: 80:5e:4f:02:97:70 capabilities: ethernet physical wireless configuration: broadcast=yes driver=rtl8723bs driverversion=6.5.0-13-generic ip=192.168.0.13 multicast=yes wireless=IEEE 802.11 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: connection wi-fi ** Attachment added: "sudo lshw -class network" https://bugs.launchpad.net/bugs/2044270/+attachment/5722315/+files/digma2023-11-22_17-16.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/2044270 Title: Wi-Fi connection lost and reestablished every 3 minutes after upgrade from Lubuntu 22.10 to 23.10 Status in network-manager package in Ubuntu: New Bug description: In Lubuntu 22.10 (Kinetic) Wi-Fi connection on my laptop was stable. A couple of days ago I upgraded Lubuntu (installed it afresh) to 23.10 (Mantic Minotaur). Now the connection is lost every couple of minutes and reestablished again in 3-20 seconds automatically. The same issue with two different internet providers (two different routers). Network manager version as told by command "apt-cache policy network- manager" is 1.44.2-1ubuntu1.2. My laptop model is Digma CITI E401. sudo lshw -class network *-network description: Wireless interface physical id: e bus info: mmc@2:0001:1 logical name: wlan0 serial: 80:5e:4f:02:97:70 capabilities: ethernet physical wireless configuration: broadcast=yes driver=rtl8723bs driverversion=6.5.0-13-generic ip=192.168.0.13 multicast=yes wireless=IEEE 802.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044270/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043015] Re: Update gnome-shell to 45.1
I successfully completed all 3 test cases with gnome-shell 45.1-0ubuntu1 on Ubuntu 23.10. To test the terminus GNOME Shell extension, I used terminus 2.3.1-1ubuntu2 from mantic-proposed. ** Tags removed: verification-needed verification-needed-mantic ** Tags added: verification-done verification-done-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/2043015 Title: Update gnome-shell to 45.1 Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Mantic: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 45 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/45.1/NEWS Test Case - Complete all the non-optional test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- gnome-shell provides the GNOME version number for the Settings app About page, as of Ubuntu 22.10 (in earlier Ubuntu releases, this was provided by gnome-desktop/gnome-desktop3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2043015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044019] Re: [SRU] libreoffice 7.6.3 for mantic
** Description changed: [Impact] * LibreOffice 7.6.3 is in its third bugfix release of the 7.6 line: https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.3_release * Version 7.6.2 is currently released in mantic. For a list of fixed bugs compared to 7.6.2 see the list of bugs fixed in the release candidates of 7.6.3 (that's a total of 115+ bugs): https://wiki.documentfoundation.org/Releases/7.6.3/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.6.3/RC2#List_of_fixed_bugs 7.6.3 RC2 is identical to the 7.6.3 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_76/1459/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/15389862/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-libreoffice-libreoffice-prereleases/mantic/amd64/libr/libreoffice/20231122_055508_b6ab7@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-libreoffice-libreoffice-prereleases/mantic/arm64/libr/libreoffice/20231122_065528_077f4@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-libreoffice-libreoffice-prereleases/mantic/armhf/libr/libreoffice/20231122_045051_d78ff@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-libreoffice-libreoffice-prereleases/mantic/ppc64el/libr/libreoffice/20231122_033828_5af8c@/log.gz * [riscv64] not available - * [s390x] ... + * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-libreoffice-libreoffice-prereleases/mantic/s390x/libr/libreoffice/20231122_124339_d7006@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 115+ bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. -- 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/2044019 Title: [SRU] libreoffice 7.6.3 for mantic Status in libreoffice package in Ubuntu: New Status in libreoffice source package in Mantic: In Progress Bug description: [Impact] * LibreOffice 7.6.3 is in its third bugfix release of the 7.6 line: https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.3_release * Version 7.6.2 is currently released in mantic. For a list of fixed bugs compared to 7.6.2 see the list of bugs fixed in the release candidates of 7.6.3 (that's a total of 115+ bugs): https://wiki.documentfoundation.org/Releases/7.6.3/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.6.3/RC2#List_of_fixed_bugs 7.6.3 RC2 is identical to the 7.6.3 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_76/1459/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
[Desktop-packages] [Bug 2033590] Re: random crashes of gnome-characters
Package: gnome-characters Architecture: amd64 Version: 41.0-4 I would like to add that the error message is also printed to `STDOUT` when the application is run in a terminal. `gnome-characters` appears to be very unstable under Ubuntu 22.04; I have never managed to have it running more than a couple of minutes. Sometimes it will crash with a segmentation fault without printing anything about `GSlice`. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-characters in Ubuntu. https://bugs.launchpad.net/bugs/2033590 Title: random crashes of gnome-characters Status in gnome-characters package in Ubuntu: Confirmed Bug description: Usually just a one-line record in syslog: Aug 30 19:10:45 COLOSSUS org.gnome.Characters[11012]: ***MEMORY- ERROR***: org.gnome.Characters[11012]: GSlice: assertion failed: sinfo->n_allocated > 0 Aug 30 19:12:38 COLOSSUS org.gnome.Characters[11134]: ***MEMORY- ERROR***: org.gnome.Characters[11134]: GSlice: assertion failed: sinfo->n_allocated > 0 Aug 30 19:17:29 COLOSSUS kernel: [ 2840.611031] pool- org.gnome.[11513]: segfault at 1c8 ip 7fd1854d1ae3 sp 7fd1794ca9d8 error 6 in libglib-2.0.so.0.7200.4[7fd18547a000+8f000] Aug 30 22:44:26 COLOSSUS kernel: [15257.581416] gnome- character[18769]: segfault at 18 ip 7fb24db9eae3 sp 7ffc99c29ca8 error 6 in libglib-2.0.so.0.7200.4[7fb24db47000+8f000] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-characters 41.0-4 ProcVersionSignature: Ubuntu 5.15.0-82.91-generic 5.15.111 Uname: Linux 5.15.0-82-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Aug 30 22:52:57 2023 InstallationDate: Installed on 2020-05-03 (1215 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-characters UpgradeStatus: Upgraded to jammy on 2022-07-15 (412 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-characters/+bug/2033590/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016933] Re: X-Plane 11 doesn't start on Wayland if offloaded to the discrete Nvidia GPU
The bug certainly is not happening in X-Plane 12 Demo. Does it still happen for you? Even if it does the original problem seems like either an Xwayland bug or an X-Plane bug. Even if it was an Xwayland bug it doesn't seem to affect other Xwayland apps. So overall I think the Importance is Low. ** Changed in: xwayland (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2016933 Title: X-Plane 11 doesn't start on Wayland if offloaded to the discrete Nvidia GPU Status in xwayland package in Ubuntu: Incomplete Bug description: On Wayland only, offloading works for `glxinfo` but cannot run 3D app like X-Plane 11: $ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia glxinfo | grep "OpenGL vendor string" OpenGL vendor string: NVIDIA Corporation $ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia ./X-Plane\ 11/X-Plane-x86_64 Whoah -- no matter how hard I tried, I failed to get a GLX visual. Something's seriously wonky on your machine. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nvidia-driver-530 (not installed) ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 19 04:30:34 2023 InstallationDate: Installed on 2023-01-04 (104 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nvidia-graphics-drivers-530 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2016933/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2024661] Re: Unable to configure Wireguard connection at NetworkManager interface
If I understand the bug description correctly, I don't think the problem is related to netplan. I am experiencing the same issue in Fedora 39 KDE. After editing WireGuard peer settings using Plasma's network settings and pressing 'OK', the 'Apply' button remains grayed out and I am unable to save settings. After closing and re-opening network settings, my changes are gone. -- 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/2024661 Title: Unable to configure Wireguard connection at NetworkManager interface Status in netplan.io package in Ubuntu: In Progress Status in network-manager package in Ubuntu: Invalid Bug description: Repro steps: 1) Open NetworkManager GUI. 2) Click "Add new Connection" and select "Wireguard" connection type. 3) Then you have to configure new connection. Basic configuration looks like that: a) Write down connection name, b) Write down local private key, c) Create new peer and populate peer's parameters: public key of the peer, allowed IPs (i.e. 0.0.0.0/0), peer's IP address and port. 4) Click "OK" and "Save". 5) Open "Peers" again. Ensure that settings were not stored. All fields are empty. Found in Kubuntu flavor version 23.10 (development), Plasma Network Manager interface. netplan.io 0.106.1-2 network-manager 1.42.4-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2024661/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007702] Re: Deb version numbering is misleading
** Also affects: chromium-browser (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: chromium-browser (Ubuntu Lunar) Importance: Undecided => Low ** Changed in: chromium-browser (Ubuntu Lunar) Assignee: (unassigned) => Nathan Teodosio (nteodosio) ** Patch added: "lunar.diff" https://bugs.launchpad.net/bugs/2007702/+attachment/5722269/+files/lunar.diff ** Patch added: "mantic.diff" https://bugs.launchpad.net/bugs/2007702/+attachment/5722270/+files/mantic.diff ** Patch added: "jammy.diff" https://bugs.launchpad.net/bugs/2007702/+attachment/5722271/+files/jammy.diff ** Patch added: "focal.diff" https://bugs.launchpad.net/bugs/2007702/+attachment/5722272/+files/focal.diff ** Description changed: For Ubuntu >= Focal the transitional debs are frozen at the version number 1:85... This might make one think[1][2] that it will install a critically outdated Chromium while it does not, because it installs the snap. + [Test plan] + + Install the package and confirm the version change with e.g. + + dpkg -l | grep '^ii *chromium-browser *2:1snap1-0ubuntu1' + + [Regression potential] + + If the version were incorrectly constructed the deb build could fail. + [1] https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/702591 [2] https://askubuntu.com/q/1420925 ** Summary changed: - Deb version numbering is misleading + [SRU] Deb version numbering is misleading -- 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/2007702 Title: [SRU] Deb version numbering is misleading Status in chromium-browser package in Ubuntu: Fix Released Status in chromium-browser source package in Focal: New Status in chromium-browser source package in Jammy: New Status in chromium-browser source package in Lunar: New Status in chromium-browser source package in Mantic: New Bug description: For Ubuntu >= Focal the transitional debs are frozen at the version number 1:85... This might make one think[1][2] that it will install a critically outdated Chromium while it does not, because it installs the snap. [Test plan] Install the package and confirm the version change with e.g. dpkg -l | grep '^ii *chromium-browser *2:1snap1-0ubuntu1' [Regression potential] If the version were incorrectly constructed the deb build could fail. [1] https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/702591 [2] https://askubuntu.com/q/1420925 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007702/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973467] Re: [Wayland] Backlight stays on with black screen when monitor should be sleeping
** Changed in: mutter (Ubuntu) Importance: Undecided => 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/1973467 Title: [Wayland] Backlight stays on with black screen when monitor should be sleeping Status in mutter package in Ubuntu: Confirmed Bug description: In Power -> Power Saving Options -> Screen Blank - the option states that the screen will be turned off after some period, which is what I'd expect from a sleep mode. I have a hybrid system. I have disabled the internal display and I use the external connected via HDMI (and I believe it is connected to the NVIDIA GPU). When the screen goes blank the external monitor is not turned off really. It goes blank but it is still turned on and glows, so no power is saved. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 15 19:16:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:0798] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0798] InstallationDate: Installed on 2022-05-01 (14 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=19e3ad11-d1ce-49ce-8809-80fc68612eb3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 065C71 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrX02:cvnDellInc.:ct10:cvr:sku0798: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.product.sku: 0798 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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/mutter/+bug/1973467/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016933] Re: X-Plane 11 doesn't start on Wayland if offloaded to the discrete Nvidia GPU
Ironically the X-Plane 12 Demo installer refuses to run on my primary Intel GPU. It only runs if I force it onto the secondary Nvidia GPU :) ** Changed in: xwayland (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2016933 Title: X-Plane 11 doesn't start on Wayland if offloaded to the discrete Nvidia GPU Status in xwayland package in Ubuntu: New Bug description: On Wayland only, offloading works for `glxinfo` but cannot run 3D app like X-Plane 11: $ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia glxinfo | grep "OpenGL vendor string" OpenGL vendor string: NVIDIA Corporation $ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia ./X-Plane\ 11/X-Plane-x86_64 Whoah -- no matter how hard I tried, I failed to get a GLX visual. Something's seriously wonky on your machine. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nvidia-driver-530 (not installed) ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 19 04:30:34 2023 InstallationDate: Installed on 2023-01-04 (104 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nvidia-graphics-drivers-530 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2016933/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044019] Re: [SRU] libreoffice 7.6.3 for mantic
** Description changed: [Impact] * LibreOffice 7.6.3 is in its third bugfix release of the 7.6 line: https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.3_release * Version 7.6.2 is currently released in mantic. For a list of fixed bugs compared to 7.6.2 see the list of bugs fixed in the release candidates of 7.6.3 (that's a total of 115+ bugs): https://wiki.documentfoundation.org/Releases/7.6.3/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.6.3/RC2#List_of_fixed_bugs 7.6.3 RC2 is identical to the 7.6.3 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_76/1459/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/15389862/+listing-archive-extra - * [amd64] ... - * [arm64] ... - * [armhf] ... - * [ppc64el] ... + * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-libreoffice-libreoffice-prereleases/mantic/amd64/libr/libreoffice/20231122_055508_b6ab7@/log.gz + * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-libreoffice-libreoffice-prereleases/mantic/arm64/libr/libreoffice/20231122_065528_077f4@/log.gz + * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-libreoffice-libreoffice-prereleases/mantic/armhf/libr/libreoffice/20231122_045051_d78ff@/log.gz + * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-libreoffice-libreoffice-prereleases/mantic/ppc64el/libr/libreoffice/20231122_033828_5af8c@/log.gz * [riscv64] not available * [s390x] ... * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 115+ bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. -- 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/2044019 Title: [SRU] libreoffice 7.6.3 for mantic Status in libreoffice package in Ubuntu: New Status in libreoffice source package in Mantic: In Progress Bug description: [Impact] * LibreOffice 7.6.3 is in its third bugfix release of the 7.6 line: https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.3_release * Version 7.6.2 is currently released in mantic. For a list of fixed bugs compared to 7.6.2 see the list of bugs fixed in the release candidates of 7.6.3 (that's a total of 115+ bugs): https://wiki.documentfoundation.org/Releases/7.6.3/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.6.3/RC2#List_of_fixed_bugs 7.6.3 RC2 is identical to the 7.6.3 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_76/1459/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITest
[Desktop-packages] [Bug 2016933] Re: X-Plane 11 doesn't start on Wayland if offloaded to the discrete Nvidia GPU
** Tags added: hybrid multigpu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2016933 Title: X-Plane 11 doesn't start on Wayland if offloaded to the discrete Nvidia GPU Status in xwayland package in Ubuntu: New Bug description: On Wayland only, offloading works for `glxinfo` but cannot run 3D app like X-Plane 11: $ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia glxinfo | grep "OpenGL vendor string" OpenGL vendor string: NVIDIA Corporation $ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia ./X-Plane\ 11/X-Plane-x86_64 Whoah -- no matter how hard I tried, I failed to get a GLX visual. Something's seriously wonky on your machine. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nvidia-driver-530 (not installed) ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 19 04:30:34 2023 InstallationDate: Installed on 2023-01-04 (104 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nvidia-graphics-drivers-530 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2016933/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973467] Re: [Wayland] Backlight stays on with black screen when monitor should be sleeping
The problem persists with 23.04 and now with 23.10 as well from what I see. The only difference is that if I turn off the HDMI screen, the notebook screen can disable backlight over time. -- 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/1973467 Title: [Wayland] Backlight stays on with black screen when monitor should be sleeping Status in mutter package in Ubuntu: Confirmed Bug description: In Power -> Power Saving Options -> Screen Blank - the option states that the screen will be turned off after some period, which is what I'd expect from a sleep mode. I have a hybrid system. I have disabled the internal display and I use the external connected via HDMI (and I believe it is connected to the NVIDIA GPU). When the screen goes blank the external monitor is not turned off really. It goes blank but it is still turned on and glows, so no power is saved. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 15 19:16:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:0798] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0798] InstallationDate: Installed on 2022-05-01 (14 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=19e3ad11-d1ce-49ce-8809-80fc68612eb3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 065C71 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrX02:cvnDellInc.:ct10:cvr:sku0798: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.product.sku: 0798 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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/mutter/+bug/1973467/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015386] Re: NVIDIA quad-GPU system crashes starting Wayland session
I've set up a dual Nvidia system and cannot reproduce any crashes. The second Nvidia card fails to display anything if a monitor is attached but that's basically the same as bug 1978905, and the same experimental patch (https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3416) mostly fixes that. Do we care about this bug anymore? Is it reproducible by anyone? ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- 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/2015386 Title: NVIDIA quad-GPU system crashes starting Wayland session Status in mutter package in Ubuntu: Incomplete Bug description: When logged into a desktop session, I created a new user account and then tried to "switch to" it. A new gnome session started for that user (test1), but after a few seconds, gnome-shell appears to have crashed. This only seems to happen on the first attempt to "switch to" a new user. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu2: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu3: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..08.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..0e.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..0f.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.89.02 Wed Feb 1 23:23:25 UTC 2023 GCC version: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Apr 5 17:23:28 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches MachineType: NVIDIA DGX Station ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=88df95a6-4fd9-475a-8b59-ad14df1ada5a ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2018 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0406 dmi.board.asset.tag: Default string dmi.board.name: X99-E-10G WS dmi.board.vendor: EMPTY dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: EMPTY dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0406:bd08/27/2018:br5.11:svnNVIDIA:pnDGXStation:pvrSystemVersion:rvnEMPTY:rnX99-E-10GWS:rvrRev1.xx:cvnEMPTY:ct3:cvrDefaultstring:sku920-22587-2510-000: dmi.product.family: DGX dmi.product.name: DGX Station dmi.product.sku: 920-22587-2510-000 dmi.product.version: System Version dmi.sys.vendor: NVIDIA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2015386/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973467] Re: [Wayland] Backlight stays on with black screen when monitor should be sleeping
Removing the nvidia-wayland tag because the bug clearly isn't specific to Wayland on Nvidia. Also the duplicate bugs don't have Nvidia at all. ** Tags removed: nvidia-wayland -- 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/1973467 Title: [Wayland] Backlight stays on with black screen when monitor should be sleeping Status in mutter package in Ubuntu: Confirmed Bug description: In Power -> Power Saving Options -> Screen Blank - the option states that the screen will be turned off after some period, which is what I'd expect from a sleep mode. I have a hybrid system. I have disabled the internal display and I use the external connected via HDMI (and I believe it is connected to the NVIDIA GPU). When the screen goes blank the external monitor is not turned off really. It goes blank but it is still turned on and glows, so no power is saved. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 15 19:16:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:0798] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0798] InstallationDate: Installed on 2022-05-01 (14 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=19e3ad11-d1ce-49ce-8809-80fc68612eb3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 065C71 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrX02:cvnDellInc.:ct10:cvr:sku0798: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.product.sku: 0798 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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/mutter/+bug/1973467/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015386] Re: NVIDIA quad-GPU system crashes starting Wayland session
Setting to low because high-end Nvidia datacenter hardware should be using Xorg instead for the foreseeable future. ** Changed in: mutter (Ubuntu) Importance: Undecided => Low -- 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/2015386 Title: NVIDIA quad-GPU system crashes starting Wayland session Status in mutter package in Ubuntu: New Bug description: When logged into a desktop session, I created a new user account and then tried to "switch to" it. A new gnome session started for that user (test1), but after a few seconds, gnome-shell appears to have crashed. This only seems to happen on the first attempt to "switch to" a new user. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu2: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu3: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..08.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..0e.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..0f.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.89.02 Wed Feb 1 23:23:25 UTC 2023 GCC version: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Apr 5 17:23:28 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches MachineType: NVIDIA DGX Station ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=88df95a6-4fd9-475a-8b59-ad14df1ada5a ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2018 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0406 dmi.board.asset.tag: Default string dmi.board.name: X99-E-10G WS dmi.board.vendor: EMPTY dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: EMPTY dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0406:bd08/27/2018:br5.11:svnNVIDIA:pnDGXStation:pvrSystemVersion:rvnEMPTY:rnX99-E-10GWS:rvrRev1.xx:cvnEMPTY:ct3:cvrDefaultstring:sku920-22587-2510-000: dmi.product.family: DGX dmi.product.name: DGX Station dmi.product.sku: 920-22587-2510-000 dmi.product.version: System Version dmi.sys.vendor: NVIDIA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2015386/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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) Importance: Medium => Low -- 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
