system crashes on preferences>screensaver

Bug #181456 reported by ftaylor
6
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

I have ubuntu gutsy 7.10 32 bit. I have dell inspiron 6400 laptop with intel 1.7ghz duo core 2 processor, 2gig ddr ram and a radeon mobility x1400 256mb graphics card.

I am running compiz fusion. I am using the xserver-xgl restricted driver, xserver-xorg whatever it is.

Every time I go to preferences - screensaver it seems to restart X. System crashes and x restarts. This stopped a few days ago when I downloaded some updates. I just updated again just now and the crashing has started again.

The actual screensaver doesn't display either. It displayed the last few days, after a recent update, prompting me to open the preferences. Now that I have updated again the crashing has resumed.

Please let me know if there is any further information required. I'm very new to ubuntu and this is the first time I have reported a bug.

<email address hidden>

Revision history for this message
Matthew Woerly (nattgew) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.

Revision history for this message
ftaylor (ftaylor) wrote : Re: [Bug 181456] Re: system crashes on preferences>screensaver

It actually seems to have cleared up to a certain extent.

The screen still always goes black rather than the screensaver, and when I
move the mouse the screensaver comes on. preferences>screensaver no longer
crashes though.

Cheers

> Thanks for taking the time to report this bug and helping to make Ubuntu
> better. You reported this bug a while ago and there hasn't been any
> activity in it recently. We were wondering is this still an issue for
> you? Thanks in advance.
>
> ** Changed in: ubuntu
> Status: New => Incomplete
>
> --
> system crashes on preferences>screensaver
> https://bugs.launchpad.net/bugs/181456
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Matthew Woerly (nattgew) wrote :

Check the settings for Power Management, too. It sounds like the display is being put to sleep, but a keyboard or mouse event only wakes the display, and the screensaver is still there.

Revision history for this message
ftaylor (ftaylor) wrote :

Yes, I had suspected that this was the case. However, upon playing around
with it some more, the bug still exists. It's like when I go to
system>preferences>screensaver it just restarts X. It only does it
sometimes. Maybe it's after the screensaver has taken the screen and then
you go back to your Desktop. It's not that big a deal really.

Finbarr

> Check the settings for Power Management, too. It sounds like the
> display is being put to sleep, but a keyboard or mouse event only wakes
> the display, and the screensaver is still there.
>
> --
> system crashes on preferences>screensaver
> https://bugs.launchpad.net/bugs/181456
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
ftaylor (ftaylor) wrote :

Yes, I had suspected that this was the case. However, upon playing around
with it some more, the bug still exists. It's like when I go to
system>preferences>screensaver it just restarts X. It only does it
sometimes. Maybe it's after the screensaver has taken the screen and then
you go back to your Desktop. It's not that big a deal really.

Finbarr

> Thanks for taking the time to report this bug and helping to make Ubuntu
> better. You reported this bug a while ago and there hasn't been any
> activity in it recently. We were wondering is this still an issue for
> you? Thanks in advance.
>
> ** Changed in: ubuntu
> Status: New => Incomplete
>
> --
> system crashes on preferences>screensaver
> https://bugs.launchpad.net/bugs/181456
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Jayson Rowe (jayson.rowe) 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!

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.