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!

(My) original report on Launchpad: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1820514

Any page under https://forums.tomshardware.com/ seems to trigger this, but I have yet to come across other sites that do. Pages can even be saved from the main Tom’s Hardware domain (https://www.tomshardware.com/) without issues.

A workaround discovered by Olivier Tilloy: clicking retry in the download manager completes the save.

Steps to reproduce:

1. Open https://forums.tomshardware.com/threads/what-is-the-actually-difference-between-udimm-and-dimm.1575984/
2. Right-click and select ’Save page as’. Point the dialog to your directory of choice.

Actual results:

There’s no copy of the page in the target directory. Going to about:downloads reveals that the download has failed, without further details.

Expected results:

For the directory to contain a downloaded copy of the page.

Tested all combinations of both (Ctrl-s/context menu in safe mode and normal mode), all with the same results. Could this be locale-dependent? The UI is in English in safe mode though, so I’m guessing safe mode should be locale-independent, as I’m on fi_FI.UTF-8 otherwise.

And just to clarify: my testing of Bionic was on real hardware as well, and I ran these latest tests on Cosmic on another computer (real hardware).

== Steps to reproduce ==
1. Open https://forums.tomshardware.com/threads/what-is-the-actually-difference-between-udimm-and-dimm.1575984/
2. Right-click and select ’Save page as’. Point the dialog to your directory of choice.

== What I expect to happen ==
For the directory to contain a downloaded copy of the page.

== What happens ==
There’s no copy of the page in the target directory. Going to about:downloads reveals that the download has failed, without further details.

== Other info ==
I’m reporting this from up-to-date Disco, albeit with a 4.* kernel (as gdm currently fails to start in my VirtualBox VM with 5.*) but it’s equally reproducible in Bionic.

Any page under https://forums.tomshardware.com/ seems to trigger this, but I have yet to come across other sites that do. Pages can even be saved from the main Tom’s Hardware domain (https://www.tomshardware.com/) without issues.