GNOME Bugzilla – Bug 359251
qstring, match_obj = match TypeError: unpack non-sequence
Last modified: 2007-07-29 13:02:30 UTC
What were you doing when the application crashed? 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 74238
qstring, match_obj = match
*** Bug 359252 has been marked as a duplicate of this bug. ***
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 ***
*** Bug 359591 has been marked as a duplicate of this bug. ***
*** Bug 359666 has been marked as a duplicate of this bug. ***
*** Bug 360469 has been marked as a duplicate of this bug. ***
*** Bug 361123 has been marked as a duplicate of this bug. ***
*** Bug 361164 has been marked as a duplicate of this bug. ***
This bug is not a dupe of bug 355687 although it may look like it. I need a way to reproduce this...
Marking needinfo
*** Bug 361291 has been marked as a duplicate of this bug. ***
Quote from bug 361291 comment 2: It seems that error occurs when deskbar has button layout and History option enabled. I clean my history and disable History option. The error disappears, i can't reproduce it anymore. I have Ubuntu Edgy Eft Beta, may be my deskbar history references to some uninstalled applications. By example, I had tomcat5 in Dapper Drake... now I have tomcat5.5. Couple weeks ago, I tried execute xchat from deskbar. Xchat was not installed in my box that time... however, i could see a mistaken xchat reference in history and it was the first error... I hope this information about deskbar history option be useful.
Ok. Thanks Karsten and cpauquez. Technical stuff, You've been warned: It strikes me that it might just be some specific handler returning a non-pair as match. Maybe this happens in the history handler under some circumstances, maybe other handlers too... Anyway, I'll look a bit into this...
Just a technical status update: Handlers returning non-pairs is not the problem. It works fine if they do, we account for such behavior elsewhere.
*** Bug 361750 has been marked as a duplicate of this bug. ***
*** Bug 361677 has been marked as a duplicate of this bug. ***
*** Bug 361693 has been marked as a duplicate of this bug. ***
*** Bug 362258 has been marked as a duplicate of this bug. ***
*** Bug 362315 has been marked as a duplicate of this bug. ***
Mikkel: have you any idea ? I would like to release a fix for this one, given the number of dupes..
I cannot reproduce. If someone can provide me the exact steps to get this error it will be appreciated
Created attachment 74948 [details] [review] Debugging aid/workaround Patch to aid the debugging of this in the future.
*** Bug 363926 has been marked as a duplicate of this bug. ***
*** Bug 363922 has been marked as a duplicate of this bug. ***
*** Bug 363921 has been marked as a duplicate of this bug. ***
*** Bug 364057 has been marked as a duplicate of this bug. ***
*** Bug 365087 has been marked as a duplicate of this bug. ***
*** Bug 365215 has been marked as a duplicate of this bug. ***
*** Bug 365163 has been marked as a duplicate of this bug. ***
*** Bug 365795 has been marked as a duplicate of this bug. ***
*** Bug 360560 has been marked as a duplicate of this bug. ***
*** Bug 365856 has been marked as a duplicate of this bug. ***
*** Bug 366029 has been marked as a duplicate of this bug. ***
*** Bug 366053 has been marked as a duplicate of this bug. ***
I applied Debugging aid patch id=74948 but have not had a single crash since clearing history.
*** Bug 366513 has been marked as a duplicate of this bug. ***
*** Bug 366517 has been marked as a duplicate of this bug. ***
I applied the workaround in 2.16 and HEAD. I removed the debugging Exception, since it will annoy users heavily and generate 100's of bug buddy reports anywy. I print an error in the console if this cause some weird behavior so we get the debug nonethelss
FWIW: This issue came up again (this time I had the patch installed) Once again, it went away when i cleared the history. BugBuddy output below: 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 81573
raise Exception ("Match object of unexpected type: %s", match.__class__)
Cool, so we know this is caused by history, and the thing returns None for some reasons. Reopening !
*** Bug 370276 has been marked as a duplicate of this bug. ***
*** Bug 370748 has been marked as a duplicate of this bug. ***
29 duplicates in the last 30 days, gnome 2.16.x blocker. raphael, any progress?
*** Bug 373212 has been marked as a duplicate of this bug. ***
*** Bug 374634 has been marked as a duplicate of this bug. ***
*** Bug 375807 has been marked as a duplicate of this bug. ***
I still cannot reproduce, and no-one gave me a way to reproduce this easily. In the meantime i have a workaround that suppress the error window, but this suppress only the symptom, not the cause.
*** Bug 377669 has been marked as a duplicate of this bug. ***
*** Bug 383794 has been marked as a duplicate of this bug. ***
*** Bug 386271 has been marked as a duplicate of this bug. ***
*** Bug 386737 has been marked as a duplicate of this bug. ***
*** Bug 387507 has been marked as a duplicate of this bug. ***
4 duplicates within the last 30 days => removing gnome-target milestone, does not seem to be important enough to me.
*** Bug 397923 has been marked as a duplicate of this bug. ***
*** Bug 394875 has been marked as a duplicate of this bug. ***
*** Bug 395057 has been marked as a duplicate of this bug. ***
*** Bug 400937 has been marked as a duplicate of this bug. ***
*** Bug 396454 has been marked as a duplicate of this bug. ***
*** Bug 403048 has been marked as a duplicate of this bug. ***
*** Bug 405010 has been marked as a duplicate of this bug. ***
*** Bug 408159 has been marked as a duplicate of this bug. ***
*** Bug 411318 has been marked as a duplicate of this bug. ***
*** Bug 411426 has been marked as a duplicate of this bug. ***
*** Bug 430504 has been marked as a duplicate of this bug. ***
*** Bug 430763 has been marked as a duplicate of this bug. ***
*** Bug 430765 has been marked as a duplicate of this bug. ***
*** Bug 434504 has been marked as a duplicate of this bug. ***
*** Bug 437978 has been marked as a duplicate of this bug. ***
*** Bug 446566 has been marked as a duplicate of this bug. ***
Raphael tells me it should be fixed now. Please reopen if it happens with deskbar >= 2.18.0.
*** Bug 461344 has been marked as a duplicate of this bug. ***