Bug 282560

Summary: klauncher said: Unknown protocol ''.
Product: [I don't know] kde Reporter: jangeorg.vdwath
Component: generalAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED UPSTREAM    
Severity: crash CC: ben, shlomif
Priority: NOR    
Version: 4.7   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:

Description jangeorg.vdwath 2011-09-22 14:57:27 UTC 
Version:           4.7 (using KDE 4.7.1) 
OS:                Linux

klauncher said: Unknown protocol ''.

Reproducible: Always

Steps to Reproduce:
I have a program written in Qt which launches a dialog to save a file. Qt provides the option to use the native filesystem dialog, which launches the kde dialog. If I specify a suggested file name that contains a "." ie. "myfile.v1-a.txt" I get the following error message "klauncher said: Unknown protocol ''."


Expected Results:  
The file dialog should open up with the suggested file name.
Comment 1 Shlomi Fish 2011-09-22 16:32:35 UTC 
Can you provide the source to the offending program? A reproducing example will be nice.
Comment 2 jangeorg.vdwath 2011-09-23 05:50:49 UTC 
I wrote an example app which launch exactly the same line of code that my project does, but it works in the example app but crash in my project. Am a bit baffled. I found the problem are linked to if I set the filter on the dialog. I will investigate further why Qt crashes.
A working example is 

#include <QtGui>

int main(int argc, char *argv[])
{
    QApplication app(argc, argv);
    
    QString saveFileName = QFileDialog::getSaveFileName(NULL, "Test", "~/temp/file.v1-a.txt", "Data file (*.dat)", NULL, QFileDialog::DontConfirmOverwrite);
    return app.exec();
}
Comment 3 jangeorg.vdwath 2011-09-23 07:37:52 UTC 
Found the problem. The example app still produces the error message "klauncher said: Unknown protocol ''" which generates a QtCryticalMsg. In my project when I receive a QtCryticalMsg I close down the program. I will log the bug with Qt as well.
Comment 4 Ben Creasy 2018-02-23 21:21:48 UTC 
Sounds like this bug got filed with Qt. Unfortunately no copy was made here. Resolving as upstream tho.