Bug 229905 - gnome-system-log: copy copies wrong lines when log is filtered
gnome-system-log: copy copies wrong lines when log is filtered
Product: Fedora
Classification: Fedora
Component: gnome-utils (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ray Strode [halfline]
Depends On:
  Show dependency treegraph
Reported: 2007-02-23 21:04 EST by Scott Douglass
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-06-25 19:50:00 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Scott Douglass 2007-02-23 21:04:14 EST
Description of problem:
With a filter applied, the text copied from the gnome-system-log log viewing
window is not the text selected.

Version-Release number of selected component (if applicable):

How reproducible:
Every time.

Steps to Reproduce:
1.Open the gnome-system-log application.
2.View /var/log/messages.
3.Enable the filter, and enter "kernel" in the filter input widget.
4.Copy some lines from the log and paste them into gedit.
5.Be surprised when what you see is not what you selected in gnome-system-log.
Actual results:
Copies lines of the log file that are not the ones selected.

Expected results:
Expected to copy visibily selected lines from the particular log.

Additional info:
Comment 1 Julian Sikorski 2007-06-21 06:45:15 EDT
Still present in f7, gnome-utils-1:2.18.1-1.fc7. My guess is that the line
numbers are taken from filterd output, but absolute ones are copied.
Comment 2 Matthias Clasen 2007-06-21 09:53:04 EDT
Corresponding upstream bug: http://bugzilla.gnome.org/show_bug.cgi?id=343215
Comment 3 Julian Sikorski 2007-06-21 09:57:51 EDT
Shall we close this one as upstream then?
Comment 4 Matthias Clasen 2007-06-25 19:50:00 EDT
We could certainly do that, since I doubt that we are going to fix this
independent from upstream.

Note You need to log in before you can comment on or make changes to this bug.