Bug 182733 - Ark crashes the KDE, and I wasn't using them
Summary: Ark crashes the KDE, and I wasn't using them
Status: RESOLVED DUPLICATE of bug 175637
Alias: None
Product: ark
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Harald Hvaal
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-01 15:49 UTC by Rafael
Modified: 2009-02-01 21:49 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rafael 2009-02-01 15:49:03 UTC
Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    SuSE RPMs

When I'm doing other tasks that (I believe) don't uses the Ark, the KDE (4.1 and 4.2) on OpenSUSE 11.1 crashes inexplicably. After I reset the computer, the font of the system were smaller(?!), the following report appears with a window of Ark openned:

Application: Ark (ark), signal SIGSEGV
[Current thread is 1 (Thread 0xb5f22700 (LWP 4346))]

In the last time, the bug occurs when I was using Firefox, Amarok, and VirtualBox(loading WinXP), but not the Ark.
Comment 1 Rafael 2009-02-01 19:18:22 UTC
I remember that in the same session that crashed, I extract a RAR file by clicking the right button on the file and clicking in "Extract archive here".

Now I tested the procedure again and I saw that in the 'System Activity', after the extracting, the Ark process continued. Because the "Restore previous session" option on KDE, every time I logged in, a crash in Ark happened.

The rest of this strange bug, I don't really know.

Sorry the bad English.   
Comment 2 Dario Andres 2009-02-01 20:11:19 UTC
Hi Rafael. Did you closed an "empty" window when the Ark crash information appeared? If you did, this is probably a duplicate of bug 175637
Comment 3 Rafael 2009-02-01 21:49:21 UTC
Yes, I did. So, I'm marking this as duplicated.

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