Bug 2231101

Summary: [abrt] mate-settings-daemon: _IO_file_doallocate(): mate-settings-daemon killed by SIGABRT
Product: [Fedora] Fedora Reporter: Davide Repetto <red>
Component: mate-settings-daemonAssignee: Wolfgang Ulbrich <raveit65.sun>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 38CC: redhat-bugzilla, red
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/32b73c4450036eed02c97a066cd611e659ea404
Whiteboard: abrt_hash:d1d41e4f2a79f3b6fb2b10a652e30d9e6d1bd83d;VARIANT_ID=matecompiz;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-05-28 13:48:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: proc_pid_status
none
File: maps
none
File: limits
none
File: environ
none
File: open_fds
none
File: mountinfo
none
File: os_info
none
File: cpuinfo
none
File: core_backtrace
none
File: dso_list
none
File: backtrace none

Description Davide Repetto 2023-08-10 14:55:37 UTC 
Description of problem:
Logged out and then in again, and I got this notification-

Version-Release number of selected component:
mate-settings-daemon-1.26.1-1.fc38

Additional info:
reporter:       libreport-2.17.11
type:           CCpp
reason:         mate-settings-daemon killed by SIGABRT
journald_cursor: s=a1dade94b8ee438d8e1dbe367998b007;i=c9845;b=e533e801dd664ba588b20799a5f22e84;m=172289a43a;t=60292bc8574a1;x=bae15b81a75823ac
executable:     /usr/libexec/mate-settings-daemon
cmdline:        /usr/libexec/mate-settings-daemon
cgroup:         0::/user.slice/user-1000.slice/session-2.scope
rootdir:        /
uid:            1000
kernel:         6.4.8-200.fc38.x86_64
package:        mate-settings-daemon-1.26.1-1.fc38
runlevel:       N 5
backtrace_rating: 4
crash_function: _IO_file_doallocate
comment:        Logged out and then in again, and I got this notification-

Truncated backtrace:
Thread no. 1 (28 frames)
 #9 _IO_file_doallocate at filedoalloc.c:101
 #10 _IO_doallocbuf at /usr/src/debug/glibc-2.37-4.fc38.x86_64/libio/libioP.h:946
 #12 _IO_file_xsgetn at fileops.c:1287
 #13 __fread_unlocked at iofread_u.c:40
 #14 __tzfile_read at tzfile.c:186
 #15 tzset_internal at tzset.c:405
 #16 __tz_convert at tzset.c:577
 #17 localtime at localtime.c:54
 #18 g_log_writer_format_fields at ../glib/gmessages.c:2316
 #19 g_log_writer_standard_streams at ../glib/gmessages.c:2602
 #26 msd_housekeeping_manager_stop at /usr/src/debug/mate-settings-daemon-1.26.1-1.fc38.x86_64/plugins/housekeeping/msd-housekeeping-manager.c:298
 #27 msd_housekeeping_manager_finalize at /usr/src/debug/mate-settings-daemon-1.26.1-1.fc38.x86_64/plugins/housekeeping/msd-housekeeping-manager.c:271
 #30 msd_housekeeping_plugin_finalize at /usr/src/debug/mate-settings-daemon-1.26.1-1.fc38.x86_64/plugins/housekeeping/msd-housekeeping-plugin.c:62
 #33 mate_settings_plugin_info_finalize at /usr/src/debug/mate-settings-daemon-1.26.1-1.fc38.x86_64/mate-settings-daemon/mate-settings-plugin-info.c:99
 #36 g_slist_foreach at ../glib/gslist.c:887
 #37 _unload_all at /usr/src/debug/mate-settings-daemon-1.26.1-1.fc38.x86_64/mate-settings-daemon/mate-settings-manager.c:302
 #38 mate_settings_manager_stop at /usr/src/debug/mate-settings-daemon-1.26.1-1.fc38.x86_64/mate-settings-daemon/mate-settings-manager.c:379
 #39 on_session_end at /usr/src/debug/mate-settings-daemon-1.26.1-1.fc38.x86_64/mate-settings-daemon/main.c:267
 #40 ffi_call_unix64 at ../src/x86/unix64.S:104
 #41 ffi_call_int at ../src/x86/ffi64.c:673
 #42 ffi_call at ../src/x86/ffi64.c:710
 #43 g_cclosure_marshal_generic at ../gobject/gclosure.c:1536
 #44 marshal_dbus_message_to_g_marshaller at /usr/src/debug/dbus-glib-0.112-5.fc38.x86_64/dbus/dbus-gproxy.c:1744
 #46 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3812
 #49 dbus_g_proxy_emit_remote_signal at /usr/src/debug/dbus-glib-0.112-5.fc38.x86_64/dbus/dbus-gproxy.c:1797
 #50 dbus_g_proxy_manager_filter at /usr/src/debug/dbus-glib-0.112-5.fc38.x86_64/dbus/dbus-gproxy.c:1358
 #57 g_main_context_iterate.isra.0 at ../glib/gmain.c:4276
 #59 gtk_main at ../gtk/gtkmain.c:1329
Comment 1 Davide Repetto 2023-08-10 14:55:41 UTC 
Created attachment 1982792 [details]
File: proc_pid_status
Comment 2 Davide Repetto 2023-08-10 14:55:42 UTC 
Created attachment 1982793 [details]
File: maps
Comment 3 Davide Repetto 2023-08-10 14:55:43 UTC 
Created attachment 1982794 [details]
File: limits
Comment 4 Davide Repetto 2023-08-10 14:55:45 UTC 
Created attachment 1982795 [details]
File: environ
Comment 5 Davide Repetto 2023-08-10 14:55:46 UTC 
Created attachment 1982796 [details]
File: open_fds
Comment 6 Davide Repetto 2023-08-10 14:55:47 UTC 
Created attachment 1982797 [details]
File: mountinfo
Comment 7 Davide Repetto 2023-08-10 14:55:49 UTC 
Created attachment 1982798 [details]
File: os_info
Comment 8 Davide Repetto 2023-08-10 14:55:50 UTC 
Created attachment 1982799 [details]
File: cpuinfo
Comment 9 Davide Repetto 2023-08-10 14:55:51 UTC 
Created attachment 1982800 [details]
File: core_backtrace
Comment 10 Davide Repetto 2023-08-10 14:55:52 UTC 
Created attachment 1982801 [details]
File: dso_list
Comment 11 Davide Repetto 2023-08-10 14:55:54 UTC 
Created attachment 1982802 [details]
File: backtrace
Comment 12 Aoife Moloney 2024-05-28 13:48:02 UTC 
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

Fedora Linux 38 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.