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 600245 - gnome-schedule unable to run under ubuntu 9.10
gnome-schedule unable to run under ubuntu 9.10
Status: RESOLVED DUPLICATE of bug 588091
Product: gnome-schedule
Classification: Other
Component: general
2.1.0
Other Linux
: Normal normal
: ---
Assigned To: GNOME Schedule Maintainers
GNOME Schedule Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-10-31 17:48 UTC by 59chip
Modified: 2009-10-31 17:57 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description 59chip 2009-10-31 17:48:51 UTC 
jean@jean-study:~$ gnome-schedule
/usr/share/gnome-schedule/mainWindow.py:158: DeprecationWarning: Use the new widget gtk.Tooltip
  tip = gtk.Tooltips ()
/usr/share/gnome-schedule/mainWindow.py:159: DeprecationWarning: Use the new widget gtk.Tooltip
  tip.enable ()
Traceback (most recent call last):

+ Trace 218699

  • File "/usr/share/gnome-schedule/gnome-schedule.py", line 74 in <module> 
    mainWindow = mainWindow.main(debug_flag, False, pr, manual_poscorrect)
  • File "/usr/share/gnome-schedule/mainWindow.py", line 257 in __init__ 
    self.schedule_reload ()
  • File "/usr/share/gnome-schedule/mainWindow.py", line 304 in schedule_reload 
    data = self.crontab.read ()
  • File "/usr/share/gnome-schedule/crontab.py", line 438 in read 
    array_or_false = self.parse (line)
  • File "/usr/share/gnome-schedule/crontab.py", line 604 in parse 
    success, ver, title, desc, output, display, command_d = self.get_job_data (job_id)
  • File "/usr/share/gnome-schedule/crontab.py", line 690 in get_job_data 
    return True, ver, title, desc, output, display, command_d
UnboundLocalError: local variable 'display' referenced before assignment 
jean@jean-study:~$
Comment 1 Gaute Hope 2009-10-31 17:57:27 UTC 

*** This bug has been marked as a duplicate of bug 588091 ***