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 420845 - crash in Gimmie: running gimmie in rhel5 ...
crash in Gimmie: running gimmie in rhel5 ...
Status: RESOLVED DUPLICATE of bug 420303
Product: gimmie
Classification: Deprecated
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Gimmie Maintainers
Gimmie Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-21 03:35 UTC by svansiclen
Modified: 2007-03-21 05:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description svansiclen 2007-03-21 03:35:36 UTC 
What were you doing when the application crashed?
running gimmie in rhel5 where ubuntulooks would never reside, so... gimmie is for ubuntu only???? ( I right clicked on linux)


Distribution: Red Hat Enterprise Linux Client release 5 (Tikanga)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0
CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0

Traceback (most recent call last):

+ Trace 120626

  • File "/usr/lib/python2.4/site-packages/gimmie/gimmie_gui.py", line 401 in do_button_press_event 
    for mi in self.topic.get_context_menu_items():
  • File "/usr/lib/python2.4/site-packages/gimmie/gimmie_computer.py", line 694 in get_context_menu_items 
    if self.settings_menu_tree:
AttributeError: 'ComputerTopic' object has no attribute 'settings_menu_tree' 






Comment 1


Tony Tsui





          2007-03-21 05:42:42 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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