https://bugzilla.novell.com/show_bug.cgi?id=800514 https://bugzilla.novell.com/show_bug.cgi?id=800514#c Martin Vidner changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mvidner@suse.com |yast2-maintainers@suse.de -- 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=800514 https://bugzilla.novell.com/show_bug.cgi?id=800514#c1 Frank Daniel changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High CC| |fdan52@comcast.net Target Milestone|--- |12.3 Beta 1 Severity|Normal |Major --- Comment #1 from Frank Daniel 2013-01-30 19:04:33 UTC --- This is a major S.N.A.F.U Is there a quick work around? I really hate to fumble through the "INIT"s. -- 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=800514 https://bugzilla.novell.com/show_bug.cgi?id=800514#c Martin Pluskal changed: What |Removed |Added ---------------------------------------------------------------------------- Component|YaST2 |YaST2 Version|12.3 Beta 1 |RC 1 AssignedTo|mvidner@suse.com |bnc-team-screening@forge.pr | |ovo.novell.com Product|openSUSE Factory |openSUSE 12.3 Target Milestone|12.3 Beta 1 |--- -- 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=800514 https://bugzilla.novell.com/show_bug.cgi?id=800514#c Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P0 - Crit Sit |P2 - High -- 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=800514 https://bugzilla.novell.com/show_bug.cgi?id=800514#c5 --- Comment #5 from Kalenz . 2013-03-07 12:55:49 UTC --- Created an attachment (id=528710) --> (http://bugzilla.novell.com/attachment.cgi?id=528710) screenshot -- 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=800514 https://bugzilla.novell.com/show_bug.cgi?id=800514#c Kalenz . changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 - High |P1 - Urgent Version|RC 1 |RC 2 Target Milestone|--- |Final Flag|SHIP_STOPPER- |SHIP_STOPPER? -- 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=800514 https://bugzilla.novell.com/show_bug.cgi?id=800514#c7 Thomas Fehr changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |mvidner@suse.com --- Comment #7 from Thomas Fehr 2013-03-12 10:36:13 UTC --- Reassigned to maintainer of yast2-runlevel -- 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=800514 https://bugzilla.novell.com/show_bug.cgi?id=800514#c9 Alexander Winzer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |a.winzer@koenig-dey.de --- Comment #9 from Alexander Winzer 2013-03-20 17:18:32 UTC --- I made an upgrade, too. And since then I got the same issue on my x64 openSUSE 12.3 system. I made an update via zypper dup directly from 12.2 to 12.3. And the problem also occurs on a i586 machine. Will this ever be fixed? In the german openSUSE mailing list I was told, this is because of the change from SysVinit to systemd. Runlevels would be replaced by so called targets. This means to me, it would never be fixed? -- 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=800514 https://bugzilla.novell.com/show_bug.cgi?id=800514#c11 --- Comment #11 from Lukas Ocilka 2013-03-21 07:17:09 UTC --- Guys, it's actually something else. openSUSE has switched from SysV services to systemd ones. These have different format now and YaST Runlevel can't read them anymore. See the current, so called, 'agent' here: https://github.com/yast/yast-yast2/blob/master/library/runlevel/src/ag_inits... We don't have time for that now, but we, of course, plan to fix it. Anyway, we accept patches. See https://help.github.com/articles/fork-a-repo -- 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=800514 https://bugzilla.novell.com/show_bug.cgi?id=800514#c13 --- Comment #13 from Kalenz . 2013-03-21 17:09:50 UTC --- Alexander, Lukas certainly knows more than I do, so trust him for now. When I said I "warned", I mean that when reporting bugs there is a function to flag a bug as a "ship-stopper", i.e., a bug that must be fixed before the next public release is shipped. I requested this, and it was ignored. If you read between the lines in Lukas' message, the idea is: "we know it's a problem, but we simply do not have the manpower to fix all the problems right now, so here's what we do: instead of making a stable 12.3 release, we make a buggy release, so that the community users become frustrated, and then hopefully they will fix all our problems for us". Unfortunately, community users (like me) expect a basic level of usability from openSUSE. Which means: if YaST is the all-powerful system control panel, then it should be possible to manage system services from YaST, and this cannot just be a broken feature in a *STABLE* release. Similarly, openSUSE users have been battling with "Xorg -configure" and xorg.conf files ever since SaX2 was dropped as "nobody has time for it". I don't want a distribution that gives me buggy software and then tells ME to fix it. My conclusion is that openSUSE is no longer suitable for productive use, and I expect to be switching to Debian soon. -- 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=800514 https://bugzilla.novell.com/show_bug.cgi?id=800514#c15 --- Comment #15 from Lukas Ocilka 2013-03-22 09:20:09 UTC --- You obviously want some more info, OK, here it is... SUSE/Attachmate definitely cares about openSUSE and we also care about our users. On the other hand, as nothing is for free except openSUSE product itself (we have to pay, e.g., this: server-housing for build service, hardware, electricity, and of course manpower), we have to make some money somewhere else. As we don't get patches for YaST from community, we have to do everything by ourselves, but manpower is not unlimited. This time we had an important release of three other products that had the same or almost the same release date with openSUSE. Systemd integration was required by openSUSE and we have spent a lot of time on that anyway. Of course, as said already we plan to fix YaST Runlevel. We definitely know we need more people and that's why we now have 38 open positions at SUSE: https://www.suse.com/company/careers/ -- 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=800514 https://bugzilla.novell.com/show_bug.cgi?id=800514#c17 --- Comment #17 from Frank Daniel 2013-03-24 20:29:39 UTC --- I don't know guys. I just installed the new 12.3 release and I found little to bitch about. (And believe me. I am one of the most dispised accounts OpenSuse has). It took close to 3 years of constant complaining, in their face changing of priority/importance and flame mail to correct some of the bugs I found. But now not only does the installation work properly, the runlevel app in Yast is working!! (at least for me) -- 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=800514 https://bugzilla.novell.com/show_bug.cgi?id=800514#c19 Frederic Crozat changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |fcrozat@suse.com InfoProvider|fcrozat@suse.com | --- Comment #19 from Frederic Crozat 2013-03-25 09:43:44 UTC --- (In reply to comment #16)

