After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 529900 - Warning: Method "Release" with signature "" on interface "org.gnome.LircProperties.ExternalToolDriver" doesn't exist
Warning: Method "Release" with signature "" on interface "org.gnome.LircProp...
Status: RESOLVED FIXED
Product: gnome-lirc-properties
Classification: Other
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: gnome-lirc-properties-maint
gnome-lirc-properties-maint
Depends on:
Blocks:
 
 
Reported: 2008-04-25 14:10 UTC by Murray Cumming
Modified: 2010-05-19 14:08 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Make 'Detect' button unsensitive during detection (3.55 KB, patch)
2010-05-19 14:08 UTC, Bastien Nocera
committed Details | Review

Description Murray Cumming 2008-04-25 14:10:24 UTC
I'm seeing this warnings several times on the terminal, though I'm not quite sure yet what is triggering them. I think it's while choosing non-supplied remote controls from the combos, though I can't narrow it down to anything in particular.

WARNING:root:org.freedesktop.DBus.Error.UnknownMethod: Method "Release" with signature "" on interface "org.gnome.LircProperties.ExternalToolDriver" doesn't exist

gnome_lirc_properties/ui/backend.py:ExternalToolDriver does have a Release() method. Is there some configuration file that needs to mention it too? Or is it just being called with the wrong parameters somewhere?
Comment 1 Murray Cumming 2008-04-29 05:59:57 UTC
On irc, Mathias said:
"
Seems we do not cast to the proper interface before using the object
with gutsy you could just invoke methods on proxy objects, and the bindings would find the proper interface.
With gutsy you have to request the intended dbus interface before you can use a proxy object.
"
Comment 2 Murray Cumming 2008-10-17 05:01:54 UTC
Great. Please commit.

I see that there is a new lirc 0.8.4 release. Are you using that mostly unpatched?

I'll do a new g-l-p release in the next few days.
Comment 3 Bastien Nocera 2008-10-17 06:44:29 UTC
(In reply to comment #2)
> Great. Please commit.
> 
> I see that there is a new lirc 0.8.4 release. Are you using that mostly
> unpatched?
> 
> I'll do a new g-l-p release in the next few days.

Wrong bug?
Comment 4 Murray Cumming 2008-10-17 07:15:51 UTC
Yeah, sorry.
Comment 5 Bastien Nocera 2010-05-15 13:58:24 UTC
Reassign to alias.
Comment 6 Bastien Nocera 2010-05-17 17:24:25 UTC
Putting this NEEDINFO until we find a reproducer. Seems to work fine here...
Comment 7 Bastien Nocera 2010-05-19 14:03:48 UTC
The problem is that we were missing:
self.__detection_driver = None
in the report_success() and report_failure() callbacks for the detection driver, so the driver still existed even though the service it was attached to had disappeared from the bus.
Comment 8 Bastien Nocera 2010-05-19 14:08:19 UTC
Created attachment 161442 [details] [review]
Make 'Detect' button unsensitive during detection

The 'Detect' button should be unsensitive during detection,
as there's no point in running irrecord twice.

This also fixes potential errors when trying to terminate
the detection driver after it had finished, or after it failed
to start.
Comment 9 Bastien Nocera 2010-05-19 14:08:37 UTC
Attachment 161442 [details] pushed as 3b91ff7 - Make 'Detect' button unsensitive during detection