Weird thing this morning. I boot up the computer. Log in to Fedora. I am on the MATE spin. It is acting quite slow. The panel and desktop background show up but then nothing else for a bit. I get a message that the mate-settings-daemon has crashed. Everything still seems to be working but I do a reboot anywyay and then things are coming up just fine and everything appears to be OK. I am wondering how I can get back to those messages because it was showing a couple other MATE related things that had recently crashed. I did file a bug report.
Is there a way to bring up those error messages in that graphical way that I saw when it happened? Because if I attempt to use journalctl, I am getting stuff from way back in October and I don’t need that. I just need what happened today. Also in the graphical error report it was showing a couple of other errors.
Maybe use journalctl -g mate to see anything related to mate for some time back.
Adding in a boot option -b N would allow you to see what has happened with each past boot. (“-b 0” is the current boot and “-b -1” is the last boot, with -N going backwards one boot at a time.)
Use man journalctl to see the many ways that command can be used.
Thank you. I take it there is no way to get back to the graphical representation of those crashes. Because that was a lot easier. But I will try what you said. I did do the man journalctl command but there was just a lot of stuff there as always.
This is the graphical report I am talking about. Looks like this…
OK. I put those commands in the terminal and a whole lot of stuff came up. Including a core dump. Not sure what to make of all that. I can have my son look at it later. I just don’t have the technical knowledge to understand most of that. A lot of information there and maybe my son will see something. Of course the thing I don’t quite understand is that the computer still appeared to be working OK but I didn’t really test that out because I just rebooted for good measure.
Found this line…
Nov 24 07:36:40 fedora abrt-notification[3111]: [🡕] Process 1600 (mate-settings-daemon) crashed in g_assertion_message_expr.cold()
Kind of just stuck right now in not figuring out what happened or why. My son even took a look but I don’t think anything jumped out at him. There was a core dump and stack traces for each core (6 of them). After the reboot everything seems to be fine. Will monitor the bug report and post up any more information that I come up with.
I have been previously instructed not to paste a screenshot here. But that was where I got my initial information and now I can not get back to it. Even my son didn’t know what that was called or how to get it back up. Does anyone know? It’s called the Problem Reporting Tool. Does it only come up when something crashes or can it be called up?
Gui messages are often not detailed enough for full analysis, so they are more of an alert than a real troubleshooting tool.
It is always preferable to post the text that can be copied and pasted from the screen when possible. It leaves the text searchable and quotable while images are neither.
Posting the text as 'preformatted text` is done in one of 2 ways.
- copy and paste the text then highlight it and click the
</>button on the toolbar of the text entry window. - place a ``` (triple back tick) on the line immediately preceding the text and also on the line following the text.
Either method gives the same end result. The pasted text retains the same formatting as seen on screen and keeps it very readable.
When we ask for information to be posted here there is usually a very good reason.
First, the individual asking often has experience with the issue being discussed and the info requested can assist in finding an answer.
Secondly, the info can be seen by many different users, and as the old saying goes “many eyes make the problem smaller”. There are now many users potentially involved, each of which may have a different insight on the issue. Limiting the actual details to one person also limits the solution to the experience of that one person.
1 Like
The thing is… When I use journalctl - b 2 right now to go back and see what was going on, I can see when the coredump happens. Then there are a whole lot of lines of text, probably hundreds all in red. There are also stack traces for different threads. So I am not sure what I should even copy and what is important.
The coredump is showing a whole lot of modules and at the top is /usr/libexec/mate-settings-daemon. After that is about 25 stack traces of different threads.
When I look at this there are something like 25 different stack traces for different threads and something like 300 lines of text there.
For example, here is the stack trace for the first thread that shows up. At the bottom is a reference to mate-settings-daemon.
Stack trace of thread 1600:
#0 0x00007fc222f573cc __pthread_kill_implementation (libc.so.6 + 0x743cc)
#1 0x00007fc222efd18e raise (libc.so.6 + 0x1a18e)
#2 0x00007fc222ee46d0 abort (libc.so.6 + 0x16d0)
#3 0x00007fc2230d9482 g_assertion_message.cold (libglib-2.0.so.0 + 0x2482)
#4 0x00007fc22314a727 g_assertion_message_expr (libglib-2.0.so.0 + 0x73727)
#5 0x00007fc1fb528a93 glib_io_free (libpulse-mainloop-glib.so.0 + 0xa93)
#6 0x00007fc21040c791 delete_events (libpulsecommon-17.0.so + 0x19791)
#7 0x00007fc21040cd1a pa_iochannel_free (libpulsecommon-17.0.so + 0x19d1a)
#8 0x00007fc21042cf6d pa_pstream_unlink (libpulsecommon-17.0.so + 0x39f6d)
#9 0x00007fc21047e584 context_unlink (libpulse.so.0 + 0x7584)
#10 0x00007fc21047ed58 pa_context_set_state (libpulse.so.0 + 0x7d58)
#11 0x00007fc21047f10c pa_context_handle_error (libpulse.so.0 + 0x810c)
#12 0x00007fc2104809c8 setup_complete_callback (libpulse.so.0 + 0x99c8)
#13 0x00007fc210426802 run_action (libpulsecommon-17.0.so + 0x33802)
#14 0x00007fc1fb52981f dispatch_func (libpulse-mainloop-glib.so.0 + 0x181f)
#15 0x00007fc2231182a3 g_main_context_dispatch_unlocked.lto_priv.0 (libglib-2.0.so.0 + 0x412a3)
#16 0x00007fc2231211f8 g_main_context_iterate_unlocked.isra.0 (libglib-2.0.so.0 + 0x4a1f8)
#17 0x00007fc22312149f g_main_loop_run (libglib-2.0.so.0 + 0x4a49f)
#18 0x00007fc223585da5 gtk_main (libgtk-3.so.0 + 0x185da5)
#19 0x000056038fcff472 main (/usr/libexec/mate-settings-daemon + 0x1472)
#20 0x00007fc222ee65b5 __libc_start_call_main (libc.so.6 + 0x35b5)
#21 0x00007fc222ee6668 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x3668)
#22 0x000056038fcff645 _start (/usr/libexec/mate-settings-daemon + 0x1645)
Of course today I boot the machine up just fine. No errors at all and the desktop loads up just fine as well. Will monitor to see if it occurs again…