sort of Rawhide related

[David]

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 Rawhide
on hardware in the past year or two.

I have been using Xfce in Rawhide for over 3 months, and I was
biased against it from the start, so I can not give a fair review.   Fedora
Xfce
just seemed so 2016, even in Rawhide.

The final straw was that Firefox 75 is coming out soon ( with better
wayland improvements ), and I missed wayland. Xfce probably
won't get wayland for a long time.   Right ?

I use a lot of gnome apps ( but in flatpaks ).

One of the first things I do after an install, is play FreeCell in
Aisleriot Solitaire to see if I "feel anything," as I have played this
game about 1,000 times ( maybe 10,000, LOL ! )

Anyways, I updated the packages, turned on the available 3rd party
repo, installed flathub,powered off, installed flatpak of Aisleriot,
rebooted,
just to test reboot, and then played
a game, and here I am. I installed htop ( fc32 ) and, it all looks good
from here.   I surfed the web, watched YouTube.

All is nominal and functional from that perspective.

LibreOffice preinstalled. Utility apps are already all grouped together
so that looks nice.

I am sending this email using this new install.

David Locklear
Novice Rawhide User 0.0.0.5 (  inside joke )

System:  ASUS Mini-ITX Intel i5-3470 with 16 GB of DDR3 at ~ 1,000 MHz
( approximately 5 years old, or more )
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Warning: gnome evolution drop old TLS protocol and you get "Error performing TLS handshake: A packet with illegal or unsupported version was received."

[Dario Lesca]

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 dal mio Linux Fedora 31 Workstation)
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Warning: gnome evolution drop old TLS protocol and you get "Error performing TLS handshake: A packet with illegal or unsupported version was received."

[Michael Cronenworth]

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
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Did you lost you wayland too?

[Paul Dufresne via test]

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 or it only offers the GNOME X11 session but names it as 
"GNOME", so you don't know.


I did open a new bug on lightdm: 
https://bugzilla.redhat.com/show_bug.cgi?id=1821790


___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Fedora 32 compose report: 20200407.n.0 changes

[Fedora Branched Report]

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 of upgraded packages:   3.11 GiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   -212.80 MiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =

= DROPPED IMAGES =
Image: LXQt live x86_64
Path: Spins/x86_64/iso/Fedora-LXQt-Live-x86_64-32-20200406.n.0.iso

= ADDED PACKAGES =
Package: ghc-path-io-1.4.2-1.fc32
Summary: Interface to ???directory??? package for users of ???path???
RPMs:ghc-path-io ghc-path-io-devel ghc-path-io-doc ghc-path-io-prof
Size:1.36 MiB

Package: python-pysmt-0.8.0-2.fc32
Summary: Solver-agnostic library for SMT Formulae manipulation and solving
RPMs:python3-pysmt
Size:370.49 KiB


= DROPPED PACKAGES =
Package: mutter328-3.28.4-7.fc32
Summary: Window and compositing manager based on Clutter
RPMs:mutter328 mutter328-devel mutter328-libs mutter328-tests
Size:17.30 MiB


= UPGRADED PACKAGES =
Package:  Zim-0.72.1-1.fc32
Old package:  Zim-0.72.0-2.fc32
Summary:  Desktop wiki & notekeeper
RPMs: Zim
Size: 1.70 MiB
Size change:  2.33 KiB
Changelog:
  * Sun Mar 29 2020 Robin Lee  - 0.72.1-1
  - Update to 0.72.1


Package:  aircrack-ng-1.6-1.fc32
Old package:  aircrack-ng-1.5.2-8.fc32
Summary:  802.11 (wireless) sniffer and WEP/WPA-PSK key cracker
RPMs: aircrack-ng aircrack-ng-devel aircrack-ng-doc
Added RPMs:   aircrack-ng-devel aircrack-ng-doc
Size: 6.01 MiB
Size change:  -9.17 MiB
Changelog:
  * Tue Jan 28 2020 Fedora Release Engineering  - 
1.5.2-9
  - Rebuilt for https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild

  * Mon Apr 06 2020 Vitaly Zaitsev  - 1.6-1
  - Resurrected package.
  - Updated to version 1.6.
  - Performed SPEC cleanup.


