[16:33] wxl: chrisccoulson broke Firefox on Lubuntu 16.04 :P [16:33] wxl: Subscribed Lubuntu Packages Team to bug 1671273 [16:33] bug 1671273 in firefox (Ubuntu) " PulseAudio requirement breaks Firefox on ALSA-only systems" [High,Confirmed] https://launchpad.net/bugs/1671273 [16:33] no one's maintaining alsa? [16:35] wxl: Don't get me started. YOU, sir, have said MANY times that Pulseaudio sucks, go ALSA... :P :P :P [16:35] wxl: And not in upstream Firefox, no [16:35] tsimonq2: that's beside the point. i'm disagreeing with the wording that it's not maintained. [16:35] oh i see support in firefox is unmaintained [16:35] ah well [16:35] wxl: Maybe Alsa is still maintained, but not in Firefox anymore [16:35] Yeah [16:35] itme to switch browsers [16:35] Bah bah bah [16:35] No no no [16:36] Make pulseaudio a hard dep :P [16:36] you'd rather have a crap load of pulse additions than keep the footprint small? [16:36] i can't say i agree [16:36] i'd put that up for discussion on the mailing list [16:37] wxl: I will. [16:37] we CAN still do chrom*IUM* on i386 [16:37] really though i'd also consider figuring out a solution to not using recommends [16:38] it's really a difficult to sustain policy [18:12] wxl: So I think this whole ALSA thing makes one thing clear [18:12] ? [18:13] wxl: We should really pay someone with the technical ability to poke around in Firefox and know what they are doing to help maintain ALSA [18:13] wxl: And for that we need donations. [18:13] wxl: Status update? [18:14] wxl: (or in general be able to throw money at things so that they can be maintained) [18:14] oh man that's still a ways away [18:14] wxl: How far away? [18:15] months, years [18:15] Aghhhhhhhhhh [18:17] wxl: What are you waiting on? [18:17] tsimonq2: legal help [18:17] unless you have money to pay for it [18:17] No I don't [18:17] well there you go [18:17] wait [18:17] wxl: Like a FSF lawyer or something like that? [18:18] https://www.softwarefreedom.org/ [19:21] bug 1675127 looks really nasty [19:21] bug 1675127 in ubiquity (Ubuntu) "ubiquity crashed with TypeError in __new__(): 'NoneType' object is not iterable" [Medium,New] https://launchpad.net/bugs/1675127 [19:23] lynorian: Can you confirm it? [19:23] I reported it [19:23] Oh :P [19:24] wxl: Thoughts? ^^^^^^^^^^^^^^^ [19:25] this might be hardware specific to a wierd setup should I try to install with no network first [19:28] tsimonq2: i'd suggest trying to reproduce it again [19:29] I did try to reproduce it again and was able to before I even reported it with the exact same setup [19:30] ok so it' snot a fluke [19:31] and we know that we can't reproduce it with older versions, right? [19:31] I have not tried in a bit on that hardware in that setup with usb wifi [19:31] I have for like 16.04 or 16.10 but not recent dailies [19:31] try alpha 2 [19:32] ok [19:32] not beta 1? [19:32] well [19:32] should be the same i imagine [19:32] this failed on 17.04.7 [19:33] alpha 2 is 17.04.4 [19:33] beta 1 is also 17.04.7 [19:33] ah version of ubiquity now I get it [19:34] same with daily [19:34] so i can assume beta 2 is also 17.04.7 [19:35] wxl yes my bug report shows that [19:38] lynorian: this occured when trying to connect to wireless, right? no problem otherwise? [19:38] yes I could not see if there were other problems [19:38] as it crashed ubiquity entirely [19:38] did you try with ethernet only to confirm you did not have the problem if wifi wasn't being employed? [19:39] not quite yet [19:39] let's double check that [19:39] looks like an update of netcfg happened in 17.0.3 http://changelogs.ubuntu.com/changelogs/pool/main/u/ubiquity/ubiquity_17.04.7/changelog [19:40] wxl I was able to connect to internet with the cable to report the bug [19:41] and unfortunately, we don't really have an iso with 16.10.14 yes but it would be good to know that it doesn't happen at all, just to be extra sure [19:42] if we can confirm it is indeed with wireless, then i'd ensure that it also happens with other flavors, especially ubuntu proper [19:42] wxl got to partitioning at least [19:42] and if it fails there, then we can sound the alarm all around the world :) [19:43] is there a way to have virtualbox directly access the wifi card? [19:44] wxl not on this box with amd=64 no vtx [19:44] hence why I built my awesome hypervisor [19:44] well i was thinking of a testcase we may be able to build to allow a wider range of users to do things [19:44] I have not done much to get physical passthrough working [19:45] I know this desktop supports it probably just have not done it [19:45] well actually [19:46] this happens early.. before the actual partitioning [19:46] so anyone should be able to run it on any machine without affecting their existing install [19:46] wxl yep [19:46] that said, i'll try to do something tonight [19:46] but tsimonq2 could help too :) [19:46] I have another laptop I could try but argh did I not charge that [19:47] it has one quite bad wifi card that I hate but I could use the same usb one [19:51] wxl booted into install on ethernet [19:54] this probably might explain why no one ran into this earlier though [19:58] it did pass running the test with ethernet on same hardware so should I put that on the tracker? [20:00] yes plese [20:01] looks like this is a nm issue of some kind https://launchpadlibrarian.net/311914177/UbiquityDebug.txt [20:08] wxl I agree with that or in how ubiquity tries to integrate nm into the installer [20:09] lynorian: can you check alpha 2? [20:09] I will [20:29] this may be my usb wifi is breaking [20:29] hard time even getting power to it [20:36] that's why it would be good to test on another machine [20:41] wxl yeah I mean I could use the network on this desktop with it [20:41] lynorian: with built in wifi? [20:42] wxl I am starting to wonder if that ancient wifi still is picking up electrical signal [20:43] I was testing it on a 7.5 year old really heavily used laptop with an even older wifi adapter like 12 years we have had it well it is I think technically proprity of time warner to get wifi working with a computer my mom used with windows ME on it [20:43] oh wow [20:43] suffice it to say it's probably at least an edge case XD [20:52] time to test the laptop with the really wierd aweak attena [20:52] but is a ton newer [20:57] -queuebot:#lubuntu-devel- Unapproved: makedev (zesty-proposed/universe) [2.3.1-93ubuntu1 => 2.3.1-93ubuntu2] (lubuntu) [21:09] wxl well this laptop I did not research and has a bad wifi chip but the installer did not crash [21:09] well at least that is better [21:28] oh wow I need to force it to use the right attena === acheronUK is now known as acheronuk [22:09] lynorian: so not reproducible on other hardware? [22:10] wxl yes [22:10] I cannot reproduce on any other hardware I have [22:10] annoying [22:10] hat ethose kind [22:17] lynorian: just make sure there's comments on the bugs, thx :) [22:28] wxl thank you [22:57] * tsimonq2 stretches [22:57] I needed that nap. [22:57] Anyways... [22:59] wxl: I really really hate this schedule. Do not divorce from your wife, and if you were to ever even think about it, not until Sierra is 18. Seriously, this sucks. [22:59] tsimonq2: don't worry, i won't. :) [23:00] wxl: So no, unfortunately I CAN'T test. I'm at my mom's stuck on this Chromebook until Friday [23:00] tsimonq2: well, we're almost done anyways. but release notes are yours! :) [23:00] tsimonq2: tl;dr on lynorian's bug i think it's very specific to that hardware [23:01] wxl: Oh shoot, did I tell you about Rafael messing with the slideshow? [23:01] uh [23:01] no [23:02] wxl: Well it's out of date. [23:02] i knew that [23:02] henk's email was very complete in that regard :) [23:02] wxl: So I guess we'll still have a slideshow that has 16.10 and lubuntu.me and LSC still on there :/ [23:02] s/me/net/ [23:02] yep [23:02] so he IS fixing it? [23:03] He's working on it. [23:03] Oh I have a bug on needing to get the new website on it [23:05] wxl: So I wanted to ask you. I had zero clue about this pulse/alsa thing before this Firefox bug. I know the basics on our stack (kernel, core utilities, GTK, GUI applications)) but what's the breakdown on other parts of the stack? [23:06] well you're asking about the sound stack essentially right? [23:06] wxl: I'm being broad here but that's a good start :) [23:08] well [23:08] i guess it doesn't have too be too complicated [23:09] i guess x is kind of similar [23:09] it's a server that takes clients and serves as a bridge to the kernel modules for display, keyboard, mouse, etc. [23:09] the "sound server" does the exact same thing [23:10] but the clients are generally applications, e.g. audacious [23:10] and the kernel modules only relate to audio hardware [23:10] ultimately, across the whole of the linux domain, i know of only two actual sound servers [23:10] 1. ALSA [23:10] 2. OSS [23:11] the others "sound servers" basically use those actual sound servers as middleware [23:11] two of those are: [23:11] 1. PulseAudio [23:11] 2. JACK [23:11] although JACK can also work with PA, too [23:12] Ah, ok. [23:12] wxl: How bloated is Pulse compared to just using ALSA directly? [23:12] tsimonq2: is it a lot? no. but it counts for something [23:13] wxl: Then sell it to me -- why do we need to use ALSA and not Pulseaudio + ALSA? [23:13] installed size is 6 times greater with pulseaudio [23:14] but installed size of alsabase is 500 so XD [23:14] pulseaudio can better handle complex cases including mutiple clients simultaneously accessing the devices [23:14] wxl: Don't forget about the whole "When PA works, it's great. When it breaks, good freaking luck" part. :P [23:14] totally that [23:15] i cannot tell you how many sound issues i've fixed by removing PA :) [23:15] the fact that it is a layer on top of ALSA can lead to a great degree of confusion [23:15] Well the good news is if it's a dep of things, you can still keep it from autospawning, thus getting the same result. [23:16] :) [23:16] i see that ALSA is generally a good choice for the average user [23:16] it is complex cases that require something like PA or JACK [23:16] or depending on what they are, some hardcore asoundrc hacking [23:17] JACK is more for the audio advanced group, UbuntuStudio people. PA is useful if you have bluetooth audio or whatever. [23:18] wxl: So if Pulseaudio is the thing with bluetooth audio or whatever, why do we ship bluetooth support? :P [23:18] yeah i haven't found it any more helpful with bluetooth [23:18] wxl: You can do it with ALSA? [23:19] sure [23:19] like i said, i do [23:20] Oh [23:20] Ok [23:20] but i'll tell you what, when it comes to doing audio production, i 1000000% use JACK [23:20] Gotcha :) [23:20] the only reason i've ever installed pulseaudio was because i couldn't find any easy way to route web browser strems through JACK using ALSA only [23:20] but no one does goofy crap like that besides me :) [23:21] wxl: With PA I can use another computer's sound system, can you do that with Alsa?! :---D [23:21] right right [23:21] could with JACK :) [23:21] Unit193: can you do it with 0 latency??? XD [23:23] honestly though i don't consider PA totally evil. it's (generally) worked well for me in kubuntu. but i generally recommend to people not to install it unless they have to or unless their particular flavor of their particular distro really supports it [23:23] wxl: Ok, I get the whole ALSA thing now. Now, as a Firefox user, I think we should continue shipping Firefox because it's bore lightweight than that RAM hog that is Chromium. So... why Chromium? [23:23] I do not notice that much difference but have really simple setups [23:23] also keep in mind that bluetooth is not ONLY used for audio [23:23] s/bore/more/ [23:23] yeah there are bluetooth keyboards and mice [23:24] i've seen lots of tests on firefox/chromium and ultimately have found every one of them to be biased in some way or another [23:24] i think the conclusion i've come to reach is that they're both ram hogs [23:25] or the content to run in javascript is too bloated and not simple [23:25] also i have had better experiences in general with chromium than firefox [23:25] right [23:25] if more people used static site generators would we have this problem? [23:25] here here lynorian :) [23:26] Hahahaha [23:28] wxl: So why a browser that is a RAM hog? Why can't we just go with a lightweight browser? [23:29] lynorian: Hey, any chance you can knock out the last ISO test? [23:30] lynorian: http://iso.qa.ubuntu.com/qatracker/milestones/374/builds/144355/testcases/1301/results [23:30] tsimonq2, I just did [23:30] lynorian: Oh ok [23:30] lynorian: Yay [23:32] -queuebot:#lubuntu-devel- Builds: Lubuntu Alternate amd64 [Zesty Beta 2] has been marked as ready [23:32] -queuebot:#lubuntu-devel- Builds: Lubuntu Desktop amd64 [Zesty Beta 2] has been marked as ready [23:32] -queuebot:#lubuntu-devel- Builds: Lubuntu Alternate i386 [Zesty Beta 2] has been marked as ready [23:32] -queuebot:#lubuntu-devel- Builds: Lubuntu Desktop i386 [Zesty Beta 2] has been marked as ready [23:32] wxl, lynorian: Done :) ^ [23:32] tsimonq2: we can go with a lightweight browser. it has been suggested many times [23:33] um [23:33] ok now everyone go test kubuntu :) [23:33] tsimonq2: it's called xombrero [23:36] wxl: Ok, so, Mr. QA guy, go ask the list for testing. :) [23:37] tsimonq2: for testing what? i thought you were done mr. release manager? :) [23:37] wxl: For your browser pick. [23:37] yeah not going down that road again [23:37] ultimately people are just going to pick whta they like [23:37] i've done this before [23:38] wxl: But why switch off of Firefox then? :)) [23:38] tsimonq2: cuz ppl being booboo butts about alsa [23:39] wxl: Then how do we do that? [23:39] wxl: Should we just go for it? :P [23:39] Because wxl likes chromium. "< wxl> ultimately people are just going to pick whta they like" :--D [23:39] exactly!!! [23:40] tsimonq2: well, right now we have pulseaudio so i guess it doesn't matter :/ [23:40] Unit193: So we just switch and when people complain, say "sudo apt install chromium-browser"? :P [23:40] we really should get rid of PA [23:40] and if infinity's going to make chrisccoulson stick the ALSA code back in, then we should be good [23:41] at least until we start having problems [23:41] wxl: You know what would be just awful? If we hacked Ubiquity to make the user pick the browser they want installed by default. XD [23:43] tsimonq2: just get rid of PA, would you? [23:44] wxl: Oh, that's right. Is this something I can just make an executive decision and be done with? [23:46] wxl: I mean, I'll talk with Julien [23:47] wxl: But we're not gonna be like you-know-who here... :| [23:47] wxl: "If Julien says it works, then it works, he knows best" - yeah nope let's not do that again [23:49] well julien can offer advice on why it may or may not be good [23:49] he's someone good to bounce technical ideas off of [23:49] ultimately he knows lubuntu best [23:50] wxl: Sure, so I'll ask him, but we're gonna talk about it, not say, "let's just not touch it at all because Julien is the wise one he knows best he knows everything about the flavour of Lubuntu" [23:50] :) [23:50] And he is the dev team... [23:51] Unit193: Technically, yeah. But if I can research and we can have an intelligent conversation about the aspects of some things, then I'd rather do that than not touch it at all. [23:51] Unit193: i think what tsimonq2 is saying is that he's part of a team of people rather than the emperor [23:52] Yeah. [23:52] That. [23:52] not like julien has ever acted like he was in that role [23:52] he's ALWAYS been very willing to work with others [23:52] but there was someone..... [23:52] You-know-who... [23:52] he-who-shall-not-be-named