Editing Fstab

[barryp3uk]

Hi I type

sudo kate /etc/fstab

& I get

X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode:  144
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode:  144
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

kdeinit: Can't connect to the X Server.
kdeinit: Might not terminate at end of session.
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

kded: cannot connect to X server :0.0
kded: ERROR: KUniqueApplication: Registering failed!
kded: ERROR: Communication problem with kded, it probably crashed.
ScimInputContextPlugin()
QObject::disconnect: Unexpected null parameter
~ScimInputContextPlugin()

What does all this mean?

Thanks, Barry.

[sky]

Re: Editing Fstab

It's because you should use kdesu kate and not sudo... sudo is for text mode I guess...

Cheers

[barryp3uk]

Re: Editing Fstab

Hi

Thanks for a quick response!

I just did a clean install of Dapper Kubuntu after being in Ubuntu Breezy for a while. What is the difference between sudo & kdesu? I've read about it but I'm not clear.

When I try

kdesu kate /etc/fstab

I get

X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode:  144
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode:  144
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode:  144
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode:  144
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode:  144
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode:  144
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
kbuildsycoca running...
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()

Looks quite similar.

Cheers!

Barry.

[sky]

Re: Editing Fstab

You're right, really strange, I don't get it...
Are you under kde ?

[barryp3uk]

Re: Editing Fstab

Yes

I did a new install (format of slave drive etc) of 6.06 which is running KDE 3.5.2 I think.

[jbernardo]

Re: Editing Fstab

On other distros, you'd have to do a "xhost +127.0.0.1" before any other user on your machine could access the x server. No idea if that is needed in kubuntu (I'm away from my machine right now).

[barryp3uk]

Re: Editing Fstab

That's over my head, mate.

I read

http://kubuntuforums.net/forums/index.php?topic=5772.0

& hashed out all references to wacom tablets. No change but I'll reboot to be sure.

[barryp3uk]

Re: Editing Fstab

OK

Now, if I sudo kate I get

Link points to "/tmp/ksocket-root"
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

kdeinit: Can't connect to the X Server.
kdeinit: Might not terminate at end of session.
Link points to "/tmp/kde-root"
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

kded: cannot connect to X server :0.0
DCOP aborting call from 'anonymous-5077' to 'kded'
kded: ERROR: Communication problem with kded, it probably crashed.
ScimInputContextPlugin()
QObject::disconnect: Unexpected null parameter
~ScimInputContextPlugin()

& if I kdesu kate I get

barry@upstairs:~$ kdesu kate /etc/fstab
kbuildsycoca running...
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()

most of that one appeared after I closed kate. :-X