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 526525 - crash in Gimmie: loggin in through gdm
crash in Gimmie: loggin in through gdm
Status: RESOLVED DUPLICATE of bug 422739
Product: gimmie
Classification: Deprecated
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Gimmie Maintainers
Gimmie Maintainers
: 526526 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-04-06 15:45 UTC by elkalle
Modified: 2008-04-13 14:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description elkalle 2008-04-06 15:45:59 UTC 
What were you doing when the application crashed?
loggin in through gdm


Distribution: Gentoo Base System release 1.12.11.1
Gnome Release: 2.20.3 2008-03-04 (Gentoo)
BugBuddy Version: 2.20.1

System: Linux 2.6.24-gentoo-r4 #2 SMP PREEMPT Sun Apr 6 13:10:09 CEST 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Aurora-looks
Icon Theme: nuoveXT.2.2

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 ---------------------
FOUND: /home/carl/.screenlets/CircleClock/themes/default
UPDATING SHAPE
Restored instances from session 'default' ...
Compositing method changed to True
UPDATING SHAPE
UPDATING SHAPE
/home/carl/.themes/Schwermetall/gtk-2.0/gtkrc:218: Unable to locate image file in pixmap_path: "Toolbar/toolbar.png"
/home/carl/.themes/Schwermetall/gtk-2.0/gtkrc:221: Background image options specified without filename
/home/carl/.themes/Schwermetall/gtk-2.0/gtkrc:864: Unable to locate image file in pixmap_path: "Scrollbars/slider-vert-insens.png"
/home/carl/.themes/Schwermetall/gtk-2.0/gtkrc:872: Background image options specified without filename
/home/carl/.themes/Schwermetall/gtk-2.0/gtkrc:1262: Unable to locate image file in pixmap_path: "Buttons/button_gray.png"
/home/carl/.themes/Schwermetall/gtk-2.0/gtkrc:1265: Background image options specified without filename
/home/carl/.themes/Schwermetall/gtk-2.0/gtkrc:1563: Unable to locate image file in pixmap_path: "Buttons/button-normal.png"
/home/carl/.themes/Schwermetall/gtk-2.0/gtkrc:1567: Background image options specified without filename
UPDATING SHAPE
--------------------------------------------------
Gimmie Version: 0.2.8

Traceback (most recent call last):

+ Trace 194401

  • File "/usr/lib64/python2.5/site-packages/gimmie/gimmie_applet.py", line 684 in gimmie_applet_factory 
    GimmieApplet(applet, iid)
  • File "/usr/lib64/python2.5/site-packages/gimmie/gimmie_applet.py", line 620 in __init__ 
    btn = TopicButtonMod(topic, applet, self.prefs)
  • File "/usr/lib64/python2.5/site-packages/gimmie/gimmie_applet.py", line 464 in __init__ 
    self._button_style_pref_changed(prefs)
  • File "/usr/lib64/python2.5/site-packages/gimmie/gimmie_applet.py", line 480 in _button_style_pref_changed 
    icon = icon_factory.load_image (icon, 18)
  • File "/usr/lib64/python2.5/site-packages/gimmie/gimmie_util.py", line 463 in load_image 
    pixbuf = self.load_icon(icon_value, icon_size, force_size)
  • File "/usr/lib64/python2.5/site-packages/gimmie/gimmie_util.py", line 416 in load_icon 
    assert icon_value, "No icon to load!"
AssertionError: No icon to load! 






Comment 1


André Klapper





          2008-04-13 14:49:17 UTC
        



*** Bug 526526 has been marked as a duplicate of this bug. ***






Comment 2


André Klapper





          2008-04-13 14:52:49 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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