Bug 138867

Summary: View window scrolls to top with new log entry.
Product: [Fedora] Fedora Reporter: Kim Lux <lux>
Component: system-logviewerAssignee: Paul Nasrat <nobody+pnasrat>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3Keywords: FutureFeature
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 19:06:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Kim Lux 2004-11-11 18:06:43 UTC
Description of problem: 
 
Request that System Log screen doesn't go to top every time a new 
event is added. 
 
Version-Release number of selected component (if applicable): 
 
Log Viewer 0.9.11 
 Copyright (c) 2002-2004 Red Hat, Inc. 
 Copyright (c) 2002-2004 Tammy Fox <tfox> 
 A graphical interface for watching log files 
 
 
How reproducible: 
 
All the time. 
 
 
Steps to Reproduce: 
 
1. Open system-logviewer 
 
2. Scroll down to the bottom of the list to see the last entry.  
 
3. System generates a message.  View window goes to the top of 
thelist. 
   
Actual results: 
 
User is looking at the first item in the list.  
 
Expected results: 
 
It would be nice if the list stayed on the last item or went to the 
new item.  Maybe a user option is needed to scroll list or not scroll 
list.  If one is working on a busy machine, it is almost impossible 
to look at anything in the middle of the list because it keeps going 
to the top of the list and then you have to refind your position.  
 
 
Additional info: 
 
I like the utility a lot.  I used to have several log files open at 
once in multiple editors and they didn't update while you were 
watching them.  system-logviewer is much, much nicer.  
 
I'd also like a button to clear the log file, but I guess I can do 
that manually.

Comment 1 Chris Lumens 2004-11-19 18:38:41 UTC

*** This bug has been marked as a duplicate of 122451 ***

Comment 2 Red Hat Bugzilla 2006-02-21 19:06:56 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.