By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 1618 - Logout status dialog quirks
Summary: Logout status dialog quirks
Status: NEW
Alias: None
Product: TDE
Classification: Unclassified
Component: tdebase (show other bugs)
Version: R14.0.x [Trinity]
Hardware: Other Linux
: P5 minor
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2013-08-10 17:15 CDT by Darrell
Modified: 2018-05-27 10:48 CDT (History)
2 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Darrell 2013-08-10 17:15:43 CDT 
Bug No. 1:
==========

There are two timers associated with the logout status dialog. One timer waits three seconds before adding two buttons to the status dialog, which then allows the user to skip notifications or cancel the logout. The second timer is 20 seconds. An associated count down timer is embedded in the Skip Notification button. When the status dialog buttons appear after the first three second expiration, the timer starts at 18 seconds rather than 20 seconds or 17 seconds (20 - 3).

An additional observation from when the status dialog buttons were being developed, although no longer possible, when the user had an unsaved document opened in kate, the status dialog appeared along with the kate dialog. Left unattended, the status dialog count down timer would reset to 21 seconds rather than 20 seconds.

The extra second seems to be a basic increment initialization bug.

Bug No. 2:
==========

With a few process/app names, the status dialog text message is too long and is truncated at the right edge. Most of the process/app names fit into the dialog fine and are readable --- at least to the extent any person can read that fast.

Bug No. 3:
==========

A specially compiled version of tdeio-locate can be used to create a logout stall that the status dialog does not work well with (refer to bug report 760). Using that trigger mechanism, there is no feedback mechanism at all when a user disables the status dialog in kcontrol. On a good note, the logout stall terminates at the end of 20 seconds (actually 21 seconds as measured with a stop watch, which confirms the 21 second bug reported above). Although such stalls likely will be corner cases, that the user receives no notification likely will motivate additional cause bug reports. Seems a simple solution would be that the status dialog always appears during a logout stall despite the user's configuration in kcontrol. That is a reasonable exception. With no stall the dialog honors the user's configuration and does not appear. As a stall would be the only exception to the user's configuration, the dialog would appear at the end of the three second timer, which means the buttons would appear immediately in the dialog and show the count down timer.