Unable to create comments if file has [] or {} as part of the filename

[Rod J]

Hi all fellow Kubuntu'ers,

I was about to report this on the KDE bug report site but thought I might run it past everyone here in case I'm mistaken about it being a bug.

This is what I was going to post on the KDE bug site:

"Hi, I'm using Dolphin 2.0 on Kubuntu 12.04.03 LTS (KDE 4.8.5).

I'm not sure if this bug should be reported on Dolphin or more likely it is a Nepomuk issue.

I like to comment a lot of files and recently I noticed that I could not get a comment on a file to 'stick' so to speak. It would seem to comment OK but if I switched away from that file to another one and then went back to the previous file the comment had disappeared.

I eventually discovered that any filename with square brackets "[ ]" or braces "{ }" is affected (parenthesis seem to be OK though). I was completely baffled for a while until I tracked down what was unique about the filename.

The behaviour is always reproducible and I tested it with multiple files with and without extensions, e.g.: "Text[file].txt", "Text[]file", "Text{file}", etc."

Thoughts anybody? Should I report it as a bug? Of course this problem may not exist in later versions of Kubuntu/KDE so I'd be interested to know if that is the case too.

Thanks.

[Rog132]

Tested with the Saucy / KDE 4.11.2. The commenting with the [] or {} as part of the filename seems to work.




Working with the Raring / KDE 4.10.5

Not working with the Quantal / KDE 4.9.5

Not working with the Precise / KDE 4.8.5


It is probably the Nepomuk - The Nepomuk has seen lot of upgrades.

The current developer blog: http://vhanda.in/blog/

With the KDE 4.10 there was - What's new with Nepomuk 4.10: http://vhanda.in/blog/2013/01/what-n...-nepomuk-4-10/


KDE upgrades for the Precise:

http://www.kubuntu.org/
--> http://www.kubuntu.org/news/kde-sc-4.11.97
----> http://www.kubuntu.org/news/kde-sc-4.11.2

[Rod J]

Thanks Rog132, a very detailed report!

I like your animated gif too, that's very cool.

I'm still a little hesitant to upgrade to KDE 4.11 even though I've had many issues with nepomuk crashes and Akonadi bugs too in 4.8.5. This bug is just another problem I guess and it's certainly making me think I should dump 4.8.5.

Thanks for confirming the bug for me. I will report the bug now, perhaps they can apply the fix to the older KDE too.