[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: KDE Automount stopped working



On Thu, Aug 21, 2008 at 10:34:53 -0400, Kumar Ravichandran wrote:
> On Thu, Aug 21, 2008 at 08:19:56AM +0200, Florian Kulzer wrote:

[...]

> > How is the overall state of your system, is it fully upgraded? I ask
> > because your version of Mutt is too new for Etch, but older than what
> > you should have for up-to-date Lenny or Sid. Is it possible that you ran
> > into a problem that has long been fixed on current Lenny/Sid, or a bug
> > that is only present for a certain mix of more-or-less outdated
> > packages?
> 
> Well, my initial install was from the Etch DVDs, but I had a mixture
> of Etch and lenny for a while. I recently did a dist-upgrade to lenny,
> but have a few sid packages from somewhere (I think during a failed
> KDE 4.1 install attempt). Anyway, I had Etch/lenny when the automount
> stopped working. I hope that answers your question.

The automatic handling of removable media requires that many different
components work together - the kernel, udev, hal, dbus, assorted KDE
libraries and services. I am not too surprised that it does not work
with the kind of mix that you seem to have on your system.

I suggest that you make up your mind which branch of Debian you want to
use and then downgrade/upgrade/remove/add packages as is necessary until
your entire system comes from that one branch only.

You can use the following command to find out which ones of your
currently installed packages do not belong to your intended target
archive ("testing" in this example, replace this string if you decide on
something else):

aptitude -F '%p%t' search '~S ~i !~Atesting' | column -t

-- 
Regards,            | http://users.icfo.es/Florian.Kulzer
          Florian   |


Reply to: