SOLVED - KDE 4.7 update - now wont boot

[keys84]

basically i let kubuntu do he kde updates yesterday (which i presume were 4.7)
it put all new kde apps on

it now wont boot past the cups loading
then stops dead

ive tried changing the name of .kde folder to .kde1 (dont know if this is enough of a change)
also deleted a folder that was in /tmp that i thought might be the cause

but it doesn't even want to boot the kernel is the way it looks to me

fsck from util-linux-ng 2.17.2
fsck from util-linux-ng 2.17.2
/dev/sda1: clean, 231189/652800 files, 1457036/2610554 blocks
/dev/sda7: clean, 66846/6356992 files, 20274537/25410798 blocks
init: ureadahead-other main process (441) terminated with status 4

 * Starting network connection manager[ OK ]
 * Stopping Mount filesystems on boot[ OK ]
 * Starting configure network device security[ OK ]
 * Starting configure network device[ OK ]
 * Stopping cold plug devices[ OK ]
 * Stopping log initial device creation[ OK ]
 * Starting enable remaining boot-time encrypted block devices[ OK ]
 * Starting configure network device security[ OK ]
 * Starting configure virtual network devices[ OK ]
 * Stopping configure virtual network devices[ OK ]
 * Stopping enable remaining boot-time encrypted block devices[ OK ]
 * Starting CUPS printing spooler/server[ OK ]
 * Starting emergency keypress handling[ OK ]
Checking for running unattended-upgrades: * Stopping device node and kernel event manager[ OK ]
 * Stopping system logging daemon[ OK ]
 * Stopping mDNS/DNS-SD daemon[ OK ]
 * Stopping CUPS printing spooler/server[ OK ]
 * Stopping emergency keypress handling[ OK ]
 * Starting System V runlevel compatibility[ OK ]
 * Starting save system clock to hardware clock[ OK ]
 * Starting save sound card(s') mixer state(s)[ OK ]
 * Stopping Bridge udev events into upstart[ OK ]
 * Stopping save sound card(s') mixer state(s)[ OK ]
 * Stopping save system clock to hardware clock[ OK ]
modem-manager[469]: <info> Caught signal 15, shutting down...


init: Disconnected from system bus

init: dbus main process (449) killed by TERM signal


Warning: Fake initctl called, doing nothing.

[keys84]

Re: SOLVED - KDE 4.7 update - now wont boot

I reinstalled

Im thinking of changing OS again
shame i got so used to it over the past couple of years (ever since kde4 came out)

but if i have to keep reinstalling to make it work i may as well be using XP
i do LOVE all the programs written for kde though.

still dont know why the kernel wouldnt load
think there was an error with the update
it struggled to load the new image kept hanging - probably this laptop causing problems again

[dibl]

Re: SOLVED - KDE 4.7 update - now wont boot

it struggled to load the new image kept hanging - probably this laptop causing problems again

If that turns out to be the problem, then switching OSs won't be a solution.

[Guest]

Re: SOLVED - KDE 4.7 update - now wont boot

I had the same issue. I let KPackagekit do updates - lots of them and a lot of them were applications. After it was finished my laptop was running slowly so I rebooted and it kept hanging at the 'check unattended upgrades' stage.

I tried lots of chrooting from a live CD and in the end I gave up and reinstalled. I'm worried about updating my system now incase it happens again.

[Snowhog]

Re: SOLVED - KDE 4.7 update - now wont boot

I say this from experience only and do not claim to be a subject matter expert, but allowing KPackagekit to 'upgrade' ones system is not 100% risk-free. I do not permit KPackagekit to upgrade anything on my systems - I do all my package management from the console using apt-get. I've never experienced any problems doing it this way - none.

sudo apt-get update

Forces a refresh of the package cache information, and should always be performed prior to doing any actual package management.

sudo apt-get dist-upgrade

dist-upgrade
      dist-upgrade in addition to performing the function of upgrade, also
      intelligently handles changing dependencies with new versions of packages;
      apt-get has a "smart" conflict resolution system, and it will attempt to upgrade
      the most important packages at the expense of less important ones if necessary.
      So, dist-upgrade command may remove some packages.

as opposed to

sudo apt-get upgrade

which is, I believe, what KPackagekit uses.

upgrade
      upgrade is used to install the newest versions of all packages currently
      installed on the system from the sources enumerated in /etc/apt/sources.list.
      Packages currently installed with new versions available are retrieved and
      upgraded; under no circumstances are currently installed packages removed, or
      packages not already installed retrieved and installed. New versions of currently
      installed packages that cannot be upgraded without changing the install status of
      another package will be left at their current version.

I believe that it is still the case, that KPackagekit does not handle dependencies, which is why do not use it for package management.