By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 1161 - Kicker says it crashed, but actually seems to work
Summary: Kicker says it crashed, but actually seems to work
Status: RESOLVED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: tdebase (show other bugs)
Version: R14.0.0 [Trinity]
Hardware: All Linux
: P5 critical
Assignee: Alexander Golubev (Fat-Zer)
URL:
Depends on:
Blocks:
 
Reported: 2012-08-06 15:10 CDT by Thierry de Coulon
Modified: 2013-04-05 01:49 CDT (History)
3 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
a debug session log (8.22 KB, application/octet-stream)
2012-12-11 11:56 CST, Alexander Golubev (Fat-Zer) 		Details
patch (647 bytes, patch)
2012-12-12 03:25 CST, Alexander Golubev (Fat-Zer) 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Thierry de Coulon 2012-08-06 15:10:46 CDT 
Sometimes, not always, not frequently (but always on TDE start) I get a message that kicker crashed. But the desktop loads and works ok after that.

Here is the crash report:

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash handler]
#5  0x00007f375fa0a775 in KSharedPixmap::x11Event(_XEvent*) () from /opt/trinity/lib/libtdeui.so.4
#6  0x00007f375da7a11c in TQApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/libtqt-mt.so.3
#7  0x00007f375da8b1ab in TQEventLoop::processEvents(unsigned int) () from /usr/lib/libtqt-mt.so.3
#8  0x00007f375dae0f59 in TQEventLoop::enterLoop() () from /usr/lib/libtqt-mt.so.3
#9  0x00007f375dae0ee2 in TQEventLoop::exec() () from /usr/lib/libtqt-mt.so.3
#10 0x00007f37588693bb in kdemain () from /opt/trinity/lib/libtdeinit_kicker.so
#11 0x00007f3758b7d950 in tdeinitmain () from /opt/trinity/lib/trinity/kicker.so
#12 0x0000000000408b4e in _start ()
Comment 1 Thierry de Coulon 2012-08-06 15:11:34 CDT 
Wheezy 64bit / TDE NIghtly build
Comment 2 Darrell 2012-09-03 19:48:28 CDT 
I have experienced a kicker crash as well upon starting TDE. Slackware 14 RC4 64-bit. Here is the backtrace:

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash handler]
#5  0x00007f1e84bd4705 in KSharedPixmap::x11Event (this=0xfed7c0, event=0x7fffb870c3f0) at /dev/shm/tdelibs/tdeui/ksharedpixmap.cpp:204
#6  0x00007f1e82c4de6c in TQApplication::x11ProcessEvent(_XEvent*) () from /opt/trinity/lib64/libtqt-mt.so.3
#7  0x00007f1e82c5ef0b in TQEventLoop::processEvents(unsigned int) () from /opt/trinity/lib64/libtqt-mt.so.3
#8  0x00007f1e82cb3dfe in TQEventLoop::processEvents(unsigned int, int) () from /opt/trinity/lib64/libtqt-mt.so.3
#9  0x00007f1e7db4f131 in ExtensionManager::initialize (this=this@entry=0xf7ac50) at /dev/shm/tdebase/kicker/kicker/core/extensionmanager.cpp:129
#10 0x00007f1e7db4fab8 in ExtensionManager::tqt_invoke (this=0xf7ac50, _id=3, _o=0x7fffb870c710) at /dev/shm/tdebase.build/kicker/kicker/core/extensionmanager.moc:120
#11 0x00007f1e82cf0fbf in TQObject::activate_signal(TQConnectionList*, TQUObject*) () from /opt/trinity/lib64/libtqt-mt.so.3
#12 0x00007f1e82f79dc0 in TQSignal::signal(TQVariant const&) () from /opt/trinity/lib64/libtqt-mt.so.3
#13 0x00007f1e82d04934 in TQSignal::activate() () from /opt/trinity/lib64/libtqt-mt.so.3
#14 0x00007f1e82d17938 in TQSingleShotTimer::event(TQEvent*) () from /opt/trinity/lib64/libtqt-mt.so.3
#15 0x00007f1e82ca28bd in TQApplication::internalNotify(TQObject*, TQEvent*) () from /opt/trinity/lib64/libtqt-mt.so.3
#16 0x00007f1e82ca2a30 in TQApplication::notify(TQObject*, TQEvent*) () from /opt/trinity/lib64/libtqt-mt.so.3
#17 0x00007f1e83ae20d4 in KApplication::notify (this=0xedf2c0, receiver=0xf7a670, event=0x7fffb870ca30) at /dev/shm/tdelibs/tdecore/kapplication.cpp:583
#18 0x00007f1e82c99712 in TQEventLoop::activateTimers() () from /opt/trinity/lib64/libtqt-mt.so.3
#19 0x00007f1e82c5f250 in TQEventLoop::processEvents(unsigned int) () from /opt/trinity/lib64/libtqt-mt.so.3
#20 0x00007f1e82cb3d09 in TQEventLoop::enterLoop() () from /opt/trinity/lib64/libtqt-mt.so.3
#21 0x00007f1e82cb3c92 in TQEventLoop::exec() () from /opt/trinity/lib64/libtqt-mt.so.3
#22 0x00007f1e7db31564 in kdemain (argc=1, argv=0xed0170) at /dev/shm/tdebase/kicker/kicker/core/main.cpp:151
#23 0x0000000000408a43 in launch (argc=argc@entry=1, _name=<optimized out>, _name@entry=0xe642a8 "kicker", args=<optimized out>, args@entry=0xe642af "", cwd=cwd@entry=0x0, envc=envc@entry=0, envs=<optimized out>, envs@entry=0xe642b7 "", reset_env=false, tty=tty@entry=0x0, avoid_loops=false, startup_id_str=startup_id_str@entry=0x40e11f "0") at /dev/shm/tdelibs/kinit/kinit.cpp:673
#24 0x0000000000409b9e in handle_launcher_request (sock=9) at /dev/shm/tdelibs/kinit/kinit.cpp:1240
#25 0x000000000040a24a in handle_requests (waitForPid=waitForPid@entry=0) at /dev/shm/tdelibs/kinit/kinit.cpp:1443
#26 0x0000000000405e58 in main (argc=5, argv=0x7f1e85c816e0, envp=0x7fffb870da18) at /dev/shm/tdelibs/kinit/kinit.cpp:1909
Comment 3 Alexander Golubev (Fat-Zer) 2012-12-11 11:56:46 CST 
Created attachment 1047 [details]
a debug session log

