Description of problem: Started nautilus and clicked on my Google account to open the Google Drive directory. Desktop completely crashed, eventually leaving me on a black screen. (I had to switch to a terminal and back to see the "shield" screen, which didn't open with 'Enter' but required me to swipe up with the mouse.) Version-Release number of selected component: GConf2-3.2.6-19.fc27 Additional info: reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/gconfd-2 crash_function: magazine_cache_trim executable: /usr/libexec/gconfd-2 journald_cursor: s=52b9622599c149f3b2bcedca8f7b4442;i=1c83383;b=a541034617c64795bef90bbf3547779d;m=ff1b14aafb;t=564a0d521f41c;x=756f7b05311cdc7e kernel: 4.14.14-300.fc27.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 magazine_cache_trim at gslice.c:649 #1 magazine_cache_push_magazine at gslice.c:710 #2 thread_memory_magazine2_unload at gslice.c:809 #3 g_slice_free_chain_with_offset at gslice.c:1199 #4 g_slist_free at gslist.c:137 #5 markup_dir_free at markup-tree.c:305 #9 markup_tree_unref at markup-tree.c:197 #10 ms_destroy at markup-backend.c:930 #11 destroy_source at markup-backend.c:785 #12 gconf_source_free at gconf-sources.c:86 Potential duplicate: bug 1484500
Created attachment 1392740 [details] File: backtrace
Created attachment 1392741 [details] File: cgroup
Created attachment 1392742 [details] File: core_backtrace
Created attachment 1392743 [details] File: cpuinfo
Created attachment 1392744 [details] File: dso_list
Created attachment 1392745 [details] File: environ
Created attachment 1392746 [details] File: exploitable
Created attachment 1392747 [details] File: limits
Created attachment 1392748 [details] File: maps
Created attachment 1392749 [details] File: mountinfo
Created attachment 1392750 [details] File: open_fds
Created attachment 1392751 [details] File: proc_pid_status
*** Bug 1560835 has been marked as a duplicate of this bug. ***
*** Bug 1571995 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.