[Desktop-packages] [Bug 2009687] Re: [lunar] Nvidia GPU unused but still powered
This might be related to a triple buffering issue: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441#note_1679803 If it is caused by triple buffering then you will find the issue is temporarily fixed in mutter 44~rc (which lacks triple buffering), and will return later in 44.0. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2009687 Title: [lunar] Nvidia GPU unused but still powered Status in GNOME Shell: Unknown Status in The Ubuntu Power Consumption Project: Triaged Status in gnome-shell package in Ubuntu: Triaged Bug description: Hi, Lenovo Legion 5 16" i7 12700H RTX 3070 Ti Nvidia 525 proprietary driver (official Ubuntu packages) Nvidia on-demand mode Ubuntu Wayland or Xorg sessions Ubuntu Lunar up to date I noticed a high power usage using powertop (or simply remaining time in g-c-c...). Nvidia driver seems offloaded but gpu power usage still shows ~ 9W -> 23W, random. uname -a Linux ** 6.1.0-16-generic #16-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 24 14:37:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux nvidia-smi Wed Mar 8 10:59:21 2023 +-+ | NVIDIA-SMI 525.85.05Driver Version: 525.85.05CUDA Version: 12.0 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===+==+==| | 0 NVIDIA GeForce ... Off | :01:00.0 Off | N/A | | N/A 34CP8 9W / 50W | 4MiB / 8192MiB | 0% Default | | | | N/A | +---+--+--+ +-+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |=| |0 N/A N/A 5445 G /usr/bin/gnome-shell3MiB | +-+ glxinfo -B name of display: :1 display: :1 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: Intel (0x8086) Device: Mesa Intel(R) Graphics (ADL GT2) (0x46a6) Version: 22.3.6 Accelerated: yes Video memory: 31821MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.6 Max compat profile version: 4.6 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) Graphics (ADL GT2) OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.3.6 OpenGL core profile shading language version string: 4.60 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.3.6 OpenGL shading language version string: 4.60 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL ES profile version string: OpenGL ES 3.2 Mesa 22.3.6 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 lspci 00:00.0 Host bridge: Intel Corporation 12th Gen Core Processor Host Bridge/DRAM Registers (rev 02) 00:01.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x16 Controller #1 (rev 02) 00:02.0 VGA compatible controller: Intel Corporation Alder Lake-P Integrated Graphics Controller (rev 0c) 00:04.0 Signal processing controller: Intel Corporation Alder Lake Innovation Platform Framework Processor Participant (rev 02) 00:06.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x4 Controller #0 (rev 02) 00:06.2 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x4 Controller #2 (rev 02) 00:07.0 PCI bridge: Intel Corporation Alder Lake-P Thunderbolt 4 PCI Express Root Port #0 (rev 02) 00:0a.0 Signal processing controller: Intel Corporation Platform Monitoring Technology (rev 01) 00:0d.0 USB controller: Intel Corporation Alder Lake-P Thunderbolt 4 USB Controller (rev 02) 00:0d.2 USB controller: Intel Corporation Alder Lake-P Thunderbolt 4
[Desktop-packages] [Bug 2012225] Re: mutter-x11-frames crashed with SIGABRT in g_assertion_message() from g_assertion_message_cmpnum() ["assertion failed (glCheckFramebufferStatus (GL_FRAMEBUFFER) ==
This also looks relevant, though only appears in one crash report: gnome-shell[10846]: JS ERROR: GLib.Error cogl-framebuffer-error-quark: Failed to create an OpenGL framebuffer object _prepareAnimationInfo@resource:///org/gnome/shell/ui/windowManager.js:1285:34 _sizeChangeWindow@resource:///org/gnome/shell/ui/windowManager.js:1277:18 ** Tags added: nvidia ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** Changed in: mutter (Ubuntu) Status: New => Confirmed ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High ** Changed in: gtk4 (Ubuntu) Importance: Undecided => High ** Changed in: mutter (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2012225 Title: mutter-x11-frames crashed with SIGABRT in g_assertion_message() from g_assertion_message_cmpnum() ["assertion failed (glCheckFramebufferStatus (GL_FRAMEBUFFER) == GL_FRAMEBUFFER_COMPLETE): (0x8cdd == 0x8cd5)"] from gsk_gl_command_queue_create_render_target() [gskglcommandqueue.c:1279] Status in GTK+: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding mutter. This problem was most recently seen with package version 44~rc-1ubuntu3, the problem page at https://errors.ubuntu.com/problem/7164cde08dbb940e13b49c4e92d4914b24e6c7dc contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2012225/+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 2012225] Re: mutter-x11-frames crashed with SIGABRT in g_assertion_message() from g_assertion_message_cmpnum() ["assertion failed (glCheckFramebufferStatus (GL_FRAMEBUFFER) ==
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk4 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2012225 Title: mutter-x11-frames crashed with SIGABRT in g_assertion_message() from g_assertion_message_cmpnum() ["assertion failed (glCheckFramebufferStatus (GL_FRAMEBUFFER) == GL_FRAMEBUFFER_COMPLETE): (0x8cdd == 0x8cd5)"] from gsk_gl_command_queue_create_render_target() [gskglcommandqueue.c:1279] Status in GTK+: Unknown Status in gtk4 package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding mutter. This problem was most recently seen with package version 44~rc-1ubuntu3, the problem page at https://errors.ubuntu.com/problem/7164cde08dbb940e13b49c4e92d4914b24e6c7dc contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2012225/+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 2012225] Re: /usr/libexec/mutter-x11-frames:6:g_assertion_message:g_assertion_message_cmpnum:gsk_gl_command_queue_create_render_target:gsk_gl_driver_create_render_target:gsk_gl
This was meant to be fixed in bug 2007766, but it's still happening for some. ** Summary changed: - /usr/libexec/mutter-x11-frames:6:g_assertion_message:g_assertion_message_cmpnum:gsk_gl_command_queue_create_render_target:gsk_gl_driver_create_render_target:gsk_gl_render_job_visit_blurred_outset_shadow_node + mutter-x11-frames crashed with SIGABRT in g_assertion_message() from g_assertion_message_cmpnum() from gsk_gl_command_queue_create_render_target() from gsk_gl_driver_create_render_target() from gsk_gl_render_job_visit_blurred_outset_shadow_node() ** Summary changed: - mutter-x11-frames crashed with SIGABRT in g_assertion_message() from g_assertion_message_cmpnum() from gsk_gl_command_queue_create_render_target() from gsk_gl_driver_create_render_target() from gsk_gl_render_job_visit_blurred_outset_shadow_node() + mutter-x11-frames crashed with SIGABRT in g_assertion_message() from g_assertion_message_cmpnum() ["assertion failed (glCheckFramebufferStatus (GL_FRAMEBUFFER) == GL_FRAMEBUFFER_COMPLETE): (0x8cdd == 0x8cd5)"] from gsk_gl_command_queue_create_render_target() [gskglcommandqueue.c:1279] ** Package changed: mutter (Ubuntu) => gtk4 (Ubuntu) ** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #5392 https://gitlab.gnome.org/GNOME/gtk/-/issues/5392 ** Also affects: gtk via https://gitlab.gnome.org/GNOME/gtk/-/issues/5392 Importance: Unknown Status: Unknown -- 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/2012225 Title: mutter-x11-frames crashed with SIGABRT in g_assertion_message() from g_assertion_message_cmpnum() ["assertion failed (glCheckFramebufferStatus (GL_FRAMEBUFFER) == GL_FRAMEBUFFER_COMPLETE): (0x8cdd == 0x8cd5)"] from gsk_gl_command_queue_create_render_target() [gskglcommandqueue.c:1279] Status in GTK+: Unknown Status in gtk4 package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding mutter. This problem was most recently seen with package version 44~rc-1ubuntu3, the problem page at https://errors.ubuntu.com/problem/7164cde08dbb940e13b49c4e92d4914b24e6c7dc contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2012225/+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 2012225] [NEW] mutter-x11-frames crashed with SIGABRT in g_assertion_message() from g_assertion_message_cmpnum() ["assertion failed (glCheckFramebufferStatus (GL_FRAMEBUFFER) =
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding mutter. This problem was most recently seen with package version 44~rc-1ubuntu3, the problem page at https://errors.ubuntu.com/problem/7164cde08dbb940e13b49c4e92d4914b24e6c7dc contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gtk Importance: Unknown Status: Unknown ** Affects: gtk4 (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: lunar -- 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/2012225 Title: mutter-x11-frames crashed with SIGABRT in g_assertion_message() from g_assertion_message_cmpnum() ["assertion failed (glCheckFramebufferStatus (GL_FRAMEBUFFER) == GL_FRAMEBUFFER_COMPLETE): (0x8cdd == 0x8cd5)"] from gsk_gl_command_queue_create_render_target() [gskglcommandqueue.c:1279] Status in GTK+: Unknown Status in gtk4 package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding mutter. This problem was most recently seen with package version 44~rc-1ubuntu3, the problem page at https://errors.ubuntu.com/problem/7164cde08dbb940e13b49c4e92d4914b24e6c7dc contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2012225/+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 2012223] Re: mutter-x11-frames crashed with SIGSEGV in fetch_request_mode() from fetch_request_mode() from gtk_widget_get_request_mode() from gtk_window_compute_default_size()
** Summary changed: - /usr/libexec/mutter-x11-frames:11:fetch_request_mode:fetch_request_mode:gtk_widget_get_request_mode:gtk_window_compute_default_size:toplevel_compute_size + mutter-x11-frames crashed with SIGSEGV in fetch_request_mode() from fetch_request_mode() from gtk_widget_get_request_mode() from gtk_window_compute_default_size() from toplevel_compute_size() -- 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/2012223 Title: mutter-x11-frames crashed with SIGSEGV in fetch_request_mode() from fetch_request_mode() from gtk_widget_get_request_mode() from gtk_window_compute_default_size() from toplevel_compute_size() Status in mutter package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding mutter. This problem was most recently seen with package version 44~beta-3ubuntu2, the problem page at https://errors.ubuntu.com/problem/461ff881978d26b3ab6a55c3a8b0cef1af4b5473 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2012223/+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 2012223] Re: /usr/libexec/mutter-x11-frames:11:fetch_request_mode:fetch_request_mode:gtk_widget_get_request_mode:gtk_window_compute_default_size:toplevel_compute_size
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- 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/2012223 Title: mutter-x11-frames crashed with SIGSEGV in fetch_request_mode() from fetch_request_mode() from gtk_widget_get_request_mode() from gtk_window_compute_default_size() from toplevel_compute_size() Status in mutter package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding mutter. This problem was most recently seen with package version 44~beta-3ubuntu2, the problem page at https://errors.ubuntu.com/problem/461ff881978d26b3ab6a55c3a8b0cef1af4b5473 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2012223/+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 2012223] [NEW] mutter-x11-frames crashed with SIGSEGV in fetch_request_mode() from fetch_request_mode() from gtk_widget_get_request_mode() from gtk_window_compute_default_size(
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding mutter. This problem was most recently seen with package version 44~beta-3ubuntu2, the problem page at https://errors.ubuntu.com/problem/461ff881978d26b3ab6a55c3a8b0cef1af4b5473 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: mutter (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: lunar -- 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/2012223 Title: mutter-x11-frames crashed with SIGSEGV in fetch_request_mode() from fetch_request_mode() from gtk_widget_get_request_mode() from gtk_window_compute_default_size() from toplevel_compute_size() Status in mutter package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding mutter. This problem was most recently seen with package version 44~beta-3ubuntu2, the problem page at https://errors.ubuntu.com/problem/461ff881978d26b3ab6a55c3a8b0cef1af4b5473 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2012223/+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 2011271] Re: gdm3: "Oh no! Something has gone wrong."
*** This bug is a duplicate of bug 2012068 ***
https://bugs.launchpad.net/bugs/2012068
** This bug has been marked a duplicate of private bug 2012068
--
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/2011271
Title:
gdm3: "Oh no! Something has gone wrong."
Status in gnome-shell package in Ubuntu:
Incomplete
Bug description:
I have installed ubuntu-desktop on Ubuntu Lunar using a RISCV system
with Nvidia GT 710 as well as on a system with a Radeon 8450. In both
cases gdm3 does not show a dialog but a message "Oh no! Something has
gone wrong." Kinetic and Jammy work fine.
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gdm3 43.0-3ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-1013.14-generic 5.19.17
Uname: Linux 5.19.0-1013-generic riscv64
ApportVersion: 2.26.0-0ubuntu2
Architecture: riscv64
CasperMD5json:
{
"result": "skip"
}
Date: Fri Mar 10 21:53:33 2023
InstallationDate: Installed on 2023-02-22 (16 days ago)
InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release
riscv64 (20230221)
ProcCpuinfoMinimal:
processor: 3
hart : 3
isa : rv64imafdc
mmu : sv39
uarch: sifive,u74-mc
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=vt220
SourcePackage: gdm3
UpgradeStatus: Upgraded to lunar on 2023-03-10 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011271/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003168] Re: SIdebar, files gets unresponsive after unlocking locked season.
[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2003168 Title: SIdebar, files gets unresponsive after unlocking locked season. Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Expired Bug description: SIdebar, files gets unresponsive after unlocking locked season. Clicking on search bar also freezes the whole season. Issue requires Restarting GTK3 or restarting the season. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-59.65-generic 5.15.78 Uname: Linux 5.15.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 18 13:35:36 2023 InstallationDate: Installed on 2021-06-20 (576 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2003168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966905] Re: Memory access errors in gnome-shell from accountsservice
Also tracking in https://errors.ubuntu.com/problem/d85747462e756cb405d1e87b9c59b0b995a7d394 ** Description changed: + https://errors.ubuntu.com/problem/d85747462e756cb405d1e87b9c59b0b995a7d394 + Valgrind memory errors in gnome-shell 42 from accountsservice: ==60511== Invalid read of size 8 ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120) ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417) ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557) ==60511==by 0x1E428ECA: _act_user_update_from_object_path (act-user.c:1346) ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511== Block was alloc'd at ==60511==at 0x4848899: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4DA5718: g_malloc (gmem.c:125) ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072) ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098) ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911) ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011) ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181) ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821) ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706) ==60511==by 0x1E429BD8: act_user_manager_get_user (act-user-manager.c:1879) ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) - ==60511== + ==60511== ==60511== Invalid read of size 8 ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a (gtype.c:4091) ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982) ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557) ==60511==by 0x1E428ECA: _act_user_update_from_object_path (act-user.c:1346) ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187)
[Desktop-packages] [Bug 2012218] Re: /usr/bin/gnome-shell:11:g_type_check_instance_cast:free_fetch_user_request:fetch_user_incrementally:on_find_user_by_name_finished:g_task_return_now
*** This bug is a duplicate of bug 1966905 *** https://bugs.launchpad.net/bugs/1966905 ** This bug has been marked a duplicate of bug 1966905 Memory access errors in gnome-shell from accountsservice -- 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/2012218 Title: /usr/bin/gnome- shell:11:g_type_check_instance_cast:free_fetch_user_request:fetch_user_incrementally:on_find_user_by_name_finished:g_task_return_now Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44~rc-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/d85747462e756cb405d1e87b9c59b0b995a7d394 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012218/+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 2012218] [NEW] /usr/bin/gnome-shell:11:g_type_check_instance_cast:free_fetch_user_request:fetch_user_incrementally:on_find_user_by_name_finished:g_task_return_now
*** This bug is a duplicate of bug 1966905 *** https://bugs.launchpad.net/bugs/1966905 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44~rc-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/d85747462e756cb405d1e87b9c59b0b995a7d394 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2012218 Title: /usr/bin/gnome- shell:11:g_type_check_instance_cast:free_fetch_user_request:fetch_user_incrementally:on_find_user_by_name_finished:g_task_return_now Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44~rc-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/d85747462e756cb405d1e87b9c59b0b995a7d394 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012218/+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 2011284] Re: A flickering and glitching problem
** Tags added: amdgpu ** Package changed: xorg-server (Ubuntu) => linux-hwe-5.4 (Ubuntu) ** Also affects: xserver-xorg-video-amdgpu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2011284 Title: A flickering and glitching problem Status in linux-hwe-5.4 package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: Dear Ubuntu Dev, I've been using my linux UBUNTU 18.04 LTS for the past 6 months and the day since I got this computer,It started glitching.Can you please fix that?I have a screenshot of the problem and I am unable to play some games due to this completely glitching and flickering Sincerely, Nihar Raju ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 10:44:09 2023 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev df) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:879e] InstallationDate: Installed on 2021-02-22 (746 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:b00c Realtek Semiconductor Corp. Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP 245 G8 Notebook PC ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=0c18d80a-c684-48f5-881d-dbe1c2478f74 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2021 dmi.bios.vendor: AMI dmi.bios.version: F.62 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 879E dmi.board.vendor: Hewlett-Packard dmi.board.version: 84.49 dmi.chassis.asset.tag: 5CG13423RK dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.62:bd04/23/2021:svnHewlett-Packard:pnHP245G8NotebookPC:pvr:rvnHewlett-Packard:rn879E:rvr84.49:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN HP 200 dmi.product.name: HP 245 G8 Notebook PC dmi.product.sku: 404V1PC#ACJ dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/2011284/+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 1966905] Re: Memory access errors in gnome-shell from accountsservice
** Changed in: accountsservice (Ubuntu) Importance: Medium => High ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1966905 Title: Memory access errors in gnome-shell from accountsservice Status in accountsservice: New Status in accountsservice package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Valgrind memory errors in gnome-shell 42 from accountsservice: ==60511== Invalid read of size 8 ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120) ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417) ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557) ==60511==by 0x1E428ECA: _act_user_update_from_object_path (act-user.c:1346) ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511== Block was alloc'd at ==60511==at 0x4848899: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4DA5718: g_malloc (gmem.c:125) ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072) ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098) ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911) ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011) ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181) ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821) ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706) ==60511==by 0x1E429BD8: act_user_manager_get_user (act-user-manager.c:1879) ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511== ==60511== Invalid read of size 8 ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a (gtype.c:4091) ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982) ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA: UnknownInlinedFun
[Desktop-packages] [Bug 2011751] Re: openbox crashed with SIGABRT
I believe we have a working patch for the problem. A quick summary of what it looks like is happening: Openbox maintains a list of windows organized by stacking order from highest to lowest. This is a doubly-linked list. There is a function in Openbox called client_calc_layer that uses a pointer into this list to walk through it while modifying it. When client_calc_layer modifies the list, it also messes up the pointer that it is actively using to walk through the list. The next element that Openbox loads contains a dangling pointer, and that promptly results in a segfault when Openbox tries to dereference that pointer. To solve the problem, I added a patch that makes Openbox save a pointer to the list element *before* the current element before modifying the list. When the list is then modified, the still-valid pointer to the previous list element is used to get a new (and actually usable!) pointer to the current list element. The old, broken pointer is then overwritten by the new, working pointer, and the segfaults stop. Using the patch, I am no longer able to reproduce this bug when following the testcase (open a browser fullscreen, right-click a link, and click "Open in new window"). I have the patched Openbox uploaded to a PPA here: https://launchpad.net/~arraybolt3/+archive/ubuntu/openbox -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2011751 Title: openbox crashed with SIGABRT Status in glib2.0 package in Ubuntu: Confirmed Status in openbox package in Ubuntu: Confirmed Bug description: Lubuntu lunar (primary box) on - dell [optiplex] 7050 (i5-6500, 16gb, intel hd530/i915) I experienced a crash yesterday (openbox) but tend to ignore the first crashes... Whilst using the machine again today a crash occurred. This is my primary box, so my setup is pretty consistent - featherpad (restored session) - hexchat (irc) - qterminal (only single tab today; usually many) - firefox (snap, most sites excluding google related) - chromium (snap, used for anything google related) - telegram (snap) - element I was using chromium full screen (trying to read my gmail inbox) when borders around windows disappeared & I lost the capacity to switch between windows; mouse would move, but keyboard appeared mostly dead (it wasn't, more I think windows weren't responding, inc. clicks with mouse though that's likely inconsistent; I could work out how to describe it yesterday, but todays is almost identical). I switched to text terminal (ctrl+alt+f4) & explored; returned to GUI and used - ctrl+alt+t to open new terminal - openbox & session returned to what I expect... ** expected outcome Openbox doesn't crash ** actual outcome all windows lost borders, and i lost ability to switch between windows I appeared to have minimal control (not true, more a fraction of what I expect) ** How to get crash For me, - I used chromium (browser) - make chromium full screen (ie. F11) - click on something & right-click to open in new window OPENBOX CRASH. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: openbox 3.6.1-10 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: LXQt Date: Thu Mar 16 09:46:22 2023 ExecutablePath: /usr/bin/openbox ExecutableTimestamp: 1643543619 InstallationDate: Installed on 2023-01-25 (49 days ago) InstallationMedia: Lubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230124) JournalErrors: -- No entries -- ProcCmdline: /usr/bin/openbox ProcCwd: /home/guiverc RebootRequiredPkgs: Error: path contained symlinks. Signal: 6 SourcePackage: openbox StacktraceTop: () at /lib/x86_64-linux-gnu/libobt.so.2 () at /lib/x86_64-linux-gnu/libc.so.6 client_calc_layer () () () at /lib/x86_64-linux-gnu/libobt.so.2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+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 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
That's not this bug then, so please open a new one by running: ubuntu-bug gnome-shell -- 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/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in GNOME Shell: New Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: [ Workaround ] Add to /etc/environment (in Ubuntu 22.04): MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 or in Ubuntu 22.10 and later: MUTTER_DEBUG_FORCE_KMS_MODE=simple and then reboot. [ Original report ] (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+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 2011803] Re: Fullscreen games repeatedly fullscreen/unfullscreen in 44~rc
It was fixed in this instead: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2921 ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Committed ** Tags added: fixed-in-mutter-44.0 fixed-upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2011803 Title: Fullscreen games repeatedly fullscreen/unfullscreen in 44~rc Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Committed Bug description: Team Fortress 2 started blinking in fullscreen mode after recent system upgrade. I attached part of apt.log showing two latest big upgrades. TF2 stopped working as intended after upgrade in 2023-03-16 02:18:19. `lsb_release -rd` output: No LSB modules are available. Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 `mutter --version` output: mutter 44.rc `inxi -G` output: Graphics: Device-1: Intel Tiger Lake-LP GT2 [UHD Graphics G4] driver: i915 v: kernel Device-2: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo Display: wayland server: X.Org v: 1.22.1.8 with: Xwayland v: 22.1.8 compositor: gnome-shell v: 44.rc driver: X: loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 resolution: 1920x1080~60Hz API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel UHD Graphics (TGL GT2) --- ProblemType: Bug ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-08-06 (221 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220806) Package: gnome-shell 44~rc-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANG=ru_RU.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.2.0-10.10-generic 6.2.0 RelatedPackageVersions: mutter-common 44~rc-1ubuntu3 Tags: wayland-session lunar Uname: Linux 6.2.0-10-generic x86_64 UpgradeStatus: Upgraded to lunar on 2022-11-27 (109 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2011803/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012146] Re: very high cpu usage, system unresponsive
Thanks for clarifying. It means that we can't tell whether the issue is related to the specific changes in ibus 1.5.28-2, or if it is a general ibus 1.5.28 problem (or an ardour 7.3 problem...). In any case my plea to also report it to ibus upstream still stands. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2012146 Title: very high cpu usage, system unresponsive Status in ibus package in Ubuntu: New Bug description: may be related to Ardour 7.3, when I start ardour and start working with the app, the system slows down and htop shows 100% cpu usage for ibus-daemon ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ibus 1.5.28-2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 18 15:21:55 2023 InstallationDate: Installed on 2022-05-13 (308 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: ibus UpgradeStatus: Upgraded to lunar on 2023-03-17 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2012146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1980080] Re: Unable to eject SDcard -getting remounted immediately
Also wondering - my lspci output shows line: 72:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5260 PCI Express Card Reader (rev 01) I'm wondering about the 'unassigned class' - might it be related to this issue. As most other devices besides NVMe disk starts from 00:, where NVMe starts from 01: Might this 72: mean that SD card reader has priority over NVMe disk ? ** Changed in: gvfs (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1980080 Title: Unable to eject SDcard -getting remounted immediately Status in gvfs package in Ubuntu: Confirmed Bug description: THe problem is on Dell XPS13 9310 and built-in microSD card reader(without adapter). When I plug the card it's visiible in file manager, with little 'eject' icon. I can read/write to it. After finishing and using eject button. THe card it's still present in gnome along with 'eject' button. But when clicking eject it says 'No object for D-bus interface' and both the device and partition blockdevices are still present. I can't also eject from command line: nusch@xps13:~$ LANG="en" eject -v /dev/mmcblk0 eject: device name is `/dev/mmcblk0' eject: /dev/mmcblk0: not mounted eject: /dev/mmcblk0: is whole-disk device eject: /dev/mmcblk0: trying to eject using CD-ROM eject command eject: CD-ROM eject command failed eject: /dev/mmcblk0: trying to eject using SCSI commands eject: not an sg device, or old sg driver eject: SCSI eject failed eject: /dev/mmcblk0: trying to eject using floppy eject command eject: floppy eject command failed eject: /dev/mmcblk0: trying to eject using tape offline command eject: tape offline command failed eject: unable to eject ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.10.0-1057.61-oem 5.10.83 Uname: Linux 5.10.0-1057-oem x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu71.2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 28 13:31:39 2022 DisplayManager: gdm3 InstallationDate: Installed on 2015-05-08 (2608 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-02-21 (126 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1980080/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012146] Re: very high cpu usage, system unresponsive
last friday I upgraded from 22.10 to 23.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2012146 Title: very high cpu usage, system unresponsive Status in ibus package in Ubuntu: New Bug description: may be related to Ardour 7.3, when I start ardour and start working with the app, the system slows down and htop shows 100% cpu usage for ibus-daemon ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ibus 1.5.28-2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 18 15:21:55 2023 InstallationDate: Installed on 2022-05-13 (308 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: ibus UpgradeStatus: Upgraded to lunar on 2023-03-17 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2012146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1225331] Re: nm-applet crashed with SIGSEGV in gtk_status_icon_set_visible()
Cannot reproduce in 22.04. ** Changed in: network-manager-applet (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1225331 Title: nm-applet crashed with SIGSEGV in gtk_status_icon_set_visible() Status in network-manager-applet package in Ubuntu: Fix Released Bug description: Firefox 23.0.1 ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: network-manager-gnome 0.9.8.0-1ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.1-0ubuntu4 Architecture: amd64 CrashCounter: 1 Date: Sat Sep 14 09:49:41 2013 ExecutablePath: /usr/bin/nm-applet IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-09-14 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130913) IpRoute: default via 192.168.0.1 dev eth1 proto static 192.168.0.0/24 dev eth1 proto kernel scope link src 192.168.0.51 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: nm-applet SegvAnalysis: Segfault happened at: 0x7f5817ee3a4c : cmp%rax,(%rdx) PC (0x7f5817ee3a4c) ok source "%rax" ok destination "(%rdx)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: network-manager-applet StacktraceTop: gtk_status_icon_set_visible () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () ?? () from /usr/lib/x86_64-linux-gnu/libappindicator3.so.1 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () Title: nm-applet crashed with SIGSEGV in gtk_status_icon_set_visible() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 2a845f086-6a84-44b0-a761-e431cd9f99f7 802-3-ethernet1379148684 sam. 14 sept. 2013 09:51:24 CETyes no /org/freedesktop/NetworkManager/Settings/2 dlink 3c972a87-187c-43ab-9c4d-d2828d9e319f 802-11-wireless 1379148688 sam. 14 sept. 2013 09:51:28 CETyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH usb0 gsm disconnected /org/freedesktop/NetworkManager/Devices/3 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/2 eth1 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1225331/+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 1332623] Re: Thunar behaves inconsistently with USB flash drive FAT32 partitions
** Changed in: glib2.0 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1332623
Title:
Thunar behaves inconsistently with USB flash drive FAT32 partitions
Status in glib2.0 package in Ubuntu:
Fix Released
Status in thunar package in Ubuntu:
Fix Released
Bug description:
I installed Xubuntu 14.04 and performed no customizations or
reconfigurations.
Observation: Thunar 1.6.3 ("File Manager" from menu) on Xubuntu 14.04
handles write permission to inserted USB flash drives inconsistently:
* I am able to create a nil file on the flash drive with Thunar and edit it.
Clearly, the flash drive is not read-only.
* Using Thunar, I cannot copy an existing file (E.g. ~/.profile) and paste it
on the flash drive - "destination is read-only" (not true!).
* However, in a terminal window, `cp` with the flash drive as a destination
succeeds.
I tried this on drives by different manufacturers and with differing
capacities and on two different Xubuntu 14.04 installations.
There might be a configuration change for Thunar to allow paste to
flash drives. If so, this should be enabled when Thunar is installed
as this behaviour is what users expect.
Note: I created the FAT32 partition with `gparted` on Linux. I also
got the same results after creating a FAT32 partition using an MACOSX
system.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: thunar 1.6.3-1ubuntu5
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Jun 20 11:30:40 2014
InstallationDate: Installed on 2014-06-19 (1 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64
(20140416.2)
SourcePackage: thunar
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1332623/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012146] Re: very high cpu usage, system unresponsive
Ok.. But when exactly did you do that? If it was very recently, you may have upgraded ibus from 1.5.27-2 directly to 1.5.28-2. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2012146 Title: very high cpu usage, system unresponsive Status in ibus package in Ubuntu: New Bug description: may be related to Ardour 7.3, when I start ardour and start working with the app, the system slows down and htop shows 100% cpu usage for ibus-daemon ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ibus 1.5.28-2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 18 15:21:55 2023 InstallationDate: Installed on 2022-05-13 (308 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: ibus UpgradeStatus: Upgraded to lunar on 2023-03-17 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2012146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012146] Re: very high cpu usage, system unresponsive
the issue started when I upgraded to 23.04 yes -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2012146 Title: very high cpu usage, system unresponsive Status in ibus package in Ubuntu: New Bug description: may be related to Ardour 7.3, when I start ardour and start working with the app, the system slows down and htop shows 100% cpu usage for ibus-daemon ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ibus 1.5.28-2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 18 15:21:55 2023 InstallationDate: Installed on 2022-05-13 (308 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: ibus UpgradeStatus: Upgraded to lunar on 2023-03-17 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2012146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012146] Re: very high cpu usage, system unresponsive
Thanks for your report! I see that you installed your system last year. Can you possibly tell if it's a regression from ibus 1.5.28-1, i.e. did it work smoothly with that version and the issue started with ibus 1.5.28-2? I'm asking because 1.5.28-2 includes two patches which are not yet in the upstream git repo, but only in the repo of the upstream maintainer. Those patches are supposed to fix bug #2009700. Whatever the answer to that question is, I would ask you to report this issue also to the upstream issue tracker: https://github.com/ibus/ibus/issues If you do, please post the URL to the issue in a comment here. And, btw, please state in the upstream issue that ibus 1.5.28-2 in Ubuntu includes the patches I mentioned. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2012146 Title: very high cpu usage, system unresponsive Status in ibus package in Ubuntu: New Bug description: may be related to Ardour 7.3, when I start ardour and start working with the app, the system slows down and htop shows 100% cpu usage for ibus-daemon ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ibus 1.5.28-2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 18 15:21:55 2023 InstallationDate: Installed on 2022-05-13 (308 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: ibus UpgradeStatus: Upgraded to lunar on 2023-03-17 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2012146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012199] [NEW] nautilus crashes during search or bulk filename editing
Public bug reported: EVERY search or bulk file renaming action causes nautilus to crash immediately. All searches cause nautilus to crash immediately. No search ever comes through. Simple typing in the search bar, or as much as clicking on it causes nautilus to crash. Once multiple files are selected and Fn+F2 (Rename) action is selected, nautilus crashes even without allowing the rename dialog box to appear. Note that single file renaming still works. The crashed window gives the option to wait, but waiting never solves the problem, and I am always forced to restart nautilus after force- quitting. What is causing this problem? If this issue is not widespread enough to receive a bugfix, could the developers guide me with this. I find doing a fresh install risky because of lack of enough storage for a complete PC backup. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Package changed: grub-installer (Ubuntu) => nautilus (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2012199 Title: nautilus crashes during search or bulk filename editing Status in nautilus package in Ubuntu: New Bug description: EVERY search or bulk file renaming action causes nautilus to crash immediately. All searches cause nautilus to crash immediately. No search ever comes through. Simple typing in the search bar, or as much as clicking on it causes nautilus to crash. Once multiple files are selected and Fn+F2 (Rename) action is selected, nautilus crashes even without allowing the rename dialog box to appear. Note that single file renaming still works. The crashed window gives the option to wait, but waiting never solves the problem, and I am always forced to restart nautilus after force- quitting. What is causing this problem? If this issue is not widespread enough to receive a bugfix, could the developers guide me with this. I find doing a fresh install risky because of lack of enough storage for a complete PC backup. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2012199/+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 2012199] [NEW] nautilus crashes during search or bulk filename editing
You have been subscribed to a public bug: EVERY search or bulk file renaming action causes nautilus to crash immediately. All searches cause nautilus to crash immediately. No search ever comes through. Simple typing in the search bar, or as much as clicking on it causes nautilus to crash. Once multiple files are selected and Fn+F2 (Rename) action is selected, nautilus crashes even without allowing the rename dialog box to appear. Note that single file renaming still works. The crashed window gives the option to wait, but waiting never solves the problem, and I am always forced to restart nautilus after force- quitting. What is causing this problem? If this issue is not widespread enough to receive a bugfix, could the developers guide me with this. I find doing a fresh install risky because of lack of enough storage for a complete PC backup. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- nautilus crashes during search or bulk filename editing https://bugs.launchpad.net/bugs/2012199 You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012195] Re: toolbox.py crashed with NameError in __readAuthType(): name 'get_distro_std_name' is not defined
*** This bug is a duplicate of bug 2012178 *** https://bugs.launchpad.net/bugs/2012178 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #2012178, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** Changed in: hplip (Ubuntu) Importance: Undecided => Medium ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/2012195/+attachment/5655712/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/2012195/+attachment/5655714/+files/ProcStatus.txt ** This bug has been marked a duplicate of private bug 2012178 ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/2012195 Title: toolbox.py crashed with NameError in __readAuthType(): name 'get_distro_std_name' is not defined Status in hplip package in Ubuntu: New Bug description: Just tried to open the HP LIP UI after running sudo apt install hplip- gui ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: hplip-data 3.22.10+dfsg0-1 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 19 11:47:40 2023 ExecutablePath: /usr/share/hplip/toolbox.py InstallationDate: Installed on 2023-03-06 (12 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) InterpreterPath: /usr/bin/python3.11 JournalErrors: Mar 19 11:47:43 User Name-BellSant-ThinkPad-T16-Gen-1 gnome-shell[814842]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Lpstat: device for DeskJet-3700: dnssd://HP%20DeskJet%203700%20series%20%5BB70076%5D._ipp._tcp.local/?uuid=31e26b75-4172-d3a7-a071-9f856b2c25c1 device for HP_DeskJet_3700_series_B70076: implicitclass://HP_DeskJet_3700_series_B70076/ MachineType: LENOVO 21CH004BUS PackageArchitecture: all Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_DeskJet_3700_series_B70076.ppd', '/etc/cups/ppd/DeskJet-3700.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_DeskJet_3700_series_B70076.ppd: Permission denied grep: /etc/cups/ppd/DeskJet-3700.ppd: Permission denied ProcCmdline: /usr/bin/python3 /usr/bin/hp-toolbox ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.1.0-16-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonArgs: ['/usr/bin/hp-toolbox'] PythonDetails: N/A SourcePackage: hplip Title: toolbox.py crashed with NameError in __readAuthType(): name 'get_distro_std_name' is not defined UpgradeStatus: Upgraded to lunar on 2023-03-11 (7 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo 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: 21CH004BUS dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.11 dmi.modalias: dmi:bvnLENOVO:bvrR23ET62W(1.32):bd11/11/2022:br1.32:efr1.11:svnLENOVO:pn21CH004BUS:pvrThinkPadT16Gen1:rvnLENOVO:rn21CH004BUS:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CH_BU_Think_FM_ThinkPadT16Gen1: dmi.product.family: ThinkPad T16 Gen 1 dmi.product.name: 21CH004BUS dmi.product.sku: LENOVO_MT_21CH_BU_Think_FM_ThinkPad T16 Gen 1 dmi.product.version: ThinkPad T16 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/2012195/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956111] Re: Colord's colorhug no longer exists but a URI and library do.
** Tags added: bloat -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1956111 Title: Colord's colorhug no longer exists but a URI and library do. Status in colord package in Ubuntu: New Status in colord package in Debian: New Bug description: https://github.com/hughsie/colord/commit/98f83acc910f527496fc149511c9dfa35f954be9 The domain listed in the upload URI in the gschema has been taken over by spammers. The library libcolorhug2 is still installed by default as a dependency of colord. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1956111/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970050] Re: [H97M-HD3, Intel Haswell HDMI, Digital Out, HDMI] No sound at all because of upgrade from 20.04 LTS to 22.04
For those with AMD CPUs, rolling back to kernel 5.19.0-32-generic can bring my HDMI/DP audio device back. Sound is played properly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1970050 Title: [H97M-HD3, Intel Haswell HDMI, Digital Out, HDMI] No sound at all because of upgrade from 20.04 LTS to 22.04 Status in alsa-driver package in Ubuntu: Confirmed Bug description: After upgrading today from 20.04 LTS to 22.04 HDMI Audio does not work at all. Audio from speakers from a headphone jack works fine. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 23 21:13:23 2022 InstallationDate: Installed on 2020-04-24 (729 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed Symptom_Card: Built-in Audio - HDA Intel HDMI Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [H97M-HD3, Intel Haswell HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: Upgraded to jammy on 2022-04-23 (0 days ago) dmi.bios.date: 04/21/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H97M-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/21/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnH97M-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH97M-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H97M-HD3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1970050/+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 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
The workaround doesn't fix the problem for me. It's not only doesn't wake up the screen, it freezes the whole system and I have to hard reset! -- 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/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in GNOME Shell: New Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: [ Workaround ] Add to /etc/environment (in Ubuntu 22.04): MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 or in Ubuntu 22.10 and later: MUTTER_DEBUG_FORCE_KMS_MODE=simple and then reboot. [ Original report ] (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+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 2012176] Re: reboot after install
*** This bug is a duplicate of bug 2003251 *** https://bugs.launchpad.net/bugs/2003251 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #2003251, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2012176/+attachment/5655630/+files/CoreDump.gz ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/2012176/+attachment/5655632/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/2012176/+attachment/5655633/+files/ProcStatus.txt ** This bug has been marked a duplicate of private bug 2003251 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ayatana-indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/2012176 Title: reboot after install Status in ayatana-indicator-messages package in Ubuntu: New Bug description: I had just done a clean install and upon reboot this error came up. Zero idea what it is referring to. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: ayatana-indicator-messages 22.9.0-1 Uname: Linux 6.1.0-16-generic x86_64 Architecture: amd64 CurrentDesktop: MATE Date: Sun Mar 19 08:36:39 2023 ExecutablePath: /usr/libexec/ayatana-indicator-messages/ayatana-indicator-messages-service ExecutableTimestamp: 1664708325 ProcCmdline: /usr/libexec/ayatana-indicator-messages/ayatana-indicator-messages-service ProcCwd: /home/zebedee ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 11 SourcePackage: ayatana-indicator-messages UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ayatana-indicator-messages/+bug/2012176/+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
