search

jstaf / onedriver

A native Linux filesystem for Microsoft OneDrive
GNU General Public License v3.0
1.92k stars 96 forks source link

GUI Launcher not working but CLI Working #233

Open afzl-wtu opened 2 years ago

afzl-wtu commented 2 years ago

I read previous issue reporting they opened GUI from launcher and then add mount point but noting happens. I have installed prebuilt .deb as mention on documentation. aarch64- ubuntu 20.04. The issue is that I did not start from cli I just installed the program through sudo apt install ./b.deb I ran it from Application launcher, a blank window appeared with + sign on left of screen . When I clicked on it it asked me to choose mount point. I choose mount point and after it it automatically closes. I tried many times. Then I ran it from terminal onedriver ~/@OneDrive and it opened authentication screen and I successfully logged in and I can see Drive mounted in my Filemanager showing folders there. I even removed ~/.cache/onedriver and first logged in through terminal and then opened launcher but still the same issue

afzl-wtu commented 2 years ago

When I run onedrive ~/@OneDrive . It mounts my filesystem now and terminal keep logging new entries and no luancher is launched. If I Ctrl+C then termianl stop logging entries and mounted Onedrive FS vanishes.

Current situation: (after running cli command I ran onedrive gui from app launcher to show there is no thing)

image

jstaf commented 2 years ago

Do you see anything if you view the logs for the GUI by invoking it on the command line using onedriver-launcher? If there are no error messages there, see if you can get logs for the systemd unit (see the readme for how to do this).

It sounds to me like there may be a problem opening the authentication popup, or a bug in the GUI. If you're feeling brave you can try building the app from the current master, which has a rewritten GUI (probably likely to sidestep the bug if it is a problem with the GUI, the new code is a lot better).

afzl-wtu commented 2 years ago

ubuntu@aarch64:~$ onedriver-launcher

(onedriver-launcher:17554): ERROR : 10:47:12.024: Could not create systemd dbus proxy: Error calling StartServiceByName for org.freedesktop.systemd1: Process org.freedesktop.systemd1 exited with status 1

Trace/breakpoint trap (core dumped) ubuntu@aarch64:~$

afzl-wtu commented 2 years ago

Do you see anything if you view the logs for the GUI by invoking it on the command line using onedriver-launcher? If there are no error messages there, see if you can get logs for the systemd unit (see the readme for how to do this).

It sounds to me like there may be a problem opening the authentication popup, or a bug in the GUI. If you're feeling brave you can try building the app from the current master, which has a rewritten GUI (probably likely to sidestep the bug if it is a problem with the GUI, the new code is a lot better).

Here is the error