Bug 2252182 - wl-clipboard exit with error in micro editor (in wayland)
Summary: wl-clipboard exit with error in micro editor (in wayland)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: wl-clipboard
Version: 39
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Marc-Andre Lureau
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-11-30 02:12 UTC by Misha Blanchet
Modified: 2024-01-31 02:03 UTC (History)
1 user (show)

Fixed In Version: wl-clipboard-2.2.1-1.fc39
Clone Of:
Environment:
Last Closed: 2024-01-31 02:03:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Misha Blanchet 2023-11-30 02:12:28 UTC
There is a know bug in wl-clipboard 2.2.0. The program exit with an error code when we tried to copy/paste in micro editor. The bug is fixed in 2.2.1.

Reproducible: Always

Steps to Reproduce:
1.Start "micro" editor
2.Make a copy (CTRL+C)
3.Paste (CTRL+V)
Actual Results:  
Error message, wl-clipboard exit with an error.

Expected Results:  
Normal copy paste

Comment 1 Fedora Update System 2024-01-22 07:31:57 UTC
FEDORA-2024-8ccc2a56c1 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-8ccc2a56c1

Comment 2 Fedora Update System 2024-01-23 01:17:43 UTC
FEDORA-2024-8ccc2a56c1 has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-8ccc2a56c1`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-8ccc2a56c1

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 3 Fedora Update System 2024-01-31 02:03:36 UTC
FEDORA-2024-8ccc2a56c1 has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.