GNOME Bugzilla – Bug 457578
crash in IP Telephony, VoIP and Video Conferencing: It still doesn't work......
Last modified: 2007-07-18 06:38:22 UTC
Version: 2.0.9 What were you doing when the application crashed? It still doesn't work... why? can you provide me more details Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 105787392 vsize: 105787392 resident: 33271808 share: 25681920 rss: 33271808 rss_rlim: 4294967295 CPU usage: start_time: 1184649813 rtime: 1053 utime: 401 stime: 652 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/ekiga' (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 -1208857808 (LWP 3590)] [New Thread -1232565360 (LWP 4340)] [New Thread -1266816112 (LWP 3858)] [New Thread -1266484336 (LWP 3857)] [New Thread -1243280496 (LWP 3713)] [New Thread -1243014256 (LWP 3711)] [New Thread -1242748016 (LWP 3688)] [New Thread -1244660848 (LWP 3681)] [New Thread -1211229296 (LWP 3650)] [New Thread -1210963056 (LWP 3649)] (no debugging symbols found) 0x00b1d402 in __kernel_vsyscall ()
+ Trace 148530
Thread 2 (Thread -1232565360 (LWP 4340))
----------- .xsession-errors --------------------- localuser:Ryen being added to access control list SESSION_MANAGER=local/Node:/tmp/.ICE-unix/3050 ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name libnm_glib_nm_state_cb: dbus returned an error. (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files Xlib: unexpected async reply (sequence 0x2af76)! Xlib: sequence lost (0x306ec > 0x2afb1) in reply type 0xe3! --------------------------------------------------
Eh... it's up to *you* to provide us with more details so we understand what happens... your stacktrace has a very strange look -- I would say it is corrupt. The question you have been asked, and you didn't answer, is : what were you doing when the application crashed?
(In reply to comment #1) Basically, I just setup the ekiga by following the steps on the GUI and eventually reach the camera test setting. I hit on the test button and then the program prompt to reply bugs... the ekiga closed itself.
Ah, this is very interesting ; now I think I know why it crashed : there is a bug in the V4L plugin in 2.0.9. We found the cause and fixed it ; unfortunately, the fix will only be in 2.0.10. *** This bug has been marked as a duplicate of 434223 ***