Hide Forgot
Version-Release number of selected component: nemo-2.0.8-1.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: nemo -n crash_function: magazine_chain_pop_head executable: /usr/bin/nemo kernel: 3.12.5-302.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 magazine_chain_pop_head at gslice.c:545 #1 thread_memory_magazine1_alloc at gslice.c:848 #2 g_slice_alloc at gslice.c:1007 #3 g_slice_alloc0 at gslice.c:1042 #4 g_source_new at gmain.c:856 #5 g_idle_source_new at gmain.c:5272 #6 emit_in_idle at gfilemonitor.c:426 #7 rate_limiter_send_virtual_changes_done_now at gfilemonitor.c:476 #8 foreach_rate_limiter_fire at gfilemonitor.c:558 #9 g_hash_table_foreach_remove_or_steal at ghash.c:1410
Created attachment 839892 [details] File: backtrace
Created attachment 839893 [details] File: cgroup
Created attachment 839894 [details] File: core_backtrace
Created attachment 839895 [details] File: dso_list
Created attachment 839896 [details] File: environ
Created attachment 839897 [details] File: limits
Created attachment 839898 [details] File: maps
Created attachment 839899 [details] File: open_fds
Created attachment 839900 [details] File: proc_pid_status
Created attachment 839901 [details] File: var_log_messages
Created attachment 839902 [details] File: exploitable
Another user experienced a similar problem: After I uninstalled a Cinnamon panel applet. reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: nemo -n crash_function: magazine_chain_pop_head executable: /usr/bin/nemo kernel: 3.12.8-300.fc20.x86_64 package: nemo-2.0.8-7.fc20 reason: nemo killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
*** Bug 1098334 has been marked as a duplicate of this bug. ***
It looks like a gtk issue to me, reassigning to gtk3
I don't see anything here pointing at gtk. Why do you think so ?
(In reply to Matthias Clasen from comment #15) > I don't see anything here pointing at gtk. Why do you think so ? sorry my mistake, I don't see much from nemo in the backtrace either.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.