Bug 161256 - kdesktop_lock crash with signal 6 SIGABRT
Summary: kdesktop_lock crash with signal 6 SIGABRT
Status: CLOSED REMIND
Alias: None
Product: kdesktop
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-25 11:04 UTC by Alexander Gavrenkov
Modified: 2009-01-02 20:35 UTC (History)
2 users (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 Alexander Gavrenkov 2008-04-25 11:04:39 UTC
Version:            (using KDE 3.5.8)
Installed from:    SuSE RPMs
OS:                Linux

Проверка системной конфигурации при запуске выключена.

[?1034h(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)
[Thread debugging using libthread_db enabled]
[New Thread 0xb69e88e0 (LWP 18939)]
(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  0xb6c898f5 in raise () from /lib/libc.so.6
#8  0xb6c8b1e1 in abort () from /lib/libc.so.6
#9  0xb6c82c1e in __assert_fail () from /lib/libc.so.6
#10 0xb6ec904c in _XRead () from /usr/lib/libX11.so.6
#11 0xb6fc275d in ?? () from /usr/lib/libGL.so.1
#12 0x0807e940 in ?? ()
#13 0x080dd6e8 in ?? ()
#14 0x000000e0 in ?? ()
#15 0x00000001 in ?? ()
#16 0x00000001 in ?? ()
#17 0x00000000 in ?? ()
Comment 1 Pino Toscano 2008-04-25 14:41:15 UTC
Unfortunately, the backtrace is not really useful.
Can you please provide a better one, by following the instructions on
http://techbase.kde.org/index.php?title=Development/Tutorials/Debugging/How_to_create_useful_crash_reports
?
Thanks
Comment 2 Lubos Lunak 2008-05-31 19:48:45 UTC
Waiting for the requested information.
Comment 3 FiNeX 2009-01-02 20:35:06 UTC
Bug closed. Kdesktop is no more mantained.