Version-Release number of selected component: NetworkManager-0.9.9.0-45.git20131003.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/sbin/NetworkManager --no-daemon crash_function: magazine_chain_pop_head executable: /usr/sbin/NetworkManager kernel: 3.16.6-200.fc20.i686 runlevel: N 5 type: CCpp uid: 0 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_list_append at glist.c:232 #4 g_queue_push_tail at gqueue.c:419 #5 ik_process_events at inotify-kernel.c:560 #6 ik_process_eq_callback at inotify-kernel.c:573 #11 g_main_context_iteration at gmain.c:3774 #12 glib_worker_main at gmain.c:5473 #13 g_thread_proxy at gthread.c:798 Potential duplicate: bug 697299
Created attachment 948314 [details] File: backtrace
Created attachment 948315 [details] File: cgroup
Created attachment 948316 [details] File: core_backtrace
Created attachment 948317 [details] File: dso_list
Created attachment 948318 [details] File: environ
Created attachment 948319 [details] File: limits
Created attachment 948320 [details] File: maps
Created attachment 948321 [details] File: open_fds
Created attachment 948322 [details] File: proc_pid_status
Created attachment 948323 [details] File: var_log_messages
Created attachment 948324 [details] File: exploitable
This looks like a problem in glib2 library. /usr/lib/libglib-2.0.so.0.3800.2 glib2-2.38.2-2.fc20.i686 (Fedora Project) Any chance you are able to reproduce the problem?
I have this problem once and i don't know how to reproduce it.