Package Details: unified-remote-server 3.13.0.2505-1

Git Clone URL: https://aur.archlinux.org/unified-remote-server.git (read-only, click to copy)
Package Base: unified-remote-server
Description: Unified Remote Server
Upstream URL: http://www.unifiedremote.com/
Keywords: remote
Licenses: Freeware
Submitter: Peace4all
Maintainer: blackhole
Last Packager: blackhole
Votes: 55
Popularity: 0.45
First Submitted: 2014-04-30 19:18 (UTC)
Last Updated: 2023-02-11 02:35 (UTC)

Latest Comments

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 Next › Last »

hybrid commented on 2016-07-06 17:45 (UTC)

The correct version string is 3.4.0.740 and the sha256sum is b911eda84ec0c4b7acf65333400d0643f6b05bc9164d20b7962080ad820f8626

blackhole commented on 2016-06-01 16:09 (UTC)

I have made some more checks. It is starting fine both manually or enabled at boot, but it is working only in the first case. In the second case no relevant errors, but android client is complaining about wifi problem.

blackhole commented on 2016-06-01 15:37 (UTC)

Ok, updated with the new systemd service, thanks.

getzze commented on 2016-05-31 17:41 (UTC)

Anyway, there will be a problem for the first time the server is started, you have to call `urserver-start` without the --no-copy option for the systemd service to work and do not forget to delete the .desktop entry.

getzze commented on 2016-05-31 17:14 (UTC)

It seems your remotes are not located in the default folder defined in urserver-start, that is `$HOME/.urserver/remotes`. If you have custom remotes, you can copy them to the default folder, otherwise run `urserver-start` without the --no-copy option and it will automatically copy the default remotes to the default folder (and recreate the .desktop file).

blackhole commented on 2016-05-31 14:06 (UTC)

Yes, it is starting, but on my phone: "No remotes available Please check your server installation" but without systemd service using this /opt/urserver/urserver --daemon is working.

getzze commented on 2016-05-31 13:32 (UTC)

You are right, I didn't realize that calling urserver-start without option would recreate the .desktop file. Now it is working with this service: #/usr/lib/systemd/user/urserver.service [Unit] Description=Unified Remote Server After=network.target [Service] Type=oneshot RemainAfterExit=yes ExecStart=/bin/bash /opt/urserver/urserver-start --no-manager --no-copy ExecStop=/bin/bash /opt/urserver/urserver-stop [Install] WantedBy=default.target

blackhole commented on 2016-05-27 14:27 (UTC)

Did you check that a systemd user service is really working in this case? Last time I checked I could autostart only inside graphical Desktop autostart options.

getzze commented on 2016-05-27 12:31 (UTC)

I get an error with the systemd service, the $HOME is not recognized if the service is run as root, with `sudo systemctl start urserver`. Instead the systemd service should be created in /usr/lib/systemd/user/urserver.service, and the service started (and enabled) by the user, without `sudo`: systemctl start --user urserver

blackhole commented on 2016-04-17 14:02 (UTC)

Normally I do not add options that I cannot test myself. As you can see this package is only x86_64. If some people is proposing a tested and working universal PKGBUILD, I will update.

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 Next › Last »