I am a novice user of Fedora Rawhide.
Today, I did a fresh new clean install ( on an cheap old SSD ) of Rawhide
as my only operating system.
I used the nightly compose finder, and chose "Workstation live"
for X86_64, using the last good iso "20200325."
This was probably my 5th time to install Ra
Il giorno mar, 07/04/2020 alle 13.43 -0500, Michael Cronenworth ha
scritto:
> On 4/7/20 12:30 PM, Dario Lesca wrote:
> > I use Fedora 32 ... and the TLS 1.0/1.1 are already disabled by
> > default
>
> Please file a bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1821934
--
Dario Lesca
(inviato
On 4/7/20 12:30 PM, Dario Lesca wrote:
I use Fedora 32 ... and the TLS 1.0/1.1 are already disabled by default
Please file a bug.
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Le 20-04-07 à 12 h 07, Kamil Paral a écrit :
On Tue, Apr 7, 2020 at 2:39 PM Paul Dufresne via test
mailto:test@lists.fedoraproject.org>>
wrote:
In lightdm, I do have 'Gnome' selected... so... is it a lightdm bug?
I have no idea. Lightdm either doesn't support starting Wayland
sessions o
OLD: Fedora-32-20200406.n.0
NEW: Fedora-32-20200407.n.0
= SUMMARY =
Added images:0
Dropped images: 1
Added packages: 2
Dropped packages:1
Upgraded packages: 46
Downgraded packages: 0
Size of added packages: 1.72 MiB
Size of dropped packages:17.30 MiB
Size
Il giorno mar, 07/04/2020 alle 12.01 -0500, Rex Dieter ha scritto:
> See if this helps:
> https://fedoraproject.org/wiki/Changes/StrongCryptoSettings#Upgrade.2Fcompatibility_impact
Yes, this help.
Thank
--
Dario Lesca
(inviato dal mio Linux Fedora 31 Workstation)
__
Il giorno mar, 07/04/2020 alle 11.35 -0500, Michael Cronenworth ha
scritto:
> Since you are posting to the test list I am assuming you are using
> Fedora Rawhide (33). You would be affected by the upcoming Change[1]
> that disables TLS 1.0/1.1 by default.
I use Fedora 32 ... and the TLS 1.0/1.1 ar
Dario Lesca wrote:
> Il giorno mar, 07/04/2020 alle 16.46 +0200, Dario Lesca ha scritto:
>> There is a work around:
>>
>> $ G_TLS_GNUTLS_PRIORITY="NORMAL:%COMPAT:+VERS-TLS1.0" evolution
>
> On evolution ML Milan say that:
>
>> the protocols are disabled system-wide.
>> Read (and edit) the /etc
On 4/7/20 11:28 AM, Dario Lesca wrote:
On evolution ML Milan say that:
the protocols are disabled system-wide.
Read (and edit) the /etc/crypto-policies/config
file to change the settings. I do not know whether it has any user-
level setting, apart of the environment variable you found.
Someone
Il giorno mar, 07/04/2020 alle 16.46 +0200, Dario Lesca ha scritto:
> There is a work around:
>
> $ G_TLS_GNUTLS_PRIORITY="NORMAL:%COMPAT:+VERS-TLS1.0" evolution
On evolution ML Milan say that:
> the protocols are disabled system-wide.
> Read (and edit) the /etc/crypto-policies/config
> file to
On Tue, Apr 7, 2020 at 2:39 PM Paul Dufresne via test <
test@lists.fedoraproject.org> wrote:
> I fond my Wayland back by doing:
>
> sudo systemctl disable lightdm ; sudo systemctl enable gdm ; reboot
>
> And I can loose Wayland again by doing the opposite:
>
> sudo systemctl enable lightdm; sudo s
If you use a old server without TLS 1.2 enable, you get:
"Error performing TLS handshake: A packet with illegal or unsupported
version was received."
See:
https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1735837.html
There is a work around:
$ G_TLS_GNUTLS_PRIORITY="NORMAL:%CO
On Tue, Apr 7, 2020 at 7:55 AM Lukas Ruzicka wrote:
>
> Yes, we are aware that suspend is hardware dependent and we might end up
> blocking on a particular set of hardware once we are able to identify such a
> set. Any ideas are welcome.
I think a "squishy" approach here might be the best optio
No missing expected images.
Failed openQA tests: 1/8 (x86_64)
Old failures (same test failed in Fedora-IoT-32-20200406.0):
ID: 569478 Test: x86_64 IoT-dvd_ostree-iso base_services_start
URL: https://openqa.fedoraproject.org/tests/569478
Passed openQA tests: 7/8 (x86_64)
--
Mail generated
I fond my Wayland back by doing:
sudo systemctl disable lightdm ; sudo systemctl enable gdm ; reboot
And I can loose Wayland again by doing the opposite:
sudo systemctl enable lightdm; sudo systemctl disable gdm; reboot
In lightdm, I do have 'Gnome' selected... so... is it a lightdm bug?
_
> The problem with this is how do you answer the question on which hardware?
> Suspend is very hardware dependent and even to the point of what devices
> are plugged into it could affect it's ability to suspend. So would that be
> just a requirement for suspend work on a VM, or a particular set of
On Tue, Apr 7, 2020 at 12:35 PM Lukas Ruzicka wrote:
> Hello friends,
> yesterday, during the Blocker Review Meeting we decided to suggest a
> blocking criterion for suspending the system, because it would clarify the
> situations where to accept a blocker like the one from yesterday
> https://bu
Hello friends,
yesterday, during the Blocker Review Meeting we decided to suggest a
blocking criterion for suspending the system, because it would clarify the
situations where to accept a blocker like the one from yesterday
https://bugzilla.redhat.com/show_bug.cgi?id=1816621.
Some of our team, me i
No missing expected images.
Passed openQA tests: 1/1 (x86_64)
--
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproj
On Mon, Apr 6, 2020 at 9:58 PM Paul Dufresne via test <
test@lists.fedoraproject.org> wrote:
> I don't understand, I lost wayland on F32!
>
> [paul@localhost ~]$ echo $GDMSESSION
> gnome
> [paul@localhost ~]$ echo $XDG_CURRENT_DESKTOP
> GNOME
> [paul@localhost ~]$ echo $WAYLAND_DISPLAY
>
> [paul@l
No missing expected images.
Passed openQA tests: 1/1 (x86_64)
--
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproj
21 matches
Mail list logo
