Bug 439252 – 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 439252 - crash in Gimmie:


Summary:	crash in Gimmie:


Status:	RESOLVED DUPLICATE of bug 421620

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-05-17 18:28 UTC by reggaemanu
Modified:	2007-05-19 02:36 UTC

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

Description reggaemanu 2007-05-17 18:28:25 UTC

What were you doing when the application crashed?



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-lowlatency #2 SMP PREEMPT Sun Apr 15 07:39:03 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Murrina Deviant
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 (629986 sec old) ---------------------
(gnome-panel:6713): Wnck-WARNING **: Unhandled action type (nil)
(emerald:6811): Wnck-WARNING **: Unhandled action type (nil)
(emerald:6811): Wnck-WARNING **: Unhandled action type (nil)
moving to movies directory filename is /home/manu/.democracy/Movies/Incomplete Downloads/250353.mov.part
new file name is /home/manu/.democracy/Movies/250353.mov
(Gecko:12380): GStreamer-CRITICAL **: gst_bus_source_dispatch: assertion `message != NULL' failed
started)>
database function called from thread <_MainThread(MainThread, started)>
database function called from thread <_MainThread(MainThread, started)>
database function called from thread <_MainThread(MainThread, started)>
database function called from 
...Too much output, ignoring rest...
--------------------------------------------------
Traceback (most recent call last):

+ Trace 134690

File "/usr/lib/python2.5/site-packages/gimmie/gimmie_applet.py", line 516 in do_button_press_event
```
self._show()
```
File "/usr/lib/python2.5/site-packages/gimmie/gimmie_applet.py", line 521 in _show
```
self.topic_win = self.topic.get_topic_window()
```
File "/usr/lib/python2.5/site-packages/gimmie/gimmie_applet.py", line 393 in get_topic_window_mod
```
self.topic_window = TopicMenu(self)
```
File "/usr/lib/python2.5/site-packages/gimmie/gimmie_applet.py", line 251 in __init__
```
self._add_toolbar_items()
```
File "/usr/lib/python2.5/site-packages/gimmie/gimmie_applet.py", line 368 in _add_toolbar_items
```
for i in self.topic.get_toolbar_items(self.tooltips):
```
File "/usr/lib/python2.5/site-packages/gimmie/gimmie_documents.py", line 396 in get_toolbar_items
```
btn = PlacesMenuButton(tooltips)
```
File "/usr/lib/python2.5/site-packages/gimmie/gimmie_documents.py", line 283 in __init__
```
self.set_menu(PlacesMenu())
```
File "/usr/lib/python2.5/site-packages/gimmie/gimmie_documents.py", line 246 in __init__
```
for item in device_source.get_items():
```
File "/usr/lib/python2.5/site-packages/gimmie/gimmie_base.py", line 219 in get_items
```
for i in self.get_items_uncached():
```
File "/usr/lib/python2.5/site-packages/gimmie/gimmie_computer.py", line 217 in get_items_uncached
```
yield DriveItem(drive)
```
File "/usr/lib/python2.5/site-packages/gimmie/gimmie_computer.py", line 106 in __init__
```
raise ValueError, "Cannot find URI to open for drive '%s'" % drive
```

ValueError: Cannot find URI to open for drive '<gnomevfs.Drive object (GnomeVFSDrive) at 0x8a18194>'

Comment 1 Pedro Villavicencio 2007-05-19 02:36:46 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 421620 ***