-
Notifications
You must be signed in to change notification settings - Fork 2
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
Traceback on os-prober call with debug logging #14
Comments
MDD has code to try to use sudo internally if no password is needed to use os-prober, so that should still work even when running the script as user. In case that doesn't work it should fall back to a partition analysis and hopefully this way find out about Windows dual boot systems. Can you try to run If you run the script as root indeed some data about X11 session might be not available. But this is a different issue. |
Here, the debug messages:
|
Ok, then this seems to be a very special case and the outcome is to be expected. I don't think there are many people with this kind of setup, so we can probably ignore it. There is still this traceback in the log though. We should look into that. |
The detection of Windows Boot Manager with
os-prober
requires admin rights (sudo), thus runningwithout
sudo
does not work. On the other hand, runningworks well for the detection of Windows Boot Manager, but it struggles detecting the Display Manager with following error message and output
instead of
"display": "x11"
.What kind of works, is running any command with sudo before. Then,
mdd
callssudo -n os-prober
within the timeout ofsudo
(15 min). But this should not be intended to be used like this.The text was updated successfully, but these errors were encountered: