GNOME Bugzilla – Bug 359655
crash in Ekiga Softphone: I closed the application...
Last modified: 2007-03-02 11:35:01 UTC
Version: 2.0.3 What were you doing when the application crashed? I closed the application (right click from tray, choose quit) Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/ekiga' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us a complete one, with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
I upgraded to edgy yesterday. I tried to close ekiga with : - the main window's menu - Ctrl+Q - the tray menu No crash.
This seems to happen when I boot up without network connectivity, and Ekiga complains it can't start the H.323 and SIP listeners. When I close it after this, it crashes.
Ah ah! That is very interesting... I'll have to try to reproduce later : no time to reboot my work computer now.
I just had a similar crash. - Started Ekiga for the first time. - Did not finish the Configuration but aborted it. - Closed the window. - Closed ekiga using a right click on the panel icon. The stack trace was just a useless as the other one. Will install dbg-syms and try to reproduce it.
hmm, could not reproduce it and there does not seem to be a ekiga-dbg-sym package as far as i can see. Don't have the time to compile it from source and all that. sorry. btw. I'm running Ubuntu Edgy, Ekiga Package Version: 2.0.3-0ubuntu1
Indeed. I also closed the application from the system tray, and I'm also disappointed edgy doesn't have a ready package. I'll recompile when I have the time.
There were a few other reports of the same kind, but I'm unable to reproduce the crash here. A backtrace would be so helpful. Let's hope some of you can provide one before Edgy is released as stable because the bug is really critical...
Could you all make sure that ATK is disabled? There is a bug in ATK (Accessibility ToolKit) making Ekiga crash when exiting...
I recompiled with debugging symbols, yet bug buddy gives me this: ############################### Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 1810432 vsize: 0 resident: 1810432 share: 0 rss: 507904 rss_rlim: 0 CPU usage: start_time: 1160149982 rtime: 0 utime: 131 stime: 0 cutime:1 cstime: 0 timeout: 130 it_real_value: 0 frequency: 271057 Backtrace was generated from '/usr/bin/ekiga' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". ############################### So I guess there's no backtrace, huh? What gives? How do I check for ATK? At least it's linked: toni@toni-laptop:~$ ldd `which ekiga` | grep atk libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0xb79c7000) I guess I'll try to install debug symbols for libatk as well.
Uh, no luck with libatk-dbg. It seems to crash on exit even if I *do* have network connectivity. I think the secret is either to keep it on for a couple of minutes and/or bring your mouse cursor to the system tray icon when its quitting. Here's the backtraceless report again: ########################################## Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 1810432 vsize: 0 resident: 1810432 share: 0 rss: 507904 rss_rlim: 0 CPU usage: start_time: 1160149982 rtime: 0 utime: 131 stime: 0 cutime:1 cstime: 0 timeout: 130 it_real_value: 0 frequency: 272878 Backtrace was generated from '/usr/bin/ekiga' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
I wonder if GDB is not buggy on Edgy. What I meant by disabling ATK is : Go in Desktop Settings, Accessibility: disable everything See this : http://bugzilla.gnome.org/show_bug.cgi?id=349047
Yes, all accessibility is disabled. Though I only (on Ubuntu edgy) System->Preferences->Accessibility->Keyboard and System->Preferences->Assistive Technology Support. Both are disabled.
I don't manage to have any crash... which is annoying : we have a few similar reports :-/
try this: gdb ekiga then type : run make it crash and when it crashes, type : thread apply all bt Perhaps it will give better results. Thanks fro helping!
Created attachment 74280 [details] Alright, here we go!
It is a crash in gnome-vfs : 240 in ghash.c (gdb) backtrace
+ Trace 75227
Not in Ekiga. I will ask seb128 if he can dig further. Thanks!
Toni, are you using GNOME 2.16.1 on an up to date Etch? If not, can you upgrade?
Yes, I am. I dist-upgrade daily.
Could you install libgnomevfs2-0-dbg to get the backtrace? The issue might be a gnomevfs one. For the ekiga package, I've just uploaded a new package revision which will make a "ekiga-dbgsym" available on the "deb http://people.ubuntu.com/~pitti/ddebs edgy main" apt source soon. Maybe you could try to run ekiga with valgrind (https://wiki.ubuntu.com/Valgrind), it might spot an issue?
Backtrace from edgy, I'll try to get one with a debug ekiga package tomorrow: "Program received signal SIGSEGV, Segmentation fault.
+ Trace 75905
Thread 1082665296 (LWP 1118)
*** Bug 362321 has been marked as a duplicate of this bug. ***
*** Bug 361742 has been marked as a duplicate of this bug. ***
*** Bug 361692 has been marked as a duplicate of this bug. ***
*** Bug 361665 has been marked as a duplicate of this bug. ***
*** Bug 361248 has been marked as a duplicate of this bug. ***
*** Bug 361127 has been marked as a duplicate of this bug. ***
*** Bug 361085 has been marked as a duplicate of this bug. ***
*** Bug 360278 has been marked as a duplicate of this bug. ***
*** Bug 359804 has been marked as a duplicate of this bug. ***
*** Bug 360041 has been marked as a duplicate of this bug. ***
*** Bug 359636 has been marked as a duplicate of this bug. ***
*** Bug 358971 has been marked as a duplicate of this bug. ***
*** Bug 359523 has been marked as a duplicate of this bug. ***
*** Bug 359508 has been marked as a duplicate of this bug. ***
*** Bug 359524 has been marked as a duplicate of this bug. ***
*** Bug 357495 has been marked as a duplicate of this bug. ***
*** Bug 362650 has been marked as a duplicate of this bug. ***
obviously confirming; lots of duplicates.
*** Bug 363007 has been marked as a duplicate of this bug. ***
*** Bug 363238 has been marked as a duplicate of this bug. ***
*** Bug 363447 has been marked as a duplicate of this bug. ***
snark, does anybody work on this? the number of duplicates can make this a blocker in a few days... :-/
They narrowed it down to the class and the method from what I can see, but it doesn't seem to be as easy as a typo. J.
Andre, nobody from the Ekiga team is working on this. From what I can see, it doesn't seem to be a bug on our side. Should we reassign to gnome-vfs? I also know seb128 from Ubuntu was investigating, but I do not know more about this.
Reassigning to gnome-vfs. Let's hope it is the problem, most backtraces are unuseful anyway, except one, indicating a crash in gnome-vfs.
I think Jan mistook this issue with a problem in HEAD... I can't even reproduce the issue here, although I "upgraded" to edgy specifically for that :-(
I get the issue every few try, I'm not sure if the backtrace is useful or not and valgrind doesn't work on ekiga here. I can provide debug informations if somebody needs that though
Hmmm... I'm wondering if recompiling ekiga with --disable-gnome wouldn't help : - if it crashes, we're still looking for a solution ; - if it doesn't crash anymore then the problem is in the gnome-specific code (gnome-vfs and gconf notably). Of course, that package would only be for testing, not for distribution ;-)
(In reply to comment #47) > I think Jan mistook this issue with a problem in HEAD... I can't even reproduce > the issue here, although I "upgraded" to edgy specifically for that :-( Right, sorry.
I've rebuilt it with --disable-gnome, after some tries gdb displayed a: "thread_db_get_info: cannot get thread info: generic error (gdb) bt
+ Trace 77315
The backtrace is not useful in that case, seems to be a crasher on exit without gnome libs too though
Then it should be moved to Ekiga again IMHO.
If the --disable-gnome still crashes, things don't look bright for ekiga indeed. Hmmm... does --disable-gnome imply --disable-dbus ? (ldd /usb/bin/ekiga | grep dbus would confirm) If it doesn't then a test with --disable-dbus would be interesting too. Sorry to ask you so much Sebastien, but since I still don't manage to reproduce here :-(
Hi - this is off-topic. I have somewhat unwittingly submitted an Ekiga crash bug which has been marked as a duplicate of this one. Little did I know that submitting my real email address would render it harvestable by spammers. I now get loads of spam in a new email account which was to serve as my spam free account for years to come. How can i delete myself from bugzilla? Søren Gellert
20 dups in 10 days - gnome 2.16.x target.
*** Bug 364096 has been marked as a duplicate of this bug. ***
Gasp... I did see it crash! But couldn't get anything from it :-/ And have been unable to reproduce again since... this bug really doesn't want me to fix it. Nasty. :-(
*** Bug 364176 has been marked as a duplicate of this bug. ***
[OFF-TOPIC] @ Søren Gellert: > I have somewhat unwittingly submitted an Ekiga crash bug which has been > marked as a duplicate of this one. Little did I know that submitting my > real email address would render it harvestable by spammers. that's not correct, this can only happen if you did not enter a real name. If you enter a real name, the email addresses are *only* accessible after logging in to bugzilla. just go to your account preferences and add a realname by visiting http://bugzilla.gnome.org/userprefs.cgi?tab=account and entering a value into the 4th text field. andre [listing https://bugzilla.mozilla.org/show_bug.cgi?id=218917 for reference here.]
(gdb) bt
+ Trace 77818
For me, that doesn't sound to be an Ekiga problem either. Isn't that gdb? I can not reproduce it on Debian. I took 2.0.3, started it, exited about 100 times, nothing wrong...
Also, there is still a backtrace indicating a crash in gnome-vfs. So, for me, it is still a gnome-vfs bug...
it might have been a gdb issue, feel free to reassign to gnome-vfs if you prefer, that will probably not fix the bug faster though
I have seen the problem once in hundred tries... and didn't manage to come out wiser from it... Wouldn't it be worth to "update" ekiga in edgy to a debug package ? Actually, I'm wondering if we haven't two issues here : (1) a bug somewhere in ekiga and/or its dependencies which gives the crash (2) a bug in gdb which makes the first impossible to track
I don't see how to fix this issue unfortunately. I won't reassign to gnome-vfs until we are sure it is a gnome-vfs issue. I will try again tonight to reproduce it.
[Sorry to continue the off-topic response, but I just thought I'd clear something up a little more than Andre did] (In reply to comment #59) > that's not correct, this can only happen if you did not enter a real name. If > you enter a real name, the email addresses are *only* accessible after logging > in to bugzilla. This isn't the whole story either; email addresses are protected as much as possible even if a realname isn't entered. For a user with email addy "foo@bar.com" and no realname will appear to those not logged in as "Comment #23 from foo bar com (points: 73)" (with the comment number and points changing depending on what the comment number is and how many points the user has, obviously) Only people who are logged in are ever shown actual email addresses. And as Andre points out, there are plans to change even that. (Oh, and there's also various smarts for detecting and banning spambots that Olav has implemented.)
*** Bug 364494 has been marked as a duplicate of this bug. ***
If nothing can be done for this bug, I think I will become crazy.
Eh, it's just the 67th comment on this bug number, and we have had only something like a hundred duplicates. I must have launched then closed ekiga thousands of times, and experienced only a single crash... There are several things that can be done : (1) at least one of the many reporters is able to reproduce the crash easily, we get him/her to install a debug package, get a nice backtrace and solve ; (2) we find a common point to the many reporters, which makes us suspect something to trigger the problem -- we are then able to reproduce it ourselves, get a nice backtrace and solve ; (3) we get a continuous flow of useless reports, with no more information and mostly unreproducible crashes : Damien gets crazy :-) We're right on track (3) until now ;-)
the bug already has a backtrace from a debug package, the issue is there is no ekiga symbol there and the gnome-vfs issue is not obvious. valgrind doesn't work for me on ekiga neither. If anybody has some debug idea let me know, the crash happens every few try with a stock user on my edgy desktop
Is it on a machine with high bandwidth? If so, perhaps you could give me an ssh access and I could try various things...
Also, perhaps you could try ekiga -d 4 and post the output of an attempt that crashes ekiga.
*** Bug 364559 has been marked as a duplicate of this bug. ***
*** Bug 364718 has been marked as a duplicate of this bug. ***
*** Bug 364935 has been marked as a duplicate of this bug. ***
I tried to have a look at the differences between ekiga-on-edgy and ekiga-on-whatever else ; here is a list of things which caught my eye : (1) required versions are changed -- probably not dangerous ; (2) launchpad integration -- is it threadsafe ? (3) eggtrayicon transparency -- is it threadsafe ? If someone who is both able to reproduce the crash and able to build packages could try without (2) and (3), that may help rule these out.
*** Bug 365308 has been marked as a duplicate of this bug. ***
*** Bug 365356 has been marked as a duplicate of this bug. ***
*** Bug 365408 has been marked as a duplicate of this bug. ***
*** Bug 365474 has been marked as a duplicate of this bug. ***
*** Bug 365524 has been marked as a duplicate of this bug. ***
*** Bug 365652 has been marked as a duplicate of this bug. ***
Sigh...
http://librarian.launchpad.net/4918987/_usr_bin_ekiga.1000.crash has another backtrace on this (from bug: https://launchpad.net/distros/ubuntu/+source/ekiga/+bug/63348) - unfortunately the bug itself is not very clear (described two issues).
*** Bug 365688 has been marked as a duplicate of this bug. ***
@Daniel it seems to confirm the problem inside gnome-vfs (the backtrace). I wonder if we shouldn't reassign it to gnome-vfs because we have 2 backtraces indicating that the problem is in gnome-vfs-shutdown.
*** Bug 365943 has been marked as a duplicate of this bug. ***
*** Bug 366317 has been marked as a duplicate of this bug. ***
*** Bug 366280 has been marked as a duplicate of this bug. ***
*** Bug 366405 has been marked as a duplicate of this bug. ***
*** Bug 366387 has been marked as a duplicate of this bug. ***
*** Bug 366248 has been marked as a duplicate of this bug. ***
*** Bug 366487 has been marked as a duplicate of this bug. ***
*** Bug 366550 has been marked as a duplicate of this bug. ***
*** Bug 366591 has been marked as a duplicate of this bug. ***
*** Bug 366612 has been marked as a duplicate of this bug. ***
*** Bug 366620 has been marked as a duplicate of this bug. ***
Pfff... we have indications the problem is in gnome_vfs_mime_shutdown. Then why does it crash only with ekiga ? Perhaps this function isn't thread-safe or something like this ? This would explain why it doesn't always crash for those who experience the bug, and why I had it only once in several hundred tries. This is something the gnome-vfs developpers probably know. Let's try to push the bug their way so they have a look : they'll hand it back if they can confirm the issue isn't their. We can't do anything about it anyway as long as our ideas don't get put to the test.
*** Bug 366738 has been marked as a duplicate of this bug. ***
*** Bug 366753 has been marked as a duplicate of this bug. ***
*** Bug 366754 has been marked as a duplicate of this bug. ***
*** Bug 366837 has been marked as a duplicate of this bug. ***
*** Bug 367100 has been marked as a duplicate of this bug. ***
*** Bug 366998 has been marked as a duplicate of this bug. ***
*** Bug 367227 has been marked as a duplicate of this bug. ***
*** Bug 367338 has been marked as a duplicate of this bug. ***
*** Bug 367600 has been marked as a duplicate of this bug. ***
*** Bug 367566 has been marked as a duplicate of this bug. ***
*** Bug 367876 has been marked as a duplicate of this bug. ***
*** Bug 368056 has been marked as a duplicate of this bug. ***
*** Bug 368100 has been marked as a duplicate of this bug. ***
*** Bug 368213 has been marked as a duplicate of this bug. ***
*** Bug 367707 has been marked as a duplicate of this bug. ***
*** Bug 368584 has been marked as a duplicate of this bug. ***
*** Bug 368695 has been marked as a duplicate of this bug. ***
*** Bug 368548 has been marked as a duplicate of this bug. ***
*** Bug 368821 has been marked as a duplicate of this bug. ***
*** Bug 369060 has been marked as a duplicate of this bug. ***
*** Bug 369178 has been marked as a duplicate of this bug. ***
*** Bug 369584 has been marked as a duplicate of this bug. ***
*** Bug 370029 has been marked as a duplicate of this bug. ***
*** Bug 369994 has been marked as a duplicate of this bug. ***
*** Bug 369992 has been marked as a duplicate of this bug. ***
*** Bug 370227 has been marked as a duplicate of this bug. ***
*** Bug 370462 has been marked as a duplicate of this bug. ***
*** Bug 370451 has been marked as a duplicate of this bug. ***
*** Bug 370655 has been marked as a duplicate of this bug. ***
*** Bug 370659 has been marked as a duplicate of this bug. ***
*** Bug 370963 has been marked as a duplicate of this bug. ***
*** Bug 371053 has been marked as a duplicate of this bug. ***
gnome-vfs is only used by the GTK filechooser backend. Would it help if we completely disabled gnome VFS in Ekiga? Can one of the GNOME VFS maintainers have a look? Or better somebody at Ubuntu? This bug is getting really annoying and nobody seems to work on it. Raising severity to BLOCKER. Thanks.
*** Bug 371065 has been marked as a duplicate of this bug. ***
*** Bug 371265 has been marked as a duplicate of this bug. ***
*** Bug 371310 has been marked as a duplicate of this bug. ***
*** Bug 371350 has been marked as a duplicate of this bug. ***
*** Bug 371355 has been marked as a duplicate of this bug. ***
*** Bug 371413 has been marked as a duplicate of this bug. ***
*** Bug 371457 has been marked as a duplicate of this bug. ***
*** Bug 371500 has been marked as a duplicate of this bug. ***
*** Bug 371568 has been marked as a duplicate of this bug. ***
Apparently the only thing we do in gnome_vfs_mime_shutdown () is call xdg_mime_shutdown (). There is no glib foo inside xdg mime so I have no idea where the g_hash_table calls are coming from. Also since ekiga seems to be the only program to have that problem. I am really not sure that is a vfs bug but it might very well be. Anyway I can't really get a clue from the current stack traces.
@Christian Kellner The problem is that Ekiga is not using gnome-vfs at all (what for?). The only thing that Ekiga is using is the file chooser, which in turn is using gnome-vfs. You can grep the source code of Ekiga for gnome-vfs, you will find nothing. Sebastien Bacher from Ubuntu could reproduce the problem but couldn't give much more info. Sebastien, have you progressed on this?
*** Bug 371674 has been marked as a duplicate of this bug. ***
*** Bug 371613 has been marked as a duplicate of this bug. ***
*** Bug 371844 has been marked as a duplicate of this bug. ***
Don't stare too blindly at gnome_vfs_mime_shutdown. Thats from crashes without debug info, so they can't be trusted more than approximately (i.e. we know the crash is in gnome-vfs, maybe in the same file as gnome_vfs_mime_shutdown). The only reliable backtrace we have is from Comment 21, which says that the crash is in a gnome-vfs thread-local data free function (stack_table_destroy). Unfortunately that comment doesn't have the full backtrace including all threads, which might be interesting, because other backtraces show gnome_vfs_mime_shutdown appearing in multiple threads, so there might be a threadsafety issue involved. Searching bugzilla for stack_table_destroy also turns up bug 365647, which is a possible dup in gimp.
Idea : we have two filechoosers, so if : (1) we release them from two different threads (2) the GHashTable is shared between both then we can have thread issues. I'll try to look at (1), can someone check (2) ?
Created attachment 76137 [details] [review] Possible fix This patch adds some protections against g_atexit handlers and thread-local storage finalizers running in the "wrong" order, which could possibly cause a crash like this. If anyone can reproduce this crash it would be nice if they can verify if it fixes the problem or not. Anyway, i'm commiting this to cvs, as it should be a safe change anyway, even if it doesn't fix this problem.
*** Bug 371974 has been marked as a duplicate of this bug. ***
*** Bug 372003 has been marked as a duplicate of this bug. ***
(updating patch status.)
*** Bug 372169 has been marked as a duplicate of this bug. ***
*** Bug 372216 has been marked as a duplicate of this bug. ***
*** Bug 372378 has been marked as a duplicate of this bug. ***
*** Bug 372465 has been marked as a duplicate of this bug. ***
*** Bug 372538 has been marked as a duplicate of this bug. ***
*** Bug 372640 has been marked as a duplicate of this bug. ***
*** Bug 372950 has been marked as a duplicate of this bug. ***
*** Bug 372968 has been marked as a duplicate of this bug. ***
*** Bug 373089 has been marked as a duplicate of this bug. ***
*** Bug 373185 has been marked as a duplicate of this bug. ***
*** Bug 373239 has been marked as a duplicate of this bug. ***
*** Bug 373242 has been marked as a duplicate of this bug. ***
*** Bug 373237 has been marked as a duplicate of this bug. ***
*** Bug 373241 has been marked as a duplicate of this bug. ***
*** Bug 373362 has been marked as a duplicate of this bug. ***
*** Bug 373449 has been marked as a duplicate of this bug. ***
*** Bug 373528 has been marked as a duplicate of this bug. ***
*** Bug 373548 has been marked as a duplicate of this bug. ***
*** Bug 373574 has been marked as a duplicate of this bug. ***
*** Bug 373712 has been marked as a duplicate of this bug. ***
*** Bug 373819 has been marked as a duplicate of this bug. ***
*** Bug 373952 has been marked as a duplicate of this bug. ***
*** Bug 374027 has been marked as a duplicate of this bug. ***
*** Bug 374054 has been marked as a duplicate of this bug. ***
*** Bug 374238 has been marked as a duplicate of this bug. ***
*** Bug 374249 has been marked as a duplicate of this bug. ***
*** Bug 374313 has been marked as a duplicate of this bug. ***
*** Bug 374357 has been marked as a duplicate of this bug. ***
*** Bug 374399 has been marked as a duplicate of this bug. ***
*** Bug 374435 has been marked as a duplicate of this bug. ***
*** Bug 374450 has been marked as a duplicate of this bug. ***
*** Bug 374536 has been marked as a duplicate of this bug. ***
*** Bug 374539 has been marked as a duplicate of this bug. ***
*** Bug 374519 has been marked as a duplicate of this bug. ***
*** Bug 374550 has been marked as a duplicate of this bug. ***
*** Bug 374579 has been marked as a duplicate of this bug. ***
*** Bug 374580 has been marked as a duplicate of this bug. ***
*** Bug 374583 has been marked as a duplicate of this bug. ***
*** Bug 374648 has been marked as a duplicate of this bug. ***
*** Bug 374726 has been marked as a duplicate of this bug. ***
*** Bug 374847 has been marked as a duplicate of this bug. ***
*** Bug 375361 has been marked as a duplicate of this bug. ***
*** Bug 375776 has been marked as a duplicate of this bug. ***
*** Bug 375778 has been marked as a duplicate of this bug. ***
*** Bug 375662 has been marked as a duplicate of this bug. ***
*** Bug 375902 has been marked as a duplicate of this bug. ***
*** Bug 376107 has been marked as a duplicate of this bug. ***
*** Bug 376238 has been marked as a duplicate of this bug. ***
*** Bug 376280 has been marked as a duplicate of this bug. ***
*** Bug 376381 has been marked as a duplicate of this bug. ***
*** Bug 376400 has been marked as a duplicate of this bug. ***
*** Bug 376437 has been marked as a duplicate of this bug. ***
*** Bug 376454 has been marked as a duplicate of this bug. ***
*** Bug 376512 has been marked as a duplicate of this bug. ***
*** Bug 376538 has been marked as a duplicate of this bug. ***
Created attachment 76801 [details] Package with the patch Could someone try to test if ekiga still crashes on exit when the patch is applied? This package should make it pretty easy! We have a possible fix and noone checks if it works, that can't last!
*** Bug 376610 has been marked as a duplicate of this bug. ***
*** Bug 376656 has been marked as a duplicate of this bug. ***
*** Bug 376673 has been marked as a duplicate of this bug. ***
*** Bug 376663 has been marked as a duplicate of this bug. ***
*** Bug 376731 has been marked as a duplicate of this bug. ***
*** Bug 376735 has been marked as a duplicate of this bug. ***
*** Bug 376960 has been marked as a duplicate of this bug. ***
*** Bug 377073 has been marked as a duplicate of this bug. ***
*** Bug 377017 has been marked as a duplicate of this bug. ***
*** Bug 377083 has been marked as a duplicate of this bug. ***
I have tried the patch in http://bugzilla.gnome.org/show_bug.cgi?id=359655#c206. I was unable to produce the crash with the patch installed. I used to be able to prior to installing this patch. I'd say it works for me. I will attach stacktraces from closing via the system tray and the file menu, just in case anyone wants a look.
Created attachment 76857 [details] after patching: close from menu
Created attachment 76858 [details] after patching: close from system tray
*** Bug 377108 has been marked as a duplicate of this bug. ***
Eh, if it's a fix, why not ship fixed packages so we don't receive that many reports ?
Graham Cranston: Btw, thanks for testing. We were in need of testers to make sure it is fixed. Thank you a lot, really!
*** Bug 377201 has been marked as a duplicate of this bug. ***
*** Bug 377178 has been marked as a duplicate of this bug. ***
*** Bug 377200 has been marked as a duplicate of this bug. ***
*** Bug 377373 has been marked as a duplicate of this bug. ***
*** Bug 377616 has been marked as a duplicate of this bug. ***
*** Bug 377618 has been marked as a duplicate of this bug. ***
*** Bug 377823 has been marked as a duplicate of this bug. ***
*** Bug 377764 has been marked as a duplicate of this bug. ***
*** Bug 377840 has been marked as a duplicate of this bug. ***
*** Bug 377916 has been marked as a duplicate of this bug. ***
*** Bug 378118 has been marked as a duplicate of this bug. ***
Do we still doubt the patch is a fix?
I don't know. The Ubuntu guys could perhaps upgrade the pack in Edgy.
*** Bug 378231 has been marked as a duplicate of this bug. ***
*** Bug 378413 has been marked as a duplicate of this bug. ***
*** Bug 378380 has been marked as a duplicate of this bug. ***
*** Bug 378415 has been marked as a duplicate of this bug. ***
*** Bug 378418 has been marked as a duplicate of this bug. ***
*** Bug 378447 has been marked as a duplicate of this bug. ***
*** Bug 378519 has been marked as a duplicate of this bug. ***
*** Bug 378649 has been marked as a duplicate of this bug. ***
*** Bug 378673 has been marked as a duplicate of this bug. ***
*** Bug 378711 has been marked as a duplicate of this bug. ***
*** Bug 378786 has been marked as a duplicate of this bug. ***
*** Bug 378851 has been marked as a duplicate of this bug. ***
*** Bug 378849 has been marked as a duplicate of this bug. ***
*** Bug 378899 has been marked as a duplicate of this bug. ***
*** Bug 378982 has been marked as a duplicate of this bug. ***
Ok, we have a confirmed fix, we hope fixed packages will be uploaded in a few days : let's close.
*** Bug 379073 has been marked as a duplicate of this bug. ***
*** Bug 379201 has been marked as a duplicate of this bug. ***
*** Bug 379291 has been marked as a duplicate of this bug. ***
*** Bug 379295 has been marked as a duplicate of this bug. ***
*** Bug 379363 has been marked as a duplicate of this bug. ***
*** Bug 379360 has been marked as a duplicate of this bug. ***
*** Bug 379423 has been marked as a duplicate of this bug. ***
*** Bug 379445 has been marked as a duplicate of this bug. ***
*** Bug 379512 has been marked as a duplicate of this bug. ***
*** Bug 379531 has been marked as a duplicate of this bug. ***
*** Bug 379551 has been marked as a duplicate of this bug. ***
*** Bug 379592 has been marked as a duplicate of this bug. ***
*** Bug 379536 has been marked as a duplicate of this bug. ***
*** Bug 379743 has been marked as a duplicate of this bug. ***
*** Bug 379948 has been marked as a duplicate of this bug. ***
*** Bug 380326 has been marked as a duplicate of this bug. ***
*** Bug 380531 has been marked as a duplicate of this bug. ***
*** Bug 380882 has been marked as a duplicate of this bug. ***
*** Bug 380964 has been marked as a duplicate of this bug. ***
*** Bug 381004 has been marked as a duplicate of this bug. ***
*** Bug 381075 has been marked as a duplicate of this bug. ***
*** Bug 381080 has been marked as a duplicate of this bug. ***
*** Bug 381160 has been marked as a duplicate of this bug. ***
*** Bug 381220 has been marked as a duplicate of this bug. ***
*** Bug 381278 has been marked as a duplicate of this bug. ***
*** Bug 381355 has been marked as a duplicate of this bug. ***
*** Bug 381486 has been marked as a duplicate of this bug. ***
*** Bug 381658 has been marked as a duplicate of this bug. ***
*** Bug 381779 has been marked as a duplicate of this bug. ***
*** Bug 381816 has been marked as a duplicate of this bug. ***
*** Bug 381819 has been marked as a duplicate of this bug. ***
*** Bug 381834 has been marked as a duplicate of this bug. ***
*** Bug 382339 has been marked as a duplicate of this bug. ***
*** Bug 382449 has been marked as a duplicate of this bug. ***
*** Bug 382497 has been marked as a duplicate of this bug. ***
*** Bug 382630 has been marked as a duplicate of this bug. ***
*** Bug 382661 has been marked as a duplicate of this bug. ***
*** Bug 382718 has been marked as a duplicate of this bug. ***
*** Bug 382753 has been marked as a duplicate of this bug. ***
*** Bug 382957 has been marked as a duplicate of this bug. ***
*** Bug 382990 has been marked as a duplicate of this bug. ***
*** Bug 383036 has been marked as a duplicate of this bug. ***
*** Bug 383139 has been marked as a duplicate of this bug. ***
*** Bug 383446 has been marked as a duplicate of this bug. ***
*** Bug 383564 has been marked as a duplicate of this bug. ***
*** Bug 383625 has been marked as a duplicate of this bug. ***
*** Bug 383632 has been marked as a duplicate of this bug. ***
*** Bug 383762 has been marked as a duplicate of this bug. ***
*** Bug 383857 has been marked as a duplicate of this bug. ***
*** Bug 384328 has been marked as a duplicate of this bug. ***
*** Bug 384137 has been marked as a duplicate of this bug. ***
*** Bug 384133 has been marked as a duplicate of this bug. ***
*** Bug 384402 has been marked as a duplicate of this bug. ***
*** Bug 384443 has been marked as a duplicate of this bug. ***
*** Bug 384458 has been marked as a duplicate of this bug. ***
*** Bug 384502 has been marked as a duplicate of this bug. ***
*** Bug 384525 has been marked as a duplicate of this bug. ***
*** Bug 384708 has been marked as a duplicate of this bug. ***
*** Bug 384824 has been marked as a duplicate of this bug. ***
*** Bug 384914 has been marked as a duplicate of this bug. ***
*** Bug 385112 has been marked as a duplicate of this bug. ***
*** Bug 385182 has been marked as a duplicate of this bug. ***
*** Bug 385241 has been marked as a duplicate of this bug. ***
*** Bug 385570 has been marked as a duplicate of this bug. ***
*** Bug 385581 has been marked as a duplicate of this bug. ***
*** Bug 385892 has been marked as a duplicate of this bug. ***
*** Bug 385972 has been marked as a duplicate of this bug. ***
*** Bug 386375 has been marked as a duplicate of this bug. ***
*** Bug 386374 has been marked as a duplicate of this bug. ***
*** Bug 386326 has been marked as a duplicate of this bug. ***
*** Bug 386566 has been marked as a duplicate of this bug. ***
*** Bug 386656 has been marked as a duplicate of this bug. ***
*** Bug 386830 has been marked as a duplicate of this bug. ***
*** Bug 387023 has been marked as a duplicate of this bug. ***
*** Bug 387016 has been marked as a duplicate of this bug. ***
*** Bug 387058 has been marked as a duplicate of this bug. ***
*** Bug 387250 has been marked as a duplicate of this bug. ***
*** Bug 387270 has been marked as a duplicate of this bug. ***
*** Bug 387342 has been marked as a duplicate of this bug. ***
*** Bug 387305 has been marked as a duplicate of this bug. ***
*** Bug 387522 has been marked as a duplicate of this bug. ***
*** Bug 387524 has been marked as a duplicate of this bug. ***
*** Bug 387571 has been marked as a duplicate of this bug. ***
*** Bug 387592 has been marked as a duplicate of this bug. ***
*** Bug 387754 has been marked as a duplicate of this bug. ***
*** Bug 387718 has been marked as a duplicate of this bug. ***
*** Bug 387802 has been marked as a duplicate of this bug. ***
*** Bug 387912 has been marked as a duplicate of this bug. ***
*** Bug 387977 has been marked as a duplicate of this bug. ***
*** Bug 387982 has been marked as a duplicate of this bug. ***
*** Bug 388014 has been marked as a duplicate of this bug. ***
*** Bug 388189 has been marked as a duplicate of this bug. ***
*** Bug 388278 has been marked as a duplicate of this bug. ***
*** Bug 388664 has been marked as a duplicate of this bug. ***
*** Bug 388694 has been marked as a duplicate of this bug. ***
*** Bug 388746 has been marked as a duplicate of this bug. ***
*** Bug 388750 has been marked as a duplicate of this bug. ***
*** Bug 388811 has been marked as a duplicate of this bug. ***
*** Bug 388854 has been marked as a duplicate of this bug. ***
It's been more than one month now that we have a fix, and still get duplicate reports on duplicate reports. When will fixed packages be finally uploaded?
*** Bug 388856 has been marked as a duplicate of this bug. ***
*** Bug 388752 has been marked as a duplicate of this bug. ***
I've repported 2 bugs on the ubuntu system (one for Ekiga and one for libgnomevfs) https://launchpad.net/distros/ubuntu/+source/ekiga/+bug/76966 https://launchpad.net/distros/ubuntu/+source/gnome-vfs2/+bug/76968 Regards, Yannick
I've closed the bugs on launchpad, opening duplicates for that is not going to make much difference, only annoy bug triagers and people reading them. As explained before stable uploads take some time, especially when people approving them are on holidays like that's the case at the moment. I've subscribed to ekiga on bugzilla and mark duplicates when they come for the moment
I'm so glad you explain us that opening duplicates isn't going to make much difference and only annoy bug triagers and people reading them, right there in a middle of a three hundred dupes bug report! Bug-buddy should report bugs to launchpad. And then the reports should go upstream if they're program bugs. This is how debian works : they deal with their packages, we deal with our bugs. This is cooperation. I'm not annoyed, I'm pissed.
Those duplicates are not opened on purpose. We have discussed with the bugsquad about using bug-buddy or not before edgy and they prefer that we use bug-buddy than not because they prefer to deal with the duplicate than missing all the crashes that would not be sent without bug-buddy. About Debian it works the same way as Ubuntu, bug-buddy is installed by default and it sends bugs to bugzilla.gnome. People can open bugs to launchpad as they do to the Debian BTS, your statement makes no sense. Note that I stopped bug-buddy in favor of apport for feisty some weeks ago, which means that new crashes trigger and Ubuntu bug and are not sent automatically to bugzilla. That will be discussed with the bugsquad again before feisty though It's easy to get frustrated by the new bug-buddy bug fload, non constructive comments like yours are not really useful though, you should better talk to the bugsquad than complain on that bug like you do
*** Bug 388984 has been marked as a duplicate of this bug. ***
*** Bug 388898 has been marked as a duplicate of this bug. ***
*** Bug 388548 has been marked as a duplicate of this bug. ***
*** Bug 389043 has been marked as a duplicate of this bug. ***
*** Bug 389057 has been marked as a duplicate of this bug. ***
*** Bug 389120 has been marked as a duplicate of this bug. ***
*** Bug 389198 has been marked as a duplicate of this bug. ***
*** Bug 389501 has been marked as a duplicate of this bug. ***
*** Bug 389513 has been marked as a duplicate of this bug. ***
*** Bug 389514 has been marked as a duplicate of this bug. ***
*** Bug 389528 has been marked as a duplicate of this bug. ***
*** Bug 389555 has been marked as a duplicate of this bug. ***
*** Bug 389778 has been marked as a duplicate of this bug. ***
*** Bug 389880 has been marked as a duplicate of this bug. ***
*** Bug 389881 has been marked as a duplicate of this bug. ***
*** Bug 389910 has been marked as a duplicate of this bug. ***
*** Bug 389995 has been marked as a duplicate of this bug. ***
*** Bug 390132 has been marked as a duplicate of this bug. ***
*** Bug 390516 has been marked as a duplicate of this bug. ***
*** Bug 390503 has been marked as a duplicate of this bug. ***
*** Bug 390593 has been marked as a duplicate of this bug. ***
*** Bug 390629 has been marked as a duplicate of this bug. ***
*** Bug 390700 has been marked as a duplicate of this bug. ***
*** Bug 390892 has been marked as a duplicate of this bug. ***
*** Bug 390923 has been marked as a duplicate of this bug. ***
*** Bug 391152 has been marked as a duplicate of this bug. ***
*** Bug 391233 has been marked as a duplicate of this bug. ***
*** Bug 391314 has been marked as a duplicate of this bug. ***
*** Bug 391302 has been marked as a duplicate of this bug. ***
*** Bug 391290 has been marked as a duplicate of this bug. ***
*** Bug 391267 has been marked as a duplicate of this bug. ***
*** Bug 391508 has been marked as a duplicate of this bug. ***
*** Bug 391480 has been marked as a duplicate of this bug. ***
*** Bug 391394 has been marked as a duplicate of this bug. ***
*** Bug 391366 has been marked as a duplicate of this bug. ***
seb128: perhaps ubuntu could backport bug 383349 (includes new strings) to 2.16?
*** Bug 390110 has been marked as a duplicate of this bug. ***
*** Bug 391820 has been marked as a duplicate of this bug. ***
*** Bug 391985 has been marked as a duplicate of this bug. ***
*** Bug 391952 has been marked as a duplicate of this bug. ***
*** Bug 392000 has been marked as a duplicate of this bug. ***
*** Bug 392228 has been marked as a duplicate of this bug. ***
*** Bug 392436 has been marked as a duplicate of this bug. ***
*** Bug 392541 has been marked as a duplicate of this bug. ***
*** Bug 392762 has been marked as a duplicate of this bug. ***
*** Bug 392970 has been marked as a duplicate of this bug. ***
*** Bug 393015 has been marked as a duplicate of this bug. ***
*** Bug 393106 has been marked as a duplicate of this bug. ***
*** Bug 393171 has been marked as a duplicate of this bug. ***
*** Bug 393416 has been marked as a duplicate of this bug. ***
*** Bug 393516 has been marked as a duplicate of this bug. ***
*** Bug 393580 has been marked as a duplicate of this bug. ***
*** Bug 393538 has been marked as a duplicate of this bug. ***
*** Bug 394037 has been marked as a duplicate of this bug. ***
*** Bug 394039 has been marked as a duplicate of this bug. ***
*** Bug 395913 has been marked as a duplicate of this bug. ***
A fixed gnome-vfs package has been uploaded.
*** Bug 398488 has been marked as a duplicate of this bug. ***
*** Bug 401813 has been marked as a duplicate of this bug. ***
*** Bug 405430 has been marked as a duplicate of this bug. ***
*** Bug 406451 has been marked as a duplicate of this bug. ***
*** Bug 409079 has been marked as a duplicate of this bug. ***
*** Bug 410379 has been marked as a duplicate of this bug. ***
*** Bug 410510 has been marked as a duplicate of this bug. ***
*** Bug 411292 has been marked as a duplicate of this bug. ***
*** Bug 411289 has been marked as a duplicate of this bug. ***
*** Bug 413808 has been marked as a duplicate of this bug. ***