|
Bugzilla – Full Text Bug Listing |
| Summary: | [opensuse][XEN]In XEN you can login to x but it doesn't come up | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Stephen Shaw <stshaw> |
| Component: | X.Org | Assignee: | Stefan Dirsch <sndirsch> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Jason Douglas <jdouglas> |
| Severity: | Blocker | ||
| Priority: | P5 - None | ||
| Version: | Beta 2 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Stephen Shaw
2007-08-25 07:10:01 UTC
don't know if this has anything to do with it... Aug 25 01:03:24 beta2 gdm[3836]: GLib-CRITICAL: g_key_file_get_string: assertion `key_file != NULL' failed Aug 25 01:03:24 beta2 gdm[3836]: GLib-CRITICAL: g_key_file_get_string: assertion `key_file != NULL' failed Aug 25 01:03:24 beta2 gdm[3836]: GLib-CRITICAL: g_key_file_free: assertion `key_file != NULL' failed /etc/X11/xorg.conf and /var/log/Xorg.0.log, please. Same problem without a Xen kernel? no. It seems to work just fine without XEN. Not sure what's going on. This worked just fine in beta 1. You might not be that lucky to get log files on this one. I have a really hard time trying to get to a console before it completely locks up the computer. Sorry don't have a second one or laptop at home to try and connect with. boot into runlevel 3 to prevent X from starting. This isn't when X is booting, its when I'm trying to log into gnome. After I hit enter on my password, it changes to a grey screen and shows X using a 100% cpu. This happened on my home computer, however I haven't been able to dup this in my lab here at work. I'm going to reinstall beta2 at home to see if this was a strange one off problem. Just some wild guess. Did you enabel Xgl? Stephen, still alive? If you think it's a blocker it also needs to be handled urgently from your side ... Sorry, I'm been trapped between a couple things, I'll try and reproduce it today, if not, then I'll move it done and/or mark it invalid. Thanks. But why do you change the status? I haven't been able to reproduce it in my lab, I was almost thinking that this was a bad install or something. Anyways, this bug sounds very similar bug #300496 There is a log file in there too, so maybe that one will have some insight to the problem as well. > Anyways, this bug sounds very similar bug #300496 indeed. *** This bug has been marked as a duplicate of bug 300496 *** |