Hi. I've got the same crash with 3.5.13.1. Here is my debug session log. As you can see XGetGeometry() returns bad values for width and height for some reason.
Comment 4 Timothy Pearson 2012-12-11 12:48:53 CST 
(In reply to comment #3)
> Created attachment 1047 [details]
> a debug session log
> 
> Hi. I've got the same crash with 3.5.13.1. Here is my debug session log. As you
> can see XGetGeometry() returns bad values for width and height for some reason.

I have added a work around to tdelibs in GIT hash 1c14fec.  Please let me know if this resolves the issue!
Comment 5 Alexander Golubev (Fat-Zer) 2012-12-12 03:25:19 CST 
Created attachment 1048 [details]
patch

I haven't seen your work around yet but I've found the reason ans solution:
According to documentation, XGetGeometry() «returns a nonzero status on success; otherwise, it returns a zero status». But we check if (status == BadDrawable).
Here is the patch.
Comment 6 Timothy Pearson 2013-04-05 01:49:31 CDT 
(In reply to comment #5)
> Created attachment 1048 [details]
> patch
> 
> I haven't seen your work around yet but I've found the reason ans solution:
> According to documentation, XGetGeometry() «returns a nonzero status on
> success; otherwise, it returns a zero status». But we check if (status ==
> BadDrawable).
> Here is the patch.

Pushed to GIT in hash 6a7a4e6.  This commit also removes my initial hack, so if the crash reappears please reopen this bug report.

Thanks for reporting, and for the patch!