Repository navigation
Closed
Description
Describe the bug
The OneDrive GUI stuck on "Starting" status. The indicator was green for a while before going back to red.
No more window popped out to prompt inputting some kind of authentication.
Syncing the files using the onedrive CLI client works fine.
Perhaps related to #249
To Reproduce
Steps to reproduce the behavior:
- Open OneDriveGUI after configuring profile
- Click on the "play" button
Expected behavior
GUI manages to sync and displays the status of file sync.
Log
If applicable, add relevant output from log file /tmp/onedrive-gui/onedrive-gui.log.
2025-11-19 09:23:53,043 [onedrivegui:1945][fn=__init__][INFO] - [GUI] Starting worker for profile cipley
2025-11-19 09:23:53,043 [onedrivegui:1949][fn=__init__][DEBUG] - [GUI] OneDrive config file: /home/cipley/.config/onedrive/accounts/cipley/config
2025-11-19 09:23:53,043 [onedrivegui:1950][fn=__init__][DEBUG] - [GUI] OneDrive config dir: <re.Match object; span=(0, 69), match='/home/cipley/.config/onedrive/accounts/cipley_zon>
2025-11-19 09:23:53,043 [onedrivegui:1952][fn=__init__][DEBUG] - [GUI] Monitoring command: 'exec onedrive --confdir='/home/cipley/.config/onedrive/accounts/cipley' --monitor -v '
2025-11-19 09:23:53,043 [onedrivegui:2548][fn=start_onedrive_monitor][INFO] - [GUI] Opening external login window
2025-11-19 09:23:53,051 [onedrivegui:2022][fn=read_stdout][INFO] - [cipley] Reading configuration file: /home/cipley/.config/onedrive/accounts/cipley/config
2025-11-19 09:23:53,051 [onedrivegui:2022][fn=read_stdout][INFO] - [cipley] Configuration file successfully loaded
2025-11-19 09:23:53,051 [onedrivegui:2022][fn=read_stdout][INFO] - [cipley] Using 'user' configuration path for application config and state data: /home/cipley/.config/onedrive/accounts/cipley
2025-11-19 09:23:53,053 [onedrivegui:2022][fn=read_stdout][INFO] - [cipley] D-Bus message bus daemon is available; GUI notifications are now enabled
2025-11-19 09:23:53,053 [onedrivegui:2022][fn=read_stdout][INFO] - [cipley] ERROR: Unable to create /var/log/onedrive
2025-11-19 09:23:53,053 [onedrivegui:2022][fn=read_stdout][INFO] - [cipley] ERROR: Please manually create '/var/log/onedrive' and set appropriate permissions to allow write access for your user to this location.
2025-11-19 09:23:53,053 [onedrivegui:2022][fn=read_stdout][INFO] - [cipley] ERROR: The requested client activity log will instead be located in your users home directory
2025-11-19 09:23:53,053 [onedrivegui:2022][fn=read_stdout][INFO] - [cipley] Using the following path to store the runtime application log: /home/cipley
2025-11-19 09:23:53,053 [onedrivegui:2022][fn=read_stdout][INFO] - [cipley] Using IPv4 and IPv6 (if configured) for all network operations
2025-11-19 09:23:53,054 [onedrivegui:2022][fn=read_stdout][INFO] - [cipley] Attempting to contact the Microsoft OneDrive Service
2025-11-19 09:23:53,150 [onedrivegui:2022][fn=read_stdout][INFO] - [cipley] Successfully reached the Microsoft OneDrive Service
2025-11-19 09:23:53,151 [onedrivegui:2022][fn=read_stdout][INFO] - [cipley] Checking Application Version ...
2025-11-19 09:23:53,223 [onedrivegui:2022][fn=read_stdout][INFO] - [cipley] Attempting to initialise the OneDrive API ...
2025-11-19 09:23:53,223 [onedrivegui:2022][fn=read_stdout][INFO] - [cipley] Configuring Global Azure AD Endpoints
2025-11-19 09:23:53,223 [onedrivegui:2022][fn=read_stdout][INFO] - [cipley] Please authorise this application by visiting the following URL:
2025-11-19 09:23:53,223 [onedrivegui:2022][fn=read_stdout][INFO] - [cipley] https://login.microsoftonline.com/common/oauth2/v2.0/authorize?client_id=d50ca740-c83f-4d1b-b616-12c519384f0c&scope=Files.ReadWrite%20Files.ReadWrite.All%20Sites.ReadWrite.All%20offline_access&response_type=code&prompt=login&redirect_uri=https://login.microsoftonline.com/common/oauth2/nativeclient
2025-11-19 09:23:53,223 [onedrivegui:2022][fn=read_stdout][INFO] - [cipley] After completing the authorisation in your browser, copy the full redirect URI (from the address bar) and paste it below.
2025-11-19 09:23:53,225 [onedrivegui:2022][fn=read_stdout][INFO] - [cipley] Paste redirect URI here: An empty or invalid response uri was entered
2025-11-19 09:23:53,225 [onedrivegui:2022][fn=read_stdout][INFO] - [cipley] The OneDrive API could not be initialised
2025-11-19 09:23:54,827 [onedrivegui:2560][fn=<lambda>][INFO] - finished worker cipley
2025-11-19 09:23:54,827 [onedrivegui:1956][fn=stop_worker][INFO] - [cipley] Waiting for worker to finish...
2025-11-19 09:23:54,827 [onedrivegui:1960][fn=stop_worker][INFO] - [cipley] Quitting thread
2025-11-19 09:23:54,827 [onedrivegui:1963][fn=stop_worker][INFO] - [cipley] Removing thread info
2025-11-19 09:23:54,827 [onedrivegui:1966][fn=stop_worker][INFO] - [GUI] Remaining running workers: {}
System Info
- Linux distribution: Arch Linux
- Desktop environment: KDE Plasma 6.4.5
- Compositor: Wayland
- Python version: 3.13.7
- Version of OneDrive client: 2.5.9
OneDriveGUI info
How did you install OneDriveGUI?: AUR
Metadata
Metadata
Assignees
Labels
No labels

