Bug 266190

Summary: Dolphin showing broken new folder dialogue window in faceted browsing mode
Product: [Applications] dolphin Reporter: smihael <smihael>
Component: generalAssignee: Dolphin Bug Assignee <dolphin-bugs-null>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: andresbajotierra, emmanuelpescosta099, kdelibs-bugs-null, samuel.brack
Priority: NOR    
Version First Reported In: 16.12.2   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: screenshoot

Description smihael 2011-02-13 11:58:05 UTC 
Created attachment 57205 [details]
screenshoot

Version:           4.6 (using KDE 4.6.0) 
OS:                Linux

Whenever I try to create new folder inside Dolphin's faceted search results I get a broken window that should be "new folder" dialogue. 

Dialogues for other document types are shown properly, but files are not created.

Reproducible: Always

Steps to Reproduce:
1. Open Dolphin.
2. In right sidebar, under Filter select (for example) Today
3. Right click, select Create new ... Folder


Actual Results:  
"Broken" window is shown (even with compositing turned off)
http://www.shrani.si/f/1O/1f/21v5n9SK/294.jpg

If I enter new folder's name (although no input field is visible) I get KLauncher's ioslave error... 

Expected Results:  
New folder dialogue should be shown properly

KDE 4.6.0
Dolphin 1.6
Kubuntu 10.10
Lang: sl
Comment 1 Samuel Brack 2011-02-13 22:17:13 UTC 
I can confirm this behaviour in Dolphin 1.6 using KDE 4.6
Comment 2 Jeroen van Meeuwen (Kolab Systems) 2012-08-24 16:19:50 UTC 
Resetting assignee to default as per bug #305719
Comment 3 Emmanuel Pescosta 2013-01-09 14:59:04 UTC 
I cannot reproduce it in Dolphin 2.1.97

1. The filter sidebar is not available anymore
2. Tested with tags/timeline/filtering/searching/... -> Everything worked fine for me (no weird new directory dialogues)
Comment 4 Frank Reininghaus 2013-04-25 20:42:41 UTC 
Closing because the filter panel does not exist anymore and it seems that there is no other place where this bug still happens (see comment 3).