Barrier is starting...but fails #1246
Comments
|
I recently had trouble with screen names being the same. Check the settings and make sure they are different. You can also increase the logging level. This may give more info about the problem. |
|
Wait...what? So maeks84 are you saying the screen names should be different? How so? Everything else I've read so far indicates that the screen names must match for Barrier to work. And, I've checked, double checked, and checked again to be sure the names do match. Barrier still starts on both my Windows laptop and on my Debian laptop. Just on this Kubuntu desktop (which is the machine I use as the barrier server) does Barrier always fail to start. |
|
Yes. When I was setting up I had two computers using "Matthews-iMac.local". Changed one and reloaded Barrier and it began working again. The problem may also be a configuration file issue. Which is why I mentioned increasing the logging level if the screen names are not the issue.
|
|
Oh, OK, now I see what you mean. Yeah, the screen name of the three machines I mentioned are all different from each other. I thought you were referring to the client name in the server configuration settings. There you would want the names to match, even though the two machines would have to have different names. So that's not the issue here. Increased the logging level one step from info to debug. Here is the output: [2021-08-23T20:05:27] INFO: starting server Does anyone see a clue now that will help solve my issue? |
|
Try increasing the logging level again. Basically want to see if it says something else about that error that is being thrown out. Increase to the max if needed. Is Barrier up-to-date on each device? |
|
Here is the report with logging increased to max level. [2021-08-24T17:01:40] INFO: starting server |
|
What happens if you start with a new config file? No clients specified. Does the server run then? |
|
Gave it a try with no clients specified, and it makes no difference. |
|
I'm afraid that I don't know then. Maybe something to do with the window manager in Kubuntu? That's getting beyond me though. Sorry I couldn't help more. |
|
Thanks for making an effort. |
|
Decided to run a little experiment today. After purging all Barrier installations, I created a new user on this Kubuntu machine, and installed barrier again. Still failed to start. After setting up Barrier in the new users environment, once the "Start" button is clicked, the application immediately crashed...same as before. Swapped a blank SSD into this desktop computer and installed a fresh Debian 11 with KDE desktop. Installed Barrier from the apt repository and set it up. Starts and works great, just as it had before on Kubuntu. So problem is not my hardware, network or settings. Something is amiss about my Kubuntu configuration...but what? |
|
I read that there issues that prevent Barrier from operating on Wayland and thought maybe that's my issue...but it's not. I've checked my graphics stack, and it was using Xorg all along. So still no resolution. |
|
Try the workaround at #1283 (comment) (thanks to @Gollum999 for mentioning that this is likely related) |
We have Barrier installed via Snap on Kubuntu 20.04, and it fails to start. Continues to show "Barrier is Starting", but never actually starts. Here is what the log reports:
[2021-08-13T08:38:07] INFO: starting server
[2021-08-13T08:38:07] INFO: config file: /tmp/Barrier.y43390
[2021-08-13T08:38:07] INFO: log level: INFO
[2021-08-13T08:38:07] ERROR: process exited with error code: 11
[2021-08-13T08:38:07] INFO: detected process not running, auto restarting
This same error repeats over and over until I Quit the process. Really strange thing is I have been using Barrier on this computer for several weeks, then when changing client laptops the other day, Barrier ended up in the current state, and has not been able to start again. Any suggestions on what can be done to make Barrier work again?
The text was updated successfully, but these errors were encountered: