Bug 342472 – Camorama crashes with Logitech Quickcam Messenger

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 342472 - Camorama crashes with Logitech Quickcam Messenger


Summary:	Camorama crashes with Logitech Quickcam Messenger


Status:	RESOLVED DUPLICATE of bug 156354

Product:	camorama
Classification:	Deprecated
Component:	User Interface
Version:	unspecified
Hardware:	Other Linux

Importance:	High critical
Target Milestone:	---
Assigned To:	Jens Knutson
QA Contact:	Jens Knutson

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-05-21 10:39 UTC by flyn
Modified:	2006-07-04 17:09 UTC

See Also:
GNOME target:	---
GNOME version:	2.13/2.14

Description flyn 2006-05-21 10:39:27 UTC

Distribution: Ubuntu 6.06 (dapper)
Package: camorama
Severity: Normal
Version: GNOME2.14.1 0.17
Gnome-Distributor: Ubuntu
Synopsis: Camorama crashes with Logitech Quickcam Messenger
Bugzilla-Product: camorama
Bugzilla-Component: User Interface
Bugzilla-Version: 0.17
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
Camorama crashes when using large view size + Laplace effect Sobel
effect

Steps to reproduce the crash:
1. Run Camorama after installing the qc-usb-messenger-1.2 driver
2. Choose Laplace effect
3. Choose Sobel effect
4.Change view size to Large
Expected Results:
Camorama crashes

How often does this happen?
Each and every time.

Additional Information:



Debugging Information:

Backtrace was generated from '/usr/bin/camorama'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225340160 (LWP 2778)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 68345

Thread 1 (Thread -1225340160 (LWP 2778))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 ??
#5 ??
#6 ??
#7 ??
#8 ??
#9 ??
#10 ??
#11 ??
#12 ??
#13 ??
#14 ??
#15 ??
#16 ??
#0 __kernel_vsyscall





------- Bug created by bug-buddy at 2006-05-21 10:39 -------


Unknown version 0.17 in product camorama.  Setting version to "unspecified".

Comment 1 Sergej Kotliar 2006-05-22 19:40:57 UTC

Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

Comment 2 flyn 2006-05-22 21:11:33 UTC

Ok, I followed the instructions in the link you gave me, he is the stack trace using Bug Buddy and GDB:

+ Trace 68375

Thread 1 (Thread -1225385216 (LWP 19333))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0#2
#4 ??
#5 ??
#6 ??
#7 ??
#8 ??
#9 ??
#10 ??
#11 ??
#12 ??
#13 ??
#14 ??
#15 ??
#16 ??
#0 __kernel_vsyscall

Comment 3 flyn 2006-05-22 21:18:17 UTC

Just in case, I tried to do this again after installing the generic gtk and gnome debug packages:

+ Trace 68376

Thread 1 (Thread -1225229568 (LWP 19743))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 ??
#5 ??
#6 ??
#7 ??
#8 ??
#9 ??
#10 ??
#11 ??
#12 ??
#13 ??
#14 ??
#15 ??
#16 ??
#0 __kernel_vsyscall
#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 ??
#5 ??
#6 ??
#7 ??
#8 ??
#9 ??
#10 ??
#11 ??
#12 ??
#13 ??
#14 ??
#15 ??
#16 ??

Comment 4 Karsten Bräckelmann 2006-07-04 17:09:56 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


Even without a good stacktrace, according to the description this seem to be a duplicate of bug 156354. Please feel free to re-open this bug immediately, if you do not agree.

*** This bug has been marked as a duplicate of 156354 ***