From: Allan Gottlieb <gottlieb@nyu.edu>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] trouble with evince (mime bad?)--Solved ??
Date: Sun, 15 Feb 2009 19:16:07 -0500 [thread overview]
Message-ID: <yu9eixzi6d4.fsf_-_@nyu.edu> (raw)
In-Reply-To: <yu97i3rlsn6.fsf@nyu.edu> (Allan Gottlieb's message of "Sun\, 15 Feb 2009 08\:46\:37 -0500")
At Sun, 15 Feb 2009 08:46:37 -0500 Allan Gottlieb <gottlieb@nyu.edu> wrote:
> At Sun, 15 Feb 2009 09:40:42 +0200 Alan McKinnon <alan.mckinnon@gmail.com> wrote:
>
>> On Saturday 14 February 2009 01:50:38 Allan Gottlieb wrote:
>>> Recently evince stopped working on one of my machines, ajglap.
>>>
>>> For every pdf, evince opens a window and complains
>>> unable to open document
>>> unhandled mime type
>>
>> As you use evince, you may be a gnome user, so this might not help you. I
>> recently had all my kde associations and (very surprisingly) a number of
>> others from other DEs go scrambled. Rebuilding kdelibs fixed all of it.
>>
>> I never did figure out how this could occur. Possibly it's something to do
>> with DEs converging on freedesktop.org standards, so an oopsie in one can have
>> system-wide side0effects.
>
> Yes, I should have mentioned that I am a gnome user.
> Thank you for responding.
Removing the file ~/.local/share/mime/mime.cache ended the problem.
The last modify date was 2006 and the failure started this month so it
wasn't the contents changing. I am guessing that a new version of
something does not like this old file.
At any rate, evince now handles pdf files as it used to.
allan
prev parent reply other threads:[~2009-02-16 0:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-13 23:50 [gentoo-user] trouble with evince (mime bad?) Allan Gottlieb
2009-02-15 7:40 ` Alan McKinnon
2009-02-15 13:46 ` Allan Gottlieb
2009-02-16 0:00 ` Marcin Zwd
2009-02-16 0:30 ` Allan Gottlieb
2009-02-16 0:53 ` Dale
2009-02-16 7:15 ` Mick
2009-02-16 8:09 ` Marcin Zwd
2009-02-16 0:16 ` Allan Gottlieb [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yu9eixzi6d4.fsf_-_@nyu.edu \
--to=gottlieb@nyu.edu \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox