| Summary: | On some computers the shutdown dialog appears with the delay | ||
|---|---|---|---|
| Product: | TDE | Reporter: | q4os_user <winebugs140> |
| Component: | other (any) | Assignee: | Slávek Banko <slavek.banko> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | CC: | bugwatch, michele.calgaro, slavek.banko |
| Priority: | P5 | ||
| Version: | R14.0.1 [Trinity] | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
| Bug Depends on: | |||
| Bug Blocks: | 2575 | ||
|
Description
q4os_user
2016-02-04 18:33:52 CST
I believe that this has a simple explanation. For logout is tested for the ability Suspend, Hibernate and Freeze. And it may be the first moment when it is necessary to activate dbus service tde_dbus_hardwarecontrol. And dbus takes a while before the service starts. I'll try to find a reasonable way to activate the service dbus earlier. >I believe that this has a simple explanation. For logout is tested for the
>ability Suspend, Hibernate and Freeze. And it may be the first moment when it
>is necessary to activate dbus service tde_dbus_hardwarecontrol. And dbus takes
>a while before the service starts.
This is a good guess Slavek. Perhaps we can get the system to check for Suspend, Hibernate and Freeze availability after login, no need to wait until the user click on the Logout button. Need to check how big that change would be though.
(In reply to Michele Calgaro from comment #2) > >I believe that this has a simple explanation. For logout is tested for the > >ability Suspend, Hibernate and Freeze. And it may be the first moment when it > >is necessary to activate dbus service tde_dbus_hardwarecontrol. And dbus takes > >a while before the service starts. > > This is a good guess Slavek. Perhaps we can get the system to check for > Suspend, Hibernate and Freeze availability after login, no need to wait > until the user click on the Logout button. Need to check how big that change > would be though. tde_dbus_hardwarecontrol is now started at background in starttde - see commits 443c9105 (master) and fb2f0303 (r14.0.x) in tdebase. Because daemon is now started early enough, the problem should be resolved. Please, you can confirm it with the R14.0.4~preliminary? The problem seems to be fixed now, after the change on tde_dbus_hardwarecontrol. Feel free to reopen the bug if this is not the case |