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 451514 - crash in Gimmie: adding to panel
crash in Gimmie: adding to panel
Status: RESOLVED DUPLICATE of bug 419830
Product: gimmie
Classification: Deprecated
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Gimmie Maintainers
Gimmie Maintainers
: 451521 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-06-27 07:56 UTC by njdubois
Modified: 2007-09-08 22:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description njdubois 2007-06-27 07:56:46 UTC
What were you doing when the application crashed?
adding to panel


Distribution: Ubuntu 7.04 (feisty)
Gnome Release: 2.18.1 2007-04-10 (Ubuntu)
BugBuddy Version: 2.18.1

System: Linux 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: UbuntuStudio
Icon Theme: UbuntuStudio

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 ---------------------
Unable to open desktop file file:///home/nick/Desktop/GConf-Editor.desktop for panel launcher: No such file or directory
Unable to open desktop file file:///home/nick/Desktop/gconf-editor.desktop for panel launcher: No such file or directory
Unable to open desktop file file:///home/nick/Desktop/gnomebaker.desktop for panel launcher: No such file or directory
Unable to open desktop file file:///home/nick/Desktop/Wine-Eject-CD.desktop for panel launcher: No such file or directory
Unable to open desktop file file:///home/nick/Desktop/GConf-Editor.desktop for panel launcher: No such file or directory
Unable to open desktop file file:///home/nick/Desktop/gconf-editor.desktop for panel launcher: No such file or directory
Unable to open desktop file file:///home/nick/Desktop/gnomebaker.desktop for panel launcher: No such file or directory
Unable to open desktop file file:///home/nick/Desktop/Wine-Eject-CD.desktop for panel launcher: No such file or directory
Unable to open desktop file file:///home/nick/Desktop/GConf-Editor.desktop for panel launcher: No such file or directory
Unable to open desktop file file:///home/nick/Desktop/gconf-editor.desktop for panel launcher: No such file or directory
Unable to open desktop file file:///home/nick/Desktop/gnomebaker.desktop for panel launcher: No such file or directory
Unable to open desktop file file:///home/nick/Desktop/Wine-Eject-CD.desktop for panel launcher: No such file or directory
Unable to open desktop file file:///home/nick/Desktop/GConf-Editor.desktop for panel launcher: No such file or directory
Unable to open desktop file file:///home/nick/Desktop/gconf-editor.desktop for panel launcher: No such file or directory
Unable to open desktop file file:///home/nick/Desktop/gnomebaker.desktop for panel launcher: No such file or directory
--------------------------------------------------
Traceback (most recent call last):
  • File "/usr/lib/python2.5/site-packages/gimmie/gimmie_gaim.py", line 438 in do_reload
    blist_doc = parse(self.blist_path)
  • File "/usr/lib/python2.5/site-packages/_xmlplus/dom/minidom.py", line 1915 in parse
    return expatbuilder.parse(file)
  • File "/usr/lib/python2.5/site-packages/_xmlplus/dom/expatbuilder.py", line 926 in parse
    result = builder.parseFile(fp)
  • File "/usr/lib/python2.5/site-packages/_xmlplus/dom/expatbuilder.py", line 207 in parseFile
    parser.Parse(buffer, 0)
ExpatError: not well-formed (invalid token): line 718, column 14

Comment 1 André Klapper 2007-07-04 15:37:56 UTC
*** Bug 451521 has been marked as a duplicate of this bug. ***
Comment 2 palfrey 2007-09-08 22:19:27 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 419830 ***