Cannot click on anything when logging into Gnome the first time

Bug #517794 reported by Reuben Firmin
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libbonobo (Ubuntu)
Expired
Low
Unassigned

Bug Description

Binary package hint: gnome-session

After booting my computer, when first logging into Gnome, nothing reponds to left or right click events. The GDM login screen _does_ respond to the mouse, so it's only once I'm logged in that the bug happens. The cursor is visible onscreen and moves around.

When I restart X (ctrl alt backspace) and re-login, the mouse works normally.

Revision history for this message
Andreas Noteng (andreas-noteng) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we can't fix it because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures

Could you please provide the following logs:
/var/log/messages
/var/log/Xorg.0.log
the output of lspci and lsusb might also be useful.

Also, you need to state which release you are using, and if possible; try and recreate the bug in the latest development release.

Thanks!

Revision history for this message
Pedro Villavicencio (pedro) wrote :

remember to set the status to Incomplete when you're asking something, thanks.

Changed in gnome-session (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Reuben Firmin (reubenf) wrote :
Download full text (3.6 KiB)

This happened again, and I was able to get some info from a different TTY.

Here's the relevant part from /var/log/messages - compiz crashes.

Feb 24 13:17:06 fridge kernel: [349959.691938] compiz.real[22928]: segfault at 5 ip 08055c3c sp bfc0a410 error 4 in compiz.real[8048000+34000]

This bug is actually intermittent - it does not always happen on first login after all. Zapping X sometimes causes it; first login sometimes works fine. Last time that this happened, ctrl alt bksp was not enough to recover from it; I had to completely reboot the machine. I didn't capture Xorg.log from that startup, but my current one is attached.

lsusb:

Bus 002 Device 004: ID 0a12:1004 Cambridge Silicon Radio, Ltd
Bus 002 Device 002: ID 04f2:0402 Chicony Electronics Co., Ltd
Bus 002 Device 003: ID 0e9c:0000 Streamzap, Inc. Streamzap Remote Control
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 007: ID 046d:c408 Logitech, Inc. Marble Mouse (4-button)
Bus 001 Device 002: ID 058f:6254 Alcor Micro Corp. USB Hub
Bus 001 Device 004: ID 05e3:0716 Genesys Logic, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

lspci:

00:00.0 Host bridge: nVidia Corporation C55 Host Bridge (rev a2)
00:00.1 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:00.2 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:00.3 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:00.4 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:00.5 RAM memory: nVidia Corporation C55 Memory Controller (rev a2)
00:00.6 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:00.7 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:01.0 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:01.1 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:01.2 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:01.3 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:01.4 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:01.5 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:01.6 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:02.0 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:02.1 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:02.2 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:03.0 PCI bridge: nVidia Corporation C55 PCI Express bridge (rev a1)
00:07.0 PCI bridge: nVidia Corporation C55 PCI Express bridge (rev a1)
00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2)
00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a3)
00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a3)
00:0a.2 RAM memory: nVidia Corporation MCP51 Memory Controller 0 (rev a3)
00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1)
00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1)
00:0f.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1)
00:10.0 PCI ...

Read more...

Revision history for this message
Reuben Firmin (reubenf) wrote :
Revision history for this message
Reuben Firmin (reubenf) wrote :

Ah, I grabbed the wrong thing from /var/log/messages. I zapped X again and hit the problem. This time, there was no message about compiz crashing; instead the only message was:

Feb 24 15:18:30 fridge bonobo-activation-server (reubenf-9075): could not associate with desktop session: Failed to connect to socket /tmp/dbus-21KoScej9t: Connection refused

So I looked back to the earlier occasion on which I got stuck, and sure enough:

Feb 24 13:17:42 fridge bonobo-activation-server (reubenf-23344): could not associate with desktop session: Failed to connect to socket /tmp/dbus-bSazBlS28S: Connection refused

So, this seems to be the cause. FWIW this time I was able to zap X a couple of times and get a session that is responsive; I wonder if I couldn't earlier because of the dead compiz on top of the bonobo issue.

Xorg from bonobo-detached X attached.

Revision history for this message
Reuben Firmin (reubenf) wrote :
Revision history for this message
Andreas Noteng (andreas-noteng) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:

apport-collect 517794

This will help us to find and resolve the problem. Bear in mind that you may need to install the python-launchpadlib package from the universe repository. Additionally, when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to "Change Non-Private" data as it will be adding information to your bug report. Thanks in advance!

affects: gnome-session (Ubuntu) → libbonobo (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in libbonobo (Ubuntu):
status: Incomplete → Expired
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.