Bug 1401184 - Konsole scrolls to the bottom on mouse selection when workspace was switched
Summary: Konsole scrolls to the bottom on mouse selection when workspace was switched
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: konsole
Version: 25
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-03 11:20 UTC by Martin Ueding
Modified: 2017-12-12 10:56 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:56:53 UTC
Type: Bug


Attachments (Terms of Use)

Description Martin Ueding 2016-12-03 11:20:55 UTC
Description of problem:

    I use Awesome WM and have a bunch of Konsole windows open on various
    workspaces. Often I have large amounts of output (GCC errors) and need to
    scroll up to find the first actual error. I then mark that with the mouse,
    copy it into the clipboard. Then I go to some other workspace, paste that
    and go back to the workspace with Konsole.

    At that point I would like to select some text in the vicinity of the
    previous selection. When I click into the window, it jumps to the bottom
    again. This is starting to drive me nuts because I then have to push
    Shift+PgUp many times again to find the same spot.

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

    16.08.2

How reproducible:

    always

Steps to Reproduce:

    1. Open a Konsole window.
    2. Create a lot of output such that you can scroll. Scroll up.
    3. Switch to another workspace and back again.
    4. Try to select some text.

Actual results:

    Scrolling jumps to the bottom again.

Expected results:

    No jumping at all. If I want to go down again, I press a button or scroll
    there manually with Shift+End.

Additional info:

    Fedora 24, all updates installed.

    Konsole theme has everything except the text window disabled, no scrollbar,
    no menu bar, no tab bar.

Comment 1 Martin Ueding 2016-12-06 15:45:57 UTC
This bug is still present in Fedora 25 as well. The version of Konsole has not changed, 16.08.2, so this is not a surprise.

Comment 2 Fedora End Of Life 2017-11-16 19:33:26 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2017-12-12 10:56:53 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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