Happy to report that the proposed packages did fix the issue for me also. Thanks everyone!

When a checklist item is in edit mode (through the specific steps below), selecting another item for editing does not take the previous item out of edit mode, and upon selecting a third item (or pressing enter) causes the second item to be overwritten by whatever content is in the first selected item.

Server Setup Information:

• Wekan version: 2.74
• Operating System: Ubuntu 16.04
• Deployment Method: snap (stable)
• Http frontend if any: Apache 2.4
• ROOT_URL environment variable: https://my-domain.com/kan

Problem description:

Steps to reproduce

1. Have a card with a checklist with 4 (or more) items with contents A, B, C, D (and so on):
2. Select item A with LBM
3. Select item B with LBM
4. Select item C with LBM
5. Select item D with LBM

What happens
At step 4, when C opens for editing, B remains in edit mode. At step 5, contents of C are overwritten by contents of B (that is, ”C” becomes a ”B”).

What I expect to happen
At step 4, for B to leave edit mode, and at step 5, the contents of C to remain as they are.

Other notes

• Reproducible in both Chrome and Firefox.
• Curiously, this does not seem to affect the firstly selected item: in step 3 above, A leaves edit mode correctly and thus B doesn’t get overwritten by the contents of item A in step 4.
• At step 5, instead of selecting item D, pressing enter has the same effect.

Browser console output
empty

snap logs wekan.wekan
nothing related

@Marcus: yup, that seems to be it:

jani@saegusa:~$ dpkg -l ’libcpd*’ ’cpdb*’
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Nimi Versio Arkkitehtuuri Kuvaus
+++-========================-=================-=================-======================================================
ii cpdb-backend-gcp 1.0.0-0ubuntu2 amd64 Common Print Dialog Backends – Google Cloud Print Back
ii libcpdb-libs-common0:amd 1.1.1-0ubuntu1 amd64 Common Print Dialog Backends – Interface Library for B
jani@saegusa:~$ SAL_DISABLE_CPD=true libreoffice –norestore
func=xmlSecCheckVersionExt:file=xmlsec.c:line=188:obj=unknown:subj=unknown:error=19:invalid version:mode=abi compatible;expected minor version=2;real minor version=2;expected subminor version=25;real subminor version=26

That is, no stack trace nor other apparent problems when starting LO with SAL_DISABLE_CPD=true.

@elvetemedve It’s cool, V14 is working just fine so I’ll just postpone updating the extension until sometime in the future. Thanks!

Looks like this is exacerbated by Wekan issue #1911, as it turns out 99,8 % of the log is about the socket connection (since 2018-09-15):

root@battra:~# grep -c -v "received client metadata from anonymous unix socket" /var/snap/wekan/common/mongodb.log
23426
root@battra:~# grep -c "received client metadata from anonymous unix socket" /var/snap/wekan/common/mongodb.log
10970660

Log rotation would still be nice, but nowhere near as critical if less than one percent of the current logging was produced (a few megabytes per year in my setup here, if I extrapolated correctly).

I noticed my mongodb.log has grown pretty large:

root@battra:~# ls -lh /var/snap/wekan/common/mongodb.log
-rw-r--r-- 1 root root 3,1G touko  4 21:14 /var/snap/wekan/common/mongodb.log

The first lines in the log are timestamped 2018-03-02T16:39:44.754+0200.

Should the log rotate automatically, but doesn’t for some reason? Alternatively, should I truncate it manually (and if so, how)? I have no use for the logs apart from the occasional bug reports here, so even losing all of it is fine.

There are no related mongodb settings keys AFAICS. (And sorry if this is unrelated to snap packaging, it was just a guess on my part.)

Server Setup Information:

• Wekan version: 2.65
• Operating System: Ubuntu 16.04
• Deployment Method: snap
• Http frontend if any: Apache 2.4

I’m using Ubuntu 18.04, which has Gnome Shell 3.28 (3.28.3+git20190124-0ubuntu18.04.1).

After I updated the extension to latest release (16), it fails to start. Gnome Shell reports this error:

