Fedora 31 Final blocker status email #4

[Ben Cotton]

Action summary


Accepted blockers
-
1. mutter — can't turn zoom off once enabled — NEW
ACTION: upstream to fix issue

2. distribution — Cannot upgrade to Fedora 31: package
exa-0.9.0-2.module_f31+5365+04413d87.x86_64 requires
libgit2.so.28()(64bit), but none of the providers can be installed —
NEW
ACTION: dnf team to look at adding output message

3. dnf — Revert skip_if_unavailable default back to true — ASSIGNED
ACTION: everyone to give karma to FEDORA-2019-ded8e6872f

4. gnome-control-center — Gnome Control Center crashes upon a typo in
Printers settings — ASSIGNED
ACTION: upstream to diagnose and fix issue

5. gnome-control-center — Apply button stays gray on Network configuration — NEW
ACTION: upstream to diagnose and fix issue

6. gnome-shell — Automatic workspaces are seriously broken — NEW
ACTION: upstream to fix issue

7. mutter — Keyboard shortcuts NOT mapped to keyboard layouts — NEW
ACTION: upstream to diagnose and fix issue

8. sddm — Cannot start Fedora-KDE-Live (F31) in basic graphics mode on
BIOS machine — NEW
ACTION: upstream to diagnose and fix issue

9. blivet-gui — bios boot partition can't be created at the disk
beginning, if a partition already exists in the middle of the disk —
ASSIGNED
ACTION: maintainer to merge PR #131



Proposed blockers
-

1. gnome-shell — numlock handling is seriously broken — NEW
ACTION: upstream to diagnose and fix issue

2. fwupd — fwupd.service fails to start if /var/cache/fwupd doesn't
exist (e.g. clean install)  — ASSIGNED
ACTION: fwupd maintainer to make the package provide /var/cache/fwupd
(and/or backport patches and request SELinux policy change)

3. grub2 — Newer kernels do not boot and have invalid grub.cfg entries
(on Xen DomU guests) — NEW
ACTION: maintainers/QA/reporter to determine scope of failure

4. vte291 — vte crashes due to out of bounds cursor — MODIFIED
ACTION: QA to verify FEDORA-2019-8288e417ac fixes the issue

Bug-by-bug detail
=

Accepted blockers
-
1. mutter — https://bugzilla.redhat.com/show_bug.cgi?id=1749433 — NEW
can't turn zoom off once enabled

Zoom remains enabled, even after logging out and logging back in.
Upstream issue has identified a commit that appears to be the culprit.
Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/826

2. distribution — https://bugzilla.redhat.com/show_bug.cgi?id=1747408 — NEW
Cannot upgrade to Fedora 31: package
exa-0.9.0-2.module_f31+5365+04413d87.x86_64 requires
libgit2.so.28()(64bit), but none of the providers can be installed

Accepted as a blocker by FESCo, even though it does not affect default
package sets. DNF team is looking at adding an output message that
would address FESCo's short-term concerns. sgallagh has proposed a
longer-term solution.

3. dnf — https://bugzilla.redhat.com/show_bug.cgi?id=1752249 — VERIFIED
Revert skip_if_unavailable default back to true

Update FEDORA-2019-ded8e6872f is confirmed to revert the default
behavior as requested.

4. gnome-control-center —
https://bugzilla.redhat.com/show_bug.cgi?id=1750394 — ASSIGNED
Gnome Control Center crashes upon a typo in Printers settings

Update FEDORA-2019-be95719373 contains a fix that breaks the search
box. This has been reported upstream.
Upstream issue: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/679

5. gnome-control-center —
https://bugzilla.redhat.com/show_bug.cgi?id=1750805 — NEW
Apply button stays gray on Network configuration

Wired network connections cannot be configured because the "apply"
button remains inactive. WiFi configuration works.
Upstream issue: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/677

6. gnome-shell — https://bugzilla.redhat.com/show_bug.cgi?id=1754630 — NEW
Automatic workspaces are seriously broken

There are several regressions in how workspaces behave, probably
related. Upstream has identified a possible culprit commit.
Upstream bug: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1497

