Suddenly unable to use keyboard and use menu's in application+

Bug #127015 reported by A Z
2
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Brian Murray

Bug Description

Using default ubuntu Feisty 7.04

What happens:
Keyboard does not respond to any keypress.
Mouse cursor can be moved, can left click, not left click, cannot click menu's of any kind anymore, ie: the menu does not appear.
I had the luck to have a shortcut to System Monitor, so I blatantly started killing processes (there wasn't a single process using up CPU/RAM).
After killing dbus-daemon, the whole gnome desktop disappeared, and gdm restarted.
I've had this situation occuring for a couple of times now, it is quite annoying.
I'll be very happy to share information you might want, I've checked several error logs, but I couldn't find anything abnormal myself there.

Revision history for this message
Pascal De Vuyst (pascal-devuyst) wrote :

Thanks for your bug report, more information is needed.

What brand and model is your keyboard and mouse?
How is your keyboard and mouse connected to your PC: PS/2, USB, USB wireless (Bluetooth), ...
For a USB keyboard or mouse include the output of the command lsusb on a terminal.
What mechanism does your mouse use: ball mouse, optical, trackball, ...
How many physical buttons and scrollwheels does you mouse have?

Try the following:
1. Direct after gnome login open a terminal and enter the following command:
  $ cp /var/log/Xorg.0.log ~/Xorg.0.log
  $ cp /var/log/dmesg ~/dmesg_boot
2. Wait until your mouse and keyboard stop working.
3. Open a terminal by pressing Ctrl-Alt-F1.
4. Enter the following commands:
  $ LANG=C
  $ cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
  $ diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff-ns
  $ dmesg > ~/dmesg
  $ diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff-ns
5. Attach Xorg.0.log, Xorg.0.log_diff-ns, dmesg_boot and dmesg_diff-ns to this bug report.

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

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and feel free to submit bug reports in the future.

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.