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 384598 - crash in Deskbar: I'm typing: gai then, cr...
crash in Deskbar: I'm typing: gai then, cr...
Status: RESOLVED DUPLICATE of bug 355687
Product: deskbar-applet
Classification: Deprecated
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Deskbar Applet Maintainer(s)
Deskbar Applet Maintainer(s)
: 406587 429729 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-12-11 03:11 UTC by Xie Yanbo
Modified: 2007-04-14 19:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Xie Yanbo 2006-12-11 03:11:25 UTC 
What were you doing when the application crashed?
I'm typing: gai
then, crash.


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):

+ Trace 93195

  • 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


André Klapper





          2006-12-14 02:15:46 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 355687 ***






Comment 2


Damien Durand





          2007-02-11 08:16:45 UTC
        



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






Comment 3


Damien Durand





          2007-04-14 19:06:37 UTC
        



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