Bug 271580 - kalarm crashes opening a new display alarm window
Summary: kalarm crashes opening a new display alarm window
Status: CLOSED FIXED
Alias: None
Product: kalarm
Classification: Applications
Component: general (show other bugs)
Version: KDE 4
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: David Jarvie
URL:
Keywords:
: 272043 299796 300225 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-04-23 21:10 UTC by Fabio Rossi
Modified: 2012-08-28 09:04 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: KDE 4.7.0, kdepim 4.4.12


Attachments
kalarm-20110423-165347.kcrash (5.26 KB, application/octet-stream)
2011-04-23 21:10 UTC, Fabio Rossi
Details
kalarm-20110425-122207.kcrash (9.02 KB, application/octet-stream)
2011-04-25 12:13 UTC, Fabio Rossi
Details
Patch containing possible fix for the crash (1.02 KB, patch)
2011-04-26 23:26 UTC, David Jarvie
Details
New crash information added by DrKonqi (8.77 KB, text/plain)
2012-05-11 04:32 UTC, Hans Liao
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Fabio Rossi 2011-04-23 21:10:03 UTC
Created attachment 59255 [details]
kalarm-20110423-165347.kcrash

Version:           KDE 4 (using KDE 4.6.2) 
OS:                Linux

kalarm crashes as soon as I try to create a new display alarm window from the systray icon. It's a regression in the current version 2.4.11 (the previous one 2.4.10 was fine).

Reproducible: Always

Steps to Reproduce:
1) right click on systray icon
2) new alarm -> new display alarm

Actual Results:  
crash of the application

Expected Results:  
no crash :-)
Comment 1 David Jarvie 2011-04-25 02:10:41 UTC
This works on my system (using KDE 4.6.2). The code which crashed is indeed new in KAlarm 2.4.11, but the crash trace is not as useful as it could be - it doesn't show function parameter values or source code line numbers, so it isn't clear where in QTransform::type() it crashes. If you're able to run a full debug version of Qt which outputs this information, that could help narrow down the problem. In the meantime, I'll investigate further.
Comment 2 Fabio Rossi 2011-04-25 12:13:54 UTC
Created attachment 59302 [details]
kalarm-20110425-122207.kcrash

Another attachment after having recompiled Qt and kalarm with -ggdb
Comment 3 David Jarvie 2011-04-25 12:53:05 UTC
Thanks. That new trace does provide some vital extra information. It looks like the QPaintEngine may not be initialised fully. As for the reason ...
Comment 4 David Jarvie 2011-04-25 18:05:56 UTC
Can you please confirm which version of Qt you are running (you stated 4.7.2 in your original bug report), and whether it is the standard Qt as supplied by Nokia, or the KDE patched version.
Comment 5 Fabio Rossi 2011-04-25 18:28:26 UTC
Yes, I confirm 4.7.2. It's the original version from Nokia installed using the Gentoo package system. Two small patches are applied, qt-assistant-4.7-fix-compat.patch and blacklist_ssl.patch, I don't think they are related to QPaintEngine
Comment 6 David Jarvie 2011-04-26 23:26:50 UTC
Created attachment 59345 [details]
Patch containing possible fix for the crash

Can you please try applying the attached patch, and let me know whether it fixes the crash for you.
Comment 7 Fabio Rossi 2011-04-26 23:53:50 UTC
The patch solves the crash, thanks!
Comment 8 David Jarvie 2011-04-27 00:46:13 UTC
Now fixed - thanks for your assistance in this. The fix will be in kdepim
4.4.12 if that is ever issued, and 4.6.0.

Git commits 4b504e760e0c994e676b55bfaca731d74841f1f4 (4.4 branch),
7635f10e879866b6644ffb7f0bd6cd0ee59de09e (4.5 branch),
312af48d5e0feb01c7677e1609dc71276d2ebb49 (master).
Comment 9 David Jarvie 2011-05-01 18:52:58 UTC
*** Bug 272043 has been marked as a duplicate of this bug. ***
Comment 10 Hans Liao 2012-05-11 04:32:39 UTC
Created attachment 71015 [details]
New crash information added by DrKonqi

kalarm (2.4.11) on KDE Platform 4.7.4 (4.7.4) using Qt 4.8.1

- What I was doing when the application crashed:

The crash wil happen  in the following manner:

- When I tried selecting "Configure Kalarm" from the menu.
- When I tried adding a new display alarm.

-- Backtrace (Reduced):
#6  QTransform::type (this=0xd0) at painting/qtransform.cpp:2048
#7  0x00007fd6b5996148 in QRasterPaintEngine::drawTiledPixmap (this=0x1768c60, r=..., pixmap=..., sr=...) at painting/qpaintengine_raster.cpp:2501
#8  0x0000000000453d89 in SpinMirror::setFrame (this=0xf7d310) at ../../kalarm/lib/spinbox2.cpp:592
#9  0x00007fd6b5820c15 in QWidget::event (this=0xf78e90, event=0x7fff48deef50) at kernel/qwidget.cpp:8569
#10 0x00007fd6b5bdcfc6 in QFrame::event (this=0xf78e90, e=0x7fff48deef50) at widgets/qframe.cpp:557
Comment 11 David Jarvie 2012-05-11 08:44:20 UTC
*** Bug 299796 has been marked as a duplicate of this bug. ***
Comment 12 David Jarvie 2012-05-18 08:30:08 UTC
*** Bug 300225 has been marked as a duplicate of this bug. ***
Comment 13 David Jarvie 2012-05-20 21:41:20 UTC
This bug has been raised as a Debian bug report - see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671619