Version-Release number of selected component: imsettings-1.7.3-6.fc29 Additional info: reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/libexec/imsettings-daemon crash_function: g_hash_table_lookup_node executable: /usr/libexec/imsettings-daemon journald_cursor: s=25e9e854390e4073b28b24d7c7aa8774;i=5a91;b=036096806eb64446a528e45c95a91bef;m=25b8918;t=5858478b4ec7d;x=4599a78d8c33b842 kernel: 5.0.5-200.fc29.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1553393 [details] File: backtrace
Created attachment 1553394 [details] File: cgroup
Created attachment 1553395 [details] File: core_backtrace
Created attachment 1553396 [details] File: cpuinfo
Created attachment 1553397 [details] File: dso_list
Created attachment 1553398 [details] File: environ
Created attachment 1553399 [details] File: limits
Created attachment 1553400 [details] File: maps
Created attachment 1553401 [details] File: mountinfo
Created attachment 1553402 [details] File: open_fds
Created attachment 1553403 [details] File: proc_pid_status
*** Bug 1649396 has been marked as a duplicate of this bug. ***
*** Bug 1697016 has been marked as a duplicate of this bug. ***
*** Bug 1723814 has been marked as a duplicate of this bug. ***
*** Bug 1738227 has been marked as a duplicate of this bug. ***
*** Bug 1745234 has been marked as a duplicate of this bug. ***
*** Bug 1740106 has been marked as a duplicate of this bug. ***
*** Bug 1753042 has been marked as a duplicate of this bug. ***
*** Bug 1717190 has been marked as a duplicate of this bug. ***
*** Bug 1696357 has been marked as a duplicate of this bug. ***
*** Bug 1671451 has been marked as a duplicate of this bug. ***
*** Bug 1668120 has been marked as a duplicate of this bug. ***
*** Bug 1665761 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Logged in and the message appeared. reporter: libreport-2.10.1 backtrace_rating: 4 cmdline: /usr/libexec/imsettings-daemon crash_function: g_mutex_lock executable: /usr/libexec/imsettings-daemon journald_cursor: s=9d60156f2c5745f1b24ced5b5316cfea;i=17fd;b=b49e6b309b464378a2676dfe6f4c52cd;m=5171da89;t=595fb91acbba2;x=4fed66abdfdf6407 kernel: 5.0.9-301.fc30.x86_64 package: imsettings-1.8.1-1.fc30 reason: imsettings-daemon killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1337
Similar problem has been detected: I logged into my desktop. A notification appeared saying there had been a problem and asking if I wanted to report it ... reporter: libreport-2.11.3 backtrace_rating: 4 cmdline: /usr/libexec/imsettings-daemon crash_function: g_mutex_lock executable: /usr/libexec/imsettings-daemon journald_cursor: s=b6f029e65975492a9baedefc01380593;i=7849;b=729ed2b8153e4f968d49af0b30e60eb9;m=2f12e08;t=597b17ee0e3b2;x=6542731f8d5533c8 kernel: 5.3.11-200.fc30.x86_64 package: imsettings-1.8.1-1.fc30 reason: imsettings-daemon killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
This morning's updates included: glib2-2.60.7-2.fc30.x86_64 glib2-devel-2.60.7-2.fc30.x86_64 gtk2-2.24.32-6.fc30.x86_64 gtk2-devel-2.24.32-6.fc30.x86_64 gtk2-immodule-xim-2.24.32-6.fc30.x86_64 Whereas imsettings was last updated on the 9th. It's possible this is exposing a bug in imsettings-daemon though.
*** Bug 1713985 has been marked as a duplicate of this bug. ***
*** Bug 1722851 has been marked as a duplicate of this bug. ***
*** Bug 1760098 has been marked as a duplicate of this bug. ***
*** Bug 1766829 has been marked as a duplicate of this bug. ***
*** Bug 1768311 has been marked as a duplicate of this bug. ***
*** Bug 1769059 has been marked as a duplicate of this bug. ***
*** Bug 1779077 has been marked as a duplicate of this bug. ***
*** Bug 1782436 has been marked as a duplicate of this bug. ***
FEDORA-2019-b370ef6421 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-b370ef6421
FEDORA-2019-0b16b7a9b7 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-0b16b7a9b7
*** Bug 1786739 has been marked as a duplicate of this bug. ***
Similar problem has been detected: ABRT notified me of this error as I was logging in. Freshly kicked workstation. reporter: libreport-2.11.3 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/dbus\x2d:1.2\x2dcom.redhat.imsettings.slice/dbus-:1.2-com.redhat.imsettings cmdline: /usr/libexec/imsettings-daemon crash_function: g_mutex_lock executable: /usr/libexec/imsettings-daemon journald_cursor: s=79362a0a3fc04ab9b4c7b5be9ac335a8;i=8ae;b=f88260dd1e324a00833571dbb6bcfad3;m=2ac1aa1;t=59b2b993ef657;x=488a847542f6e94d kernel: 5.3.14-300.fc31.x86_64 package: imsettings-1.8.1-2.fc31 reason: imsettings-daemon killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
imsettings-1.8.2-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-b370ef6421
imsettings-1.8.2-1.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-0b16b7a9b7
imsettings-1.8.2-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.
imsettings-1.8.2-1.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 1795785 has been marked as a duplicate of this bug. ***