Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 90811 - app-text/djvu-3.5.14 segfaults after printing
Summary: app-text/djvu-3.5.14 segfaults after printing
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Text-Markup Team (OBSOLETE)
URL: http://sourceforge.net/tracker/index....
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-28 19:15 UTC by Pablo De Nápoli
Modified: 2006-05-30 00:54 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
gdb session showing the bug (djvu-bug.txt,2.71 KB, text/plain)
2005-04-28 19:16 UTC, Pablo De Nápoli 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Pablo De Nápoli 2005-04-28 19:15:44 UTC 
app-text/djvu-3.5.14 crashes with a segfault after printing "custom pages"
but the pages get printed.
I'm using net-print/cups-1.1.23-r1 and a local printer (HP640C)
As an atachment I'm sending to you a gdb session that shows the point
at which the program segfaults.
I've reported this bug to upstream mantainers, but I've received no
answer. Is anyone actually mantaining this package?



Reproducible: Always
Steps to Reproduce:
1.open your favourite djvu file 
2.select print page / of the custom pages / and some custom pages like "1,2,3" 
3.choose printer / command "lp" and press "Ok"


Actual Results:  
the pages are printed but after that the program crashes with a  
segmentation fault. 


the program shouldn't crash!
Comment 1 Pablo De Nápoli 2005-04-28 19:16:21 UTC 
Created attachment 57533 [details]
gdb session showing the bug
Comment 2 Martin Ehmsen (RETIRED) gentoo-dev 2006-05-03 02:22:31 UTC 
Does this still happen with the latest version (3.5.17)?!?
Are you using stable or unstable arch? (you forgot the output of emerge --info)
Comment 3 Martin Ehmsen (RETIRED) gentoo-dev 2006-05-11 00:54:07 UTC 
Your upstream bug was closed due to no response from you.
When (if at all) you can reproduce this bug with the latests version of djvu then feel free reopen this bug and the upstream bug.
Comment 4 Serge Gavrilov 2006-05-30 00:54:39 UTC 
I also discovered this bug in 3.5.16. After upgrading to 3.5.17 the bug has disappeared.