Bug 428763 – crash in Gimmie:

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 428763 - crash in Gimmie:


Summary:	crash in Gimmie:


Status:	RESOLVED DUPLICATE of bug 421732

Product:	gimmie
Classification:	Deprecated
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Gimmie Maintainers
QA Contact:	Gimmie Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-04-11 20:10 UTC by serkan
Modified:	2007-04-12 22:41 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description serkan 2007-04-11 20:10:58 UTC

What were you doing when the application crashed?



Distribution: Gentoo Base System release 1.12.10
Gnome Release: 2.18.0 2007-04-10 (Gentoo)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-gentoo-r5 #1 SMP PREEMPT Tue Apr 10 05:19:41 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70000000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Murrina-Eternal_Blue
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 (38 sec old) ---------------------
Initializing gnome-mount extension
(compiz-tray-icon:5194): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(compiz-tray-icon:5194): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(compiz-tray-icon:5194): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(compiz-tray-icon:5194): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(nautilus:5184): Liboobs-WARNING **: There was an unknown error communicating with the backends: Process /usr/bin/system-tools-backends exited with status 0
(nautilus:5184): Liboobs-WARNING **: There was an unknown error communicating with the backends: Process /usr/bin/system-tools-backends exited with status 0
** Message: drive = 0
** Message: volume = 0
--------------------------------------------------
Traceback (most recent call last):

+ Trace 126975

File "/usr/lib64/python2.5/site-packages/gimmie/gimmie_applet.py", line 516 in do_button_press_event
```
self._show()
```
File "/usr/lib64/python2.5/site-packages/gimmie/gimmie_applet.py", line 521 in _show
```
self.topic_win = self.topic.get_topic_window()
```
File "/usr/lib64/python2.5/site-packages/gimmie/gimmie_applet.py", line 393 in get_topic_window_mod
```
self.topic_window = TopicMenu(self)
```
File "/usr/lib64/python2.5/site-packages/gimmie/gimmie_applet.py", line 181 in __init__
```
TopicView.__init__(self, topic)
```
File "/usr/lib64/python2.5/site-packages/gimmie/gimmie_topicwin.py", line 926 in __init__
```
self.sidebar = Sidebar(topic)
```
File "/usr/lib64/python2.5/site-packages/gimmie/gimmie_topicwin.py", line 860 in __init__
```
self.add_sources()
```
File "/usr/lib64/python2.5/site-packages/gimmie/gimmie_topicwin.py", line 873 in add_sources
```
for source in self.topic.get_sidebar_source_list():
```
File "/usr/lib64/python2.5/site-packages/gimmie/gimmie_base.py", line 311 in get_sidebar_source_list
```
self.do_reload()
```
File "/usr/lib64/python2.5/site-packages/gimmie/gimmie_computer.py", line 736 in do_reload
```
source_list.append(AdministrationSource())
```
File "/usr/lib64/python2.5/site-packages/gimmie/gimmie_computer.py", line 492 in __init__
```
self.do_reload()
```
File "/usr/lib64/python2.5/site-packages/gimmie/gimmie_computer.py", line 495 in do_reload
```
self.system_settings_menu_source = self.system_settings_menu_tree.get_toplevel_flat_source()
```

AttributeError: 'NoneType' object has no attribute 'get_toplevel_flat_source'

Comment 1 Tony Tsui 2007-04-12 22:41:26 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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