Bug 184935 - Aplicativo: Ark (ark), sinal SIGSEGV 0x00007ff177a186b0 in nanosleep () from /lib/libc.so.6 Thread 1 (Thread 0x7ff17b6206f0 (LWP 6218)): [KCrash Handler] #5 0x000000000040d2a0 in _start ()
Summary: Aplicativo: Ark (ark), sinal SIGSEGV 0x00007ff177a186b0 in nanosleep () from ...
Status: RESOLVED DUPLICATE of bug 175637
Alias: None
Product: ark
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Harald Hvaal
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-19 13:55 UTC by Ailton
Modified: 2009-04-12 06:51 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 Ailton 2009-02-19 13:55:55 UTC 
Version:           Ark (using KDE 4.2.0)
Compiler:          ark 
OS:                Linux
Installed from:    Ubuntu Packages

Aplicativo: Ark (ark), sinal SIGSEGV
0x00007ff177a186b0 in nanosleep () from /lib/libc.so.6

Thread 1 (Thread 0x7ff17b6206f0 (LWP 6218)):
[KCrash Handler]
#5  0x000000000040d2a0 in _start ()
Comment 1 Ailton 2009-02-19 13:57:43 UTC 
The start, system ubuntun 8.10, granphis kde 4.2
Comment 2 Dario Andres 2009-02-19 23:47:30 UTC 
Did you closed a blank Ark window that appeared on KDE startup when the crash dialog appeared ?
Thanks
Comment 3 wviolette 2009-03-11 15:01:15 UTC 
KDE Startup, blank Ark window appears (sometimes multiple Ark windows), closing the window(s) triggers the crash dialog(s). Seems like it only happens if I've used Ark in previous session. Hope that helps...
OpenSuSE 11.1 x86_64
KDE 4.2.0

Application: Ark (ark), signal SIGSEGV
0x00007f286a7adcb0 in nanosleep () from /lib64/libc.so.6
[Current thread is 1 (Thread 0x7f286e4df750 (LWP 4857))]

Thread 1 (Thread 0x7f286e4df750 (LWP 4857)):
[KCrash Handler]
#5  0x000000000040c8bc in _start ()
Comment 4 Dario Andres 2009-03-14 13:26:08 UTC 
@Yes: that crash is bug 175637 (already fixed)
Comment 5 Raphael Kubo da Costa 2009-04-12 06:51:24 UTC 

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