[Bug 306144] Re: evince segmentation fault

2010-09-16 Thread Bug Watch Updater
** Changed in: evince Status: Invalid = Unknown ** Changed in: evince Importance: Unknown = Critical -- evince segmentation fault https://bugs.launchpad.net/bugs/306144 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. --

[Bug 306144] Re: evince segmentation fault

2009-01-19 Thread Sebastien Bacher
the new version has been uploaded to jaunty now ** Changed in: poppler (Ubuntu) Status: Fix Committed = Fix Released -- evince segmentation fault https://bugs.launchpad.net/bugs/306144 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 306144] Re: evince segmentation fault

2009-01-12 Thread Sebastien Bacher
that's a poppler bug fixed upstream now ** Changed in: poppler (Ubuntu) Sourcepackagename: evince = poppler Status: Incomplete = Fix Committed -- evince segmentation fault https://bugs.launchpad.net/bugs/306144 You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 306144] Re: evince segmentation fault

2009-01-06 Thread Bug Watch Updater
** Changed in: evince Status: Unknown = Invalid -- evince segmentation fault https://bugs.launchpad.net/bugs/306144 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

[Bug 306144] Re: evince segmentation fault

2008-12-22 Thread Dimitrios Symeonidis
leandro, you are the reporter of the other bug, which is confirmed, reported upstream and fix committed. no need to report this anywhere else... -- evince segmentation fault https://bugs.launchpad.net/bugs/306144 You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 306144] Re: evince segmentation fault

2008-12-22 Thread Dimitrios Symeonidis
changed upstream assignment, as original upstream report was marked as duplicate ** Changed in: evince Bugwatch: GNOME Bug Tracker #563638 = GNOME Bug Tracker #555375 -- evince segmentation fault https://bugs.launchpad.net/bugs/306144 You received this bug notification because you are a

[Bug 306144] Re: evince segmentation fault

2008-12-12 Thread Leandro
I have reported a similar bug here: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/307435 Since the only error message is a segmentation fault, I cannot say if this is a duplicate or not. Anyway, there I have attached the pdf file that causes the crash. -- evince segmentation fault

[Bug 306144] Re: evince segmentation fault

2008-12-08 Thread Pedro Villavicencio
thanks for the report, could you attach the pdf file to the report? thanks. ** Changed in: evince (Ubuntu) Importance: Undecided = Medium Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs) Status: New = Incomplete -- evince segmentation fault

[Bug 306144] Re: evince segmentation fault

2008-12-08 Thread Elias K Gardner
As mentioned above the file is from jstor and according to my reading of the terms of use I am not allowed to post the pdf file. I have sent them a message and will see if I can post the file or a similar one that causes crashes so that we can solve the issue. -- evince segmentation fault

[Bug 306144] Re: evince segmentation fault

2008-12-07 Thread Elias K Gardner
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/20295733/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/20295735/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/20295737/ProcStatus.txt -- evince

[Bug 306144] Re: evince segmentation fault

2008-12-07 Thread Elias K Gardner
I guess the most likely cause of this is really a bad pdf being distributed by jstor. I will look into contacting them as well. -- evince segmentation fault https://bugs.launchpad.net/bugs/306144 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 306144] Re: evince segmentation fault

2008-12-07 Thread Elias K Gardner
Success1! I have gotten the 4th page to open with pdf edit without it crashing. I reported this upstream to evince (link above). I also email jstor will have to wait to see what their response is. If I get a chance I will ask if there is some way I can get a pdf from them that crashes that i can