Bug 218922

Reading again my bug description, I realize I forgot to mention that kate is functional once the message closed, it's just very annoying that it appears on every file open / save.

It's happening also with mingw, after updating kde to 4.3.4. ( in home machine this does not happen, in work machine it's the first time I install kde in a non-'c:' drive, but it is not happening only with kate, but several other apps such as konqueror, etc.. )

same behaviour, kdeinit fails but apps work normally after that, work machine is also windows XP, but 32 bits ( home machine is vista )

Thanks for the precision. I updated the bug title to show it's not kate specific.

Hello,
This seems like the same bug as bug#219066

I can confirm this too. I have tried both MinGW and MSVC in WinXP. Both have the same kdeinit4.exe problem.

Also, even if ignore the error and Kate launch properly, there is an error dialog that shows: "Could not start process Cannot talk to klauncher: The name org.kde.klauncher was not provided by any .service files."

Same here with XP and SP3.

How can I help to fix this problem?

looking at it there are some questions I'd have:
Please close down KDE completely, then open dbgview and a console:
What happens if you do run kdeinit4 with any of the options:
*kdeinit4 --verbose (this would just start kdeinit4, dbus and kded)
*kdeinit4 --list (this should give you some output in dbgview)
*kdeinit4 --shutdown (after you started it)
*kdeinit4 --terminate (after you started it)

Hmm... Is there anything I need to do to get some outputs in dbgview ? 
I just started it, then started a console, launched the specified commands. Everytime, I get the kdeinit4.exe error message, but I never get anything in dbgview.

Am I doing something wrong ?

Same result here. I think I don'T have the debug version of the kde/qt libs installed. I have searched the package manager but there I haven't found debug packages.
Btw I'm using the msvc32 build.

> debug packages 

One more topic for the coming KDE on Windows developer sprint.

In detailed error message it is said something about AMD, while I have Intel CPU on this computer. Is it possible that release was just compiled with some AMD64 optimizations and fails because of this?

Also Intel CPU here (Xeon), maybe this is a track to follow ?

FWIW, Installed unstable 4.3.90, and the bug is also there.

I have the same issue here since upgrading to 4.3.4.
I removed all configurations and KDE related files and tried again but it still crashes. 
Unfortunately there is no change with the UNSTABLE packages, they crash too!
I'm on intel (Core 2 Duo), too.
When I downgrade to 4.3.3 I don't have this problem.

Maybe let's vote for this issue?

I'm also using a Intel Core2 Duo CPU T9600.

I have this issue since I upgraded the package kdelibs from 4.3.4 to 4.3.4-1.
(After I upgraded the whole installation to 4.3.4 I noticed (one day later) that there was a new version of kdelibs.)
I'm using an Intel processor, WinXP(SP3) and the msvc32 build.

From https://bugs.kde.org/show_bug.cgi?id=218922#c13:
>When I downgrade to 4.3.3 I don't have this problem.

The same here. Downgrading to 4.3.3 from 4.3.4 solved it.

(XP 64-bit, currently using 4.3.90 but I experienced the same thing in 4.3.4) 
I did some digging and found that the org.kde.klauncher.service file doesn't exist.  I'm not familiar with how exactly dbus works, but I assume that it should go in <KDEInstallDir>\share\dbus-1\service\ (where I found similarly-named files).  I also noticed that other files in that directories show paths to incorrect locations (c:\kde\kde-<somedir>\bin rather than <KDEInstallDir>\bin).

Never mind my previous comment - downgrading to 4.3.3 reveals that those files are practically the same (the only difference being the line endings - \r\n in 4.3.3 and \n in 4.3.90 - which upon changing may have fixed this issue, but resulted in dolphin and konqueror failing to start after several kdeinit4 crashes and other error dialogs and plasma-desktop showing a blank desktop with a couple of X buttons for failed widgets)

I believe his is the same bug as bug#219066

Same here, XP SP3, Core 2 Duo E6600 processor. Most of KDE4win apps fail with this error.

Just reproduced the same with 4.4.0 version.

Nothing Kate specific here, if many apps fail with this.