7. mutter — https://bugzilla.redhat.com/show_bug.cgi?id=1754373 — NEW
Keyboard shortcuts NOT mapped to keyboard layouts

All shell keyboard shortcuts are broken, except for those where the
keys happen to be in the same position in both the current keyboard
layout and en_US.
Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/822

8. sddm — https://bugzilla.redhat.com/show_bug.cgi?id=1728240 — NEW
Cannot start Fedora-KDE-Live (F31) in basic graphics mode on BIOS machine

This issue only seems to affect BIOS machines when using basic
graphics mode. This appears to be related to an issue encountered in
F30 (RHBZ #1683197).
Upstream issue: https://github.com/sddm/sddm/issues/1204

9. blivet-gui — https://bugzilla.redhat.com/show_bug.cgi?id=1755813 — ASSIGNED
bios boot partition can't be created at the disk beginning, if a
partition already exists in the middle of the disk

blivet tries to place the BIOS boot partition after existing partiions
in certain configurations, which mean

Re: Upgrading from F30 to F31 beta reboot issue

[Chris Murphy]

I suggest trying --debugsolver with both the download and reboot
subcommands. 'man dnf system-upgrade' suggests --debugsolver should
work. I recommend taring the debugdata dir that will create, and
setting the filename and attachment description so it's clear whether
the tarball is for reboot or download.

The debugdata dir will be located in the current dir. So that'll be
easy to find for the download command. But I have no idea where it'll
be located for reboot so you'll probably have to use find.

Sometimes these are bigger than the 20MB attachment size, so you might
have to stick it in a dropbox/googledrive like thing and post the URLs
for them in the bug report.

---
Chris Murphy
___
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: Testing of F31 Workstation beta drop 1003.n.1

[Adam Williamson]

On Fri, 2019-10-04 at 13:28 -0400, pmkel...@frontier.com wrote:
> In regard to my testing of F31 Workstation beta drop 1003.n.1:
> 
> This was a bare metal install on a Lenovo M53 with a i5-4570 CPU. After 
> the ISO was checksummed it was loaded to a thumb drive using Media 
> Writer. The thumb drive was written successfully and then used to boot 
> the test machine. The test machine booted to Live normally and the 
> Install option was selected. Anaconda started normally and the options 
> to delete all and reclaim space were selected for the hard drive. The 
> install ran normally and the reboot to the hard drive was normal.
> 
> I ran several of the standard tests and logged the results with relval.
> 
> There were two failures noted:
> 
> When checking for services start, fwupd did not load. A restart was 
> tried and fwupd still did not load.

This is https://bugzilla.redhat.com/show_bug.cgi?id=1757948 .

> When checking error checks a gnome-shell crash was shown. I must have 
> missed it when it happened. I tried filling a bug using the abrt tool, 
> but after the back trace started, I got a message saying the back trace 
> failed. I haven't seen more gnome-shell crashes.
> 
> In regard to my as deployed tests the following problems were observed:
> 
> Firewall-applet was installed, but after the startup, it quit 
> unexpectedly. When I tried to report the bug with the abrt tool again 
> the back trace failed. Over several restarts I have had no further cases 
> where abrt caught a failure, but the applet is not working. I don't get 
> the connection notification during a startup. System-Monitor shows 
> firewall-applet as a loaded process.

You can try using 'coredumpctl' to get backtraces of the crashed apps,
though it's harder than with abrt. Run 'coredumpctl list' to get a list
of crashes; then run 'coredumpctl gdb ', where  is the pid
associated with one of the crashes, to run gdb on it. You need gdb
installed, obviously. gdb will likely tell you a debuginfo package is
missing and give you a command to install it; quit out of gdb and do
that, then run coredumpctl gdb again, and gdb will tell you a bunch
*more* debuginfos to install. Repeat this cycle till gdb is happy, then
do:

set logging on
thread apply all bt full
c (when prompted)

and a backtrace should be saved to a file gdb.txt in the directory you
ran from.

> I have updates and update notifications disabled for the software 
> application:
> 
> (gsettings set org.gnome.software allow-updates false)
> (gsettings set org.gnome.software download-updates false)
> 
> However, I get a continuing string of notifications that there are 
> important updates to install. when I do (sudo dnf upgrade --refresh) I 
> get (Nothing to do Complete). Updates were run earlier; before I started 
> configuring the system for as deployed testing.

Can you file a bug upstream on this? Thanks! Probably against gnome-
software to start with.

> RHBZ BUG# 1694782 still applies. The authentication popup can not be 
> satisfied, dismissed, or moved.

Yep, I've poked upstream on this one again :/
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
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

Testing of F31 Workstation beta drop 1003.n.1

[pmkel...@frontier.com]

In regard to my testing of F31 Workstation beta drop 1003.n.1:

This was a bare metal install on a Lenovo M53 with a i5-4570 CPU. After 
the ISO was checksummed it was loaded to a thumb drive using Media 
Writer. The thumb drive was written successfully and then used to boot 
the test machine. The test machine booted to Live normally and the 
Install option was selected. Anaconda started normally and the options 
to delete all and reclaim space were selected for the hard drive. The 
install ran normally and the reboot to the hard drive was normal.


I ran several of the standard tests and logged the results with relval.

There were two failures noted:

When checking for services start, fwupd did not load. A restart was 
tried and fwupd still did not load.


When checking error checks a gnome-shell crash was shown. I must have 
missed it when it happened. I tried filling a bug using the abrt tool, 
but after the back trace started, I got a message saying the back trace 
failed. I haven't seen more gnome-shell crashes.


In regard to my as deployed tests the following problems were observed:

Firewall-applet was installed, but after the startup, it quit 
unexpectedly. When I tried to report the bug with the abrt tool again 
the back trace failed. Over several restarts I have had no further cases 
where abrt caught a failure, but the applet is not working. I don't get 
the connection notification during a startup. System-Monitor shows 
firewall-applet as a loaded process.


I have updates and update notifications disabled for the software 
application:


(gsettings set org.gnome.software allow-updates false)
(gsettings set org.gnome.software download-updates false)

However, I get a continuing string of notifications that there are 
important updates to install. when I do (sudo dnf upgrade --refresh) I 
get (Nothing to do Complete). Updates were run earlier; before I started 
configuring the system for as deployed testing.


RHBZ BUG# 1694782 still applies. The authentication popup can not be 
satisfied, dismissed, or moved.


Have a Great Day!

Pat (tablepc)
___
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: Upgrading from F30 to F31 beta reboot issue

[Adam Williamson]

On Fri, 2019-10-04 at 00:31 -0700, Samuel Sieb wrote:
> On 10/3/19 11:30 PM, Rodger Etz wrote:
> > Yes, basically, saving the state is not implemented yet for --reboot and 
> > would fix it.
> > 
> > And it should be fixed, I agree. Although the conditon seems very rare 
> > and existing for quite some time, system-upgrade should behave in a 
> > deterministic way.
> 
> You should file a bug on dnf in bugzilla.  I wonder if it should be a 
> blocker, but it's not clear what the conditions are that trigger it.

Yeah, so far we have a lot of discussion but not (AFAICS) a clear
reproducer or a clear indication of exactly where the bug is. Please do
file a bug, with as much context as you can, including all the logs and
the exact commands you ran. Thanks!
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
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: Upgrading from F30 to F31 beta reboot issue

[Rodger Etz]

Filed against dnf as suggested: 1758588



‐‐‐ Original Message ‐‐‐
On Friday, 4. October 2019 09:31, Samuel Sieb  wrote:

> On 10/3/19 11:30 PM, Rodger Etz wrote:
>
> > Yes, basically, saving the state is not implemented yet for --reboot and
> > would fix it.
> > And it should be fixed, I agree. Although the conditon seems very rare
> > and existing for quite some time, system-upgrade should behave in a
> > deterministic way.
>
> You should file a bug on dnf in bugzilla. I wonder if it should be a
> blocker, but it's not clear what the conditions are that trigger it.
>
> 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

___
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-31-20191004.n.0 compose check report

[Fedora compose checker]

No missing expected images.

Failed openQA tests: 5/153 (x86_64), 1/2 (arm)

New failures (same test not failed in Fedora-31-20191003.n.1):

ID: 463075  Test: x86_64 KDE-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/463075
ID: 463082  Test: x86_64 Silverblue-dvd_ostree-iso desktop_browser
URL: https://openqa.fedoraproject.org/tests/463082

Old failures (same test failed in Fedora-31-20191003.n.1):

ID: 463041  Test: x86_64 Server-dvd-iso modularity_tests
URL: https://openqa.fedoraproject.org/tests/463041
ID: 463054  Test: x86_64 Workstation-live-iso desktop_update_graphical
URL: https://openqa.fedoraproject.org/tests/463054
ID: 463077  Test: arm Minimal-raw_xz-raw.xz 
install_arm_image_deployment_upload
URL: https://openqa.fedoraproject.org/tests/463077
ID: 463088  Test: x86_64 Silverblue-dvd_ostree-iso release_identification
URL: https://openqa.fedoraproject.org/tests/463088

Soft failed openQA tests: 2/153 (x86_64)
(Tests completed, but using a workaround for a known bug)

New soft failures (same test not soft failed in Fedora-31-20191003.n.1):

ID: 463157  Test: x86_64 universal install_arabic_language
URL: https://openqa.fedoraproject.org/tests/463157

Old soft failures (same test soft failed in Fedora-31-20191003.n.1):

ID: 463158  Test: x86_64 universal install_asian_language
URL: https://openqa.fedoraproject.org/tests/463158

Passed openQA tests: 146/153 (x86_64)

New passes (same test not passed in Fedora-31-20191003.n.1):

ID: 463048  Test: x86_64 Workstation-live-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/463048
ID: 463070  Test: x86_64 KDE-live-iso desktop_update_graphical
URL: https://openqa.fedoraproject.org/tests/463070
ID: 463118  Test: x86_64 universal install_blivet_software_raid
URL: https://openqa.fedoraproject.org/tests/463118

Skipped non-gating openQA tests: 1 of 155

Installed system changes in test x86_64 Workstation-live-iso 
install_default_upload: 
System load changed from 0.69 to 0.48
Previous test data: https://openqa.fedoraproject.org/tests/462756#downloads
Current test data: https://openqa.fedoraproject.org/tests/463046#downloads

Installed system changes in test x86_64 KDE-live-iso install_default_upload: 
Used mem changed from 736 MiB to 916 MiB
System load changed from 2.19 to 2.00
Average CPU usage changed from 1.67142857 to 83.09047619
Previous test data: https://openqa.fedoraproject.org/tests/462771#downloads
Current test data: https://openqa.fedoraproject.org/tests/463061#downloads

Installed system changes in test x86_64 KDE-live-iso install_default@uefi: 
Used mem changed from 958 MiB to 726 MiB
1 services(s) removed since previous compose: pcscd.service
System load changed from 1.04 to 0.32
Previous test data: https://openqa.fedoraproject.org/tests/462773#downloads
Current test data: https://openqa.fedoraproject.org/tests/463063#downloads

Installed system changes in test x86_64 Silverblue-dvd_ostree-iso 
install_default@uefi: 
Mount /run/user/1000 contents changed to 87.65591398% of previous size
Previous test data: https://openqa.fedoraproject.org/tests/462789#downloads
Current test data: https://openqa.fedoraproject.org/tests/463079#downloads

Installed system changes in test x86_64 Silverblue-dvd_ostree-iso 
install_default_upload: 
System load changed from 0.09 to 0.22
Previous test data: https://openqa.fedoraproject.org/tests/462790#downloads
Current test data: https://openqa.fedoraproject.org/tests/463080#downloads

Installed system changes in test x86_64 universal install_package_set_kde: 
System load changed from 2.40 to 0.89
Previous test data: https://openqa.fedoraproject.org/tests/462838#downloads
Current test data: https://openqa.fedoraproject.org/tests/463128#downloads
-- 
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

Fedora 31 compose report: 20191004.n.0 changes

[Fedora Branched Report]

OLD: Fedora-31-20191003.n.1
NEW: Fedora-31-20191004.n.0

= SUMMARY =
Added images:0
Dropped images:  0
Added packages:  0
Dropped packages:0
Upgraded packages:   0
Downgraded packages: 0

Size of added packages:  0 B
Size of dropped packages:0 B
Size of upgraded packages:   0 B
Size of downgraded packages: 0 B

Size change of upgraded packages:   0 B
Size change of downgraded packages: 0 B

= ADDED IMAGES =

= DROPPED IMAGES =

= ADDED PACKAGES =

= DROPPED PACKAGES =

= UPGRADED PACKAGES =

= DOWNGRADED PACKAGES =
___
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: Gnome on F31: X and Wayland clipboard weirdness(es)/regressions

[Lukas Ruzicka]

>
>
> It would be of course up to debate. I'm just saying it's a good topic for
> debate.
>
>
Sure, I will buy popcorn and coke :D


-- 

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: Gnome on F31: X and Wayland clipboard weirdness(es)/regressions

[Kamil Paral]

On Fri, Oct 4, 2019 at 12:50 PM Lukas Ruzicka  wrote:

>
>
> Both have been rejected as blockers due to being too "edge case". But
>> pasting into QT applications seems sufficiently broad to be considering as
>> blocking, I think. So if your problems are not related to those two issues
>> (e.g. have a VM running), please file new bugs and feel free to propose
>> them as blockers (or at least mark them as CommonBugs).
>>
>
> I am not sure you would be able to block on this, since no QT applications
> are in standard Workstation installation. As far as I have seen, there is a
> tendency not to block on additional software.
>

It would be of course up to debate. I'm just saying it's a good topic for
debate.
___
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: Gnome on F31: X and Wayland clipboard weirdness(es)/regressions

[Lukas Ruzicka]

Both have been rejected as blockers due to being too "edge case". But
> pasting into QT applications seems sufficiently broad to be considering as
> blocking, I think. So if your problems are not related to those two issues
> (e.g. have a VM running), please file new bugs and feel free to propose
> them as blockers (or at least mark them as CommonBugs).
>

I am not sure you would be able to block on this, since no QT applications
are in standard Workstation installation. As far as I have seen, there is a
tendency not to block on additional software.


-- 

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: Gnome on F31: X and Wayland clipboard weirdness(es)/regressions

[Kamil Paral]

On Thu, Oct 3, 2019 at 3:30 PM Ankur Sinha  wrote:

> Hello,
>
> I ran into an issues with copy/pasting on F31 with the new Gnome 3.34.
> Are these known, or are they expected and if not where should one file
> bugs please?
>
> gnome-shell-3.34.0-3.fc31.x86_64
>
>
> --- Issue 1 
>
> X clipboards cleared when applications closed
>
> Steps to reproduce:
>
> 1. Run gnome with Wayland
> 2. Install xsel and wl-clip to investigate the X and Wayland clipboard
> contents respectively
> 3. Open Gedit and write some text
> 4. Open a terminal (tile them both for ease)
> 5. In gedit copy the text: highlight and right click > copy
> 5. In the terminal, run the following commands:
> 5a. xsel -o (PRIMARY X selection buffer)
> 5b. xsel -o -b (CLIPBOARD X selection buffer)
> 5c. wl-paste (wayland selection buffer)
> 6. Then, close gedit, and re-run these commands.
>
> When gedit is running, the copied text is available to the X and wayland
> clipboards---all commands will show it.
>
> When gedit is closed, the `xsel` commands no longer show any results.
> The contents of the clipboards have been cleared. wl-paste still pastes
> the expected output.
>
> Is this expected behaviour?
>
>
>  Issue 2: cannot yank (copy) from gvim into Qt applications running on
> Gnome 
>
> Note that in the above, we used Gedit which I assume runs on wayland and
> accesses the required wayland clipboard properly.
>
> In the second scenario, if one copies anything from Gvim, it is
> available to the respective X clipboard, and the Wayland clipboard, but
> Qt applications running in Gnome cannot access any of this.
>
> Steps to reproduce:
>
> 1. Run gnome with wayland
> 2. Install xsel and wl-clip to investigate the X and Wayland clipboard
> contents respectively
> 3. Install qutebrowser and/or falkon
> 4. Open a terminal, open qutebrowser and falkon
> 5. Run a new Gvim instance: gvim -u NONE (ensures that no vimrc files are
> read)
> 6. Write two lines of text in Gvim (press i to enter insert mode, write a
> line, hit enter, write another line, press ctrl c to exit insert mode)
> 7. Copy the first line into the X CLIPBOARD selection buffer: go to the
> start of the line, press v to enter visual mode, go to the end of the line
> to highlight it; press "+y to yank to the + register (X CLIPBOARD selection)
> 8. In a terminal, check if this is available:
> 8a. wl-paste: shows copied text
> 8b. xsel -o -b: shows copied text
> 9. Try pasting in falkon or qutebrowser: ctrl v or right click > paste
> (greyed out): nothing shown.
> 10. Copy the second line into the X PRIMARY selection buffer: go to the
> start of the line, press v to enter visual mode, go to the end of the line
> to highlight it; press "*y to yank to the * register (X PRIMARY selection)
> 10a. wl-paste: still shows first line
> 10b. xsel -o -b: shows first line (as expected)
> 10c. xsel -o -p: shows second line (as expected)
> 11. Try pasting in falkon or qutebrowser: ctrl v or right click > paste
> (greyed out): nothing shown.
> 12. Open gedit, write something, copy it, try pasting in Falkon
> 12a. Irrespective of whether gedit remains open or not, the text is
> available the first time I try to paste it, and not any longer.
> 12b. On qutebrowser, though, this remains available, so this is a falkon
> thing/feature
> 12c. wl-paste continues to show this value as many times as you run it.
> 13. Since the x selections are cleared when gedit is closed (issue 1), vim
> cannot access the copied text at all using either the + or * registers
> later.
>
> So:
> - the wayland buffer is synced with the X CLIPBOARD buffer, which is
>  fine: https://wiki.gnome.org/Initiatives/Wayland/PrimarySelection
> - but none of this is available to Qt applications running in Gnome if
>  if it originates from X buffers?
>


Hi, so far I'm aware of these two clipboard-related issues:
https://bugzilla.redhat.com/show_bug.cgi?id=1751646
https://bugzilla.redhat.com/show_bug.cgi?id=1755038

Both have been rejected as blockers due to being too "edge case". But
pasting into QT applications seems sufficiently broad to be considering as
blocking, I think. So if your problems are not related to those two issues
(e.g. have a VM running), please file new bugs and feel free to propose
them as blockers (or at least mark them as CommonBugs).

I have learned that mutter now contains a clipboard manager, that should
keep clipboard contents even after an application is closed (that wasn't
the case before). But I don't know which exact cases it should cover (X11,
Wayland, Wayland<->XWayland). Hopefully some people here from the desktop
list can clarify.
___
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/a

Re: Upgrading from F30 to F31 beta reboot issue

[Samuel Sieb]

On 10/3/19 11:30 PM, Rodger Etz wrote:
Yes, basically, saving the state is not implemented yet for --reboot and 
would fix it.


And it should be fixed, I agree. Although the conditon seems very rare 
and existing for quite some time, system-upgrade should behave in a 
deterministic way.


You should file a bug on dnf in bugzilla.  I wonder if it should be a 
blocker, but it's not clear what the conditions are that trigger it.

___
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: Upgrading from F30 to F31 beta reboot issue

[Samuel Sieb]

On 10/3/19 7:08 PM, Chris Murphy wrote:

Does anyone know if --allow-erasing needs to be passed to both
'download' and 'reboot' subcommands for this to work correctly?

Or does the download subcommand track options and apply them in the
rebooted offline/upgrade environment?


The options must get saved somewhere because I use that often.  You 
don't need to give it to the reboot subcommand.

___
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