<div dir="ltr"><p dir="ltr">Hi, I can confirm it works. Also I haven't noticed any complaints in the journal. Good luck with v4.<br></p>
<br><div class="gmail_quote">lør. 14. feb. 2015 18.10 skrev David Herrmann <<a href="mailto:dh.herrmann@gmail.com" target="_blank">dh.herrmann@gmail.com</a>>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Daniel!<br>
<br>
On Fri, Feb 13, 2015 at 1:16 PM, David Herrmann <<a href="mailto:dh.herrmann@gmail.com" target="_blank">dh.herrmann@gmail.com</a>> wrote:<br>
> Hi<br>
><br>
> On Thu, Feb 12, 2015 at 11:32 PM, Daniel Buch <<a href="mailto:boogiewasthere@gmail.com" target="_blank">boogiewasthere@gmail.com</a>> wrote:<br>
>> Hi again,<br>
>><br>
>> I found another problem, again with avahi-daemon but in combination with<br>
>> Telepathy haze.<br>
>> feb 13 08:26:39 dbuch-laptop systemd-coredump[1211]: Process 1167<br>
>> (telepathy-haze) of user 1000 dumped core.<br>
>><br>
>> Stack trace of thread<br>
>> 1167:<br>
>> #0 0x00007fe0c9557ae0<br>
>> g_logv (libglib-2.0.so.0)<br>
>> #1 0x00007fe0c9557d1f<br>
>> g_log (libglib-2.0.so.0)<br>
>> #2 0x000000000041261c<br>
>> n/a (telepathy-haze)<br>
>> #3 0x00007fe0c955091d<br>
>> g_main_context_dispatch (libglib-2.0.so.0)<br>
>> #4 0x00007fe0c9550cf8<br>
>> n/a (libglib-2.0.so.0)<br>
>> #5 0x00007fe0c9551022<br>
>> g_main_loop_run (libglib-2.0.so.0)<br>
>> #6 0x00007fe0c9214631<br>
>> tp_run_connection_manager (libtelepathy-glib.so.0)<br>
>> #7 0x000000000040e73b<br>
>> n/a (telepathy-haze)<br>
>> #8 0x00007fe0c8b1e800<br>
>> __libc_start_main (libc.so.6)<br>
>> #9 0x000000000040e7ad<br>
>> n/a (telepathy-haze)<br>
><br>
> This looks like a bug in telepathy, properly triggered by a dbus<br>
> error. This should be fixed upstream, but..<br>
><br>
>> feb 13 08:26:42 dbuch-laptop systemd[642]: Starting DBUS1:<br>
>> org.freedesktop.Telepathy.<u></u>Conn<u></u>ectionManager.haze...<br>
>> feb 13 08:26:42 dbuch-laptop systemd[642]: Started DBUS1:<br>
>> org.freedesktop.Telepathy.<u></u>Conn<u></u>ectionManager.haze.<br>
>> feb 13 08:26:42 dbuch-laptop systemd[1]: Starting Avahi mDNS/DNS-SD Stack...<br>
>> feb 13 08:26:42 dbuch-laptop avahi-daemon[1217]: Found user 'avahi' (UID 84)<br>
>> and group 'avahi' (GID 84).<br>
>> feb 13 08:26:42 dbuch-laptop avahi-daemon[1217]: Successfully dropped root<br>
>> privileges.<br>
>> feb 13 08:26:42 dbuch-laptop avahi-daemon[1217]: avahi-daemon 0.6.31<br>
>> starting up.<br>
>> feb 13 08:26:42 dbuch-laptop avahi-daemon[1217]: Successfully called<br>
>> chroot().<br>
>> feb 13 08:26:42 dbuch-laptop avahi-daemon[1217]: Successfully dropped<br>
>> remaining capabilities.<br>
>> feb 13 08:26:42 dbuch-laptop avahi-daemon[1217]: Loading service file<br>
>> /services/sftp-ssh.service.<br>
>> feb 13 08:26:42 dbuch-laptop avahi-daemon[1217]: Process 313 died: No such<br>
>> process; trying to remove PID file. (/var/run/avahi-daemon//pid)<br>
>> feb 13 08:26:42 dbuch-laptop systemd[1]: Started Avahi mDNS/DNS-SD Stack.<br>
>> feb 13 08:26:42 dbuch-laptop avahi-daemon[1217]: Loading service file<br>
>> /services/ssh.service.<br>
>> feb 13 08:26:42 dbuch-laptop avahi-daemon[1217]: Joining mDNS multicast<br>
>> group on interface wlp3s0.IPv4 with address 192.168.1.2.<br>
>> feb 13 08:26:42 dbuch-laptop avahi-daemon[1217]: New relevant interface<br>
>> wlp3s0.IPv4 for mDNS.<br>
>> feb 13 08:26:42 dbuch-laptop avahi-daemon[1217]: Network interface<br>
>> enumeration completed.<br>
>> feb 13 08:26:42 dbuch-laptop avahi-daemon[1217]: Registering new address<br>
>> record for fe80::eab1:fcff:fec4:eae1 on wlp3s0.*.<br>
>> feb 13 08:26:42 dbuch-laptop avahi-daemon[1217]: Registering new address<br>
>> record for 192.168.1.2 on wlp3s0.IPv4.<br>
>> feb 13 08:26:42 dbuch-laptop avahi-daemon[1217]: Registering HINFO record<br>
>> with values 'X86_64'/'LINUX'.<br>
>> feb 13 08:26:42 dbuch-laptop systemd-bus-proxyd[329]: Failed to send message<br>
>> to bus: Operation not permitted<br>
><br>
> ..this might be what triggered it. It'd be interesting to see which<br>
> message was refused here. I'll see whether we can make the bus-proxy<br>
> more verbose on EPERM.<br>
<br>
This issue should be fixed with systemd-git and kdbus-git:<br>
- systemd-bus-proxyd no longer closes the connection on EPERM, but<br>
forwards the error<br>
- kdbus no longer generates EPERM for unicast-signals<br>
<br>
The bus-proxyd fix should make sure that avahi continues running, the<br>
kdbus fix should make sure that EPERM is no longer generated for<br>
avahi.<br>
<br>
Thanks<br>
David<br>
</blockquote></div></div>