Bug 161429 - kbluelock crashed and caused signal 6 (SIGABRT)
Summary: kbluelock crashed and caused signal 6 (SIGABRT)
Status: RESOLVED DUPLICATE of bug 152929
Alias: None
Product: kde-bluetooth
Classification: Unmaintained
Component: kbluelock (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Mattia Merzi
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-30 01:37 UTC by Joan Deurloo
Modified: 2010-08-19 10:50 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Joan Deurloo 2008-04-30 01:38:00 UTC 
Version:           3.5.9 (using 3.5.9, compiled sources)
Compiler:          Target: i586-manbo-linux-gnu 
OS:                Linux

A program would not close, so I tried escape and then had to reboot my computer.  When it started up, a report on my computer said that kbluelock had crashed and that I should send a report.
Comment 1 Pino Toscano 2008-04-30 03:46:29 UTC 
Can you please attach a backtrace, as explained in the page:
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Comment 2 FiNeX 2008-11-19 20:25:19 UTC 
Changed severity to "crash". I hope to have selected only the right bugs (>100) :-)
Comment 3 Dario Andres 2009-05-29 22:08:24 UTC 
Marking as NEEDSINFO
Comment 4 Andreas Schallenberg 2009-10-12 21:46:53 UTC 
I just talked to another user having the same problem.

And: The bug may be related to
http://bugs.kde.org/show_bug.cgi?id=152421
Comment 5 Nicolas L. 2010-08-19 10:50:09 UTC 
i close this bug as dupp of the second one .


Reopen this one if someone isn't agree with me.

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