GNOME Bugzilla – Bug 435592
crash in Gimmie: I've pressed the 'Applic...
Last modified: 2007-05-08 19:55:54 UTC
What were you doing when the application crashed? I've pressed the 'Application'-Button Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: AluminumAlloy-Smog Icon Theme: Tango 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 ----------- .xsession-errors (12 sec old) --------------------- ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) java.net.UnknownHostException: Freya: Freya at java.net.InetAddress.getLocalHost(InetAddress.java:1315) at org.netbeans.CLIHandler.initialize(CLIHandler.java:487) at org.netbeans.CLIHandler.initialize(CLIHandler.java:291) at org.netbeans.Main.execute(Main.java:161) at org.netbeans.Main.main(Main.java:48) CalDAV Eplugin starting up ... (evolution-2.10:8038): evolution-mail-WARNING **: ignored this junk plugin: not enabled or we have already loaded one (evolution-2.10:8038): e-utils-WARNING **: Plugin 'Bogofilter Ausschuss-Erweiterung' failed to load hook 'org.gnome.evolution.mail.junk:1.0' ** (evolution-2.10:8038): DEBUG: mailto URL command: evolution %s ** (evolution-2.10:8038): DEBUG: mailto URL program: evolution -------------------------------------------------- Traceback (most recent call last):
+ Trace 132168
self._show()
self.topic_win = self.topic.get_topic_window()
self.topic_window = TopicMenu(self)
TopicView.__init__(self, topic)
self.sidebar = Sidebar(topic)
gtk.VBox.__init__(self, False, 4)
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 416060 ***