Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
10-21-2013, 07:43 PM
|
#1
|
LQ Newbie
Registered: May 2013
Distribution: Slackware
Posts: 16
Rep: 
|
KDE unable to detect non-text filetypes
Well this is random. I boot my system today and it suddenly doesn't know how to make head or tails of PNG files. (Slackware32 14.0.) I noticed this when trying to run Chrome:
I did #slackpkg reinstall libpng, to no effect. Yes I did recently update libtiff from Slackware-security, but I don't know why that would be related.
Last edited by slimkid; 10-21-2013 at 08:49 PM.
Reason: change topic title
|
|
|
10-21-2013, 07:58 PM
|
#2
|
LQ Muse
Registered: Aug 2005
Location: A2 area Mi.
Posts: 17,673
|
Quote:
I noticed this when trying to run Chrome:
|
so this is a chrome web browser issue and NOT a system issue
reinstalling tiff will not help with png
libpng uses zlib
libtiff uses libjpg
So this is a google chrome web browser problem .
now is this "chromium" or "Chrome"
|
|
|
10-21-2013, 08:29 PM
|
#3
|
LQ Newbie
Registered: May 2013
Distribution: Slackware
Posts: 16
Original Poster
Rep: 
|
It's Chrome, and it's not just Chrome. Like when I navigate in a file browser to a PNG file, it doesn't know what icon to give it (normally it has one), and when I hover over the icon, it says "Unknown" where it would normally say "PNG image" or whatever.
...and it's not just PNG images, apparently. I just figured out my system doesn't know what to do with archives (inc. docx and odt)! Or video files! It's calling them all "unknown". Yet in System Settings > File Associations, everything looks normal....
|
|
|
10-21-2013, 08:38 PM
|
#4
|
LQ Newbie
Registered: May 2013
Distribution: Slackware
Posts: 16
Original Poster
Rep: 
|
Also, attempting to manually open any image in Gwenview returns this error: "Gwenview cannot display documents of type application/octet-stream".
|
|
|
10-21-2013, 10:08 PM
|
#5
|
LQ Muse
Registered: Aug 2005
Location: A2 area Mi.
Posts: 17,673
|
as an experiment and help nail things down
make a new temporary user
and see if that user can see thumbnails of images
and knows the metadata for non text files
|
|
|
10-21-2013, 10:15 PM
|
#6
|
LQ Newbie
Registered: May 2013
Distribution: Slackware
Posts: 16
Original Poster
Rep: 
|
Already tried -- nope.
|
|
|
10-21-2013, 10:29 PM
|
#7
|
Senior Member
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 4,825
|
try reinstalling oxygen-gtk2, oxygen-gtk3, and oxygen-icons
|
|
|
10-21-2013, 10:31 PM
|
#8
|
LQ Newbie
Registered: May 2013
Distribution: Slackware
Posts: 16
Original Poster
Rep: 
|
How would that enable system to begin recognizing non-text filetypes again?
|
|
|
10-22-2013, 01:37 AM
|
#9
|
LQ Muse
Registered: Aug 2005
Location: A2 area Mi.
Posts: 17,673
|
i am not very familiar with Slack
the normal fix for missing meta data for KDE is to rename ~/.kde4 to ~/.kde4.backup and relogin
however the NEW user ALSO had the same problem , so that will not fix it .
so some software chain is busted
re go over the last updates and the error logs
/var/log/????
something errored with the update you did
|
|
|
10-22-2013, 05:47 PM
|
#10
|
LQ Newbie
Registered: May 2013
Distribution: Slackware
Posts: 16
Original Poster
Rep: 
|
The most recent changes on my system are the installation of SDL2, and the upgrade of orc, pysetuptools, hplip, xorg-server (+ graphics driver reinstall), and libtiff. I don't know which log files you would want to see.
Here's my ls -l:
Code:
-rw------- 1 root root 0 Oct 18 04:40 btmp
-rw------- 1 root root 0 Sep 21 04:40 btmp.1
drwxr-xr-x 2 root root 4096 May 30 02:04 ConsoleKit
-rw-r--r-- 1 root root 972 Oct 21 20:43 cron
-rw-r--r-- 1 root root 5832 Oct 17 19:07 cron.1
-rw-r--r-- 1 root root 4212 Sep 21 03:31 cron.2
-rw-r--r-- 1 root root 432 Aug 19 18:05 cron.3
-rw-r--r-- 1 root root 1589 Aug 8 04:06 cron.4
drwxr-xr-x 2 root root 4096 Jun 26 01:53 cups
-rw-r--r-- 1 root root 277899 Oct 21 20:43 debug
-rw-r--r-- 1 root root 1704664 Oct 17 19:07 debug.1
-rw-r--r-- 1 root root 1270797 Sep 21 03:31 debug.2
-rw-r--r-- 1 root root 132127 Aug 20 01:33 debug.3
-rw-r--r-- 1 root root 456246 Aug 8 04:06 debug.4
-rw-r----- 1 root root 62687 Oct 21 20:43 dmesg
-rw-r--r-- 1 root root 24048 Oct 21 19:12 faillog
-rw-r--r-- 1 root root 463 Jun 2 05:53 gufw_log_server.txt
-rw-r--r-- 1 root root 988 Jun 2 05:53 gufw_log.txt
drwxrwxr-- 3 root lp 4096 Oct 18 22:43 hp
drwxr-xr-x 2 root root 4096 May 28 21:57 httpd
drwxr-xr-x 2 root root 4096 Mar 12 2011 iptraf
-rw-r--r-- 1 root root 799508 Oct 21 21:01 kdm.log
-rw-r--r-- 1 root root 292584 Oct 21 20:44 lastlog
-rw-r--r-- 1 root root 402 Oct 18 04:41 maillog
-rw-r--r-- 1 root root 400 Sep 21 04:42 maillog.1
-rw-r--r-- 1 root root 400 Aug 20 04:42 maillog.2
-rw-r--r-- 1 root root 0 Aug 8 04:40 maillog.3
-rw-r--r-- 1 root root 402 Aug 2 04:42 maillog.4
-rw-r--r-- 1 root root 4816484 Oct 21 21:02 messages
-rw-r--r-- 1 root root 5967808 Oct 18 04:40 messages.1
-rw-r--r-- 1 root root 2753500 Sep 21 04:31 messages.2
-rw-r--r-- 1 root root 287072 Aug 20 04:25 messages.3
-rw-r--r-- 1 root root 1002532 Aug 8 04:26 messages.4
drwxr-xr-x 2 root root 4096 May 15 2001 nfsd
drwxr-xr-x 2 root root 69632 Oct 21 20:45 packages
drwxr-xr-x 2 root root 4096 Oct 18 04:40 pgl
-rw-r--r-- 1 root root 2428 Oct 21 20:44 pm-powersave.log
-rw-r--r-- 1 root root 6007 Oct 6 19:06 pm-suspend.log
drwxr-xr-x 2 root root 49152 Oct 21 20:42 removed_packages
drwxr-xr-x 2 root root 45056 Oct 21 20:42 removed_scripts
drwxr-xr-x 2 root root 4096 Apr 25 2010 sa
drwxr-xr-x 2 root root 4096 Aug 30 00:37 samba
drwxr-xr-x 2 root root 4096 May 30 14:56 sbopkg
drwxr-xr-x 2 root root 45056 Oct 21 20:45 scripts
-rw-r--r-- 1 root root 11214 Oct 21 21:01 secure
-rw-r--r-- 1 root root 41618 Oct 17 19:08 secure.1
-rw-r--r-- 1 root root 34827 Sep 21 03:47 secure.2
-rw-r--r-- 1 root root 2270 Aug 19 18:15 secure.3
-rw-r--r-- 1 root root 16550 Aug 8 04:16 secure.4
drwxr-xr-x 3 root root 4096 Sep 30 17:48 setup
-rw-r--r-- 1 root root 0 Oct 18 04:40 spooler
-rw-r--r-- 1 root root 0 Sep 21 04:40 spooler.1
-rw-r--r-- 1 root root 0 Aug 20 04:40 spooler.2
-rw-r--r-- 1 root root 0 Aug 8 04:40 spooler.3
-rw-r--r-- 1 root root 0 Aug 2 04:40 spooler.4
-rw-r--r-- 1 root root 1016557 Oct 21 21:01 syslog
-rw-r--r-- 1 root root 6648826 Oct 18 04:39 syslog.1
-rw-r--r-- 1 root root 5152926 Sep 21 04:39 syslog.2
-rw-r--r-- 1 root root 733291 Aug 20 04:39 syslog.3
-rw-r--r-- 1 root root 2357841 Aug 8 04:39 syslog.4
drwxr-xr-x 2 root root 4096 Jun 9 00:40 teamviewer
drwxr-xr-x 2 uucp root 4096 May 28 21:58 uucp
-rw-r--r-- 1 root root 217119 Aug 8 01:48 vbox-install.log
-rw-r--r-- 1 root root 179 Aug 21 15:00 vbox-uninstall.log
-rw-rw-r-- 1 root voice 1073280 Oct 21 21:02 wtmp
-rw-rw-r-- 1 root voice 1345536 Sep 21 04:39 wtmp.1
-rw-r--r-- 1 root root 62097 Oct 21 21:01 Xorg.0.log
-rw-r--r-- 1 root root 67545 Oct 21 20:42 Xorg.0.log.old
-rw-r--r-- 1 root root 52505 Jul 9 06:10 Xorg.1.log
-rw-r--r-- 1 root root 52629 Jun 4 21:39 Xorg.1.log.old
|
|
|
10-22-2013, 06:22 PM
|
#11
|
LQ Muse
Registered: Aug 2005
Location: A2 area Mi.
Posts: 17,673
|
I would start with " messages"
Code:
su -
kate /var/log/messages
|
|
|
10-22-2013, 07:27 PM
|
#12
|
LQ Newbie
Registered: May 2013
Distribution: Slackware
Posts: 16
Original Poster
Rep: 
|
Not seeing anything strange-looking in there. Anything in particular I should be looking for?
|
|
|
10-22-2013, 07:45 PM
|
#13
|
LQ Newbie
Registered: May 2013
Distribution: Slackware
Posts: 16
Original Poster
Rep: 
|
Here is something new. When I open Dolphin via terminal to view error messages, navigate to a file ~/desktop.png, right click > Properties > Create new filetype, I've gotten this stuff:
Code:
could not reset stream of /home/rkido/desktop.png from pos 65536 to 0 after reading with PngEndAnalyzer:
keditfiletype(3093)/kdecore (trader) mimeTypeSycocaServiceOffers: KMimeTypeTrader: mimeType "application/x-kdeuser1" not found
keditfiletype(3093)/kdecore (trader) mimeTypeSycocaServiceOffers: KMimeTypeTrader: mimeType "application/x-kdeuser1" not found
Not having much luck googling this error though.
|
|
|
10-22-2013, 08:32 PM
|
#14
|
LQ Newbie
Registered: May 2013
Distribution: Slackware
Posts: 16
Original Poster
Rep: 
|
I did some more careful and tedious googling/web-crawling and came upon some answers that were vague, but helpful enough to point me in the right direction.
So with that octet-stream thing, I ran
Code:
find / -name 'octet*'
Which led me to /usr/share/mime/application/octet-stream.xml
I renamed that to octet-stream.xml.bak, refreshed the mime database, and voila -- my system is functional again.
But weirdness remains: now that I've refreshed the mime-database... another octet-stream.xml has popped up. I still don't know how this is being created, or where it's coming from. Yet, my system is functional again, nonetheless....
|
|
|
10-22-2013, 09:34 PM
|
#15
|
Member
Registered: Apr 2011
Location: Canada
Distribution: Slackware
Posts: 99
Rep:
|
Well, octet-stream.xml is a definition for the mime type octet-stream, which is basically any file that is not made of text - a series of bytes. By default, programs don't know what to do with octet-stream files because they are so vague - on my machine, they are .bin files, which should just be executed and nothing else.
It could have been that the definition for octet-stream in your octet-stream.xml was incorrect (the "*.bin" changed to "*" or similar), or that all the mime type definitions were corrupted and octet-stream was a fallback, though I'm not certain how a mime database would be corrupted. In any case, updating your mime database was the correct thing to do.
A good overview of MIME is here.
|
|
|
All times are GMT -5. The time now is 02:12 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|