Somehow related: Google just told me that Debian has a systemd gui called "systemadm": http://packages.debian.org/de/sid/systemd-gui

Frederic, do you know if systemadm would be useful for openSUSE? Does it do what the YaST runlevel editor would do if it had systemd support? BTW: I didn't find it in the buildservice - does it hide somewhere? ;-)

it is available in systemd-ui package. But it isn't actively developed by upstream, unfortunately (but it should work). I think some of the YaST hackers could look at systemadm code, since it interact with systemd to get list of services and so on through systemd D-Bus api. -- 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=800514 https://bugzilla.novell.com/show_bug.cgi?id=800514#c21 FeiXiang Zhang changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |be@lokales.de --- Comment #21 from FeiXiang Zhang 2013-04-01 05:48:56 UTC --- *** Bug 811827 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=811827 -- 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=800514 https://bugzilla.novell.com/show_bug.cgi?id=800514#c22 --- Comment #22 from Alexander Winzer 2013-06-11 07:27:21 UTC --- I apologise I forgot to post a workaround, supported by a user of the german mailing list[1]. You just need to find an older distribution (or install in a VM) and get the file /etc/inittab. Copy this file to your 12.3 distribution and the yast runlevel editor works at least in console mode. I fixed this problem with 32 and 64 bit version of 12.3. So I guess it would be the most simple solution by openSUSE to provide this file with on of the next updates of that specific yast rpm. [1] http://lists.opensuse.org/opensuse-de/2013-04/msg00311.html -- 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=800514 https://bugzilla.novell.com/show_bug.cgi?id=800514#c24 --- Comment #24 from Alexander Winzer 2013-08-24 09:32:17 UTC --- What eaxctly does that mean? Will there be a yast service manager for openSUSE 12.3, too. Or will there be this new model finally appear with openSUSE 13.1. Could you please explain to me what "Factory" means in this case. And furthermore will my workaround be fixed automaticly? Or would I need to delete the file /etc/inittab or clean other files... Thanks a lot. -- 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=800514 https://bugzilla.novell.com/show_bug.cgi?id=800514#c26 --- Comment #26 from Alexander Winzer 2013-08-27 11:27:00 UTC --- Thanks for your help. But this doesn't exactly help: I insert the YaST-repo to my repos.d and did a "zypper dup". This upgrades only the following packages: install|libstorage4 |2.24.3-2.1 |i586 ||openSUSE_12.3_YaST install|perl-Bootloader |0.709-98.1 |i586 ||openSUSE_12.3_YaST install|yast2-x11 |3.0.1-2.1 |i586 ||openSUSE_12.3_YaST install|yast2-inetd-doc |3.0.0-6.17 |noarch||openSUSE_12.3_YaST install|yast2-theme-openSUSE |3.0.0-5.1 |noarch||openSUSE_12.3_YaST install|yast2-trans-de |3.0.0-206.2|noarch||openSUSE_12.3_YaST install|yast2-online-update-frontend|3.0.0-7.6 |noarch||openSUSE_12.3_YaST install|yast2-nfs-common |3.0.0-6.6 |noarch||openSUSE_12.3_YaST install|yast2-trans-stats |2.19.0-16.4|noarch||openSUSE_12.3_YaST install|libstorage-ruby |2.24.3-2.1 |i586 ||openSUSE_12.3_YaST install|yast2-theme-openSUSE-Oxygen |3.0.0-5.1 |noarch||openSUSE_12.3_YaST install|yast2-branding-openSUSE |3.0.0-29.2 |noarch||openSUSE_12.3_YaST install|yast2-control-center |3.0.0-3.1 |i586 ||openSUSE_12.3_YaST install|yast2-control-center-qt |3.0.0-3.1 |i586 ||openSUSE_12.3_YaST After all a "zypper up" kept telling me: Loading repository data... Reading installed packages... The following package updates will NOT be installed: autoyast2-installation yast2 yast2-add-on yast2-apparmor yast2-backup yast2-bootloader yast2-core yast2-country yast2-country-data yast2-firewall yast2-hardware-detection yast2-http-server yast2-inetd yast2-installation yast2-iscsi-client yast2-kerberos-client yast2-ldap yast2-ldap-client yast2-mail yast2-metapackage-handler yast2-mouse yast2-network yast2-nfs-client yast2-nis-client yast2-ntp-client yast2-online-update yast2-packager yast2-packager-webpin yast2-pam yast2-perl-bindings yast2-pkg-bindings yast2-printer yast2-proxy yast2-restore yast2-ruby-bindings yast2-runlevel yast2-samba-client yast2-samba-server yast2-scanner yast2-security yast2-slp yast2-sound yast2-storage yast2-sudo yast2-sysconfig yast2-transfer yast2-tune yast2-tv yast2-update yast2-users yast2-vm yast2-xml yast2-ycp-ui-bindings Nothing to do. I suspect I'll have to install at least "yast2-runlevel", but I became pretty careful after an accident yesterday. I updated it all by hand via "zypper install yast2... yast2 ... " which worked just fine. But after all I couldn't start yast2 anymore. It kept telling my there would be problems with missing ncurses plugins. Even a forced reinstall didn't work. Then I tried to repair my yast with "zypper dup" again without the YaST-repo, which didn't work at all. Finally a "zypper in -f $(rpm -qa --qf "%{NAME} ")" saved my system. So is my guess with "yast2-runlevel" right? Because of the trouble which caused me, I would only try it with this package a last time... -- 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=800514 https://bugzilla.novell.com/show_bug.cgi?id=800514#c28 --- Comment #28 from Alexander Winzer 2013-08-27 14:01:34 UTC --- I thought so. But as you can see "yast2-services-manager" wasn't offered even with this YaST-repo. I had (and have again) installed libncurses 4 and 5. Actually i tried a "zypper in -f libncurses4 libncurses5 libyui-ncurses4 libyui-ncurses-pkg4 ncurses-utils" before my "downgrade session". However it didn't help. Right now I see, that libncurses4 seems not involved anymore. I don't know, how version 4 was uninstalled and version 6 installed, because "zypper in -f $(rpm -qa --qf "%{NAME} ")" should just reinstall all my current packages. However a "rpm -qa --last | grep ncurses" shows this now: libyui-ncurses-pkg4-2.43.4.1-1.5.1.i586 Mon Aug 26 18:50:07 2013 libyui-ncurses4-2.43.3.1-1.5.1.i586 Mon Aug 26 18:26:31 2013 ncurses-utils-5.9-26.1.1.i586 Mon Aug 26 18:20:54 2013 libncurses5-5.9-26.1.1.i586 Mon Aug 26 18:19:55 2013 libncurses6-5.9-26.1.1.i586 Mon Aug 26 18:19:55 2013 I'll keep looking for "yast2-services-manager" and try my luck with it. Thanks, Alex -- 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=800514 https://bugzilla.novell.com/show_bug.cgi?id=800514#c30 --- Comment #30 from Alexander Winzer 2013-08-27 14:11:08 UTC --- OK. Here we go again. A "zypper in yast2-services-manager" and a "yast2" after it brings: terminate called after throwing an instance of 'YUIPluginException' what(): Couldn't load plug-in ncurses YaST got signal 6 at YCP file /usr/share/YaST2/clients/menu.rb:193 /sbin/yast2: line 431: 12381 Aborted $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS Is there any way besides a "zypper in -f $(rpm -qa --qf "%{NAME} ")" to fix this? -- 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=800514 https://bugzilla.novell.com/show_bug.cgi?id=800514#c32 --- Comment #32 from Alexander Winzer 2013-08-27 14:21:04 UTC --- You're right. Found the missing package, installed it with "zypper in libyui-ncurses-pkg5" and yast works fine, like it did before. Thanks for your patient help! -- 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.