GNOME Bugzilla – Bug 456014
crash in Camorama Webcam Viewer: J'ai mis l'effet Laplace
Last modified: 2007-08-22 04:20:10 UTC
What were you doing when the application crashed? J'ai mis l'effet Laplace Distribution: Debian lenny/sid Gnome Release: 2.18.2 2007-05-28 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.21-2-686 #1 SMP Mon Jun 25 20:53:36 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 39063552 vsize: 39063552 resident: 18087936 share: 15114240 rss: 18087936 rss_rlim: 4294967295 CPU usage: start_time: 1184184269 rtime: 59 utime: 40 stime: 19 cutime:5 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/camorama' (no debugging symbols found) Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1224862016 (LWP 3718)] (no debugging symbols found) 0xb7f787f2 in ?? () from /lib/ld-linux.so.2
+ Trace 147340
Thread 1 (Thread -1224862016 (LWP 3718))
----------- .xsession-errors (21 sec old) --------------------- /etc/kde3/kdm/Xsession: line 11: /etc/profile: Permission non accordée Xsession: X session started for claude at mercredi 11 juillet 2007, 22:04:11 (UTC+0200) startkde: Starting up... kbuildsycoca running... ASSERT: "!name.isEmpty()" in /tmp/buildd/kdelibs-3.5.7.dfsg.1/./kio/kio/kdirlister.cpp (969) kio_trash: WARNING: couldn't stat /home/claude/.local/share/Trash/files/DEBS OggS-SEEK: at 0 want 350200 got 345536 (diff-requested 350200) OggS-SEEK: at 349632 want 520 got 0 (diff-requested -349112) ** Message: Orage **: Too small icon size, using static icon ** Message: Orage **: Build alarm list: Processed 0 events. Found 0 alarms of which 0 are active. (Searched 0 recurring alarms.) --------------------------------------------------
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 ***