On Fri, 2012-03-09 at 12:49 -0500, David Rosenstrauch wrote:

Been seeing a weird quirk with KDE's konqueror recently. Was wondering if this is something unique to my personal configuration, or if it's an upstream bug that needs to be filed. Can some KDE user confirm?

1) Launch konqueror in file manager mode. e.g.:

[darose@daroselin ~]$ konqueror /tmp

2) Go to the right pane, which lists the files in /tmp. Find an empty area in the pane and right-click on it. (i.e., don't right-click on a file) That pops up a menu. 3) Select "Create New". That pops up a sub-menu. 4) Select "Text File ...". That pops up a box to enter the file name. 5) Enter a file name of (for example) "foobar.txt". 6) The file that gets created is "foobar.txt.desktop". 7) WTF?!?!?!?!?!?

Anyone else seeing this behavior too?

Thanks,

DR

I've got Xfce only installed. Konqueror does behave the same way here. I just installed kdebase-konqueror a minute ago and didn't change any settings. - Ralf

On Fri, Mar 9, 2012 at 2:49 PM, David Rosenstrauch wrote:

Been seeing a weird quirk with KDE's konqueror recently.  Was wondering if this is something unique to my personal configuration, or if it's an upstream bug that needs to be filed.  Can some KDE user confirm?

1) Launch konqueror in file manager mode.  e.g.:

[darose@daroselin ~]$ konqueror /tmp

2) Go to the right pane, which lists the files in /tmp.  Find an empty area in the pane and right-click on it.  (i.e., don't right-click on a file)  That pops up a menu. 3) Select "Create New".  That pops up a sub-menu. 4) Select "Text File ...".  That pops up a box to enter the file name. 5) Enter a file name of (for example) "foobar.txt". 6) The file that gets created is "foobar.txt.desktop". 7) WTF?!?!?!?!?!?

Anyone else seeing this behavior too?

In my tests, it worked as it should. The file got the right name, just like I typed it. -- A: Because it obfuscates the reading. Q: Why is top posting so bad? For mor information, please read: http://idallen.com/topposting.html ------------------------------------------- Denis A. Altoe Falqueto Linux user #524555 -------------------------------------------

On Fri, Mar 9, 2012 at 4:35 PM, David Rosenstrauch wrote:

Hmmm ... interesting.  So maybe it is something specific to my config after all.

Are you using the latest version of konqueror?  (4.8.1)

Not quite... I'm still using 4.8.0. But I'm at my job right now. I'll test when I get home, in a system using 4.8.1. -- A: Because it obfuscates the reading. Q: Why is top posting so bad? For mor information, please read: http://idallen.com/topposting.html ------------------------------------------- Denis A. Altoe Falqueto Linux user #524555 -------------------------------------------

David Rosenstrauch wrote:

Been seeing a weird quirk with KDE's konqueror recently. Was wondering if this is something unique to my personal configuration, or if it's an upstream bug that needs to be filed. Can some KDE user confirm?

1) Launch konqueror in file manager mode. e.g.:

[darose@daroselin ~]$ konqueror /tmp

2) Go to the right pane, which lists the files in /tmp. Find an empty area in the pane and right-click on it. (i.e., don't right-click on a file) That pops up a menu. 3) Select "Create New". That pops up a sub-menu. 4) Select "Text File ...". That pops up a box to enter the file name. 5) Enter a file name of (for example) "foobar.txt". 6) The file that gets created is "foobar.txt.desktop". 7) WTF?!?!?!?!?!?

Anyone else seeing this behavior too?

Same issue here, both with Konqueror and Dolphin (makes sense as I understand they use the same kpart for file browsing). Latest 64 bits 4.8.1 packages. Jerome -- mailto:jeberger@free.fr http://jeberger.free.fr Jabber: jeberger@jabber.fr

On 03/09/2012 03:02 PM, David Rosenstrauch wrote:

On 03/09/2012 02:51 PM, Denis A. Altoé Falqueto wrote:

...

On Fri, Mar 9, 2012 at 4:35 PM, David Rosenstrauch wrote:

...

Hmmm ... interesting. So maybe it is something specific to my config after all.

Are you using the latest version of konqueror? (4.8.1)

Not quite... I'm still using 4.8.0. But I'm at my job right now. I'll test when I get home, in a system using 4.8.1.

Hmmm ... perhaps this is a change that crept in in 4.8.1 then. Makes sense - I use this piece of functionality a lot, and only noticed this bug recently.

If you could please post back with your findings on your 4.8.1 system, I'd appreciate it, since it'll help me file the bug report.

Thanks,

DR

FYI - looks like there's already an upstream bug report for this: https://bugs.kde.org/show_bug.cgi?id=295490 DR