[00:09] jibel: all day gdb is fine actually since it just monitors signals if nothing is added.... anyways other option is that your core files taken by apport are usable... [06:05] good morning desktoppers [06:06] good morning [06:06] salut didrocks [06:09] salut oSoMoN [06:12] Morning [06:15] good morning frederikf[m] [06:16] Yay the riotX thing actually works on Android! [06:16] hey frederikf[m] [06:19] marcustomlinson here it is : https://dashboard.snapcraft.io/snaps/yaru-dark-theme-toggle/revisions/1/ [06:21] * @marcustomlinson here it is : https://dashboard.snapcraft.io/snaps/yaru-dark-theme-toggle/revisions/1/ === pstolowski|afk is now known as pstolowski [07:24] goood morning desktopers [07:25] happy birthday seb128 [07:25] hey didrocks, thx :) [07:37] Hi! [07:38] In 18.04 and above, is there a way to disable notifications? Like a "Do not distub" mode or something... I only saw a GNOME extension and apparently it's very buggy [07:45] pieq, hey, you can disable them in gnome-control-center notifications' panel [07:45] brb, changing location [07:53] morning [07:54] hey willcooke [07:55] hi pieq, how goes? Your photo is doing well in the comp. Too close to call at this point though [07:56] hey willcooke, pieq [07:56] willcooke, pretty good! Long weekend looming here (中秋節, aka "mid-autumn festival") [07:57] willcooke, and cool for the pic! I have personal favorites (not mine), hope they will do well too! [07:57] willcooke, how many ppl voted so far> [07:57] ? [07:57] 339 [07:57] Which is pretty good actuallyt [07:57] morning didrocks [07:59] seb128, merci pour le conseil! I didn't even think of looking there... =_=) I hope GNOME adds a button in the actual notification area soon... [08:01] np [08:01] worth reporting upstream if you think that should be done, but what it is you are trying to get done exactly? [08:01] ayo [08:01] I think they were rather thinking in workflow, like disable them on projector on when in fullscreen [08:02] hey Laney, how are you? [08:03] hey seb128 [08:03] very well thanks! looks nice and sunny today [08:03] you? [08:05] Laney, I'm good, stopped for an 'english breakfast' on my way back this morning, just got my juice/coffee/toast/egg/bacon :) [08:05] and it's sunny outside after a day of rain! [08:07] :> [08:08] hey Laney [08:09] good morning desktopers! [08:09] Laney, hi, could you sync gnome-shell-extensions from debian/exp? [08:09] ricotz: yeah, thanks for the reminder [08:10] write a sync-when-available script for me please :-) [08:11] hehe, thanks :) [08:11] hey ricotz [08:12] seb128, hi [08:31] I think they were rather thinking in workflow, like disable them on projector on when in fullscreen → *exactly* my use case: when I give a talk, I don't want random Hexchat notifications popping up [08:32] pieq, k, that's something being discussed for a while [08:32] (another use case: when I try to focus on fixing a bug, I don't want notifications to pop up on my screen :)) [08:33] seb128, OK. Do you know if the GNOME community reached a consensus and it's just waiting on being implemented or it's still being debated? [08:34] I don't remember the details [08:34] but i'm pretty sure they are in agreement than 'presentation' mode should have no notification [08:35] (I don't remember if that was somewhat supposed to be already implemented/working today or part of plans though) [08:35] would need to check a bit the upstream reports etc [08:35] but it might be a topic we discuss for next cycle, it has been on our backlog for a while [08:35] one more last minute question for you guys: with gnome shell 3.32 the adaptive transparency has stopped working for the dock (I personally do not know if it is connected to 3.32 or some dashtodock thing) and we had to decide between perma transparent or perma opaque. Here is a pull request for a low transparency permanently for the dock only (not the panel). Looks a bit like unity7, we would like to hear a +1 or [08:35] -1 from you: [08:35] https://github.com/ubuntu/yaru/pull/1518 [08:36] willcooke, Trevinho, ^ [08:36] hey frederikf[m] :) [08:36] hey frederikf[m] [08:36] seb128, cool! Sorry, I feel very far away from all these discussions related to the desktop environment... [08:37] frederikf[m], the adaptive mode was dropped because gnome-shell dropped that feature for their panel and we followed that for consistency between the UI elements iirc [08:37] pieq, no worry! [08:37] hi 🙂 And happry birthday seb128 ? [08:37] frederikf[m], thanks ;-) [08:37] looking at the PR now [08:38] +1'd looks good. I like it [08:39] willcooke, frederikf[m], that makes the top panel and dock not be consistent, unsure if that's an issue or not [08:39] IMO its not an issue [08:39] (if you didn't figure that out yet, I'm not the person to ask for an opinion on UI consitency :-) [08:40] frederikf[m], can the headbar be semi trans too to match? [08:40] that would look weird imho [08:41] morning everyone 0/ [08:41] hi clobrano [08:42] hey clobrano, how are you? [08:42] hey willcooke, how's it going? [08:42] seb128, semi trans header would look weird? Yeah, could be. I think it looks fine as it is in those screenshots tbh [08:42] hi seb128, I'm doing good, yourself? [08:42] clobrano, I'm good! [08:42] :) [08:44] willcooke, seb128: the permanent transparency (of the dock onlyl) will always depend on the wallpaper, so it's hard to make it work always good, but this big chunk of black on the side is also heavy [08:44] indeed [08:46] yeah, I think the balance in those screenshots is good. It could be because of the wallpapers, but it looks right to me. And better than a big slab of black for sure [08:46] +1 [08:47] (brb, changing location) [08:59] Good morning seb128! I just sent you an email. [09:00] good, I'll wait just a little for Mads to reply, before merging the change, so that it can go in Eoan [09:00] quickety quick [09:05] GunnarHj, hey, k [09:31] not so super important issue I've observed in eoan: rhythmnox with the alternative-toolbar extension doesn't have the "modern" toggle any longer set to active, resulting in basically disabling the reason for this extension (client side decorations) - is this an issue and if yes is it known? : ) [09:33] frederikf[m], not known I think but I will check on a new profile/install, thx for raising it [09:35] np! it's this toggle: https://i.imgur.com/fM6tbGF.png [09:59] Laney, yaru changelog updated and merged :+1 [10:00] cool [10:00] thanks! [10:31] :) [11:20] pkgstripfiles on yaru is a bad idea [11:21] Laney: pkgstripfiles? [11:22] it runs as part of the build [11:22] and compresses all the images in a package [11:23] cool for the package that ends up in the ubuntu archive [11:23] not really needed for me testing it here :> [11:24] I see. It might be cool to have a release build, different than development build [11:32] Laney: where does it run? I don't see it in the meson script nor in the build log [11:33] you need to install it into your build chroot [11:34] then it gets its little teeth into the proceedings by taking over dh_builddeb [11:34] package is called pkgbinarymangler [11:35] just finished, 20 minutes later 😏 [11:38] 🤦‍♂️ [11:40] ok [11:42] it's uploaded [11:42] well done on meeting the user interface freeze [11:42] done better than the default wallpaper 😈 [11:42] 🥳 [13:11] ricotz, I modified slightly your patch to have the firefox build select the highest llvm version available: https://bazaar.launchpad.net/~mozillateam/firefox/firefox-beta.xenial/revision/1297 [13:13] ricotz, I'm now working on re-enabling unity-menubar.patch [13:14] ricotz, note that I didn't export neither AS nor LLVM_CONFIG, CC and CXX seem to be enough [13:14] but maybe that's different when building trunk? [13:16] oSoMoN, will take a look, did you test built it without those exports? [13:16] ricotz, yes: https://launchpad.net/~osomon/+archive/ubuntu/ff70-clang-xenial/+packages [13:17] at least on xenial that works, I'll now test bionic in a separate PPA [13:17] oSoMoN, I see, and e.g. eoan so with llvm 9? [13:18] oSoMoN, why so many separate ppas? [13:19] marcustomlinson, hey, I'm probably going to bother you with a stupid question but I guess a libreoffice update is coming? I see we have .0 where Debian has .1 and upstream .2? :) [13:19] ricotz, they're throwaway PPAs, I delete them afterwards [13:19] oSoMoN, ok [13:24] oSoMoN, I assume you are pushing these changes to the other series too, later today beta 6 will be tagged [13:30] ricotz, yes, I'll push the changes before beta 6 is out [13:31] oSoMoN, I guess with these toolchain changes a trunk build on xenial is worth another try [13:32] oSoMoN, thanks [13:33] you’re welcome [13:57] random question, but does anyone has some experience doing stacked charts? what tool/language/library would you recommend? (I wanted to draw the stats of packages updates/tosync/topupdate over time) [14:21] libreoffice, google spreadsheet if it's a one time thing, grafana if it's live data [14:27] lol, of course, using libreoffice, stupid me [14:27] thx jibel :) [14:27] I was stuck in the mindset of command line utility or python library for some reason, but yeah probably easier to do in libreoffice :) [14:35] if you insist on trying a CLI tool, I'd go for gnuplot ;) [14:36] seb128, marcustomlinson, libreoffice 6.3.1 and 6.2.7 are the current releases [14:36] (declared released last week) [14:36] ricotz: 6.2.6 you mean [14:37] marcustomlinson, no, as I said [14:37] ricotz: https://wiki.documentfoundation.org/ReleasePlan/6.2 [14:37] marcustomlinson, don't trust the wiki [14:37] https://download.documentfoundation.org/libreoffice/stable/ [14:38] it is security related release [14:39] ricotz, http://download.documentfoundation.org/libreoffice/src/6.3.2/ [14:39] seb128, this is a prerelease [14:39] 6.3.2 rc1 [14:39] naming .1 a rc is weird [14:39] that's usually > .0 [14:40] it is 6.3.2.1 [14:40] ricotz, thx for the info :) [14:40] seb128, https://cgit.freedesktop.org/libreoffice/core/ [14:41] yeah, I'm lost now :p [14:42] https://wiki.documentfoundation.org/ReleasePlan/6.3#6.3.2_release [14:42] 6.3 wiki seems accurate [14:42] k [14:46] marcustomlinson, regarding some recent component-mismatch fixes, imo it is better to move such dependency to Suggests to not loose track of them (as done in the past) [14:48] Laney: seems like autopkgtests continues to try to execute on s390x while 0.2 and 0.2.1 doesn't have binaries produced for it, how do you unteach autopkgtests about s390x for it? [14:49] dunno, I thought that proposed-migration wouldn't have requested that one [14:50] yeah, same. That made sense when n-1 had run with it, (so, logical for 0.2), but not for 0.2.1 [14:50] any idea apart from putting an unblock on zsys/s390x? [14:50] (without version, urgh… :/) [14:52] well another way to do it would be to make the test skippable (Restrictions: skippable) and then exit 77 when it shouldn't be run [14:53] hum, if you have some example for debian/control/tests [14:54] but I guess 0.2.1 can need seom hint in between… :/ [14:54] debian/tests/control [14:55] (it's still annoying as an infra limitation to carry those skippable hints + exit hack forever) [14:55] sure [14:55] thanks! [14:55] i'm just telling you how you can help yourself out of it [14:55] annoying or not [14:57] weird that we are the first one to hit this, but yeah, if there is no other way, we'll do… [14:59] Laney, I just this second got the wallpaper. No greyscale though. I will get that bug opened today one way or antother [15:11] didrocks: something like https://paste.debian.net/1100280/ [15:11] and as for the actual fix, I guess it would be in https://git.launchpad.net/~ubuntu-release/britney/+git/britney2-ubuntu/tree/britney2/policies/autopkgtest.py tests_for_source [15:11] but you'd probably have to be careful around e.g. arch:all packages [15:11] willcooke: neat, is it 99999 TB? [15:12] lol [15:13] wow, 1.6MB [15:13] Laney: ok, we don't have a running script, but a command, but I guess it accepts && and ||. I'll give it a shot, thanks [15:14] until then, the hint will be fine, thanks :) [15:14] if britney has a some testsuite, I might give it a shot directly there [15:16] seeing the number of special cases and hacks there, /me shivers [15:16] it sure does === clobrano_ is now known as clobrano [15:54] banding banding banding [15:54] argh [15:56] https://en.wikipedia.org/wiki/Colour_banding on wallpapers or missing r? :) [15:56] yeah that :) [15:56] always with the banding [15:56] lalala, "classic" [15:56] I've tried every filter and trick I found on the internet, nothing works [15:57] The PNG libs on Mac are better than Linux it seems [15:57] * didrocks gives a random gimp plugin after google search and say "just" use that [15:57] or at least, better at dithering it [15:57] + it's easy [15:57] + "finally" :) [15:57] :D === pstolowski is now known as pstolowski|afk [16:45] Laney: did you add the hint for zsys meanwhile? Unsure if the "yes" you told before was related to that [16:45] I have something for skipping, but will be in next upload [17:00] no I didn't, sorry for giving that impression [17:01] I'd say it's probably best to test that right away so you don't get blocked / annoyed by it the next time? [17:04] Laney: I would have liked to have it in tomorrow morning to avoid adding a ppa in our tests, but I need to download first an autopkgtests vm (which I don't have the time before tomorrow anyway) to test this works, but if you don't feel confortable about it, I'll have to deal with it [17:04] well OK I can if you want [17:05] I don't mind very much, I'm just giving you advice that you are free to not follow [17:05] thanks :) Also, that would avoid a build with a dummy upload just to workaround some autopkgtests infra [17:05] limitations* [17:05] well, this is staged in my git [17:05] sure, but the risk you are facing is that the next upload this workaround is broken and you could have fixed it tomrorrow [17:05] I'm not going to get the new wallpapers until tomorrow now [17:06] just that I want to properly test it and doesn't worth an upload (I'm sure we'll upload a new zsys anyway) [17:06] yeah… [17:06] I've opened a bug, but I expect I will need to make it a UIFe [17:06] it totally is worth an upload to fix tests [17:06] I gotta shoot off. I'll keep an eye on email just in case though [17:06] night all [17:06] it's not really "fixing tests", it's fixing "autopkgtests infra which is launching tests on an arch where no package is published" [17:07] (well, workarounding) [17:07] right I'm not interested in splitting hairs with you [17:07] I've committed the hint now [17:07] thx [17:09] actually I am [17:09] I wasn't claiming this wasn't a workaround [17:09] I was giving you advice that it would be better to test your workaround [17:10] fine, it's important to you that it is autopkgtest's fault - that is not in dispute [17:10] still good to make sure such things work as expected though [17:10] imo [17:10] goodnight [17:11] o/