Bug 250399

Version:           2.5 (using KDE 4.5.0) 
OS:                Linux

Let's say you create a valid profile file like "hostname.somedomain.org" through some method.  You can start a new tab using the profile if you're already in konsole.

But if you now try to start up konsole via the command:

konsole --profile hostname.somedomain.org

it will fail.  Rename the same profile file to just "hostname" and

konsole --profile hostname

will work.  OR specify the full path to the file with the original name:

konsole --profile ~/.kde4/apps/konsole/hostname.somedomain.org

That works too, but to re-iterate:

konsole --profile hostname.somedomain.org

fails to start the desired profile and falls back to the default profile.  Note that this command:

konsole --list-profiles 

will list your profile files truncated at the first peroid so if I've got both the original "hostname.somedomain.org.profile" and "hostname.profile" files then the result is:

konsole --list-profiles 

hostname
hostname

Note that this bug has implications for the interaction between konsole and the konsoleprofiles widgit and perhaps other kde applications as well.  If you keep trying to start a profile from the widgit like "hostname.somedomain.org" you will get the default profile instead.

While I haven't played around with it, konsole might suffer from other file name parsing problems, the most important ones to check would be probably be "@" and space, but honestly, any file-name ending in ".profile" SHOULD be valid and work the same way as any other profile file-name.

Reproducible: Always

Steps to Reproduce:
execute, from your favorite terminal emulator in X11:

konsole --profile hostname.somedomain.org

Actual Results:  
start konsole with the default profile (or if you have have a profile file named "hostname.profile" I'll bet you'll start THAT profile)

Expected Results:  
start konsole with the profile "hostname.profile".

OS: Linux (x86_64) release 2.6.35-ARCH
Compiler: gcc

I think this bug should be easy to fix, because it's almost certainly a very basic implementation error of how konsole parses profile file-names.  It's annoying  because it causes mysterious behavior in konsole profiles, and it's also annoying because I want o name konsole profiles designed explicitly to initiate ssh sessions something like "hostname.somedomain.org" and have the file-name and profile-name agree.