Hangover from kde 3.5 in kde4 when launching file manager after plugging in a SSC card
1i5t5.duncan at cox.net
Sat Nov 28 19:30:44 GMT 2009
Anne Wilson posted on Sat, 28 Nov 2009 16:52:10 +0000 as excerpted:
> On Saturday 28 November 2009 16:40:18 Basil Fowler wrote:
>> Firstly, I was able to sort out yesterday's problem - it was not a KDE
>> matter after all, but a sysconfig problem.
>> But I believe this one is:
>> As I mentioned previously, I have upgraded to Mandriva 2010.0 from
>> 2008.1. When plug in USB storage and click on the icon with the USB
>> sign, a flag comes up with the list "Devices recently plugged in".
>> On clicking on the device, a window appears in the centre of the screen
>> with a list of actions. one action is "Open with File Manager" - so
>> far so good.
>> When I click on this option, I get the error message: KDEinit could not
>> launch openoffic.org-2-2 Could not find openoffice.org2.2 executable
> It seems strange that it should look for OpenOffice if you selected File
>> This is not surprising, since I have not had openoffice.org 2.2 on the
>> computer for a long time.
>> I have "grepped" the entire .kde4 directory for any reference to this
>> program, but have found none.
>> Any hints where to look? File Associations?
> That's certainly the first place I'd look. You'll find it in
> SystemSettings, Advanced tab.
... Or, depending on your "application formerly known as kcontrol,
generically aka system settings", settings (got that, the kcontrol aka
systemsettings settings, even if it doesn't really control many system
settings at all, see that sysconfig setting mentioned above, it's for kde
settings, thus kcontrol is more accurate in any case), under "Advanced
User Settings", "File Associations". That's on kde 4.3.3, kcontrol set
to "classic tree view".
Under file associations, under inode, I'd check blockdev, directory, and
mount-point. Were it a CD/DVD, I'd also check under x-content for the
appropriate media type, but unless you've done something exotic like
format your USB mass-storage as ISO-9660 or some such, that's unlikely to
be of interest, here.
Another place to check, also under advanced user settings, is Device
Actions. That's based on info hal feeds in, with each action available
or not based on a boolean logic tree. The open with filemanager action
should be there. Here, it's set to "kioclient exec %f".
So now we lookup kioclient. Try running kioclient --help in a konsole
window. Here, the interesting option for further information is
kioclient --commands. Running that and checking the exec option, the
"%f" above would be a placeholder for the file (likely presented as a
file:// url), aka the 'url' in the documentation. 'mimetype' is omitted,
so according to that, the mimetype is determined automatically (by file
Which brings us back to file associations, but there's another angle on
them other than the one above. Above, we checked the logical mimetypes
to see if they had any strange OOo associated actions, but the reverse
possibility is that the normal OOo mimetype is for some reason too broad,
and taking in whole filesystems or block devices (presumably fat32 if
you've not formatted the mass-storage otherwise). So that's the other
thing to check there. Do a search for openoffic.org-2-2 and see what
Also note that it's possible, particularly if you upgraded in-place, that
the setting might be in the system mimetypes, not your user mimetypes.
One way to check that would be (from a VT with X not running, or from
Gnome or something other than kde4, at least) to rename your ~/.kde4 dir
temporarily, then log back in with a "clean" user config, and see if the
action happens then. If it does, it's very likely a system config
issue. If not, you know it's in your user kde config. You can of course
revert the temporary test at that point, again logged out of KDE, of
course, deleting the temp config it wrote during the test and replacing
it with your original config, if desired. If you have as many
customizations as I do, you'll desire. If you don't customize much,
it'll probably be no big deal to blow away the old config and start anew,
and simpler to do that than to find the issue.
Another testing alternative, even more thorough, would be to create a
brand new user, entirely fresh home dir, and login to kde as them. If
the problem exists there, you know for sure it's a system problem, since
there was no existing user config at all to even consider. If it
doesn't, you know it's a user config problem.
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
This message is from the kde mailing list.
Account management: https://mail.kde.org/mailman/listinfo/kde.
More info: http://www.kde.org/faq.html.
More information about the kde