[00:00] sil2100: So... is someone going to set the tested flag to 'yes' so it'll show up in trello? [00:00] ToyKeeper: yeah, once it's ready Saviq will set it to Yes - I think he's finishing up some final tests from his side [00:00] Saviq: right? [00:00] sil2100, is 10 ready to test otherwise? [00:01] sil2100, just starting the rtm testing, but am positive, gimme ½h [00:01] sil2100: Whoa... wait. We're going to try to land something with 19 different bug fixes in it, last-minute, right before the final build? [00:02] ToyKeeper: yep..! [00:02] ;) [00:03] pmcgowan wanted those nifty fixes in along with the blocker fix [00:03] ToyKeeper, if it makes it any easier, they are really self-contained things [00:03] and not huge changes either [00:06] There sure are a lot of them though... we've been aiming for one fix per image, especially near deadlines, not ~20 all in one bundle. Very high-risk even if the individual changes aren't huge. [00:09] slangasek: hi! Would you be around here to kick off a new RTM image when silo 10 gets published and lands in the archive? [00:09] ribru: if you could make sure silo 10 gets published after QA then it would be awesome [00:09] sil2100: what's the eta on that? I can be around this evening but will be away from the computer very shortly [00:10] I really need to EOD now, have to pick up my car at 7 am [00:10] slangasek: let me think: aroung 20 minutes for Saviq to finish testing, ~30 min for ToyKeeper's sign-off, some time for migration... I guess not earler than 1.5h from now? [00:11] sil2100: ok, I should be back around that time [00:11] As a general rule, to get a good estimate, form your best guess (in detail), then double the number and bump up the unit by one. So, if the expectation is 1.5 hours, the realistic expectation would be 3 days. [00:11] Saviq, it's meant to fix https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1381731 ? [00:11] Ubuntu bug 1381731 in ubuntu-system-settings (Ubuntu) "[oobe] Shutdown dialog does not appear in welcome wizard" [High,In progress] [00:11] brendand, it's meant to prepare for the fix in ubuntu-system-settings [00:11] Thanks everyone! [00:11] o/ [00:11] Goodnight [00:12] sil2100: There's no way I can verify 20 bug fixes in 30 minutes, especially since it takes ~15 minutes just to flash and install. [00:13] ToyKeeper, let's not aim to verify them all then [00:13] ToyKeeper, obviously not ideal, but [00:13] ... final image candidate, big high-risk landing, ... don't verify it? Can I retroactively call in sick today? [00:16] brendand: i can help if you guys want [00:16] ToyKeeper, it's more important it doesn't cause any big regressions [00:16] brendand, ToyKeeper, FWIW, I *am* verifying them all [00:17] brendand: If you want to sign off without testing, you're welcome to. :) [00:17] ToyKeeper, i didn't suggest that [00:17] have already done so for vivid, and will for rtm in a moment, after autopilot finishes [00:17] slangasek, if you're still around, could you please publish vivid silo 5 for me [00:23] ToyKeeper, btw you know where to find the sanity tests right? [00:23] Saviq: I'm around to publish things [00:23] ribru, ah, I got used to you being on holidays ;) [00:24] brendand: I think so, but it doesn't hurt to send the link again. [00:24] brendand: Oh, actually I still have it open. [00:24] ToyKeeper, yeah i was about to say :) [00:25] I was planning to pick up a bluetooth headset on my way back from dinner so I can do the sanity tests completely, but it looks like I might not be going at all. [00:25] (should be leaving about now) [00:26] ToyKeeper, you go, i'll deal with the silo and you can test the image after you get back [00:27] brendand: You sure? [00:27] ToyKeeper, yes [00:28] brendand: Okay, I'll get going on the image tests right after the build finishes... [00:28] Saviq, where's that bug olli confirmed? [00:28] brendand, black scopes is it? [00:29] Saviq, i don't see it amongst the million or so fixes in that silo :P [00:29] Saviq, yeah that one [00:29] brendand, yeah, because it does not fix it (or well, not confirmed that it does) [00:29] brendand, I couldn't reproduce, olli didn't have time yet [00:29] Saviq, :/ [00:29] Saviq, now i'm really confused [00:30] brendand, the more important one was different [00:30] Saviq, ok? [00:30] Saviq, enlighten me [00:30] brendand, http://pad.lv/1382039 [00:30] Launchpad bug 1382039 in qtmir (Ubuntu) "[TOPBLOCKER] Apps scope empty on boot" [Critical,In progress] [00:30] Saviq, ahhh ok [00:30] brendand, the other one is bug #1386653 [00:30] bug 1386653 in unity8 (Ubuntu) "[TOPBLOCKER] Scopes fail to launch when the network stack is not up" [Critical,Confirmed] https://launchpad.net/bugs/1386653 [00:31] AP pass, /me goes for testing [00:31] Saviq, i'll focus on those two fixes and regression testing [00:31] Saviq, you make sure the other fixes are verified [00:31] brendand, doing that, + test plan [00:33] lovely, just had a unity8 crash - with 13 and 10 installed [00:47] ribru: ubuntu silo 25 can be freed, it's not up to me, it's up to tvoss doing some testing there, but we can re-do that change if necessary, it's trivial [00:50] ribru: for silo 16 I'll check back with awe and abeato tomorrow, to see whether they tested it. it's a direct upload, so they very well could have. [00:50] arf, maybe not, there's nothing in it [00:50] Saviq, is it just me or has silo 10 somehow removed the autobrightness control on the battery indicator? [00:50] in any case, we'll finish off that landing completely tomorrow, it's simple to test and to build the package [00:50] brendand, hmm just you, is here fine for me [00:51] brendand, care to restart indicator-power [00:51] Saviq, hmm yeah [00:52] Saviq, even after i rebooted it didn't come back though [00:52] Saviq, that's a known bug though i guess? [00:52] brendand, first I've heard of it [00:52] i've got the autobrightness here with silo 10 [00:55] cyphermox: thanks, oh just noticed that one was still utopic as well, doubly should be freed ;-) [00:58] brendand, +1 from me [00:58] verified all the fixes that fix, did not find regressions [00:59] it's still quite crashy though, seems silo 13 did not solve everything [00:59] Saviq, i got a dash crash [01:00] brendand, got a .crash file? [01:01] Saviq, no i didn't keep it [01:01] brendand, yeah, so, crashes and black scopes we will start investigating tomorrow [01:02] brendand, as indeed I did not see stability promised by silo 13 [01:02] Saviq, anyway i'd better go to bed now. we can roll the dice with this one [01:02] but no more than before 10 [01:02] brendand, I'm confident in this one, if that's of any help [01:03] been testing it two days now [01:03] Saviq, take it away [01:03] Saviq, you should probably go to bed too no :) [01:03] ribru, rtm 10 up for publishing please [01:03] Saviq, let ribru handle it [01:03] brendand, beds are for wussies [01:03] ;) [01:03] well i'm a wussie then - night [01:04] o/ [01:04] brendand, thanks [01:05] almost [01:05] ribru, looks like spreadsheet hates us again, did not update the status [01:05] ribru, don't forget to kick an image as soon as 10 (and 13) have landed [01:05] I don't think i can kick rtm images.... [01:05] Checking statuses [01:09] Saviq: this is some new kind of evil from the spreadsheet. usually when "the status doesn't update" there's some field missing that I just fill in. in the last few days I've seen a number of cases where nothing is missing but it just doesn't show up anyway. it's totally fucking bizarre [01:10] ribru, good we're getting something to replace the spreadsheet then :) [01:10] Saviq: and not a moment too soon! [01:10] ok, publishing [02:23] slangasek: OK landing 10 is landed, can you kick an rtm image? [02:23] indeed I can [02:23] slangasek: thanks [02:23] thanks, just got back and was looking for its status [02:25] ribru: running [02:26] slangasek: thanks! [02:26] ToyKeeper: ^^^ looks like the image should be ready for testing on an hour or so [03:24] ribru: So... sometime around now? [03:24] Let's see, did silo 10 land? [03:27] ToyKeeper: it's definitely landed... slangasek ran the image build [03:58] ribru: Are we expecting a notification from imgbot about the build finishing? [03:59] ToyKeeper: i would assume so, but not sure... [04:00] ToyKeeper: can you just try flashing to see if the image is there? My laptop isn't handy [04:01] ribru: It should be image 139? [04:01] ToyKeeper: sounds right i think. [04:02] imgbot: stunt [04:02] * imgbot rolls on its back and purrs [04:02] Hmmm [04:02] 139 is downloading... not sure how long it has been there. [04:31] does 139 have silo 10 & 13? [04:33] ToyKeeper, I can't repro https://bugs.launchpad.net/ubuntu/+source/unity-scope-scopes/+bug/1386653 anymore [04:33] Ubuntu bug 1386653 in unity8 (Ubuntu) "[TOPBLOCKER] Scopes fail to launch when the network stack is not up" [Critical,Confirmed] [04:33] Saviq, ^ [04:33] olli: 139 should have 10 and 13 in it. [04:33] Assuming it passes sanity testing, we'll be sending it to PES and will start on the really detailed testing. [04:35] that's the plan [04:46] ToyKeeper, do you see u8 crashing when working the indicators? [04:46] spec nw-indicator? [04:46] olli: Not yet. [04:47] olli: However, I tried to get u8 to crash for an hour with silo 13 installed, and wasn't able to get it to fail. I got six other crashes, but not u8. [04:47] olli: ... and with 13+10 installed, brendand said he got a unity8 crash. [04:48] hm, i crashed it twice in 1 session [04:48] but can't repro now :/ [04:48] That's worrisome... I had a feeling that 10 might have un-fixed the crash fix in 13. [04:48] * olli brings baby to bed [04:48] In general, the size and hasty landing of silo 10 makes me nervous. [04:51] olli: Ah, there it is. Got unity8 to crash. All I did was accept an incoming call. [04:51] I get the feeling 139 is fail and we'll have to back out silo 10. [04:55] ToyKeeper, interesting [04:56] With three of us trying to crash unity8 for at least an hour each (image 138 + silo 13), it was unshakable. But image 139 is just as crashy as ever. [04:58] olli: Did you see the change list in silo 10? https://trello.com/c/enrjHgsd/ [05:15] I saw it [05:15] if it hadn't landed today it would have landed tomorrow, Saviq just "happened" (sil2000 called him) to show up and fix it today instead of tomorrow [05:16] ToyKeeper, [05:18] mornings [05:18] hey Mirv [05:19] hey olli [05:25] ToyKeeper, not sure if this was only the procedure when you helped with 114... but maybe... it might be more helpful if you could file the bugs (spec. the crashes) before you EOD, rather than pile it up (liek I think we did with 114) [05:25] olli: Yeah, I've been doing it that way ever since. [05:33] awesome! [05:33] I am brainfried, logging off, good luck ToyKeeper! [05:33] Thanks. I can tell you already this failed sanity testing. [05:34] I'm just trying to measure how *much* it failed. [05:35] so I guess I'll locally prepare 010 revert to have something ready when Savi_q and sil2100 wake up in a couple of hours? [05:36] * Mirv does that [05:37] Mirv, Saviq is going to cherry pick from 10 if the whole silo fails [05:37] not sure what though [05:43] right [07:54] good morning === chihchun_afk is now known as chihchun [08:37] sil2100, today will be fun [08:38] brendand: every day is a fun day! [08:38] Wellark, today will be really fun [08:38] brendand: you got some mushrooms stored away for special occasions? [08:39] * Wellark wants whatever brendand has [08:39] Wellark, yeah i think something special is needed ATM [08:39] brendand: *hug* [08:39] Wellark, well that's special [08:40] * brendand needed that [08:42] Fun fun [08:43] So, did silo 10 end up landing? [08:44] I see it did [08:45] sil2100, yes but ToyKeeper found issues still [08:45] I don't see a new image with it though [08:45] sil2100: it did, and it's suspected it _might_ undo the fix from 13, crash wise [08:45] ... [08:45] sil2100, as if 13 either didn't land properly or 10 reverted some aspect of it [08:45] 139 should be ready, no changelog though on ogra's site [08:46] sil2100, i'm testing 139 now [08:46] sil2100, so far i didn't hit any crashes [08:46] ! [08:46] brendand: you know what I want to say now? [08:46] * sil2100 whispers "shipit" [08:47] maybe it's also possible the 13 never fixed it completely [08:47] Mirv, or maybe there are just other crashes around [08:48] brendand: you mentioned yesterday that when you were testing silo 13 that you still encountered crashes, right? [08:52] hmpf [08:52] * ogra_ wonders why the bot stayed quiet [08:54] sil2100, not after i reset the device [09:01] Just hope that indeed we don't have any additional instabilities [09:01] But I suppose that's a risk that management wanted to take [09:02] well, reading selenes summary it seems we got a lot worse [09:05] ogra_, that's not levelling with my my experience here though [09:05] i'm still testing [09:05] it definitely hasn't gotten worse [09:05] just not all the way better maybe [09:05] ah, sounded very pessimistic [09:07] igonre the bot ... it might spit out nonsense soon [09:07] (seems the watchdog on the image build server was killed somehow) [09:11] * popey refrains from commenting on ogra_ making sense [09:11] heh [09:12] http://people.canonical.com/~ogra/touch-image-stats/rtm/139.changes [09:13] in case you still need it [09:13] http://people.canonical.com/~ogra/touch-image-stats/4.changes for vivid [09:15] \o/ [09:15] ogra_: is there a way to distinguish .changes files for vivid from the utopic ones? [09:16] sil2100, via the path ? [09:17] (and usually the bot only announces them next to the image number and distro name) [09:17] Ah, you moved the old ones to 'utopic' [09:17] yeah [09:17] * ogra_ needs to make a script to fix the links of the archived ones [09:21] * ogra_ sees the smoketests and dances ... [09:21] finally [09:22] FWIW, the new image is definitely more stable on mako than what it was yesterday [09:25] yesterday I was quite constantly seeing 100% unity8 CPU usage after a boot, and later a crash (or two), after it possibly stabilized. none of that today. [09:25] http://paste.ubuntu.com/8758270/ [09:25] thats the results of the topafter.log in the unity8 test [09:26] i *think* we have a media-hub problem [09:26] just guessing by these 200% CPU usage [09:26] Oooh, one failure in UITK o/ [09:28] sil2100: \o/ [09:28] o/ [09:28] \o [09:28] well, so it seems your smkoetest clearly exposes the unity8 crash [09:29] Which one? The dashboard one? [09:29] the unity8 smoketest [09:29] I still see the same crashes there indeed [09:30] sil2100, http://paste.ubuntu.com/8758270/ topafter [09:30] hmm [09:30] unhappy firefox [09:31] weird [09:32] after half a connect i get "server not found" in my face [09:32] (all other websites work fine) [09:32] can you gusy connect to the hangout ? [09:34] * ogra_ curses === tvoss|food is now known as tvoss [09:40] sil2100, ping [09:40] tvoss: pong [09:41] sil2100, so what's the promotion status=? [09:41] still crashing [09:41] tvoss: we're still testing [09:41] sil2100, ogra_ please note that 13 never was meant as the silver bullet [09:41] ogra_, still crashing isn't helpful. What exactly is crashing and where? What does the stack trace say? [09:41] tvoss, i have no idea, ask QA [09:42] brendand, ping [09:43] tvoss: everyone is on a call right now... [09:43] tvoss, i have a stack trace here [09:43] you'll get longer answers in a bit [09:43] brendand, shoot [09:43] tvoss, well a crash file anyway [09:43] popey, sure [09:43] tvoss, i need to retrace it [09:47] brendand, no need to, just shoot the crash file [09:52] brendand: tvoss: regarding mako with today's image, I filed bug #1388019, .crash file at http://people.canonical.com/~tjyrinki/unity8_apport/20141031/_usr_bin_unity8.32011.crash [09:53] bug 1388019 in unity8 (Ubuntu) "unity8 crashed with SIGSEGV in core::dbus::Bus::handle_message()" [Undecided,New] https://launchpad.net/bugs/1388019 [09:53] ogra_: so if I've id 5946f7c6-60e2-11e4-be34-fa163e75317b , how do I fetch it? [09:53] Mirv, is mako blocking promotion? [09:54] Mirv, errors.ubuntu.com/oops/ [09:54] so on start up the following crashed unity8 unity8-dash app-launch and scopes scopes runner \o/ [09:55] Mirv, what brendand said [09:55] Mirv, sorry, that's in media-hub client as far as I can see from the crash file [09:55] if the automatic retracer did its work already you should get a stack [09:57] tvoss, http://people.canonical.com/~brendan-donegan/_usr_bin_unity8.32011.crash - careful it's 14MB [09:58] brendand, top of the stack trace points towards qtqml [09:59] tvoss, yeah [09:59] Mirv, ^ ? [10:03] Mirv, i have a few of the media-hub ones here too [10:03] Mirv, ogra_ is there any chance we can get a better stack trace? [10:04] tvoss, only with the m,atchin dbg packages installed [10:04] tvoss, ask pitti, perhaps there is a way to squeeze more info out of the retracer [10:05] ogra_, I will try to retrace locally [10:05] tvoss: http://davmor2.co.uk/~davmor2/unity8-crash/ [10:05] davmor2, you can ignore ubuntu-app-launch ... thats only moaning about a duplicated icon [10:05] (fitbit) [10:05] davmor2, sorry, cannot access the individual files, insufficient permissions [10:06] tvoss: give me 5 [10:06] davmor2, what triggered the crash? [10:06] tvoss: surely mako is not blocking, just in case it's useful (and I don't have krillin) [10:06] tvoss: typing in the simpin [10:06] brendand: ogra_: thanks! no backtrace yet https://errors.ubuntu.com/oops/5946f7c6-60e2-11e4-be34-fa163e75317b [10:07] I was trying /problem/ url [10:07] ogra_: so far I have only unity8 crasah [10:07] Mirv, StackTraceTop points to media-hub though [10:07] brendand: true [10:07] and via media-hub to dbus-cpp [10:07] tvoss, btw, in case that helps unity8 is also crashing during smoke testing ... we have a test that loops ten times over the processlist and CPU usage ... this is how the system looks afterwards http://paste.ubuntu.com/8758270/ [10:08] tvoss: try again [10:09] Mirv, sure, why does that point to dbus-cpp? [10:09] see StacktraceAddressSignature [10:09] it is the lowest in the stack [10:09] ogra_, that's at best a heuristic, sorry [10:09] (well, above libc) [10:09] ogra_, sure, but you want to look at the highest in the stack to assign to a project [10:09] media-hub then i guess [10:10] tvoss: StacktraceTop's first two lines are in libmedia-hub-client.so.2 and the next two lines to libdbus-cpp.so.4, then core::dbus::Bus::handle_message(std::shared_ptr const&) () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 [10:10] and having it hang at 200% CPU in tests as well as always having a media-hub and scoperunner crash file created alongside unity8 also points to one of these three [10:10] Mirv, sure, with that, it segfaults in media-hub obviously [10:12] the issues started somewhere in the 120s [10:12] http://people.canonical.com/~ogra/touch-image-stats/rtm/123.changes [10:12] this looks like we got a *lot* of media related landings there [10:13] https://lists.ubuntu.com/archives/rtm-14.09-changes/2014-October/000753.html perhaps ? [10:14] ogra_, probably, I will look into the stack trace as soon as retracing finished [10:14] davmor2, I'm on the 10th reboot entering pin, no crash for unity8 here? [10:14] and there was a later one in 126 [10:14] http://launchpadlibrarian.net/188170974/media-hub_2.0.0%2B14.10.20141016-0ubuntu1_2.0.0%2B14.10.20141024~rtm-0ubuntu1.diff.gz [10:15] tvoss: I have 2 lock sims and it never fails to crash [10:16] tvoss, sometimes it only fails after a while of usage ... but i could get it pretty reliably in the past when bein fast entering SIM PIN and then quickly the unlock PIN === chihchun is now known as chihchun_afk [10:16] it also happens often when you get a notification for SMS [10:17] ogra_: can you pass us the scoperunner crash file? [10:17] thostr_: it's on the krillin dashboard if anything [10:17] On each test suite [10:19] thostr_, http://people.canonical.com/~ogra/ubuntu-touch/_usr_lib_arm-linux-gnueabihf_unity-scopes_scoperunner.32011.crash [10:19] right, what sil2100 said too [10:19] just click any of the test names and scroll down on http://dashboard.ubuntu-ci:8080/smokeng/utopic/touch_stable/krillin/139:20141031:20141028-3ca60be/649/ [10:21] sil2100, Mirv, so we reverted 10 rtm did we? [10:21] Saviq: no, why? [10:21] sil2100, /me reading the backlog is all [10:21] Saviq: no, it's just an option [10:21] ah ok [10:21] lemme know if I can help [10:22] Saviq: rtm 10 is still in the image, QA is still dogfooding to make sure if it's causing issues or not [10:22] kk [10:22] Saviq: but it has been mentioned that unity8 is still crashing somewhere, but it's currently hard to get a completely objective opinion [10:22] Saviq, could you help retracing http://davmor2.co.uk/~davmor2/unity8-crash/_usr_bin_unity8.32011.crash with all necessary debug packages installed? [10:22] So we're waiting [10:23] tvoss, doing [10:23] Saviq, ack and thx [10:23] I'm going to clear out my /var/crash now so if I see any new ones I know they are fresh [10:24] ogra_: thanks [10:25] thostr_: there is one in http://davmor2.co.uk/~davmor2/unity8-crash/ to incase you want to compare [10:33] davmor2, camera videos not getting thumbnailed, is that a known issue? [10:34] brendand: they are for me [10:34] brendand: let me make one [10:34] davmor2, they appear in the video scope? [10:36] ogra_: the scope runner crash is actually a crash in events scope... [10:37] brendand: http://people.canonical.com/~davmor2/video-tn.png [10:40] thostr_: we're aware of that crash, the dev is spending some time today to fix [10:42] cwayne: are we both talking about https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1382567 [10:42] Ubuntu bug 1382567 in The Savilerow project "Top Crasher: /usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner:*** Error in `/usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner': free(): invalid pointer: ADDR ***" [Undecided,Confirmed] [10:42] thostr_: yes [10:43] ogra_: btw. sorry for sending out G+ announces for landing e-mails with one day delay, but the lists.launchpad.net ML archive refreshes really really slow, usually I need to wait like 2 hours for the mail to appear there [10:43] So I usually need to share it in the morning [10:44] cwayne: let's update the bug and add the rtm tag to make it visible, otherwise we need to answer the same questions x times... [10:45] thostr_: sure, i was thinking of closing that one and putting it in hanloon, and then linking the hanloon bug from there [10:45] cwayne: works for me. [10:46] can you put me and Pete on the watcher list? [10:47] sil2100, np [10:47] thostr_: done [10:47] cwayne: thanks [10:48] brendand, i think jhodapp works on something camera/thumbnail related currently [10:57] * sil2100 needs to AFK for ~1h [11:00] biab restarting server [11:08] tvoss, did you see ToyKeeper 's crash file? https://launchpadlibrarian.net/188758251/_usr_bin_unity8.32011.crash [11:09] brendand, haven't looked at it in depth, yet [11:09] brendand, trying to prove something, gimme 15 [11:10] olli, good morning :) [11:10] that remains to be seen ;) [11:10] heh [11:10] a friendly hello to everyone though [11:10] such optimism :) [11:13] cwayne: what's optimism? [11:13] * ogra_ is really scared to upgrade to 139 ... bu i guess i shoulld to collect more crashers [11:13] davmor2: it's that thing you have right before something goes horribly wrong [11:15] cwayne: nope doesn't ring a bell [11:15] cwayne: are telling me that you expect things to work? [11:15] on occasion [11:17] davmor2, wow [11:17] * ogra_ just entered his sim pin on 139 [11:17] this is gross [11:17] ogra_: did it crash horribly? [11:17] well, it didnt scream or some such ... so not sure about horribly [11:18] but yeah, it went directly to the spinner [11:18] brendand, tvoss: ^ [11:18] and weather still gets me totally wrong data on the dashboard [11:18] (200km away) [11:19] hmm, and all events in the dashboard seem to be in some weird TZ [11:19] definitely not in mine [11:19] ogra_: that's a bug in remote scopes [11:19] ogra_: ditto but that known and isn't going away any time soon so ignore that ;) [11:19] ogra_: that bugs fixed in next custom tar release [11:19] (the events one) [11:19] olli, the short version is that there appear to still be some crashers around [11:19] cwayne, ok [11:19] brendand, I guessed :) [11:20] the weather channel one is that we're not properly passing the lat/lng to remote scopes, so it's using geoip [11:20] and saw it myself, installed 139 shortly after it saw daylight [11:20] ogra_, how many sims do you have installed? [11:20] olli, personally it feels way better than 138 [11:20] same here [11:20] not had a single unity crash yet [11:20] tvoss, two ... one with PIN one without [11:20] davmor2, i just succesfully unlocked two sims [11:21] ogra_, same here, I'm on the 15th reboot and no crash when entering my SIM PIN [11:21] davmor2, you have magic sims [11:21] brendand, and i just succesfully chashed the session unlocking one [11:21] let me reboot [11:21] popey, try switching flight on/off, repeat, maybe do wifi on with flight off [11:21] boom [11:21] brendand: seems ogra_ has the same magic sims in Germany though [11:21] olli: nope ☻ [11:21] but I couldn't repro last night reliably [11:21] ogra_, we should gather all the crashes and figure out where they're coming from and decide what the next course of action is [11:21]