[GH-ISSUE #701] HDD goes nuts when moving mouse between machines #557

Open
opened 2026-05-05 06:40:45 -06:00 by gitea-mirror · 8 comments
Owner

Originally created by @ivanaponi on GitHub (May 28, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/701

HDD goes nuts when moving mouse between machines

Windows 7 server, Linux client

Rapidly move the mouse between server and client, the client HDD activity light goes bonkers

Is this due to it being in Flatpak wrappers on Linux Mint (no native package there) or is it common to all packages?

Originally created by @ivanaponi on GitHub (May 28, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/701 HDD goes nuts when moving mouse between machines Windows 7 server, Linux client Rapidly move the mouse between server and client, the client HDD activity light goes bonkers Is this due to it being in Flatpak wrappers on Linux Mint (no native package there) or is it common to all packages?
Author
Owner

@ivanaponi commented on GitHub (May 28, 2020):

Seems to mostly happen when the Cinnamon desktop and not a terminal or other app is foreground

<!-- gh-comment-id:635272976 --> @ivanaponi commented on GitHub (May 28, 2020): Seems to mostly happen when the Cinnamon desktop and not a terminal or other app is foreground
Author
Owner

@p12tic commented on GitHub (May 28, 2020):

@ivanaponi Could you install iotop and run it in a terminal? That would show what process is using the HDD. I somehow suspect that Barrier logs too much stuff in your case, maybe worth to check what is the log level and reduce it?

<!-- gh-comment-id:635288778 --> @p12tic commented on GitHub (May 28, 2020): @ivanaponi Could you install `iotop` and run it in a terminal? That would show what process is using the HDD. I somehow suspect that Barrier logs too much stuff in your case, maybe worth to check what is the log level and reduce it?
Author
Owner

@ivanaponi commented on GitHub (May 28, 2020):

[jdb2/dm3-8] is reporting high IO % usage on the rapid change and it's only when the desktop is foreground (nemo desktop but not the nemo file explorer open does this)

Barrier log level is INFO and it's reporting enter leave screen, but this isn't happening for other foreground apps that also cause the logging

<!-- gh-comment-id:635291835 --> @ivanaponi commented on GitHub (May 28, 2020): [jdb2/dm3-8] is reporting high IO % usage on the rapid change and it's only when the desktop is foreground (nemo desktop but not the nemo file explorer open does this) Barrier log level is INFO and it's reporting enter leave screen, but this isn't happening for other foreground apps that also cause the logging
Author
Owner

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

Weird. [jdb2/dm3-8 are kernel-space processes - see here for a bit more info - so I do wonder why the I/O usage is spiking with regards to Barrier. What desktop environment do you use? I've had issues with high I/O usage with KDE and GNOME for example.

<!-- gh-comment-id:635397664 --> @shymega commented on GitHub (May 28, 2020): Weird. `[jdb2/dm3-8` are kernel-space processes - see [here](https://unix.stackexchange.com/questions/4583/what-is-jbd2-dm-3-8-and-kdmflush-and-why-are-they-constantly-on-iotop) for a bit more info - so I do wonder why the I/O usage is spiking with regards to Barrier. What desktop environment do you use? I've had issues with high I/O usage with KDE and GNOME for example.
Author
Owner

@ivanaponi commented on GitHub (May 28, 2020):

Cinnamon Desktop Environment (with nemo as the desktop file manager - but not happening with nemo file manger window), Barrier is in a Flatpak wrapper (not my choice but the only one available for Linux Mint 19.3 repos).

<!-- gh-comment-id:635399051 --> @ivanaponi commented on GitHub (May 28, 2020): Cinnamon Desktop Environment (with nemo as the desktop file manager - but not happening with nemo file manger window), Barrier is in a Flatpak wrapper (not my choice but the only one available for Linux Mint 19.3 repos).
Author
Owner

@github-actions[bot] commented on GitHub (Sep 21, 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.

<!-- gh-comment-id:695867456 --> @github-actions[bot] commented on GitHub (Sep 21, 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.
Author
Owner

@p12tic commented on GitHub (Jan 10, 2021):

This is a valid bug report, let's not close it.

<!-- gh-comment-id:757529179 --> @p12tic commented on GitHub (Jan 10, 2021): This is a valid bug report, let's not close it.
Author
Owner

@p12tic commented on GitHub (Jan 10, 2021):

I think the problem is that Barrier flushes logs to disk too often. I've fixed a number of unnecessary flushes in #1013, but this does not affect logging.

<!-- gh-comment-id:757529611 --> @p12tic commented on GitHub (Jan 10, 2021): I think the problem is that Barrier flushes logs to disk too often. I've fixed a number of unnecessary flushes in #1013, but this does not affect logging.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/barrier#557
No description provided.