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 544713 - crash in Deskbar: just click top and botto...
crash in Deskbar: just click top and botto...
Status: RESOLVED DUPLICATE of bug 490981
Product: deskbar-applet
Classification: Deprecated
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Deskbar Applet Maintainer(s)
Deskbar Applet Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2008-07-25 15:47 UTC by ruslylove
Modified: 2008-07-26 12:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description ruslylove 2008-07-25 15:47:10 UTC 
What were you doing when the application crashed?
just click top and bottom


Distribution: Ubuntu 8.04 (hardy)
Gnome Release: 2.22.2 2008-06-03 (Ubuntu)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-19-generic #1 SMP Fri Jul 11 23:41:49 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Human
Icon Theme: Human

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

Traceback (most recent call last):

+ Trace 203776

  • File "/usr/lib/python2.5/site-packages/deskbar/ui/preferences/DeskbarPreferences.py", line 427 in on_button_down_clicked 
    self.module_list.move_module_down(iter)
  • File "/usr/lib/python2.5/site-packages/deskbar/core/ModuleList.py", line 162 in move_module_down 
    iter_next = self.iter_next(iter)
TypeError: iter should be a GtkTreeIter 






Comment 1


Sebastian Pölsterl





          2008-07-26 12:02:16 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 490981 ***