Hide Forgot
abrt version: 2.0.0 comment: it crashes on startup. Same with dconf-editor gui. A few weeks ago on an other install this tool worked flawless. executable: /usr/bin/dconf cmdline: dconf component: dconf kernel: 2.6.38.2-9.fc15.x86_64 uid: 500 reason: Process /usr/bin/dconf was killed by signal 6 (SIGABRT) architecture: x86_64 username: stefan package: dconf-0.7.3-1 os_release: Fedora release 15 (Lovelock) time: 1302015839 rating: 0 Text file: event_log, 2729 bytes Text file: smaps, 32368 bytes Binary file: coredump, 585728 bytes Text file: dsos, 4207 bytes Text file: maps, 6524 bytes backtrace ----- [New LWP 8145] warning: Corrupted shared library list warning: Corrupted shared library list warning: Corrupted shared library list warning: Corrupted shared library list Failed to read a valid object file image from memory. Core was generated by `dconf'. Program terminated with signal 6, Aborted. #0 0x00000038bc0362c5 in ?? () Thread 1 (LWP 8145): #0 0x00000038bc0362c5 in ?? () No symbol table info available. #1 0x0000000000000000 in ?? () No symbol table info available. warning: Corrupted shared library list From To Syms Read Shared Object Library 0x00000038bbc00b20 0x00000038bbc1954a Yes /lib64/ld-linux-x86-64.so.2 No symbol "__abort_msg" in current context. No symbol "__glib_assert_msg" in current context. rax 0x0 0 rbx 0x2 2 rcx 0xffffffffffffffff -1 rdx 0x6 6 rsi 0x1fd1 8145 rdi 0x1fd1 8145 rbp 0x2 0x2 rsp 0x7fff1beb8318 0x7fff1beb8318 r8 0x22cde00 36494848 r9 0x38bc12eb00 243673524992 r10 0x8 8 r11 0x206 518 r12 0x4 4 r13 0x7fff1beb8918 140733661808920 r14 0x0 0 r15 0x38be3164a0 243709076640 rip 0x38bc0362c5 0x38bc0362c5 eflags 0x206 [ PF IF ] cs 0x33 51 ss 0x2b 43 ds 0x0 0 es 0x0 0 fs 0x0 0 gs 0x0 0 No function contains program counter for selected frame.
Created attachment 490006 [details] File: event_log
Created attachment 490007 [details] File: smaps
Created attachment 490008 [details] File: dsos
Created attachment 490009 [details] File: maps
Created attachment 490010 [details] File: backtrace
*** This bug has been marked as a duplicate of bug 691364 ***