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 364021 - crash in Camorama Webcam Viewer: Ich wollte Laplace ankli...
crash in Camorama Webcam Viewer: Ich wollte Laplace ankli...
Status: RESOLVED DUPLICATE of bug 154867
Product: camorama
Classification: Deprecated
Component: User Interface
unspecified
Other All
: High critical
: ---
Assigned To: Camorama Maintainers
Camorama Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-21 20:29 UTC by mail
Modified: 2006-10-21 20:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description mail 2006-10-21 20:29:01 UTC
What were you doing when the application crashed?
Ich wollte Laplace anklicken


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

Memory status: size: 58552320 vsize: 0 resident: 58552320 share: 0 rss: 13606912 rss_rlim: 0
CPU usage: start_time: 1161462457 rtime: 0 utime: 350 stime: 0 cutime:284 cstime: 0 timeout: 66 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 -1224915280 (LWP 16294)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1224915280 (LWP 16294))

  • #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 André Klapper 2006-10-21 20:33:02 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 issue has been already fixed.

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