[GH-ISSUE #223] Trash bin isn't working #179

New issue

Closed

opened 2026-05-05 05:32:35 -06:00 by gitea-mirror · 4 comments

gitea-mirror commented

2026-05-05 05:32:35 -06:00

Owner

Originally created by @AdrianKoshka on GitHub (Jan 12, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/223

Operating Systems

Server: Fedora 29

Client: Raspbian x86 (Debian stretch)

Barrier Version

Steps to reproduce bug

Open barrier
Go to `Configure Server..."
Drag a new screen onto the grid
Try to drag new screen into the trash

Originally created by @AdrianKoshka on GitHub (Jan 12, 2019). Original GitHub issue: https://github.com/debauchee/barrier/issues/223 ### Operating Systems ### Server: Fedora 29 Client: Raspbian x86 (Debian stretch) ### Barrier Version ### ![about](https://user-images.githubusercontent.com/8690255/51077520-c5fa2300-1675-11e9-9e45-3ff29df11e90.png) ### Steps to reproduce bug ### 1. Open barrier 2. Go to `Configure Server..." 3. Drag a new screen onto the grid 4. Try to drag new screen into the trash ![trash](https://user-images.githubusercontent.com/8690255/51077536-12ddf980-1676-11e9-83d5-e0001bbd307f.gif)

gitea-mirror

2026-05-05 05:32:35 -06:00

closed this issue
added the
bug
label

gitea-mirror commented

2026-05-05 05:32:40 -06:00

Author

Owner

@TafThorne commented on GitHub (Jan 22, 2019):

This behaviour is also seen in the same version while running under flatpak on Ubuntu 18.04.

@TafThorne commented on GitHub (Jan 22, 2019): This behaviour is also seen in the same version while running under flatpak on Ubuntu 18.04.

gitea-mirror commented

2026-05-05 05:32:43 -06:00

Author

Owner

@AdrianKoshka commented on GitHub (Jan 22, 2019):

Of course, it's going to be seen no matter the distro.

@AdrianKoshka commented on GitHub (Jan 22, 2019): Of course, it's going to be seen no matter the distro.

gitea-mirror commented

2026-05-05 05:32:44 -06:00

Author

Owner

@mssalvatore commented on GitHub (Apr 16, 2019):

I built both the current master branch (commit d85a47ad80) and commit 53ebc47a on Fedora 29, Ubuntu 18.04, and Kubuntu 18.04. I was unable to reproduce this behavior.

@mssalvatore commented on GitHub (Apr 16, 2019): I built both the current master branch (commit d85a47ad80024) and commit 53ebc47a on Fedora 29, Ubuntu 18.04, and Kubuntu 18.04. I was unable to reproduce this behavior.

gitea-mirror commented

2026-05-05 05:32:46 -06:00

Author

Owner

@shymega commented on GitHub (Aug 7, 2020):

This is no longer reproducible on v2.3.2 on my openSUSE Tumbleweed system. Therefore I will close this issue, as there has also been a report of it working in later commits.

@shymega commented on GitHub (Aug 7, 2020): This is no longer reproducible on v2.3.2 on my openSUSE Tumbleweed system. Therefore I will close this issue, as there has also been a report of it working in later commits.

gitea-mirror referenced this issue

2026-05-05 05:46:14 -06:00

[GH-ISSUE #297] Unable to run Linux barrier client during startup using systemd #238