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 526836 - crash in Gimmie: Starting GNOME
crash in Gimmie: Starting GNOME
Status: RESOLVED DUPLICATE of bug 499776
Product: gimmie
Classification: Deprecated
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Gimmie Maintainers
Gimmie Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-04-07 22:42 UTC by IanGrey531
Modified: 2008-04-13 15:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description IanGrey531 2008-04-07 22:42:36 UTC
What were you doing when the application crashed?
Starting GNOME


Distribution: Ubuntu 7.10 (gutsy)
Gnome Release: 2.20.1 2007-10-19 (Ubuntu)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: MurrinaUbuntu
Icon Theme: CrystalClear-GNOME-1.0.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



----------- .xsession-errors (10 sec old) ---------------------
(Do:10284): libgnomevfs-WARNING **: Internal error: the configuration system was not initialized. Did you call _gnome_vfs_configuration_init?
(Do:10284): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed
(Do:10284): libgnomevfs-WARNING **: Internal error: the configuration system was not initialized. Did you call _gnome_vfs_configuration_init?
(Do:10284): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed
(Do:10284): libgnomevfs-WARNING **: Internal error: the configuration system was not initialized. Did you call _gnome_vfs_configuration_init?
Could not read Amarok database file: Mono.Data.Sqlite.SqliteException: Unable to open the database file
unable to open database file
  at Mono.Data.Sqlite.Sqlite3.Open (System.String strFilename) [0x00000] 
  at Mono.Data.Sqlite.SqliteConnection.Open () [0x00000] 
Could not read Banshee database file: Unable to open the database file
unable to open database file
--------------------------------------------------
Gimmie Version: 0.3.0

Traceback (most recent call last):
  • File "/usr/local/libexec/gimmie_applet", line 85 in <module>
    import gimmie_applet
  • File "/usr/local/lib/python2.5/site-packages/gimmie/gimmie_applet.py", line 18 in <module>
    from gimmie_library import DocumentsTopic
  • File "/usr/local/lib/python2.5/site-packages/gimmie/gimmie_library.py", line 24 in <module>
    from gimmie_delicious import delicious_source
  • File "/usr/local/lib/python2.5/site-packages/gimmie/gimmie_delicious.py", line 19 in <module>
    picurl = urllib2.urlopen("http://del.icio.us/favicon.ico")
  • File "urllib2.py", line 124 in urlopen
    return _opener.open(url, data)
  • File "urllib2.py", line 381 in open
    response = self._open(req, data)
  • File "urllib2.py", line 399 in _open
    '_open', req)
  • File "urllib2.py", line 360 in _call_chain
    result = func(*args)
  • File "urllib2.py", line 1107 in http_open
    return self.do_open(httplib.HTTPConnection, req)
  • File "urllib2.py", line 1082 in do_open
    raise URLError(err)
URLError: <urlopen error (-2, 'Name or service not known')>

Comment 1 André Klapper 2008-04-13 15:28:33 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 499776 ***