Your message dated Sat, 1 Feb 2020 10:21:55 +0100
with message-id <[email protected]>
and subject line Re: Bug still present in Debian Jessie
has caused the Debian Bug report #693522,
regarding systemd: Doing init 5 from runlevel 1 will result in an unusable
system
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 [email protected]
immediately.)
--
693522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693522
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 44-5
Severity: normal
Tags: upstream
Dear Maintainer,
I am using the "systemd-sysv", but the issue is identical if i use the sysvinit
init implementation.
Starting the system normally, and giving "init 1" it will correctly go to
rescue mode and ask for the root password to proceed.
Inserting the root password and then just typing "init 5" will result in a very
odd situation:
- Blank screen, blinking cursor at the top left corner, but an X11 pointer
shows.
- After that, pressing ctrl+alt+F1 will take me to KDM.
- I can login to KDE normally.
- Whatever ctrl+alt+F* combination i use, i will only see my KDE session, no
virtual terminals.
- Despite wicd up and running, route -n will show that the gateway is not set.
(Okay i could set it manually or do something about it myself).
The non working virtual terminals are annoying and i have no clue how to make
them reappear except for a reboot.
Bye
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.6.6a (SMP w/4 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages systemd depends on:
ii dpkg 1.16.9
ii initscripts 2.88dsf-34
ii libacl1 2.2.51-8
ii libaudit0 1:1.7.18-1.1
ii libc6 2.13-36
ii libcap2 1:2.22-1.2
ii libcryptsetup4 2:1.4.3-4
ii libdbus-1-3 1.6.8-1
ii libkmod2 9-2
ii liblzma5 5.1.1alpha+20120614-1
ii libpam0g 1.1.3-7.1
ii libselinux1 2.1.9-5
ii libsystemd-daemon0 44-5
ii libsystemd-id128-0 44-5
ii libsystemd-journal0 44-5
ii libsystemd-login0 44-5
ii libudev0 175-7.1
ii libwrap0 7.6.q-24
ii udev 175-7.1
ii util-linux 2.20.1-5.2
Versions of packages systemd recommends:
pn libpam-systemd <none>
Versions of packages systemd suggests:
ii python 2.7.3-3
ii python-cairo 1.8.8-1+b2
ii python-dbus 1.1.1-1
pn systemd-gui <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 232-25
On Tue, 19 May 2015 16:28:15 +0200 Folken <[email protected]> wrote:
> Hi,
>
> I just would like to confirm this bug still present in a clean
> upgrade from wheezy to jessie.
>
> Doing a
> systemctl isolate rescue.target
> Correctly boots into the rescue mode
>
> Doing a
> systemctl isolate multi-user.target
>
> Switches to multi-user target and then after 2-3 seconds the terminal
> is unusable. Switching to a different virtual console will not display
> any gettys.
>
> The debian system was installed with base-system target only. No
> graphical interface.
I can confirm this behaviour with 215/jessie and it is no longer
reproducible with 232/stretch. So closing the bug report accordingly.
Regards,
Michael
signature.asc
Description: OpenPGP digital signature
--- End Message ---
