Bug 1320681

How is this related to the coreutils package?

How are you confirming this is a software problem at all?

Kamil,

Thanks for your response.

1) I believe that the tty binary comes from core utils. Yes?

2) the problem comes and goes, and has crossed Fedora version boundaries... even with different hardware.

Thanks,

George...

Kamil,

How can you just close this bug without even waiting for my information?

Here's what dnf says about /usr/bin/tty.

dnf provides /usr/bin/tty
Last metadata expiration check: 0:29:45 ago on Wed Mar 23 12:49:34 2016.
coreutils-8.24-6.fc23.x86_64 : A set of basic GNU tools commonly used in shell scripts
Repo        : @System

coreutils-8.24-4.fc23.x86_64 : A set of basic GNU tools commonly used in shell scripts
Repo        : fedora

coreutils-8.24-6.fc23.x86_64 : A set of basic GNU tools commonly used in shell scripts
Repo        : updates

I have not closed the bug.

Anyway, I fail to see how the issue could be related to the tty binary.  It is just a utility that prints name of the terminal connected to standard input.

Please provide details about your HW, kernel and the graphics driver in use.

Kamil,

You raise an interesting point. I had assumed that this was the device driver for the device. Let me see under which circumstances I get this behavior. It just might be a specific piece of software using the device. I'll post here if/when I find something.

I jumped to the conclusion that since this bug is listed as "NOTABUG" below with a "resolved as" status, that you had closed the bug.

I apologize for the misfire.

Thanks for your help and time.

George...


lspci reports:


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]
   Expansion ROM at <unassigned> [disabled]
   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

I agree with Kamil - I don't see any connection with tty utility - although it can't be ruled out. I think terminal is more likely than coreutils - what terminal do you use? We can reassign it there, as terminal maintainer may have other ideas how to better debug this issue.

Ondrej/Kamil,

Thank you so much for your help.

I use Konsole about 99% of the time and was not able to produce the problem with the various utilities I use (more/less/cat/vi) although I think I've seen it with the boot console and the virtual consoles (i.e., ctrl-f2). I was able to create the problem with xterm though but the characteristics of the problem are different.

I'm not sure just where this one should go.

Again, thanks for your help AND time,

George...

Just to be clear, you have tried different physical displays and it had no impact on the issue, right?

I see you have two graphics cards installed.  Could you please check which of them is used when the problem occurs?

Have you tried to switch the primary display to the other graphics card?

Kamil,

1) right.
2) I'm not sure how to tell which card is in use. I would presume that the Nvidia card is for the laptop screen since this is a "gamer" laptop so the Samsung is the other card. Yes?
3) I only use the Samsung

Let me try switching to the laptop display as primary. I'll report here.

Again, Thanks, 

George...

(In reply to George R. Goffe from comment #9)
> 2) I'm not sure how to tell which card is in use.

For Xorg, the info should be available in /var/log/Xorg.0.log.  I am not sure about the native tty, probably the output of dmesg should give some hints.

> I would presume that the
> Nvidia card is for the laptop screen since this is a "gamer" laptop so the
> Samsung is the other card. Yes?

Samsung?  I though the other graphics card was Intel.

Kamil,

You're right... I chose the wrong word. Intel -> Samsung.

After some testing I have discovered software that changes the "brightness" of the tty or whatever I'm using. It's a full screen editor. I'm trying to contact the maintainer. The problem appears EVERYWHERE.

Thank you so much for all your time and patience with me. This bug can be "really" closed.

Thanks again,

George...

Ok, thanks for information, closing NOTABUG based on that.