Bug 143253

Summary: Konqueror crash if one closes parent window before action on "open with" dialog
Product: [Applications] konqueror Reporter: Dan O'Huiginn <daniel>
Component: generalAssignee: Konqueror Bugs <konqueror-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: backtrace

Description Dan O'Huiginn 2007-03-20 12:16:54 UTC 
Version:            (using KDE KDE 3.5.6)
Installed from:    Ubuntu Packages
OS:                Linux

As reported and confirmed in Ubuntu: https://launchpad.net/ubuntu/+source/kdebase/+bug/91509

Konquerer crashes if one gets a popup window which has a link to some content that creates the "open with" dialog, closes the popup window (before choosing one of the "open with" options), and only then chooses one action. My guess is that there is a code reference (a pointer) to the parent window ( to make some kind of back-notify, maybe to return focus? ) which segfaults because there is no parent window anymore.
Example ( not that this is not particular of this URL, this is reproductible with any kind of page/site where we can follow this sequence )
1 - open web page from wich you can have a popup window (http://209.161.33.50/dictionary/crash)
2 - open the popup (in this example, click the red speaker image after "Main Entry: crash"
3 - the popup window has a wav file, which triggers the appearance of "Open '...' ?". Do not choose an option here and instead, close the popup window.
4 - choose one option from the "Open '...'?" window. Konqueror will crash.
Comment 1 Dan O'Huiginn 2007-03-20 12:18:23 UTC 
Created attachment 20054 [details]
backtrace
Comment 2 Tommi Tervo 2007-08-08 10:50:33 UTC 

*** This bug has been marked as a duplicate of 91246 ***
Comment 3 Joao Clemente 2007-08-23 14:26:30 UTC 
Please see coment I left on bug 91246. I believe this bug should not have been stated as invalid/duplicate, because at most, this is a more generic description of the problem, so by keeping only the other bug you'll be getting away from the problem. I read and reread the description on bug 91246 and personally I dont think they are related, or at lease it does not contain usefull tracking information.