https://bugzilla.redhat.com/show_bug.cgi?id=2267831
Bug ID: 2267831 Summary: [abrt] nemo: nemo_global_preferences_get_mono_font_family_match(): nemo killed by SIGSEGV Product: Fedora Version: 38 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:0588c901cdc12490c9e61566d51c7c3a3a170659;VAR IANT_ID=cinnamon; Component: nemo Assignee: leigh123linux@googlemail.com Reporter: david.wells5@ntlworld.com QA Contact: extras-qa@fedoraproject.org CC: epel-packagers-sig@lists.fedoraproject.org, leigh123linux@googlemail.com, riehecky@fnal.gov Target Milestone: --- Classification: Fedora
Description of problem: Developed on Sat - no system updates or changes made prior to onset. Problem is that with Fedora 38 Cinnamon spin the file manager crashes when trying to start and generates the attached error. I have rolled back the Nemo version and this does not fix the issue. I also tried with an earlier kernel instance and that did not fix things either. Tried reseting Nemo settings to defaults and that didn't work. What is strange is that when logged in as a user the issue happens whether I run Nemo from a terminal window or from menus or clicking on a folder on the desktop. However, if I run Nemo from a terminal window using sudo it starts up and works, though there are some warnings in the terminal window: $ sudo nemo Swipe your right index finger across the fingerprint reader ERROR SET META:15 Setting attribute metadata::nemo-list-view-sort-column not supported ERROR SET META:15 Setting attribute metadata::nemo-list-view-sort-reversed not supported ERROR SET META:15 Setting attribute metadata::nemo-list-view-zoom-level not supported
The machine is a Thinkpad T440P with an internal M2 SSD and two 2.5" 1TB internal SSD drives. Native OS is Fedora 38 with VirtualBox being used to support W10 and W7 VMs when needed. Fedora/Cinnamon has been stable on this machine for years so I doubt it's a hardware issue.
Any suggestions on what to do next would be welcome.
Dave
Version-Release number of selected component: nemo-6.0.2-1.fc38
Additional info: reporter: libreport-2.17.11 journald_cursor: s=56d1aca382704fcbb0916f6eb1e1a23d;i=8c24a;b=85e7a3373a3e4d958bcccc7387fa1800;m=7e594c1c;t=612be591db3e9;x=4a6fea010c345d72 cmdline: /usr/bin/nemo /home/dave kernel: 6.7.6-100.fc38.x86_64 package: nemo-6.0.2-1.fc38 runlevel: N 5 uid: 1000 executable: /usr/bin/nemo type: CCpp backtrace_rating: 4 reason: nemo killed by SIGSEGV cgroup: 0::/user.slice/user-1000.slice/session-2.scope rootdir: / crash_function: nemo_global_preferences_get_mono_font_family_match
Truncated backtrace: Thread no. 1 (14 frames) #0 nemo_global_preferences_get_mono_font_family_match at ../libnemo-private/nemo-global-preferences.c:382 #1 update_date_fonts at ../src/nemo-list-view.c:2443 #2 create_and_set_up_tree_view at ../src/nemo-list-view.c:2733 #3 nemo_list_view_init at ../src/nemo-list-view.c:4345 #4 g_type_create_instance at ../gobject/gtype.c:1983 #5 g_object_new_internal at ../gobject/gobject.c:2246 #7 g_object_new_valist at ../gobject/gobject.c:2585 #9 nemo_view_factory_create at ../src/nemo-view-factory.c:70 #10 create_content_view at ../src/nemo-window-manage-views.c:1056 #11 got_file_info_for_view_selection_callback at ../src/nemo-window-manage-views.c:951 #12 call_ready_callbacks_at_idle at ../libnemo-private/nemo-directory-async.c:1851 #16 g_main_context_iterate.isra.0 at ../glib/gmain.c:4276 #17 g_main_context_iteration at ../glib/gmain.c:4343 #18 g_application_run at ../gio/gapplication.c:2573
https://bugzilla.redhat.com/show_bug.cgi?id=2267831
David Wells david.wells5@ntlworld.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|unspecified |medium
https://bugzilla.redhat.com/show_bug.cgi?id=2267831
--- Comment #13 from David Wells david.wells5@ntlworld.com --- More input.
If I create a new account on the machine and log in to that account nemo works fine, So, I assume that something has changed in my normal account that triggers nemo to crash when it starts up. This would explain why the issues starting was not related to doing software updates. Also fits with the fact that if I run nemo using sudo when logged in to my regular account it also works.
Any thoughts on where to look in my normal account for something that triggers this behaviour in nemo?
Dave
https://bugzilla.redhat.com/show_bug.cgi?id=2267831
leigh scott leigh123linux@googlemail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Doc Type|--- |If docs needed, set a value
--- Comment #14 from leigh scott leigh123linux@googlemail.com --- Try running this as standard user in the affected account
gsettings reset org.gnome.desktop.interface monospace-font-name
https://bugzilla.redhat.com/show_bug.cgi?id=2267831
David Wells david.wells5@ntlworld.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|medium |low
--- Comment #15 from David Wells david.wells5@ntlworld.com --- Scott, thanks for the suggestion. I actually managed to resolve the problem last night so I can't test your suggestion now but I suspect it may have resolved the issue. I still think the way the software handles things is a bug but having figured our what external issue triggers the crash I've corrected that and things are now working.
What I did was compare settings in my normal account with those in the root account (in which nemo ran without a problem). The sequence of steps is shown below:
gsettings list-recursively org.nemo.preferences
showed org.nemo.preferences date-font-choice 'auto-mono' as the font setting
If I looked at the fonts installed in my default account
fc-list | grep mono
it came up with no result, the same command on the root account showed multiple fonts with "mono" in the name
So, I then used DNF in my normal account to install google-go-mono-fonts and after doing that nemo ran without a problem.
So, whatever happened on Saturday must have removed the mono fonts from my normal account and once they where gone nemo started crashing. Restoring the fonts stops nemo crashing and it now runs fine.
IMHO the code should be a bit more resilient in the case where it can't find the configured font. Either giving an informative error message and exiting gracefully rather than crashing. Or, use one of the faults that is available and give a warning that this is being done and may result in format issues for text showing file details.
With regard to your suggestion. I had run the following early in the debug process and it had no effect so if this would achieve the same outcome as your suggestion then it wouldn't have helped.
reset-recursively org.nemo
Essentially the nemo settings hadn't changed when the problem occurred, the issue was the font that nemo was configured to use was no longer present.
Hope this makes sense. I've changed the bug priority to low as the workaround to the issue that causes nemo to crash is simple to do.
https://bugzilla.redhat.com/show_bug.cgi?id=2267831
--- Comment #16 from David Wells david.wells5@ntlworld.com --- Should have read the previous comment before hitting save. Correction to the second suggestion on action to take:
Or, use one of the fonts that is available and give a warning that this is being done and may result in format issues for text showing file details.
https://bugzilla.redhat.com/show_bug.cgi?id=2267831
Aoife Moloney amoloney@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution|--- |EOL Last Closed| |2024-05-31 09:17:01
--- Comment #17 from Aoife Moloney amoloney@redhat.com --- 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.
epel-packagers-sig@lists.fedoraproject.org