Bug 1274931 - xdg-screensaver suspend winID, does not work with winID in decimal format
Summary: xdg-screensaver suspend winID, does not work with winID in decimal format
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xdg-utils
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-23 23:17 UTC by Norman Goldstein
Modified: 2016-07-19 20:15 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 20:15:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Norman Goldstein 2015-10-23 23:17:20 UTC
Description of problem:
xdg-screensaver suspend winID, does not work with winID in decimal format

Version-Release number of selected component (if applicable):
1.1.1


How reproducible:
Always

Steps to Reproduce:
1. Use xwininfo to get a window id, say, 0x3e00001
2. Run:   xdg-screensaver suspend 65011713
(The same number is expressed in hex and dec)
3.

Actual results:
If winID is expressed as 0x3e00001 the xdg command succeeds.
If winID is expressed as 65011713, the xdg command fails, with the messages:
   Protocol error: bad 3 (Window); Sequence Number 5
   Opcode (20, 0) = GetProperty
   Bad resource 1694570259 (0x65011713)
   at -e line 15.
It appears that the decimal number is being treated as hex digits.

Expected results: No complaints, and the screensaver is suspended.


Additional info:
The suspending works fine when using hex format for the window ids.

Comment 1 Fedora End Of Life 2016-07-19 20:15:05 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.