Activity
kobyon commentedon Nov 20, 2025
Having the same problem.
Karls-0 commentedon Nov 20, 2025
The same problem. It looks like latest 2.5.9 updated breaks compatibility with GUI. Before this update all was fine.
bpozdena commentedon Nov 20, 2025
Hi @cipley, based on your screenshot, you are using OneDriveGUI v1.1.1 which is more than a year old. Please use the latest GUI version 1.2.2 - preferably the AppImage version provided by me.
EDIT: I've just tested the AUR package https://aur.archlinux.org/packages/onedrivegui and it successfully installed GUI v1.2.2 and there were no issues. Not sure why you would use Arch (BTW) and not update your packages for over a year ;-) .
I can't reproduce any login issues on GUI v1.2.2 and onedrive client 2.5.9, so I can only assume @kobyon and @Karls-0 might need to update their GUI as well. If not, please share more details about your issues.
Karls-0 commentedon Nov 20, 2025
I use 1.2.2, but tested also on 1.2.0. The same problem. OneDrive client version is v2.5.9-1+np1+1.1. I do not use AUR, I'm on Linux Mint 22.2. All was working fine till this moment, couple of months of smooth sync.
bpozdena commentedon Nov 20, 2025
@Karls-0, can you please start the GUI from terminal, initiate sync and then share the resulting logs from the terminal? Also share a screenshot of the GUI showing your problem.
kobyon commentedon Nov 20, 2025
I didnt catch there was a updated appimage, so updated this now. After updating the GUI was stuck in this state
So I stopped the onedrive user service, deleted all files under
.config/onedriveand.config/onedrive-gui, aswell as my Onedrive sync folder:~/onedrive, and relogged.After relogging and starting the application again, I was now prompted to create a new profile. So I setup a new profile with no custom settings. And was actually prompted with the sign in link :D
However. After signing in again, the application was back to the same state as the image above, "OneDrive sync is starting...".
Karls-0 commentedon Nov 20, 2025
The GUI is the same as posted by @kobyon. Regarding logs (after loading config):
2025-11-20 17:55:37,081 [workers.py:125][fn=read_stdout][INFO] - [karls] D-Bus message bus daemon is available; GUI notifications are now enabled
2025-11-20 17:55:37,081 [workers.py:125][fn=read_stdout][INFO] - [karls] ERROR: Invalid skip_dir entry '.*' detected.
2025-11-20 17:55:37,081 [workers.py:125][fn=read_stdout][INFO] - [karls] To exclude hidden directories (those starting with '.'), enable the 'skip_dotfiles' configuration option instead of using wildcard patterns.
2025-11-20 17:55:38,684 [main_window.py:424][fn=][INFO] - finished worker karls
2025-11-20 17:55:38,684 [main_window.py:733][fn=remove_worker][INFO] - [karls] Removing thread info
2025-11-20 17:55:38,684 [main_window.py:735][fn=remove_worker][INFO] - [GUI] Remaining running workers: {}
And that's all, sync never starts. All I see from this that I use incorrect way to skip dotfiles, but it used to make no problems.
cipley commentedon Nov 20, 2025
I sincerely cannot answer that rather than it's a mystery...I do regularly update my packages - however I almost exclusively use pacman for it. Maybe that's why it doesn't get updated.
I tried updating the GUI to v1.2.3 (via AUR) and can happily say that solved my problem.
(file lists were truncated, but I can confirm they synced now)
The auth process also went as intended.
I want to close this issue since mine has resolved, but seeing there are others who had the same problem as mine, perhaps this can be open for a while longer?
My suggestion is the same as @bpozdena, try to update both the client and GUI to the latest versions.
My understanding is perhaps the way the client process dotfile skip changed; now it asks for the configuration option instead.
Maybe you can change your configuration on that.
bpozdena commentedon Nov 20, 2025
Aha, yeah, that will be it. You should use YAY if you have AUR packages installed.
Perfect, thanks a lot for the quick confirmation.
Karls-0 commentedon Nov 20, 2025
So I guess I have to wait for 1.2.3, as on GitHub 1.2.2 is the newest?
bpozdena commentedon Nov 20, 2025
As the error suggest, you will need to remove the skip_dir entry for
.*. And instead disable sync of dot files with the below checkbox. It will apply to both files and directories starting with a dot.I will improve the error messaging in the GUI to make it more obvious why the sync has stopped.
bpozdena commentedon Nov 20, 2025
OK, in your case the sync in the GUI did not start because the onedrive sync was already running as a service. You should have just stopped and disable the service, then start the sync via GUI.
You can never have onedrive client sync running twice on the same machine for the same onedrive account.
In any case, I will improve the GUI error message to make it more obvious why the sync can't start. This is already implemented, but for some reason does not work in your case.
If you have not rebooted yet and would like to help me, please look inside of
/tmp/onedrive-gui/onedrive-gui.log, look for the error message that was shown when the issue was happening and share it with me.Karls-0 commentedon Nov 20, 2025
It is the same as in consol log:
2025-11-20 17:55:37,081 [workers.py:125][fn=read_stdout][INFO] - [karls] ERROR: Invalid skip_dir entry '.*' detected.
2025-11-20 17:55:37,081 [workers.py:125][fn=read_stdout][INFO] - [karls] To exclude hidden directories (those starting with '.'), enable the 'skip_dotfiles' configuration option instead of using wildcard patterns.
I removed the problematic
.*and it is re-syncing now, so it may be the case. At least if it will keep working after re-sync.abraunegg commentedon Nov 21, 2025
@Karls-0
That was your error - your configuration. Please read the client documentation to correctly configure your client:
https://github.com/abraunegg/onedrive/blob/master/docs/application-config-options.md
abraunegg commentedon Nov 21, 2025
@cipley
This was a bug that was fixed as 'skip_dir' should never have allowed a
.*entry.This was fixed in v2.5.8. Please refer to the release notes: https://github.com/abraunegg/onedrive/releases/tag/v2.5.8
bpozdena commentedon Nov 21, 2025
All fixes and more will be included in OneDriveGUI v1.3.0. ETA one week or so..
Fix detection of already running onedrive process #255
Improved error handling and messaging #255
Implement GUI version check #255