Bug 175950

Summary:	A Fatal Error Occurred
Product:	[Unmaintained] adept	Reporter:	Cliff Petheram <cp4home>
Component:	general	Assignee:	Peter Rockai <me>
Status:	RESOLVED NOT A BUG
Severity:	crash	CC:	finex
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Cliff Petheram 2008-11-24 03:04:11 UTC

Version:            (using KDE 4.1.3)
OS:                Linux
Installed from:    Ubuntu Packages

Application: Adept (adept), signal SIGSEGV
(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)
[Thread debugging using libthread_db enabled]
[New Thread 0x7fb8d94076f0 (LWP 6520)]
(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)
(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]
#5  0x00000000004c0ff6 in ?? ()
#6  0x0000000000484690 in ?? ()
#7  0x000000000048897c in ?? ()
#8  0x00000000004889aa in ?? ()
#9  0x0000000000458545 in _start ()
#0  0x00007fb8d60635f0 in nanosleep () from /lib/libc.so.6

Comment 1 FiNeX 2008-11-25 13:30:29 UTC

If you can reproduce the crash, you should install the debug enabled packages and provide a new backtrace. Read this page for the instructions:

http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Thanks!

Comment 2 Peter Rockai 2008-12-09 09:32:35 UTC

Please provide more data: what were you doing at the time of crash, if it's
possible to reproduce and how, and terminal output from adept (run "sudo adept"
in terminal, try to crash it and then paste what it has printed to the
terminal). When you have at least part of that, please reopen the bug. Thank
you.