Bug 69364 - MIT-SCREEN-SAVER ScreenSaverQueryInfo() til-or-since negative after ForceScreenSaver()
Summary: MIT-SCREEN-SAVER ScreenSaverQueryInfo() til-or-since negative after ForceScre...
Status: RESOLVED MOVED
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium minor
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-15 00:15 UTC by Kevin Ryde
Modified: 2018-12-13 22:29 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
program printing til-or-since after ForceScreenSaver (1.14 KB, text/plain)
2013-09-15 00:15 UTC, Kevin Ryde
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Ryde 2013-09-15 00:15:34 UTC
Created attachment 85839 [details]
program printing til-or-since after ForceScreenSaver

In recent Debian i386 xvfb 1.12.4, if the screen saver is turned on programatically with ForceScreenSaver then the "til-or-since" field of MIT-SCREEN-SAVER ScreenSaverQueryInfo is some apparent negative value.

The program foo.c attached prints

    state 1
    til_or_since 4294369575 (or as signed -597721)

where I expected til_or_since would be some small positive value, being the short time since ForceScreenSaver turned on the saver.

Is that the way til-or-since is supposed to work?  It's CARD32 in the the spec and proto.h, and "unsigned long" in the Xlib bindings, so I would think it ought not be an apparent twos-complement negative like 4294369575.
Comment 1 GitLab Migration User 2018-12-13 22:29:15 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/448.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.