[Bug 783862] New: [sysvinit-init] runlevel switching broken WRT KDM3
https://bugzilla.novell.com/show_bug.cgi?id=783862 https://bugzilla.novell.com/show_bug.cgi?id=783862#c0 Summary: [sysvinit-init] runlevel switching broken WRT KDM3 Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: PC OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: mrmazda@earthlink.net QAContact: qa-bugs@suse.de CC: anixx@opensuse.org Found By: --- Blocker: --- Created an attachment (id=508449) --> (http://bugzilla.novell.com/attachment.cgi?id=508449) y2logs from host big31 I don't recall seeing any of the following during 12.2 development on 9 x86 systems with sysvinit-init installed (Bug 768788 makes sysvinit-init preferable to systemd-init), but I'm not sure I used kdm3 (or 4; I prefer and mostly use startx on test systems when I actually want to use X) enough on those systems that I might have noticed the following: 1-init 1/telinit 1 from tty3 in runlevel 3 does not switch to tty1 to request root passwd 2-init 3/telinit3 from runlevel 5 produces unexpected messages: A-Usage message for killproc B-Running /etc/init.d/after.local even though 0 uncommented lines in after.local 3-init 3/telinit 3 from runlevel 5 does not terminate kdm3 login manager on tty7. To restore fully functional runlevel 5/kdm3 login manager requires killing multiple kdm processes. I suspect 1, 2 & 3 are at least partially independent issues. My primary interest in filing here is #3. These occur/fail on 2 x86-64 systems installed fresh after 12.2 release, with all available updates subsequently applied via zypper dup. Both were minimal X installs with KDE3 added via zypper after setting solver.onlyRequires=true in zypp.conf. On host big41 sysvinit-init was not originally installed. On host gx260 I had installed 32 bit 12.2 early in development and zypper dup'd periodically. Last updated 24 Aug, it did not have these problems until after zypper dup, and reboot, today. #1B above it doesn't do, but kdm3 login manager was replaced by xdm after the reboot, which I fixed by changing DISPLAYMANAGER="kdm" to DISPLAYMANAGER="kdm3". On host gx280 I had installed 32 bit 12.2 early in development and zypper dup'd periodically. Last updated 28 Aug, it did not have these problems until after zypper dup, and reboot, today. Kdm3 login manager was replaced by xdm after the reboot, which I fixed by changing DISPLAYMANAGER="kdm" to DISPLAYMANAGER="kdm3". On host gx27b I had installed 32 bit 12.2 with KDE4 early in development and zypper dup'd periodically. Last updated 23 Sep, including KDE 4.9.x, it does not have these problems either before zypper dup and reboot today, or after, except for producing the 2B message above. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=783862 https://bugzilla.novell.com/show_bug.cgi?id=783862#c kk zhang <kkzhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kkzhang@suse.com AssignedTo|bnc-team-screening@forge.pr |werner@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=783862 https://bugzilla.novell.com/show_bug.cgi?id=783862#c1 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |sndirsch@suse.com InfoProvider| |kkzhang@suse.com --- Comment #1 from Dr. Werner Fink <werner@suse.com> 2012-10-15 13:00:11 UTC --- Why I've assigned to this bug? SysVinit is dead! Beside this, even as maintainer of sysvinit, I'm not responsible for broken boot scripts nor for wrong usage of killproc ;) Also I'm not maintainer of of the xdm boot script ;) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=783862 https://bugzilla.novell.com/show_bug.cgi?id=783862#c2 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Component|Basesystem |KDE3 InfoProvider|kkzhang@suse.com | --- Comment #2 from Stefan Dirsch <sndirsch@suse.com> 2012-10-15 13:22:45 UTC --- The displaymanagers themselves are meanwhile responsible for setting the right environment. See also bnc#775548. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=783862 https://bugzilla.novell.com/show_bug.cgi?id=783862#c3 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |werner@suse.com AssignedTo|werner@suse.com |anixx@opensuse.org --- Comment #3 from Dr. Werner Fink <werner@suse.com> 2012-10-16 15:01:00 UTC --- This is a KDE problem -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=783862 https://bugzilla.novell.com/show_bug.cgi?id=783862#c4 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[sysvinit-init] runlevel |runlevel switching broken |switching broken WRT KDM3 |WRT KDM3 (and "KDM" in | |Trinity) --- Comment #4 from Felix Miata <mrmazda@earthlink.net> 2013-08-05 00:06:05 UTC --- "Init 3" is still broken in 12.3, and even using systemd-init instead of sysvinit-init. Whether also in 13.1M3 or later I need to verify. In 12.2 running Trinity instead of KDE3, and sysvinit-init installed, I get this: # init 3 INIT: Switching to runlevel: 3 Boot logging started on /dev/tty3(/dev/console) at <timestamp> Master Resource Control: previous runlevel: 5, switching to runlevel: 3 Master Resource Control: Running /etc/init.d/before.local done killproc: Usage: killproc [-v] [-q] [-L] [-g|-G] [-N] [--p pid_file] [-i ingnore_file] \ [-c root] [-t<sec>] [-SIG] /full/path/to/executable killproc -l done Master Resource Control: Running /etc/init.d/after.local done Master Resource Control: runlevel 3 has been reached # Excerpts from tail of 'ps -A': PID TTY TIME CMD 1717 ? 00:00:00 kdm 1734 tty1 00:00:00 mingetty 1735 tty2 00:00:00 mingetty 1736 ? 00:00:00 login 1737 tty4 00:00:00 mingetty 1738 tty5 00:00:00 mingetty 1739 tty6 00:00:00 mingetty 1757 tty7 00:00:00 X 1766 ? 00:00:00 kdm 1767 ? 00:00:01 kdm_greet 1771 ? 00:00:00 tsak 1775 ? 00:00:00 krootimage 1778 ? 00:00:00 kwin 1781 ? 00:00:00 dcopserver 1792 ? 00:00:00 console-kit-dae 1858 ? 00:00:00 polkitd 1869 tty3 00:00:00 bash 1946 tty3 00:00:00 ps -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=783862 https://bugzilla.novell.com/show_bug.cgi?id=783862#c Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|runlevel switching broken |"runlevel" switching broken |WRT KDM3 (and "KDM" in |WRT KDM3 (and "KDM" in |Trinity) |Trinity) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=783862 https://bugzilla.novell.com/show_bug.cgi?id=783862#c5 --- Comment #5 from Felix Miata <mrmazda@earthlink.net> 2013-12-31 01:13:24 UTC --- Still a 12.2 problem as of last updates. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=783862 https://bugzilla.novell.com/show_bug.cgi?id=783862#c6 --- Comment #6 from Felix Miata <mrmazda@earthlink.net> 2013-12-31 01:28:06 UTC --- On same host gx260 init 3 failing to stop KDM is still a 12.3 problem too. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=783862 https://bugzilla.novell.com/show_bug.cgi?id=783862#c7 --- Comment #7 from Felix Miata <mrmazda@earthlink.net> 2013-12-31 01:33:27 UTC --- On same host gx260 init 3 failing to stop KDM is a 13.1 problem too. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=783862 https://bugzilla.novell.com/show_bug.cgi?id=783862#c8 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|KDE3 |KDE3 Version|Final |201409* Product|openSUSE 12.2 |openSUSE Factory --- Comment #8 from Felix Miata <mrmazda@earthlink.net> 2014-09-12 05:19:18 EDT --- On same host gx260, 'systemctl isolate multi-user.target' failing to stop KDM is a Factory problem too. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=783862 https://bugzilla.novell.com/show_bug.cgi?id=783862#c9 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |mrmazda@earthlink.net --- Comment #9 from Dr. Werner Fink <werner@suse.com> 2014-09-12 09:28:01 UTC --- Check find /etc/systemd/ /usr/lib/systemd/ /run/systemd/ -name multi-user.target\* -ls find /etc/systemd/ /usr/lib/systemd/ /run/systemd/ -name multi-user.target.wants -a -type d | while read d ; do ls -l $d/; done btw: I can not reproduce this with xdm, it works perfect that is I can fix off and on xdm by systemctl isolate multi-user.target systemctl isolate graphical.target -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com