Bug 226

Yes, it's a bit buggy, IIRC there was talk about removing it altogether...

Keywords: (none) => Triaged
CC: (none) => anssi.hannula

And replacing by what? I don't like to write my xorg.conf by hand XD.
I would rather have a tool which is a little bit buggy than have non.
But that's my opinion. Is there a log of this discussion?

He means the "Test" button :)

Ahmad meant removing the "test" option not the whole XFdrake  iirc

CC: (none) => dmorganec

Yes, sorry, my comment could have been clearer.

*** Bug 236 has been marked as a duplicate of this bug. ***

CC: (none) => yleny

No it's very usefull in the summary of the installer.
We could hide it in the standalone tool though.
But I'm not sure it's such a nice idea

CC: (none) => thierry.vignaud

I guess you don't have x11-driver-input installed?
That would mean we should either suggests it or adapt the test config file

is this bug still valid ?

Keywords: Triaged => NEEDINFO

(In reply to comment #9)
> is this bug still valid ?

In mageia 1 installer i586 I still ran into this bug when testing my graphical card + screen settings. Do you want more recent information?

CC: (none) => marja11

What's the output of 'lspcidrake -v|grep Card'?
Also attach (not paste) your whole /etc/X11/xorg.conf as well as your /var/log/Xorg.0.log & Xorg.9.log
Also what's the output of 'rpm -qa x11-driver-*|sort'

@ Fabian

Do you still have this bug? I don't have it, nor in current cauldron, nor in updated Mageia 1, even though I did get the black frozen screen when pushing "test" during install (1x witn 1 rc DVD and 1x with Mageia 1 DVD)

If you still have it, please upload all the attachments Thierry asked for. 

If you don't have it anymore, please tell so this bug can be closed.

It dosn't crash any more. But now  I get a grew screen with the message that the test mode will be left after a few seconds. I can't do anything in this situation. After this time I get back to the normal environment.
Should I close this Bug and open a new Bug or add more details here?

(In reply to comment #13)
> It dosn't crash any more. But now  I get a grew screen with the message that
> the test mode will be left after a few seconds. I can't do anything in this
> situation. After this time I get back to the normal environment.
> Should I close this Bug and open a new Bug or add more details here?

Thanks for replying!

I changed the summary of this bug, so this gets covered by it, too

Please attach the /var/log/Xorg.9.log of the last time you pushed test and got this grey screen.

(I really thought this was a known issue, but I can't find a bug report on this, although someone mentioned it in bug 427)

Summary: Clicking "Test" in XFdrake causes black screen => Clicking "Test" in XFdrake causes grey screen ( was: causes black screen)

Oops

Don't forget the other attachments Thierry asked for!

Created attachment 914 [details]
xorg.conf

Created attachment 915 [details]
Xorg.0.log

XFdrake was started at something with 25XX (Only the last two messages inserted after starting XFdrake)

Created attachment 916 [details]
Xorg.9.log

$ lspcidrake -v|grep Card
Card:NVIDIA GeForce 6100 to GeForce 360: nVidia Corporation|G86 [GeForce 8500 GT] [DISPLAY_VGA] (vendor:10de device:0421 subv:1458 subd:3460) (rev: a1)

$ rpm -qa x11-driver-*|sort
x11-driver-input-evdev-2.6.0-2.mga1
x11-driver-video-nouveau-0.0.16-0.20110303.3.mga1
x11-driver-video-nvidia-current-280.13-1.mga2.nonfree
x11-driver-video-vesa-2.3.0-6.mga1

nouveau crashs on a other way:

With nouveau I don't get a grew screen ans some error messages.
at Xorg.0.log it creates the same two messages but in Xorg.9.log are real errors.

Created attachment 917 [details]
Xorg.9.log_nouveau

Xorg.9.log when I test the nouveau driver.

Ah and when I test something at the next boot X dosn's start.
(Also I don't save changes and also there is no change in xorg.conf.)

Thanks, Fabian, for uploading all the files

@ Assignee
I think this bug was assigned correctly, but please confirm by putting "OK" on the whiteboard or by confirming in a comment

same bug at the install with an intel graphical card

CC: (none) => yves

(In reply to comment #25)
> same bug at the install with an intel graphical card

Mageia 1 freshly installed and up to date.
Apparently this bug is still present (grey screen). But is it a bug ?
It may simply be that a colored test image (like the one in mandriva) is not loaded ?

CC: (none) => garaud

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

I didn't try cauldron either. The bug (not very annoying) is still present in Mageia 1 today.
Yesterday I installed Mageia 2 from the 64bit DVD but I was unable to start X (system hangs). Not very surprising as the DVD is supplied without proprietary graphic drivers. Then I tried a network install with CD + non-free firmware : same result. Finally I tried to install the driver (NVIDIA-Linux-
x86_64-295.53.run) from the NVIDIA site, but I was unsuccessful too
Laptop: Toshiba Qosmio X500 with NVIDIA Geforce GTS 360M.
Of course when I click "Test" in XFdrake I get a black screen, but this is due to the system hanging, a quite different problem.
So I cannot yet answer your question, sorry :(

well it it's still valid on some card

Keywords: NEEDINFO => (none)

Thanks to bugzilla (see https://bugs.mageia.org/show_bug.cgi?id=6128) I succeeded to install the right proprietary driver for a NVIDIA Geforce GTS 360M. Now I can confirm that The bug is still valid for Mageia 2.

*** Bug 6349 has been marked as a duplicate of this bug. ***

CC: (none) => yankee495

http://svnweb.mageia.org/soft/drakx-kbd-mouse-x11/trunk/lib/Xconfig/test.pm?revision=391&view=markup
or in /usr/lib/libDrakX/Xconfig/test.pl

line 116
- my $pixbuf = Gtk2::Gdk::Pixbuf->new_from_file("$::prefix/usr/share/mdk/xfdrake/xfdrake-test-card.png");
+ 116 	my $pixbuf = Gtk2::Gdk::Pixbuf->new_from_file("$::prefix/usr/share/mga/xfdrake/xfdrake-test-card.png");

Keywords: (none) => Junior_job, PATCH

Thx for spotting this.
Fixed in SVN

Status: NEW => RESOLVED
Resolution: (none) => FIXED