i tried the suggestion to use the debug viewer and run kdeinit from the command line but the debug viewer doesn't show anything... all I get is my post mortem debugger asking if I want to use visual studio to debug the problem. 

Can I attach it to sources/symbols to find out where the error is or is the binary disassembly any use to anyone here? 

Sorry... Also confirm 4.4 with this issue on windows XP

The problem seems still to exist. I can confirm that, unfortunately.
This makes KDE on windows unusable for me and for a great amount of users for about 10 weeks now :(
If the problem was just introduced with 4.3.4 (It didn't occur before), it can't be that hard to find out the reasons. But this bug is still marked as "NEW" and doesn't seem to be overtaken by someone.

Hope that it get's fixed soon now...

Myself and Patrick Spendrin are looking at the issue, which mostly means that Patrick is looking into it ;) the newest piece of the puzzle is this backtrace: 

>	ntdll.dll!_RtlLengthSid@4()  + 0x8 bytes	
 	kdeinit4.exe!0040196c() 	
 	[Frames below may be incorrect and/or missing, no symbols loaded for kdeinit4.exe]	
 	kernel32.dll!_LocalFree@4()  + 0x2b bytes	
 	45ffffff()

if anyone knows why there would be an unknown exception thrown with this backtrace then they know how to fix this bug. the exact message is: 

Unhandled exception at 0x7c9131a6 in kdeinit4.exe: 0xC0000005: Access violation reading location 0x00000001.

I'm not sure if what we're looking into warrants changing the bug status from New to Assigned or Needs Info but we are working on it.

Hi, thanks for your investigation. I really appreciate knowing that someone is working on this issue :)

Thanks, Steffen

Problem also occurs on my PC on my account, but on fresh account error doesn't occur. Maybe this helps. I've removed all non-standard paths from PATH variable, but didn't help.

And some more. Problem doesn't occur on local system account, and do occur on account from AD domain.

Ok, Andrew and I came near to the spot where the error is, we do have a workaround now, but I hope to be able to work on a real solution this afternoon. I will make updates available in the coming (2-3) days.

(In reply to comment #30)
> Ok, Andrew and I came near to the spot where the error is, we do have a
> workaround now, but I hope to be able to work on a real solution this
> afternoon. I will make updates available in the coming (2-3) days.

Thanks =D ! will test as soon as available.

After looking a bit, we also found a fix now. I will provide updated packages for 4.4.0 for both compilers tonight (these can be found on winkde.org mirror) and nightly builds will update as soon as they do work again.

Ok, please everybody: (update to 4.4.0) and or download this http://winkde.org/pub/kde/ports/win32/releases/stable/latest/kdelibs-mingw4-4.4.0-1-bin.tar.bz2 package for mingw4 or this package http://winkde.org/pub/kde/ports/win32/releases/stable/latest/kdelibs-vc90-4.4.0-1-bin.tar.bz2 for vc90(msvc) compiler. Unpack this directly into your KDE installation directory after having closed all running KDE processes.
After that please simply retry what I wrote above: kdeinit4 --verbose, kdeinit4 --list etc.
If this fixes the issues, please give a short note.

Working fine for me. Bug seems to be fixed.

Great! That problem was really making KDE on Windows unusable for me. I have just tried the fix and after unpacking with WinZip (cygwin's tar created unusable files for some reason), it works *much better*. When I browse with dolphin, I no longer get zillions of error messages. I can actually see the files and open them. Wow!

However, there is an error every now and then (haven't yet figured out whether it is linked with any specific action). I will attach the error message.
And the management of network drives still is very unintuitive. But that's a different point...

Created attachment 41126 [details]
Error message from kioslave

SVN commit 1096439 by sengels:

fix crashes in kdeinit4 when using Active Directory

BUG: 218922

 M  +19 -1     kdecore/util/kuser_win.cpp  
 M  +12 -1     kinit/kinit_win.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1096439

SVN commit 1096444 by sengels:

backport r1096439
CCBUG: 218922

 M  +19 -1     kdecore/util/kuser_win.cpp  
 M  +12 -1     kinit/kinit_win.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1096444

This fixes the bug for me. Thanks for the fix!

Thanks for the correction, and keep up the good work :)

Hi, just tested it today and it works! Thank you very much for your great work!