Bug 132501

Summary:	Failed to load module "ChangeMe" after VNC installation
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Christian Boltz <suse-beta>
Component:	Installation	Assignee:	Marcus Schaefer <ms>
Status:	RESOLVED DUPLICATE	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Normal
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	y2logs Xorg.0.log xorg.conf (after installation)

Description Christian Boltz 2005-11-06 20:23:34 UTC

After installing a machine over VNC, X doesn't work. I did a fresh installation (no update).

rckdm start shows "OK", rckdm status shows "running" - but X is not running.

After checking the Xorg.0.log, I found the reason:
---
(II) LoadModule: "ChangeMe"
(WW) Warning, couldn't open module ChangeMe
(II) UnloadModule: "ChangeMe"
(EE) Failed to load module "ChangeMe" (module does not exist, 0)
[...]
(EE) No drivers available.

Fatal server error:
no screens found
---

The "ChangeMe" is also contained in xorg.conf:

Section "Device"
  Driver        "ChangeMe"
  Identifier    "Device[0]"
  # device_options
  Option        "sw_cursor" "on"
EndSection


Please note that this bugreport covers two problems:
- a broken entry in xorg.conf after installation
- an error in the start script which detects X as running

Comment 1 Christian Boltz 2005-11-06 20:28:24 UTC

Created attachment 56560 [details]
y2logs

Comment 2 Christian Boltz 2005-11-06 20:29:38 UTC

Created attachment 56561 [details]
Xorg.0.log

Comment 3 Christian Boltz 2005-11-06 20:30:41 UTC

Created attachment 56562 [details]
xorg.conf (after installation)

Comment 4 Marcus Schaefer 2005-11-10 11:55:59 UTC

If you did a remote installation via VNC there will be no real X
configuration created because you are remote. If you now change your
side from remote to local you first have to create a X configuration
manually. This is an intended behavior.

simply call:

  sax2

configure your system and save the configuration. After this everything
should work as local X session as well. You should have in mind if you
do a remote installation no local X service will be configured only the
default framebuffer based X config is copied from the first CD to the
installed system.

Comment 5 Christian Boltz 2005-11-21 23:28:48 UTC

I know that I can call sax2 manually. If this is intended behaviour after a VNC installation, it's OK for me.

But:
- the second problem remains (rckdm start reports "done" while no X-Server is 
  running) - this is the reason for reopening this bug (or should I open a new 
  one? Just tell me.)
- your "intended bahaviour" should be worth a note somewhere after 
  installation ;-)

Comment 6 Marcus Schaefer 2005-11-22 11:37:30 UTC

Hmm, I think for a VNC installation the default runlevel could be
set to 3 because there is no real X-Session available. This could be
seen as a "fix". I think you can open a new bug with topic:

  default runlevel for VNC installation should be set to 3

well I'm not responsible for the default runlevel so maybe yast2-maintainers
could be a starting point here but this one I will close as worksforme :)

Comment 7 Christian Boltz 2005-11-27 12:56:29 UTC

> I think you can open a new bug with topic:
>  default runlevel for VNC installation should be set to 3

done (#135605)

There's still the issue with rckdm status showing "running" while the X-Server does *not* run. Shall I also open a bug for this?

Comment 8 Marcus Schaefer 2005-11-28 09:24:24 UTC


*** This bug has been marked as a duplicate of 135605 ***