Arch Linux User Repository

When starting through systemd, systemd status gives the below:

Mar 04 23:00:18 ArchTest systemd[596]: Starting Unified Remote Server...
Mar 04 23:00:18 ArchTest bash[1850722]: skipping copy
Mar 04 23:00:18 ArchTest bash[1850722]: starting server
Mar 04 23:00:18 ArchTest bash[1850731]: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files
Mar 04 23:00:18 ArchTest bash[1850722]: skipping manager
Mar 04 23:00:18 ArchTest systemd[596]: Finished Unified Remote Server.
Mar 04 23:00:43 ArchTest systemd-coredump[1856889]: [LNK] Process 1850748 (urserver) of user 1000 dumped core.

                                                    Stack trace of thread 1851022:
                                                    #0  0x00007f4be6c808ec n/a (libc.so.6 + 0x878ec)
                                                    #1  0x00007f4be6c31ea8 raise (libc.so.6 + 0x38ea8)
                                                    #2  0x00007f4be6c1b53d abort (libc.so.6 + 0x2253d)

Not very useful, I think, but thought I'd put it out there

Yes I tested today and it crashes immediately.

I cannot find errors.

New server version 3.13.0.2505 (52) crashes when you type using the Android system keyboard. The first letter you type works but server immediately crashes before second letter can be typed. Keyboard remote and other remotes work. Tested on EndeavourOS and Debian with same results. reported to dev

I'm having a tough time getting this to start correctly and stay working. On first launch if set to autostart in anyway, whether it be the autostart in ~/.config/autostart, or via systemd, it crashes on first connection. The whole thing will issue a coredump. If I start it manually via "/opt/urserver/urserver --damon" or calling the urserver-start script, it will always crash on first connection.

The only way I've got the server to start and stay running is to use systemd, but stop and start it after the system is online. If I don't stop and start it, it will crash on first connection. It also works to just select restart server on the web page. I also noticed the web interface will say it didn't detect a LAN address on first start, but after restarting it's fine.

Any ideas?

No I can't ping my IP address, but I can ssh to it and I see it reachable with ip neigh. So weird.

You can install an Android console on phone, for example Termux.

Try to ping the server.

If not working, you have some configuration problem on phone

Thanks for taking the time. They are both in the same network (although the PC is wired and the smartphone is WiFi) and both are 192.168.1.x. I have tried to disable/enable WiFi and also turning on and off the router.

I have connectivity on both but, for some reason, I cannot ping to and from the cellphone. I actually can't ping anything from the smartphone, not even 8.8.8.8, so probably that's another issue.

On the other hand it works normally on Windows, even if I can't ping, and Windows is on the same machine but as a different boot.

Just now I was testing on Xiaomi Mi 10.

Some smartphone disable WiFi after some time on standby

Try to disable/re-enable Wifi

Be sure that server and smartphone are in the same network, for example 192.168.1.x

Personally I have both server and smartphone on static IP, that is recommended in this case

Last error:

"WiFi connection problem. Unable to send to broadcast.:sendto failed:EPERM (operation not permitted)"

But after reset it says just "WiFi connection problem."

I doesn't find the server on the list, I had to add it manually.

You should start it as user with

/opt/urserver/urserver --daemon

On smartphone

Preferences:

Enable Auto-Update servers on smartphone app

Status:

See what error do you have (Last error)

Force disconnect -> Clear cache -> Force connect

Servers:

Delete all servers and select the right one from found servers