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 356521 - crash in Camorama Webcam Viewer: Switching on Mirror Imag...
crash in Camorama Webcam Viewer: Switching on Mirror Imag...
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-18 11:48 UTC by Simone Tolotti
Modified: 2006-09-23 13:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Simone Tolotti 2006-09-18 11:48:59 UTC 
What were you doing when the application crashed?
Switching on Mirror Image with Philips spc200nc


Distribution: Gentoo Base System version 1.12.5
Gnome Release: 2.16.0 2006-09-17 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 30932992 vsize: 0 resident: 30932992 share: 0 rss: 15667200 rss_rlim: 0
CPU usage: start_time: 1158580012 rtime: 0 utime: 121 stime: 0 cutime:94 cstime: 0 timeout: 27 it_real_value: 0 frequency: 12

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

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

+ Trace 72637

Thread 1 (Thread -1221896528 (LWP 23163))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/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 ??
  • #0 __kernel_vsyscall 






Comment 1


Sergej Kotliar





          2006-09-19 09:28:36 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:11 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 ***