** Description changed:
+ Hi,
+
+ I think it is actually reproducible, but not necessarily with update-
+ manager. What I did was ending my gnome-display-manager session with
+ alt-ctrl-F2. Sometimes I do this with alt-ctrl-backspace. The reason is
+ a crash of the GUI, where I can still move the arrow (cursor) over the
+ Desktop display, but I can no longer open any application by clicking on
+ an icon, not even a terminal for some reason. Sometimes when I have a
+ heavier crash I just have to use the soft reboot button. I am now using
+ the alfa 3 Intrepid, possibly updated to alfa 4? I did this mainly
+ because I needed network manager 0.7.0 to get my 3 mobile broadband USB
+ modem to work (Huawei E220). I mind you there, that I don't know how to
+ put information into the bug tracking system through the terminal, so
+ therefore I cannot report these problems. Possibly other newbies will
+ experience the same problem. Is there a way to reach launchpad through
+ the command line. Anyway, to reproduce the situation, sometimes the
+ display crashes, mostly due to an application crash I think. I have 3
+ applications that crash on a regular basis. These are Virtual Box 1.6.4,
+ firefox and gnome-terminal. I use the new VirtualBox because VMWare is
+ not compatible with my hardware and I need the USB support of the newer
+ versions. Sometimes it crashes, but run sudo apt-get update, upgrade and
+ dist-upgrade several times a day, as well as dpkg-reconfigure -a and
+ apt-get install -f and update-manager -d and synaptic. I reboot
+ frequently. So sometimes this vbox thing works and sometimes not. I
+ think there is a problem with getting the right info to you, because you
+ people care more about my security than I do. The terminal stopped
+ working for no good reason and is still broke I now use terminal.app or
+ Konsole. Firefox stopped working because I downloaded 5 other languages:
+ Dutch, French, German and Spanish and also several plugins. So I usually
+ do apt-get source and build-dep and then some updates and stuff, when a
+ package stops working. Sometimes I can still use all my display windows,
+ except the ones for applications that I opened after one of the above
+ mentioned applications crashed. Sometimes the display freezes and I can
+ only move the cursor (arrow), but not open any icons or due a right-
+ click with the touchpad button. In more extreme case I can not even move
+ the cursor anymore. In that case I cannot reach the command line with
+ alt+ctrl+F2 or alt+ctrl+backspace either and I must reboot using the
+ soft reboot button. I am beginning to assume that there may be a time
+ progression relationship between the three different forms of this bug.
+ The mildest form occurs unrelated to time. But the medium one, where I
+ can still move the cursor and reach the command line, will progess to a
+ total freeze if I don't kill the display and I have to use the soft
+ reboot key then. I think this means the PCU gets into a loop, possibly
+ because of the display application, or possibly by something else.
+ Anyway, when I have rebooted, then I often get the star mentioning an
+ application crashed, please report. I always choose report, but often I
+ can't connect and get a bad gateway warning. I click on close and then
+ that information is lost. In other instances I can reach launchpad, but
+ the title I get (is your bug one of these?), is identical to a
+ previously reported bug. I then just close the window, because when I
+ click report a new bug, the bug team will say, already exist, but please
+ feel free .... on so on. The other option is subscribe to the bug, but
+ then my mail box gets spammed. So I mean: I have a bug that shortcuts my
+ CPU capacity, due to failure in either vbox, terminal or firefox. Then
+ the display freezes and I have to reboot, through the command line or
+ the soft reboot. Whatever application I used after one of the three
+ previously mentioned failed, gets reported through the bug report
+ system. But possibly this is caused by a totally different bug all
+ together. And the bug team replies: already exists or invalid because
+ unable to reproduce. This is normal, because I usually reconfigure the
+ package after the application crashes and other stuff, apt-get source
+ and apt-get build-dep and update or upgrade, so this may be an issue. Or
+ it might be another application I open as the processor is getting in a
+ loop (or the ROM? I have upgraded it to 2GB, and everything works just
+ fine, Vista and Ubuntu). This bug I just report says update-manager
+ crashes. But this is because I did alt+ctrl+F2 to close the display and
+ get login and password in terminal mode. After I login and do update and
+ upgrade and stuff, I tried to do update-manager -d but get cannot open
+ display message and then sudo reboot. Then I get the report problem
+ popup, but the title of it does probably not reflect the cause of the
+ bug. It would be easier if you gave me the instructions on how to
+ further examine the bug in the command line mode, for instance by ps -A
+ and the kill -9 or kill --nice and see which application is staying
+ active. I could then contact the bug team by typing mail, and sending
+ this info. Or maybe you can write me a shellscript. I will do setuid,
+ chmod and chown as you describe, and then I can report any medium crash,
+ through the command line. My display won't open anymore, but I still
+ have internet connectivity (visible through apt-get update and upgrade).
+ Please give me some problem gathering instructions and a shell script
+ or, some instructions on how to pipe through cat or vim and how to use
+ mail. Then I can certainly report anything you want. One last thing:
+ when I reboot, the command line indicates ufw failed and firestarter
+ failed, but all other applications work, but one. When it reaches br0,
+ it hangs for a minute and says: cannot start network (or something -
+ I'll write it down if it can be useful) because no network checksum.
+ This br0 is a bridge for Virtual Box, that I created personally to get
+ internet connection for my virtual machine. I followed the instructions
+ on the official documentation site punctually. Please ask me as soon as
+ possible, since I update regularly and in time I can no longer
+ reproduce, and then the bug squad says invalid.
+
+ Cheers,
+
+ Thomas
+
Binary package hint: update-manager
Random crash on start-up.
ProblemType: Crash
Architecture: i386
Date: Sun Mar 2 05:24:53 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/update-manager
InterpreterPath: /usr/bin/python2.5
NonfreeKernelModules: fglrx
Package: update-manager 1:0.87.10
PackageArchitecture: all
ProcCmdline: /usr/bin/python2.5 /usr/bin/update-manager
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=en_CA.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/bin/update-manager']
SourcePackage: update-manager
Title: update-manager crashed with RuntimeError in <module>()
Traceback:
Traceback (most recent call last):
File "/usr/bin/update-manager", line 43, in <module>
gtk.init_check()
RuntimeError: could not open display
Uname: Linux 2.6.24-10-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev video
--
update-manager crashed with RuntimeError in <module>()
https://bugs.launchpad.net/bugs/197581
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
