strange screen tearing effect
by Tim
Since updating to Fedora 26, I get a strange screen tearing effect on
any moving image (scrolling webpages, watching live video, anything
that moves). The effect is unnoticeable on static displayes. The
effect is like this diagram:
http://imgbox.com/TqED2C76
There's a portion at the top of the screen related to one moment in
time, with a dividing line going across the screen, related to another
moment. The really strange thing is that there's a diagonal portion to
this division.
The division slowly rolls down the screen, so it can be seen that the
screen refresh rate is different from the source material (whatever it
may be).
According to driconf, which offers options I know nothing about, and
offers nothing I see related to setting any vertical sync options, the
graphics set is using: NV98 (nouveau)
The display configurator (I'm using Mate) gives me 60 or 75 Hz refresh
rates, and they will change the rate that the dividing line rolls down
the screen, but not eliminate it.
I'm using a LCD screen connected through a DVI cable (both ends, no
conversions). Mate's display configurator says its DVI-I
How can I get rid of this?
--
[tim@localhost ~]$ uname -rsvp
Linux 4.13.5-200.fc26.x86_64 #1 SMP Thu Oct 5 16:53:13 UTC 2017 x86_64
Boilerplate: All mail to my mailbox is automatically deleted.
There is no point trying to privately email me, I only get to see
the messages posted to the mailing list.
Using Windows software is like coating all your handtools with sewage.
3 years, 11 months
- 3
- 5
FW update from gnome-softwares
by Jeandet Alexis
Hello,
Today I got for the first time a dell Precision 5520 and I saw the
firmware(EFI) update from gnome softwares, this is AWESOME!
I hope more vendors will push their fw in the near future :).
Thanks guys,
Alexis.
3 years, 11 months
- 2
- 2
Re: f26 to f26 cups sharing problem
by tar＠sonic.net
>Take that entry out of the hosts file, then try "ping liberty.local".
>Does it work? If not, then make sure you have the "nss-mdns" package
>installed.
Well this seems to be on the right track(mdns issue).
I removed the ".local" line from /etc/hosts .
The nss-mdns package is installed, so I decided to test it as suggested in
the README.
On the client, testing for the client address
getent hosts rights.local
returns
192.168.1.4 rights.local
Great, that's what we want fromnss-mdns, so now lets test for the server
address:
getent hosts liberty.local
... times out with no response and returns a status code of 2.
Which seems to match the timeout from "cups-browsed -v"
If I skip the ".local" we get
getent hosts rights
192.168.1.4 rights.localdomain rights
.. correct for the client
getent hosts liberty
192.168.1.6 liberty.localdomain liberty
.. correct for the server
And since this all depends on /etc/nsswitch.conf, the relevant line there is
hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname
I also confirmed that avahi-daemon is running on the client
and that firewalld has mdns allowed (client and server).
Thanks for the good lead, this seems to be the problem area, any ideas on
next things to try/investigate?
3 years, 11 months
- 2
- 1