Kubuntu 7.04: "DRIScreenInit failed", crashed in xf86SetCursor

Bug #124715 reported by Schmirrwurst
2
Affects Status Importance Assigned to Milestone
xserver-xorg-video-savage (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: kdm

When I logout from kde normally over the gui, the xsession is crashing, and the system is staying on the command line frontend, and is not starting kdm anymore...

Revision history for this message
Schmirrwurst (schmirrwurst) wrote :
Revision history for this message
Schmirrwurst (schmirrwurst) wrote :
Revision history for this message
Marco Maini (maini10) wrote :

Thanks for your report. Which version of Kubuntu are you using? Please attach the file xsession-errors, because this may be an X crash. Thanks.

Changed in kdebase:
assignee: nobody → maini10
status: New → Incomplete
Revision history for this message
Schmirrwurst (schmirrwurst) wrote :

I could not find any xsession-errors file on my system ! Where is it ?

Revision history for this message
Schmirrwurst (schmirrwurst) wrote :

Ok I found some .xsession-errors files but it seems that from the moment I disconnect to the crash, the Xserver isn't writing any log on that file (I tried to move the old one before disconnecting, and I remains empty after crash).
Anyway, here my .xsession-errors file

Revision history for this message
Schmirrwurst (schmirrwurst) wrote :

I use Kubuntu Feisty, which is up to date ...

Revision history for this message
Schmirrwurst (schmirrwurst) wrote :
Revision history for this message
Schmirrwurst (schmirrwurst) wrote :
Revision history for this message
Marco Maini (maini10) wrote :

Thanks for your collaboration. Could you please attach /var/log/Xorg.0.log file?
Please make a test. Try to log in when command line appears and give command startx. Post the results.
Thanks again.

Revision history for this message
Marco Maini (maini10) wrote :

I forgot in the previous comment, please attach the output of command lspci -n to know information about your hardware. Thanks.

Revision history for this message
Schmirrwurst (schmirrwurst) wrote : Re: kdm crashed after kde logout in Kubuntu 7.04
Revision history for this message
Schmirrwurst (schmirrwurst) wrote :
Revision history for this message
Schmirrwurst (schmirrwurst) wrote :
Revision history for this message
Marco Maini (maini10) wrote :

I think this report has sufficient information to be confirmed. However, in my opinion this bug doesn't affect kdebase but is related with Xorg and Savage driver. A similar problem seems to be reported in Debian and a patch should be developed for that.

Changed in kdebase:
assignee: maini10 → nobody
status: Incomplete → Confirmed
Revision history for this message
Marco Maini (maini10) wrote :

Reference to Debian bug (sorry but I don't find the correct upstream project):
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=407199

Revision history for this message
Schmirrwurst (schmirrwurst) wrote : Re: Kubuntu 7.04: Error SAVAGE(0): [drm] DRIScreenInit failed.

After your answer, I tried to change the driver from savage to vesa, and it is working... So you are right, it is a xorg issue, but a big one !
I think this bug has to be marked as important !?

A new user of ubuntu, that is coming on the command-line each time he want to disconnect, will probabably give up really quickly and go back to windobe ...

Revision history for this message
Schmirrwurst (schmirrwurst) wrote :

What is suprising, is that I had no problem installing Ubuntu Feisty, I could disconnect without problem...
It's only after I reinstall, and this time with KUBUNTU, that I get this problem...

Do gnome better manage drm errors ? Or is the ubuntu installation cd, using vesa, whereas kubuntu install the savage driver ??

Revision history for this message
Tormod Volden (tormodvolden) wrote :

This sounds like an old bug that has been fixed in the newer -savage driver. Can you please test in Gutsy or Hardy?

Changed in xserver-xorg-driver-savage:
assignee: nobody → tormodvolden
status: Confirmed → Incomplete
Revision history for this message
Tormod Volden (tormodvolden) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in xserver-xorg-video-savage:
assignee: tormodvolden → nobody
status: Incomplete → 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.