Bug 159241 - Kicker Crash (beim Abmelden)
Summary: Kicker Crash (beim Abmelden)
Status: RESOLVED DUPLICATE of bug 146502
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: KDE (show other bugs)
Version: Beta 8
Hardware: 64bit SuSE Linux 10.1
: P5 - None : Critical (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-17 20:54 UTC by Eberhard Möller
Modified: 2006-03-17 21:04 UTC (History)
1 user (show)

See Also:
Found By: Development
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eberhard Möller 2006-03-17 20:54:08 UTC
"sorry! leider nur DEUTSCH möglich "
Beobachte diesen Fehler seit Suse10.0 
sowohl mir Original-KDE als auch 
weniger oft nach Update auf KDE3.5
Und nun leider auch gleich beim ersten
Test der Suse10.1Beta8.
_______________
beim Abmelden aus KDE
kommt ein Hinweisfenster (Kicker - Crash)
siehe Anhang:
Comment 1 Eberhard Möller 2006-03-17 20:57:48 UTC
Überprüfung der Systemkonfiguration beim Start deaktiviert.

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1230600528 (LWP 11134)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xffffe410 in __kernel_vsyscall ()
#7  0xb70008d0 in raise () from /lib/libc.so.6
#8  0xb7001fa3 in abort () from /lib/libc.so.6
#9  0xb703602b in __libc_message () from /lib/libc.so.6
#10 0xb703b9b1 in malloc_printerr () from /lib/libc.so.6
#11 0xb703cc10 in _int_free () from /lib/libc.so.6
#12 0xb703d024 in free () from /lib/libc.so.6
#13 0xb71aa681 in operator delete () from /usr/lib/libstdc++.so.6
#14 0xb67d65d7 in Kicker::~Kicker () from /opt/kde3/lib/libkdeinit_kicker.so
#15 0xb67f6884 in kdemain () from /opt/kde3/lib/libkdeinit_kicker.so
#16 0xb7f8e524 in kdeinitmain () from /opt/kde3/lib/kde3/kicker.so
#17 0x0804e39f in ?? ()
#18 0x00000001 in ?? ()
#19 0x08072590 in ?? ()
#20 0x00000001 in ?? ()
#21 0x00000000 in ?? ()
Comment 2 Eberhard Möller 2006-03-17 21:04:25 UTC

*** This bug has been marked as a duplicate of 146502 ***