kdesu kate /etc/fstab - generates a lot of error messages

Bug #67253 reported by Henrik R. on 2006-10-20
4
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Undecided
Unassigned

Bug Description

In order to exchange data between my new Kubuntu 6.06.1 and my old Windows 2000 system I needed the above command, which I executed from the Konsole (Terminal program).
I did achieve to insert the needed line in /etc/fstab, but the command generated a large list of errors, which are included below.
After restarting Linux I did the command again, and saved the list of errors again. This time it was shorter. Also included below:

First trail:

henrik@henrik-desktop:~$ kdesu kate /etc/fstab
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode: 146
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode: 146
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode: 146
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode: 146
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
Link points to "/tmp/ksocket-root"
Link points to "/tmp/kde-root"
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode: 146
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode: 146
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
kbuildsycoca running...
Reusing existing ksycoca
kio (KSycoca): ERROR: No database available!
ScimInputContextPlugin()
QObject::connect: No such signal KListView::doubleclicked(QListViewItem*)
QObject::connect: (sender name: 'unnamed')
QObject::connect: (receiver name: 'KateSaveModifiedDialog')
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode: 146
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode: 146
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
ScimInputContextPlugin()
QObject::disconnect: Unexpected null parameter
invalid length 24902
Failed to process 45 bytes from server
invalid length 24902
invalid length 24902
invalid length 24902
~ScimInputContextPlugin()
henrik@henrik-desktop:~$

Second trail:

For some strange reason the first line disappeared at the top of the Konsole (Terminal program)-window:
henrik@henrik-desktop:~$ kdesu kate /etc/fstab

X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode: 146
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode: 146
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode: 146
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode: 146
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
Link points to "/tmp/ksocket-root"
Link points to "/tmp/kde-root"
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode: 146
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode: 146
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
kbuildsycoca running...
ScimInputContextPlugin()
QObject::disconnect: Unexpected null parameter
~ScimInputContextPlugin()
henrik@henrik-desktop:~$

towsonu2003 (towsonu2003) wrote :

are you using the "composite" extension for X? (if you don't know, you can just attach your /etc/X11/xorg.conf here as a file. thanks

Henrik R. (henrik-roseno) wrote :

I think I have just uploaded the file you requested (/etc/X11/xorg.conf) although I can't see it here.

towsonu2003 (towsonu2003) wrote :

nope, I can't see it either :) can you try again? thanks

(PS. don't forget to check the box besides "Include Attachment" option below the comment area.)

Henrik R. (henrik-roseno) wrote :
towsonu2003 (towsonu2003) wrote :

not using Composite (those errors were very similar to some errors I got when using the "composite" extension and tried to start some programs). assigning to xorg due to X errors.

Up to "Failed to open device" this is a duplicate of bug #42553.
The workaround is to comment out in /etc/X11/xorg.conf:

        InputDevice "stylus" "SendCoreEvents"
        InputDevice "cursor" "SendCoreEvents"
        InputDevice "eraser" "SendCoreEvents"

As for the other messages, I am not sure at all. They may be a duplicate of bug #53845. Or they may be not.

I think that the best approach to no confuse everybody would be to close this bug as a duplicate of bug #42553.

Then, if you get any errors that are not equal to those reported in bug #53845, please open a new bug report.

Thanks in advance.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers