Bug 410768 - [Regression] Activity in tab does not make tab title highlighted
Summary: [Regression] Activity in tab does not make tab title highlighted
Status: RESOLVED DUPLICATE of bug 410142
Alias: None
Product: konsole
Classification: Applications
Component: tabbar (show other bugs)
Version: master
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-09 14:23 UTC by Konstantin Kharlamov
Modified: 2019-08-09 19:43 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Konstantin Kharlamov 2019-08-09 14:23:16 UTC
SUMMARY

Usually, any new text in non-focused tab causes its title to change color, so you can
see there's something new happened. However on master it stopped working.

STEPS TO REPRODUCE
1. Open Konsole
2. Execute command `ping localhost` (so there's something working)
3. Press Ctrl+Shift+t (that should open a new tab, and make you switch there)
4. Look at the text on the non-focused tab, where ping is running

OBSERVED RESULT

It has the same color as the new tab you're currently in.

EXPECTED RESULT

It should have distinct color that signifies that while you were in another tab, new text appeared.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Archlinux, repro both in Plasma 5.16 and pure i3wm
KDE Plasma Version: 5.16
KDE Frameworks Version: 5.60.0
Qt Version: 5.13.0
Konsole versions tested: commits ac9ccc94 (older) and 0107e68e (latest).
Comment 1 Konstantin Kharlamov 2019-08-09 14:25:22 UTC
Sry, forgot to say: last known working version is  19.04.3
Comment 2 Nate Graham 2019-08-09 15:12:05 UTC
19.04.3 is the last released version. Are you using Konsole from an unreleased repo or compiling it from git master?
Comment 3 Konstantin Kharlamov 2019-08-09 15:13:51 UTC
(In reply to Nate Graham from comment #2)
> 19.04.3 is the last released version. Are you using Konsole from an
> unreleased repo or compiling it from git master?

I use it from Arch repository¹. Why…?

1: https://www.archlinux.org/packages/extra/x86_64/konsole/
Comment 4 Nate Graham 2019-08-09 15:24:58 UTC
(In reply to Konstantin Kharlamov from comment #3)
> I use it from Arch repository¹. Why…?
Because then you're using 19.04.3 (the latest released version), which you've said was known to be working. :)

Please confirm which version you're using and which version it was last working in.
Comment 5 Konstantin Kharlamov 2019-08-09 15:28:43 UTC
(In reply to Nate Graham from comment #4)
> (In reply to Konstantin Kharlamov from comment #3)
> > I use it from Arch repository¹. Why…?
> Because then you're using 19.04.3 (the latest released version), which
> you've said was known to be working. :)
> 
> Please confirm which version you're using and which version it was last
> working in.

Well, yeah, this is probably confusing, by version here I mean "version of binary", as in "the version of binary that's of 19.04.3 version works, and the version of binary that I built from master doesn't". What word should I've used instead? Sorry, I'm not a native speaker.
Comment 6 Nate Graham 2019-08-09 18:11:02 UTC
(In reply to Konstantin Kharlamov from comment #5)
> Well, yeah, this is probably confusing, by version here I mean "version of
> binary", as in "the version of binary that's of 19.04.3 version works, and
> the version of binary that I built from master doesn't". What word should
> I've used instead? Sorry, I'm not a native speaker.
Ah, so the version you compiled from source (git master) has the bug. Thanks!
Comment 7 Konstantin Kharlamov 2019-08-09 19:20:38 UTC
(In reply to Nate Graham from comment #6)
> (In reply to Konstantin Kharlamov from comment #5)
> > Well, yeah, this is probably confusing, by version here I mean "version of
> > binary", as in "the version of binary that's of 19.04.3 version works, and
> > the version of binary that I built from master doesn't". What word should
> > I've used instead? Sorry, I'm not a native speaker.
> Ah, so the version you compiled from source (git master) has the bug. Thanks!

Well, I mentioned it at the beginning and the bottom of the description :)
Comment 8 Christoph Feck 2019-08-09 19:43:38 UTC

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