Bug 179871

Summary:	Automatic drive seeking fails on floppy
Product:	[Unmaintained] kdelibs	Reporter:	Vincent Rodrigue <drvince>
Component:	general	Assignee:	KDE-Windows <kde-windows>
Status:	RESOLVED FIXED
Severity:	crash	CC:	andriusmao, cfeck, ps_ml, ralf.habacker
Priority:	NOR
Version:	4.1
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Vincent Rodrigue 2009-01-07 01:44:23 UTC

Version:           4.1.3 (using KDE 4.1.3)
Compiler:          4.1.3 compiled package for Windows 4.1.3 compiled package for Windows
OS:                MS Windows
Installed from:    MS Windows

When starting most binaries (eg.: kate, kwrite, kspread) the window opens then it asks for a floppy in A:\, Continue, Try Again, Cancel.  Whatever the answer, it crashes to a Windows error reporting window and closes.

Also, if there is a floppy in the drive, write protected or not, the app. goes straight to the crash.

Comment 1 Ralf Habacker 2009-01-07 14:50:22 UTC

We need more informations about this issue: 

1. Which OS (including service pack number) are you using exactly ? 
2. Can you see if there is a wmiapsrv.exe and if yes kill it and start kword - does kword still crashes ? 
3. To get a stack trace Can you download http://internap.dl.sourceforge.net/sourceforge/mingw/mingw-utils-0.3.tar.gz, unpack and run bin/drmingw -i in a dos prompt. Then start kword or another application. If the application crashes press debug and append the result to this thread. 

Thanks
 Ralf

Comment 2 Vincent Rodrigue 2009-01-07 19:45:00 UTC

(In reply to comment #1)
> 1. Which OS (including service pack number) are you using exactly ?
WinXP SP3 32bit on an Athlon 64 4000+
 
> 2. Can you see if there is a wmiapsrv.exe and if yes kill it and start kword -
> does kword still crashes ?
I am using Process Explorer and no, there wasn't a wmiapsrv.exe process that started.

> 3. To get a stack trace Can you download
> http://internap.dl.sourceforge.net/sourceforge/mingw/mingw-utils-0.3.tar.gz,
> unpack and run bin/drmingw -i in a dos prompt. Then start kword or another
> application. If the application crashes press debug and append the result to
> this thread. 
drmingw gave this:
kword.exe caused an Access Violation at location 65076b02 in module QtGui4.dll Reading from location 0000000c.

Registers:
eax=00000000 ebx=0000000c ecx=0000000c edx=000017cc esi=04184c40 edi=041dd088
eip=65076b02 esp=00d9f89c ebp=00000013 iopl=0         nv up ei pl zr na po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000246

Call stack:
65076B02  QtGui4.dll:65076B02  public: bool __thiscall QIcon::isNull(void)const 

and it's the same report regardless to what I answer when it tells me that there is no disk also regardless to if there is a disk or not.

Comment 3 Ralf Habacker 2009-01-07 22:58:35 UTC

The related code is shown below - ecx points to an invalid address, which causes the seg fault. 

65076B00  xor         eax,eax 
65076B02  cmp         dword ptr [ecx],eax 
65076B04  sete        al   
65076B07  ret              

Because the crash happens somewhere in qtgui4.dll and the related function is called very often, I guess the crash does not have anything to do with the floppy related popup. I will probably be a bad pointer access. 

Can't say more yet. :-(

Comment 4 Christoph Feck 2011-07-28 16:42:52 UTC

What is the status of this bug in recent KDE versions? Please add a comment.

Comment 5 Andrius 2012-02-28 20:33:22 UTC

Marking as NEEDSINFO + WORKSFORME

Comment 6 Andrius 2012-02-28 20:36:07 UTC

Sorry, bugzilla moved me to a different bug and I hadn't noticed, changing back to UNCONFIRMED