Bug 227043 - kdm and X window system crash
Summary: kdm and X window system crash
Status: RESOLVED DOWNSTREAM
Alias: None
Product: kdm
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdm bugs tracker
URL:
Keywords:
: 227258 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-02-15 18:42 UTC by Valery Mamonov
Modified: 2010-02-16 23:20 UTC (History)
1 user (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 Valery Mamonov 2010-02-15 18:42:53 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-2-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

What I was doing when the application crashed:
I have clicked link in pdf document and got a lot of endlessly starting konqueror windows. I had unable to stop this looping process and deciced to logout from kde session. I have clicked on "Logout" and got kdm crash. Restart of kdn was unsuccessful, I got crash again. This process looped too.

 -- Backtrace:
Application: unknown (kdmgreet), signal: Segmentation fault
The current source language is "auto; currently c".
[KCrash Handler]
#4  0x000000000219c888 in ?? ()
#5  0x00007f849ba24ba3 in jpeg_start_decompress () from /usr/lib/libjpeg.so.62
#6  0x00007f849a7cf9ca in read_jpeg_image (device=<value optimized out>, outImage=0x7fff64da3cf0, parameters=..., scaledSize=<value optimized out>, inQuality=-1) at qjpeghandler.cpp:817
#7  0x0000003e3868cbf2 in QImageReader::read (this=<value optimized out>, image=<value optimized out>) at image/qimagereader.cpp:1077
#8  0x0000003e3868d14c in QImageReader::read (this=<value optimized out>) at image/qimagereader.cpp:1027
#9  0x0000003e3867bc66 in QImage::load (this=<value optimized out>, fileName=<value optimized out>, format=<value optimized out>) at image/qimage.cpp:4577
#10 0x000000000044200d in KdmPixmap::loadPixmap (this=0x1f9b650, pClass=...) at ../../../kdm/kfrontend/themer/kdmpixmap.cpp:101
#11 0x000000000044232b in KdmPixmap::drawContents (this=0x1f9b650, p=0x7fff64da4270, r=...) at ../../../kdm/kfrontend/themer/kdmpixmap.cpp:197
#12 0x000000000043a587 in KdmItem::paint (this=0x1f9b650, p=0x7fff64da4270, rect=..., background=true, primaryScreen=<value optimized out>) at ../../../kdm/kfrontend/themer/kdmitem.cpp:350
#13 0x000000000043a54b in KdmItem::paint (this=<value optimized out>, p=0x7fff64da4270, rect=..., background=<value optimized out>, primaryScreen=<value optimized out>)
    at ../../../kdm/kfrontend/themer/kdmitem.cpp:366
#14 0x00000000004383dc in KdmThemer::paintBackground (this=0x1f71df0, dev=0x7fff64da4390, 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 Oswald Buddenhagen 2010-02-15 19:05:05 UTC
debian sid is currently in a libjpeg transition. did you by any chance upgrade the system right before that happened?
Comment 2 Valery Mamonov 2010-02-15 19:13:01 UTC
Yes, I upgraded libjpeg right before.

2010/2/15 Oswald Buddenhagen <ossi@kde.org>

> https://bugs.kde.org/show_bug.cgi?id=227043
>
>
>
>
>
> --- Comment #1 from Oswald Buddenhagen <ossi kde org>  2010-02-15 19:05:05
> ---
> debian sid is currently in a libjpeg transition. did you by any chance
> upgrade
> the system right before that happened?
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
>
Comment 3 Oswald Buddenhagen 2010-02-15 20:41:18 UTC
ok. if the problem does not re-surface, then this was some "library replacement glitch". if the problem persists, then the libjpg upgrade poses a binary compatibility problem which needs to be solved by recompiling. in either case this is not kde's fault, so i'm closing this report.
Comment 4 Oswald Buddenhagen 2010-02-16 23:20:56 UTC
*** Bug 227258 has been marked as a duplicate of this bug. ***