gwenview crashed with SIGSEGV in KIPIPlugins::KPWriteImage::write2PNG()

Bug #408330 reported by Ofir Klinger
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
kipi-plugins
New
Undecided
Unassigned
kipi-plugins (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: kdegraphics

Trying to save a scan from my LAN scanner (DCP-540CN, which has a driver of Brother, the manufacture) causes gwenview to crash.

If more information needed, or reproducing the bug, just reply here.

ProblemType: Crash
Architecture: i386
Date: Mon Aug 3 13:40:01 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gwenview
Package: gwenview 4:4.2.98-0ubuntu2
ProcCmdline: /usr/bin/gwenview -caption Gwenview -icon gwenview
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-4.23-generic
SegvAnalysis:
 Segfault happened at: 0x829a5ec <_ZN11KIPIPlugins12KPWriteImage9write2PNGERK7QString+1708>: movzbl (%edx,%esi,1),%eax
 PC (0x0829a5ec) ok
 source "(%edx,%esi,1)" (0x09502000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: kdegraphics
StacktraceTop:
 KIPIPlugins::KPWriteImage::write2PNG(QString const&) ()
 ?? () from /usr/lib/kde4/kipiplugin_acquireimages.so
 ?? () from /usr/lib/kde4/kipiplugin_acquireimages.so
 QMetaObject::activate(QObject*, int, int, void**) ()
 QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
Title: gwenview crashed with SIGSEGV in KIPIPlugins::KPWriteImage::write2PNG()
Uname: Linux 2.6.31-4-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Ofir Klinger (klinger-ofir) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:KIPIPlugins::KPWriteImage::write2PNG (this=0xbfc60684,
KIPIAcquireImagesPlugin::ScanDialog::slotSaveImage (
KIPIAcquireImagesPlugin::ScanDialog::qt_metacall (
QMetaObject::activate (sender=0x91b6e80,
QMetaObject::activate (sender=0x91b6e80, m=0x34178e8,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in kdegraphics (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Looks like an issue with one of the kipi graphics plugins.

affects: kdegraphics (Ubuntu) → kipi-plugins (Ubuntu)
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

A fix has been committed for the next kipi-plugins release after 0.4.0.

Changed in kipi-plugins (Ubuntu):
importance: Medium → Low
status: New → Fix Committed
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Hum, gotta get lex to set kipi-plugins to not track bugs in launchpad.

Changed in kipi-plugins:
status: New → Fix Released
Revision history for this message
Ofir Klinger (klinger-ofir) wrote :

Do you want me to test the fix? will it be added to the repo?

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Should be fixed, now that we have the 0.5.0 release in.

Changed in kipi-plugins (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Got a duplicate... guess it's not fixed.

Changed in kipi-plugins (Ubuntu):
status: Fix Released → Confirmed
Changed in kipi-plugins:
status: Fix Released → New
Revision history for this message
Luka Renko (lure) wrote :

Can somebody still reproduce this with kipi-plugins 0.7.0 in Karmic?

Changed in kipi-plugins (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Luka Renko (lure) wrote :

I am closing this due to no response. Feel free to reopen if you can reproduce with recent version of kipi-plugins (for example 0.9.0 from karmic-backports).

Changed in kipi-plugins (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.