=== jibel_ is now known as jibel [10:21] dm8tbr, so is there a chance you can get us the syslog ? [10:21] ogra_ roped me in here... On current daily-live amd64 ubiquity dies before even displaying the live/install choser. known problem? [10:22] as soon as I get home, but I also created one bug with an image from a few days ago that contained a lot of stuff [10:22] let me see if I can find it [10:22] ah, yeah, that would help :) [10:27] narf don't have my launchpad credentials on this laptop. just a sec [10:27] 1153272 1153266 [10:27] the other one is for network-manager doing very weird stuff and crashing [10:27] bug 1153272 [10:27] I'll be able to try things again once I come home [10:27] bug 1153266 [10:27] come on bot ... [10:27] :)2~ [10:28] slow bot is slow [10:28] heh, yeah [10:28] or dead [10:28] or lobotomized [10:28] heh [10:28] (that's a real setting for supybot, which ubottu is based on. it mutes the bot on a given channel) [10:29] well, i doubt it was actuvely muted [10:29] *actively [10:30] given that the hardware is not totally super ancient (ThinkPad T61p), I guess this should be of interest even if it's somehow hw-related [10:30] yeah [10:31] oh and just in case: it happened with 3 different daily images and two different usb-sticks [10:32] looks like the first one is NM related as well [10:33] interesting, so nm crashes ubiquity [10:34] * dm8tbr puts bets on the intel wifi card [10:34] iw3945 IIRC in that model [10:35] Mar 10 14:49:51 ubuntu ubiquity[3145]: File "/usr/lib/ubiquity/ubiquity/nm.py", line 210, in build_cache [10:35] Mar 10 14:49:51 ubuntu ubiquity[3145]: devices = self.manager.GetDevices() [10:35] thats in the traceback of the first one [10:36] so it dies when talking to NM it seems ... falling over in dbus communication [10:37] if you have a HW switch to disable the wifi i would try another install with it disabled ... if it works you can be pretty sure its the wlan card [10:37] the second bug points to eth0 though [10:38] Mar 10 14:34:13 ubuntu NetworkManager[9700]: (eth0): deactivating device (reason 'managed') [2] [10:38] Mar 10 14:34:13 ubuntu NetworkManager[9700]: [1362926053.564506] [nm-system.c:254] sync_addresses(): (eth0): error -19 returned from rtnl_addr_delete(): Invalid address for specified address family [10:40] interesting enough, killing NM and running dhclient works just fine [10:40] I'll have a look though [10:41] yeah, and a recent log woould be good [10:41] to see if its still the same issue [10:42] should we discuss this still here or does the NM component make it a different problem? [10:51] well, it tears down ubiquity ... [13:07] bug 1153272 [13:07] Launchpad bug 1153272 in ubiquity (Ubuntu) "ubiquity crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name :1.37 was not provided by any .service files" [Medium,New] https://launchpad.net/bugs/1153272 [13:08] ogra: ah, now it works. The bug was marked private, because the information collector thought it had picked up password data in the logs [13:08] ah [13:08] dm8tbr: that's a dupe of our never-ending whoopsie/nm/ConsoleKit timing out. [13:08] still ? [13:09] i thought that was fixed weeks ago [13:09] but it shouldn't be happening on the (20130310) image (from that report) [13:09] right [13:09] xnox: It happened with todays image too [13:10] nm goes into an endles loop of connect/disconnect [13:10] bug 1153266 is now public too [13:10] Launchpad bug 1153266 in network-manager-applet (Ubuntu) "nm-applet crashed with SIGSEGV in add_to_object_array_unique()" [Medium,New] https://launchpad.net/bugs/1153266 [13:14] haha, I think this is an ipv6 problem [13:15] nm_setting_ip6_config_get_dhcp_hostname: assertion NM_IS_SETTING_IP6_CONFIG (setting) failed [13:15] then two more messages and then the kernel says segfault [13:16] I can take this to the NM people, I hang out on their channel anyway. Thoughts? [13:16] ogra_: reading nm.py, we should be more resilient and expect nm to fail. but that shouldn't be bringing the installer down. Plus I have bugs to fix in nm.py to match recent design. [13:16] cyphermox: ^ bug 1153266 [13:16] Launchpad bug 1153266 in network-manager-applet (Ubuntu) "nm-applet crashed with SIGSEGV in add_to_object_array_unique()" [High,Confirmed] https://launchpad.net/bugs/1153266 [13:16] dm8tbr: we have nm people hanging out here as well ;-) [13:16] ah, cyphermox is also here :) [13:16] just noticed :) [13:16] yeah [13:17] let me see if I can find more info than the bug has [13:18] Mar 10 14:36:12 in https://launchpadlibrarian.net/133563713/WifiSyslog.txt [13:18] that's what I see now too [13:18] seems it tanks on trying DHCPv6 [13:19] my router _should_ only send RA, but who knows what Netgear did to it... [13:19] that also explains it why I'm the first to experience the bug and report it... mass v6 deployment and all that [13:20] seems unlikely to be dhcpv6 [13:20] could be the new DUID code though [13:20] (I test ipv6 everyday here) [13:21] http://paste.ubuntu.com/5613583/ [13:21] perhaps I should change the lease and RA timeouts :) [13:21] anyway, I'm going to test something, see if it's DUID [13:31] In ubiquity: "# TODO: DBus exceptions. Catch 'em all." [13:32] cyphermox: let me dump some RA traffic [13:45] attached dump to the ticket [13:45] https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1153266/+attachment/3573991/+files/radvdump.txt [13:45] Launchpad bug 1153266 in network-manager-applet "nm-applet crashed with SIGSEGV in add_to_object_array_unique()" [High,Confirmed] [14:27] dm8tbr: I wonder if it has to do with your particular setup w/ other-flag, so the RAs for addresses and DHCP for dns and stuffs? [14:27] stgraber: you have the rig to test ipv6, would you have time to reproduce this crash? ^^ [14:28] if you tell me what to do I can also do something [14:28] well, we have some automated tests for ipv6 -- we shoud first check if it's easy to reproduce with that [14:28] I could e.g. dump all the ethernet traffic that goes to the system around crash time [14:28] ok [14:29] nah, I don't think it will be necessary [14:29] we do have a stack trace [14:30] andthe three last messages in syslog before the crash [14:54] dm8tbr: I filed the bug upstream, updated LP [15:06] k, thanks [15:06] * dm8tbr feels useful for finding a bug in NM :) [15:12] yay === kentb is now known as kentb-out [22:34] stgraber: I noticed the same problem [22:34] (http://irclogs.ubuntu.com/2013/02/27/%23ubuntu-installer.txt 20:25) [22:35] stgraber: I managed to make it boot *once*, and this happened to be the time I was recording the boot sequence http://youtu.be/Qttov7aTzkA [22:35] I've not since been able to make that happen [22:37] normally I just get a single "error: couldn't send network packet." and that's it