Impossible to mount Onedrive

Desktop
,
1

Hi there everyone.

I don’t know why, but today I’ve booted my system and it’s impossible to access Onedrive.

When I click my account in File, I get a small window saying something like “Impossible to access name_of_my_onedrive_account_here - mount specific not valid”.

I’ve tried to disconnect and re-connect the account, but nothing changed.

Any suggestion?

edit: using Bluefin stable (based on Fedora 41 with Gnome 47)

1 Like
2

  1. Please always specify your distro, s/w version etc.

  2. Was OneDrive working before and it stopped working after a reboot, or it never worked?

3

Hi.

I have updated the first post and will leave here the answers:

  1. I am using Bluefin stable (it’s based on Fedora 41, with Gnome 47)
  2. Yes, it was working just fine yesterday. Quick history:
  • yesterday I booted the system
  • updated it
  • rebooted it
  • onedrive was still working and I could access files. I didn’t modify any ot them; I didn’t do anything else in the system
  • today it’s not working, no updates from yesterday to install
4

OneDrive works fine on older image of FC41 (updated few weeks ago).

sid@fedora:~$ rpm -qi gnome-online-accounts
Name        : gnome-online-accounts
Version     : 3.52.1
Release     : 1.fc41
...

but fails with below error on my Debian Unstable with g-o-a 3.53.1

goa-onedrive-error
goa-onedrive-error403×218 7.93 KB

Might be a regression in some recent package. Not sure.

5

Oh, that’s exactly the error I’m seeing (but on Bluefin)

6
1 Like
7

Same, Fedora 41, Gnome 47, Kernel: 6.12.13-200.fc41.x86_64.
Solved by downgrading goa, sudo dnf downgrade gnome-online-accounts

8

Downgrade from

  • gnome-online-accounts-3.53.1-3.fc41 to
  • gnome-online-accounts-3.53.1-4really3.52.2

is already in progress in Fedora 41.

Refer https://src.fedoraproject.org/rpms/gnome-online-accounts/.

10

This thread is different from Unable to open OneDrive files, which is what your above comment refers to. The issue in this thread is due to a packaging issue in Fedora 41 and Debian Unstable, which has been resolved.

Closing this topic.

1 Like