Description of problem: Crashed after Wireshark main window had been closed. Version-Release number of selected component: wireshark-qt-2.2.6-4.fc26 Additional info: reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: wireshark -k -i - crash_function: QObject::disconnect executable: /usr/bin/wireshark-qt journald_cursor: s=375888cef57b49058eeb2f3c24389c57;i=6138a;b=93035e50e6e14a46b638c5ceb9731dbd;m=7fe170232f;t=55167ec47ff80;x=6ad6c9ee4ecdcee7 kernel: 4.11.3-300.fc26.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (5 frames) #0 QObject::disconnect at kernel/qobject.cpp:2956 #2 QDBusConnectionPrivate::closeConnection at qdbusintegrator.cpp:1145 #3 QDBusConnectionPrivate::~QDBusConnectionPrivate at qdbusintegrator.cpp:1069 #5 QDBusConnectionManager::run at qdbusconnection.cpp:186 #6 QThreadPrivate::start at thread/qthread_unix.cpp:368 Potential duplicate: bug 1417872
Created attachment 1285960 [details] File: backtrace
Created attachment 1285961 [details] File: cgroup
Created attachment 1285962 [details] File: core_backtrace
Created attachment 1285963 [details] File: cpuinfo
Created attachment 1285964 [details] File: dso_list
Created attachment 1285965 [details] File: environ
Created attachment 1285966 [details] File: limits
Created attachment 1285967 [details] File: maps
Created attachment 1285968 [details] File: open_fds
Created attachment 1285969 [details] File: proc_pid_status
Created attachment 1285970 [details] File: var_log_messages
Created attachment 1285971 [details] File: exploitable
Similar problem has been detected: Crashed when closed reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/wireshark /home/mayorov/Work/ / /Moscow.TestBed/Certification.HLR-FE7SP1/tests/rszi.pcap crash_function: QObject::disconnect executable: /usr/bin/wireshark-qt journald_cursor: s=375888cef57b49058eeb2f3c24389c57;i=11272b;b=94bf791f0c1c409c9c7566c8b7471e60;m=3b5e6cc316;t=552188c8b6a13;x=9a8a9eab29555113 kernel: 4.11.4-300.fc26.x86_64 package: wireshark-qt-2.2.7-1.fc26 reason: wireshark-qt killed by signal 11 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Just opening and closing Wireshark causes this error. It happened on Fedora 25 also. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/wireshark crash_function: QObject::disconnect executable: /usr/bin/wireshark-qt journald_cursor: s=1f216fd1cd5146589d206b080ddde7af;i=8b92;b=ccb8c40424e64151a687137b8f61bdc3;m=27c80aa2f;t=5541bd6a8f85d;x=e54d89b4e2177641 kernel: 4.11.9-300.fc26.x86_64 package: wireshark-qt-2.2.7-1.fc26 reason: wireshark-qt killed by signal 11 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Hi, I can't reproduce this bug anymore on F25, up to date and Wireshark 2.2.7. Wireshark opens and closes ok, without errors, so I guess it's fixed for me.
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.