Why do piped dbus-monitor commands crash?
asked 2015-03-29 10:59:51 +0300
When trying to pipe dbus-monitor into a command and then >> to a file, sometimes Fingerterm closes without notice when the command has collected several seconds of dbus-monitor output and user interaction events. Why is this? Does dbus-monitor start to catch itself monitoring itself and get infinite recursive feedback, does it run out of memory, or is it likely something simpler? Since the GUI from which I run dbus-monitor closes, it's hard to tell from here.
You could try to run it from a ssh session, to see if it behaves the same way there?
juiceme ( 2015-03-29 19:34:08 +0300 )editI'll get back to you on that, hopefully later in the week.
rdmo ( 2015-03-29 20:10:40 +0300 )editAm thinking if such topics are best discussed over IRC \ Dev Mailing list...
anandrkris ( 2015-03-29 20:56:46 +0300 )editOr, enable the option to background
dbus-monitorso that its output appears indmesg, on Linux and particularly Sailfish, such as:dbus-monitor --dmesgIt would be especially helpful if users could configure this in the Jolla Settings GUI:
Dbus monitoring: on/offI know there may be nuanced arguments for and against this. Please refrain from comments like 'it is not a priority' and 'the Jolla developers are working on more important issues'.
That is a given assumption and voting up or down is more helpful. Please comment on the merits of and issues raised by this change to the role and positioning of
rdmo ( 2015-04-04 11:39:30 +0300 )editdbus-monitor.