Version: (using KDE KDE 3.4.3) Installed from: AIX Packages Compiler: george staikos packages OS: AIX when i try and connect via xdmcp to kde, the greeter fails to start, and I get stuck in a look of it starting, then failing and repeat until the xserver is killed. I get the following log error when trying to start kdm: Jan 30 17:13:40 kdm_greet[52590] panic: Config value 0x102b not available Jan 30 17:13:40 kdm: 158.234.41.52:0[34750] error: Abnormal termination of greeter for display 158.234.41.52:0, code 1, signal 0
have you restarted kdm after upgrading?
yes, I've also tried installing onto a system which did not have kde at all and get the same error. it seems that config value 0x102b is PingInterval, although it doesn't help if I set the value in the config file (previously it was commented out), I still get the same error.
something must be thoroughly hosed. kdm's build magic should preclude such inconsistencies. please start kdm with -debug 15 an send me the daemon.* syslog.
Created attachment 15238 [details] KDM Log from crash
have attached the kdm.log file, there was no logging to the daemon.log syslog
you have a weird system ... no syslog, no /dev/random, no working kdm ... :) i really have no clue what's going on. the build seems inconsistent. seems like nobody tried using kdm from these packages before. :) any idea, george?
No idea.. reza?
I'm able to reproduce the problem. I've never noticed before because I log in from the console instead of using XDMCP. I'll try to dig deeper and see what's going on here.
Created attachment 15260 [details] Temporary workaround kdm_greet is here: read.read(??, ??, ??) at 0xd01e62c8 Reader(0x2ff22a30, 0x4) at 0x100063ec GRead(0x2ff22a30, 0x4) at 0x10006358 GRecvInt() at 0x10008dfc ReqCfg(0x102b) at 0x1000618c GetCfgInt(0x102b) at 0x10008b3c unnamed block $b1, line 105 in "kdmconfig.cpp" init_config(), line 105 in "kdmconfig.cpp" main(0x1, 0x2ff22e9c) at 0x10005824 kdm is here: FindCfgEnt(d = 0x2003b4d8, id = 4139), line 344 in "resource.c" CtrlGreeterWait(0x1) at 0x10018c6c OpenGreeter() at 0x1001937c ManageSession(0x2003b4d8) at 0x1001961c StartDisplayP2(0x2003b4d8) at 0x1000392c StartDisplay(0x2003b4d8) at 0x10003b74 manage(0x2ff210e8, 0x10, 0x17, 0x8) at 0x10013af8 ProcessRequestSocket(0x8) at 0x100140ec ProcessListenSockets(0x2ff211c0) at 0x10023bac MainLoop() at 0x10002a40 main(0x3, 0x2ff22b2c) at 0x10002354 It seems that at this point, "PingInterval" is not a loaded configuration value. Using the attached patch, I can force it to be, and everything starts working fine. However, I'm still not sure what the root cause of the problem is. Oswald, does this give you any general idea what's happening?
have applied that patch, and the greeter does indeed start now, however it appears that none of the variables in the kdmrc are being read, as the greeter starts with the user list, a clock and no picture, despite the reverse being specificed in the kdmrc. also, upon trying to login I get: Mar 23 09:31:59 kdm: 158.234.41.52:0[24104] info: Cannot create session log file : No such file or directory Mar 23 09:31:59 kdm[25872] info: Cannot convert Internet address 158.234.41.52 to host name Mar 23 09:32:01 kdm_greet[14050] error: Can't open default user face QImage::convertDepth: Image is a null image QImage::smoothScale: Image is a null image
Created attachment 15276 [details] a better fix I see what you're talking about. Try this patch instead. I think it might work better.
could you email me the resulting kdm binary reza? i'm not in a position to compile the whole of the kdm binary (managed to compile the kdm_config binary as it doesnt have many dependencies). I can then test asap.
yes, that seems to work fine now with the latest patch.
Oswald, Does the fix seem acceptable to you?
ah, so it is another occurrence of *this* bug ... reza, the packages are really only kde 3.4, yes? an upgrade to 3.5.2 should suffice then ...
Yes, they are 3.4.3 packages. Would it do any harm if the old package was rebuilt with that patch, just so it doesn't crash any more?
first i'd update the whole kdm package. :) if that's no option, you have to track down the patch and its dependencies yourself ... i don't remember the details any more.
*** This bug has been marked as a duplicate of 114385 ***