When saving a file, engauge segfault with (gdb) run Starting program: /usr/bin/engauge warning: Could not load shared library symbols for linux-vdso.so.1. Do you need "set solib-search-path" or "set sysroot"? [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". QPixmap::setMask: Cannot set mask while pixmap is being painted on QPixmap::setMask: Cannot set mask while pixmap is being painted on Program received signal SIGSEGV, Segmentation fault. Q3Action::removeFrom (this=0xa8b3f0, w=0xa2ccb0) at widgets/q3action.cpp:1228 1228 widgets/q3action.cpp: Aucun fichier ou dossier de ce type. (gdb) bt #0 Q3Action::removeFrom (this=0xa8b3f0, w=0xa2ccb0) at widgets/q3action.cpp:1228 #1 0x000000000047db98 in MruDocuments::mergeDocument (this=0x7fffffffab00, doc=...) at src/mrudocuments.cpp:101 #2 0x000000000044a64f in DigitMain::documentSaveAs (this=0x7fffffffa7f0, doc=0x94c6a0) at src/digitmain.cpp:2179 #3 0x000000000044aa3d in DigitMain::documentSave (this=0x7fffffffa7f0, doc=0x94c6a0) at src/digitmain.cpp:2130 #4 0x000000000044e5d8 in DigitMain::slotFileSave (this=0x7fffffffa7f0) at src/digitmain.cpp:2254 #5 0x00000000004a896d in DigitMain::qt_static_metacall (_o=0x7fffffffa7f0, _c=<optimized out>, _id=5, _a=<optimized out>) at moc_digitmain.cpp:186 #6 0x00007ffff62fa121 in QMetaObject::activate (sender=0x9ca840, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3547 #7 0x00007ffff62fa121 in QMetaObject::activate (sender=0x9c1200, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fffffff9140) at kernel/qobject.cpp:3547 #8 0x00007ffff681d491 in QAction::activated (this=<optimized out>, _t1=-22) at .moc/release-shared/moc_qaction.cpp:297 #9 0x00007ffff681d50d in QAction::activate (this=0x9c1200, event=<optimized out>) at kernel/qaction.cpp:1260 #10 0x00007ffff6c76969 in QMenuPrivate::activateCausedStack (this=0x9c6a10, causedStack=..., action=0x9c1200, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:1028 #11 0x00007ffff6c7c842 in QMenuPrivate::activateAction (this=0x9c6a10, action=0x9c1200, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:1120 #12 0x00007ffff6874bb3 in QWidget::event (this=0x91c620, event=0x7fffffff9ca0) at kernel/qwidget.cpp:8371 #13 0x00007ffff6c7dd93 in QMenu::event (this=0x91c620, e=0x7fffffff9ca0) at widgets/qmenu.cpp:2469 #14 0x00007ffff68238f4 in notify_helper (e=0x7fffffff9ca0, receiver=0x91c620, this=0x709540) at kernel/qapplication.cpp:4557 #15 QApplicationPrivate::notify_helper (this=0x709540, receiver=0x91c620, e=0x7fffffff9ca0) at kernel/qapplication.cpp:4529 #16 0x00007ffff6828f1b in QApplication::notify (this=<optimized out>, receiver=0x91c620, e=0x7fffffff9ca0) at kernel/qapplication.cpp:4100 #17 0x00007ffff62e606b in QCoreApplication::notifyInternal (this=0x7fffffffab80, receiver=0x91c620, event=0x7fffffff9ca0) at kernel/qcoreapplication.cpp:915 ---Type <return> to continue, or q <return> to quit--- #18 0x00007ffff6824882 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #19 QApplicationPrivate::sendMouseEvent (receiver=0x91c620, event=0x7fffffff9ca0, alienWidget=0x0, nativeWidget=0x91c620, buttonDown=0x0, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3168 #20 0x00007ffff68a21d3 in QETWidget::translateMouseEvent (this=0x91c620, event=<optimized out>) at kernel/qapplication_x11.cpp:4441 #21 0x00007ffff68a0932 in QApplication::x11ProcessEvent (this=0x7fffffffab80, event=0x7fffffffa3c0) at kernel/qapplication_x11.cpp:3630 #22 0x00007ffff68c7da2 in x11EventSourceDispatch (s=0x70d120, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #23 0x00007ffff4ae975a in g_main_dispatch (context=0x70bb40) at gmain.c:2539 #24 g_main_context_dispatch (context=0x70bb40) at gmain.c:3075 #25 0x00007ffff4ae9ab8 in g_main_context_iterate (context=0x70bb40, block=1, dispatch=1, self=<optimized out>) at gmain.c:3146 #26 0x00007ffff4ae9b6c in g_main_context_iteration (context=0x70bb40, may_block=1) at gmain.c:3207 #27 0x00007ffff6315196 in QEventDispatcherGlib::processEvents (this=0x70a9b0, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #28 0x00007ffff68c7a66 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #29 0x00007ffff62e4b12 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #30 0x00007ffff62e4d97 in QEventLoop::exec (this=0x7fffffffa780, flags=...) at kernel/qeventloop.cpp:204 #31 0x00007ffff62e9c85 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187 #32 0x000000000041df9c in main (argc=1, argv=<optimized out>) at src/main.cpp:217 (gdb) Steps to reproduce it: 1) run engauge 2) import a jpeg file 3) do some work or do nothing 4) save a file
Created attachment 325486 [details] emerge --info
I find a way to use engauge, but it is a little bit irritatiing. The file is saved before the crash. Sometime, when I run "engauge the_file", it work, and I can continue to work and save it again without problem. Sometime, it crash with the same error than reported, and I must start from the beginning, import the jpeg file again, and try to save it. At the first save of a file, engauge is crashing every time.
I did download the git repo of engauge, and I cannot reproduce this bug with it. The GIT code depend on QT4 instead of QT3, that even if the README and INSTALL files are not updated. It include also a few more fixes for the widgets. So, the best move would be to do a tarball (or a patch) from the git repo and integrate it in portage. Or wait for a new release.
Created attachment 325636 [details] live ebuild I make this live ebuild. The sed patch for the doc is still needed.
(In reply to comment #4) > Created attachment 325636 [details] > live ebuild > > I make this live ebuild. > > The sed patch for the doc is still needed. The best idea is to download it and generate a tarball with latest snapshot, otherwise there is a great risk of live ebuild working some days and failing others
Created attachment 325940 [details] ebuild for engauge-5.0_p20121007 As the about dialog show version 5.0, I named it 5.0_p20121007. I hope this is a correct name. It work fine here. The tarball was too big, so you can find it here: http://depositfiles.com/files/f42n4bigv
Denis, can you please look at this? Dominique has provided all needed information. If you don't have time to maintain this package, maybe you should drop you from its metadata and leave it to other maintainers (or proxy-maintainers, maybe Dominique is willing to do that: http://www.gentoo.org/proj/en/qa/proxy-maintainers/index.xml )
Sorry for the delay, I was very busy. And still is. But the time I will use to maintain this package will be largely paid back with the time I win with engauge. So yes, I can become a proxy maintainer. I will take contact with the proxy project right away.
(In reply to comment #8) > Sorry for the delay, I was very busy. And still is. > > But the time I will use to maintain this package will be largely paid back > with the time I win with engauge. So yes, I can become a proxy maintainer. I > will take contact with the proxy project right away. Will CC them as calchan keeps quiet :/
Sorry about not replying before, this basically slipped under my radar. I will be more than happy to commit anything that Dominique will send me. I will be equally happy if anybody else updates/fixes this package. Old devs know I'm not territorial at all as I have blogged about this and said so on mailing lists before. It's a bit late now but I will look at it tomorrow morning. If any of you feels like doing it before that don't hesitate. It looks like the tarball has disappeared from wherever it was so a new one will need to be generated. Denis.
Created attachment 336206 [details] ebuild for engauge-5.1 In the meantime, they did a 5.1 release, so we can just use the sourceforge tarball. I tested it only on ~amd64, but I added the ~x86 keyword. It was the only solution to satisfy repoman.
I just pushed the update to CVS. I have tested on both x86 and amd64 and it works. The only thing I have changed is I have removed the build dep on xz-utils which isn't necessary any longer. Thanks Dominique. Denis.
