In issue #1818 I found this:
I see the same
g_menu_insert_item/g_menu_remove_all: assertion 'G_IS_MENU (menu)' failederror messages when starting the client from the terminal (~100 per second), but
without crash.
Here I found 3.5GB of this message in todays(!) logfile, when my /var partition ran full.
Older logfiles were compressed though smaller, but also showed tons of this lines.
that's the exact line:
Mar 31 10:16:54 lorien nextcloud[9783]: g_menu_insert_item: assertion 'G_IS_MENU (menu)' failed
I ran a wc over yesterdays logfile: 110782886 identical lines in one logfile. The same line was written to messages, syslog and user.log resulting in 19,5GB of logfiles in one day.
in the meantime I worked around the problem by entirely turning off the _user_ faciity in rsyslog.conf
*.*;auth,authpriv.none;\
user.none -/var/log/syslog
user.* stop
Hi, same log spamming here (.xsession-error takes 15Go...).
Standard Debian package.
nextcloud --version gives:
Nextcloud version 2.6.0git
Using Qt 5.12.5, built against Qt 5.11.3
Using 'OpenSSL 1.1.1d 10 Sep 2019'
Just to be clear, are you reporting a bug or is this basically a feature request to implement something like a limit for the size of the logfile?
I'd consider this a bug.
Am 3. April 2020 17:01:29 MESZ schrieb Claudius Ellsel notifications@github.com:
Just to be clear, are you reporting a bug or is this basically a
feature request to implement something like a limit for the size of the
logfile?--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/nextcloud/desktop/issues/1904#issuecomment-608491863
--
gesendet von meinem mitnehmbaren Kulturzugangsgerät.
Erreichbarkeitsinformation für Martin Lorenz
geostationär:
49179 Ostercappeln
Bremer Straße 7
52.343347° N | 8.222369° E
https://osm.org/go/0Ga3geSAF
https://w3w.co/soll.unbewusst.zart
9F4C86VC+9R9
fernmündlich: +49-5473-8019862
fernschriftlich: +49-5473-8019861
geomobil:
fern/mündlich/schriftlich:
+49-1577-6209634
+43-680-2371767
auf diversen elektronischen Kulturzugangsgeräten:
mit offenem Zugang
e-mail: [email protected]
martin.[email protected]
[email protected]
martin.[email protected]
matrix: @mlo:matrix.org
jabber/XMPP: [email protected]
Signal: +49-1577-6209634
in zugangsbeschränkten Nutzergruppen
Ev.LKH: www.intern-e.evlka.de
iserv: lws-ostercappeln.net als martin.lorenz
Jede Ähnlichkeit fehlender Kontaktoptionen mit lebenden
oder toten Briefkästen ist unerwünscht und zufällig, ebenso die
Ähnlichkeit mit Cephalopoden.
Alright, also arguable. I will leave the bug label. But basically the bug you report is that the size of the log file can grow that large (because no measures are taken to prevent this), correct? Maybe you can adjust the title (and description) a bit to show that more clearly.
Just to be clear, the message g_menu_insert_item: assertion 'G_IS_MENU (menu)' failed appeared 3568 times this morning in less than 3 seconds. And this kind of burst is recurrent.
The problem is not rolling log, the problem is the frequency at which this message is logged.
Alright, understood.
A quick analysis of my .xsession-errors file (78GiB, the record is mine now!) shows that in one millisecond, I got around 50 errors.
(process:230533): GLib-GIO-CRITICAL **: 22:47:14.856: g_menu_insert_item: assertion 'G_IS_MENU (menu)' failed
On the same time, nextcloud client was at 100% on one CPU thread and was unresponsive.
version 2.6.4
OS: EndeavourOS (Arch Linux based)
Same behaviour here on a Kubuntu 19.10 with nextcloud client 2.6.4
Yep, same problem here - just posted to the Nextcloud help forums. I'm using Archlinux with Nextcloud client 2.6.4-1. In about an hour of uptime I got 9559911 copies of that error, and an .xession-errors file about 985Mb in size. I don't want to turn off error logging, all I want to do is to stop the Nextcloud client doing it!
Additional info: for me it only happens on the first run of nextcloud client.
When I restart it, it doesn't happen anymore. So any debug param should be put on the place where nextcloud is autostarted. Not afterwards after a nextcloud restart. Because the issue won't happen again.
Can still reproduce consistently. Not sure if related but the nextcloud process also uses 1GiB of RAM (when having wrote 21 GiB of logs)
I can also reproduce this. I'm using Ubuntu 20.04 with the NextCloud client that comes from the software (2.6.2-1build1). When I save a file in Vim, I get 4 of these messages. I've started the client from the terminal with the --background flag.
Looking at the comments I here, I suspect it could be because we all don't run the Gnome desktop, but use a different desktop environment or custom window manager (I'm currently using XMonad). Maybe a DE or WM that doesn't show or even run a system tray?
Can't reproduce anymore :o
Version: 3.0.3
Looking at the comments I here, I suspect it could be because we all don't run the Gnome desktop, but use a different desktop environment or custom window manager (I'm currently using XMonad). Maybe a DE or WM that doesn't show or even run a system tray?
I'm running XFCE with a system tray. Anyone with Gnome here?
Yes, it's right pain. I have temporarily given up on Nextcloud and started
using Syncthing instead. It's a very different sort of sync, and doesn't
work with a cloud base, but at least it shares my files across my computers
with the minimum of fuss. If the Nextcloud developers can fix up this
error, or provide a Nextcloud sync that doesn't need a GUI, I'll be right
back in.
I'm using KDE because I always have, I like its look and feel, and the
times I've tried other environments (gnome, XFCE for example) I've always
felt a bit constrained.
On Sun, Dec 27, 2020 at 10:22 AM tuxayo notifications@github.com wrote:
Can't reproduce anymore :o
Version: 3.0.3Looking at the comments I here, I suspect it could be because we all don't
run the Gnome desktop, but use a different desktop environment or custom
window manager (I'm currently using XMonad). Maybe a DE or WM that doesn't
show or even run a system tray?I'm running XFCE with a system tray. Anyone with Gnome here?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/nextcloud/desktop/issues/1904#issuecomment-751406169,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABHFPJ3IJIXLG5EMK5S3TS3SWZV5FANCNFSM4LWQOQGA
.
Can't reproduce anymore :o
Version: 3.0.3
Indeed, I wouldn't be surprised if this was gone with 3.0.3. If someone else can confirm I'll close it.
Most helpful comment
I'd consider this a bug.
Am 3. April 2020 17:01:29 MESZ schrieb Claudius Ellsel notifications@github.com:
--
gesendet von meinem mitnehmbaren Kulturzugangsgerät.
Erreichbarkeitsinformation für Martin Lorenz
geostationär:
49179 Ostercappeln
Bremer Straße 7
52.343347° N | 8.222369° E
https://osm.org/go/0Ga3geSAF
https://w3w.co/soll.unbewusst.zart
9F4C86VC+9R9
fernmündlich: +49-5473-8019862
fernschriftlich: +49-5473-8019861
geomobil:
fern/mündlich/schriftlich:
+49-1577-6209634
+43-680-2371767
auf diversen elektronischen Kulturzugangsgeräten:
mit offenem Zugang
e-mail: [email protected]
martin.[email protected]
[email protected]
martin.[email protected]
matrix: @mlo:matrix.org
jabber/XMPP: [email protected]
Signal: +49-1577-6209634
in zugangsbeschränkten Nutzergruppen
Ev.LKH: www.intern-e.evlka.de
iserv: lws-ostercappeln.net als martin.lorenz
Jede Ähnlichkeit fehlender Kontaktoptionen mit lebenden
oder toten Briefkästen ist unerwünscht und zufällig, ebenso die
Ähnlichkeit mit Cephalopoden.