Unity sometimes stuck right after login on dualscreen

Bug #1042076 reported by Christoph K.
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Unity
Expired
Undecided
Unassigned
unity (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Hi,

there seems to be a really annoyin bug either in unity or compiz or maybe even Xorg (at least i think one of those is to blame).

Sometimes (approximatly 1 out of 10 times) unity gets stuck right after login on my dual screen setup. I've never seen that problem on 2 other systems with only one display! Didn't see that problem on Xfce either.

I can still move around the mouse but i cant click anything. Switching to the terminal and executing "export DISPLAY=localhost:0.0; unity --replace" fixes it for a short time (about 10 secs). In case i'm fast enought to logout in this time and log back in everything seems to work most of the time.

Doesn't look like fglrx is to blame. Even had this problem using the opensource driver.

Anybody else got this problem?

Let me know what you need to debug that. and i'll append it next time it happens.

i'm running 12.04.1 ... no ppa's
the packages i got installed:

libunity-core-5.0-5 5.14.0-0ubuntu1
libunity-misc4 4.0.4-0ubuntu2
libunity9 5.12.0-0ubuntu1.1
unity 5.14.0-0ubuntu1
unity-common 5.14.0-0ubuntu1
unity-services 5.14.0-0ubuntu1

compiz 1:0.9.7.8-0ubuntu1.4
compiz-core 1:0.9.7.8-0ubuntu1.4
compiz-gnome 1:0.9.7.8-0ubuntu1.4
compiz-plugins-default 1:0.9.7.8-0ubuntu1.4
compiz-plugins-main-default 1:0.9.7.0~bzr19-0ubuntu10
compizconfig-backend-gconf 0.9.5.92-0ubuntu5
libcompizconfig0 0.9.7.0~bzr428-0ubuntu6

xorg 1:7.6+12ubuntu1

some xrandr information on my display setup

Screen 0: minimum 320 x 200, current 3600 x 1080, maximum 3600 x 1920
DFP1 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 474mm x 296mm
   1680x1050 59.9*+
...
DFP2 connected 1920x1080+1680+0 (normal left inverted right x axis y axis) 598mm x 336mm
   1920x1080 60.0*+
...
CRT1 disconnected (normal left inverted right x axis y axis)
CRT2 disconnected (normal left inverted right x axis y axis)
TV disconnected (normal left inverted right x axis y axis)
CV disconnected (normal left inverted right x axis y axis)

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Christoph,

If unity (compiz) is actually stuck then a stack trace will help us to confirm and find out why.

Please:
1. Download the attached script to your home directory.
2. Keep logging out/in until you reproduce the bug again.
3. Switch to a virtual terminal (Ctrl+Alt+F1) and log in.
4. Run:
    sh ./dstack compiz >> compizstuck.txt
5. Repeat #4 a few times.
6. Run:
    sudo restart lightdm
7. Log in normally and attach the file compizstuck.txt to this bug.

Changed in unity (Ubuntu):
status: New → Incomplete
Revision history for this message
Christoph K. (christoph-k-deactivatedaccount-deactivatedaccount) wrote :
Revision history for this message
Christoph K. (christoph-k-deactivatedaccount-deactivatedaccount) wrote :

hope that'll help.

i noticed i sometimes can even click on the unity menu on the left side... i couldn't figure out when that happens.

Revision history for this message
Omer Akram (om26er) wrote :

can you install debug symbols for unity, nux and compiz and then create the crash? from the attached stacktrace looks like fglrx bug ?

Changed in unity:
status: New → Incomplete
Revision history for this message
Christoph K. (christoph-k-deactivatedaccount-deactivatedaccount) wrote :

Omer,

can you tell me how to install the debug symbols?
I couldn't find any packages refering to them.

Revision history for this message
Christoph K. (christoph-k-deactivatedaccount-deactivatedaccount) wrote :

found it
https://wiki.ubuntu.com/DebuggingProgramCrash

i just installed

compiz-core-dbgsym
compiz-gnome-dbgsym
unity-dbgsym
xserver-xorg-dbgsym

tryin to reproduce it now

Revision history for this message
Omer Akram (om26er) wrote :

sudo apt-get install unity-dbgsym unity-services-dbgsym libunity-core-6.0-5-dbgsym nux-tools-dbgsym libnux-3.0-0-dbgsym compiz-core-dbgsym libdecoration0-dbgsym

above command should install all the required.

Revision history for this message
Christoph K. (christoph-k-deactivatedaccount-deactivatedaccount) wrote :

logged in about 30 times with the debug symbols installed... didn't happen so far. will keep them installed and get back to this as soon as it happens again.

to me the system with installed debugsymbols feels a bit sluggish... is it just me hallucinating or does it really slow down with installed debugsymbols? in case it really gets slowed down it could also be some weird race condition on loggin i guess.

Revision history for this message
Christoph K. (christoph-k-deactivatedaccount-deactivatedaccount) wrote :

ok now it happened twice in row!

got some more debuginformation for you

compizstuck2.txt was exactly the same problem as before (except for included debug symbols this time)

compizstuck3.txt was slightly different... it started working for a short period again while creating those stacktraces and then suddenly stopped working again

Revision history for this message
Christoph K. (christoph-k-deactivatedaccount-deactivatedaccount) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for unity (Ubuntu) because there has been no activity for 60 days.]

Changed in unity (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Unity because there has been no activity for 60 days.]

Changed in unity:
status: Incomplete → Expired
Revision history for this message
Christoph K. (christoph-k-deactivatedaccount-deactivatedaccount) wrote :

Think i narrowed that issue down quite a bit.

1. It's not an dual-screen issue! Got the same behaviour after unplugging one of them several times.
2. It seems to be related to my inputdevices (Logitech K120 Keyboard,Logitech G400 Mouse) and/or my USB-Headset! (Creative HS-950).

Last 2 times it happened i unplugged the headset and suddenly everything worked just fine again (no logout / restart required).

Revision history for this message
Christoph K. (christoph-k-deactivatedaccount-deactivatedaccount) wrote :
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.