=== pizzaiolo is now known as pizza
[06:05] <oSoMoN> good morning desktoppers
[06:09] <bittin> morning
[06:21] <oSoMoN> good morning bittin 
[06:23] <didrocks> good morning oSoMoN, bigon 
[06:23] <didrocks> bittin*
[06:28] <jibel> Good morning
[06:30] <seb128> goood morning desktopers!
[06:32] <duflu> Hi oSoMoN, bittin, didrocks, jibel, seb128 
[06:39] <didrocks> hey duflu, seb128, jibel 
[06:43] <oSoMoN> salut didrocks, jibel, seb128 
[06:43] <oSoMoN> hey duflu 
[06:45] <seb128> hey duflu, lut didrocks oSoMoN , how are you?
[06:46] <oSoMoN> I'm feeling good, how are you?
[06:47] <duflu> seb128, not bad. You?
[06:47] <seb128> I'm alright, I slept better, temperature went down by ~10°C :)
[06:48] <oSoMoN> nice
[06:49] <seb128> oSoMoN, lissyx, https://github.com/brailcom/speechd/commit/43a967b1 fyi
[06:49] <ubottu> Commit 43a967b in brailcom/speechd "Make all modules provide a list of voices"
[06:50] <seb128> he also rolled a new version and started packaging it for Debian, I will merge in Ubuntu once it's uploaded
[06:51] <lissyx> ah nice
[07:02] <oSoMoN> nice
[07:10] <lissyx> hm
[07:10] <lissyx> https://github.com/brailcom/speechd/commit/68c12d3412a12b96fdd3cbc0bb6fa8962cd65ebf
[07:10] <ubottu> Commit 68c12d3 in brailcom/speechd "Add SPEECHD_CMD environment variable"
[07:10] <lissyx> I'm wondering if it could be related to the issue
[07:12] <lissyx> oSoMoN, except by stage-packages + prime of /usr/bin/speech-dispatcher, would there be another way to make it visible to the snap?
[07:15] <lissyx> seb128, do you know if it is going to make it to 18.04 as well?
[07:23] <oSoMoN> lissyx, the speech-dispatcher binary doesn't need to be in the snap, right? the app should use the host's binary
[07:24] <lissyx> well I think it could
[07:24] <lissyx> but I dont see /usr/bin/speech-dispatcher when inside the snap
[07:25] <oSoMoN> but you don't need to see it, the app communicates with it through the lib (using a socket), doesn't it?
[07:27] <lissyx> yes and no
[07:27] <lissyx> it has this auto spawn mechanism
[07:27] <lissyx> it needs to run the binary somehow
[07:38] <seb128> lissyx, oSoMoN, the code in the referenced url suggests the lib 'spawn' it by calling subprocess.Popen to start the service binary, which isn't going to work in the snap
[07:39] <seb128> I'm going to open a feature request to have proper socket activation using systemd
[07:40] <lissyx> seb128, I'm not sure what you are referring to, but it's already verified
[07:40] <lissyx> "SPEECHD_CMD=/bin/true spd-say -L" and it breaks
[07:40] <seb128> lissyx, you mean?
[07:40] <lissyx> there's no question about how it starts the binary
[07:41] <seb128> right, I could have been more assertive in what I wrote
[07:41] <seb128> they do need to rewrite the activation in a way which work with confinement
[07:41] <seb128> like having a systemd unit and socket activation and rely on systemd to activate it
[07:43] <seb128> ah, it's already reported, https://github.com/brailcom/speechd/issues/448
[07:43] <ubottu> Issue 448 in brailcom/speechd "enhancement: add systemd socket activation support" [Open]
[07:49] <lissyx> seb128, tried to stage speech-dispatcher package and it is not working
[07:50] <lissyx> I do have /usr/bin/spd-say exposed but no /usr/bin/speech-dispatcher ?
[07:50] <seb128> is it in another path or something?
[07:51] <seb128> weird
[07:51] <lissyx> seb128, and with socket activation we would still need to grant access for $XDG_RUNTIME_DIR/speech-dispatcher/speechd.sock on snapd side, right
[07:51] <seb128> yes
[07:51] <seb128> that's how things work for other services like at-spi
[07:52] <seb128> I don't except that ^ to be an issue, did mardy reply to you yesterday?
[07:53] <seb128> we should already propose that tweak imho, it would be a first step and make it easier to workaround for users even if the autoactivation is not working
[08:09] <lissyx> seb128, but all of that is not going to be fixed on 1804 I guess
[08:18] <seb128> lissyx, no, but 18.04 ships with firefox with a deb
[08:19] <lissyx> seb128, but it is still impacted by bogus speech-dispatcher
[08:22] <seb128> lissyx, right, we could consider SRUing the fixes for the missing voices to older Ubuntu series
[08:23] <lissyx> is speech-dispatcher part of the default docker image?
[08:23] <seb128> but I don't think we want changes like reworking the activation to be SRUed, if/when that lands
[08:23] <lissyx> I'm a bit lost in our TaskCluster setup
[08:23] <seb128> I don't know, I'm not familiar with the Ubuntu docker image
[08:24] <lissyx> https://searchfox.org/mozilla-central/rev/8dd35cd8f5284fbaa506aab02fe42fc87efb249e/taskcluster/ci/docker-image/kind.yml#25,29,43,46,50-55
=== schopin_ is now known as schopin
[09:15] <lissyx> seb128, I see at-spi references in desktop_legacy interface
[09:15] <lissyx> I guess that's where I should do it as well
[09:16] <seb128> lissyx, yes, I pointed that one yesterday, https://github.com/snapcore/snapd/pull/11208/files , I think it should be a similar just for the other socket
[09:16] <ubottu> Pull 11208 in snapcore/snapd "interfaces: allow access to new at-spi socket location in desktop-legacy" [Merged]
[09:26] <lissyx> seb128, https://github.com/snapcore/snapd/pull/12081/files
[09:26] <ubottu> Pull 12081 in snapcore/snapd "Bug 1787245 - Grant access to speech-dispatcher socket" [Open]
[09:26] <lissyx> seb128, rebuilt locally with that change, installed snapd
[09:28] <seb128> lissyx, I gave my +1 but I'm not part of the snapd team so we need another review, should be easy to get though
[09:29] <lissyx> yeah but it's not working so far
[09:30] <seb128> even if you spawn the service manually from outside the snap?
[09:30] <seb128> can you verify from a snap run --shell env that you can access the socket as expected?
[09:30] <lissyx> that's what I am doing
[09:31] <lissyx> user@ubuntu-2204-snap:/home/user$ ls -hal /run/user/1000/snap.firefox/speech-dispatcher/speechd.sock
[09:31] <lissyx> ls: cannot access '/run/user/1000/snap.firefox/speech-dispatcher/speechd.sock': No such file or directory
[09:31] <lissyx> user@ubuntu-2204-snap:/home/user$ ls -hal /var/run/user/1000/speech-dispatcher/speechd.sock
[09:31] <lissyx> srwxrwx--- 1 user user 0 ao\u00fbt  26 11:31 /var/run/user/1000/speech-dispatcher/speechd.sock
[09:31] <lissyx> $XDG_RUNTIME_DIR/ does not see it
[09:32] <seb128> I'm unsure how to properly test snapd changes, #snappy or jamesh can probably help you
[09:32] <seb128> did you rebuild the deb or the snap?
[09:32] <lissyx> even forcing, $ SPEECHD_ADDRESS=/var/run/user/1000/speech-dispatcher/speechd.sock spd-say -L
[09:32] <lissyx> Failed to connect to Speech Dispatcher:
[09:32] <lissyx> Unknown or unsupported communication method
[09:32] <lissyx> I rebooted the VM
[09:33] <seb128> snapd has some magic to autorefresh and re-exec so it can update itself even if the deb isn't updated
[09:33] <seb128> so if you rebuilt the deb that might not be the snapd code in use
[09:33] <lissyx> I rebuilt the deb, rebooted
[09:33] <seb128> I think you need to rebuild the snap
[09:33] <seb128> jamesh, ^ can you help to clarify how to test snapd changes?
[09:34] <lissyx> "snap changes" does not respect LC_ALL=C ?
[09:34] <lissyx> it does not show any snapd changes at least
[09:36] <jamesh> lissyx: wait for the CI run to complete, then download the "snap-files" artifact from https://github.com/snapcore/snapd/actions/runs/2932666861 (I got here by clicking the "Checks" tab at the top of the PR, then chose "Tests" from the list on the right).
[09:37] <jamesh> lissyx: unzip that, then install the snap with "snap install --dangerous snapd_*.snap"
[09:37] <lissyx> jamesh, can you check that at least the changes are good?
[09:37] <jamesh> lissyx: you can then switch back to main line snapd with "snap refresh --amend --stable snapd"
[09:37] <lissyx> $XDG_RUNTIME_DIR/ seems not to be /var/run/user/1000/
[09:38] <jamesh> lissyx: looking.
[09:38] <seb128> brb, changing location
[09:39] <jamesh> lissyx: snaps currently run with a private XDG_RUNTIME_DIR, which will be found at "$XDG_RUNTIME_DIR/snap.$SNAP_NAME". You'll probably need to update the desktop-launch script from Snapcraft's gnome extension to either set an environment variable or symlink the speech-dispatcher dir.
[09:41] <lissyx> jamesh, that's not really answering my question
[09:41] <lissyx> jamesh, granting "/{,var/}run/user/[0-9]*/speech-dispatcher/speechd.sock" gets us access to what, inside the snap?
[09:43] <lissyx> I dont have access to the artifacts at https://github.com/snapcore/snapd/runs/8033511152?check_suite_focus=true
[09:44] <lissyx> ah yeah it's on the summary page
[09:44] <lissyx> poor github ui once again
[09:44] <jamesh> lissyx: it'll allow you to connect to that socket. The problem is that for the snap, XDG_RUNTIME_DIR is not /run/user/1000 (or whatever). So libraries looking for the socket based on that env variable won't work automatically.
[09:44] <lissyx> and yay for github blocking non auth usesr to download artifacts ...
[09:46] <jamesh> lissyx: This basically comes down to a decision that seemed good at the time, but has caused its own set of problems. I'd like to get to a point where we expose a private XDG_RUNTIME_DIR at the expected location and the interfaces bind mount in the corresponding files, but it is non-trivial to implement.
[09:47] <lissyx> I guess I should stop working
[09:48] <lissyx> now it's nautilus that decided I dont have to connect anonymous on my NAS but I need to issue user/pass
[09:51] <lissyx> ok now I get snapd listed in snap changes
[09:51] <lissyx> jamesh, and it is still not working
[09:52] <lissyx> user@ubuntu-2204-snap:/home/user$ SPEECHD_ADDRESS=/var/run/user/1000/speech-dispatcher/speechd.sock spd-say -L
[09:52] <lissyx> Failed to connect to Speech Dispatcher:
[09:52] <lissyx> Unknown or unsupported communication method
[09:52] <lissyx> user@ubuntu-2204-snap:/home/user$ SPEECHD_ADDRESS=/run/user/1000/speech-dispatcher/speechd.sock spd-say -L
[09:52] <lissyx> Failed to connect to Speech Dispatcher:
[09:52] <lissyx> Unknown or unsupported communication method
[09:52] <lissyx> user@ubuntu-2204-snap:/home/user$ ls -hal /var/run/user/1000/speech-dispatcher/speechd.sock /run/user/1000/speech-dispatcher/speechd.sock
[09:52] <lissyx> srwxrwx--- 1 user user 0 ao\u00fbt  26 11:52 /run/user/1000/speech-dispatcher/speechd.sock
[09:52] <lissyx> srwxrwx--- 1 user user 0 ao\u00fbt  26 11:52 /var/run/user/1000/speech-dispatcher/speechd.sock
[09:52] <lissyx> user@ubuntu-2204-snap:/home/user$ 
[09:53] <lissyx> and yes, the speech-dispatcher server was working
[09:53] <jamesh> lissyx: if you're running your modified snapd, you should be able to see the policy changes for a snap that plugs desktop-legacy in /var/lib/snapd/apparmor/profiles
[09:53] <jamesh> The AppArmor policies should have been regenerated and loaded into the kernel when you installed the new snapd snap
[09:54] <lissyx> yes it is there
[09:55] <jamesh> If you've got a fairly small test snap, you could try running it with "snap run --strace"
[09:56] <lissyx> I dont
[09:56] <lissyx> and strace on spd-say outside of snap was huge
[09:57] <lissyx> with an inet_socket setup it was working inside the snap
[09:57] <jamesh> lissyx: looking at https://htmlpreview.github.io/?https://github.com/brailcom/speechd/blob/master/doc/speech-dispatcher.html#Setting-Communication-Method it seems you can't just use the socket path in SPEECHD_ADDRESS
[09:58] <jamesh> You probably want SPEECHD_ADDRESS=unix_socket:/run/user/1000/speech-dispatcher/speechd.sock
[09:59] <lissyx> boom
[09:59] <lissyx> for some reason outside of the snap it was working without unix_socket:
[10:00] <jamesh> maybe it tries a default address if $SPEECHD_ADDRESS doesn't work, and the fallback didn't work for the snap
[10:00] <lissyx> it was definitively doing weird things
[10:02] <lissyx> jamesh, ok it's racy to get firefox to talk with speech-dispatcher
[10:03] <lissyx> jamesh, but I got it
[10:03] <lissyx> so the PR should be enough at that point
[10:03] <jamesh> great!
[10:04] <lissyx> seb128, the socket activation bug is old, do you think we can expect to get it fixed soonish?
[10:10] <seb128> lissyx, it was tagged as needshelp so it might be a sign that they don't really know what to do
[10:11] <seb128> we could try to help but it doesn't seem an high priority issue or feature so I've mixed feelings about it
[10:11] <lissyx> we're breaking accessibility
[10:12] <lissyx> that sounds a bit not cool to me
[10:12] <seb128> is that an accessiblity feature?
[10:12] <seb128> screen reader is working
[10:12] <seb128> I don't know what TTS is for exactly
[10:13] <lissyx> WebSpeech API
[10:16] <lissyx> seb128, if it's not going to happen soonish, we should (sorry, it's not nice but) have speech-dispatcher exposed in the snap then
[10:17] <lissyx> https://github.com/brailcom/speechd/issues/336
[10:17] <ubottu> Issue 336 in brailcom/speechd "Support socket activation" [Open]
[10:17] <seb128> lissyx, I'm fine with that
[10:17] <lissyx> there was already this one
[10:17] <seb128> ah, James had commented on it :)
[10:18] <lissyx> seb128, there is already a set of those files
[10:18] <lissyx> I even got tricked by it, I thought it was the way to run it
[10:18] <seb128> so maybe it's easy to do the remining work
[10:18] <seb128> remaining
[10:19] <lissyx> not the .socket
[10:19] <lissyx> jamesh, is this you? https://github.com/brailcom/speechd/issues/336
[10:19] <ubottu> Issue 336 in brailcom/speechd "Support socket activation" [Open]
[10:19] <seb128> lissyx, the current systemd unit is a system one and the readme recommends not using it this way
[10:20] <jamesh> lissyx: yes.
[10:20] <lissyx> seb128, that being said, prime did nnot work in my case and I dont know how to debug that further
[10:21] <lissyx> doh
[10:21] <lissyx> This part is missing libraries that cannot be satisfied with any available stage-packages known to snapcraft:
[10:21] <lissyx> - libdotconf.so.0
[10:21] <lissyx> - libespeak-ng.so.1
[10:21] <lissyx> These dependencies can be satisfied via additional parts or content sharing. Consider validating configured filesets if this dependency was built.
[10:21] <lissyx> so I need to change my hat to "linker that reads ldd output"
[10:26] <lissyx> let's see if priming the speech-dispatcher can make autospawn work
=== Droid is now known as Maik
[11:26] <mdeslaur> looks like the power management control panel got lobotomized in 22.04...what's the trick to getting a laptop to suspend when closing the lid with an external monitor attached?
[11:37] <mdeslaur> is editing HandleLidSwitchDocked=ignore in logind.conf the way to do this, or is there a proper gui somewhere%
[11:44] <seb128> I don't think there is a GUI, and I don't think the settings shrinked, we didn't have that option before either
[11:45] <lissyx> seb128, oSoMoN have you ever tried hg clone --stream?
[11:45] <lissyx> it seems to speed up the build quite a bit
[11:45] <seb128> that's one for oSoMoN, I didn't
[11:45] <seb128> mdeslaur, https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1793918 btw
[11:45] <ubottu> Launchpad bug 1793918 in gnome-tweaks (Ubuntu) "Add/reintroduce setting to enable suspend on lid-close with external monitors attached" [Low, Confirmed]
[11:46] <mdeslaur> seb128: hrm, thanks...the logind thing didn't work
[11:47] <seb128> mdeslaur, https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/111
[11:47] <ubottu> Issue 111 in GNOME/gnome-settings-daemon "Allow suspend with external monitor connected" [Opened]
[11:47] <seb128> mdeslaur, https://www.reddit.com/r/Fedora/comments/sci5is/suspend_laptop_closing_lid_while_connected_to_an/ also
[11:48] <seb128> needs /etc/UPower/UPower.conf IgnoreLid=true it seems
[11:48] <mdeslaur> wow, thanks for your morning google-fu, mine failed for some reason :)
[11:49] <oSoMoN> lissyx, no I didn't, my hg-fu is rather bad
[11:49] <lissyx> mine as well
[11:49] <lissyx> but paul's an expert :)
[11:49] <lissyx> I will run a few more tests
[11:49] <lissyx> but here it looks like it takes down from 10-15min to a few
[11:50] <oSoMoN> lissyx, let's go for that in the nightly branch if the improvement is significant
[12:03] <mdeslaur> seb128: lol, I installed jammy on the wife's new laptop.She complained that it wasn't suspending when closing the lid. I just tried her old one running bionic and it doesn't either.
[12:04] <mdeslaur> change is hard :)
[12:04] <seb128> users... :)
[12:04] <mdeslaur> our job would be way easier if we didn't have users :)
[12:06] <seb128> indeed!
[12:06] <lissyx> oSoMoN, here it seems to be stable ~250s
[12:06] <lissyx> https://paste.mozilla.org/r8bgz8Ce/raw
[12:07] <oSoMoN> let me test here
[12:19] <lissyx> grmmbl
[12:19] <lissyx> still no /usr/bin/speech-dispatcher
[12:20] <lissyx> and this time, "prime firefox" does not show any warning
[12:20] <seb128> lissyx, can you share your snapcraft.yaml?
[12:20] <oSoMoN> data transfer was pretty fast here ("transferred 3.88 GB in 95.3 seconds (41.6 MB/sec)"), but resolving deltas and whatnot still took just under 11 minutes
[12:22] <lissyx> https://paste.mozilla.org/7ajDFXM7
[12:22] <lissyx> oSoMoN, delta took ~1m
[12:22] <lissyx> but I'm building with 96 cores 96GB RAM
[12:24] <lissyx> manually running "prime firefox" shows different results :[
[12:26] <oSoMoN> haha, I can't beat 96 cores and 96GB of RAM with my 12 cores and 64GB of RAM
[12:26] <jbicha> happy Friday
[12:26] <oSoMoN> happy Friday jbicha !
[12:27] <lissyx> still nothing in /usr/bin/speech-dispatcher
[12:27] <lissyx> so it's building fine, but there is nothing, what kind of magic is this
=== ginggs_ is now known as ginggs
[12:34] <seb128> lissyx, want to share your snapcraft.yaml so I can try?
[12:34] <lissyx> I shared the diff
[12:43] <KGB-0> gnome-online-accounts ubuntu/master a93c01c Sebastien Bacher debian/ changelog patches/series patches/0002-livepatch-auth.patch * https://deb.li/ixgMR
[12:44] <KGB-0> * debian/patches/0002-livepatch-auth.patch:
[12:44] <KGB-0>   - remove the livepatch integration, it's not used anymore since
[12:44] <KGB-0>     that's handled by 'ua' now
[12:44] <KGB-0> gnome-online-accounts ubuntu/master 8e03174 Sebastien Bacher debian/changelog * upload to ubuntu * https://deb.li/4Ctd
[12:48] <jbicha> ricotz: I'm glad your LO migrated quickly this time :)
[13:01] <lissyx> oSoMoN, fix what I could for hunspell
[13:03] <ricotz> jbicha, the launchpad builders aren't grumpy anymore :)
[13:03] <lissyx> seb128, https://paste.debian.net/1251759/
[13:04] <lissyx> grmbl
[13:04] <lissyx> there's a bogus line
[13:04] <seb128> lissyx, that has no mention of speech-dispatcher?
[13:04] <lissyx> (but it was not there before)
[13:05] <lissyx> seb128, line 287
[13:06] <seb128> interesting, why is firefox doing no matching in ctrl-F on "speec" but it does when I add the 'h'?!
[13:06] <seb128> ah, I had the words only checkbox ticked for some reason
[13:07] <seb128> lissyx, l288, are you sure it's fine to add 2 items on one line?
[13:07] <seb128> or is that the boggus line you mentioned
[13:07] <lissyx> seb128, no, but that was nnot there before
[13:07] <seb128> ack
[13:07] <lissyx> yeah that's the one
[13:14] <lissyx> oSoMoN, do you know the status of pipewire with firefox snap?
[13:16] <lissyx> seb128, i'm doing a last build and I think I'm done for the week
[13:17] <seb128> lissyx, ack, I started a build here but it's likely to take a while
[13:17] <seb128> and as I said that I got a build fail...
[13:18]  * seb128 deletes the apikey section and retry
[13:24] <KGB-2> gnome-online-accounts signed tags a26ea6e Sebastien Bacher ubuntu/3.45.2-0ubuntu3 * gnome-online-accounts Debian release 3.45.2-0ubuntu3 * https://deb.li/qCwF
[13:24] <KGB-2> gnome-online-accounts ubuntu/master 70cb257 Sebastien Bacher debian/ changelog control control.in gnome-online-accounts.install * https://deb.li/38yY1
[13:24] <KGB-2> * debian/gnome-online-accounts.install:
[13:24] <KGB-2>   - Don't list the lpa_helper script anymore
[13:24] <KGB-2> * debian/control.in:
[13:24] <KGB-2>   - remove the python3 and python3-macaroonbakery depends, they were
[13:24] <KGB-2>     needed for the livepatch helper which has been removed
[13:24] <KGB-2> gnome-online-accounts ubuntu/master 5e33d45 Sebastien Bacher debian/changelog * upload to ubuntu * https://deb.li/Hy6h
[13:31] <lissyx> seb128, built, installed and nothing
[13:31] <lissyx> and no error / warning during the build
[13:32] <lissyx> even the libs I added are not  there
[13:33] <lissyx> oh no
[13:34] <lissyx> I was looking in /usr
[13:34] <lissyx> not in $SNAP/usr ...
[13:35] <lissyx> spd-say -L does not respect SPEECHD_CMD
[13:36] <seb128> lissyx, so speech-dispatcher is in your snap just not in the location you were checking?
[13:36] <lissyx> yeah ...
[13:36] <seb128> k, great :)
[13:36] <lissyx> and spd-say still insist on /usr
[13:36] <lissyx> libspeechd seems as well
[13:36] <seb128> :(
[13:37] <lissyx> $ env|grep SPEECHD
[13:37] <lissyx> SPEECHD_CMD=/snap/firefox/x15/usr/bin/speech-dispatcher
[13:37] <lissyx> SPEECHD_ADDRESS=unix_socket:/run/user/1000/speech-dispatcher/speechd.sock
[13:37] <lissyx> user@ubuntu-2204-snap:/home/user$ spd-say -L
[13:37] <lissyx> Failed to connect to Speech Dispatcher:
[13:37] <lissyx> Error: Can't connect to unix socket /run/user/1000/speech-dispatcher/speechd.sock: Connection refused. Autospawn: Autospawn failed. Spawn error 8: Failed to execute child process \u201c/usr/bin/speech-dispatcher\u201d (No such file or directory)
[13:39] <lissyx> I'll deal with that next week.
[13:39] <seb128> lissyx, enjoy the weekend!
[13:42] <seb128> lissyx, it works on my normal system
[13:42] <seb128> $ export SPEECHD_CMD=/tmp/speech-dispatcher 
[13:42] <seb128> $ spd-say -O
[13:42] <seb128> $ ps aux |  grep speech-dis
[13:42] <seb128> ...
[13:42] <seb128> seb128    288773  0.0  0.0 120036  2364 ?        Ssl  15:42   0:00 /tmp/speech-dispatcher --spawn --communication-method unix_socket --socket-path /run/user/1000/speech-dispatcher/speechd.sock
[13:43] <lissyx> seb128, yes, it works also on my system
[13:43] <lissyx> nont inside the snap
[13:43] <seb128> k, so more snap fun for next week
[13:43] <seb128> try to wipe that from memory and enjoy the weekend meanwhile ;)