[Kommander-devel] bugfest

[Eric Laffoon]

On Thursday 07 September 2006 1:34 am, Eric Laffoon wrote:
> Seems like if you use
> @setGlobal(device, @Input.openfile(/dev,"", Printer Device Name))
> then you have a real problem. Selecting a device causes a slow smoldering
> crash of the dialog.

Wow! Disregard. I need to set my system rebuilding. I just tried this with 
kdialog and something is definitely wrong, though I'm not sure if it was in 
the amd64 configuration changes, a gcc update or what. I get the same error 
hk_classes through... At least they both end with "Alarm Clock".
kio (KDirWatch): WARNING: KDirWatch::removeDir can't handle '/dev'
*** glibc detected *** double free or corruption (out): 0x0000000000b6ee70 ***
Alarm clock

Knoda crash
*** glibc detected *** double free or corruption (out): 0x00000000008c4250 ***
Alarm clock

I wonder what is with Alarm clock constantly being what is corrupted?

Can someone confirm the attached dialog doesn't crash when selecting a device 
on initialization?
-- 
Eric Laffoon
Project Lead - kdewebdev module
-------------- next part --------------
A non-text attachment was scrubbed...
Name: inklevels.kmdr
Type: application/x-kommander
Size: 23491 bytes
Desc: not available
Url : http://momo.creolmail.org/pipermail/kommander-devel/attachments/20060907/c2b221da/inklevels-0001.bin