Bug 227135 - Krash of KDM when starting
Summary: Krash of KDM when starting
Status: RESOLVED DOWNSTREAM
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-16 07:40 UTC by Ulrich Van Den Hekke
Modified: 2010-02-16 12:50 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ulrich Van Den Hekke 2010-02-16 07:40:51 UTC
Application that crashed: kdmgreet
Version of the application: 
KDE Version: 4.3.4 (KDE 4.3.4)
Qt Version: 4.5.3
Operating System: Linux 2.6.32-trunk-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

What I was doing when the application crashed:
When starting KDM (but also when reading a mail in KMail, or starting Kontact) the application crash.

 -- Backtrace:
Application: unknown (kdmgreet), signal: Segmentation fault
The current source language is "auto; currently c".
[KCrash Handler]
#4  0x00000000012a5468 in ?? ()
#5  0x00007f97f3af2ba3 in jpeg_start_decompress () from /usr/lib/libjpeg.so.62
#6  0x00007f97f289d9ca in read_jpeg_image (device=<value optimized out>, outImage=0x7fff1cbbad30, parameters=..., scaledSize=<value optimized out>, inQuality=-1) at qjpeghandler.cpp:817
#7  0x00007f97fb237bf2 in QImageReader::read (this=0x7fff1cbbad90, image=0x7fff1cbbad30) at image/qimagereader.cpp:1077
#8  0x00007f97fb23814c in QImageReader::read (this=0x7fff1cbbad90) at image/qimagereader.cpp:1027
#9  0x00007f97fb226c66 in QImage::load (this=0x10a0910, fileName=..., format=<value optimized out>) at image/qimage.cpp:4577
#10 0x000000000044200d in KdmPixmap::loadPixmap (this=0x10a07d0, pClass=...) at ../../../kdm/kfrontend/themer/kdmpixmap.cpp:101
#11 0x000000000044232b in KdmPixmap::drawContents (this=0x10a07d0, p=0x7fff1cbbb2b0, r=...) at ../../../kdm/kfrontend/themer/kdmpixmap.cpp:197
#12 0x000000000043a587 in KdmItem::paint (this=0x10a07d0, p=0x7fff1cbbb2b0, rect=..., background=true, primaryScreen=<value optimized out>) at ../../../kdm/kfrontend/themer/kdmitem.cpp:350
#13 0x000000000043a54b in KdmItem::paint (this=<value optimized out>, p=0x7fff1cbbb2b0, rect=..., background=<value optimized out>, primaryScreen=<value optimized out>)
    at ../../../kdm/kfrontend/themer/kdmitem.cpp:366
#14 0x00000000004383dc in KdmThemer::paintBackground (this=0x1077c10, dev=0x7fff1cbbb3d0, rect=..., primaryScreen=true) at ../../../kdm/kfrontend/themer/kdmthemer.cpp:195
#15 0x0000000000436086 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../../kdm/kfrontend/kgapp.cpp:368

Reported using DrKonqi
Comment 1 Sergey Sarbash 2010-02-16 11:46:40 UTC
The same here.
After last update from sid (Debian) I've got the crash with kdm:

Application: unknown (kdmgreet), signal: Segmentation fault
[KCrash Handler]
#4  0x0000000002154e18 in ?? ()
#5  0x00007fe5b5d1aba3 in jpeg_start_decompress () from /usr/lib/libjpeg.so.62
#6  0x00007fe5b4ac59ca in ?? () from /usr/lib/qt4/plugins/imageformats/libqjpeg.so
#7  0x00007fe5bd529bf2 in QImageReader::read(QImage*) () from /usr/lib/libQtGui.so.4
#8  0x00007fe5bd52a14c in QImageReader::read() () from /usr/lib/libQtGui.so.4
#9  0x00007fe5bd518c66 in QImage::load(QString const&, char const*) () from /usr/lib/libQtGui.so.4
#10 0x000000000044200d in ?? ()
#11 0x000000000044232b in ?? ()
#12 0x000000000043a587 in ?? ()
#13 0x000000000043a54b in ?? ()
#14 0x00000000004383dc in ?? ()
#15 0x0000000000436086 in ?? ()
#16 0x00007fe5bcc57abd in __libc_start_main (main=<value optimized out>, argc=<value optimized out>, ubp_av=<value optimized out>, init=<value optimized out>, fini=<value optimized out>, 
    rtld_fini=<value optimized out>, stack_end=0x7fff68954bd8) at libc-start.c:222
#17 0x0000000000417ae9 in _start ()
Comment 2 Sergey Sarbash 2010-02-16 12:05:06 UTC
Ok, it seems that it's already fixed:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570004

Just wait for updates in repo.
Comment 3 Dario Andres 2010-02-16 12:50:23 UTC
Yes, this is probably caused by the libjpeg update.