Description of problem: After launching Bustle, the user has two options: start a new capture or load a bustle capture file. If the user selects new capture, a modal dialog pops up with a "stop" button and counts the dbus messages. When the user clicks "stop", the application closes. There is no opportunity to review the dbus messages, let alone save them. Version-Release number of selected component (if applicable): bustle-0.5.4-3.fc26.x86_64 How reproducible: Always Steps to Reproduce: 1. Run Bustle 2. Start a new capture. 3. Stop the capture Actual results: Application closes Expected results: Application remains open Additional info:
When recording finishes, Bustle reloads the recorded log from disk. (The log is actually saved to ~/.cache/bustle.) I don't remember my rationale for doing this. What seems to be happening here is that reading back the log is failing due to a change in libpcap which rejects logs with a large snaplen https://bugs.freedesktop.org/show_bug.cgi?id=100220 . Then Bustle tries to fall back to reading an older (pre-2011!) plaintext log format, which is crashing. I'll cook up a fix.
I have released Bustle 0.6.1 which does not crash in this situation. As discussed on https://bugs.freedesktop.org/show_bug.cgi?id=100220 libpcap Git has some changes which allow D-Bus logs to have a 128MiB snaplen. So Fedora may want to cherry-pick the two relevant patches to libpcap as well as updating Bustle: https://github.com/the-tcpdump-group/libpcap/commit/1a6b088a88886eac782008f37a7219a32b86da45 https://github.com/the-tcpdump-group/libpcap/commit/42c3865d71a3d3ad3fc61ee382ad3b5113d40552
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.