Description of problem: I did nothing. I Just started Ekiga and before I could connecto the the Echo service to test, it crashed (twice). Version-Release number of selected component: ekiga-4.0.0-1.fc18 Additional info: backtrace_rating: 4 cmdline: ekiga crash_function: PVideoInputDevice_V4L2::Open executable: /usr/bin/ekiga kernel: 3.7.4-204.fc18.x86_64 remote_result: NOTFOUND uid: 1002 Truncated backtrace: Thread no. 1 (8 frames) #0 PVideoInputDevice_V4L2::Open at vidinput_v4l2.cxx:224 #1 PVideoInputDevice::CreateOpenedDevice at ptlib/common/videoio.cxx:1410 #2 GMVideoInputManager_ptlib::open at ../lib/engine/components/ptlib/videoinput-manager-ptlib.cpp:129 #3 Ekiga::VideoInputCore::internal_open at ../lib/engine/videoinput/videoinput-core.cpp:525 #4 Ekiga::VideoInputCore::start_preview at ../lib/engine/videoinput/videoinput-core.cpp:312 #5 operator() at /usr/include/boost/function/function_template.hpp:760 #6 run_later_or_back_in_main_helper at ../lib/engine/framework/runtime-glib.cpp:68 #12 gtk_main at gtkmain.c:1257 Potential duplicate: bug 709105
Created attachment 692593 [details] File: backtrace
Created attachment 692594 [details] File: cgroup
Created attachment 692595 [details] File: core_backtrace
Created attachment 692596 [details] File: dso_list
Created attachment 692597 [details] File: environ
Created attachment 692598 [details] File: gconf_subtree
Created attachment 692599 [details] File: limits
Created attachment 692600 [details] File: maps
Created attachment 692601 [details] File: open_fds
Created attachment 692602 [details] File: proc_pid_status
Created attachment 692603 [details] File: smolt_data
Created attachment 692604 [details] File: var_log_messages
ptlib-2.10.10-1.fc17,opal-3.10.10-1.fc17,ekiga-4.0.1-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/ptlib-2.10.10-1.fc17,opal-3.10.10-1.fc17,ekiga-4.0.1-1.fc17
ptlib-2.10.10-1.fc18,opal-3.10.10-1.fc18,ekiga-4.0.1-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/ptlib-2.10.10-1.fc18,opal-3.10.10-1.fc18,ekiga-4.0.1-1.fc18
Package ptlib-2.10.10-1.fc17, opal-3.10.10-1.fc17, ekiga-4.0.1-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing ptlib-2.10.10-1.fc17 opal-3.10.10-1.fc17 ekiga-4.0.1-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-2890/ptlib-2.10.10-1.fc17,opal-3.10.10-1.fc17,ekiga-4.0.1-1.fc17 then log in and leave karma (feedback).
No immediate crashes in F18. Thank you.
I just started ekiga. If I do not have the system connected to the internet, it starts without registering. So, it's obviously something to do with registration or after that. backtrace_rating: 4 Package: ekiga-4.0.1-1.fc18 OS Release: Fedora release 18 (Spherical Cow)
Oops, spoke to soon. My main system is having a problem with avahi after upgrade, so ekiga cannot register. But, if ekiga tries to register, I still get a crash, immediately. I tried to submit a new bug in F18, but bugzilla says it's the identical error (see comment 17). So, this is is not fixed and now applies to F18, too.
Please run ekiga with "ekiga -d 4" and attach the log, also provide the latest crash output with debug symbols.
Created attachment 703123 [details] New log (ekiga -d 4)
I'm not sure what you need, Peter. Is this the unanalyzed core file? Where do I get that? Isn't ekiga already stripped of the debug symbols?
ptlib-2.10.10-1.fc18, opal-3.10.10-1.fc18, ekiga-4.0.1-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
ptlib-2.10.10-1.fc17, opal-3.10.10-1.fc17, ekiga-4.0.1-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
This is not fixed; I thought I explained that. Let me know if I can provided any evidence you need to find the problem. I take it ekiga isn't dying immediately for you?
You need to provide the updated crash output with debug symbols. Details on how to this is provided here http://fedoraproject.org/wiki/StackTraces
Hmm. That page looks old and shows how to generate a backtrace, not "crash output." Isn't abrt supposed to do that for me, anyway? I guess I assumed that was the purpose of the backtrace servers. Don't they have the debug infos? Here's the one I made myself after installing the debuginfo packages: #0 0x00007f2ba735d53b in PVideoInputDevice_V4L2::Open (this=0x2828a90, devName=...) at vidinput_v4l2.cxx:224 #1 0x0000003fd241d7a2 in PVideoInputDevice::CreateOpenedDevice (driverName=..., deviceName=..., startImmediate=false, pluginMgr=0x0) at ptlib/common/videoio.cxx:1410 #2 0x0000003fd304816a in GMVideoInputManager_ptlib::open (this=0x24f9d30, width=176, height=144, fps=<optimized out>) at ../lib/engine/components/ptlib/videoinput-manager-ptlib.cpp:130 #3 0x0000003fd2fd000c in Ekiga::VideoInputCore::internal_open (this=0x24cd5b0, width=176, height=144, fps=30) at ../lib/engine/videoinput/videoinput-core.cpp:529 #4 0x0000003fd2fd0312 in Ekiga::VideoInputCore::start_preview (this=0x24cd5b0) at ../lib/engine/videoinput/videoinput-core.cpp:316 #5 0x0000003fd2f9934b in operator() (this=0x2503c80, this@entry=<error reading variable: value has been optimized out>) at /usr/include/boost/function/function_template.hpp:760 #6 run_later_or_back_in_main_helper (data=0x2503c80, data@entry=<error reading variable: value has been optimized out>) at ../lib/engine/framework/runtime-glib.cpp:68 #7 0x0000003940e485db in g_timeout_dispatch (source=source@entry=0x27d2800, callback=<optimized out>, user_data=<optimized out>) at gmain.c:4026 #8 0x0000003940e47a55 in g_main_dispatch (context=0x23d70a0) at gmain.c:2715 #9 g_main_context_dispatch (context=context@entry=0x23d70a0) at gmain.c:3219 #10 0x0000003940e47d88 in g_main_context_iterate (context=0x23d70a0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3290 #11 0x0000003940e48182 in g_main_loop_run (loop=0x27b2a10) at gmain.c:3484 #12 0x0000003fcf74b077 in IA__gtk_main () at gtkmain.c:1257 #13 0x000000000041ea2f in main (argc=1, argv=0x7fff3397e768) at gui/main.cpp:227 It's still not clear what else you need. I will upload a new log file. Do you want the core file?
Sorry, I didn't catch a new stderr log from the most recent crash, but I'm almost certain it is the same as before.
(In reply to comment #26) > Hmm. That page looks old and shows how to generate a backtrace, not "crash > output." Isn't abrt supposed to do that for me, anyway? I guess I assumed > that was the purpose of the backtrace servers. Don't they have the debug > infos? Backtrace, crash output.. same thing but we need it with the debug symbols resolved rather than raw. abrt is suppose to do it but as you see above if it matches the crash it doesn't update it for newer versions. We need an updated version. The camera works for me without issue on my laptop and ekiga runs and I can get up the output on screen.
There is something interesting in the -d 4 log, at the end: 2013/02/26 12:51:03.329 0:09.349 PVidInDev numerator is zero and denominator is 1, driver bug?? I will look into it. In the meantime, if you can, execute gdb with -d 4 as presented at http://wiki.ekiga.org/index.php/Debugging_Ekiga#How_to_get_a_stack_backtrace_from_a_crash_or_freeze.
Ah, okay, thanks. Not familiar with the lingo, sorry for the confusing. Yeah, this looks a lot more interesting, now. I'll upload the new log file right now. I used it a long long time ago, but didn't have any one to call. And, if I don't let it register, it seems to run fine and it used to work with my camera, too. It just seems to get worse each Fedora release, but I can't figure out why.
Created attachment 704811 [details] new log run via gdb with -d 4 args
(In reply to comment #30) > I used it a long long time ago, but didn't have any one to call. And, if I Yes, this is a problem. You can use it also to call classical phones. It is like Windows and GNU/Linux :) > don't let it register, it seems to run fine and it used to work with my > camera, too. It just seems to get worse each Fedora release, but I can't > figure out why. There were difficult times for ekiga in the past, but now stability and registration are very strong.
(In reply to comment #31) > Created attachment 704811 [details] > new log run via gdb with -d 4 args I see the error, I will take a look. It is a problem related to your driver.
Awesome. I just got avahi working again on my other system and now ekiga runs and registers and seems to work with my camera on that box. Echo test works too. Okay, so could this all just be a driver problem with my camera? Here I was waiting to get Ekiga working before I bought an HD camera when I should have done the reverse. ... hehe, I keep trying post at the same time you do. Okay thanks so much for your help. I don't mean to make you track down a driver problem with my hardware. I'm willing to do it. If you point me in the right direction though, that'd be helpful.
I have to check if it is a driver bug, or ptlib does not take into account the specificity of this driver. I have used a HD camera without problem (but note that ekiga is limited to about 640x480).
Paul, what is the name of your camera? Do you use a special driver for it, or linux's one which comes by default? Does vlc or cheese work with your camera?
Hi Eugen, I haven't done anything special, so I assume it's the default driver. I certainly haven't installed any proprietary driver software. I see "media", videodev, and uvcvideo in loaded kernel modules. Does that help? I don't know about VLC, but cheese works and has worked for at least a year. Yes, I just checked again, hadn't tried it since F18 upgrade, but it's good. (Sorry to hear about the resolution limitation. :-( I had no idea.)
This is fixed with http://sourceforge.net/p/opalvoip/code/29220/
I think the award for the most dreadful web interface to SCM goes to sourceforge. Update incoming shortly
ptlib-2.10.10-2.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/ptlib-2.10.10-2.fc17
ptlib-2.10.10-2.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/ptlib-2.10.10-2.fc18
(In reply to comment #38) > This is fixed with http://sourceforge.net/p/opalvoip/code/29220/ Indeed. I still do not know how to commit/update without being asked each time for the password. Copying it by ssh is forbidden.
Package ptlib-2.10.10-2.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing ptlib-2.10.10-2.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-3575/ptlib-2.10.10-2.fc17 then log in and leave karma (feedback).
:-) Awesome! The new ptlib seems to be working; got registered and tried the camera. Thanks so much, Eugen, that was impressive. I'll try a test call later and leave karma, too. Thank you.
Yep, call-back test worked great, echo test was good. Thank you very much.
ptlib-2.10.10-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
ptlib-2.10.10-2.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.