Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: PC frozewhilst was using Darktable.. powerdevil, kactivitymanagerd solaar, gdb and Darktable all appearto have crashed at the same time according to ABRT. After a hard restart I had some funky graphics (i.e. flashing menues and dialogs) untill after perfoming a second restart. Version-Release number of selected component: gdb-headless-7.12-36.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: gdb /usr/bin/darktable 31415 -batch -ex 'set logging on /tmp/darktable_bt_IIULUY.txt' -x /usr/share/darktable/gdb_commands crash_function: dump_core executable: /usr/libexec/gdb global_pid: 31500 kernel: 4.9.2-200.fc25.x86_64 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 dump_core at ../../gdb/utils.c:568 #3 gdb_demangle_signal_handler at ../../gdb/cp-support.c:1521 #5 d_print_comp at ../../libiberty/cp-demangle.c:5594 #6 d_print_comp_inner at ../../libiberty/cp-demangle.c:5156 #7 d_print_comp at ../../libiberty/cp-demangle.c:5594 #8 d_print_comp_inner at ../../libiberty/cp-demangle.c:4706 #9 d_print_comp at ../../libiberty/cp-demangle.c:5594 #10 d_print_comp_inner at ../../libiberty/cp-demangle.c:5156 #11 d_print_comp at ../../libiberty/cp-demangle.c:5594 #12 d_print_comp_inner at ../../libiberty/cp-demangle.c:5168
Created attachment 1243325 [details] File: backtrace
Created attachment 1243326 [details] File: cgroup
Created attachment 1243327 [details] File: core_backtrace
Created attachment 1243328 [details] File: dso_list
Created attachment 1243329 [details] File: environ
Created attachment 1243330 [details] File: limits
Created attachment 1243331 [details] File: maps
Created attachment 1243332 [details] File: mountinfo
Created attachment 1243333 [details] File: namespaces
Created attachment 1243334 [details] File: open_fds
Created attachment 1243335 [details] File: proc_pid_status
Created attachment 1243336 [details] File: var_log_messages
*** This bug has been marked as a duplicate of bug 1367131 ***
There was also a system crash - unreportable due to vbox modules tainting the kernel. All the others were unreportable due to incomplete data or an unusable backtrace.