[05:37] <didrocks> good morning!
[05:39] <didrocks> frederikf[m]: clobrano: hey! new Yaru dropped the aubergine background color on gnome-terminal, was that discussed? That was kind of ubuntu's signature IIRC
[05:40] <didrocks> (maybe it's not Yaru, but gnome-terminal upgrade)
[05:52] <jibel> Salut didrocks
[05:55] <Trevinho> frederikf[m]: hey, can you confirm that it was 70% the transparency, right?
[05:55] <Trevinho> (hi!) :)
[05:57] <frederikf[m]> 0.3 transparentized is 70% opaqueness. Sorry just woke up. I hope this is what you mean
[05:57] <Trevinho> frederikf[m]: and yeah, get that aubergine back :P
[05:57] <Trevinho> frederikf[m]: yeah :)
[05:58] <didrocks> Trevinho: another thing, right click on an ubuntu dock item (opened application) shows the popover on the other screen (the most left one, while the dock is on the right one) and never refresh (piling up popup), is it known?
[05:58] <didrocks> and hey Trevinho ;)
[05:58] <frederikf[m]> didrocks we would love to, but GNOME terminal defaults to the light theme. And a light headerbar with a dark aubergine window doesn't look good. Could we default the variant to dark in the terminal? It's still aubergine for the dark variant (try it)
[05:59] <Trevinho> hi didrocks
[05:59] <Trevinho> didrocks: known and fixed :)
[05:59] <didrocks> Trevinho: can't wait for a release ;)
[05:59] <Trevinho> didrocks: was something added last time on 3.34, so didn't update the dock before
[05:59] <didrocks> nice, one less bug to file! :)
[05:59] <didrocks> frederikf[m]: hum, I don't have anything auberginy, even dark
[06:00] <Trevinho> didrocks: if you want get that now, just apply https://github.com/micheleg/dash-to-dock/commit/bb5b0c545292549525ab1ceda6bbce633f49cfbd.patch :)
[06:00] <didrocks> Trevinho: perfect, thanks!
[06:02] <Trevinho> didrocks: mh, I tried a lot to get your crash though, but wasn't able :_(
[06:02] <Trevinho> nor to understand much what's going on...
[06:02] <didrocks> Trevinho: was easily reproducible by seb and I at least, let me see if new G-S fixed it
[06:02] <didrocks> ok, back in intellihide mode, let's see…
[06:03] <didrocks> will keep you posted
[06:03] <frederikf[m]> didrocks when you change to yaru-dark I mean
[06:03] <didrocks> frederikf[m]: I don't have yaru-dark in gnome terminal color profile?
[06:03] <Trevinho> didrocks: see if you can get some good stuff out from your journalctl
[06:04] <didrocks> I have dark on white, white on dark, tango (dark/light), solarized (dark/light)
[06:04] <didrocks> Trevinho: will do. Maybe the crash has just been magically fixed recently by something else, we got some shell updates since then
[06:04] <frederikf[m]> Trevinho I'll revert the dash to dock change then, okay?
[06:04] <didrocks> Trevinho: I was getting it multiple times an hour, so we'll know quickly :)
[06:05] <Trevinho> frederikf[m]: the theme one you mean...
[06:05] <Trevinho> frederikf[m]: I've just pushed dock one, I will release that soon
[06:05] <Trevinho> here it is xD
[06:06] <Trevinho> crash? :)
[06:06] <didrocks> Trevinho: and just got the crash
[06:06] <frederikf[m]> didrocks sorry I meant leave the terminal internal colours on system default. Then change the gnome theme to yaru dark in gnome tweaks or via that gsetting kongfu
[06:06] <didrocks> yep
[06:06] <Trevinho> why did it reload weechat though? :o
[06:06] <Trevinho> is it wayland?
[06:06] <Trevinho> anyways... if you don't get enough, give a check to https://is.gd/wiki_gnome_shell_crash_debug
[06:07] <Trevinho> and then try also with the patch, maybe... helps, although the windows previews shouldn't be generated until needed, but maybe they're not.
[06:07] <didrocks> Trevinho: https://paste.ubuntu.com/p/vDZbQ5GPyR/
[06:07] <didrocks> Trevinho: no, Xorg
[06:08] <didrocks> Trevinho: well, now with systemd, crashing or alt-f2 restarts most of apps…
[06:08] <Trevinho> didrocks: mh, did you get any "gnome-shell crashed...." msg before?
[06:08] <Trevinho> LANEEEEEEYYYYYYYYYYYYYYYYYY
[06:08] <Trevinho> :D
[06:09] <didrocks> Trevinho: no, the only mention of crash is: "sept. 13 08:05:27 casanier gnome-shell[3636]: GNOME Shell crashed with signal 5", which is after
[06:09] <didrocks> so the consequence of the stacktrace, no?
[06:09] <Trevinho> no, I mean, that crashed with... and then there *might* be a JS trace
[06:09] <Trevinho> if there's that's what we look for, if not... it's pure sadness.
[06:09] <didrocks> Trevinho: well, you have a stacktrace in my pastebin, no?
[06:09] <didrocks> the one just above
[06:10] <Trevinho> didrocks: JS ERROR: TypeError: mutterWindow.get_texture(...).get_size is not a function this one is the one that the patch fixes
[06:10] <Trevinho> but shouldn't lead to a crash, although... but was the crashed with... before of that ?
[06:10] <didrocks> Trevinho: ah, but I didn't restart since I applied your patch
[06:10] <Trevinho> immediatly before I'm saying
[06:10] <didrocks> ok, let me alt-f2
[06:11] <didrocks> which will restart weechat…
[06:11] <Trevinho> give me the context with the crashed...
[06:11] <Trevinho> so I get it better
[06:11] <didrocks> like, how to reproduce?
[06:11] <didrocks> well, let's see with your patch first
[06:11] <didrocks> as you can see, quite easy to trigger for me anyway :)
[06:11] <Trevinho> no, with the message signal...
[06:11] <Trevinho> before and after
[06:12] <didrocks> nothing relevant, like the journal entry is multiple seconds before and not related to the Shell
[06:12] <Trevinho> journalctl /usr/bin/gnome-shell -b0 | grep -A 30 "== Stack trace for context"
[06:13] <didrocks> frederikf[m]: so, I changed the gtk app theme to Yaru-dark, let the system them on gnome-terminal, and it's grey on white…
[06:13] <didrocks> Trevinho: https://paste.ubuntu.com/p/rxDQjSYckq/
[06:15] <didrocks> Trevinho: another crash, this time without interacting with dash to dock
[06:15] <didrocks> just showing up a popup in a gtk app… (clicking on the combobox)
[06:15] <didrocks> so, I have 2 monitors, card is nvidia…
[06:15] <frederikf[m]> didrocks that's not good. Let me get a coffee please
[06:16] <didrocks> and another crash… this is really annoying
[06:16] <Trevinho> can you try disabling the desktop extension also?
[06:16] <didrocks> sure
[06:16] <Trevinho> although the fact happens with intelli-hide seems to be related to the dock indeed
[06:17] <Trevinho> try attach the shell with this also https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces/Details#Obtaining_a_stack_and_JS_trace_using_GDB_for_an_already_running_gnome-shell
[06:17] <Trevinho> and let's see that gdb.txt later
[06:17] <didrocks> Trevinho: what would that give compared to the stacktrace generated by apport?
[06:17] <Trevinho> although if that's as the bug is quite useless
[06:17] <Trevinho> mh, not much a part from a JS call again
[06:18] <Trevinho> but maybe...
[06:18] <Trevinho> well, apport doesn't directly call gjs, we do in the shell, but still not the best
[06:18] <didrocks> ok, let's see, it's attached
[06:18] <didrocks> Trevinho: same for you, correct, if you set yaru-dark as gtk theme app, you don't have the aubergine background for the terminal?
[06:23]  * Trevinho heads out... feel free to send me logs
[06:23] <didrocks> no crash yet
[06:23] <didrocks> but you didn't answer me :)
[06:23] <didrocks> frederikf[m]: in all seriousness, I really feel we should, by default, bring back the aubergine back on the terminal. This is really one of the signature of ubuntu desktop
[06:24]  * frederikf[m] uploaded an image: Peek 2019-09-13 08-23.gif (610KB) < https://matrix.org/_matrix/media/v1/download/matrix.org/aDNdDnzchVdkFkujfUShCSAC >
[06:24] <frederikf[m]> can you see this gif?
[06:24] <frederikf[m]> it is definetly aubergine in yaru-dark
[06:24] <didrocks> Trevinho: come back!
[06:24] <didrocks> crashed
[06:24] <didrocks> with the desktop extension disabled
[06:24] <oSoMoN> good morning desktoppers
[06:24] <clobrano_> morning everyone 0/
[06:24] <didrocks> hey oSoMoN
[06:25] <didrocks> & clobrano_
[06:25] <didrocks> Trevinho: https://paste.ubuntu.com/p/TZVQ88Xckz/
[06:25] <oSoMoN> morning clobrano, salut didrocks
[06:25] <frederikf[m]> @didrocks
[06:25] <frederikf[m]> @didrocks https://i.imgur.com/Yf7ZM1B.gif
[06:25] <didrocks> frederikf[m]: hum, which gsettings key this is playing with? maybe tweaks doesn't use the same
[06:26] <didrocks> frederikf[m]: but yeah, I think in the default light theme, the terminal should be kept the same
[06:26] <didrocks> (and this color scheme is good)
[06:26] <frederikf[m]> just switching to yaru-dark  : )  same with tweaks. maybe you've changed the terminal colors to something like "tango" ?
[06:26] <didrocks> I just tried tweaks and no theme is changing…
[06:26] <frederikf[m]> i show you how a light terminal with this aubergine looks
[06:27]  * didrocks uses dconf directly
[06:27] <clobrano_> yeah, I confirm that yaru-dark has aubergine color for terminal, at least when installed from sourc
[06:27] <frederikf[m]> good. I show you how aubergine looks in the light theme now
[06:28] <clobrano_> I didn't notice the light variant dropped aubergine though, sorry
[06:28]  * clobrano_ usually uses a different terminal theme :)
[06:28] <didrocks> I wonder why gsettings set org.gnome.desktop.interface gtk-theme 'Yaru-Dark' doesn't work here… concerning
[06:29] <didrocks> (I doesn't change any theme…)
[06:29] <clobrano_> weird
[06:29] <didrocks> maybe with the crashes, g-s-d is stuck
[06:29] <didrocks> let me restart my sessino
[06:29] <didrocks> session*
[06:29] <clobrano_> didrocks: stupid idea, but what about "Yaru-dark"?
[06:29] <clobrano_> lowercase "d"
[06:29]  * frederikf[m] uploaded an image: image.png (189KB) < https://matrix.org/_matrix/media/v1/download/matrix.org/BwOHMuWKvAzXpexBvxlmKrxO >
[06:29] <didrocks> clobrano_: tried as well, nothing
[06:30] <didrocks> frederikf[m]: this would look good to me, and I really feel the branding here is important
[06:30] <clobrano_> yep, I immagined
[06:30] <didrocks> let me restart my session first
[06:31] <frederikf[m]> can't you rather change the default to "prefer dark" for the gnome-terminal or something? 🙂 But okay, if you think this looks harmonous enough we'll change it
[06:31] <didrocks> ok, I think it was really g-s-d which was in a bad state
[06:32] <didrocks> changing the theme works now
[06:32] <didrocks> frederikf[m]: but yeah, I would really insist that we keep aubergine as a our background terminal color, even in light themes (which is the default…)
[06:32] <didrocks> you can maybe check with will once he's around
[06:32] <frederikf[m]> ok 😐️
[06:33] <clobrano_> it doesn't seem too bad (except the tabs maybe :D) https://usercontent.irccloud-cdn.com/file/LJLBGyzF/image.png
[06:33] <didrocks> yeah, it was quite similar to what I had before with light-themes in ambiance
[06:33] <didrocks> (well, radiance)
[06:35] <didrocks> Trevinho: I'm removing the intellihide for now, let me know if the gdb.txt is enough for you
[06:37] <frederikf[m]> @tr
[06:37] <frederikf[m]> ups
[06:37] <frederikf[m]> Trevinho: https://github.com/ubuntu/yaru/pull/1520
[06:48] <didrocks> Laney: FYI, https://github.com/ubuntu/zsys/commit/3edea2982293fc5853e16a24c72dc5bc21e6af1b. Works well from my local tests
[07:06] <seb128> hey there, happy friday desktopers!
=== pstolowski|afk is now known as pstolowski
[07:07] <seb128> Trevinho, the segfault was easy enough for me to trigger on intel with dual screen and the launcher in between the screens in autohide, with having a  windows over it and trying to play a bit wih moving the cursor between screens and doing some dnd of dock icons
[07:46] <marcustomlinson> morning!
[07:47] <didrocks> hey marcustomlinson
[07:49] <marcustomlinson> didrocks: hey :) can I ask you a favour (seeing that you so kindly greeted me first). Could you trigger these for me?
[07:49] <marcustomlinson> https://autopkgtest.ubuntu.com/request.cgi?release=eoan&arch=amd64&package=libreoffice&ppa=marcustomlinson/libreoffice&trigger=libreoffice/1:6.3.1-0ubuntu1
[07:49] <marcustomlinson> https://autopkgtest.ubuntu.com/request.cgi?release=disco&arch=amd64&package=libreoffice&ppa=marcustomlinson/libreoffice&trigger=libreoffice/1:6.2.7-0ubuntu0.19.04.1
[07:49] <didrocks> marcustomlinson: and done!
[07:49] <marcustomlinson> didrocks: thanks :)
[07:50] <didrocks> yw ;)
[07:56] <seb128> hey marcustomlinson
[08:02] <Laney> heyyyyyyyy
[08:03] <willcooke> morning
[08:03] <didrocks> hey Laney, willcooke
[08:06] <marcustomlinson> hey seb128 willcooke and Laney
[08:06] <seb128> hey willcooke, Laney, how is uk today?
[08:07] <marcustomlinson> suspended...
[08:10] <Laney> moin willcooke didrocks marcustomlinson seb128
[08:10] <Laney> it's nice out there!
[09:18] <seb128> Laney, thxs for the review :)
[09:18] <Laney> np, thanks for the fix!
[09:41] <Laney> xnox: liking your noisy plymouth
[09:44] <oSoMoN> ricotz, would you mind pushing your changes to the firefox-beta branches? I've re-enabled unity-menubar.patch, and I'd like to push that on top
[10:53] <ricotz> oSoMoN, done
[11:00] <oSoMoN> ricotz, thanks
[11:35] <willcooke> Laney, wallpaper!! https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1843798
[11:35] <ubot5> Launchpad bug 1843798 in ubuntu-wallpapers (Ubuntu) "19.10 Eoan default wallpapers" [Undecided,New]
[11:35] <willcooke> Laney, do you want me to file a UIFe?
[11:35] <Laney> yeh mail the team with a link to that bug
[11:35] <willcooke> roger roger.  Thx
[11:36] <Laney> big one this time round
[11:38] <willcooke> I couldnt get it any smaller.  The JPG is just over 1 meg, but it's a bit jagged.
[11:39] <willcooke> I'll email you the jpg, see what you think
[11:39] <Laney> I like it more when the .png file is a .png :P
[11:39] <willcooke> heh
[11:39] <willcooke> yeah
[11:39] <willcooke> I crushed it, but wasn't happy with the end result
[11:39] <willcooke> that online tool wasnt any better
[11:40] <willcooke> and Wayne in design got it down from 15MB to 1.8
[11:40] <xnox> Laney:  thanks
[11:40] <Laney> cool
[11:41] <xnox> didrocks:  one needs to hinted as force-badtest zsys/version/s390x or some such. it should clear once it migrates..... or at least that was my impression.
[11:42] <Laney> it did migrate
[11:42] <xnox> didrocks:  hopefully you were already helped about zsys however
[11:42] <Laney> xnox: you might want to help reviewing https://code.launchpad.net/~jibel/ubiquity/+git/ubiquity/+merge/372690 ?
[11:44] <xnox> Laney:  added myself as reviewer
[11:44] <Laney> coolio
[11:48] <willcooke> Laney, UIFE email sent
[11:48]  * willcooke <- food 
[11:48] <Laney> ta duck
[13:10] <GunnarHj> Hi oSoMoN, Did you ever attend to bug #1842256? Good if you didn't, because the issue seems to have disappeared with the latest version, so I closed the bug.
[13:10] <ubot5> bug 1842256 in gdm3 (Ubuntu Eoan) "~/.pam_environment overridden by /etc/default/locale" [Undecided,Invalid] https://launchpad.net/bugs/1842256
[13:12] <Laney> probably that MR indeed
[13:12] <Laney> it made weird stuff happen
[13:17] <xnox> willcooke:  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1843899
[13:17] <ubot5> Launchpad bug 1843899 in gnome-shell (Ubuntu) "gnome-shell calendar widget is not centered on the screen" [Undecided,New]
[13:18] <GunnarHj> Laney: It makes me more confident that you also thinks so. :) For a while I thought I had simply screwed it up.
[13:18] <xnox> willcooke:  i cannot unsee this, with the new wallpaper.
[13:22] <willcooke> erk
[13:23] <willcooke> that could be because of the icons extension
[13:24] <willcooke> xnox, is that a single monitor?
[13:25] <xnox> willcooke:  yes, single high-dpi laptop screen
[13:25] <xnox> willcooke:  "icons extension" something i did, or something from the default config?
[13:25] <willcooke> default
[13:26] <willcooke> xnox, out of interest can you toggle auto hide for the dock on and off?
[13:28] <xnox> willcooke:  if i turn autohide, the calendar widget is centered.
[13:29] <xnox> willcooke:  when i turn auto-hide off, i see the dock slowly push in from the left, and also push the calendar widget to the right
[13:29] <willcooke> thx xnox
[13:29] <didrocks> I'm pretty sure we did discuss this at length in the past :)
[13:29] <didrocks> including in Unity
[13:29] <didrocks> (shifting the date)
[13:30] <didrocks> but I don't remember what we did in the end in Unity, but I remember we told "let's not touch that" for the Shell
[13:30] <xnox> willcooke:  also icons on the desktop wiggle about when toggling dock autohide on/off.
[13:31] <xnox> didrocks:  unity had calendar on the far right, not in the centre, no?
[13:31] <xnox> didrocks:  it wasn't "almost in the middle of the screen"
[13:31] <didrocks> xnox: oh right, see how memory can derail…
[13:32] <didrocks> what was the center discussion? Oh, it was about the fullscreen windows titlebar with/without the dock hidden
[13:32] <xnox> ah
[13:32] <GunnarHj> seb128: Do you have any plan to update IBus in eoan? (1.5.21 is in experimental.)
[13:33] <seb128> GunnarHj, I have a note to look at it on my todo just didn't to it, if you want to give it a go that would be welcome/helpful
[13:34] <xnox> willcooke:  added comment about our debugging that dock's auto-hide pushes things around.
[13:34] <willcooke> ta
[13:35] <GunnarHj> seb128: The reason I asked is that in any case I'd like to add a fresh upstream commit. But if you think that it's fine to merge with experimental, I can take a look at it.
[13:36] <seb128> GunnarHj, I think it's fine to update to at least .20
[13:36] <seb128> I didn't check changed in the newest
[13:38] <GunnarHj> seb128: Is that what you suggest? Or should I go for 21 unless there is something weird with it?
[13:40] <seb128> GunnarHj, I trust you for having a feeling if that version needs a ffe/is risky or not, but feel free to ask if you have doubt
[13:44] <GunnarHj> seb128: I'll give it a shot. In a sense it's better from a risk POV to get 21 in now, since then 19.10 will serve as a test before next LTS. In my experience the IM users tend to not be very inclined to use the dev versions.
[13:45] <seb128> GunnarHj, sounds resonable yes
[14:02] <seb128> Trevinho, bug #1843520 ... I think I saw you mentioning earlier that it was fixed but I don't see ubuntu-dock commits, where was it fixed?
[14:02] <ubot5> bug 1843520 in gnome-shell-extension-ubuntu-dock (Ubuntu) "ubuntu-dock right-click menu appears at the top-left corner of the desktop (which in some cases is the wrong monitor) and is permanent" [High,Confirmed] https://launchpad.net/bugs/1843520
[14:03] <Trevinho> seb128: it's in the 3.34 branch I've pushed to a master PR. Will merge soon once other issues are hopefully fixed
[14:03] <seb128> Trevinho, ok, thanks
[14:03] <Trevinho> I linked the patch before
[14:04] <Trevinho> meanwhile.... can't wait for the oom killer cause my laptop is frozen... even in SSH login :'(
[14:04] <seb128> :(
[14:04] <seb128> those are annoying, I usually end up sitting on power
[14:07] <seb128> Trevinho, so it was fixed in what component just to triage properly? I can't find the log/reference
[14:09] <Trevinho> seb128: dash-to-dock
[14:10] <Trevinho> well ubuntu-dock actually for us
[14:10] <seb128> Trevinho, thx
[14:37] <Trevinho> uff, got a crash.... now can't get it anymore -_-
[14:39] <seb128> :(
[14:39] <seb128> Trevinho, did you manage to get the dual screen/autohide launcher one?
[14:39] <Trevinho> seb128: that one, i'm trying for a while, but...
[14:40] <Trevinho> also didrocks is getting it on dual-monitor or only on single?
[14:40] <Trevinho> I'm trying with dual though
[14:40] <seb128> dual
[14:40] <seb128> I think it's not there/more difficult to get on single
[14:41] <seb128> I trigger it quite easy with the dock in between two screens and monky click/dnd on the launcher and cross the screens forth and back
[14:41] <seb128> e.g not normal use but monkey clicking and moving around, doing dnd of icons, relaxing those, trying again
[14:43] <Trevinho> I've an issue with dnd icons, but that's another not should be the crash
[14:43] <seb128> k
[14:43] <seb128> well monkey clicking/moving made me crash if 3 times in 5 minutes
[14:43] <seb128> so I was just sharing that tip if it's useful
[14:45] <Trevinho> #notabug! -_-
[14:45] <Trevinho> yeah, I'm trying to... but before it happened easily when just opening the bg menu after some playing
[14:45] <Trevinho> now I can't anymore
[14:46] <Trevinho> crazy how it was happening all the time to Didier, while I can't
[14:46] <seb128> maybe you fixed it ? ;)
[14:46] <jibel> Trevinho, in bug 1736664 what do you call the ShellJournal
[14:46] <ubot5> bug 1736664 in gnome-shell (Ubuntu) "gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler() from g_logv() from g_log() from gjs_callback_closure() from ffi_closure_unix64_inner() [any error message logged from JavaScript will look like this]" [Low,Confirmed] https://launchpad.net/bugs/1736664
[14:46] <jibel> ?
[14:47] <Trevinho> jibel: it's the gnome-shell journalctl log, that is attached to the bug when using ubuntu-bug
[14:53] <seb128> jibel, https://salsa.debian.org/gnome-team/gnome-shell/blob/debian/master/debian/source_gnome-shell.py#L42
[14:56] <jibel> Trevinho, I'll file a separate bug with the data, mark it as duplicate if you think it is
[14:56] <didrocks> Trevinho: have you looked the gdb trace I gave you?
[14:56] <Trevinho> jibel: yeah, better
[14:57] <didrocks> but yeah, as seb wrote, just moving the cursor between the display (having the dock between them), you can trigger it very easily here
[14:57] <didrocks> and on dual monitor… well, my mouse travels :)
[14:57] <Trevinho> didrocks: yeah, but not helpful... it's the same we get on lp.. We need to catch what happens before on JS side, since that only tracks that we crash on JS garbage collecting... which is... nothing :(
[14:57] <jibel> Trevinho, bug 1843914
[14:57] <ubot5> bug 1843914 in gnome-shell (Ubuntu) "gnome-shell crashed with signal 5 in ObjectInstance::~ObjectInstance()" [Undecided,New] https://launchpad.net/bugs/1843914
[14:57] <jibel> tell me if you need more data from the journal
[14:58]  * Trevinho chcks
[14:58] <didrocks> Trevinho: unfortunaly, next week will be only single monitor… or maybe we can try having one and connecting my laptop it?
[14:58] <didrocks> but yeah, in 5 minutes or less, you can get it :p
[14:58] <Trevinho> jibel: looks like same as didrocks
[14:58] <didrocks> jibel: welcome to the club :p
[14:58] <didrocks> maybe some underlying issues, different ways to trigger it
[14:59] <Trevinho> and no js trace :_(
[14:59] <Trevinho> didrocks: can you check by luck if you get it also in wayland? althugh... well maybe you don't want to kill your session :P
[15:00] <didrocks> Trevinho: yeah, don't want to kill the session at this point…
[15:00] <didrocks> but as seb128 could reproduce as well… (and there are some dups), I bet it can be quite common in that setup (at least)
[15:01] <seb128> Trevinho, also knowing it doesn't happen in wayland isn't going to help you much fixing it, will it?
[15:02] <Trevinho> didrocks: and you already using the patch for the menus, right? That doesn't make any difference...
[15:02] <Trevinho> (it should not, but maybe...)
[15:02] <didrocks> Trevinho: yes, I got it with your patch
[15:02] <didrocks> and the desktop-icons disabled
[15:03] <Trevinho> seb128: it does, cause it makes me testing it easier
[15:03] <seb128> just test under xorg :p
[15:03] <didrocks> (but I confirm the patch fix the popup menu issues :))
[15:07] <Laney> UMM
[15:08] <Laney> how do I get back to an orphaned commit in bzr if I bzr pull --overwrite by mistake?
[15:08] <Laney> in git I'd look in `git reflog`
[15:09] <Trevinho> Laney: mh, if you have the ref you can get it back... but.... mhmhm
[15:09] <Trevinho> no idea
[15:09] <Trevinho> grep in your .bzr maybe you get an id somehow?
[15:11] <seb128> (I don't know either)
[15:12] <didrocks> I'm not even sure bzr keeps the state for this or if --overwrite just replace .bzr/
[15:13] <Laney> if you uncommit it prints something to get the old state back
[15:13] <Laney> that makes me believe that it has something like the reflog
[15:13] <didrocks> oh, maybe you should try to commit, uncommit -> grep then for what it prints
[15:13] <didrocks> maybe it's in a special file or so
[15:14] <Laney> good idea but sadly not :(
[15:14] <Laney> let me try #bzr
[15:14] <didrocks> keep us posted if you get anything!
=== jdstrand_ is now known as jdstrand
[15:28] <seb128> ricotz, hey, do you have any idea about the dee build failure on eoan (https://launchpadlibrarian.net/442256979/buildlog_ubuntu-eoan-s390x.dee_1.2.7+17.10.20170616-4ubuntu2_BUILDING.txt.gz)
[15:29] <seb128> vapigen errors out
[15:29] <seb128> error: construct properties not supported for specified property type
[15:38] <Laney> yayay got it
[15:38] <Laney> install bzrtools, use `bzr heads --dead-only'
[15:39] <didrocks> nice!
[15:41] <ricotz> seb128, looking
[15:42] <seb128> ricotz, thx
[15:49] <ricotz> seb128, where is the corresponding repository?
[15:50] <seb128> ricotz, unsure there is one for the packaging, the upstream project is https://code.launchpad.net/~unity-team/dee/trunk
[15:51] <seb128> well that includes packaging but seems not in sync with the archive, need to be sorted out
[15:53] <ricotz> seb128, hard to look at when this is so scattered
[15:53] <seb128> ricotz, dget https://launchpad.net/ubuntu/+archive/primary/+sourcefiles/dee/1.2.7+17.10.20170616-4ubuntu2/dee_1.2.7+17.10.20170616-4ubuntu2.dsc
[15:53] <ricotz> and build fixes are still patches in packaging
[15:54] <seb128> right
[15:54] <seb128> well, I'm interested in fixing the package at this point
[15:55] <seb128> if you throw me a diff for the code I can upstream it and deal with the packaging
[15:55] <ricotz> seb128, I remember encountering this package, I will try
[15:55] <seb128> sorry, the place I was sitting at is closing, I need to change location, be back in 10 min, will read the irclog if you reply meanwhile
[15:55] <seb128> ricotz, thx
[15:55] <seb128> brb
[16:05] <Laney> willcooke: seen https://squoosh.app ?
[16:05] <willcooke> Oooh!
[16:05] <Laney> didn't actually manage to make it smaller, but it's pretty neat
[16:06] <willcooke> https://tinypng.com/
[16:06] <willcooke> thats what I was using before
[16:06] <Laney> from google apparently
[16:06] <willcooke> noice
[16:06]  * willcooke wonders what libs it's using
[16:06]  * willcooke looks
[16:07] <willcooke> http://optipng.sourceforge.net/
[16:07] <willcooke> TIL: Sourceforge is still a thing
[16:07] <willcooke> ha, last updated Dec 2017
[16:09] <Laney> apparently it's using wasm
[16:09] <Laney> so running the compressors in the browser ???
[16:10] <ricotz> seb128, this is crude hack, just to have it built -- https://paste.debian.net/plain/1100570 -- I remember the usage of those struct types is problematic
[16:11] <didrocks> if it's wasm, certainly :)
[16:16] <seb128> (back)
[16:16] <ricotz> seb128, this is crude hack, just to have it built -- https://paste.debian.net/plain/1100570 -- I remember the usage of those struct types is problematic
[16:17] <seb128> ricotz, thx
[17:12] <Laney> ok byeeeeeeee
[17:12] <Laney> see some of you sunday :>
[17:12] <willcooke> see you Laney
[17:12] <willcooke> I'm off too
[17:12] <willcooke> night all
[17:12] <willcooke> looking forward to seeing you