nautilus freezes when locking out and in again

Bug #153180 reported by Kai Wüstermann
4
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

Tuning my /etc/X11/xorg.conf locked out and in for serveral times. After two or three lockins Nautilus was freezed with 90%-CPU. I did not use nautilus at the sessions.

A killall nautlilus solves the problem.

There is a bug report #84737 Nautilus freezes on secondary monitor. I am working on the secondary monitor on a Radeon RV250 [Mobility FireGL 9000] (rev 01).

Revision history for this message
Basilio Kublik (sourcercito) wrote :

Hi Kai
what do you mean with lock out/in the file, are you changing the file permissions?
please describe the steps to reproduce this bug, in much details as you can.

Thanks in advance

Revision history for this message
Kai Wüstermann (k-wuestermann) wrote :

Moin Basilio,

I locked out of gnome several times, so that the Xserver had to restart and I had to type my name and password.

I just tried to reproduce this behavior locking out and in again 10 times, but now it's alright. I also tried to restart the Xserver by pressing Alt+Ctrl+Del. I also can't reproduce the problem.

May be, that this is a problem of the X driver. Now I'm using "ati". Yesterday I tried "radeon", "vesa" and "fglrx" too. But I can't remember what driver was loaded, when the problem appeared.

The problem I tried to solve was: If the resolution of the secondary monitor is better than the laptop display the panels appear in the area left on the top which is equal to the smaller display. The panel on the top can't be expanded to the whole width of the secondary monitor.

With help of the ubuntuusers.de I solved this problem by switching off the laptop display using xrandr.

I hope this description helps to get ubuntu better. If the problem comes again, I will try to describe the thinks I will done before.

Kai

Revision history for this message
Basilio Kublik (sourcercito) wrote :

Hi Kai
Thanks for the explanation, i wasn't able to reproduce this bug either, i'm closing this report as invalid for now, if you ever experience this issue again, please re-open the report so we can work on it. Thanks again for taking the time to inform this issue, feel free to report any future bugs you might find.

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.