[prev in list] [next in list] [prev in thread] [next in thread]
List: kde
Subject: Re: [kde] kio_file: WARNING: Could not find mime type
From: Bogus Zaba <bogzab () blueyonder ! co ! uk>
Date: 2005-04-07 22:27:47
Message-ID: 4255B3E3.4060307 () blueyonder ! co ! uk
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Danijel Tasov wrote:
>Hi,
>
>i've updated to KDE 3.4, and now I'm getting these warnings when
>starting konqueror. This wouldn't be annoying to me, but for each
>warning I also get a pop-up-window. Has somebody an idea of what
>is wrong?
>
>kio_file: WARNING: Could not find mime type
>inode/directory
>kio_file: WARNING: Could not find mime type
>inode/directory-locked
>kio_file: WARNING: Could not find mime type
>inode/blockdevice
>kio_file: WARNING: Could not find mime type
>inode/chardevice
>kio_file: WARNING: Could not find mime type
>inode/socket
>kio_file: WARNING: Could not find mime type
>inode/fifo
>kio_file: WARNING: Could not find mime type
>inode/directory
>kio_file: WARNING: Could not find mime type
>inode/directory-locked
>kio_file: WARNING: Could not find mime type
>inode/blockdevice
>kio_file: WARNING: Could not find mime type
>inode/chardevice
>kio_file: WARNING: Could not find mime type
>inode/socket
>kio_file: WARNING: Could not find mime type
>inode/fifo
>kio_file: WARNING: Could not find mime type
>inode/directory
>kio_file: WARNING: Could not find mime type
>inode/directory-locked
>kio_file: WARNING: Could not find mime type
>inode/blockdevice
>kio_file: WARNING: Could not find mime type
>inode/chardevice
>kio_file: WARNING: Could not find mime type
>inode/socket
>kio_file: WARNING: Could not find mime type
>inode/fifo
>kio_file: WARNING: Could not find mime type
>inode/directory
>kio_file: WARNING: Could not find mime type
>inode/directory-locked
>kio_file: WARNING: Could not find mime type
>inode/blockdevice
>kio_file: WARNING: Could not find mime type
>inode/chardevice
>kio_file: WARNING: Could not find mime type
>inode/socket
>kio_file: WARNING: Could not find mime type
>inode/fifo
>
> -DaTa-
>
>
>
I got similar messages (not so many) when I upgraded from Suse 9.0 to
9.2, which I guess involved an upgrade of KDE from something older to
3.3.0. Was not a problem for other users. I guessed that they were
problems with file associations so I played around a bit with these
using Konqueror>Tools>"Configure Konqueror">"File Associations". Seemed
to help a bit for a while but the wrong setup kept being re-generated by
something. In the end I got sick of it and took the more drastic step of
deleting my user .kde directory. This did the trick and had some other
beneficial side-effects - like I lost desktop icons for each of my
Windows partitions which I had never liked or needed. The only
dis-benefit that I remember was that some kde applications acted like
they had never been run (most annoying I think was Kopete where I had to
enter all my contacts again).
Bogus Zaba
>------------------------------------------------------------------------
>
>___________________________________________________
>This message is from the kde mailing list.
>Account management: https://mail.kde.org/mailman/listinfo/kde.
>Archives: http://lists.kde.org/.
>More info: http://www.kde.org/faq.html.
>
[Attachment #5 (text/html)]
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Danijel Tasov wrote:
<blockquote cite="mid20050407211801.GA8698@knast.server-king.de"
type="cite">
<pre wrap="">Hi,
i've updated to KDE 3.4, and now I'm getting these warnings when
starting konqueror. This wouldn't be annoying to me, but for each
warning I also get a pop-up-window. Has somebody an idea of what
is wrong?
kio_file: WARNING: Could not find mime type
inode/directory
kio_file: WARNING: Could not find mime type
inode/directory-locked
kio_file: WARNING: Could not find mime type
inode/blockdevice
kio_file: WARNING: Could not find mime type
inode/chardevice
kio_file: WARNING: Could not find mime type
inode/socket
kio_file: WARNING: Could not find mime type
inode/fifo
kio_file: WARNING: Could not find mime type
inode/directory
kio_file: WARNING: Could not find mime type
inode/directory-locked
kio_file: WARNING: Could not find mime type
inode/blockdevice
kio_file: WARNING: Could not find mime type
inode/chardevice
kio_file: WARNING: Could not find mime type
inode/socket
kio_file: WARNING: Could not find mime type
inode/fifo
kio_file: WARNING: Could not find mime type
inode/directory
kio_file: WARNING: Could not find mime type
inode/directory-locked
kio_file: WARNING: Could not find mime type
inode/blockdevice
kio_file: WARNING: Could not find mime type
inode/chardevice
kio_file: WARNING: Could not find mime type
inode/socket
kio_file: WARNING: Could not find mime type
inode/fifo
kio_file: WARNING: Could not find mime type
inode/directory
kio_file: WARNING: Could not find mime type
inode/directory-locked
kio_file: WARNING: Could not find mime type
inode/blockdevice
kio_file: WARNING: Could not find mime type
inode/chardevice
kio_file: WARNING: Could not find mime type
inode/socket
kio_file: WARNING: Could not find mime type
inode/fifo
-DaTa-
</pre>
</blockquote>
I got similar messages (not so many) when I upgraded from Suse 9.0 to
9.2, which I guess involved an upgrade of KDE from something older to
3.3.0. Was not a problem for other users. I guessed that they were
problems with file associations so I played around a bit with these
using Konqueror>Tools>"Configure Konqueror">"File
Associations". Seemed to help a bit for a while but the wrong setup
kept being re-generated by something. In the end I got sick of it and
took the more drastic step of deleting my user .kde directory. This did
the trick and had some other beneficial side-effects - like I lost
desktop icons for each of my Windows partitions which I had never
liked or needed. The only dis-benefit that I remember was that some kde
applications acted like they had never been run (most annoying I think
was Kopete where I had to enter all my contacts again).<br>
<br>
Bogus Zaba<br>
<br>
<blockquote cite="mid20050407211801.GA8698@knast.server-king.de"
type="cite">
<pre wrap=""></pre>
<pre wrap="">
<hr size="4" width="90%">
___________________________________________________
This message is from the kde mailing list.
Account management: <a class="moz-txt-link-freetext" \
href="https://mail.kde.org/mailman/listinfo/kde">https://mail.kde.org/mailman/listinfo/kde</a>.
Archives: <a class="moz-txt-link-freetext" \
href="http://lists.kde.org/">http://lists.kde.org/</a>. More info: <a \
class="moz-txt-link-freetext" \
href="http://www.kde.org/faq.html">http://www.kde.org/faq.html</a>.</pre> \
</blockquote> <br>
</body>
</html>
___________________________________________________
This message is from the kde mailing list.
Account management: https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic