-
Notifications
You must be signed in to change notification settings - Fork 413
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERROR: cannot retrieve objects: The name org.freedesktop.miracle.wifi was not provided by any .service files (ctl_wifi_fetch() in ....../miraclecast/src/ctl/ctl-wifi.c:1172) #298
Comments
Did you install miraclecast? That conf file should be present on Here config for meson: https://github.com/albfan/miraclecast/blob/master/res/meson.build#L3 See by default all build systems install on /use/local, I've updated build instructions to avoid that: See https://github.com/albfan/miraclecast/wiki/Building |
Yup... I had miraclecast successfully installed using cmake, almost the same instruction as https://github.com/albfan/miraclecast/wiki/Building, but installed under folder /usr/local . |
upload here the logs for support described in FAQ on this wiki. There's some problem with your run of miracle-wifid |
|
in miracast protocol your device can act as source (share a video stream (normally from its screen)) or as sink( receives and shows a video streaming). Both are peers for miracast To try to use miraclecast as source you should look into #4 and #172 (which is still a WIP) continue this in those issues please |
I think you forget to copy the res/org.freedesktop.miracle.conf to /etc/dbus-1/system.d/. |
I'm seeing the exact same issue using the AUR from Arch Linux. Should I upload my logs as well? And if so, do you want me to create a new issue or append to this one? |
@dnapier you can upload here |
I have same issue with the AUR package. What logs do you need from me? The error occurs when trying to do this
or this
For peer. Given the difference between sink and peer described above I'ld like to do peer but I can't do either. |
@codeman101. Not sure what happens Download the package with:
And upload the build (tar.gz) here so I can inspect |
@albfan I don't use youart that aur helper has been deprieciated on Arch. I use yay which does it all. The only command I had to run run was I could make a temporary repo to upload it to but I'd rather not if possible. Is there any way you can make a quick VM of Manjaro and run the command to see the tar.gz for yourself? You would just need to install yay which is done via |
Here I made a temp repo to upload it. https://github.com/codeman101/temporary-for-data-transfer. I didn't do this originally because I thought gihub would get angry because of the size of the file is. |
Thanks. AUR package seems correct. (it installs the dbus file) org.freedesktop.miracle.wifi service is provided by You can check with:
Only if daemon is running you will see the service avaliable, so after run miracle-wifid in other terminal service should be avaliable, or in a oneliner:
|
That was it the instructions in the readme don't trigger the daemon but that second line you wrote in that post did it. Please consider making the following edits to your readme
Also I think I encountered a serious bug (or lack of instruction) because when I got out of the miraclectl and restarted network manager and wpa my router didn't accept the correct password until I rebooted the machine. |
@codeman101 what about:
About Instructions as peer, is true that they are misleading, as that feature is not implemented. The bug (I guess is that you have miracle-wifid running in background) is because miracle-wifid is running a wpa_supplicant process with Wifi-Direct. That conflicts with NetworkManager. All you have to do is stop the miracle-wifid daemon. That's why is recommended to run daemon in other terminal, to kill it just with Ctrl+C. anyway you can always kill it with:
At some point we should use NetworkManager directly, now (since version 1.16) it deals with Wifi-Direct, and running as a service (systemd) istead of manually run the daemon. |
That would be great. It would definitely make it more user-friendly so the user doesn't have restart network manger when they want to go back to using the internet.
You should add this to the readme. If it's running like a true systemd service (or even a general unix background process) killing the terminal it was executed in won't kill it.
By the way one of the commands in the readme causes this process to stop. I think it's when I run the command to get into the wifictl. |
1. My environment:
2. tests:
3. ERROR message:
Try miracle-sinkctl
In fact, I got the same ERROR while using command miracle-wifictl:
Extra:
Any suggestions?
The text was updated successfully, but these errors were encountered: