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 405385 - unpack non-sequence
unpack non-sequence
Status: RESOLVED DUPLICATE of bug 366656
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: 2007-02-07 15:03 UTC by Cristobal M. Palmer
Modified: 2007-02-07 20:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Cristobal M. Palmer 2007-02-07 15:03:01 UTC
What were you doing when the application crashed?
trying to launch gcalc-tool


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.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

Traceback (most recent call last):
  • File "/usr/lib/python2.4/site-packages/deskbar/ui/cuemiac/CuemiacTreeView.py", line 292 in __get_match_icon_for_cell
    qstring, match_obj = match
TypeError: unpack non-sequence

Comment 1 Damien Durand 2007-02-07 20:00:21 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 366656 ***
Comment 2 Cristobal M. Palmer 2007-02-07 20:55:23 UTC
Firstly, the bug you point to is marked as a dupe 355687.

Secondly, it would've been nice if you'd pointed to a version of deskbar that fixes the bug. I have a fully-updated edgy system, which shows:

cmpalmer@kant:~$ dpkg -l deskbar-applet|grep ^ii
ii  deskbar-applet 2.16.0-0ubuntu4 keyword-driven navigational bar for GNOME

I'll go pester the ubuntu folk about what update will fix this, since I can't seem to find a bug in their tracker that matches 355687. I'm just hoping you'll keep in mind that fairly non-technical users may use bug buddy and include an email. If you close a bug like this with nothing more than a pointer to another bug, that kind of user will throw up his/her hands and be lost.

Thanks,
CMP