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 589898 - local variable 'gobject' referenced before assignment
local variable 'gobject' referenced before assignment
Status: RESOLVED FIXED
Product: LDTP
Classification: Other
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: LDTP maintainers
LDTP Development Mailing List
Depends on:
Blocks:
 
 
Reported: 2009-07-27 16:21 UTC by Murray Cumming
Modified: 2009-07-27 17:07 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Murray Cumming 2009-07-27 16:21:20 UTC
Using ldtp from git master, I get this when using Glom's test scripts. I guess it could be a problem in our python, but maybe it's a problem in ldtp. I think this is when trying to use the GtkFileChooser:

Traceback (most recent call last):
  • File "database-creation/create-db.py", line 71 in <module>
    common.select_backend(creation_dialog, backend)
  • File "./common.py", line 93 in select_backend
    if ldtp.objectexist(dialog_title, 'rbtn' + text):
  • File "/opt/gnome220/lib/python2.5/site-packages/ldtp.py", line 1903 in objectexist
    objinfo = getobjectinfo (windowName, componentName)
  • File "/opt/gnome220/lib/python2.5/site-packages/ldtp.py", line 3381 in getobjectinfo
    logFailures ('getobjectinfo failed: %s' % msg.value)
  • File "/opt/gnome220/lib/python2.5/site-packages/ldtp.py", line 111 in logFailures
    log (ldtputils.imagecapture (outFile = _logFile), "screenshot")
  • File "/opt/gnome220/lib/python2.5/site-packages/ldtputils.py", line 203 in imagecapture
    gobject.idle_add(capturescreenshot)
UnboundLocalError: local variable 'gobject' referenced before assignment

Comment 1 Nagappan Alagappan 2009-07-27 17:01:51 UTC
Committed a fix in git, request to check it. If you face this issue again, please reopen this bug.

Thanks for the bug report.

Thanks
Comment 2 Murray Cumming 2009-07-27 17:07:01 UTC
Yes, that seems to fix it. Thanks.