Bug 394633 - How to unintentionally delete home directory using kontact
Summary: How to unintentionally delete home directory using kontact
Status: RESOLVED WORKSFORME
Alias: None
Product: kontact
Classification: Applications
Component: contacts (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-23 19:51 UTC by audun
Modified: 2022-12-26 05:20 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description audun 2018-05-23 19:51:09 UTC
So I deleted my entire home directory using kontact. Here's how:

I never used kontact before, but had .vcf files in ~/.local/share/contacts synced with vdirsyncer from a carddav server.

This was before installing kontact and Akonadi.

Now I decided to use Kontact and carddav directly, so I don't need those directories anymore, so I deleted them using the terminal and adjusted vdirsyncer config to not sync those anymore.

I noticed the directories lingered in kontact, so i deleted it from the view there as well, and i restarted kontact. It proceeded to explode with error messages, and now my home directory was completely cleaned out.
Comment 1 Christoph Feck 2018-05-28 23:08:30 UTC
> the directories lingered in kontact

Could you be more specific in which view folders where still displayed, even after removing them?
Comment 2 audun 2018-05-29 05:35:04 UTC
It was folders in .local/share/contacts

They contained a bunch of vcards from my carddav account

On 29 May 2018 01:08:54 Christoph Feck <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=394633
>
> --- Comment #1 from Christoph Feck <cfeck@kde.org> ---
>> the directories lingered in kontact
>
> Could you be more specific in which view folders where still displayed, even
> after removing them?
>
> --
> You are receiving this mail because:
> You reported the bug.
> You voted for the bug.
Comment 3 Justin Zobel 2022-11-26 00:14:01 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Bug Janitor Service 2022-12-11 05:07:07 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2022-12-26 05:20:58 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!