You could make a quick dirty "script" to fix it, I usually would do that manually, but it WILL mess up anything else in the /etc/ that you changed for your purposes.
but what your doing would be: finding all files in /etc if the file has *.dpkg-new cp that to just * Any compiled package has the specific file name/path of the "config" it needs to start up, it doesn't want config.dpkg-new. You can see that it is a different file name yourself. ubuntu's karmic install doesn't take into account that you will quit in the middle. jon. On Tue, Sep 15, 2009 at 5:11 PM, Jon Bradley <[email protected]> wrote: > well "my solution" wouldn't be an absolute one as I was saying, again, I'll > tell you it looks like the /etc/ files are being mv'd to the *.dpkg-new, and > WITHOUT ANY of the '/etc' file, WHATEVER IT IS xorg, init etc. That > "system" xorg, init, etc. will not work. > > So, where ever your upgrade stops, meaning it was stopped at any point in > time in the upgrade, which means it was a different "system" xorg, init, > etc, things that you would notice on your system not booting. There is a > /etc file missing. > > to summery THERE IS NO CONFIGURATION ANYMORE in that specific "system". > > It seems to rename them, so that hacked up fix would to to rename them > back. > That is all. > > -------------------- > by the word "system": X windows, Init scripts, Gnome, (well gnome is over > X, remember that too) .. This bug is about "Quitting the upgrade premature, > then you notice it doesn't boot" --- other things (to this effect, say you > don't have a syslog) could actually happen. > > I'm just trying to describe and define it here. > not offer the "right" fix, thats for the ubuntu guys :) > > peace. > > > > On Tue, Sep 15, 2009 at 2:33 PM, AnthonyC <[email protected]> wrote: > >> Yeah, having the same problem too. I did was the update manager >> suggested, a partial upgrade... then rebooted... now, I can't get Gnome >> back! arrr...missing NBR! >> >> Seems like the update manager held two packages back, the upstart and >> initscripts. >> >> Don't know what you mean by "fixed after normal upgrade"...but I sure >> would like to get my Karmic NBR back! >> >> I checked the above solutions... don't have any of the suggested files >> sitting in /etc/init >> >> Anyone? >> >> -- >> Karmic Koala stopps dead after /scripts/init-bottom >> https://bugs.launchpad.net/bugs/398214 >> You received this bug notification because you are a direct subscriber >> of the bug. >> >> Status in Ubuntu: New >> >> Bug description: >> Hi, >> >> After an update yesterday my Karmic installation no longer completely >> boots in any kernel (in safe or other wise) I have kernels 2.30.8, 2.30.9 >> and 2.30.10 installed. >> >> When not in safe mode I see the splash screen the the screen goes blank >> and nothing happens. I can press Alt-F1 and what I see something like the >> following: >> >> kinit: name_to_dev_t(/dev/disk/by-uuid/...) - dev(8,3) >> kinit: trying to resume from /dev/disk/by0uuid/... >> kinit: No resume image, doing normal boot... >> >> In safe mode I see the above with the following additional lines: >> >> Begin: Running /scripts/local-bottom ... >> Done. >> Done. >> Begin: Running /scripts/init-bottom ... >> Done. >> [ 42.560077] CE: hpet increasing min_delta_ns to 15000 nsec >> >> Immediately after updating X appeared to have died but I could access >> virtual terminals now after attempting to reboot (with all kernels) I never >> get any virtual terminals. >> >> Regards, >> Ivan Wills >> > > -- Karmic Koala stopps dead after /scripts/init-bottom https://bugs.launchpad.net/bugs/398214 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
