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 441742 - crash in Camorama Webcam Viewer: Trying Logitech QuickCam...
crash in Camorama Webcam Viewer: Trying Logitech QuickCam...
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: 2007-05-28 06:03 UTC by prp
Modified: 2007-08-22 04:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description prp 2007-05-28 06:03:51 UTC
What were you doing when the application crashed?
Trying Logitech QuickCam Pro 4000 for the first time.
Clicked "Laplace" button in camorama.


Distribution: Gentoo Base System version 1.12.6
Gnome Release: 2.16.2 2007-01-01 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 23252992 vsize: 0 resident: 23252992 share: 0 rss: 11390976 rss_rlim: 0
CPU usage: start_time: 1180332043 rtime: 0 utime: 318 stime: 0 cutime:95 cstime: 0 timeout: 223 it_real_value: 0 frequency: 0

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)
`system-supplied DSO at 0xb7f03000' has disappeared; keeping its symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225320784 (LWP 9404)]
0xb7f03410 in __kernel_vsyscall ()
  • #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 ??
  • #4 ??

Comment 1 Sven Herzberg 2007-08-22 04:19:52 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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