gpar2 doesn't start on Feisty

Bug #99751 reported by Vis
2
Affects Status Importance Assigned to Milestone
gpar2 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: gpar2

X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
terminate called after throwing an instance of 'Glib::FileError'
Aborted (core dumped)

Revision history for this message
Bryce Harrington (bryce) wrote :

The X Error: BadDevice errors are probably just from the wacom entries in xorg.conf (see bug 42553).

Please run this through gdm to get a backtrace to determine why it's aborting.

Changed in gpar2:
status: New → Incomplete
Revision history for this message
Gareth Fitzworthington (mapping-gp-deactivatedaccount) wrote :

We are closing this report (no response to request for information). To reopen the report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in gpar2:
status: Incomplete → Invalid
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.