Alex Rampp, thank you for reporting this and helping make Ubuntu better. Oneiric reached EOL on May 9, 2013. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases
Is this an issue on a supported release? If so, please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal: cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo service apport start force_start=1 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line: sudo nano /etc/apport/crashdb.conf and comment out the line: 'problem_types': ['Bug', 'Package'], by changing it to: # 'problem_types': ['Bug', 'Package'], Save, close, and try to file the crash report again via: ubuntu-bug /var/crash/_my_crash_report.crash I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Please do not attach your crash report manually to this report and reopen it. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: evince (Ubuntu) Status: New => Invalid ** Attachment removed: "Core dump when evince segfaulted" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/916152/+attachment/2672950/+files/core.2210.bz2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/916152 Title: Segmentation Fault Status in evince package in Ubuntu: Invalid Bug description: Sometimes (not deterministically reproducable) evince crashes with a segmentation fault. The problem does not depend on the document opened, it also occures with no document opened. On console I get the following error messages: (evince:2210): Gtk-WARNING **: Theme parsing error: gtk- buttons.css:159:10: Expected valid border (evince:2210): Gtk-WARNING **: Theme parsing error: gtk- bars.css:102:16: Themeing engine 'adwaita' not found (evince:2210): Gtk-WARNING **: Theme parsing error: gtk- bars.css:117:16: Themeing engine 'adwaita' not found (evince:2210): Gtk-WARNING **: Theme parsing error: gtk- bars.css:134:16: Themeing engine 'adwaita' not found (evince:2210): Gtk-WARNING **: Theme parsing error: gtk- bars.css:153:16: Themeing engine 'adwaita' not found (evince:2210): Gtk-WARNING **: Theme parsing error: gtk- bars.css:165:16: Themeing engine 'adwaita' not found (evince:2210): Gtk-WARNING **: Theme parsing error: gtk- bars.css:175:16: Themeing engine 'adwaita' not found (evince:2210): Gtk-WARNING **: Theme parsing error: gtk- bars.css:186:16: Themeing engine 'adwaita' not found (evince:2210): Gtk-WARNING **: Theme parsing error: gtk- bars.css:198:16: Themeing engine 'adwaita' not found (evince:2210): Gtk-WARNING **: Theme parsing error: gtk- bars.css:208:16: Themeing engine 'adwaita' not found (evince:2210): Gtk-WARNING **: Theme parsing error: gtk- bars.css:218:16: Themeing engine 'adwaita' not found (evince:2210): Gtk-WARNING **: Theme parsing error: gtk- bars.css:223:16: Themeing engine 'adwaita' not found I reproduced the segfault in gdb, perhaps here is some useful infoman to you: (gdb) bt #0 0x00007f893801cc2a in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007f8938f14cb5 in g_param_spec_pool_lookup () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #2 0x00007f8938f0f201 in g_object_set_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #3 0x00007f8938f10057 in g_object_set () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #4 0x00007f893b7dff40 in ?? () #5 0x00007f8938f2b373 in g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #6 0x00007f8938f0b5ac in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #7 0x00007f8938f0de94 in g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #8 0x00007f8938f0ed66 in g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #9 0x00007f8938f0f074 in g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #10 0x00007f893b7e13d3 in ?? () #11 0x00007f893b7cc3c3 in ?? () #12 0x00007f893b7c7c0a in main () (gdb) info frame Stack level 0, frame at 0x7fffac59f0c0: rip = 0x7f893801cc2a; saved rip 0x7f8938f14cb5 called by frame at 0x7fffac59f1a0 Arglist at 0x7fffac59f0b0, args: Locals at 0x7fffac59f0b0, Previous frame's sp is 0x7fffac59f0c0 Saved registers: rip at 0x7fffac59f0b8 (gdb) info registers rax 0x1 1 rbx 0x7f893c74db10 140227401538320 rcx 0x2c9 713 rdx 0x7f893cc2a060 140227406635104 rsi 0xffffffff 4294967295 rdi 0x2c0 704 rbp 0x2c9 0x2c9 rsp 0x7fffac59f0b8 0x7fffac59f0b8 r8 0x7f893c74db18 140227401538328 r9 0x8a2 2210 r10 0x1 1 r11 0x1 1 r12 0x7f8938ad0828 140227338111016 r13 0x7f8938ad0840 140227338111040 r14 0x7f8938345000 140227330199552 r15 0x7f893cc2a060 140227406635104 rip 0x7f893801cc2a 0x7f893801cc2a eflags 0x10286 [ PF SF IF RF ] cs 0x33 51 ss 0x2b 43 ds 0x0 0 es 0x0 0 fs 0x0 0 gs 0x0 0 I also attached a core dump My System is a Lubuntu 11.10 with current patch level. If I can help you with further information please write a comment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/916152/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
