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 765556 - Highlighting and output showing issues
Highlighting and output showing issues
Status: RESOLVED INVALID
Product: gnome-terminal
Classification: Core
Component: general
3.20.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-04-25 19:06 UTC by Inactive account
Modified: 2016-10-24 09:41 UTC
See Also:
GNOME target: ---
GNOME version: 3.19/3.20


Attachments
gnome-terminal_16-04_Execute_Invisible_Output_Issue.png (85.01 KB, image/png)
2016-04-25 19:06 UTC, Inactive account
Details
gnome-terminal_16-04_Execute_Shown_Output_Issue.png (84.44 KB, image/png)
2016-04-25 19:07 UTC, Inactive account
Details
gnome-terminal_16-04_Highlighting_Issue1.png (116.34 KB, image/png)
2016-04-25 19:07 UTC, Inactive account
Details
gnome-terminal_16-04_Highlighting_Issue2.png (241.50 KB, image/png)
2016-04-25 19:08 UTC, Inactive account
Details

Description Inactive account 2016-04-25 19:06:36 UTC
Created attachment 326707 [details]
gnome-terminal_16-04_Execute_Invisible_Output_Issue.png

I have noticed that on Ubuntu GNOME 16.04 with GNOME 3.20 that often when I execute a command although the cursor goes to the right place and still blinks as it should the output is not shown until I press Enter once more:

    gnome-terminal_16-04_Execute_Invisible_Output_Issue.png

    gnome-terminal_16-04_Execute_Shown_Output_Issue.png

I have also noticed that often when clicking and dragging to select text though when I copy and paste it somewhere else I can see that all the text was really selected, it doesn't show all the text to be selected (it is normally much more extreme with many more lines missing the highlighting than shown here though):

    gnome-terminal_16-04_Highlighting_Issue1.png

I have also noticed that if I select text but then move my mouse the other way some of the text doesn't get unselected as it should:

    gnome-terminal_16-04_Highlighting_Issue2.png

Don't let the fact that the screenshots are from my Ubuntu (Unity) 16.04 VM confuse you though, the same happens on my GNOME one, I just had my Unity one open at the time when I wanted to take the sreenshots.

I initially reported this bug here but thought I should also do so upstream: https://bugs.launchpad.net/ubuntu-gnome/+bug/1574810
Comment 1 Inactive account 2016-04-25 19:07:07 UTC
Created attachment 326708 [details]
gnome-terminal_16-04_Execute_Shown_Output_Issue.png
Comment 2 Inactive account 2016-04-25 19:07:46 UTC
Created attachment 326709 [details]
gnome-terminal_16-04_Highlighting_Issue1.png
Comment 3 Inactive account 2016-04-25 19:08:29 UTC
Created attachment 326710 [details]
gnome-terminal_16-04_Highlighting_Issue2.png
Comment 4 Christian Persch 2016-04-25 19:16:21 UTC
Can you repro the issue with a pristine gnome-terminal (i.e. sans the the transparency patch that ubuntu applies, and without any ubuntu gtk modules (like overlay scrollbar)), on the default theme (Adwaita) ?
Comment 5 Inactive account 2016-04-25 19:44:51 UTC
Yes, I can.
Comment 6 Egmont Koblinger 2016-04-26 11:04:40 UTC
> on Ubuntu GNOME 16.04 with GNOME 3.20

Could you please clarify what version of gnome-terminal, vte, Gtk+, GNOME etc. you have and from where? (I'm asking because Ubuntu 16.04 ships GNOME 3.18.)

Do the display glitches get fixed when you change the window manager focus to another window?
Comment 7 Inactive account 2016-04-26 14:31:37 UTC
Here is the information you requested:

gnome-terminal version: 3.20.0-0ubuntu1~xenial1
vte version: 0.44.1
GTK+ version: 3.20.3-0ubuntu1~xenial0

I have got them from (though this is the same with GNOME 3.18 from the standard and official repositories) the gnome3 and gnome3-staging PPAs maintained by the GNOME3 LaunchPad team: https://launchpad.net/~gnome3-team

And yes, most often when mousing over the bits that are highlighted wrong or clicking on another window mostly (if not completely) fix them. However this does not apply to the times when I execute code and the output is not properly shown if at all, then the only thing which will fix that seems to be pressing Enter.
Comment 8 Christian Persch 2016-04-26 15:38:51 UTC
> gnome-terminal version: 3.20.0-0ubuntu1~xenial1

That's not a pristine upstream version; it contains the whole boatload of ubuntu patches.
Comment 9 Inactive account 2016-04-26 15:40:35 UTC
I know, but I have also tested it with an official upstream version which I compiled manually.
Comment 10 Egmont Koblinger 2016-04-26 16:07:49 UTC
Given that:

- you see multiple different kinds of corruptions (if it was a vte/g-t bug then it'd be multiple independent bugs);
- nothing relevant changed recently (at least definitely not until 0.42.x);
- we haven't had such bugreports for about two years now;
- according to my best knowledge, vte completely repaints on focus in/out, yet it doesn't always fix it for you;

I suspect that it's a way lower level issue (probably the video driver; maybe, but in my opinion less likely: X or Gtk+).
Comment 11 Christian Persch 2016-05-08 08:54:34 UTC
All the screenshots are from ubuntu with the weird scrollbar etc so hard to tell what exactly is wrong...

If this also happens with vte 0.42 (gnome-terminal 3.18), then it's probably some X/gtk/whatever issue.

If it doesn't happen with 0.42 but does happen with 0.44, it *might* be a bug introduced in the refactoring. If so, is this reproducible in the vte-2.91 test app using upstream gtk and upstream vte (no ubuntu patches or gtk modules), using default theme? Then please use git bisect to find the first broken commit.
Comment 12 Egmont Koblinger 2016-05-08 08:58:33 UTC
(In reply to Christian Persch from comment #11)
> All the screenshots are from ubuntu with the weird scrollbar

Note that Ubuntu no longer uses its own weird overlay scrollbar module, but changed to Gtk+'s stock solution.
Comment 13 Inactive account 2016-10-24 09:34:13 UTC
This bug appears to no longer be present on 3.20 nor 3.22.