Bug 180307 - The application KPlayer (kplayer) crashed and caused the signal 11 (SIGSEGV).
Summary: The application KPlayer (kplayer) crashed and caused the signal 11 (SIGSEGV).
Status: RESOLVED NOT A BUG
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-11 02:52 UTC by Leonard Pistol
Modified: 2009-01-16 06:34 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 Leonard Pistol 2009-01-11 02:52:20 UTC
Version:           4.1.3 (using KDE 4.1.3)
OS:                Linux
Installed from:    Ubuntu Packages

After a wile, the application just crashes, without any peculiar reason, and I receive this output.

Application: KPlayer (kplayer), 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) 
(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) 
[Thread debugging using libthread_db enabled] 
[New Thread 0xb5c8d6c0 (LWP 7675)] 
[New Thread 0xb4373b90 (LWP 7679)] 
(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 0x08062a6b in _start () #0 0xb7f4d430 in __kernel_vsyscall () 

Thank you.
Comment 1 Dario Andres 2009-01-11 14:39:07 UTC
Without any reason or steps and without debugging symbols this report is going to be no use :(
Please, read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports to know how to install debug symbols packages, so if you experience this bug again you can give us more information about the crash.
Thank you for reporting :)