OK this is the backtrace log I generated using the method that you
described. but this time when I run evince through gdb it doesn't crash
immediately. the program just getting non responsive. the only thing I
can do is force quit it. but I performed the steps you've mentioned
anyway and as soon as I type 't a a bt f' at the gdb prompt,evince
quits.

Here are some lines that for some reason not included in the backtrace log I 
find suspicious. (These lines appear in my terminal, I'm copy pasting this from 
there)
------------------------------
(gdb) r
Starting program: /usr/bin/evince Networking\ Self-teaching\ Guide.pdf
[Thread debugging using libthread_db enabled]
[New Thread 0xb6eaf750 (LWP 5848)]
[New Thread 0xb6b75b90 (LWP 5851)]
[New Thread 0xb5f37b90 (LWP 5852)]
Error (9360116): Dictionary key must be a name object
Error (9360260): Bad 'Length' attribute in stream
Error (0): Call to Object where the object was type 11, not the expected type 8

Program received signal SIGABRT, Aborted.
[Switching to Thread 0xb6b75b90 (LWP 5851)]
0xb8061430 in __kernel_vsyscall ()
-------------------------------

According to this, the program has received SIGABRT , Which I can't figure out 
received from where.
also I've renamed the pdf file which I have problems viewing and opened it 
using evince but the result was same. it quits immediately.

** Attachment added: "backtrace.log"
   http://launchpadlibrarian.net/33096038/backtrace.log

-- 
evince crashes immediately after loading a document
https://bugs.launchpad.net/bugs/440382
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to