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 350147 - beagle-search cycles through error messages on scroll
beagle-search cycles through error messages on scroll
Status: RESOLVED FIXED
Product: beagle
Classification: Other
Component: General
0.2.6
Other All
: Normal minor
: ---
Assigned To: Beagle Bugs
Beagle Bugs
: 352620 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-08-06 12:02 UTC by Philip Johnson
Modified: 2006-08-24 03:35 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Philip Johnson 2006-08-06 12:02:20 UTC
Please describe the problem:
When beagle-search is opened and no search query has been entered, scrolling the mouse causes the bottom viewport to display the "beagle cannot be ran as root" and  "search service not running" error messages, regardless of the fact that beagle is not being run as root and the search service (beagled) is running.

Searching works correctly regardless of this problem.

Steps to reproduce:
1. Launch beagle-search
2. Hover mouse over bottom viewport to give focus
3. Scroll

Actual results:
beagle-search displays "search service not running" and "beagle cannot be ran as root" error messages.

Expected results:
Quick Tips page to remain static. (ie: nothing)

Does this happen every time?
Yes.

Other information:
Dapper Drake, GNOME 2.14.3
Comment 1 Joe Shaw 2006-08-08 17:59:30 UTC
Hahaha.  Nice one. :)
Comment 2 Kevin Kubasik 2006-08-08 18:10:22 UTC
hehehehe, I say we add a monkey to the end and call it an easter egg :P
Comment 3 Joe Shaw 2006-08-08 18:57:06 UTC
Checked in a fix for this.
Comment 4 Philip Johnson 2006-08-10 09:57:02 UTC
Ah, you see :). Top class and on form as per usual :).
Cheers for the speedy fix!
Comment 5 Joe Shaw 2006-08-24 03:35:12 UTC
*** Bug 352620 has been marked as a duplicate of this bug. ***