Bug 215837 - Autoaway plugin should use DBus instead of calling xprop
Summary: Autoaway plugin should use DBus instead of calling xprop
Alias: None
Product: Fedora
Classification: Fedora
Component: xchat-gnome
Version: 11
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Brian Pepple
QA Contact: Fedora Extras Quality Assurance
Whiteboard: bzcl34nup
Depends On:
TreeView+ depends on / blocked
Reported: 2006-11-15 23:20 UTC by Matěj Cepl
Modified: 2018-04-11 19:08 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-06-28 10:23:19 UTC

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
GNOME Bugzilla 397723 None None None Never

Description Matěj Cepl 2006-11-15 23:20:14 UTC
Description of problem:
Apparently autoaway plugin polls xprop quite often for information whether the
screensaver is on. Together with bug 215832 I got interesting situation when
xchat-gnome generated 12 core-dumps a minute ;-). Notwithstanding that bug, I
think that being Gnome-oriented, xchat-gnome should use DBus to get information
whether screensaver is on.

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

How reproducible:
100% with xorg-x11-utils-7.1-2.fc6

Steps to Reproduce:
1.switch Autoaway plugin on
2.run xchat-gnome

Comment 1 Brian Pepple 2006-11-16 21:45:58 UTC
Actually, the autoway plugin does use dbus w/ the gnome-screensaver, but code
for dbus support was moved into the main code for xchat recently, and seems to
have broken the autoaway plugin.  Once I get settled in from my vacation, I look
at fixing the autoaway plugin.

Comment 2 Brian Pepple 2007-01-16 20:08:30 UTC
The autoaway plugin is definitely not working correctly.

When running the following, the autoaway plugin doesn't activate:
dbus-send --session --dest=org.gnome.ScreenSaver --type=method_call
--print-reply --reply-timeout=20000 /or/gnome/ScreenSaver
org.gnome.ScreenSaver.SetActive boolean:true

I'll try to find some time tomorrow, to see if I can fix this.

Comment 3 Matěj Cepl 2007-03-01 17:18:58 UTC

Comment 4 Brian Pepple 2007-03-01 17:54:15 UTC
pong.  I have been swamped with work, and haven't had a chance to work on this
since January when I opened a bug upstream.

Comment 5 Bug Zapper 2008-04-04 04:43:01 UTC
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers

Comment 6 Bug Zapper 2008-05-14 02:28:18 UTC
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:

Comment 7 ritz 2009-05-09 21:09:44 UTC
fix attached to 

Comment 8 Bug Zapper 2009-06-09 09:11:21 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:

Comment 9 Bug Zapper 2010-04-27 11:40:49 UTC
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 10 Bug Zapper 2010-06-28 10:23:19 UTC
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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.

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.