Welcome to the most active Linux Forum on the web.
Go Back > Forums > Linux Forums > Linux - Distributions > SUSE / openSUSE
User Name
SUSE / openSUSE This Forum is for the discussion of Suse Linux.


  Search this Thread
Old 06-02-2005, 05:08 PM   #16
Registered: May 2003
Location: London
Distribution: kubuntu 8.10
Posts: 593
Blog Entries: 1

Rep: Reputation: 30

Just got the same problem with 3.4.0 and yorches's suggestion seems to work for me so far.
Old 06-15-2005, 04:06 PM   #17
LQ Newbie
Registered: Oct 2004
Posts: 2

Rep: Reputation: 0
Worked for me too, thanks. I'm also running 3.4 and my problem started after I went in to add a new file association. Just an innocuous change (associating .sxc to OpenOffice) caused this to start happening. Weird. Anyway, thanks for the solution.
Old 07-05-2005, 08:08 AM   #18
LQ Newbie
Registered: Jul 2005
Distribution: Debian - Sarge
Posts: 1

Rep: Reputation: 0
muzhogg: Seems your solution of setting hidden to false has fixed the issue for me.
Old 08-02-2005, 04:31 AM   #19
LQ Newbie
Registered: Apr 2004
Posts: 4

Rep: Reputation: 0
finally solved it for me

I had the same problem and it was driving me crazy. But looking at this forum I found the solution. In the ~/.kde/share/mimelnk/application I had 2 files apart from the octet... one. I had created associations with the control center for fcheck and maya. The problem arose after doing this. I deleted those associations in the control center, but it did not delete the files. I simply deleted these 2 files (fcheck.desktop and maya.desktop) and the problem went away.

Haven't logged out and back in again, so will report when I do.
Old 08-06-2005, 10:54 PM   #20
LQ Newbie
Registered: Aug 2005
Posts: 2

Rep: Reputation: 0
I had the same problem.
It also cause a kdeinit process to hang up and almost block the processor.
I believe that the /tmp/kde-user/ksycoca explanation/fix is misleading. Comparing with other users (who didn't have the problem), they had no file
In contrast, I had. Removing this file solved the problem.
(Afterwards, I also removed the /tmp/kde-user/ksycoca, as removing something in /tmp should generally rather help than harm, therefore I don't know if this was necessary or not. As a matter of fact, the file was recreated.)
Old 08-16-2005, 01:58 PM   #21
LQ Newbie
Registered: Aug 2005
Posts: 1

Rep: Reputation: 0
mime-type error fixed

I had mime-type error while starting k3b. Turns out I have upgraded system (Gentoo) to KDE 3.4, but startx still pointed to and started 3.3. After I changed startx to 3.4 error went away.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Could not find mime type application/octet-stream jon rouse Mandriva 11 02-14-2007 01:18 AM
could not find mime type application/octet-stream WhiteTornado Fedora 7 04-12-2006 12:52 PM
Could not find mime type - application/octet-stream EuroJovi Linux - Software 4 01-26-2006 01:30 PM
Could not find mime type application/octet-stream ERROR CyberDoc Mandriva 10 10-17-2005 08:18 PM
Missing MIME type odat Programming 1 08-16-2001 05:54 AM > Forums > Linux Forums > Linux - Distributions > SUSE / openSUSE

All times are GMT -5. The time now is 10:02 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration