Jump to content
Flirc Forums

flirc_1.3.0-1_amd64.deb segfault

Recommended Posts


on ubuntu 14.10 amd64, the Flirc gui (from flirc_1.3.0-1_amd64.deb) immediately segfaults and doesn't open.

here is a backtrace, if you have an unstripped binary (preferably compiled with -ggdb3) i can get you info for that as well.

Thread 1 (Thread 0x30b901428c0 (LWP 3172)):
#0  0x000000000058c3b0 in ?? ()
#1  0x0000030b8efb240d in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#2  0x0000030b8efb2805 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#3  0x0000030b8c0f0b28 in _SmcProcessMessage () from /usr/lib/x86_64-linux-gnu/libSM.so.6
#4  0x0000030b8bee2167 in IceProcessMessages () from /usr/lib/x86_64-linux-gnu/libICE.so.6
#5  0x0000030b8e232a7a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x0000030b8e27d02e in QSocketNotifier::activated(int) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7  0x0000030b8e23b76b in QSocketNotifier::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x0000030b8ef3511c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#9  0x0000030b8ef3b870 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#10 0x0000030b8e21e86d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#11 0x0000030b8e24c61c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#12 0x0000030b8cc76c5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x0000030b8cc76f48 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x0000030b8cc76ffc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x0000030b8e24c031 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#16 0x0000030b8efd84e6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#17 0x0000030b8e21d4f1 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#18 0x0000030b8e21d805 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#19 0x0000030b8e222f67 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#20 0x0000000000411f32 in ?? ()
#21 0x0000030b8d7e2ec5 in __libc_start_main (main=0x411e66, argc=1, argv=0x380ef672658, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x380ef672648) at libc-start.c:287
#22 0x000000000040f80f in ?? ()

Share this post

Link to post
Share on other sites

I think it's just missing a dependency....


can you run the gui manually:




What does it spit out?

Thanks, I'm looking into this.

Share this post

Link to post
Share on other sites

I can reproduce this. So strange. Any rate, I will have a fix by tonight. It's just a matter of time before I solve it.

Share this post

Link to post
Share on other sites

should be fixed now. No longer compiling in mint, but compiling in a chroot ubuntu 64 utopic clean room. Something seems funny with the fonts, let  me know.

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...