Gutsy / now in Hardy - X only starts in recovery mode

Bug #173901 reported by pablo_g
2
Affects Status Importance Assigned to Milestone
X.Org X server
Invalid
Undecided
Unassigned

Bug Description

If i try to start Gutsy not in recovery mode X never starts, and there is no way to interrupt the process, that does not let you do anything than push the reboot or shutdown button of the CPU. So I always start Gutsy in recovery mode and wathching the kernel until y get the message like " give root password for maintenance " and then i press Control D, and if i do not use control+ alt+backspace I get the same problem than booting not in recovery mode.
I think that way I do is not a good way, but it is the only way i could think to resolve my problem and i really want to use direct rendering, so, if i do not do that, i cannot do a lot of thing like playing some games and use Compiz.
I discovered so many people with the same problem than me, not only in KDE, ( I use KDE ). Anyway I browsed this page and I do not think this bug is duplicated somewhere. If it is, please let me know, or a way i can help to fix it. Thank you.

Revision history for this message
pablo_g (pablogastonbodnar) wrote : Re: Gutsy - X only starts in recovery mode and being forced with tricks

I really dont know if the reason of this was compiz, but the problem appeared after i installed it, or kde or xorg.conf, because now in hardy alpha, i tried to modify xorg.conf and using kde gnome or xfce, and disable glx in xorg.conf. But all tried did not work, i saw other bugs related and did some things like modifying driver nv, for vesa or vga or nvidia. At this time i am really lost about what to do.

Revision history for this message
pablo_g (pablogastonbodnar) wrote :

What i see when is the moment " that does not let you do anything than push the reboot or shutdown button of the CPU " is the shell screen with not other thing than a cursor and nothing you can do with the keyboard to exit, nor ctrl alt backspace, nor ctrl alt delete, etc ... Adittionally now i see a message box in the screen when i enter in recovery mode , if i do not use control alt backspace, telling something like it is not recommended to start as a privileged user, with the options " continue " or " quit ". Both options leave again to the shell with the cursor.

Revision history for this message
pablo_g (pablogastonbodnar) wrote : Re: Gutsy - X only starts in recovery mode and being forced with tricks after modifying /etc/X11/xorg.conf to use glx direct rendering exactly as suggested in Compiz web page for NVidia drivers

I sometimes use ctrl alt F1 and not ctrl alt backspace, to avoid the "cursor", but i do not do that now because i decided to disable kdm.

Revision history for this message
pablo_g (pablogastonbodnar) wrote :

After ctrl alt F1 or ctrl alt backspace, i log in and the y type startx and enter. This is the only way to use Ubuntu for me.

Revision history for this message
pablo_g (pablogastonbodnar) wrote :

This bug i could read searching in Internet is with Gutsy, and now it is the same in Hardy for me. In fact i did not have this problem in Feisty, but i do not want to use Feisty for this only problem i have ... What can i do to help to resolve this bug ? Thank you in advance.

Revision history for this message
pablo_g (pablogastonbodnar) wrote : Re: Gutsy - X only starts in recovery mode

Added as insecure bug to have to start in recovery mode.

Revision history for this message
pablo_g (pablogastonbodnar) wrote :

Fixed erasing vga=792 from /boot/grub/menu.lst. Now in not recovery mode, but still only way to login is typing user and password and then start x. No welcome window available, but i have still message suggesting not starting session as a privileged user. This bug has to be closed. I will report a new bug.

Revision history for this message
pablo_g (pablogastonbodnar) wrote :

Commented last time is with kdm. With gdm everything works ok !

Revision history for this message
pablo_g (pablogastonbodnar) wrote :

In gdm everything is ok, but you have to keep erased vga=792 in menu.lst.

Revision history for this message
pablo_g (pablogastonbodnar) wrote :

In gdm everything is ok with vga=789.

dino99 (9d9)
Changed in xorg-server:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.