Bug 356895 – crash in Camorama Webcam Viewer: I'm experimenting the va...

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 356895 - crash in Camorama Webcam Viewer: I'm experimenting the va...


Summary:	crash in Camorama Webcam Viewer: I'm experimenting the va...


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-20 12:47 UTC by otto_grunf
Modified:	2006-09-23 14:00 UTC

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

Description otto_grunf 2006-09-20 12:47:45 UTC

What were you doing when the application crashed?
I'm experimenting the various preferences of the program


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

Memory status: size: 40706048 vsize: 0 resident: 40706048 share: 0 rss: 13901824 rss_rlim: 0
CPU usage: start_time: 1158756360 rtime: 0 utime: 146 stime: 0 cutime:135 cstime: 0 timeout: 11 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 -1225161040 (LWP 10754)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 72824

Thread 1 (Thread -1225161040 (LWP 10754))

#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 ??
#15 ??
#16 ??
#0 __kernel_vsyscall

Comment 1 Sergej Kotliar 2006-09-20 16:57:10 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 14:00: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 ***