Pedro Villavicencio wrote:
> It works fine for me with intrepid in a i386 system this is maybe only
> amd64 related, can you get a backtrace as described here:
> http://wiki.ubuntu.com/DebuggingProgramCrash ; thanks a lot.
>
> ** Changed in: evince (Ubuntu)
> Importance: Undecided => Medium
> Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
> Status: New => Incomplete
Thanks for looking at this.
I installed the evince-dbgsym package, but the version of evince there
wont run. Maybe there's some step in the debugging setup that's not on
the DebuggingProgramCrash page?
I'm guessing you're not interested in a backtrace of the standard evince?
--
Sebastian Kuzminsky
"Much of what we learned from the sense of touch was unscientific
prejudice, which must be rejected if we are to have a true picture
of the world." -- Bertrand Russell
Pedro Villavicencio wrote: wiki.ubuntu. com/DebuggingPr ogramCrash ; thanks a lot.
> It works fine for me with intrepid in a i386 system this is maybe only
> amd64 related, can you get a backtrace as described here:
> http://
>
> ** Changed in: evince (Ubuntu)
> Importance: Undecided => Medium
> Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
> Status: New => Incomplete
Thanks for looking at this.
I installed the evince-dbgsym package, but the version of evince there mCrash page?
wont run. Maybe there's some step in the debugging setup that's not on
the DebuggingProgra
I'm guessing you're not interested in a backtrace of the standard evince?
--
Sebastian Kuzminsky
"Much of what we learned from the sense of touch was unscientific
prejudice, which must be rejected if we are to have a true picture
of the world." -- Bertrand Russell