Bug 151451

Summary:	Application crashed using edit
Product:	[Applications] digikam	Reporter:	Steve Nordstrom <sjn45>
Component:	Portability-Runtime	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	caulier.gilles
Priority:	NOR
Version:	0.9.2
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:	0.9.4
Sentry Crash Report:

Description Steve Nordstrom 2007-10-28 02:51:59 UTC

Version:           0.9.2 (using KDE KDE 3.5.7)
Installed from:    SuSE RPMs
OS:                Linux

I was editing (cropping) several pictures.
I had cropped and saved three files with no problem.
After defining the area to be cropped on the fourth picture, the application crashed.

Below is the file the digikam program presented.
I hope it helps you.

System configuration startup check disabled.

#[?1034h(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2ae8d94a98b0 (LWP 13559)]
[New Thread 0x43005950 (LWP 13632)]
[New Thread 0x42003950 (LWP 13580)]
[New Thread 0x41802950 (LWP 13579)]
[New Thread 0x40800950 (LWP 13578)]
[New Thread 0x41001950 (LWP 13574)]
(no debugging symbols found)
(no debugging symbols found)
0x00002ae8d1a69088 in ?? () from /lib64/libc.so.6
#0  0x00002ae8d1a69088 in ?? () from /lib64/libc.so.6
#1  0x00002ae8d1a0bf5e in ?? () from /lib64/libc.so.6
#2  0x00002ae8d1a08f6b in free () from /lib64/libc.so.6
#3  0x00002ae8d0d1926e in QMetaObject::~QMetaObject ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#4  0x00002ae8d0d19183 in QMetaObjectCleanUp::~QMetaObjectCleanUp ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#5  0x00002ae8d19cc37e in exit () from /lib64/libc.so.6
#6  0x00002ae8d0c667f1 in ?? () from /usr/lib/qt3/lib64/libqt-mt.so.3
#7  0x00002ae8d0615103 in KApplication::xioErrhandler ()
   from /opt/kde3/lib64/libkdecore.so.4
#8  0x00002ae8d46ea4b4 in _XIOError () from /usr/lib64/libX11.so.6
#9  0x00002ae8d46f0820 in _XPutXCBBuffer () from /usr/lib64/libX11.so.6
#10 0x00002ae8d46f17ef in _XSend () from /usr/lib64/libX11.so.6
#11 0x00002ae8d46de950 in ?? () from /usr/lib64/libX11.so.6
#12 0x00002ae8d46deb71 in XPutImage () from /usr/lib64/libX11.so.6
#13 0x00002ae8d0c8a3cb in QPixmap::convertFromImage ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#14 0x00002ae8d0d35249 in QPixmap::convertFromImage ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#15 0x00002ae8cf1836cf in Digikam::DImg::convertToPixmap ()
   from /opt/kde3/lib64/libdigikam.so.0
#16 0x00002ae8cf23f04e in Digikam::DImgInterface::paintOnDevice ()
   from /opt/kde3/lib64/libdigikam.so.0
#17 0x00002ae8cf24b3de in Digikam::Canvas::paintViewport ()
   from /opt/kde3/lib64/libdigikam.so.0
#18 0x00002ae8cf24b6bf in Digikam::Canvas::viewportPaintEvent ()
   from /opt/kde3/lib64/libdigikam.so.0
#19 0x00002ae8d0e1f611 in QScrollView::eventFilter ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#20 0x00002ae8d0d23472 in QObject::activate_filters ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#21 0x00002ae8d0d234c7 in QObject::event ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#22 0x00002ae8d0d55473 in QWidget::event ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#23 0x00002ae8d0ccd6dd in QApplication::internalNotify ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#24 0x00002ae8d0cce3be in QApplication::notify ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#25 0x00002ae8d06f13dd in KApplication::notify ()
   from /opt/kde3/lib64/libkdecore.so.4
#26 0x00002ae8d0ca3ae1 in QWidget::repaint ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#27 0x00002ae8d0ccedd5 in QApplication::sendPostedEvents ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#28 0x00002ae8d0c832bb in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#29 0x00002ae8d0ce1f53 in QEventLoop::enterLoop ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#30 0x00002ae8d0ce1e02 in QEventLoop::exec ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#31 0x00000000004032af in QGList::~QGList ()
#32 0x00002ae8d19b6b54 in __libc_start_main () from /lib64/libc.so.6
#33 0x0000000000402159 in QGList::~QGList ()
#34 0x00007fffdbdd09b8 in ?? ()
#35 0x0000000000000000 in ?? ()

Comment 1 caulier.gilles 2007-11-28 16:26:49 UTC

Steve,

Your backtrace is not suitable. Please compile digiKam using full debug and give us a new gdb backtrace.

Thanks in advance

Gilles Caulier

Comment 2 Steve Nordstrom 2007-11-28 23:36:33 UTC

I do not know how to compile Digikam using full debug.
What commands do I use?
I do not know what a gdb backtrace is. (I assume it is
similar to what I provided to you last time.)
What commands do I use?
Sorry I cannot be more help.

Newbie (can you tell?) 

--- Gilles Caulier <caulier.gilles@gmail.com> wrote:

[bugs.kde.org quoted mail]



      ____________________________________________________________________________________
Get easy, one-click access to your favorites. 
Make Yahoo! your homepage.
http://www.yahoo.com/r/hs

Comment 3 Arnd Baecker 2007-11-29 00:17:37 UTC

See http://www.digikam.org/?q=contrib under
"If you are experiencing crashes with digiKam" and
for installation instructions "http://www.digikam.org/?q=download/svn"
under "Install digiKam in your Home Directory".

Good luck, it will be a bit of a rough ride if you are installing something
like this from source the first time...

Arnd

Comment 4 caulier.gilles 2008-03-18 13:56:22 UTC

Steve,

This entry still valid using 0.9.3 ?

Gilles Caulier

Comment 5 Steve Nordstrom 2008-03-19 00:21:01 UTC

I did not crash the application (Digikam) the last
time I used it, but I am not sure I was doing the same
edit functions that I was when I had the problem
before.

Sorry.

Thanks for your inquiry.

Steve N

--- Gilles Caulier <caulier.gilles@gmail.com> wrote:

[bugs.kde.org quoted mail]



      ____________________________________________________________________________________
Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs

Comment 6 caulier.gilles 2008-03-19 06:11:35 UTC

Steve,

Thanks for the report. I close this file now. Don't hesitate to re-open if necessary in the future...

Gilles Caulier

Comment 7 Steve Nordstrom 2008-03-19 22:57:21 UTC

Gilles,
I noticed that the revision of Digikam currently in my
machine is 0.9.2.
Perhaps I have received an update which fixed the
problem.
I don't pay real close attention to what updates are
offered, I just load them.

Thanks for the inquiry.

Steve


--- Gilles Caulier <caulier.gilles@gmail.com> wrote:

[bugs.kde.org quoted mail]
----------------------------------------------------------------------------
>              Status|UNCONFIRMED                
> |RESOLVED
>          Resolution|                           
> |WORKSFORME
> 
> 
> 
> ------- Additional Comments From caulier.gilles
> gmail com  2008-03-19 06:11 -------
> Steve,
> 
> Thanks for the report. I close this file now. Don't
> hesitate to re-open if necessary in the future...
> 
> Gilles Caulier
> 




      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