Bug 138664 - Plugged Wacom tablet makes Xorg not start
Plugged Wacom tablet makes Xorg not start
Product: Fedora
Classification: Fedora
Component: xorg-x11 (Show other bugs)
athlon Linux
medium Severity medium
: ---
: ---
Assigned To: X/OpenGL Maintenance List
David Lawrence
Depends On: 138658
  Show dependency treegraph
Reported: 2004-11-10 11:02 EST by Runar Ingebrigtsen
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-04-11 15:23:19 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Runar Ingebrigtsen 2004-11-10 11:02:52 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Gecko/20040922 Epiphany/1.2.7

Description of problem:
If I plug the Wacom (USB) tablet after having logged in, it works

If I plug the Wacom (USB) tablet before X starts, X refuses to start
and I end up with a blank screen. No input seems to get me back to

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Boot runlevel 3.
2. Plug in Wacom tablet.
3. Change runlevel to 5.

Actual Results:  Screen blanks and no input seems to cause any impact.

I can log in over SSH, though.

Expected Results:  X should start and I should be able to log in.

Additional info:
Comment 1 Kristian Høgsberg 2004-11-10 12:28:53 EST
Could you please post you the /etc/X11/xorg.conf and the
/var/log/Xorg.0.log files.  Also, did you install the linuxwacom
package and did you edit the xorg.conf file in any way? Thanks.
Comment 2 Mike A. Harris 2004-11-10 15:30:12 EST
Setting bug status to "NEEDINFO", awaiting file attachments and
comment update from initial reporter.
Comment 3 Mike A. Harris 2005-04-11 15:23:19 EDT
Closing bug "NOTABUG" due to lack of response to above request for
more information.

Note You need to log in before you can comment on or make changes to this bug.