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 361922 - crash in Camorama Webcam Viewer: mirror image crashes
crash in Camorama Webcam Viewer: mirror image crashes
Status: RESOLVED DUPLICATE of bug 156333
Product: camorama
Classification: Deprecated
Component: User Interface
unspecified
Other All
: High critical
: ---
Assigned To: Camorama Maintainers
Camorama Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-13 12:15 UTC by aleko52
Modified: 2006-10-13 14:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description aleko52 2006-10-13 12:15:51 UTC
What were you doing when the application crashed?
mirror image crashes


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 69824512 vsize: 0 resident: 69824512 share: 0 rss: 14135296 rss_rlim: 0
CPU usage: start_time: 1160741750 rtime: 0 utime: 320 stime: 0 cutime:255 cstime: 0 timeout: 65 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 -1225128272 (LWP 4770)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1225128272 (LWP 4770))

  • #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 Elijah Newren 2006-10-13 14:06:43 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 Karsten Bräckelmann 2006-10-13 14:46:06 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 ***