Public bug reported:
I'm not entirely sure as to what the reason of this is, however I think
it started the undesirable behaviour when:
all things were fine, I could use konqueror and kdevelop etc fine,
I then ran kcontrol and set the icons to use the ubuntu human icons,
which produced a nice integration effect of my kde applications with the
rest of my desktop
I then fired up konqueror and when it went to a file view it started
chewing up the entire CPU output provoking me to painstakingly kill it
via a VT, doing nothing in the process
By starting up konqueror and sending it to a http:// or other protocol
it complains of "can't talk to klauncher"
some KDE filechoosers don't work, either silently failing after showing
an empty box or complaining of not being able to start klauncher or
somelike, this is sporadic depending on application and being almost
random in its appearance, for example Kdevelop fail, while kate works
fine - kolf sometimes doesn't start at all - although there appears to
be some kind of X driver problem with kolf as well.
Switching back to the KDE icons doesn't change anything, konqueror still
persists in it's processor hungry crashing
KDE applications all complain at startup, printing this:
X Error: BadDevice, invalid or uninitialized input device 166
Major opcode: 144
Minor opcode: 3
Resource id: 0x0
Failed to open device
several times over (although this has been the behaviour all the time)
all in all it appears that KDE is being pretty unreliable, perhaps
there's something damaged about the underlying dcopserver architecture,
perhaps if I was running a KDE session it would be okay? Perhaps this is
a multitude of problems that span several bugs?
** Affects: kdebase (Ubuntu)
Importance: Undecided
Status: Unconfirmed
** Description changed:
I'm not entirely sure as to what the reason of this is, however I think
it started the undesirable behaviour when:
- I ran kcontrol and set the icons to use the ubuntu human icons, which
- produced a nice integration effect of my kde applications with the rest
- of my desktop
+ all things were fine, I could use konqueror and kdevelop etc fine,
+
+ I then ran kcontrol and set the icons to use the ubuntu human icons,
+ which produced a nice integration effect of my kde applications with the
+ rest of my desktop
I then fired up konqueror and when it went to a file view it started
chewing up the entire CPU output provoking me to painstakingly kill it
via a VT, doing nothing in the process
By starting up konqueror and sending it to a http:// or other protocol
it complains of "can't talk to klauncher"
some KDE filechoosers don't work, either silently failing after showing
an empty box or complaining of not being able to start klauncher or
somelike, this is sporadic depending on application and being almost
random in its appearance, for example Kdevelop fail, while kate works
fine - kolf sometimes doesn't start at all - although there appears to
be some kind of X driver problem with kolf as well.
+ KDE applications all complain at startup, printing this:
+
+ X Error: BadDevice, invalid or uninitialized input device 166
+ Major opcode: 144
+ Minor opcode: 3
+ Resource id: 0x0
+ Failed to open device
+
+ several times over (although this has been the behaviour all the time)
+
all in all it appears that KDE is being pretty unreliable, perhaps
there's something damaged about the underlying dcopserver architecture,
- perhaps if I was running a KDE session it would be okay?
+ perhaps if I was running a KDE session it would be okay? Perhaps this is
+ a multitude of problems that span several bugs?
** Tags added: dcop dcopserver icons kde klauncher kubuntu xserver
** Description changed:
I'm not entirely sure as to what the reason of this is, however I think
it started the undesirable behaviour when:
all things were fine, I could use konqueror and kdevelop etc fine,
I then ran kcontrol and set the icons to use the ubuntu human icons,
which produced a nice integration effect of my kde applications with the
rest of my desktop
I then fired up konqueror and when it went to a file view it started
chewing up the entire CPU output provoking me to painstakingly kill it
via a VT, doing nothing in the process
By starting up konqueror and sending it to a http:// or other protocol
it complains of "can't talk to klauncher"
some KDE filechoosers don't work, either silently failing after showing
an empty box or complaining of not being able to start klauncher or
somelike, this is sporadic depending on application and being almost
random in its appearance, for example Kdevelop fail, while kate works
fine - kolf sometimes doesn't start at all - although there appears to
be some kind of X driver problem with kolf as well.
+ Switching back to the KDE icons doesn't change anything, konqueror still
+ persists in it's processor hungry crashing
+
KDE applications all complain at startup, printing this:
X Error: BadDevice, invalid or uninitialized input device 166
Major opcode: 144
Minor opcode: 3
Resource id: 0x0
Failed to open device
several times over (although this has been the behaviour all the time)
all in all it appears that KDE is being pretty unreliable, perhaps
there's something damaged about the underlying dcopserver architecture,
perhaps if I was running a KDE session it would be okay? Perhaps this is
a multitude of problems that span several bugs?
** Tags added: konqueror
--
klauncher failure
https://launchpad.net/bugs/77297
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
