Le dimanche 11 mai 2008 à 18:42 -0400, Noah Meyerhans a écrit : > On Sun, May 11, 2008 at 01:58:22AM +0200, Josselin Mouette wrote: > > > When trying to remove gdm, which is not currently running, I get the > > > following: > > > > > > streaker:~# dpkg -r gdm > > > (Reading database ... 156521 files and directories currently installed.) > > > Removing gdm ... > > > Stopping GNOME Display Manager: gdminvoke-rc.d: initscript gdm, action > > > "stop" failed. > > > dpkg: error processing gdm (--remove): > > > subprocess pre-removal script returned error exit status 1 > > > Scheduling reload of GNOME Display Manager configuration: gdminvoke-rc.d: > > > initscript gdm, action "reload" failed. > > > Errors were encountered while processing: > > > gdm > > > > > > In prerm, the call to invoke-rc.d to stop gdm should probably be > > > followed with "|| true". Or maybe there should be a check to verify > > > that gdm is actually running before calling invoke-rc.d. > > > > I’m sorry, but I can’t reproduce that. In fact, if you look at gdm.init, > > you’ll see that it never fails for the stop action, so I don’t > > understand how you could get this error. > > Well, it happened; I'm not making this up.
I’m not saying that, but I don’t have a clue. Is your /etc/init.d/gdm script customized one way or another? > I wonder about the second > part of the dpkg output, where it says "Scheduling reload of GNOME > Display Manager configuration" and calls the init script with the reload > option. I can't imagine why "dpkg -r" would be triggering a reload, > though. This is when the old postinst is called in abort-upgrade mode. This one as well should never fail with the init script as currently written. Cheers, -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `- our own. Resistance is futile.
signature.asc
Description: Ceci est une partie de message numériquement signée
