Re: [Discuss-gnuradio] GTK related segmentation fault when running GRC

[CEL]

Hi Jason,

that backtrace didn't quite tell me anything, but then I googled the
library in which the segfault happens (gtk3-nocsd).
The github page to that library literally describes it as "A hack to
disable gtk+ 3 client side decoration"; the readme says it's
automatically being preloaded into the system after installation.

I guess I found my prime suspect. Can you try uninstalling 

apt remove libgtk3-nocsd0

logging out and back in (essentially: killing all GTK3 programs) and
see whether the problem persists?

Best regards,
Marcus
 
On Thu, 2019-05-30 at 14:28 -0600, Jason Fritz wrote:
> I've the high level source of the problem, but not the root. If I
> simply change my Desktop from Mate to Ubuntu's default, then GRC runs
> fine and doesn't seg fault. So it seems there's something with Mate
> on Ubuntu that conflicts with something in gnuradio-companion causing
> it to seg fault, but I have no idea how to figure out what that might
> be so I can fix it. I'm not sure I'd call it a bug, but there's
> definitely a problem. Perhaps a gnuradio developer can test this on a
> box running Mate? I'm not sure if it has to be Ubuntu or if it could
> be any other distro. If anyone has any clues on how to fix this (I'd
> really prefer using Mate over Unity) please let me know, or if you
> need me to get more diagnostics to debug.
> 
> On Wed, May 22, 2019 at 4:54 PM Jason Fritz <address@hidden> wrote:
> > Problem: When I run gnuradio-companion and then just select the
> > window and move the mouse around or try to resize the window, the
> > program generates a segmentation fault. I don't even have the
> > opportunity to load any models and usually only have to wait <10
> > seconds before the crash.
> > 
> > OS: Ubuntu 18.04
> > 
> > I did read about other seg faults with GRC, but none quite matched
> > my situation. One suggested running gdb to get a backtrace, which I
> > did and why I believe the problem is GTK related. The backtrace is
> > given below from PyBOMBS installation.
> > 
> > My initial gnuradio installation was via apt-get. Thinking that was
> > the problem, I removed it and used PyBOMBS following the
> > instructions at 
> > https://www.gnuradio.org/blog/2016-06-19-pybombs-the-what-the-how-and-the-why/
> > , which matches others I've found. When that still didn't solve the
> > problem, I tried compiling from source, although I tested it before
> > running 'make install'. No luck there either, and I couldn't figure
> > out how to get some of the dependencies so I'd prefer to use the
> > Pybombs version. 
> > 
> > I'm not ruling out a conflict somewhere, but the backtrace seems to
> > indicate a GTK problem. Any ideas? Need more info?
> > 
> > Thanks!
> > 
> > > which python
> > /usr/bin/python
> > > python --version
> > Python 2.7.15rc1
> > > which gnuradio-companion
> > /usr/local/src/prefix/default/bin/gnuradio-companion
> > 
> > > gbd --args python $(which gnuradio-companion)
> > run
> > *** move mouse around window until it crashes about 5 seconds later
> > ***
> > (gdb) bt
> > #0  0x0000000000000154 in  ()
> > #1  0x00007ffff7bd0c2b in gdk_window_set_decorations () at
> > /usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0
> > #2  0x00007fff94ce16f3 in  () at /usr/lib/x86_64-linux-gnu/libgtk-
> > x11-2.0.so.0
> > #3  0x00007fff8e04a277 in  () at /usr/lib/x86_64-linux-gnu/gtk-
> > 2.0/modules/libappmenu-gtk-module.so
> > #4  0x00007fff9558310d in g_closure_invoke () at /usr/lib/x86_64-
> > linux-gnu/libgobject-2.0.so.0
> > #5  0x00007fff9559612e in  () at /usr/lib/x86_64-linux-
> > gnu/libgobject-2.0.so.0
> > #6  0x00007fff9559e715 in g_signal_emit_valist () at
> > /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> > #7  0x00007fff9559f12f in g_signal_emit () at /usr/lib/x86_64-
> > linux-gnu/libgobject-2.0.so.0
> > #8  0x00007fff94cd53d8 in gtk_widget_realize () at /usr/lib/x86_64-
> > linux-gnu/libgtk-x11-2.0.so.0
> > #9  0x00007fff94cdfa5d in  () at /usr/lib/x86_64-linux-gnu/libgtk-
> > x11-2.0.so.0
> > #10 0x00007fff9558310d in g_closure_invoke () at /usr/lib/x86_64-
> > linux-gnu/libgobject-2.0.so.0
> > #11 0x00007fff9559612e in  () at /usr/lib/x86_64-linux-
> > gnu/libgobject-2.0.so.0
> > #12 0x00007fff9559e715 in g_signal_emit_valist () at
> > /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> > #13 0x00007fff9559f12f in g_signal_emit () at /usr/lib/x86_64-
> > linux-gnu/libgobject-2.0.so.0
> > #14 0x00007fff94cd4b96 in gtk_widget_show () at /usr/lib/x86_64-
> > linux-gnu/libgtk-x11-2.0.so.0
> > #15 0x00007fff8e2569da in  () at /usr/lib/x86_64-linux-gnu/gtk-
> > 2.0/modules/liboverlay-scrollbar.so
> > #16 0x00007fff960f7d03 in  () at /usr/lib/x86_64-linux-gnu/libglib-
> > 2.0.so.0
> > #17 0x00007fff960f7285 in g_main_context_dispatch () at
> > /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
> > #18 0x00007fff960f7650 in  () at /usr/lib/x86_64-linux-gnu/libglib-
> > 2.0.so.0
> > #19 0x00007fff960f7962 in g_main_loop_run () at /usr/lib/x86_64-
> > linux-gnu/libglib-2.0.so.0
> > #20 0x00007fff94bb6a37 in gtk_main () at /usr/lib/x86_64-linux-
> > gnu/libgtk-x11-2.0.so.0
> > #21 0x00007fff9525ba75 in  () at /usr/lib/python2.7/dist-
> > packages/gtk-2.0/gtk/_gtk.so
> > #22 0x000055555564f8af in PyEval_EvalFrameEx ()
> > #23 0x000055555564f232 in PyEval_EvalFrameEx ()
> > #24 0x000055555564f232 in PyEval_EvalFrameEx ()
> > #25 0x0000555555647d0a in PyEval_EvalCodeEx ()
> > #26 0x0000555555647629 in PyEval_EvalCode ()
> > #27 0x000055555567861f in  ()
> > #28 0x0000555555673322 in PyRun_FileExFlags ()
> > #29 0x000055555567267d in PyRun_SimpleFileExFlags ()
> > #30 0x00005555556211ab in Py_Main ()
> > #31 0x00007ffff77feb97 in __libc_start_main (main=
> >     0x555555620b10 <main>, argc=2, argv=0x7fffffffdab8,
> > init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized
> > out>, stack_end=0x7fffffffdaa8) at ../csu/libc-start.c:310
> > #32 0x0000555555620a2a in _start ()
> > 
> 
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio