Description of problem: Just detach and attach again mouse, keyboard or bluetooth heaphones... Version-Release number of selected component: gnome-session-3.35.3-1.fc32 Additional info: reporter: libreport-2.11.3 backtrace_rating: 4 cgroup: 0::/user.slice/user-1002.slice/user/gnome\x2dsession\x2dmanager.slice/gnome-session-manager cmdline: /usr/libexec/gnome-session-binary --systemd-service --session=gnome crash_function: __strcmp_avx2 executable: /usr/libexec/gnome-session-binary journald_cursor: s=15db3b4213e7481e949c0c6d133afd7a;i=bc59;b=e9a168642e0f4f5d9f5d6c30fe5f58c3;m=2f422c96;t=59c6c47ab041a;x=b06f7a0916095fbc kernel: 5.5.0-0.rc6.git2.2.fc32.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1002 Truncated backtrace: Thread no. 1 (3 frames) #0 __strcmp_avx2 at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:101 #1 g_str_equal at ../glib/ghash.c:2287 #2 on_object_added at ../libgnome-desktop/gnome-idle-monitor.c:207
Created attachment 1653412 [details] File: backtrace
Created attachment 1653413 [details] File: core_backtrace
Created attachment 1653414 [details] File: cpuinfo
Created attachment 1653415 [details] File: dso_list
Created attachment 1653416 [details] File: environ
Created attachment 1653417 [details] File: exploitable
Created attachment 1653418 [details] File: limits
Created attachment 1653419 [details] File: maps
Created attachment 1653420 [details] File: mountinfo
Created attachment 1653421 [details] File: open_fds
Created attachment 1653422 [details] File: proc_pid_status
Similar problem has been detected: gnome-session crashes every time when connected devices such as mouse, keyboard, bluetooth headset, video capture card. reporter: libreport-2.11.3 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/gnome\x2dsession\x2dmanager.slice/gnome-session-manager cmdline: /usr/libexec/gnome-session-binary --systemd-service --session=gnome crash_function: __strcmp_avx2 executable: /usr/libexec/gnome-session-binary journald_cursor: s=834dde1828fa4584b63fb4b08b4715c4;i=15460;b=1e41d450aeba4dd1ba986924bfad4fca;m=9fdd17dc9;t=59c664a934ea2;x=8b1af273e5f273ff kernel: 5.5.0-0.rc6.git2.2.fc32.x86_64 package: gnome-session-3.35.3-1.fc32 reason: gnome-session-binary killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Last gnome-session version which not affected by this issue: # rpm -q gnome-session gnome-session-3.34.2-2.fc32.x86_64
Proposed as a Blocker and Freeze Exception for 32-beta by Fedora user mikhail using the blocker tracking app because: Because block base functionality (user couldn't plug new devices + couldn't wake up monitor after sleeping)
Also with gnome-session-3.35.3-1.fc32 I couldn't wake up monitor after sleeping. In system log I see message: gnome-shell[13023]: Failed to DPMS: Failed to set connector 63 property 2: Invalid argument
Mikhail, it's awkward for a private bug to be a proposed/accepted blocker as only RH folks can see it. trr, could you check whether there is really any private information in the attachments, and possibly change the bug to public? Note you can mark individual attachments (instead of the whole bug) as private. Thanks!
Sorry, I can not unselect fedora_contrib_private from Groups.
*** Bug 1793625 has been marked as a duplicate of this bug. ***
Status changed to public.
monitor->priv->path is NULL. a quick hack around this, $ vim gnome-desktop-3.35.4/libgnome-desktop/gnome-idle-monitor.c 200 static void 201 on_object_added (GDBusObjectManager *manager, 202 GDBusObject *object, 203 gpointer user_data) 204 { 205 GnomeIdleMonitor *monitor = user_data; 206 207 if (monitor->priv->path == NULL || !g_str_equal (monitor->priv->path, g_dbus_object_get_object_path (object))) 208 return; From dbus-monitor, not sure if this is related signal time=1580149987.410405 sender=org.freedesktop.DBus -> destination=:1.55 serial=4294967295 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameLost string "org.gnome.SettingsDaemon.Power" signal time=1580149987.410436 sender=org.freedesktop.DBus -> destination=(null destination) serial=4294967295 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged string "org.gnome.SettingsDaemon.Power" string ":1.55" string "" signal time=1580149987.410455 sender=org.freedesktop.DBus -> destination=:1.55 serial=4294967295 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameLost string ":1.55" signal time=1580149987.410465 sender=org.freedesktop.DBus -> destination=(null destination) serial=4294967295 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged string ":1.55" string ":1.55" string ""
Created attachment 1656053 [details] dbus log just before the crash
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle. Changing version to 32.
I am not sure why we haven't discussed this bug in any blocker review meetings yet. Reporters, is it still happening with GNOME 3.35.92? Thanks!
Seems, problem is solved (at least in GNOME Shell 3.35.92).