Updates killed my Kubuntu

[Indigas]

Well Hello all, yesterday installed Kubuntu, after i made updates, after restart when try too boot in Kubuntu i got an error doesnt remember which error....And formated that HDD today and installled Kubuntu again, now i am scared for installing updates, any ideas plz ?

[arochester]

Re: Updates killed my Kubuntu

What updates? What was the error message? Very often Kubuntu can be recovered...

[disturbedite]

Re: Updates killed my Kubuntu

possibly the recent libc6 update? everyone should have known about that one, it was all over the linux world...i was even bitten by it. but it was an easy recovery:
simply booted with a livecd & told dpkg to install the previous version of libc6 on my system.

[Fintan]

Re: Updates killed my Kubuntu

Which version of Kubuntu did you install? Gutsy (7.10) or Hardy (beta 8.04) or kde4 alpha?

[DracoTB]

Re: Updates killed my Kubuntu

possibly the recent libc6 update? everyone should have known about that one, it was all over the linux world...i was even bitten by it.

Perhaps not all of us were monitoring the Linux World yesterday? :P

but it was an easy recovery:
simply booted with a livecd & told dpkg to install the previous version of libc6 on my system.

For those who are used to these things but maybe not to those of us who've only just started.

The error I got after installing the updates was something like:

kernel panic, no sync

and then nothing. Is this the error that you speak of?
If it is I'll just leave that update out and apply all of the other 158.

[Indigas]

Re: Updates killed my Kubuntu

Which version of Kubuntu did you install? Gutsy (7.10) or Hardy (beta 8.04) or kde4 alpha?

Gutsy (7.10)

[Snowhog]

Re: Updates killed my Kubuntu

For Gutsy Installations:

Open Adept Manager (K Menu | System | Adept Manger) and click on Adept | Manage Repositories. On the first tab, check all items (you don't need the last item checked unless you intend to download source files for compiling). On the Third-Party Software tab uncheck/delete the cdrom repository entry. Close the window. If Adept doesn't automatically fetch updates, click on Fetch Updates. You will now have access to the thousands of available packages. If you still have problems, open a console and type:

sudo dpkg --configure -a

If after this, you still have Adept problems, then:

To fix Adept errors:

Open a console and type:

sudo dpkg --configure -a

should fix it, else continue with

sudo apt-get clean

sudo apt-get update

sudo apt-get install

[DracoTB]

Re: Updates killed my Kubuntu

http://img.photobucket.com/albums/v2...1337/error.png

That happened yesterday as well and afterward I got a 'Out of Range' error from my monitor. Ended up having to reinstall again. I don't want to restart at the moment because I'm fairly sure it will do the same thing again.

[Runaway1956]

Re: Updates killed my Kubuntu

Rule of thumb for updates, on any Unix like system: DO NOT INSTALL ALL AVAILABLE UPDATES!!

I like Adept Manager, it seems as reliable as any manager I've ever fooled with. Or more so, maybe.

Open Adept, tell it to update itself, then open the menu again, and choose SAFE UPDATES. I'm new to Ubuntu, but I've run three versions of Suse Linux, as well as two other Debian distros. Doing a full upgrade of everything on your machine is almost guaranteed to break dependencies.

I think all package managers today have an option for "safe" upgrades. Some of them are safer than others, but I know that Adept worked satisfactorily on my machine.

If you have the patience to once again install Ubuntu, and follow my advice, be sure to decline the updated driver for your video card. That is almost certainly what is causing your monitor to display the "out of range" message. Save the video driver update for another thread, and another upgrade session.

[DracoTB]

Re: Updates killed my Kubuntu

It's actually come back up this time but I can't access Adept Manager. I get this even on a restart.

Another process is using the packaging system database (probably some other Adept application or apt-get or aptitude).
Would you like to attempt to resolve this problem? No will enter read-only mode and Cancel to quit and resolve this issue yourself.

This is the crash report that I get when I hit yes. Crashed with signal 6 (SIGABRT)

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1235675456 (LWP 6280)]
(no debugging symbols found)
[KCrash handler]
#6 0xffffe410 in __kernel_vsyscall ()
#7 0xb65ec875 in raise () from /lib/tls/i686/cmov/libc.so.6
#8 0xb65ee201 in abort () from /lib/tls/i686/cmov/libc.so.6
#9 0xb67f86e0 in __gnu_cxx::__verbose_terminate_handler ()
  from /usr/lib/libstdc++.so.6
#10 0xb67f5f65 in ?? () from /usr/lib/libstdc++.so.6
#11 0xb67f5fa2 in std::terminate () from /usr/lib/libstdc++.so.6
#12 0xb67f60ca in __cxa_throw () from /usr/lib/libstdc++.so.6
#13 0x0812b916 in ?? ()
#14 0x0812be8a in ?? ()
#15 0x0812bee8 in ?? ()
#16 0x0812c735 in ?? ()
#17 0x0812a22d in ?? ()
#18 0x08114379 in ?? ()
#19 0x080951ed in ?? ()
#20 0x0807378d in ?? ()
#21 0x0807408e in ?? ()
#22 0xb6e3c893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#23 0xb71c88ec in QSignal::signal () from /usr/lib/libqt-mt.so.3
#24 0xb6e5c842 in QSignal::activate () from /usr/lib/libqt-mt.so.3
#25 0xb6e64258 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
#26 0xb6dd3af0 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#27 0xb6dd591f in QApplication::notify () from /usr/lib/libqt-mt.so.3
#28 0xb7599cd2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#29 0xb6d66209 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#30 0xb6dc653b in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#31 0xb6d7ad49 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#32 0xb6dee1ce in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#33 0xb6dedfde in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#34 0xb6dd5699 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#35 0x0806f75e in ?? ()
#36 0xb65d8050 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#37 0x0806f401 in ?? ()

I can't see any processes in the list that would be preventing Adept Manager from accepting the password so that it can work.

[DracoTB]

Re: Updates killed my Kubuntu

Ok, after 9 hours of installing and reinstalling Kubuntu I've discovered some of what Adept is doing wrong.

When confronted with what appears to be a later version of a program/library by a different author it defaults to leaving the old version there even though the programs being installed need the newer version. This wouldn't be the problem it is if Adept actually took note of the errors and informed you of them and then undid the upgrading that depends on the newer version.

What I need to know ATM though is:
1) How do I tell if the later version has been installed or not and
2) How do I then set it up

The program I need to know about is qt3

[Indigas]

Re: Updates killed my Kubuntu

i am just scared to do updates again... After every my trying i need to reformat those partitions

[Indigas]

Re: Updates killed my Kubuntu

and again.. after updates... Kubuntu is dead.... :/

When i try to PowerUP Computer and Boot into Kubuntu i just see black screen, when i try too boot into Kubuntu Recovery mode, in Console i try to type KDM and i just see black screen then (((

[DracoTB]

Re: Updates killed my Kubuntu

http://img.photobucket.com/albums/v2...adepterror.png

dpkg reports "libqt3-mt is not configured yet"

libqt3-mt is most definitely installed and, I would assume, configured. Interestingly enough I get this error while trying to upgrade libqt3-mt.

[Runaway1956]

Re: Updates killed my Kubuntu

I'm not experienced enough to walk anyone through a rescue of a botched system. All I can tell you, is what I have done in similar circumstances:

Reformat, reinstall, then exercise care when choosing updates.

I've not yet explored all the possible repositories for Kubuntu, but I totally wrecked an installation of OpenSuse 10.2 just by using every repository I could find. There were broken dependencies that a Super Nerd would have difficulties with.

Always choose "safe update", until you are very experienced, or someone you trust advises you differently.