[ros-bugs] [Bug 4343] Texter Management breaks Space, Enter and Tab keys

ReactOS.Bugzilla at www.reactos.org ReactOS.Bugzilla at www.reactos.org
Mon Apr 6 22:30:06 CEST 2009


http://www.reactos.org/bugzilla/show_bug.cgi?id=4343


jansssens <jroeloffzen at hotmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jroeloffzen at hotmail.com




--- Comment #1 from jansssens <jroeloffzen at hotmail.com>  2009-04-06 22:30:05 CET ---
confirmed in r40390:
0- run wordpad
1- install Texter
2- start Texter
3- [Enter] in Wordpad has no effect. Typing chars works
4- exit Texter
5- [Enter] in Wordpad works again

See (partial) debug logging below. First line appears when starting Texter.
Disabling Texter doesn't change behaviour, only exit does.


(subsystems\win32\win32k\ntuser\sysparams.c:862) FIXME: Unsupported SPI Action
0
x2000 (uiParam: 0x0, pvParam: 0x9d8b4d34, fWinIni: 0x0)
(ntoskrnl\mm\section.c:4757) FIXME: didn't check for outstanding write probes
(ntoskrnl\mm\section.c:4757) FIXME: didn't check for outstanding write probes
(ntoskrnl\mm\section.c:4757) FIXME: didn't check for outstanding write probes
(ntoskrnl\mm\section.c:4757) FIXME: didn't check for outstanding write probes
(subsystems\win32\win32k\objects\gdiobj.c:652) Object 0x0 currently being
destro
yed!!!
(subsystems\win32\win32k\objects\gdiobj.c:675) Attempt DeleteObject 0x0
currentl
y being destroyed!!!
(subsystems\win32\win32k\ntuser\timer.c:514) Unable to locate timer in message
q
ueue for Window.
(subsystems\win32\win32k\ntuser\cursoricon.c:140) Removing pointer!
(subsystems\win32\win32k\ntuser\timer.c:514) Unable to locate timer in message
q
ueue for Window.
(subsystems\win32\win32k\ntuser\timer.c:437) Invalid window handle
(subsystems\win32\win32k\ntuser\timer.c:437) Invalid window handle


-- 
Configure bugmail: http://www.reactos.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.


More information about the Ros-bugs mailing list