[07:57] Hi [08:02] I'm trying to dirty reinstall Ubuntu GNOME after a packaging mishap, but it stays at the "Removing conflicting perating system files..." stage. It's just outputting systemd network refreshes. [08:03] how long have you waited? [08:04] mgedmin: About an hour [08:05] seems like long enough :/ [08:05] I don't know how to debug this -- can you get a shell? [08:05] mgedmin: I had the first 30 minutes since power on for figuring out why Ubiquity closes right after entering user details. [08:06] mgedmin: The trick was to use "sudo ubiquity" [08:06] uhh interesting [08:06] did you launch it from a terminal instead of from a launcher? [08:06] mgedmin: Shell? For SSHing? [08:06] in a livecd session? [08:06] shell as in a terminal where you could run pstreee and see what processes are runnin [08:07] LiveUSB [08:07] Oh I see... [08:07] or dstat to see if any cpu/disk/network i/o is happening [08:07] or, dunno, strace to see what the installer is waiting for [08:08] unfortunately I'm completely unfamiliar with the installer so I don't think I can help interpret whatever you're seeing [08:10] I'm restarting Ubiquity and going through the steps again. I'll reply with an strace output when it happens again. [08:13] mgedmin: Well, it didn't go through the residual OS file removal stage anymore. Weird. [08:14] mgedmin: But so far so good. So far. [08:17] ubiquity crashes some times :( [08:18] rebooting seems to help [08:18] Or just running "sudo ubiquity" like I did. :) [08:19] that shouldn't make a difference? [08:28] Really? Then how come the installer actually got past the user info screen? [08:29] Honestly, I'm not sure anyone knows why it works. I think it's one of those things that shouldn't work but did and we have no idea why. [08:32] OK, the install actually finished! Finally! [09:04] jbicha, ping [09:05] darkxst: hi [09:05] how are things going for yakkety? [09:05] * darkxst grabbing an ISO while I have internet [09:06] I think things are going well [09:06] I am fixing an ancient bug: https://launchpad.net/ubuntu/+source/ubuntu-gnome-wallpapers/16.10.2 [09:07] right, no one ever noticed those! [09:08] I was wondering why my trusty vm had a solid blue background… [09:08] but that might be because of something else [09:09] our .iso didn't actually build yesterday because of a minor transition (the new wallpapers package took several hours to be accepted) [09:10] ive seen some issues with backgrounds in vmware but they work after pressing [09:11] not sure one day matters, I havent been able to get an ISO since June ;( [09:13] Debian testing (!) is already on GNOME 3.22 https://www.0d.be/debian/debian-gnome-3.22-status.html [09:13] great! [09:14] how is gtk 3.22? things settled down following css nodes in 3.20? [09:14] well the MATE maintainer is upset https://sunweavers.net/blog/node/45 [09:15] so apprently not so well [09:15] ? [09:15] except for mate, I think 3.22 has been relatively calm and quiet [09:16] but wasnt mate gtk 2 until recently? [09:16] yes, so the Debian GNOME team wasn't aware that there could be a problem because there never was before [09:21] darkxst: can you set up the yakkety322.html tracker? (it should be ready in git) [09:27] jbicha, didnt I do that? or did I not update the cron job [09:28] well the other pages are working, but that's a new page so maybe that's why it didn't work? [09:28] meh no ssh keys on this laptop [09:28] hold on [09:37] jbicha, right I didnt update cron job [09:38] will run on the hour [09:38] now [10:04] * darkxst still downloading iso :( [10:08] I'm heading out now [10:09] k, I should have internet for the rest of weekend, then back to staff lodge === ericchu_ is now known as ericchu