Bug 1384624

Sorry for the delay.  I somehow overlooked this bug.  Anyway, this does not seem to be related to coreutils.  It must be some issue with graphics card driver, or your hardware.

On a second look, this bug is very similar to bug #1320681.  Were you able to identify/resolve the root cause of the other bug?

Kamil,

I'm on FC 25 now so I changed the system level above to 25.

The problem was solved time ago, I think... several years ago. It comes back frequently and I file a new bug report.

I'm sorry to disagree with you about where "tty" comes from but dnf says:

dnf provides /usr/bin/tty 
Last metadata expiration check: 2:01:25 ago on Tue Nov 22 09:49:37 2016.
coreutils-8.25-15.fc25.x86_64 : A set of basic GNU tools commonly used in shell scripts
Repo        : @System

coreutils-8.25-14.fc25.x86_64 : A set of basic GNU tools commonly used in shell scripts
Repo        : fedora

coreutils-single-8.25-14.fc25.x86_64 : coreutils multicall binary
Repo        : fedora

coreutils-8.25-15.fc25.x86_64 : A set of basic GNU tools commonly used in shell scripts
Repo        : updates

coreutils-single-8.25-15.fc25.x86_64 : coreutils multicall binary
Repo        : updates

(In reply to George R. Goffe from comment #3)
> I'm sorry to disagree with you about where "tty" comes from but dnf says:

Yes, the /usr/bin/tty binary comes from coreutils but it is completely unrelated to your problem.  tty(1) is a tiny utility that prints file name of the terminal connected to standard input.  It does not implement a tty, neither any rendering of terminal's output on your graphics device.

Kamil,

So, who "owns" this code?

Some time ago I wrote a bug on this code because the password prompt as entered by the user was displaying the password in clear text. It seems to me that something is "turning off" the intensity of the data for the first (top) few lines.

You say, this isn't you... then, who?

Regards,

George...

The login prompt is implemented in /sbin/agetty which belongs to util-linux.  But it does not implement any font rendering directly.  It just communicates through a character device provided by kernel.

Kamil,

Thanks for your help. Can you transfer this bug to them please?

Regards,

George...

Sure, moving to kernel...

Please provide details about the graphics card HW and driver you are using.

(In reply to Kamil Dudka from comment #8)
> Please provide details about the graphics card HW and driver you are using.

... and also details about your (external?) display.  Some LCD panels tend to dim backlight if the scene being rendered is mostly dark.  Some of them allow to disable this feature.

*********** MASS BUG UPDATE **************
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 25 kernel bugs.
 
Fedora 25 has now been rebased to 4.9.3-200.fc25.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26.
 
If you experience different issues, please open a new bug report for those.

Laura,

It looks like I missed the "need info" flag for this one. Can you give me commands that would/might provide the info requested please?

Regards,

George...

The needinfo in this case is just a general 'is the problem still occuring'. If the problem is still occuring, please give information about your graphics (lspci should be a good start).

This system is an ASUS N53SN-RH71 (Laptop), Physical display is Samsung TV (27") driven via the HDMI port.

00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])                                                                                                                           
        Subsystem: ASUSTeK Computer Inc. Device 1712                                                                                         
        Flags: bus master, fast devsel, latency 0, IRQ 11                                                                                    
        Memory at dc400000 (64-bit, non-prefetchable) [size=4M]                                                                              
        Memory at b0000000 (64-bit, prefetchable) [size=256M]                                                                                
        I/O ports at e000 [size=64]                                                                                                          
        [virtual] Expansion ROM at 000c0000 [disabled] [size=128K]                                                                           
        Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-                                                                           
        Capabilities: [d0] Power Management version 2
        Capabilities: [a4] PCI Advanced Features
        Kernel modules: i915


01:00.0 VGA compatible controller: NVIDIA Corporation GF108M [GeForce GT 550M] (rev a1) (prog-if 00 [VGA controller])
        Subsystem: ASUSTeK Computer Inc. Device 1712
        Flags: fast devsel, IRQ 11
        Memory at db000000 (32-bit, non-prefetchable) [disabled] [size=16M]
        Memory at c0000000 (64-bit, prefetchable) [disabled] [size=256M]
        Memory at d0000000 (64-bit, prefetchable) [disabled] [size=32M]
        I/O ports at d000 [disabled] [size=128]
        Expansion ROM at dc000000 [disabled] [size=512K]
        Capabilities: [60] Power Management version 3
        Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [78] Express Endpoint, MSI 00
        Capabilities: [b4] Vendor Specific Information: Len=14 <?>
        Capabilities: [100] Virtual Channel
        Capabilities: [128] Power Budgeting <?>
        Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?>
        Kernel modules: nouveau

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 25 kernel bugs.

Fedora 25 has now been rebased to 4.10.9-200.fc25.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26.

If you experience different issues, please open a new bug report for those.

*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the 
relevant data from the latest kernel you are running and any data that might have been requested previously.

Justin,

Sorry I missed the need info flag...

The problem still happens AND with either KDE or WindowMaker and seems to be geometry related.

The tty problem still happens.

The "with window manager" seems to be geometry related. I make a fully maximized konsole and enter the clear command. This shows the problem... after 3 or so lines, the screen brightens.

With Konsole corner dragged, max height, width dragged to fill the screen shows the problem when approximately 85% of the screen is covered.

I can NOT get a screen snapshot to show the problem.

I'm on FC 27 (rawhide) now and am STILL having this problem.

The Samsung "monitor" is a 27" TV.

Need other info?

George...

George, as you describe the problem, it seems like a feature of your Samsung TV:  if the scene being displayed is mostly dark, the TV dims the back light to make the black parts of the scene more black.  This feature could be optional, please check your TV's manual.

Kamil,

I have fiddled with the config of the TV and seem to have eliminated the problem.

I will watch the situation and report any difficulties.

I guess you can close this one now?

MANY thanks for your help,

George...

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.

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.