kded: ERROR: KUniqueApplication: Registering failed!

Thanks for taking the time to report this bug and helping to make Ubuntu better. With which version of Ubuntu did you notice this issue? Thanks in advance.

i've make one mistake: this report bug it's no-good:
cause the bug it's the same of 55322 not of the 55233
as i write, i've send a second report bug that it's
the right one...

--- Brian Murray <email address hidden> a écrit :

> Thanks for taking the time to report this bug and
> helping to make Ubuntu
> better. With which version of Ubuntu did you notice
> this issue? Thanks
> in advance.
>
> ** Changed in: adept (Ubuntu)
> Assignee: (unassigned) => Brian Murray
> Status: Unconfirmed => Needs Info
>
> --
> same that 55233
> https://bugs.launchpad.net/bugs/119333
> You received this bug notification because you are a
> direct subscriber
> of the bug.
>

___________________________________________________________________________
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions !
Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses
http://fr.answers.yahoo.com

the version it's kubuntu 7.04
i'still have the same problem, and i'get also a related error whenever i launch a program: some like:

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
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.
kapture::PkgSystem::PkgSystem()

did you use kdesu adept or sudo adept?

 We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again