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 411426 - crash in Deskbar: typing text into deskbar...
crash in Deskbar: typing text into deskbar...
Status: RESOLVED DUPLICATE of bug 359251
Product: deskbar-applet
Classification: Deprecated
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Deskbar Applet Maintainer(s)
Deskbar Applet Maintainer(s)
: 431071 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-02-24 01:21 UTC by ubuntu
Modified: 2007-04-18 20:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description ubuntu 2007-02-24 01:21:29 UTC 
What were you doing when the application crashed?
typing text into deskbar and it was doing incremental search on my text


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 113391

  • 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


Pedro Villavicencio





          2007-02-24 01:32:29 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 359251 ***






Comment 2


Damien Durand





          2007-04-18 20:33:06 UTC
        



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