Mailinglist Archive: opensuse-bugs (10057 mails)

< Previous Next >
[Bug 552492] New: X server locks when the kernel is of xen flavour
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Wed, 4 Nov 2009 06:16:28 -0700
  • Message-id: <bug-552492-21960@xxxxxxxxxxxxxxxxxxxxxxxx/>
http://bugzilla.novell.com/show_bug.cgi?id=552492


Summary: X server locks when the kernel is of xen flavour
Classification: openSUSE
Product: openSUSE 11.2
Version: RC 2
Platform: x86-64
OS/Version: openSUSE 11.2
Status: NEW
Severity: Major
Priority: P5 - None
Component: Xen
AssignedTo: jdouglas@xxxxxxxxxx
ReportedBy: jp.pozzi@xxxxxxxxx
QAContact: qa@xxxxxxx
Found By: ---


Created an attachment (id=325501)
--> (http://bugzilla.novell.com/attachment.cgi?id=325501)
Files from /var/log/gdm in tar format

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4)
Gecko/20091028 Iceweasel/3.5.4 (Debian-3.5.4-1)

Hello,

I try the opensuse 11.2 rc2 and I get a problem using XEN :
The Xserver does not work when launched with the xen kernel.

All is OK when I start with other kernels (desktop or failsafe) where X is
working perfectly.



Reproducible: Always

Steps to Reproduce:
1. use the XEN kernel
2. try to use X
3. it's done
Actual Results:
I have done no specific changes from the installation (out of the box).
When started nothing can be done, the keyboard does not allow to switch to
another tty (Ctrl+Alt+F1 does nothing).
I can connect to the system through ssh from another system and even when i
stop and restart the "xdm" service the screen stay the same as if nothing was
done.
The problem seems to be with "gdm", but the same result was obtained with
"kdm".




Some lines from /var/log/warn :
Nov 4 14:03:14 amdx2-2 gdm-simple-greeter[2393]: GLib-GObject-CRITICAL:
g_param_spec_flags: assertion `G_TYPE_IS_FLAGS (flags_type)' failed
Nov 4 14:03:14 amdx2-2 gdm-simple-greeter[2393]: GLib-GObject-CRITICAL:
g_object_class_install_property: assertion `G_IS_PARAM_SPEC (pspec)' failed
===================================================
File : /var/log/gdm/:0-slave.log.1 :
Could not initialise connection to hald.
Normally this means the HAL daemon (hald) is not running or not ready.
Could not initialise connection to hald.
Normally this means the HAL daemon (hald) is not running or not ready.
=========================================================================
but hal seems to be running :
ps -ef | grep hal
104 1498 1 0 14:03 ? 00:00:00 /usr/sbin/hald --daemon=yes
root 1506 1498 0 14:03 ? 00:00:00 hald-runner
root 1595 1506 0 14:03 ? 00:00:00 hald-addon-input: Listening on
/dev/input/event1 /dev/input/event3 /dev/input/event2
root 1626 1506 0 14:03 ? 00:00:00 hald-addon-storage: polling
/dev/sr0 (every 16 sec)
104 1628 1506 0 14:03 ? 00:00:00 hald-addon-acpi: listening on
acpid socket /var/run/acpid.socket
root 3896 3836 0 14:10 pts/0 00:00:00 grep hal

--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >