[06:21] good morning [06:24] hi all [06:25] salut jibel [06:27] Salut didrocks, ça va? [06:28] et toi jibel ? [06:28] pluvieusement [06:31] didrocks, maybe I found a solution for the "failed to mount / device not ready issue" [06:31] didrocks, I'm testing it right now [06:34] sweet! [06:36] didrocks, using partx instead of partprobe seems to do the rtick [06:36] rtick [06:36] ... [06:36] didrocks, jibel bonjour ! Since you are the zfs on Ubuntu experts now ;), I have a stupid question; I read this over the weekend: https://arstechnica.com/information-technology/2019/10/a-detailed-look-at-ubuntus-new-experimental-zfs-installer/ and I don't quite get it. If you have ZFS installed, you cannot really know how much free space you have now, do you? Since as soon as you take a snapshot, every deletion/modification of a file results in [06:36] more space used... [06:36] trick [06:38] Morning didrocks and jibel [06:44] hey duflu [06:45] salut pieq: you can use zfs status. We need to look more at df, if it reports the correct value or not [06:46] didrocks, ok so there will be a lot of work to adapt the usual tools (like disks, baobab etc.) to be used easily if zfs is activated [06:46] or zfs list -o space [06:48] good morning desktoppers [06:51] Morning oSoMoN [06:51] hey duflu [06:57] good morning! [07:01] Morning Trevinho. Thanks for the dock fix(es)! === pstolowski|afk is now known as pstolowski [07:09] good morning Trevinho [07:14] hey oSoMoN and duflu, and np [07:19] Morning desktoppers o/ [07:19] morning Wimpress [07:19] Trevinho: You arrived OK then? [07:20] Wimpress: yeah, thanks. All foost [07:20] good* [07:20] hey oSoMoN, Trevinho, Wimpress [07:21] damned keyboard... Although now stock waiting for the replacement bus 😡 [07:21] o/ [07:22] salut didrocks [07:48] Morning Wimpress [08:01] hullo [08:01] hey Laney [08:03] hey didrocks [08:03] good weekend? [08:03] not really. You? [08:03] what :( [08:03] mine was nice yes :( [08:03] travelled to London? [08:04] did but for something else, not the release sprint, i'm at home today [08:04] ah ok [08:05] hey Laney [08:05] yo oSoMoN [08:10] Hi Laney and willcooke [08:10] afternoon duflu, morning all [08:12] greetings duflu [08:12] morning desktopers [08:12] good morning willcooke, marcustomlinson [08:17] goood morning desktopers, did you have a good w.e? [08:18] salut seb128, et toi ? [08:18] seb128: recovering from a cold :/ and didn't have time to relax, too much to do. so yeah, bit bleh... yourself? :) [08:18] didrocks, oui, plutôt bon [08:19] marcustomlinson, busy but good, I feel like we had good time and got some things done also, but didn't rest much as a consequence [08:19] oh well, busy is good too :) [08:19] true, no time to be sick ;P [08:20] I'm in the tram to join Trevinho to the gnome-shell hackfest, I might not be on IRC at time but emails work or just wait for me to be back online if you need me :) [08:20] haha [08:20] salut seb128. very good week-end here, my mother paid us a visit, we enjoyed really good family time [08:20] I feel like I've been sick non stop since we have the kid, not much atm though which is good [08:20] oSoMoN, ah, nice! [08:21] *cough* *cough* [08:21] * willcooke has a cold too [08:22] hey willcooke, get better! [08:24] that time of the year :/ yeah get better soon willcooke [08:33] Morning seb128 [08:37] seb128 Trevinho have a good hackfest 🙂 [08:38] Wimpress: we'll have, although seb si as always LAAAaate, not like the always-on-time-italian! [08:40] I can't tell if you're joking [08:40] * duflu assumes so [08:47] * Laney peers at glib2.0 [08:49] hey duflu, Wimpress [08:49] Wimpress, thanks! [08:49] duflu, he's trolling me because he was there first today ;-) [08:50] moin seb128 [08:51] hey Laney, how are you? had you a good w.e ? are you in London yet ? [08:56] seb128, Pi booted :) Curiously username/password ubuntu/ubuntu and ubuntu/blank do not work [08:56] empty password? [08:56] Tried that [08:56] ah you tries :/ [08:57] tried [08:57] * duflu edits the image directly [08:59] was good thanks! nice beer fest :> [08:59] i'm going down to the office tomorrow [09:03] Anyone have any view on: [09:03] https://bugs.launchpad.net/ubuntu/+source/example-content/+bug/1826040 [09:03] Launchpad bug 1826040 in nautilus (Ubuntu) "examples.desktop file is not executable and only opens into default text editor(gedit)" [Undecided,Confirmed] [09:04] Should we just remove the examples.desktop file? [09:04] from new installs [09:04] or leave it as is for now [09:04] removing it sounds good [09:06] * willcooke looks at example-content [09:09] maybe it's just time to drop the example-content package from the seeds [09:10] it's useful to have some multimedia content on the iso sometime to test e.g totem [09:10] fair point [09:10] is testing a good enough reason to have it installed for everyone though? [09:10] I didn't speak about installed :) [09:11] also I don't know who worked on the content and how much we/they still care about it [09:11] I'm talking about the live image too [09:11] there might be other reasons, but that one isn't good enough imho [09:12] There's a video from mardy and some music. < 13MB in total. Not updated since, erm, maybe 2014 [09:12] I've no strong opinion, it's somewhat a nice personal touch but probably most people don't care at the same time [09:16] willcooke, we can replace the .desktop by a standard ln -s if we still care about making the content visible, but removing wfm [09:17] The only thing in the install file is that .desktop file. I'm unsure how to make it a symlink. I'm in too deep [09:17] * willcooke should have kept his mouth shut [09:20] willcooke, just drop it if you think you content is outdated [09:20] it's probably not great [09:20] I looked at the change log and it got updated 2018 by nhaines [09:20] and people who install probably don't care much about the 'side' goodies and just want to install [09:20] it's not super out of date, but equally, meh [09:22] right, as said I don't have a strong opinion [09:23] those content like the extra wallpapers give a small bit of 'personnal' touch/make the iso a bit more than only an installer/functional system imho [09:23] but I'm unsure many users care/are sensitive to that [09:23] so maybe it's a whatever [09:34] are the minimum requirements to install Ubuntu Desktop documented somewhere? [09:34] I found https://help.ubuntu.com/community/Installation/SystemRequirements but I am not sure this is the reference [09:35] minimum memory should probably be raised to 4GB, otherwise OOM killer is triggered frequently [09:35] jibel, https://discourse.ubuntu.com/t/please-raise-hardware-recommendations/9814 discuss the topic and list some pages which have refeences to requirements [09:36] Thanks I didn't see this topic [09:36] jibel, https://github.com/canonical-web-and-design/ubuntu.com/issues/5246#event-2388672446 bumped it this cycle [09:37] the wiki should probably be edited, it was also pointed out in a comment [09:37] ah so it's just the wiki that is out of sync [09:44] cannot log in [09:45] jibel, to the wiki thing? [09:45] docs site [09:46] willcooke, the wiki [09:46] jibel, I'm in [09:46] stand by [09:46] willcooke, this page https://help.ubuntu.com/community/Installation/SystemRequirements [09:47] just make sure it says de same thing than the dl page for desktop [09:47] jibel, done [09:47] there is only the RAM that differs apparently [09:48] willcooke, thanks for your contributions :) [09:48] (…and helping to make ubuntu better blablabla ;)) [09:48] * willcooke pats himself on the head [09:49] I like that we get that for every upload [09:49] "Thank you for your contribution to Ubuntu." [09:49] you're welcome, Launchpad [11:59] Anyone got a clean 19.10 nvidia system handy? Seems installing steam from the archive results in missing libnvidia-gl-435:i386, so steam won't launch. [11:59] bug 1848001 [11:59] bug 1848001 in Ubuntu MATE "libnvidia-gl-435:i386 not installed from Ubiquity checkbox in 19.10 beta" [Undecided,New] https://launchpad.net/bugs/1848001 [12:06] popey, I do, what do you want to verify [12:06] ? [12:07] If you have ticked the "give me non-free stuff" in ubiquity, and post-install you "sudo apt install steam && steam" does steam launch? [12:07] For the bug reporter, he noted the 64-bit nvidia driver is installed when that box is ticked, but post-install, the steam app doesn't work because the 32-bit nvidia binary isn't available. [12:07] popey, the installer doesn't install 32bit binaries [12:08] Is this a regression? Did this work in 19.04 and now doesn't? [12:08] no [12:08] Users have always had to install some 32-bit nvidia library? [12:08] I think so [12:09] skeptical face engaged. [12:09] to be confirmed by someone who knows steam [12:09] gonna rip the driver out of my gaming system and try that [12:09] thanks [12:09] tseliot, ^ did we install 32bit binaries on 64bit installation in the past? [12:10] when installing 3rd party drivers from the installer [12:10] steam-installer recommends nvidia-driver-libs-i386 [12:10] yeah, but it is not installed by ubuntu-drivers when you request to install nvidia drivers [12:15] this was discussed somewhere in the backlog. our steam package is old and needs a merge, and debian doesn't match our driver libs/meta/something [12:15] or such was the jist of what I read [12:17] bug 1848009 is fun :) [12:17] bug 1848009 in gnome-shell (Ubuntu) "Delay launching application launcher gets longer the more apps are open" [Undecided,New] https://launchpad.net/bugs/1848009 [12:17] this reminds me of Unity Startup Edition [12:17] the "you can open an application 3 times only" [12:18] :D [12:29] jibel, the nvidia-driver-$flavour metapackage recommends the i386 packages [12:32] also, I assume some of the games to be 32 bit only, so you would need 32 bit driver libraries too [12:33] also, nvidia-driver-libs-i386 doesn't exist in Ubuntu. It sounds like something that is available in Debian [12:33] It's not the games initially being reported in the bug, it's steam itself. [12:37] maybe it's really a 32 bit app? I haven't really looked into that [12:39] it [12:39] *it is [12:39] /home/alan/.steam/ubuntu12_32/steam: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.6.24, BuildID[sha1]=5cc05963be376b1bb3e6a531797a08036e7e4a3b, not stripped [12:39] [12:40] yes, then it definitely needs 32 bit driver libraries [14:09] Hey! Did anyone have a chance to look at LP: #1847896 ? [14:09] Launchpad bug 1847896 in gnome-shell (Ubuntu) "Unable to shutdown or restart from log-in screen" [Undecided,Confirmed] https://launchpad.net/bugs/1847896 [14:10] Nope [14:10] Adam was able to reproduce it on his system [14:10] Yup, me too [14:10] Multiple times [14:11] Good [14:11] That means that it'll be easier for someone to look into when that time comes :> [14:15] It feels SRUable indeed [14:17] nod [14:25] rls tagging sounds good for that one [14:25] which is done, good [14:34] sil2100, could someone having the issue add their journalctl to the bug? [14:35] didn't think it was necessary to ask for that since everybody can reproduce at will [14:35] but sure :-) [14:35] sil2100, does it happen with an user logged in, or after logging out from the user session first? [14:36] it does happen after logging out, yes [14:37] and it does happen if you go to the "login as another user" screen when a user is still logged in [14:37] seb128: it happens in both cases from what I know, both when there are users logged in and when there's no user [14:38] Laney, it was not clear from the IRC description that it would always happen, 'able to reproduce multiple times" was worded in a way that suggested it was not always (and I don't want to restart/shutdown my machine now so didn't test for that reason) [14:39] ok [14:39] Laney, also I wish people would file bugs with details/log as a general rule rather than just IRC ping, but that's probably another discussion [14:39] Laney, anyway I stop there, I'm slightly annoyed that you told me off for asking for a log, maybe you did not but I feel like that way atm [14:39] sorry for the noise, going back to other things on that note [14:40] well thanks for telling me [14:40] should probably have mentioned that bit in /query [14:40] sorry for not thinking about it before hitting enter [14:43] no worries [14:43] sorry it came across like that [14:44] I'm generally trying to keep the channel from getting distracted by bug link pastes if that helps to explain my motivations [14:45] not saying that's what was happening there necessarily btw [14:45] just it can explain why I might say some things ... :-) [14:45] right [14:46] anyway, log has a endSessionDialog no XDG_SESSION_ID fetched from logind warning [14:46] and a shutdown failing "interactive auth required" [14:47] ha, I was just pasting that in to the bug [14:47] systemd session work side effect? [14:47] we are discussing it now then? ;-) [14:47] anyway it's rls tagged so we will get to it [14:47] could be [14:47] lol [14:48] I've pasted the relevant bits to the bug (I think) [14:48] well, I just wanted to bugs report to have proper info so they are useful when we decide to have a look, which is why I complained about the lack of journal/log; we have that now :) [14:48] willcooke, thx [15:06] hum, glib symbols seem to not work under valgrind for real, got them missing in an e-d-s error now :/ [15:06] just valgrind some glib thing? [15:06] to reproduce [15:07] --32419-- WARNING: Serious error when reading debug info [15:07] --32419-- When reading debug info from /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0.6200.1: [15:07] --32419-- debuginfo section duplicates a section in the main ELF file [15:07] 😳 [15:08] Trevinho, hey! I opened a new PR for https://github.com/ubuntu/yaru/issues/1526 [15:09] Trevinho, for SRU, current master is some commits ahead of latest release, is that a problem? [15:21] Laney, right, I mentioned those warnings at doko the other day but I think they might be red herring, it gives similar warnings for other binaries but those have working debug symbols (I think, checking again) [15:23] the symbols work as far as gdb is concerned [15:23] afaics [15:24] right, which would indicate a problem on the valgrind side? [15:25] dunno :( [15:25] downgrading that to disco's version doesn't fix the warnings anyway [15:42] valgrind from disco has the same problem [15:42] could be due to some libc change or something :/ [15:43] seb128: I rebuilt it skipping dh_dwz and the warning is gone [15:43] wait [15:43] no I passed nostrip (that fixes it too, unsurprisingly) [15:43] let me try again [15:55] ok now confirmed that for realz [15:59] Laney, it fixes the warning but does it make the symbols work? [16:01] I get things like [16:01] ==9058== 184 bytes in 1 blocks are possibly lost in loss record 227 of 236 [16:01] ==9058== at 0x483CFAF: realloc (in /usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so) [16:01] ==9058== by 0x4ABC58F: g_realloc (gmem.c:164) [16:13] damn it you infected my brain with that gdm thing [16:15] bet you all 10€ (each) that it's fixed by https://github.com/systemd/systemd/commit/a2dcb1d78737d3daa301ee63fbdd02837acb71a8 [16:18] Laney, it also made me look at gnome-session open issue and make me want https://gitlab.gnome.org/GNOME/gnome-session/merge_requests/28 but that's proably fine for a SRU (slower shutdown) [16:19] I need to chase Trevinho also into backporting a few g-s stack fixes [16:19] at least the one for the night mode/color profile not working [16:19] on wayland? [16:19] Jonas fixed that after .1 [16:20] I'm going to review that gnome-session stuff, you don't need to worry about that [16:20] k, thx [16:20] yeah, the color stuff is wayland only, probably good for a first SRU [16:20] or we wait for .2 [16:20] yes [16:20] waiting is totally fine === pstolowski is now known as pstolowski|afk === paride5 is now known as paride [17:01] night all. London tomorrow [17:39] rbalint: could you add a2dcb1d78737d3daa301ee63fbdd02837acb71a8 into the next systemd upload pls for https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847896 ? [17:39] Launchpad bug 1847896 in gnome-shell (Ubuntu) "Unable to shutdown or restart from log-in screen" [High,Confirmed] [18:56] Laney, sure, but i have to note that i planned updating systemd only after release [18:56] Laney, it is quite annoying bug although === jdstrand_ is now known as jdstrand