github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00

[GH-ISSUE #809] touching Chrome to barrier crashes Chrome #641

New issue

Open

opened 2026-05-05 06:49:43 -06:00 by gitea-mirror · 7 comments

gitea-mirror commented

2026-05-05 06:49:43 -06:00

Owner

Originally created by @ariocwhite on GitHub (Jul 21, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/809

Operating Systems

Server: Windows 10-v20H2 - 1904

Client: Linux Lite 5.0 (Ubuntu 20.04)

Barrier Version

Server: (windows) 2.3.2-snapshot-210c2b70
Client: (apt) 2.3.2-Release-0000000000

Steps to reproduce bug

(Using 3 monitors, dual-monitor windows setup, 1 linux laptop)

Drag tab from Chrome from 1 windows screen to other works
(no issue, don't know if barrier is involved with regular multi-monitor setup, but included anyways)
Drag tab (or the whole program) from Chrome, touch it to screen border where barrier configured
Chrome crashes items dragged... either tab or entirety as applicable.

Other info

Super useful, thoroughly enjoying it, just have to be careful.
It is understood Chrome on windows doesn't belong on linux...
don't know if this is a barrier issue or a Chrome issue... apologies if N/A

Originally created by @ariocwhite on GitHub (Jul 21, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/809 ### Operating Systems ### Server: Windows 10-v20H2 - 1904 Client: Linux Lite 5.0 (Ubuntu 20.04) ### Barrier Version ### Server: (windows) 2.3.2-snapshot-210c2b70 Client: (apt) 2.3.2-Release-0000000000 ### Steps to reproduce bug ### (Using 3 monitors, dual-monitor windows setup, 1 linux laptop) 1. Drag tab from Chrome from 1 windows screen to other works (no issue, don't know if barrier is involved with regular multi-monitor setup, but included anyways) 2. Drag tab (or the whole program) from Chrome, touch it to screen border where barrier configured 3. Chrome crashes items dragged... either tab or entirety as applicable. ### Other info ### Super useful, thoroughly enjoying it, just have to be careful. It is understood Chrome on windows doesn't belong on linux... don't know if this is a barrier issue or a Chrome issue... apologies if N/A

gitea-mirror added the

bug

windows

linux

labels 2026-05-05 06:49:43 -06:00

gitea-mirror commented

2026-05-05 06:49:47 -06:00

Author

Owner

@Acters commented on GitHub (Jul 22, 2020):

Doesn't occur in Windows Server to Windows Client configurations. I wonder if this cross platform only issue, or Windows Server to other OS issue. We need a mac user to weigh in.

Version 2.3.3

@Acters commented on GitHub (Jul 22, 2020): Doesn't occur in Windows Server to Windows Client configurations. I wonder if this cross platform only issue, or Windows Server to other OS issue. We need a mac user to weigh in. Version 2.3.3

gitea-mirror commented

2026-05-05 06:49:50 -06:00

Author

Owner

@Monoverde888 commented on GitHub (Jul 28, 2020):

bumping issue

@Monoverde888 commented on GitHub (Jul 28, 2020): bumping issue

gitea-mirror commented

2026-05-05 06:49:52 -06:00

Author

Owner

@shymega commented on GitHub (Jul 28, 2020):

Please don't bump issues. We will get round to them.. bumping just means more time on replying. Bear in mind this is a project with little devs, so bear with.

@shymega commented on GitHub (Jul 28, 2020): Please don't bump issues. We will get round to them.. bumping just means more time on replying. Bear in mind this is a project with little devs, so bear with.

gitea-mirror commented

2026-05-05 06:49:54 -06:00

Author

Owner

@Brockhold commented on GitHub (Jul 30, 2020):

For the sake of adding data, I am unable to reproduce on a similar setup. I have tried two monitor configurations on the host; single and dual (stacked). Both clients have only one monitor each.

Host:
Windows 10 Pro 1909
Barrier 2.3.2-shapshot210c2b70
Chrome version 84.0.4147

Client A:
Arch Linux
Barrier 2.3.3-release (from community)
Top edge of host screen

Client B:
Ubuntu 20.04
Barrier 2.3.2-shapshot9080ce45 (from snap)
Right edge of host screen

@Brockhold commented on GitHub (Jul 30, 2020): For the sake of adding data, I am unable to reproduce on a similar setup. I have tried two monitor configurations on the host; single and dual (stacked). Both clients have only one monitor each. Host: Windows 10 Pro 1909 Barrier 2.3.2-shapshot210c2b70 Chrome version 84.0.4147 Client A: Arch Linux Barrier 2.3.3-release (from community) Top edge of host screen Client B: Ubuntu 20.04 Barrier 2.3.2-shapshot9080ce45 (from snap) Right edge of host screen

gitea-mirror commented

2026-05-05 06:49:56 -06:00

Author

Owner

@ariocwhite commented on GitHub (Jul 30, 2020):

perhaps the difference is pro vs. home? i thought pro had more
virtualization/hyperV support...
also of note, i'm using the windows insider program, slow lane

On Wed, Jul 29, 2020 at 8:26 PM Benjamin Rockhold notifications@github.com
wrote:

For the sake of adding data, I am unable to reproduce on a similar setup.
I have tried two monitor configurations on the host; single and dual
(stacked). Both clients have only one monitor each.

Host:
Windows 10 Pro 1909
Barrier 2.3.2-shapshot210c2b70
Chrome version 84.0.4147

Client A:
Arch Linux
Barrier 2.3.3-release (from community)
Top edge of host screen

Client B:
Ubuntu 20.04
Barrier 2.3.2-shapshot9080ce45 (from snap)
Right edge of host screen

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/debauchee/barrier/issues/809#issuecomment-666000145,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKLQ6YUNWCJX435VCCQLI4TR6C45DANCNFSM4PEAKLSQ
.

@ariocwhite commented on GitHub (Jul 30, 2020): perhaps the difference is pro vs. home? i thought pro had more virtualization/hyperV support... also of note, i'm using the windows insider program, slow lane On Wed, Jul 29, 2020 at 8:26 PM Benjamin Rockhold <notifications@github.com> wrote: > For the sake of adding data, I am unable to reproduce on a similar setup. > I have tried two monitor configurations on the host; single and dual > (stacked). Both clients have only one monitor each. > > Host: > Windows 10 Pro 1909 > Barrier 2.3.2-shapshot210c2b70 > Chrome version 84.0.4147 > > Client A: > Arch Linux > Barrier 2.3.3-release (from community) > Top edge of host screen > > Client B: > Ubuntu 20.04 > Barrier 2.3.2-shapshot9080ce45 (from snap) > Right edge of host screen > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/debauchee/barrier/issues/809#issuecomment-666000145>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AKLQ6YUNWCJX435VCCQLI4TR6C45DANCNFSM4PEAKLSQ> > . >

gitea-mirror commented

2026-05-05 06:49:58 -06:00

Author

Owner

@shymega commented on GitHub (Jul 30, 2020):

No, nothing to do with Windows edition..

OK, thanks for confirming.

On this date - Wed, Jul 29, 2020 at 06:23:30PM -0700, ariocwhite wrote:

perhaps the difference is pro vs. home? i thought pro had more
virtualization/hyperV support...
also of note, i'm using the windows insider program, slow lane

On Wed, Jul 29, 2020 at 8:26 PM Benjamin Rockhold notifications@github.com
wrote:

For the sake of adding data, I am unable to reproduce on a similar setup.
I have tried two monitor configurations on the host; single and dual
(stacked). Both clients have only one monitor each.

Host:
Windows 10 Pro 1909
Barrier 2.3.2-shapshot210c2b70
Chrome version 84.0.4147

Client A:
Arch Linux
Barrier 2.3.3-release (from community)
Top edge of host screen

Client B:
Ubuntu 20.04
Barrier 2.3.2-shapshot9080ce45 (from snap)
Right edge of host screen

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/debauchee/barrier/issues/809#issuecomment-666000145,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKLQ6YUNWCJX435VCCQLI4TR6C45DANCNFSM4PEAKLSQ
.

--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/debauchee/barrier/issues/809#issuecomment-666020367

--
Kind regards,
Dom Rodriguez (shymega)

@shymega commented on GitHub (Jul 30, 2020): No, nothing to do with Windows edition.. OK, thanks for confirming. On this date - Wed, Jul 29, 2020 at 06:23:30PM -0700, ariocwhite wrote: > perhaps the difference is pro vs. home? i thought pro had more > virtualization/hyperV support... > also of note, i'm using the windows insider program, slow lane > > On Wed, Jul 29, 2020 at 8:26 PM Benjamin Rockhold <notifications@github.com> > wrote: > > > For the sake of adding data, I am unable to reproduce on a similar setup. > > I have tried two monitor configurations on the host; single and dual > > (stacked). Both clients have only one monitor each. > > > > Host: > > Windows 10 Pro 1909 > > Barrier 2.3.2-shapshot210c2b70 > > Chrome version 84.0.4147 > > > > Client A: > > Arch Linux > > Barrier 2.3.3-release (from community) > > Top edge of host screen > > > > Client B: > > Ubuntu 20.04 > > Barrier 2.3.2-shapshot9080ce45 (from snap) > > Right edge of host screen > > > > — > > You are receiving this because you authored the thread. > > Reply to this email directly, view it on GitHub > > <https://github.com/debauchee/barrier/issues/809#issuecomment-666000145>, > > or unsubscribe > > <https://github.com/notifications/unsubscribe-auth/AKLQ6YUNWCJX435VCCQLI4TR6C45DANCNFSM4PEAKLSQ> > > . > > > > > -- > You are receiving this because you commented. > Reply to this email directly or view it on GitHub: > https://github.com/debauchee/barrier/issues/809#issuecomment-666020367 -- Kind regards, Dom Rodriguez (shymega)

gitea-mirror commented

2026-05-05 06:50:01 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 29, 2020):

This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions[bot] commented on GitHub (Sep 29, 2020): This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

No labels

Rows
Columns