Bug 4640 - Moving (sorting) accounts creates account duplication.
Summary: Moving (sorting) accounts creates account duplication.
Status: NEW
Alias: None
Product: Claws Mail (GTK 2)
Classification: Unclassified
Component: Other (show other bugs)
Version: 3.19.1
Hardware: PC Linux
: P3 normal
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2022-10-20 11:48 UTC by linux.felixbecker2
Modified: 2022-10-20 16:44 UTC (History)
1 user (show)

See Also:


Attachments
Screenshot of account duplication after account moving and restart of claws-mail. (25.95 KB, image/png)
2022-10-20 11:48 UTC, linux.felixbecker2
no flags Details

Description linux.felixbecker2 2022-10-20 11:48:51 UTC
Created attachment 2307 [details]
Screenshot of account duplication after account moving and restart of claws-mail.

I have a lot of email accounts configured (used only for sending), since I use different email dresses for almost any different purpose (especially for each new web registration I use a dedicated email adress).

Now I wanted to categorise those accounts. To do so, I have created "placeholder accounts" that have a name like "--- Category ---", and only the bare minimum data filled in in order for claws-mail to accept it, so that I can easily distunguish them when I select in the compose window an account to use.

Then I use the "Edit accounts..." window to move accounts around, and quite often I need scrolling in order to reach the new place.

Quite often I then see that accounts get duplicated:

* After quitting claws-mail, `clawsker` errors out with messages like
  ```
  Error: duplicate section 'Account: 56' in resource file '/home/[...]/.claws-mail/accountrc'
  ```
* I have to manually edit the `accountrc` in order to remove the duplicate.
* In the "Edit accounts..." window in claws-mail they at first do not appear duplicated, but when I restart claws-mail they appear duplicated.
* Not every move creates a duplicated account.


Manually sorting my accounts via manually editing the `accountrc` is not a viable option because it is too easy to mess things up.


I cannot provide my accountrc for privacy and security reasons, but I at least suppled a screenshot with obfuscation, see attachment.


### claws-mail version:

* Latest git checkout,
* compiled against gtk2.
* `claws-mail --version`: `3.19.0git86`.
* Latest git commit hash: 15c070cb3
* Latest git commit date: 2022-10-20

Build on Arch Linux from the AUR[1] according to this recipe: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=claws-mail-gtk2-git, especially with the following options passed to `./configure`:

```
--prefix=/usr
--disable-static
--enable-shared
--enable-nls
--enable-manual
--enable-libsm
--enable-ipv6
--enable-gnutls
--enable-enchant
--enable-crash-dialog
--disable-generic-umpc
--enable-compface
--enable-pthread
--enable-startup-notification
--enable-dbus
--enable-ldap
--enable-jpilot
--disable-networkmanager
--enable-libetpan
--disable-valgrind
--disable-alternate-addressbook
--enable-svg
--enable-deprecated
--enable-acpi_notifier-plugin
--enable-address_keeper-plugin
--enable-archive-plugin
--enable-att_remover-plugin
--enable-attachwarner-plugin
--enable-bogofilter-plugin
--enable-bsfilter-plugin
--enable-clamd-plugin
--enable-dillo-plugin
--disable-fancy-plugin
--enable-fetchinfo-plugin
--enable-gdata-plugin
--enable-libravatar-plugin
--enable-litehtml_viewer-plugin
--enable-mailmbox-plugin
--enable-managesieve-plugin
--enable-newmail-plugin
--enable-notification-plugin
--enable-pdf_viewer-plugin
--enable-perl-plugin
--enable-python-plugin
--enable-pgpcore-plugin
--enable-pgpmime-plugin
--enable-pgpinline-plugin
--enable-rssyl-plugin
--enable-smime-plugin
--enable-spamassassin-plugin
--enable-spam_report-plugin
--enable-tnef_parse-plugin
--enable-vcalendar-plugin
--enable-demo-plugin
```

[1]
https://aur.archlinux.org/packages/claws-mail-gtk2-git
Comment 1 linux.felixbecker2 2022-10-20 11:51:25 UTC
I increased the importance from "normal" to "major" since when there is messing up of some config file, also more serious data corruption might occur.

I wanted to set the severity higher, but I forgot in the first place, and cannot do it anymore now.
Comment 2 Paul 2022-10-20 12:07:26 UTC
cannot reproduce this. At what point do you see the duplicated accounts? During the drag'n'drop procedure? After quitting? After re-starting? After using clawsker??
Comment 3 linux.felixbecker2 2022-10-20 12:12:30 UTC
> At what point do you see the duplicated accounts? During the drag'n'drop procedure? After quitting? After re-starting? After using clawsker??

After quitting I see them reported by `clawsker` and confirm in the `accountrc`. (Before everything looks fine in `claws-mail`, and before I cannot use `clawsker`).
And after re-starting within `claws-mail`.

And as I wrote, not _every_ move creates this. But roughly every 20%-40% of moves in my case of many accounts.
Comment 4 linux.felixbecker2 2022-10-20 12:17:26 UTC
P.S.:

> > At what point do you see the duplicated accounts? During the drag'n'drop procedure? After quitting? After re-starting? After using clawsker??
> 
> After quitting I see them reported by `clawsker` and confirm in the `accountrc`. (Before everything looks fine in `claws-mail`, and before I cannot use `clawsker`).
> And after re-starting within `claws-mail`.

I also see when I moved an account, then edit it (because I noticed a mistake). Then the highlighting jumps back to the original place where I now can find the account duplicated (it is also at the new place), and I can confirm within the `accountrc`, all before quitting `claws-mail`.
Comment 5 linux.felixbecker2 2022-10-20 16:44:08 UTC
P.S.:

> I also see when I moved an account, then edit it (because I noticed a mistake). Then the highlighting jumps back to the original place where I now can find the account duplicated (it is also at the new place)

and both copies did get the edit I did carry out.

Note You need to log in before you can comment on or make changes to this bug.