Re: [Bug 63348] Re: ekiga segfaults on start up
Whatever the reasons are for the delay, the fact is that ekiga does not work for a lot of users, right now, on the current ubuntu release, 6.10. And probably *never* has. Maybe when 7.04 is released later this week, the minority of machines affected by the bug will be able to upgrade out of the trouble. Maybe. Point is, a backport of the fix, when it was identified all those months ago, would have saved a lot of folks a lot of trouble. As it is, what seems to have been unnecessary delay in backporting a fix to a known bug has cost both ekiga and ubuntu some goodwill points. I understand this is not particularly down down to you folks at ekiga, so please feel free to forward this email to where it may do some good! Thanks for all the efforts. It sure looks like what I need. I hope to try it out soon :) On Wed, 2007-04-11 at 12:08 +, Snark wrote: 2.0.x releases are bugfix-only releases : cherry-picking makes no sense. -- ekiga segfaults on start up https://bugs.launchpad.net/bugs/63348 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 63348] Re: ekiga segfaults on start up
The fact is that we ekiga developpers develop ekiga. And ubuntu packages ekiga. If packages don't follow the bugfixes releases, then there's nothing we can do except pester that the bug reports come directly to us, giving us undue work. -- ekiga segfaults on start up https://bugs.launchpad.net/bugs/63348 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 63348] Re: ekiga segfaults on start up
hmmm this edgy system is kept up to date, so i guess that means ekiga has been broken for a long time on a lot of systems? ... On Wed, 2007-04-11 at 05:22 +, Snark wrote: 2.0.3 is very old : we're releasing 2.0.9 in a few days! -- ekiga segfaults on start up https://bugs.launchpad.net/bugs/63348 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 63348] Re: ekiga segfaults on start up
No, that mean edgy itself hasn't been kept up to date, and we ekiga developers suffer duplicate reports on duplicate reports although we try to be as reactive as possible for volunteers. Pun intended. -- ekiga segfaults on start up https://bugs.launchpad.net/bugs/63348 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 63348] Re: ekiga segfaults on start up
Ah, my bad -- down to ubuntu then, of course. The bug's in the process of ubuntifying your releases :) Ekiga looks well interesting. I've managed to register (using another system) but on that system the configuration wizard's 'audio devices' test button produces no feedback from the mic. I may just have to wait for the ubuntu wheels to turn ... On Wed, 2007-04-11 at 09:08 +, Snark wrote: No, that mean edgy itself hasn't been kept up to date, and we ekiga developers suffer duplicate reports on duplicate reports although we try to be as reactive as possible for volunteers. Pun intended. -- ekiga segfaults on start up https://bugs.launchpad.net/bugs/63348 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 63348] Re: ekiga segfaults on start up
Unless you are a rolling distro (e.g. gentoo, debian testing) then it is impossible to keep up with bleeding edge packages all the time and what normally happens is that fixes to major problems are cherry picked from later releases (so called backporting). Why not just migrate to the latest thing all the time? With new features come new bugs and sometimes new dependencies. However it does appear that the ekiga in Feisty is only 2.0.3-0ubuntu8.. Snark: You seem to be suggesting that the cause of this problem has been found and fixed. Can you point to the the isolated piece of code that fixes this so that a backport can be released? -- ekiga segfaults on start up https://bugs.launchpad.net/bugs/63348 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 63348] Re: ekiga segfaults on start up
2.0.x releases are bugfix-only releases : cherry-picking makes no sense. -- ekiga segfaults on start up https://bugs.launchpad.net/bugs/63348 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 63348] Re: ekiga segfaults on start up
But the bug description is exactly what my ekiga on edgy does when I try to start it. Everytime! # ekiga Segmentation fault (core dumped) # head /var/crash/_usr_bin_ekiga.1000.crash ProblemType: Crash Date: Wed Apr 11 00:20:06 2007 ** Attachment added: ekiga segfaults on start http://librarian.launchpad.net/7257490/_usr_bin_ekiga.1000.crash -- ekiga segfaults on start up https://bugs.launchpad.net/bugs/63348 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 63348] Re: ekiga segfaults on start up
2.0.3 is very old : we're releasing 2.0.9 in a few days! -- ekiga segfaults on start up https://bugs.launchpad.net/bugs/63348 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 63348] Re: ekiga segfaults on start up
Rejecting ** Changed in: ekiga (Ubuntu) Status: Unconfirmed = Rejected -- ekiga segfaults on start up https://launchpad.net/bugs/63348 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 63348] Re: ekiga segfaults on start up
I can't reproduce this bug in Ubuntu Feisty (Herd 5) ekiga 2.0.3-0ubuntu6 Mark as rejected? -- ekiga segfaults on start up https://launchpad.net/bugs/63348 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 63348] Re: ekiga segfaults on start up
Mark as rejected as you wish, but notice that 2.0.3 is old news already : we're up to 2.0.5! -- ekiga segfaults on start up https://launchpad.net/bugs/63348 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 63348] Re: ekiga segfaults on start up
No, I believe accessibility was off when both crashes occurred (I am vaguely already aware of an ekiga+accessibility bug that has been reported elsewhere). Re: This bug is not clear (from upstream bug) Ouch. I tried my best. I first reported the problem getting towards a month ago it clearly takes time for people to follow up on this stuff. In the intervening time I decided to try ekiga again and received another crash and naively thought they must be connected because I'm not getting very far. I have no current need for a SIP application and was merely trying to be be helpful by systematically starting all the programs in the menu and reporting problems that I found before Edgy's release. If Canonical wants to employ and pay me to produce better bug reports it is free to offer me a job and I'll work with a video camera over my shoulder and spend more time reading the backtraces... As a follow up and can no longer reproduce either problem after half a dozen attempts so I guess we should just mark this bug as rejected. -- ekiga segfaults on start up https://launchpad.net/bugs/63348 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 63348] Re: ekiga segfaults on start up
Hum... the backtraces are quite different - is this really the same problem? -- ekiga segfaults on start up https://launchpad.net/bugs/63348 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 63348] Re: ekiga segfaults on start up
Can we try to dissect the two issues from another? The one seems to be a gnome-vfs issue, the other one connected to pwlib. -- ekiga segfaults on start up https://launchpad.net/bugs/63348 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 63348] Re: ekiga segfaults on start up
However, the 2nd backtrace might bring some light into http://bugzilla.gnome.org/show_bug.cgi?id=359655 ** Changed in: ekiga (Ubuntu) Importance: Undecided = Medium Assignee: (unassigned) = Ubuntu Desktop Bugs -- ekiga segfaults on start up https://launchpad.net/bugs/63348 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 63348] Re: ekiga segfaults on start up
The druid may crash because accessibility is on... It's a bug in atk, where multithreading isn't supported. -- ekiga segfaults on start up https://launchpad.net/bugs/63348 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 63348] Re: ekiga segfaults on start up
Snark: I doubt that to be honest - there's no indication in any of the backtrace, neither atk nor gail are mentioned in it. Sitsofe: do you use accessibility features? -- ekiga segfaults on start up https://launchpad.net/bugs/63348 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 63348] Re: ekiga segfaults on start up
This problem still appears to be here with ekiga 2.0.3-0ubuntu3 ** Attachment added: ekiga crash report http://librarian.launchpad.net/4918987/_usr_bin_ekiga.1000.crash -- ekiga segfaults on start up https://launchpad.net/bugs/63348 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 63348] Re: ekiga segfaults on start up
Here's a backtrace (there doesn't appear to be a dbg package for ekiga). (gdb) thread apply all bt Thread 10 (process 12980): #0 0xe410 in __kernel_vsyscall () #1 0xb65eba8c in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0 #2 0xb72985b3 in PSyncPoint::Wait () from /usr/lib/libpt.so.1.10.2 #3 0x08162cd4 in ?? () #4 0x08162cbc in ?? () #5 0xb589a390 in ?? () #6 0xb703abe4 in ?? () from /usr/lib/libopal.so.2.2 #7 0x0003 in ?? () #8 0xb72e1fd5 in typeinfo name for PDictionaryPOrdinalKey, PReadWriteMutex::Nest () from /usr/lib/libpt.so.1.10.2 #9 0xb589a398 in ?? () #10 0xb68e6015 in OpalManager::GarbageCollection () from /usr/lib/libopal.so.2.2 #11 0x08162b8c in ?? () #12 0x08100588 in vtable for PTime () #13 0x451fb384 in ?? () #14 0x00075511 in ?? () #15 0x451fb384 in ?? () #16 0x1ca44a68 in ?? () #17 0x in ?? () ---Type return to continue, or q return to quit--- Thread 9 (process 12981): #0 0xe410 in __kernel_vsyscall () #1 0xb64622e1 in ___newselect_nocancel () from /lib/tls/i686/cmov/libc.so.6 #2 0xb7297ac0 in PHouseKeepingThread::Main () from /usr/lib/libpt.so.1.10.2 #3 0x0013 in ?? () #4 0x08506650 in ?? () #5 0x in ?? () Thread 8 (process 13118): #0 0xe410 in __kernel_vsyscall () #1 0xb645f7c3 in *__GI___poll () from /lib/tls/i686/cmov/libc.so.6 #2 0xb743b883 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0xb743bbf9 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #4 0xb77b2e62 in e_book_get_type () from /usr/lib/libebook-1.2.so.9 #5 0xb745641f in g_thread_create_full () from /usr/lib/libglib-2.0.so.0 #6 0xb65e8504 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #7 0xb64694de in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 7 (process 13120): #0 0xe410 in __kernel_vsyscall () #1 0xb645f7c3 in *__GI___poll () from /lib/tls/i686/cmov/libc.so.6 #2 0xb743b883 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 ---Type return to continue, or q return to quit--- #3 0xb743bbf9 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #4 0xb74ff7e0 in link_set_io_thread () from /usr/lib/libORBit-2.so.0 #5 0xb745641f in g_thread_create_full () from /usr/lib/libglib-2.0.so.0 #6 0xb65e8504 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #7 0xb64694de in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 6 (process 13378): #0 0xe410 in __kernel_vsyscall () #1 0xb64622e1 in ___newselect_nocancel () from /lib/tls/i686/cmov/libc.so.6 #2 0xb72973d8 in PThread::PXBlockOnIO () from /usr/lib/libpt.so.1.10.2 #3 0x0024 in ?? () #4 0x083f7518 in ?? () #5 0x083f75a0 in ?? () #6 0x0841b4e0 in ?? () #7 0x in ?? () Thread 5 (process 13379): #0 0xe410 in __kernel_vsyscall () #1 0xb64622e1 in ___newselect_nocancel () from /lib/tls/i686/cmov/libc.so.6 #2 0xb7284a30 in PSocket::Select () from /usr/lib/libpt.so.1.10.2 #3 0x0028 in ?? () #4 0x083f7628 in ?? () #5 0x084252e0 in ?? () ---Type return to continue, or q return to quit--- #6 0x08425368 in ?? () #7 0x in ?? () Thread 4 (process 13382): #0 0xe410 in __kernel_vsyscall () #1 0xb65eba8c in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0 #2 0xb74bf113 in ?? () from /usr/lib/libgthread-2.0.so.0 #3 0xb2102ee8 in ?? () #4 0x0813d4a0 in ?? () #5 0xb42643b8 in ?? () #6 0xb749e1e4 in ?? () from /usr/lib/libglib-2.0.so.0 #7 0xb65eacc0 in __pthread_mutex_unlock_usercnt () from /lib/tls/i686/cmov/libpthread.so.0 #8 0xb42643c8 in ?? () #9 0xb7447e7f in g_queue_peek_tail_link () from /usr/lib/libglib-2.0.so.0 Previous frame inner to this frame (corrupt stack?) Thread 3 (process 13383): #0 0xe410 in __kernel_vsyscall () #1 0xb65eba8c in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0 #2 0xb74bf113 in ?? () from /usr/lib/libgthread-2.0.so.0 #3 0xb2102ee8 in ?? () ---Type return to continue, or q return to quit--- #4 0x0813d4a0 in ?? () #5 0xb4a653b8 in ?? () #6 0xb749e1e4 in ?? () from /usr/lib/libglib-2.0.so.0 #7 0xb65eacc0 in __pthread_mutex_unlock_usercnt () from /lib/tls/i686/cmov/libpthread.so.0 #8 0xb4a653c8 in ?? () #9 0xb7447e7f in g_queue_peek_tail_link () from /usr/lib/libglib-2.0.so.0 Previous frame inner to this frame (corrupt stack?) Thread 2 (process 13384): #0 0xe410 in __kernel_vsyscall () #1 0xb65eba8c in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0 #2 0xb74bf113 in ?? () from /usr/lib/libgthread-2.0.so.0 #3 0xb2102ee8 in ?? () #4 0x0813d4a0 in ?? () #5 0xb2a613b8 in ?? () #6 0xb74bef75 in ?? () from /usr/lib/libgthread-2.0.so.0 #7 0x0002 in ?? () #8 0xb749e1e4 in ?? () from /usr/lib/libglib-2.0.so.0 #9 0xb2a613f8 in ?? () #10 0xb7447e7f in g_queue_peek_tail_link () from /usr/lib/libglib-2.0.so.0 #11 0xb741bb41 in g_async_queue_sort () from /usr/lib/libglib-2.0.so.0 #12 0xb7457f73 in g_thread_pool_push () from
