Bug 354501 – crash in Camorama Webcam Viewer: Click Effect Mirror imag...

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 354501 - crash in Camorama Webcam Viewer: Click Effect Mirror imag...


Summary:	crash in Camorama Webcam Viewer: Click Effect Mirror imag...


Status:	RESOLVED DUPLICATE of bug 156333

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-09-05 19:16 UTC by Perfecto Martís Flórez
Modified:	2006-09-23 13:54 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description Perfecto Martís Flórez 2006-09-05 19:16:11 UTC

What were you doing when the application crashed?
Click Effect Mirror image and when I saw nothing happens click again and again


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.15.92

Memory status: size: 69496832 vsize: 0 resident: 69496832 share: 0 rss: 14131200 rss_rlim: 0
CPU usage: start_time: 1157483488 rtime: 0 utime: 1390 stime: 0 cutime:1231 cstime: 0 timeout: 159 it_real_value: 0 frequency: 0

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 -1224636752 (LWP 11326)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 71662

Thread 1 (Thread -1224636752 (LWP 11326))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_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 ??
#0 __kernel_vsyscall

Comment 1 Sergej Kotliar 2006-09-06 00:58:53 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 Sergej Kotliar 2006-09-23 13:54:23 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.


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