TÖRÖK Attila
TÖRÖK Attila
This issue is still present in 6.0.
This issue is still present in 6.0.
This issue is still present in 6.0.
Thanks for the report and the idea for a fix! We'll look into it.
I believe this is fixed by https://github.com/omnetpp/omnetpp/commit/094d8b9d9af173e6f758a8e0cfebaca901e7c133
I don't think so, not really: ``` [attila:~]$ journalctl -u dbus-broker -b0 Mar 10 02:37:53 ryzen systemd[1]: Starting D-Bus System Message Bus... Mar 10 02:37:53 ryzen dbus-broker-launch[800]: Looking up NSS...
> It unconditionally prints any warnings/errors. I see. > Does that log include messages when the bug actually appears? Of course. These disconnections result in no log output from `dbus-broker`...
Also, a minor correction about `notify-send`: it does terminate eventually, it just takes about 55 seconds (+/- 5 seconds). I suspect a read/poll timeout, because the notification doesn't actually appear....
Is there any way I could raise the log level, or enable some verbose/debug/tracing mode, where _everything_ (not just errors) is dumped into the journal, so that I (we?) can...
I have some `.pcap` captures saved by Bustle from when this happens. Does this give anyone any hints at all?  (Sorry for the enormous image...) The point it not...