I have forgetten to mention a detail.
The locally connected printers via parallel interface are working after
system start with systemd. The printers connected via ethernet don't.
All printers are working after system start with sysvinit.
___
Ths system was running for two weeks now with no issues. I almost
gathered some hope, that it's finally stable now. :( Next crash..
This time sshd crashed in the first place and the stack of the coredump
seems broken. Both very strange, that never happened before.
As usual, all other services
On 20 July 2015 at 03:48, Eduard Bloch e...@gmx.de wrote:
Hallo,
* Felipe Sateler [Sun, Jul 19 2015, 03:14:11PM]:
So, we have 2 issues:
1. Your system is not shutting down
2. Systemd is not telling you enough to discover what is wrong.
I'm afraid 2 is really an upstream issue and not an
Hi,
Just rebooted machine works ok:
Jul 20 14:25:22 sss sshd[8256]: pam_unix(sshd:session): session opened
for user xxx by (uid=0)
Jul 20 14:25:22 sss systemd-logind[1129]: New session 233 of user xxx.
(no delay)
Problem appears after about 300 ssh logins (/var/log/auth.log):
Jul 20 15:07:02
On 20 July 2015 at 04:39, Andreas Brogle an...@ok.de wrote:
Package: systemd
Version: 222-2
Severity: normal
Dear Maintainer,
All applications don't show my network printers in their printer dialogue,
for example iceweasel or claws-mail.
I can see and configure all my printers with cups
Très Cher(e),
Excusez moi de cette manière de vous contacter car nous ne nous connaissons
pas, je viens d'écrire votre adresse par pure hasard tout en demandant a Dieu
de me guider vers une personne de bonne moralité, je me suis dis que vous êtes
la personne qu'il me faut. En bref, je me nomme
#
# bts-link upstream status pull for source package systemd
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
# remote status report for #792403 (http://bugs.debian.org/792403)
# Bug title: systemd-bootchart crashes when
