Project

General

Profile

Bug #1086

qkd-module-manager crashes on detection of QKD modules in the system

Added by Oliver Maurhart over 2 years ago. Updated over 1 year ago.

Status:
Assigned
Priority:
High
Target version:
Start date:
11.07.2016
Due date:
% Done:

0%

Estimated time:

Description

qkd-module-manager crashes when some modules are present on the system.

steps to reproduce:
1. Launch qkd-module-manager
2. Launch any qkd-module

expected:
  • qkd-module-manager shows the new detected QKD module
result:
  • qkd-module-manager crashes

History

#1 Updated by Oliver Maurhart over 2 years ago

Develop branch just made a switch to Qt5. The qkd library now has no more widgets inside the lib. So move the widget stuff of the lib inside the module-manager.

#2 Updated by Cristina Tamas over 1 year ago

  • Tracker changed from Bug to Feature

port into qt5 / libqwt-qt5 succeeded
crash as described not reproduced yet
open: fighting with / against git

#3 Updated by Cristina Tamas over 1 year ago

  • Tracker changed from Feature to Support

is there anything I have to learn about configuration new to the version 2 months ago?

$ /usr/bin/qkd-pipeline --verbose start test/test-data/autoconnect/pipeline-cat-alice.xml
Loading pipeline configuration from 'test/test-data/autoconnect/pipeline-cat-alice.xml'...
Loading pipeline configuration from 'test/test-data/autoconnect/pipeline-cat-alice.xml' done.
Starting:  --config test/test-data/autoconnect/cat-pipeline.conf --debug 
Unable to get module PID or DBus service name - is module running?
Starting:  --config test/test-data/autoconnect/cat-pipeline.conf --debug 
Unable to get module PID or DBus service name - is module running?
terminate called after throwing an instance of 'std::runtime_error'
  what():  Can't query DBus with no DBus address
Aborted (core dumped)

Might be only some package incompatibility ...

#4 Updated by Oliver Maurhart over 1 year ago

Did you ensure that /usr/bin/qkd-pipeline is the very same as you just built in your project? Since it seems that you are running a source code pipeline with the system's qkd-pipeline tool. As things change inside the sources quite rapidly this may be the cause of your problems.

There should not be any exception thrown as seen in the output of yours.

And - btw - this should actually be a ticket on its own.

#5 Updated by Cristina Tamas over 1 year ago

  • Assignee changed from Cristina Tamas to Oliver Maurhart

Sure the same pipeline; configuration valid; generated key damaged.
Consider this part (# 3-5) as solved / closed - sorry for this parenthesis.

#6 Updated by Cristina Tamas over 1 year ago

  • Tracker changed from Support to Bug

feature_1086 ready to merge into develop

Also available in: Atom PDF