Your message dated Wed, 30 Jul 2014 11:46:27 +0200
with message-id <53d8bef3.3030...@debian.org>
and subject line Re: Bug#648747: systemd: Getty setup broken
has caused the Debian Bug report #648747,
regarding systemd: Getty setup broken
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
648747: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 37-1
Severity: normal

Dear Maintainer,

I upgraded systemd and tried it again. It still does the following (although I 
cannot give you exact output) after a terminal reset on boot:
Getty1

starting foo
            some message
                        next message

It looks like some old printer problems or like a terminal that expects 
newlines at \r\n but only gets \n. Very strange!

OTOH: Why does systemd reset the terminal so that all the other boot messages 
disappear?

HS

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.1.0 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages systemd depends on:
ii  initscripts         2.88dsf-13.12
ii  libacl1             2.2.51-4     
ii  libaudit0           1.7.18-1     
ii  libc6               2.13-21      
ii  libcap2             1:2.22-1     
ii  libcryptsetup1      2:1.3.0-3    
ii  libdbus-1-3         1.4.16-1     
ii  libpam0g            1.1.3-4      
ii  libselinux1         2.1.0-4      
ii  libsystemd-daemon0  37-1         
ii  libsystemd-login0   37-1         
ii  libudev0            172-1        
ii  libwrap0            7.6.q-21     
ii  udev                172-1        
ii  util-linux          2.19.1-5     

Versions of packages systemd recommends:
ii  libpam-systemd  37-1

Versions of packages systemd suggests:
pn  python       2.7.2-9
pn  systemd-gui  <none> 

-- no debconf information



--- End Message ---
--- Begin Message ---
Hi,

Michael Biebl asked for more information in November 2012 as the bug was
not reproducible with systemd 44-5. As no further information has been
provided, I'm now closing this bug.

Please reopen with additional information if this is still a problem.

Ansgar

--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Reply via email to