Arch Linux

FossLover

Member

Registered: 2025-03-09

Posts: 15

[Solved] KDE's KIO-GDrive Plugin Leaving Hidden Residue After Being D

Hello,

After installing Kio-Gdrive, the Google1 and Google2 folders were created. Then, for some reason, I uninstalled Kio-Gdrive and reinstalled it. However, when I logged in again, it started from Google3 instead of Google1.

Yes, I know I can rename it, but I’m asking out of curiosity. What do I need to do to completely remove Kio-Gdrive from my system? And why does it start naming from Google3 instead of Google1?

I believe getting an answer to this will also help me better understand how Linux works.

I manually deleted the Google1 and Google2 folders. Then, I removed the Kiogdrive plugin from the application store, restarted my computer, and reinstalled Kiogdrive. However, when I added my Google account again, instead of starting over from Google1, it continued from Google3. This made me think that there might be some configuration or cache files that I haven’t completely removed.

I would really appreciate it if you could explain how to do a complete uninstallation so that I can better understand Linux’s logic. When I checked ~/.config and ~/.local/share, I couldn’t find any files related to Kiogdrive.

I think the issue might also be related to KAccounts because I can see the googlex count there. But when I delete it, it has no effect.

Thx...

Last edited by FossLover (2025-03-16 15:17:41)

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 14,846

Re: [Solved] KDE's KIO-GDrive Plugin Leaving Hidden Residue After Being D

https://wiki.archlinux.org/title/Dotfiles should help to give you an idea how things work.

Moderator Note :
If this stays a general discussion about dotfiles and how to handle them I feel it can stay in this board, but if it evolves into a support question it will be moved.

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

FossLover

Member

Registered: 2025-03-09

Posts: 15

Re: [Solved] KDE's KIO-GDrive Plugin Leaving Hidden Residue After Being D

@Lone_Wolf

Thank you for the link. I realize that I need to do more research on dotfiles. My question is intended as support since my goal is to reset the googlex count. However, it will also be a valuable opportunity to learn more about how Linux works. So, it has value from both perspectives. But since it was opened for support purposes, you may move it to the relevant section.

FossLover

Member

Registered: 2025-03-09

Posts: 15

Re: [Solved] KDE's KIO-GDrive Plugin Leaving Hidden Residue After Being D

Hello again, 

Through trial and error, I found that the file I needed to delete was the "signon.db" file located in the ~/.config/signond folder. 

Thank you very much for your help, interest, and support! 

Long live LINUX, long live FREE SOFTWARE!

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 14,846

Re: [Solved] KDE's KIO-GDrive Plugin Leaving Hidden Residue After Being D

Please prepend [Solved] to the thread title (edit first post) .

Moderator Note : moving to Applications & Desktop Environments

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky