Hide Forgot
Description of problem: Installed gr-osmosdr and attempted to run 'osmocom_fft -f 100000000' with HackRF hardware. Get the following error: (osmocom_fft:5128): GLib-GObject-WARNING **: invalid cast from 'GdkWaylandDisplay' to 'GdkX11Display' Segmentation fault (core dumped) Version-Release number of selected component (if applicable): Fedora Branched 25 20160815 Workstation-Live gr-osmosdr 0.1.3-21.20141023git42c66fdd.fc25 How reproducible: Always Steps to Reproduce: 1. Install gr-osmosdr 2. Attach HackRF harware SDR 3. osmocom_fft -f 100000000 Actual results: Segmentation fault Expected results: Should run and open an FFT window
Unfortunately I do not own HackRF, but this seems like glib/wayland problem.
AFAIK there are no GdkWaylandDisplay or GdkX11Display casts in the gr-osmosdr code, so probably there is nothing to fix in gr-osmosdr, reassigning to WxGTK3, but maybe it is also not correct place. AFAIK other packages temporally workaround this problem by disabling GTK3.
Can you please provide a stack trace from the core dump?
Closing due to lack of response from originator.
Created attachment 1536892 [details] strace from segfault
Reopening as still seeing this problem. Missed the first call for info a couple years ago. Haven't tested with this hardware since. Still seeing the same error, will attach an strace of the segfault. Let me know what else I can do. Description of problem: Installed gr-osmosdr and attempted to run 'osmocom_fft -f 100000000' with HackRF hardware. Get the following error: (osmocom_fft:5128): GLib-GObject-WARNING **: invalid cast from 'GdkWaylandDisplay' to 'GdkX11Display' Segmentation fault (core dumped) Version-Release number of selected component (if applicable): Fedora 29 Workstation installed on bare metal gr-osmosdr-0.1.4-14.20170221git2a2236cc.fc29 How reproducible: Always Steps to Reproduce: 1. Install gr-osmosdr 2. Attach HackRF harware SDR 3. osmocom_fft -f 100000000 Actual results: Segmentation fault Expected results: Should run and open an FFT window
An amendment to comment 6, the error display is ONLY "Segmentation fault (core dumped)" and NOT "(osmocom_fft:5128): GLib-GObject-WARNING **: invalid cast from 'GdkWaylandDisplay' to 'GdkX11Display'". I missed deleting this line from the previous comment.
We really need a *stack trace* of the core dump, not an strace. Please see https://fedoraproject.org/wiki/StackTraces#Obtaining_a_stack_trace_using_just_GDB for how to get a stack trace.
The procedure provided in comment 8 did not work for me, it results in the following "No executable file specified." Can I use "coredumpctl" to provide you with what you need?
(In reply to Geoffrey Marr from comment #9) > The procedure provided in comment 8 did not work for me, it results in the > following "No executable file specified." Can I use "coredumpctl" to provide > you with what you need? Yes, coredumpctl should work too.
It still would be good to get a stack trace from this, but I have a hunch about the problem. Can you see if this works around the problem: GDK_BACKEND=x11 osmocom_fft -f 100000000
Hi Scott, sorry I haven't gotten that stack trace to you, when I did, I got a file that was 140mb large and between looking how to shrink that and my other daily work, it fell through the cracks. Any help you have there would be appreciated. I ran your bit above and... it works perfectly, just as it should. Let me know what else I can do other than the stack trace; I'll work on that right now.
Given that forcing X11 worked around the problem, I don't think we need any further information. The root cause here is that wxGLCanvas doesn't work under Wayland, and subsequently crashes. The crash itself has been fixed upstream (and probably we should cherry-pick that fix into Fedora). Long term, wxGLCanvas support for Wayland is being worked on, but it is taking some time. We could also implement a workaround into gr-osmosdr, but I'm not entirely sure where would be the best place to put it.
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-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 '29'. 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 29 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 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.