"386" -- probably a package with "i386" in the name, as you're running
32-bit Linux for the "Intel" i386/ia32 platform.
I expect some package script saw MySQL processes running, wanted them
stopped, maybe tried to stop them with the normal mysql scripts, and
got mighty unhappy when it saw that there were still some
(Slimserver-started) MySQL processes running.
Fixing a corrupt Debian package manager state is something I've run
into once, and it was unpleasant. I hope someone else here or on the
Ubuntu forums can guide you through fixing that. Web searches got me
through it, but I've been using Linux for over a decade...
It sounds like it's probably a good idea to stop Slimserver when
updating (though that *really* shouldn't be necessary). To do so in
Debian, get a command prompt and run
Code:
--------------------
sudo /etc/init.d/slimserver stop
--------------------
That should stop Slimserver and its MySQL daemon.
Synaptic/Ubuntu/Debian should be smart enough to stop the "real" Ubuntu
MySQL daemon for an update if needed.
Good luck,
Peter
--
peterw
http://www.tux.org/~peterw/
free plugins: http://www.tux.org/~peterw/#slim
BlankSaver BottleRocket FuzzyTime SaverSwitcher SleepFade StatusFirst
VolumeLock
------------------------------------------------------------------------
peterw's Profile: http://forums.slimdevices.com/member.php?userid=2107
View this thread: http://forums.slimdevices.com/showthread.php?t=34317
_______________________________________________
unix mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/unix
