Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: I started settings. Version-Release number of selected component: control-center-3.16.2-1.fc22 Additional info: reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: gnome-control-center --overview crash_function: talloc_abort executable: /usr/bin/gnome-control-center global_pid: 17479 kernel: 4.0.4-301.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 var_log_messages: [System Logs]:\n-- Logs begin at Чт 2015-05-28 10:24:10 MSK, end at Пт 2015-05-29 16:10:41 MSK. -- Truncated backtrace: Thread no. 1 (10 frames) #2 talloc_abort at ../talloc.c:340 #3 talloc_abort_unknown_value at ../talloc.c:364 #4 talloc_chunk_from_ptr at ../talloc.c:383 #5 _talloc_free at ../talloc.c:1572 #6 gfree_charcnv at ../source3/lib/charcnv.c:30 #7 gfree_all at ../source3/lib/util.c:86 #8 SMBC_module_terminate at ../source3/libsmb/libsmb_context.c:128 #9 smbc_free_context at ../source3/libsmb/libsmb_context.c:333 #10 _pp_samba_get_devices_thread at pp-samba.c:492 #11 run_in_thread at gsimpleasyncresult.c:858
Created attachment 1032096 [details] File: backtrace
Created attachment 1032097 [details] File: cgroup
Created attachment 1032098 [details] File: core_backtrace
Created attachment 1032099 [details] File: dso_list
Created attachment 1032100 [details] File: environ
Created attachment 1032101 [details] File: limits
Created attachment 1032102 [details] File: maps
Created attachment 1032103 [details] File: mountinfo
Created attachment 1032104 [details] File: namespaces
Created attachment 1032105 [details] File: open_fds
Created attachment 1032106 [details] File: proc_pid_status
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.