Details
-
Bug
-
Resolution: Fixed
-
Major
-
0.4.9-dev-60-g1dfbed9 https://github.com/reactos/reactos/commit/1dfbed9c3dbd135c7bf51090b9cadde6d2642340
Description
Stopping Printer Spooler service takes more than 1 minute (+error if cancel)
reactos-bootcd-0.4.14-dev-1455-g963d39b-x86-gcc-lin-dbg but was already present in 0.4.13-dev-1200 (not a recent regression)
This service likely does nothing at thisstage but "stopping" from the service manager takes more than 1 minute.
Click on "close" on the service stop Windows does nothing and leads to error with 0x0 winwow handle and Pipe write failure but this is reported in a dedicated ticket as it happens for all services : https://jira.reactos.org/browse/CORE-16950
err:(dll/win32/advapi32/service/scm.c:140) RpcBindingFree returned 0x6a6 |
err:(dll/win32/advapi32/service/scm.c:140) RpcBindingFree returned 0x6a6 |
(base/system/services/database.c:624) ScmRemoveServiceImage() called |
err:(win32ss/user/user32/windows/dialog.c:2103) got invalid window handle (00000000); buggy app !? |
err:(dll/win32/advapi32/service/eventlog.c:144) RpcBindingFree returned 0x6a6 |
err:(dll/win32/advapi32/service/scm.c:140) RpcBindingFree returned 0x6a6 |
err:(dll/win32/advapi32/service/sctrl.c:693) Pipe write failed (Error: 232) |
Initially occured with Printer Spooler but happens with many others (DNS server, ...)
Attachments
Issue Links
- blocks
-
CORE-12413 We incorrectly stop the services
- Resolved
-
CORE-13233 TightVNC Server 2.8.8 does not work if you stop and try to start as a service.
- Resolved
-
CORE-14222 Regression TightVNC 2.7.10 from rapps crashes with unhandled exception upon Shutdown from context menu
- Resolved
- is blocked by
-
CORE-16950 "Close" button on Service start/stop progress windows leads to null windows handle and pipe write failure
- Resolved
- relates to
-
CORE-19133 Printers bring-up epic link.
- Open
-
CORE-15064 SERVICE_CONTROL_STOP on Spooler takes ages
- Resolved