Ubuntu
xorg-server package

Unable to find screen.

Bug #58300 reported by Curt
2
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Invalid
Undecided
Brian Murray

Bug Description

Binary package hint: xserver-xorg-core

After the most previous xserver-xorg-core I was unable to load the xserver. All config and drivers were ok and the same prior to the update, however, I was receiving the error that "Unable to find screen." All attempts to correct the issue as proposed in the forums were to no avail.

A full reinstall of X did not correct the issue. To correct the issue, I was required to completely reinstall Ubuntu. All is well after doing so.

Revision history for this message
Cristóbal M. Palmer (cristobalpalmer) wrote :

Do you have the version number and/or any error messages from when you were unable to load X? If so, could you please provide them?

Changed in xorg-server:
status: Unconfirmed → Needs Info
Revision history for this message
Curt (mokshadaya) wrote : Re: [Bug 58300] Re: Unable to find screen.

Hi Cristobal.

xserver-xorg-core 1:1.0.2 (I believe this was the most recent update.)
ATI Technologies Inc Radeon Mobility M6 LY driver
Ubuntu Dapper w/2.6.15.24 Kernel

Upon the start of X I got the error "Unable to find screen." Going
through the configuration of X was flawless and without errors, however,
upon typing startx..... I would receive the same error. I reloaded the
ATI driver. Still the same error. I reloaded the xserver-xorg-core
update. Still the same error. I also completely reinstalled X. Still
the same error.

I also then booted up the live CD of Ubuntu Dapper and compared the X
files used by the CD with the ones already loaded on my system. I
couldn't find anything that was an issue.

I then went through a complete reinstall of Ubuntu Dapper and downloaded
the same update which caused the issue with the hopes of replicating the
issue and acquiring more data. After a reboot X loaded normally with no
issues. I assumed at that point that it was a glitched install of the
update that pooched something else in the system that I didn't have the
patience to locate. Quite an oddity.

Unfortunately, I didn't copy or save the log files prior to reloading
the OS.

I'm not sure if anyone else is having this issue, but I felt that I
should communicate it in case they are. Thanks for your time.

Cristobal M. Palmer wrote:
> Do you have the version number and/or any error messages from when you
> were unable to load X? If so, could you please provide them?
>
> ** Changed in: xorg-server (Ubuntu)
> Status: Unconfirmed => Needs Info
>
>

Revision history for this message
Brian Murray (brian-murray) wrote :

I am closing this because you didn't have any log files to help us track down the issue and no one else seems to have reported the issue either.

Changed in xorg-server:
assignee: nobody → brian-murray
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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