Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Invalid node channel message" then segfault #109

Closed
Geremia opened this issue Jul 8, 2017 · 4 comments
Closed

"Invalid node channel message" then segfault #109

Geremia opened this issue Jul 8, 2017 · 4 comments
Assignees
Labels
component: Qt related resolution: UPSTREAM ISSUE The issue in an upstream dependency can not be solved by our developers. Please report it upstream. type: BUG
Milestone

Comments

@Geremia
Copy link

Geremia commented Jul 8, 2017

Whenever I try opening a bible translation, I get this:

(BibleTime 2.11.0_rc2) WARNING: Not a BibleTime Bookmark XML file
[1:1:0100/000000.722656:ERROR:broker_posix.cc(41)] Invalid node channel message
Segmentation fault

I'm on Linux 4.9.34.

@jaakristioja
Copy link
Member

(BibleTime 2.11.0_rc2) WARNING: Not a BibleTime Bookmark XML file

This is most likely not related to the crash which follows.

[1:1:0100/000000.722656:ERROR:broker_posix.cc(41)] Invalid node channel message

This is an error message from the Qt web engine, and most likely not a bug in BibleTime.

Segmentation fault

We're unable to say much more about this crash unless you provide us a backtrace for it. For example, run bibletime in gdb (e.g. using gdb bibletime) and once it crashes, use the thread apply all bt and thread apply all bt full to get a backtrace and a detailed backtrace respectively.

@Geremia
Copy link
Author

Geremia commented Aug 16, 2017

@jaakristioja Here's the dump of what occurs when I double-click on a bible to view.

@Geremia
Copy link
Author

Geremia commented Sep 15, 2017

@jaakristioja By the way, I still get this issue, even after upgrading to Qt version 5.9.1.

@jaakristioja
Copy link
Member

Ok, it appears that this is caused by upstream Qt issue 61213, which the Qt guys have not yet resolved. In commit d941081 we have already a workaround for this issue, but this is not yet part of any official BibleTime release.

@jaakristioja jaakristioja added resolution: UPSTREAM ISSUE The issue in an upstream dependency can not be solved by our developers. Please report it upstream. and removed MORE INFORMATION NEEDED labels Sep 16, 2017
@jaakristioja jaakristioja self-assigned this Sep 16, 2017
@jaakristioja jaakristioja added this to the 2.11.1 milestone Sep 16, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: Qt related resolution: UPSTREAM ISSUE The issue in an upstream dependency can not be solved by our developers. Please report it upstream. type: BUG
Development

No branches or pull requests

2 participants