[08:35] ping asac [11:04] hallo [11:05] hey micahg [11:05] up already, on a Sunday too ? [11:06] BUGabundo: haven't been to sleep yet :) [11:08] ahh [11:08] that's... bad! [11:09] (firefox-3.6:11673): Gtk-CRITICAL **: gtk_tree_sortable_set_sort_column_id: assertion `GTK_IS_TREE_SORTABLE (sortable)' failed [11:09] [New Thread 0x7f0b55c56950 (LWP 12308)] [11:09] [Thread 0x7f0b55c56950 (LWP 12308) exited] [11:09] Program received signal SIGSEGV, Segmentation fault. [11:09] [Switching to Thread 0x7f0b83f5e710 (LWP 11673)] [11:09] guudie! a reproducebla FF crash [11:11] I think it's a know GTK bug with sort list [11:14] stevel reported a similar bug in ff3.0 [11:14] bug 393005 [11:14] Launchpad bug 393005 in firefox-3.0 "firefox crashes with "gtk_tree_sortable_set_sort_column_id: assertion `GTK_IS_TREE_SORTABLE (sortable)' failed" in file selection dialog" [Critical,Triaged] https://launchpad.net/bugs/393005 [11:14] yeah but it is a GTK known bug [11:14] not a FF one [11:14] several ppl suffeting from it on +1 [11:14] do you have a bug #? [11:15] better change Affects [11:15] no micahg [11:15] not that many gtk bugs eheh [11:15] should be quick to find knowing the error trace [11:16] BUGabundo: bug 391398 [11:16] Launchpad bug 391398 in gtk+2.0 "Applications segfault with gtk+ version 2.17.2 when selecting listbox values" [High,Confirmed] https://launchpad.net/bugs/391398 [11:17] yeah could be it [11:17] how do you think we should do? [11:18] I'm just going to post a comment [11:18] set affect to gtk and leave FF invalid to get extra hits? [11:18] 'cause removing FF will just make ppl file new bugs on Firefox [11:18] well, I can add FF on the gtk bug [11:18] the gtk bug is master [11:19] humm dupe that one, and mark FF invalid I guess [11:19] now that I know what it is, I can just dupe the ff bugs [11:19] great [11:19] see, you should be on +1 too [11:19] eheh [11:19] nah [11:20] I have do work on my Ubuntu install :) [11:21] LOLOL [11:21] I meant the #, not OS version [11:21] ahaha [11:21] very annoying bug, making navigation on the Open PATH bar unusable :(( [11:22] ah [11:22] nah, I don' thave time to read all that [11:26] Were those 2 bugs the same error? [11:29] which too? [11:29] mine and the reported? [11:29] or both you mention? [11:30] no, the 2 I mentioned [11:30] a quick look at trace seems so [11:30] but feel free to download the BT and compare [11:31] the ff bug didn't have a BT [11:31] ahh [11:32] ask steve for one [11:32] or I can reproduce one pretty easy [11:32] well, he'll check the bug in the morning [11:32] and either contribute to it [11:32] just need to get the gdb libs (again) [11:32] or yell at me for duping it :) [11:32] yeah, if it isn't some one will undupe or file a new [11:33] I'm wondering if I should tag the gtk bug metabug [11:34] ask on #-bugs [11:40] hi [11:41] I unduped it [11:41] there was another similar bug with a separate upstream [11:41] which leads me to believe that this one might be different as well [11:41] different symptoms [11:42] ok [11:42] * micahg really needs to get some sleep [11:44] ahah [11:45] its Noon here [11:45] there? [13:26] anyone ever heard of http://www.ksplice.com/ ? upgrading without reboots [13:49] $ firefox-3.6 [13:49] Gdk-ERROR **: The program 'firefox-3.6' received an X Window System error. [13:49] This probably reflects a bug in the program. [13:49] The error was 'BadWindow (invalid Window parameter)'. [13:49] (Details: serial 1853 error_code 3 request_code 20 minor_code 0) [13:49] fta: do you know this one ? [14:35] If I test an extension in the latest ubuntu-mozilla-daily, is it safe to mark the extension as working in 3.5? [14:41] I guess [14:45] BUGabundo: Fair enough, may the fox smite me down if I am wrong :) [14:47] yeah === BUGabundo1 is now known as BUGabundo === asac_ is now known as asac === micahg1 is now known as micahg === micahg1 is now known as micahg [23:34] fta@ix:~ $ firefox-3.6 [23:34] INTERNAL ERROR on Browser End: Could not get the plugin manager [23:34] System error?:: No such file or directory [23:34] asac, ^^ [23:36] hey fta [23:36] back? [23:37] yes [23:37] gasp, same in safe mode [23:38] I need to start 3.6 3 or 4 times for it to work [23:38] --syns does help [23:38] why? [23:38] there's a trace up, in the log here [23:40] ok, not the same