Closed GoogleCodeExporter closed 9 years ago
i think this has to do with the Webcam API, if its possible try with a
different webcam
else
can you run qt-facetrainer through gdb
gdb qt-facetrainer
start
continue
when it segfaults
type
bt
paste the output here
Original comment by rohan.a...@gmail.com
on 17 Feb 2010 at 5:29
The same thing for me. Here is a backtrace:
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff6623ea5 in cvCanny () from /usr/lib64/libcv.so.3
(gdb) bt
#0 0x00007ffff6623ea5 in cvCanny () from /usr/lib64/libcv.so.3
#1 0x00007ffff6691c1c in cvHaarDetectObjects () from /usr/lib64/libcv.so.3
#2 0x000000000041da17 in faceDetector::runFaceDetector(_IplImage*) ()
#3 0x000000000041b8b7 in detector::runDetector(_IplImage*) ()
#4 0x000000000041145a in faceTrainer::timerEvent(QTimerEvent*) ()
#5 0x00007ffff6dac58e in QObject::event(QEvent*) () from
/usr/lib64/libQtCore.so.4
#6 0x00007ffff72829e4 in QWidget::event(QEvent*) () from
/usr/lib64/libQtGui.so.4
#7 0x00007ffff75d171b in QMainWindow::event(QEvent*) () from
/usr/lib64/libQtGui.so.4
#8 0x00007ffff7237b8c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
()
from /usr/lib64/libQtGui.so.4
#9 0x00007ffff723e27f in QApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libQtGui.so.4
#10 0x00007ffff6d9e93c in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from
/usr/lib64/libQtCore.so.4
#11 0x00007ffff6dc3806 in ?? () from /usr/lib64/libQtCore.so.4
#12 0x00007ffff6dc0d68 in ?? () from /usr/lib64/libQtCore.so.4
#13 0x00007ffff4f5461e in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#14 0x00007ffff4f58008 in ?? () from /lib64/libglib-2.0.so.0
#15 0x00007ffff4f5812a in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#16 0x00007ffff6dc0a33 in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from
/usr/lib64/libQtCore.so.4
#17 0x00007ffff72c8d4e in ?? () from /usr/lib64/libQtGui.so.4
#18 0x00007ffff6d9d562 in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib64/libQtCore.so.4
#19 0x00007ffff6d9d705 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib64/libQtCore.so.4
#20 0x00007ffff6d9f2cb in QCoreApplication::exec() () from
/usr/lib64/libQtCore.so.4
#21 0x0000000000412020 in main ()
(gdb)
Original comment by tos...@gmail.com
on 10 Mar 2010 at 9:30
I was in the process of making rpms for f12 and f13 complies fine but there
seems to
be an error related to opencv (ps this happens even when there is no camera.)
The dialogue first screen comes up press next then the program crashes.
Here is the output
(<unknown>:4986): GStreamer-CRITICAL **:
Trying to dispose element appsink1, but it is in READY instead of the NULL
state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
This problem may also be caused by a refcounting bug in the
application or some element.
(<unknown>:4986): GStreamer-CRITICAL **:
Trying to dispose element ffmpegcsp1, but it is in READY instead of the NULL
state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
This problem may also be caused by a refcounting bug in the
application or some element.
(<unknown>:4986): GStreamer-CRITICAL **:
Trying to dispose element fakesink, but it is in READY instead of the NULL
state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
This problem may also be caused by a refcounting bug in the
application or some element.
(<unknown>:4986): GStreamer-CRITICAL **:
Trying to dispose element typefind, but it is in READY instead of the NULL
state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
This problem may also be caused by a refcounting bug in the
application or some element.
(<unknown>:4986): GStreamer-CRITICAL **:
Trying to dispose element decodebin1, but it is in READY instead of the NULL
state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
This problem may also be caused by a refcounting bug in the
application or some element.
(<unknown>:4986): GStreamer-CRITICAL **:
Trying to dispose element capsfilter0, but it is in READY instead of the NULL
state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
This problem may also be caused by a refcounting bug in the
application or some element.
(<unknown>:4986): GStreamer-CRITICAL **:
Trying to dispose element appsink2, but it is in READY instead of the NULL
state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
This problem may also be caused by a refcounting bug in the
application or some element.
(<unknown>:4986): GStreamer-CRITICAL **:
Trying to dispose element ffmpegcsp2, but it is in READY instead of the NULL
state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
This problem may also be caused by a refcounting bug in the
application or some element.
(<unknown>:4986): GStreamer-CRITICAL **:
Trying to dispose element fakesink, but it is in READY instead of the NULL
state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
This problem may also be caused by a refcounting bug in the
application or some element.
(<unknown>:4986): GStreamer-CRITICAL **:
Trying to dispose element typefind, but it is in READY instead of the NULL
state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
This problem may also be caused by a refcounting bug in the
application or some element.
(<unknown>:4986): GStreamer-CRITICAL **:
Trying to dispose element decodebin2, but it is in READY instead of the NULL
state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
This problem may also be caused by a refcounting bug in the
application or some element.
OpenCV ERROR: Unspecified error (unicap: failed to get info for device
)
in function CvCapture_Unicap::initDevice, cvcap_unicap.cpp(138)
Terminating the application...
Segmentation fault (core dumped)
Also in F12 I got a seg fault when trying to authenticate.
Am testing in F13 if it works there I'll give you the opencv versions.
Steven
Original comment by stevenj...@gmail.com
on 11 May 2010 at 12:47
I have solved the problem - work around only.
It is to do with the fact that most distributions have upgraded opencv to
version 2.
According to opencv wikii major version numbers indicate a change in api
structure.
For fedora i have made a compatible rpm for opencv that only installs the
libraries.
So to work properly pam-face-authentication need to be complied against
opencv-devel-1.0.0
Original comment by stevenj...@gmail.com
on 13 May 2010 at 9:41
see http://forums.fedoraforum.org/showthread.php?p=1359447#post1359447
for updated install details
Steven
Original comment by stevenj...@gmail.com
on 13 May 2010 at 9:42
These are being marked as duplicates of 106. Please see/track that bug for
Issues
Original comment by armadefu...@gmail.com
on 8 Mar 2013 at 9:07
Original issue reported on code.google.com by
lgom...@gmail.com
on 9 Feb 2010 at 12:57