Extension "System_Monitor@bghome.gmail.com" had error: TypeError: GObject.registerClass() used with invalid base class (is PanelMenuButton)

Downgrading to release 14 makes it work again.

Ubuntu’s appindicator extension has a similar issue from a while back, with pointers to an issue with the extensions website, but I’m unsure if this is related.

In any case, I decided to open this issue to at least document it. Feel free to close it if it’s intentional (Gnome Shell 3.28 no longer supported), or otherwise not a bug with System Monitor.

Can’t speak for Stuart, but I’m the other one affected, and still so:

jani@saegusa:~$ apt-cache policy libreoffice
libreoffice:
Asennettu: 1:6.0.7-0ubuntu0.18.04.5
Ehdokas: 1:6.0.7-0ubuntu0.18.04.5
Versiotaulukko:
*** 1:6.0.7-0ubuntu0.18.04.5 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages
500 http://archive.ubuntu.com/ubuntu bionic-security/universe amd64 Packages
100 /var/lib/dpkg/status
1:6.0.3-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
jani@saegusa:~$ libreoffice –norestore
Application Error

Fatal exception: Signal 6
Stack:
/usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7f5cb050b568]
/usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c3a6)[0x7f5cb05343a6]
/lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7f5cb0145f20]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f5cb0145e97]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7f5cb0147801]
/usr/lib/libreoffice/program/libmergedlo.so(+0x2d5c882)[0x7f5cb34ae882]
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5AbortERKN3rtl8OUStringE+0xa2)[0x7f5cb343a2b2]
/usr/lib/libreoffice/program/libmergedlo.so(+0x1d0d470)[0x7f5cb245f470]
/usr/lib/libreoffice/program/libmergedlo.so(+0x2cedc5d)[0x7f5cb343fc5d]
/usr/lib/libreoffice/program/libuno_sal.so.3(+0x163b2)[0x7f5cb050e3b2]
/usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c26f)[0x7f5cb053426f]
/lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7f5cb0145f20]
/lib/x86_64-linux-gnu/libc.so.6(+0xb1646)[0x7f5cb01b8646]
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_dbus_node_info_new_for_xml+0x124)[0x7f5cae74dce4]
/usr/lib/libreoffice/program/libmergedlo.so(+0x2d6aa3b)[0x7f5cb34bca3b]
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc92d6)[0x7f5cae7432d6]
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9518)[0x7f5cae743518]
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d1a3)[0x7f5cae7071a3]
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8dbc6)[0x7f5cae707bc6]
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc1082)[0x7f5cae73b082]
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d1a3)[0x7f5cae7071a3]
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d1d9)[0x7f5cae7071d9]
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x155)[0x7f5cae15b285]
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4c650)[0x7f5cae15b650]
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7f5cae15b6dc]
/usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x41444)[0x7f5c9ac63444]
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5YieldEv+0x2e)[0x7f5cb343a9be]
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application7ExecuteEv+0x45)[0x7f5cb343c165]
/usr/lib/libreoffice/program/libmergedlo.so(+0x1d12e93)[0x7f5cb2464e93]
/usr/lib/libreoffice/program/libmergedlo.so(+0x2cef846)[0x7f5cb3441846]
/usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7f5cb3441950]
/usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x115)[0x7f5cb2485fb5]
/usr/lib/libreoffice/program/soffice.bin(+0x78b)[0x557ff5eff78b]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7f5cb0128b97]
/usr/lib/libreoffice/program/soffice.bin(+0x7ca)[0x557ff5eff7ca]

The Debian BTS has a related report [1] which suggests to me this issue should have been fixed way back in v1.11. But even if installing wasn’t broken, with the legacy databases discontinued, it’s not much use in the long term.

Geoip-database-contrib has already been removed from Debian entirely [2] due to deprecation by upstream, apparently in favor of geoipupdate [3].

(I’m not affiliated with either package and have no solutions; I’m just documenting the connections here.)

* [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666063
* [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900400
* [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885441

Yep, retrying does work.

I’ve now reported this to Mozilla and linked to it. Thanks, Olivier!