Bug 123082

Summary: playing music and opening a new file
Product: [Applications] ark Reporter: MurDoK <murdok.lnx>
Component: generalAssignee: Harald Hvaal <metellius>
Status: RESOLVED NOT A BUG    
Severity: crash CC: kouzinopoulos, rakuco
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description MurDoK 2006-03-04 17:41:39 UTC 
Version:           3.5.1 (using KDE KDE 3.5.1)
Installed from:    Ubuntu Packages

Reproduce:

1- Open a .rar file (maybe others) with a wav file (maybe others)
2- Double click on wav file to reproduce it
3- Minimize ark window and open another rar file from konqueror

Ark crashes and the new file is not opened.

Should:
 a) Open the new file in a new window
 b) Stop playing and open the new file

Excuse my bad english please :)
Comment 1 Henrique Pinto 2006-03-04 17:45:10 UTC 
On Sat 04 Mar 2006 13:41, MurDoK wrote:
> Ark crashes and the new file is not opened.


Do you have a test archive? Could you provide us a backtrace?

Thank you for your report!
Comment 2 MurDoK 2006-03-06 21:45:28 UTC 
It says ark cannot create a valid backtrace (spanish):

***************************
Este trazado inverso parece inútil.
Probablemente se deba a que sus paquetes están generados de forma que eviten la creación de trazados inversos adecuados, o la pila se ha corrompido seriamente durante el fallo de la aplicación.

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
*******************

You don't need my test archive. Just compress a mp3 file, open it, play it using ark and open the compressed file again.
Comment 3 Haris Kouzinopoulos 2006-03-18 20:07:56 UTC 
Hi, i cannot reproduce your bug. Does it happen every time? I need exact steps to reproduce it and if possible a test archive
Comment 4 Haris Kouzinopoulos 2006-04-09 18:09:12 UTC 
I am closing this bug as invalid. The reported isn't giving much details and i cannot reproduce it. If you find a way to reproduce this bug and/or a valid backtrace, please reopen it. Thanks!