bluesdog
01-04-2008, 04:39 AM
A recent upgrade to KDE 3.5.8-1 (sid) seems to have interfered with the administrator mode in kcontrol, so that after choosing admin mode in, for example, login manager, and entering the root password, kcontrol cannot complete the login process.
Clicking any of the other selections causes kcontrol to crash.
When launched from a terminal using the command, kcontrol is useable up until the point where admin privileges are requested, at which point
the terminal displays following:
QImage::smoothScale: Image is a null image
QImage::smoothScale: Image is a null image
QImage::smoothScale: Image is a null image
QLayout "unnamed" added to QVBox "m_body", which already has a layout
X Error: BadMatch (invalid parameter attributes) 8
Major opcode: 6
Minor opcode: 0
Resource id: 0x3a00690and displays
kcontrol: Fatal IO error: client killedWhen it crashes following a click on any other selection.
Apparently a similar error occurred a while back, with the early 3.4 release
Simple workaround: Launch kcontrol as root from a terminal with command $ kdesu kcontrolResult: kcontrol functions normally, and no errors display in terminal.
Another user on the Debian forum reported the same problem, but there's no mention of it yet on the KDE bug-tracker. I'll wait a few days before posting it there...
Clicking any of the other selections causes kcontrol to crash.
When launched from a terminal using the command, kcontrol is useable up until the point where admin privileges are requested, at which point
the terminal displays following:
QImage::smoothScale: Image is a null image
QImage::smoothScale: Image is a null image
QImage::smoothScale: Image is a null image
QLayout "unnamed" added to QVBox "m_body", which already has a layout
X Error: BadMatch (invalid parameter attributes) 8
Major opcode: 6
Minor opcode: 0
Resource id: 0x3a00690and displays
kcontrol: Fatal IO error: client killedWhen it crashes following a click on any other selection.
Apparently a similar error occurred a while back, with the early 3.4 release
Simple workaround: Launch kcontrol as root from a terminal with command $ kdesu kcontrolResult: kcontrol functions normally, and no errors display in terminal.
Another user on the Debian forum reported the same problem, but there's no mention of it yet on the KDE bug-tracker. I'll wait a few days before posting it there...