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 1205

Summary:	[kdesktop] Crash on startup
Product:	TDE	Reporter:	nils-henkel
Component:	other (any)	Assignee:	Timothy Pearson <kb9vqf>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	bugwatch, michele.calgaro, wofgdkncxojef
Priority:	P5
Version:	R14.0.x [Trinity]
Hardware:	amd64
OS:	Debian Wheezy
Compiler Version:		TDE Version String:
Application Version:		Application Name:

Description nils-henkel 2012-09-09 09:57:17 CDT

kdesktop crashes when TDE is started.
But afterwards, everything seems to work fine, I do not see any problems.


Backtrace:

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash handler]
#5  0x00007f317b243475 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#6  0x00007f317b2466f0 in abort () from /lib/x86_64-linux-gnu/libc.so.6
#7  0x00007f317b27d32b in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#8  0x00007f317b286b76 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#9  0x00007f317b28b8ac in free () from /lib/x86_64-linux-gnu/libc.so.6
#10 0x00007f317de4d557 in TQStringData::deleteSelf() () from /usr/lib/libtqt-mt.so.3
#11 0x00007f318023a2ac in KService::~KService() () from /opt/trinity/lib/libkio.so.4
#12 0x00007f318023a439 in KService::~KService() () from /opt/trinity/lib/libkio.so.4
#13 0x00007f3180202728 in ?? () from /opt/trinity/lib/libkio.so.4
#14 0x00007f31802a2c72 in KFileMetaInfoProvider::loadPlugin(TQString const&, TQString const&) () from /opt/trinity/lib/libkio.so.4
#15 0x00007f31802a30d8 in KFileMetaInfoProvider::loadAndRegisterPlugin(TQString const&, TQString const&) () from /opt/trinity/lib/libkio.so.4
#16 0x00007f31802a344a in KFileMetaInfoProvider::mimeTypeInfo(TQString const&, TQString const&) () from /opt/trinity/lib/libkio.so.4
#17 0x00007f31802a4012 in KFileMetaInfo::init(KURL const&, TQString const&, unsigned int) () from /opt/trinity/lib/libkio.so.4
#18 0x00007f31802a41e8 in KFileMetaInfo::KFileMetaInfo(TQString const&, TQString const&, unsigned int) () from /opt/trinity/lib/libkio.so.4
#19 0x00007f3180e6e531 in ?? () from /opt/trinity/lib/libtdeinit_kdesktop.so
#20 0x00007f3180e72305 in ?? () from /opt/trinity/lib/libtdeinit_kdesktop.so
#21 0x00007f3180e72688 in ?? () from /opt/trinity/lib/libtdeinit_kdesktop.so
#22 0x00007f317dc109af in TQObject::activate_signal(TQConnectionList*, TQUObject*) () from /usr/lib/libtqt-mt.so.3
#23 0x00007f317dc10a40 in TQObject::activate_signal(int) () from /usr/lib/libtqt-mt.so.3
#24 0x00007f317dc374e2 in TQTimer::event(TQEvent*) () from /usr/lib/libtqt-mt.so.3
#25 0x00007f317dbc21ad in TQApplication::internalNotify(TQObject*, TQEvent*) () from /usr/lib/libtqt-mt.so.3
#26 0x00007f317dbc2320 in TQApplication::notify(TQObject*, TQEvent*) () from /usr/lib/libtqt-mt.so.3
#27 0x00007f317ea57554 in KApplication::notify(TQObject*, TQEvent*) () from /opt/trinity/lib/libtdecore.so.4
#28 0x00007f317dbb9062 in TQEventLoop::activateTimers() () from /usr/lib/libtqt-mt.so.3
#29 0x00007f317db7dbd0 in TQEventLoop::processEvents(unsigned int) () from /usr/lib/libtqt-mt.so.3
#30 0x00007f317dbd36a9 in TQEventLoop::enterLoop() () from /usr/lib/libtqt-mt.so.3
#31 0x00007f317dbd3632 in TQEventLoop::exec() () from /usr/lib/libtqt-mt.so.3
#32 0x00007f3180e28c63 in kdemain () from /opt/trinity/lib/libtdeinit_kdesktop.so
#33 0x00007f317b22fead in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
#34 0x0000000000400931 in _start ()

Comment 1 nils-henkel 2012-09-11 12:48:56 CDT

upgraded the bug to "normal" importance.

Not sure why I did not notice this before, but after kdesktop crashes, obviously desktop background, icons, etc. do not work.

kdesktop also crashes when started from the command line, yielding the error

[kdesktop] SAK driven secure dialog is not available for use (retcode 6).  Check tdmtsak for proper functionality.
*** glibc detected *** kdesktop: free(): invalid pointer: 0x0000000000ddb530 ***

Comment 2 Timothy Pearson 2012-09-11 13:22:18 CDT

I notice this is on Debian Wheezy.  Wheezy is unstable; does this crash occur on any other distribution?

Comment 3 nils-henkel 2012-09-13 03:02:50 CDT

I just installed some updates and, on first glance, the problem seems to be mostly fixed. I can start kdesktop from konsole and the desktop looks fine.

However, I still get (in konsole):

nils@zuhause:~$ kdesktop
nils@zuhause:~$ [kdesktop] SAK driven secure dialog is not available for use (retcode 6).  Check tdmtsak for proper functionality.

Comment 4 wofgdkncxojef 2018-05-24 11:40:19 CDT

I'm closing this too old and doesn't crash anymore.
The warning about SAK is still there though.
We can live with that.

Comment 5 Michele Calgaro 2018-05-27 07:06:42 CDT

Yes, we do mind.
You are not a TDE developer AFAIK. Then don't go around and close bugs just as you see fit without FIRST discussing with the development team.

The correct way of action is:
1) you find a bug that you think should be closed
2) you write to the developer mailing list explaining clearly why the bug should be closed
3) if the development team agrees, they will instruct you to close such bug.

Thanks for your understanding.

Comment 6 wofgdkncxojef 2018-05-27 12:10:41 CDT

You should restrict what none dev accounts can do.

Comment 7 Michele Calgaro 2018-07-29 05:12:28 CDT

A lot of work has gone into kdesktop since the time of the report. kdesktop does not crash anymore. Closing the bug.
Feel free to reopen it if you can reproduce it systematically and provide detailed info.
Regarding the SAK message, there is already bug 925 for it.