3rd crash while being dumb playing solitaire ... seems to be in the drag and drop process. Jumps to a terminal login.

[Ayla]

Binary package hint: software-center

Ubuntu 9.10

Was in QA ... but retired. Just killing time playing solitaire ... This may be solely related to solitaire and not important. During quick play the system crashes and jumps to a terminal login prompt. I'm new to Ubuntu and just feeling my around. This reminds me of the 'dreaded blue screen' of 'Windows' of years gone by.

If anyone has some test scripts they nned some work on ... email me at <email address hidden>. I really was a senior QA analyst and could 'break' a lot of code.

Jim

ProblemType: Bug
Architecture: i386
Date: Thu Feb 4 21:09:14 2010
DistroRelease: Ubuntu 9.10
Package: software-center 1.0.3
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
SourcePackage: software-center
Uname: Linux 2.6.31-17-generic i686
XsessionErrors:
 (gnome-settings-daemon:4026): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:4026): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:4144): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:4122): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (gnome-panel:4119): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -5 and height 24

[Paul Broadhead (pjbroad)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in software-center.
For future reference you might be interested to know that a lot of applications have bug reporting functionality built in to them. This can be accessed via the Report a Problem option in the Help menu for the application with which you are having an issue. You can learn more about this feature at https://wiki.ubuntu.com/ReportingBugs.

[Matthew Paul Thomas (mpt)]

Ayla, please disregard Paul Broadhead's comment. (1) You did indeed report this bug against a package originally, but (2) software-center was not the appropriate package, and (3) you couldn't have used "Help" > "Report a Bug" as he suggested since the whole graphical display had crashed.

When the graphical display does crash, it's usually a problem with the xorg package or with the particular graphics driver you're using, so I'm moving this report to "xorg" to start with. If you can reproduce the problem frequently, as a QA veteran you may be able to chew through our instructions on debugging it. <https://wiki.ubuntu.com/DebuggingXorg> Best of luck, and thanks for helping.

[Paul Broadhead (pjbroad)]

Matthew, my comments are the standard response when trying to help identify a package for a bug where one is not present. The comment is intended more for future bug reporting not just the current bug. Apologies to all if I identified the wrong package, at least my effort got the ball rolling.

[Bryce Harrington (bryce)]

Hi Ayla,

Thanks for including the attached files. Could you also include your /var/log/Xorg.0.log (or Xorg.0.log.old) from after reproducing the issue?

Please attach the output of `lspci -vvnn` too.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.