On 24/11/2021 06:06, John Pilkington wrote:
I'm used to reading messages in order of time of arrival. Threaded display in
Thunderbird, or the presentation of the archive by Hyperkitty, doesn't do this;
the current thread about NVIDIA drivers is utterly disjointed in both, with
recent posts bu
On 11/23/21 9:19 PM, Tim via users wrote:
Other people manage to do this, why can't you? (That's a generic
"everyone else" you question, I'm not referencing you John.)
Because nobody ever taught them how to do it and they don't know how to
learn things like that on their own.
___
On Tue, 2021-11-23 at 22:06 +, John Pilkington wrote:
> I'm used to reading messages in order of time of arrival. Threaded
> display in Thunderbird, or the presentation of the archive by
> Hyperkitty, doesn't do this; the current thread about NVIDIA drivers
> is utterly disjointed in both, w
On Tue, 2021-11-23 at 12:58 -0600, Roger Heflin wrote:
> This is the magic decoder ring web page. The most recent cards that
> I think were kicked out are anything with a GK* in the code name
> (kepler). So any kepler cards seem to stop at 470.X. And GF*
> stopped a while ago at 340 I think. I
John,
On 2021-11-24 09:06, John Pilkington wrote:
I'm used to reading messages in order of time of arrival. Threaded
display in Thunderbird, or the presentation of the archive by
Hyperkitty, doesn't do this; the current thread about NVIDIA drivers
is utterly disjointed in both, with recent pos
On 23/11/2021 22:26, Samuel Sieb wrote:
On 11/23/21 14:06, John Pilkington wrote:
I'm used to reading messages in order of time of arrival. Threaded
display in Thunderbird, or the presentation of the archive by
Hyperkitty, doesn't do this; the current thread about NVIDIA drivers
is utterly di
On 11/23/21 13:02, Tim Evans wrote:
OK, looks like I'm good with version 470xx
$ lspci | grep -i nvidia
01:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT
730] (rev a1)
$ rpm -qa | grep akmod-nvidia
akmod-nvidia-470xx-470.82.00-1.fc35.x86_64
So, to repeat my question ab
On 24/11/2021 05:02, Tim Evans wrote:
On 11/23/21 13:58, Roger Heflin wrote:
This is the magic decoder ring web page. The most recent cards that I
think were kicked out are anything with a GK* in the code name
(kepler). So any kepler cards seem to stop at 470.X. And GF*
stopped a while ago at
On 11/23/21 14:06, John Pilkington wrote:
I'm used to reading messages in order of time of arrival. Threaded
display in Thunderbird, or the presentation of the archive by
Hyperkitty, doesn't do this; the current thread about NVIDIA drivers is
utterly disjointed in both, with recent posts burie
I'm used to reading messages in order of time of arrival. Threaded
display in Thunderbird, or the presentation of the archive by
Hyperkitty, doesn't do this; the current thread about NVIDIA drivers is
utterly disjointed in both, with recent posts buried at random partway
up the display. Is th
HI All,
FC35
Xfce 4.16
virt-viewer-10.0-4.fc35.x86_64
Is there a way to switch virt-viewer's decorations
from its current dark theme to a light or different
theme?
Many thanks,
-T
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe
On 11/23/21 13:58, Roger Heflin wrote:
This is the magic decoder ring web page. The most recent cards that I
think were kicked out are anything with a GK* in the code name
(kepler). So any kepler cards seem to stop at 470.X. And GF*
stopped a while ago at 340 I think. If your card just stopp
On Sat, Nov 6, 2021 at 2:12 PM Matthew Saltzman wrote:
>
> I have a Lenovo Yoga X1 (2nd generation), on which I was happily
> running a dual boot of the original Windows 10 installation that came
> with the machine and Fedora 34, which I had upgraded through a few
> versions of Fedora.
>
> This ti
I have try to start a VM from a iso live Fedora 35 Workstation and the
problem with libreoffice still exist.
https://i.imgur.com/twOVYi2.png
I have not install fedora, only try and simple open Libreoffice and the
font into font selection menu are wreid
Is this a know issue?
Many thanks
Dario
I
Il giorno mar, 23/11/2021 alle 10.18 -0500, Tom Horsley ha scritto:
> On Tue, 23 Nov 2021 11:10:43 -0400
> George N. White III wrote:
>
> > You should compare the
> > font settings between the two systems.
>
> Or at least the list of installed fonts on the two systems
>
> rpm -q -a | fgrep font
This is the magic decoder ring web page. The most recent cards that I
think were kicked out are anything with a GK* in the code name
(kepler). So any kepler cards seem to stop at 470.X. And GF*
stopped a while ago at 340 I think. If your card just stopped working
it is probably a GK* variant c
Il giorno mar, 23/11/2021 alle 18.13 +0100, Ulf Volmer ha scritto:
> The issue with the torborwser is handled at
>
> https://gitlab.torproject.org/tpo/applications/tor-browser-build/-
> /issues/40382
>
> There is also a workaround described
Thank, this work around work for torbrowser:
Modify
On Tue, Nov 23, 2021 at 1:22 PM Roger Heflin wrote:
>
> Just to confuse things, there are at least 2 very different Variants
> of GeForce GT 730's. One is based on Kepler and I know is
> supported by 470.x(GK208B), and there is an older one that probably
> needs 340(GF108).
Roger,
I know, a
Just to confuse things, there are at least 2 very different Variants
of GeForce GT 730's. One is based on Kepler and I know is
supported by 470.x(GK208B), and there is an older one that probably
needs 340(GF108).
I have been studying the nvidia cards to sort out which ones do x264
encoding an
On 23.11.21 14:47, Dario Lesca wrote:
On my Notebook with Fedora 34 up to date (also on 35 new installation
on VM) some application show part of your text message with weird font
like this:
Torbrowser: https://i.imgur.com/7FRv4Xu.png
Libreoffice: https://i.imgur.com/9tkRqwH.png
The issue with
On 23/11/2021 14:17, Tim Evans wrote:
On 11/22/21 19:32, Ed Greshko wrote:
Actually, the exclude was needed when the akmod-nvidia-340xx package
was in the rpmfusion-nonfree-updates-testing. Without the
exclude the akmod-nvidia-340xx would get downgraded to the broken
version.
I just removed
Unfortunately, I can't find any "raop" support in the Fedora repos.
Thanks very much for getting me this far.
On 11/22/21 11:46 PM, Samuel Sieb wrote:
On 11/22/21 21:32, Samuel Sieb wrote:
Pulseaudio has support for sending to airplay(2). You need to load
the raop(2) module and your airplay d
On Tue, 23 Nov 2021 11:10:43 -0400
George N. White III wrote:
> You should compare the
> font settings between the two systems.
Or at least the list of installed fonts on the two systems
rpm -q -a | fgrep font
should get you a list.
___
users mailing
On Tue, 23 Nov 2021 at 09:47, Dario Lesca wrote:
> On my Notebook with Fedora 34 up to date (also on 35 new installation on
> VM) some application show part of your text message with weird font like
> this:
>
> Torbrowser: https://i.imgur.com/7FRv4Xu.png
> Libreoffice: https://i.imgur.com/9tkRqwH
On 11/22/21 19:32, Ed Greshko wrote:
Actually, the exclude was needed when the akmod-nvidia-340xx package was
in the rpmfusion-nonfree-updates-testing. Without the
exclude the akmod-nvidia-340xx would get downgraded to the broken version.
I just removed the exclude from my configuration which
On my Notebook with Fedora 34 up to date (also on 35 new installation
on VM) some application show part of your text message with weird font
like this:
Torbrowser: https://i.imgur.com/7FRv4Xu.png
Libreoffice: https://i.imgur.com/9tkRqwH.png
On another PC with Fedora 34 up to date like my notebook
26 matches
Mail list logo
