[05:51] <didrocks> hello
[05:52] <ricotz> good morning
[05:52] <duflu> Hi didrocks and ricotz 
[06:04] <oSoMoN> good morning desktoppers, happy Friday!
[06:09] <duflu> Hi oSoMoN 
[06:11] <didrocks> hey duflu, ricotz, oSoMoN 
[13:41] <lissyx> seb128, it's like socket activation does not even work for me
[13:41] <lissyx> is there a special flag to set or something ?
[13:57] <nteodosio> lissyx: It's very likely broken. I'm inspecting the logs Speechd wants to use local unix socket.
[13:57] <lissyx> :[
[13:58] <nteodosio> lissyx: My "systemctl status --user speech-dispatcher.socket" indidactes the socket was used at some point, though. http://paste.debian.net/1256286/
[14:00] <lissyx> but you manually start ?
[14:02] <nteodosio> Nope
[14:02] <lissyx> oSoMoN, FTR I repro the "xhost+" issue under lxde
[14:23] <seb128> lissyx, nteodosio, it works sometime for me, often on a fresh system restart
[14:23] <seb128> I had spd-say -L return empty or segfault in the snap env instead of complaining about the socket
[14:26] <nteodosio> seb128: What is the snap that bundles spd-say? It will be useful for testing.
[14:27] <rs2009> nteodosio: iirc the snap was gnome-calculator
[14:32] <nteodosio> rs2009: Not that one, but thanks anyway
[14:33] <seb128> nteodosio, none, I tried with 
[14:33] <seb128> $ snap run --shell gnome-calculator
[14:34] <seb128> copied libspeechd.so.2  libspeechd.so.2.6.0  spd-say from the system to $SNAP_USER_DATA
[14:34] <seb128> and did 
[14:34] <seb128> $ LD_LIBRARY_PATH=./ ./spd-say -L
[14:34] <seb128> and you need
[14:34] <seb128> $ export SPEECHD_ADDRESS=unix_socket:/var/run/user/1000/speech-dispatcher/speechd.soc
[14:35] <nteodosio> seb128: Thanks. Note that is missing a "k" in the end, I suppose it is a copy-paste typo.
[14:35] <seb128> yes it is :p
[14:52] <rs2009> nteodosio: oops, sorry
[14:54] <nteodosio> rs2009: No problem; You were actually correct after all haha
[15:13] <lissyx> weird
[15:14] <lissyx> I went away 45 min, my laptop was asking the filesystem passphrase, it rebooted :[
[15:16] <seb128> :(
[15:23] <lissyx> i've rebooted it this morning after several weeks of uptime
[15:23] <lissyx> I worry some bad update might have slipped in
[15:24] <rs2009> lissyx: hmm, that's been happening pretty frequently for me lately