Package:  anaconda-32.24.5-1.fc32
Old package:  anaconda-32.24.4-1.fc32
Summary:  Graphical system installer
RPMs: anaconda anaconda-core anaconda-dracut anaconda-gui 
anaconda-install-env-deps anaconda-live anaconda-tui anaconda-widgets 
anaconda-widgets-devel
Size: 19.26 MiB
Size change:  8.98 KiB
Changelog:
  * Fri Apr 03 2020 Martin Kolman  - 32.24.5-1
  - Don't clear errors by expanding pages in the custom spoke (vponcova)
  - Fix the permission for changing a mount point (#1818500) (vponcova)
  - Allow to use an existing unlocked LUKS in one special case (#1772902)
(vponcova)
  - Fix the encryption checkbox in the custom spoke (#1819360) (vponcova)
  - Don't manually trigger a device encryption change (vponcova)
  - Rename _test_dbus_property to _check_dbus_property (jkonecny)


Package:  astrometry-0.78-6.fc32
Old package:  astrometry-0.78-5.fc32
Summary:  Blind astrometric calibration of arbitrary astronomical images
RPMs: astrometry astrometry-data astrometry-data-4204 
astrometry-data-4205 astrometry-data-4206 astrometry-data-4207 astrometry-devel 
astrometry-libs python3-astrometry
Size: 1.77 GiB
Size change:  -57.43 KiB
Changelog:
  * Tue Jan 28 2020 Fedora Release Engineering  - 
0.78-6
  - Rebuilt for https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild


Package:  astrometry-tycho2-2.0-8.fc32
Old package:  astrometry-tycho2-2.0-6.fc31
Summary:  Tycho-2 catalogue for astrometry.net
RPMs: astrometry-tycho2
Size: 812.71 MiB
Size change:  -205.05 MiB
Changelog:
  * Tue Jan 28 2020 Fedora Release Engineering  - 
2.0-7
  - Rebuilt for https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild

  * Sun Mar 29 2020 Mattia Verga  - 2.0-8
  - Temporarily disable s390 due to astrometry dependency


Package:  atk-2.36.0-1.fc32
Old package:  atk-2.35.1-2.fc32
Summary:  Interfaces for accessibility support
RPMs: atk atk-devel
Size: 2.61 MiB
Size change:  25.60 KiB
Changelog:
  * Thu Apr 02 2020 Kalev Lember  - 2.36.0-1
  - Update to 2.36.0


Package:  boost-1.69.0-15.fc32
Old package:  boost-1.69.0-14.fc32
Summary:  The free peer-reviewed portable C++ source libraries
RPMs: boost boost-atomic boost-build boost-chrono boost-container 
boost-context boost-contract boost-coroutine boost-date-time boost-devel 
boost-doc boost-doctools boost-examples boost-fiber boost-filesystem 
boost-graph boost-graph-mpich boost-graph-openmpi boost-iostreams boost-jam 
boost-locale boost-log boost-math boost-mpich boost-mpich-devel 
boost-mpich-python3 boost-mpich-python3-devel boost-numpy3 boost-openmpi 
boost-openmpi-devel boost-openmpi-python3 boost-openmpi-python3-devel 
boost-program-options boost-python3 boost-python3-devel boost-random 
boost-regex boost-serialization boost-stacktrace boost-static boost-system 
boost-test boost-thread boost-timer boost-type_erasure boost-wave
Size: 310.18 MiB
Size ch

Re: Warning: gnome evolution drop old TLS protocol and you get "Error performing TLS handshake: A packet with illegal or unsupported version was received."

[Dario Lesca]

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)
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Warning: gnome evolution drop old TLS protocol and you get "Error performing TLS handshake: A packet with illegal or unsupported version was received."

[Dario Lesca]

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 are already disabled by default

-- 
Dario Lesca
(inviato dal mio Linux Fedora 31 Workstation)
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Warning: gnome evolution drop old TLS protocol and you get "Error performing TLS handshake: A packet with illegal or unsupported version was received."

[Rex Dieter]

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/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 know how to configure this file for change the default system-
> wide ?

See if this helps:
https://fedoraproject.org/wiki/Changes/StrongCryptoSettings#Upgrade.2Fcompatibility_impact

-- Rex
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Warning: gnome evolution drop old TLS protocol and you get "Error performing TLS handshake: A packet with illegal or unsupported version was received."

[Michael Cronenworth]

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 know how to configure this file for change the default system-wide ?


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.


Instead of looking for ways to enable TLS 1.0/1.1 you should engage with your 
provider to offer TLS 1.2 or 1.3.



[1] https://fedoraproject.org/wiki/Changes/StrongCryptoSettings2
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Warning: gnome evolution drop old TLS protocol and you get "Error performing TLS handshake: A packet with illegal or unsupported version was received."

[Dario Lesca]

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 change the settings. I do not know whether it has any user-
> level setting, apart of the environment variable you found.

Someone know how to configure this file for change the default system-
wide ?

Thanks

-- 
Dario Lesca
(inviato dal mio Linux Fedora 31 Workstation)
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Did you lost you wayland too?

[Kamil Paral]

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 systemctl disable gdm; reboot
>
> 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 or
it only offers the GNOME X11 session but names it as "GNOME", so you don't
know.
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Warning: gnome evolution drop old TLS protocol and you get "Error performing TLS handshake: A packet with illegal or unsupported version was received."

[Dario Lesca]

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:%COMPAT:+VERS-TLS1.0" evolution

but  It's bette advise all.

Thanks


-- 
Dario Lesca
(inviato dal mio Linux Fedora 31 Workstation)
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Suggest a new criterion for Suspend.

[Ben Cotton]

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 option. So we
don't care which hardware specifically, but the general impact. Is it
1% of hardware? We probably don't want to block on it. Is it 10% of
hardware? That might be more compelling. Is it 100% of hardware? Yeah,
this is a blocker. Obviously we can't use specific numbers, but
focusing on the scale of the impact the idea.

Do we want to scope it specifically to desktop-oriented deliverables?
Suspending Workstation or the KDE Spin is probably a common use case.
Suspending Server less so. I don't expect there would be cases where
that would actually matter, since they should share the important
parts in common, but if nothing else, it reduces the number of tests
that need to be done.

-- 
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Fedora-IoT-32-20200407.0 compose check report

[Fedora compose checker]

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 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.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Did you lost you wayland too?

[Paul Dufresne via test]

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?
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Suggest a new criterion for Suspend.

[Lukas Ruzicka]

> 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
> hardware?
>
> Peter
>

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.
Concerning a VM, I was not able to suspend the VM, it only stopped
responding and it needed to be restarted to make it work again, the state
was not kept. So, according to the criterion, suspend was not working.




>
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>


-- 

Lukáš Růžička

FEDORA QE, RHCE

Red Hat



Purkyňova 115

612 45 Brno - Královo Pole

lruzi...@redhat.com
TRIED AND PERSONALLY TESTED, ERGO TRUSTED. 
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Suggest a new criterion for Suspend.

[Peter Robinson]

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://bugzilla.redhat.com/show_bug.cgi?id=1816621.
> Some of our team, me included, believe that it should be an *independent*
> criterion (not part of Login, Reboot, Power Off) and it should be targeted
> to *Final*.
>
> This is the suggestion of the criterion, please comment if you like to
> patch it or have other suggestions, too.
>
>  Criterion 
> Suspend to RAM
>
> Suspending the machine must work using the standard console commands and
> the mechanisms offered by all release-blocking desktops.
>
> Work?
> The machine must be able to suspend, keeping the current state of all
> running applications and the operating system itself. When awoken,
> everything must be restored to its original state. Suspend must work
> repetitiously.
>

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
hardware?

Peter
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Suggest a new criterion for Suspend.

[Lukas Ruzicka]

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 included, believe that it should be an *independent*
criterion (not part of Login, Reboot, Power Off) and it should be targeted
to *Final*.

This is the suggestion of the criterion, please comment if you like to
patch it or have other suggestions, too.

 Criterion 
Suspend to RAM

Suspending the machine must work using the standard console commands and
the mechanisms offered by all release-blocking desktops.

Work?
The machine must be able to suspend, keeping the current state of all
running applications and the operating system itself. When awoken,
everything must be restored to its original state. Suspend must work
repetitiously.



-- 

Lukáš Růžička

FEDORA QE, RHCE

Red Hat



Purkyňova 115

612 45 Brno - Královo Pole

lruzi...@redhat.com
TRIED AND PERSONALLY TESTED, ERGO TRUSTED. 
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Fedora-Cloud-31-20200407.0 compose check report

[Fedora compose checker]

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.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Did you lost you wayland too?

[Kamil Paral]

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@localhost ~]$
>

This:
$ echo $XDG_SESSION_TYPE
will give you either `x11` or `wayland` depending on your session type.


>
> The about in Gnome settings give: Windowing System: X11 ... but I am
> pretty sure I am logged under Gnome, not Gnome Classics or on Xorg.
>

You can select that using the bottom right icon before confirming your
password. If you log in as "GNOME" (meaning Wayland), but you get X11, then
the answer is probably somewhere in the logs. There are certain cases where
wayland isn't available and it falls back to X11. E.g. when using nvidia
binary drivers.
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Fedora-Cloud-30-20200407.0 compose check report

[Fedora compose checker]

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.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org