Comment 8 for bug 150465

I had recently upgraded from Ubuntu 7.10 to 8.04. There must have been some transmission errors in the data coming off the Internet during the update, as I ended up with a very buggy system. I restored my original system, from a tar archive, on top of the 8.04 installation (may not have been a good idea?). On first boot, I discovered that I could not "sudo" (unable to resolve host "casi", was the message, as best I can remember), and I was unable to access certain things from the menu--most n otably the Synaptic update manager. On second boot, I received a flurry of "crash detected" messages that came in so fast I was unable to deal with them. The first one opened Firefox on a Launchpad page--the successive ones opened additional Launchpad pages. The top page (last crash report) required me to sign in, which I did, then proceeded to fill in the requested information. When I went to the next page, it too blocked me from doing anything, until I logged in, but when I tried to log in, it wiped the page clean and posted the notice that I was already logged in, so the information for the bug report was lost. All the other pages did the same thing, so only one bug got reported. The next boot resulted in the system hanging, during boot up. The message was that the root drive could not be found. It posted the correct UUID for my HDD, but then said it didn't exist, and dropped me into a shell. I read through the script files, and found where the message was coming from, but was unable to determine the source of the failure. Since then, I have tricked the system into working--sort of--and have recovered some of the information the system had created for the crash reports. The info related to this particular crash follows:

ProblemType: Crash
Architecture: i386
Date: Fri Apr 25 01:24:40 2008
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/file-roller
NonfreeKernelModules: cdrom
ProcCmdline: file-roller file:///home/bili/Documents/BitTorrent%20meta%20files/BitTorrent%20seed%20files/HOT%20DRUNK%20BITCHES%20-%20Fucking%20at%20a%20Sex%20Orgy%20Party%20-%20Cute%20Girls%20Fucking%20Till%20They%20CUMMM!!/HOT%20DRUNK%20BITCHES%20-%20Fucking%20at%20a%20Sex%20Orgy%20Party%20-%20Cute%20Girls%20Fucking%20Till%20They%20CUMMM!!.rar
ProcCwd: /home/bili
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
<there was a lot of seemingly redundant data in here--if you need it, let me know.>
Package: file-roller 2.20.0-0ubuntu1
PackageArchitecture: i386
Registers:
 eax 0x0 0
 ecx 0x0 0
 edx 0x1 1
 ebx 0x8107868 135297128
 esp 0xbfb16780 0xbfb16780
 ebp 0xbfb167b8 0xbfb167b8
 esi 0x846e7e0 138864608
 edi 0xffffffff -1
 eip 0x80760a7 0x80760a7 <gtk_tree_view_set_enable_search@plt+137599>
 eflags 0x10246 [ PF ZF IF RF ]
 cs 0x73 115
 ss 0x7b 123
 ds 0x7b 123
 es 0x7b 123
 fs 0x0 0
 gs 0x33 51
SourcePackage: file-roller
Stacktrace:
 #0 0x080760a7 in ?? ()
 #1 0x080ba890 in ?? ()
 #2 0x00000010 in ?? ()
 #3 0x00000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
ThreadStacktrace:
 .
 Thread 1 (process 8070):
 #0 0x080760a7 in ?? ()
 #1 0x080ba890 in ?? ()
 #2 0x00000010 in ?? ()
 #3 0x00000000 in ?? ()
Title: file-roller crashed with SIGSEGV