GNOME Bugzilla – Bug 352595
crash in Deskbar: The error is quite persi...
Last modified: 2006-08-29 23:15:00 UTC
What were you doing when the application crashed? The error is quite persistent, happens always when searching with beagle-live enabled. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.15.92 2006-08-22 (Ubuntu) BugBuddy Version: 2.15.92 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 70885
self._on_hit_added(query, container, qstring, qmax)
match = BeagleLiveMatch(self, result)
self.result["text"] = self.result["text"].replace("'", "\\'")
*** Bug 352679 has been marked as a duplicate of this bug. ***
*** Bug 352622 has been marked as a duplicate of this bug. ***
*** Bug 352702 has been marked as a duplicate of this bug. ***
*** Bug 352760 has been marked as a duplicate of this bug. ***
*** Bug 352769 has been marked as a duplicate of this bug. ***
*** Bug 352803 has been marked as a duplicate of this bug. ***
This happens consistently for me as well with Beagle Live enabled, whatever the search is. If I disable Beagle Live, it works without crashing
*** Bug 352990 has been marked as a duplicate of this bug. ***
Created attachment 71680 [details] [review] Proposed patch. Entirely untested The problem seems to be that the "text" field is never added to the self.result dict. The attached patch tried to get around this. NOTE: I have not tested this patch at all - can anyone give feedback?
I just applied it and it seems to work fine.
Cool pecanov. At this point in the release process I would like atleast one other confirmation before I commit. Anyone?
The patch seems to work here. Thank you :-)
Created attachment 71750 [details] Backtrace OK, almost: now I have errors in preferences window and while searching. The search error disappears when beagle-live is disabled, preferences error does not and maybe it's unrelated.
Oh, the search crash appeared when I made a search for something that should return a directory with national characters and spaces. Neither the search bug nor the one in preferences window does not happen as long as I search only for things without national characters in their names/urls.
Ok, I committed the patch. Aleksander: The second stack trace is a known bug #352874. However it would be greatly helpful if you could find a way to reproduce the bug. Another thing I might persuade you into doing; could you file a bug about the first stacktrace - the one with the national characters?
Created attachment 71795 [details] [review] The escaped_uri field was not set properly Aleksander: Hold it with the bug filing :-) Make sure you update your cvs to get the last patch and then try this patch, and let me know how it works.
Created attachment 71796 [details] [review] take two The old patch broke beagle-live. If somebody already applied it you can reverse a patch with "patch -R < mypatch.patch", or just delete the broken file and re-update cvs.
*** Bug 353321 has been marked as a duplicate of this bug. ***
*** Bug 353332 has been marked as a duplicate of this bug. ***
*** Bug 353374 has been marked as a duplicate of this bug. ***
*** Bug 353365 has been marked as a duplicate of this bug. ***
Created attachment 71826 [details] Another set of tracebacks OK, almost works, but: the folders open OK. The text files with national characters in file names won't open. The text files with plain-ascii names open, but there are tracebacks in deskbar -w output. Tested both on patched Ubuntu distro and fresh cvs checkout :-) Thanks :> (deskbar no longer fails when searching, and that's really nice :-))
The new patch still seems to crash my deskbar, I get the following Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.15.92 2006-08-22 (Ubuntu) BugBuddy Version: 2.15.92 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 71191
Ricky, did You apply both of the non-obsolete patches? The second one fixes the other problem I mentioned in this bug, but this traceback seems like the problem that I reported first (and which works for me, at least). OTOH, should I submit the national characters problem in another bug? Maybe that's a dumb question, but I'm still a bit shy about this bug-submitting thing :-)
*** Bug 353368 has been marked as a duplicate of this bug. ***
Please keep different issues in different bugs even if slightly related. Thanks for your contributions !
(In reply to comment #24) > Ricky, did You apply both of the non-obsolete patches? The second one fixes the > other problem I mentioned in this bug, but this traceback seems like the > problem that I reported first (and which works for me, at least). No I hadn't - my mistake I misread the comments! With both of the non-obsolete patches it now works fine
*** Bug 353427 has been marked as a duplicate of this bug. ***
*** Bug 353466 has been marked as a duplicate of this bug. ***