Mannisenojasta oli toukokuussa naarattu polkupyöränraatoja ja muuta romua, mutta ne romut ja jätesäkit roskineen ovat jääneet siihen polun varteen. Kannattaisi varmaan kerätä talteen ennen kuin joku neropatti viskoo ne takaisin ojaan.
This. Good business or bad, that’s all that it is: business. Companies aren’t people, grievances and forgivances don’t apply.
I’m facing the same issue consistently with Whooshkaa URLs, for example: https://player.whooshkaa.com/episode?id=330009
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:
Problem description:
Steps to reproduce
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
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.
@stokito The client (nor the access point) never send the password; see this answer (and Wikipedia).
@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
10970660Log 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: