Comment # 4 on bug 1110456 from Thomas Blume

(In reply to Thorsten Kukuk from comment #3)
> (In reply to Thomas Blume from comment #2)
> 
> > Have you got a machine where I can log in to see the issue?
> 
> I have many, you can use e225.suse.de

There is a mismatch in the socket where systemd listens.
The machine shows:

-->
e225:/var/log # dmesg | grep ' Listening on'
[    1.423452] systemd[1]: Listening on udev Control Socket.
[    1.423509] systemd[1]: Listening on Journal Socket (/dev/log).
[...]
e225:/var/log # ls -l /dev/log
lrwxrwxrwx 1 root root 28 Oct  6 01:59 /dev/log -> /run/systemd/journal/dev-log
--<

On my reference machine it looks like this:

kvm126:~ # dmesg | grep ' Listening on'
[    2.204170] systemd[1]: Listening on udev Control Socket.
[    4.004526] systemd[1]: Listening on Syslog Socket.

rsyslog listens on:

/run/systemd/journal/syslog and that's where systemd should be listening too.

>From the systemd setup I don't see differences, but in
/etc/apparmor.d/abstractions/base I cannot find and entry for:

/run/systemd/journal/syslog

So, maybe apparmor needs to be reconfigured (on my reference machine there is
no apparmor installed).
Can I disable apparmarmor and reboot your machine to double check?