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 357343 - crash in Camorama Webcam Viewer: sélection de l'option mi...
crash in Camorama Webcam Viewer: sélection de l'option mi...
Status: RESOLVED DUPLICATE of bug 156333
Product: camorama
Classification: Deprecated
Component: User Interface
unspecified
Other All
: High critical
: ---
Assigned To: Jens Knutson
Jens Knutson
Depends on:
Blocks:
 
 
Reported: 2006-09-23 16:04 UTC by f.metivier
Modified: 2006-09-23 16:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description f.metivier 2006-09-23 16:04:18 UTC
What were you doing when the application crashed?
sélection de l'option miroir


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

Memory status: size: 58064896 vsize: 0 resident: 58064896 share: 0 rss: 15175680 rss_rlim: 0
CPU usage: start_time: 1159027414 rtime: 0 utime: 234 stime: 0 cutime:174 cstime: 0 timeout: 60 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 -1224763728 (LWP 6522)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1224763728 (LWP 6522))

  • #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 Karsten Bräckelmann 2006-09-23 16:14:48 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.


Most likely that infamous crash again...

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