/usr/bin/wireshark:6:qt_message_fatal:QMessageLogger::fatal:QXcbConnection::QXcbConnection:QXcbIntegration::QXcbIntegration:QXcbIntegrationPlugin::create
Bug #1587562 reported by
errors.ubuntu.com bug bridge
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Wireshark |
Fix Released
|
Unknown
|
|||
wireshark (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
The Ubuntu Error Tracker has been receiving reports about a problem regarding wireshark. This problem was most recently seen with version 2.0.2+ga16e22e-1, the problem page at https:/
Changed in wireshark: | |
status: | Unknown → Fix Released |
Changed in wireshark: | |
status: | Fix Released → Incomplete |
Changed in wireshark: | |
status: | Incomplete → Fix Released |
To post a comment you must log in.
This looks like what is expected to happen when you try and run a Qt application with no X server available... Qt prints a message and aborts. Not sure what else we're supposed to do in that case.