GNOME Bugzilla – Bug 500153
crash in Deskbar:
Last modified: 2007-11-28 17:59:13 UTC
What were you doing when the application crashed? Distribution: Unknown Gnome Release: 2.20.1 2007-11-01 (FreeBSD GNOME Project) BugBuddy Version: 2.20.1 System: FreeBSD 7.0-BETA2 FreeBSD 7.0-BETA2 #39: Fri Nov 9 10:17:40 MSK 2007 root@vbook.fbsd.ru:/usr/obj/usr/src/sys/VBOOK i386 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: gnome 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 ----------- .xsession-errors (4754 sec old) --------------------- SIM-IM: 28/11/2007 10:27:27 [DBG] Ack message SIM-IM: 28/11/2007 10:27:27 [DBG] Ack: 242963272 87794623 (175821274) SIM-IM: 28/11/2007 10:27:27 [DBG] Plugin info request 175821274 (6) SIM-IM: 28/11/2007 10:27:27 [DBG] Level: 0E5A [09C4 0014] SIM-IM: 28/11/2007 10:27:28 [DBG] Ack message SIM-IM: 28/11/2007 10:27:28 [DBG] Ack: 1622107984 904347229 (175821274) SIM-IM: 28/11/2007 10:27:29 [DBG] 175821274 unknown cap 0xd3 0xd4 0x53 0x19 0x8b 0x32 0x40 0x3b 0xac 0xc7 0xd1 0xa9 0xe2 0xb5 0x81 0x3e SIM-IM: 28/11/2007 10:27:29 [DBG] Plugin info request 175821274 (5) SIM-IM: 28/11/2007 10:27:29 [DBG] Level: 0DE6 [09C4 0014] SIM-IM: 28/11/2007 10:27:29 [DBG] Ack message SIM-IM: 28/11/2007 10:27:29 [DBG] Ack: 1214904087 672031380 (175821274) SIM-IM: 28/11/2007 10:27:29 [DBG] Plugin info request 175821274 (6) SIM-IM: 28/11/2007 10:27:29 [DBG] Level: 0D3B [09C4 0014] ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 179926
cell.set_property ("has-more-actions", len(match.get_actions()) > 1)
I've did: <Meta><Enter> - to call applet (it is hotkey) enter word in input <Meta><Enter> - tu submit (instead of enter) *crash*
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 471672 ***