Version: 1.1.75+ #3400 (using 4.2.1 (KDE 4.2.1) "release 103", KDE:KDE4:Factory:Desktop / openSUSE_11.1) Compiler: gcc OS: Linux (x86_64) release 2.6.27.19-3.2-default I usually see the message: KDEinit could not launch '/usr/bin/konvi' each time I run konversation KDE4. Plus if I don't close konversation before logging out or rebooting, and konversation is automatically started on login, the error message dialogue box is not shown, but it shows up when I try to logout or shutdown, preventing my system from shutting down until I have clicked on close. I do not have konversation KDE3 installed. 'konvi' is present on my machine in the following locations: konvi: /usr/bin/konvi /usr/bin/X11/konvi -rwxr-xr-x 1 root root 2.1M 2009-03-13 11:38 /usr/bin/konvi* -rwxr-xr-x 1 root root 2.1M 2009-03-13 11:38 /usr/bin/X11/konvi*
Just to clarify, konversation DOES still work if I either click on OK or simply ignore the massage. This is running under KDE4.2.1 openSUSE 11.1 - 64bit, clean install.
SVN commit 940136 by pino: add dbus service name CCBUG: 187246 M +1 -0 konvi.desktop WebSVN link: http://websvn.kde.org/?view=rev&revision=940136
Can you still reproduce the problem with a more recent version?
I have all the latest updates that have been released through opensuse updates, the version numbers now show: Konversation Version 1.1.75+ #3400 Using KDE 4.2.1 (KDE 4.2.1) "release 106" So I guess that means it's the same version, just a newer build of KDE? That's odd though because I could swear I saw several updates to Konversation come in with all the other KDE4 updates over the last week or so! Sorry, I'm a user not a programmer :(. And yes, it still does the same thing.
The openSUSE packages currently contain checkouts of our SVN code repository; we have not made any public releases yet. The version number and build number haven't been changed in the source lately, so you may well have gotten Konversation updates without this string of characters changing.
I'm quite willing to help in any way, just give me instructions, or ask any questions :) Regards.
The problem is now fixed with today's updates. Thankyou very much :)