[opensuse] stop and start x-server from console

Istvan Gabor

18 Dec 2013 18 Dec '13

19:53

Hello: As the subject says: I would like to stop and start x-server from a console window, eg vt1. Similar to what I could do in openSUSE 11.2 using init 3 init 5 commands. I have openSUSE 12.2 with kdm3 display manager. I tried so far: init 3; init 5 systemctl stop xdm.service systemctl restart.xdm.service of which none worked. ?? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Show replies by date

Carlos E. R.

18 Dec 18 Dec

20:02

On 2013-12-18 20:53, Istvan Gabor wrote:

...

init 3; init 5

This should work in any release. -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)

ellanios82

20:42

On 12/18/2013 10:02 PM, Carlos E. R. wrote:

...

On 2013-12-18 20:53, Istvan Gabor wrote:

...
init 3; init 5 This should work in any release.

- If, while using XFCE4 : one does CTL + ALT + F2 and logs on as Root, What command can open as Root, a second instance of Xfce4 , from console ? ................ thanks -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R.

20:56

On 2013-12-18 21:42, ellanios82 wrote:

...

- If, while using XFCE4 : one does CTL + ALT + F2 and logs on as Root,

What command can open as Root, a second instance of Xfce4 , from console ?

That's a different question. If you are root, this should work: startx -- :8 or, perhaps: startx xfce -- :8 The "startx" command is deprecated (not depreciated, that's a different word), but it still works. To allow it working as user, you have to do certain change to the permissions. It is documented, in the permission.local file. The correct procedure is start the second session via exit menu in desktop, but apparently, xfce does not have it. -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)

Felix Miata

21:55

On 2013-12-18 21:56 (GMT+0100) Carlos E. R. composed:

...

ellanios82 wrote:

...

...
- If, while using XFCE4 : one does CTL + ALT + F2 and logs on as Root,

...

...
What command can open as Root, a second instance of Xfce4 , from console ?

...

That's a different question.

...

If you are root, this should work:

...

startx -- :8

...

or, perhaps:

...

startx xfce -- :8

Likely neither. The login manager runs on :0. Next available X is :1, then :2, then :3. :8 is likely not defined. 'startx xfce -- :1' may be what he needs. I don't know if or where I might have xfce installed to try. I mostly stick to KDE3, KDE4 & TDE. Ctrl-Alt-F8 should focus :1 once it is running. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R.

22:24

On 2013-12-18 22:55, Felix Miata wrote:

...

On 2013-12-18 21:56 (GMT+0100) Carlos E. R. composed:

...

...
If you are root, this should work:

...
startx -- :8

...
or, perhaps:

...
startx xfce -- :8

Likely neither.

The first one works, the second doesn't (probably because the exact word is not 'xfce'). I tried on a virtual machine running 13.1, which almost crashed (after going from ctrl-alt-f7..8 successfully twice), probably because it is virtual. -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)

ellanios82

19 Dec 19 Dec

07:46

On 12/18/2013 11:55 PM, Felix Miata wrote:

...

Likely neither. The login manager runs on :0. Next available X is :1, then :2, then :3. :8 is likely not defined. 'startx xfce -- :1' may be what he needs. I don't know if or where I might have xfce installed to try. I mostly stick to KDE3, KDE4 & TDE. Ctrl-Alt-F8 should focus :1 once it is running.

_________ thanks, all . . . will try regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Per Jessen

06:54

Carlos E. R. wrote:

...

On 2013-12-18 21:42, ellanios82 wrote:

...
- If, while using XFCE4 : one does CTL + ALT + F2 and logs on as Root,

What command can open as Root, a second instance of Xfce4 , from console ?

That's a different question.

If you are root, this should work:

startx -- :8

or, perhaps:

startx xfce -- :8

The "startx" command is deprecated (not depreciated, that's a different word), but it still works. To allow it working as user, you have to do certain change to the permissions. It is documented, in the permission.local file.

For running doom3, I have long been using Alt-F2, "xinit doom3 -- :1" (on an elderly 10.3 system though). Might that work for xfce too? -- Per Jessen, Zürich (2.3°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R.

09:35

On 2013-12-19 07:54, Per Jessen wrote:

...

Carlos E. R. wrote:

...

For running doom3, I have long been using Alt-F2, "xinit doom3 -- :1" (on an elderly 10.3 system though). Might that work for xfce too?

xinit? Mmmm, right, you have to issue a program to run. I tried with none, I got an xterm alone. I tried on a virtual machine. When I issued ctrl-alt-f7 it switched, but on ctrl-alt-f8 there was nothing. Had to kill it (same as with startx). Might be related to trying on a vm. -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)

ellanios82

10:42

On 12/18/2013 10:56 PM, Carlos E. R. wrote:

...

On 2013-12-18 21:42, ellanios82 wrote:

...
- If, while using XFCE4 : one does CTL + ALT + F2 and logs on as Root,

What command can open as Root, a second instance of Xfce4 , from console ? That's a different question.

If you are root, this should work:

startx -- :8

or, perhaps:

startx xfce -- :8

The "startx" command is deprecated (not depreciated, that's a different word), but it still works. To allow it working as user, you have to do certain change to the permissions. It is documented, in the permission.local file.

The correct procedure is start the second session via exit menu in desktop, but apparently, xfce does not have it.

- as root , [ after CTL+ALT_F2 ] : # startx -- :2 successfully starts KDE ................. startx xfce -- :2 does not work : xfce GUI fails to initiate { not to worry } .................... thanks -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R.

11:06

On 2013-12-19 11:42, ellanios82 wrote:

...

On 12/18/2013 10:56 PM, Carlos E. R. wrote:

...

- as root , [ after CTL+ALT_F2 ] :

# startx -- :2 successfully starts KDE

.................

startx xfce -- :2 does not work : xfce GUI fails to initiate

{ not to worry }

You can try other incantations. Perhaps XFCE, xfce4... no, I tried those, too. Some other word then. I'm definitely sure that the syntax is correct (I have used it for ages), but we have to find the right word for xfce. -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)

ellanios82

13:00

On 12/19/2013 01:06 PM, Carlos E. R. wrote: ___________ "you can try other incantations. Perhaps XFCE, xfce4... no, I tried those, too. Some other word then. I'm definitely sure that the syntax is correct (I have used it for ages), but we have to find the right word for xfce." __________ - aha! : the incantation is : startxfce4 -- :2 [this succeeds start xfce4 ] ................... thanks -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R.

15:44

On 2013-12-19 14:00, ellanios82 wrote:

...

On 12/19/2013 01:06 PM, Carlos E. R. wrote: ___________ "you can try other incantations. Perhaps XFCE, xfce4... no, I tried those, too. Some other word then. I'm definitely sure that the syntax is correct (I have used it for ages), but we have to find the right word for xfce." __________

- aha! : the incantation is :

startxfce4 -- :2 [this succeeds start xfce4 ]

It crashed here! Both virtual machine and host were unusable, they both locked. I had to sshing from another machine, and then I killed the ssh session connecting host and guest. This killed startxfce4 and both machines recovered. -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)

Cristian Rodríguez

15:49

El 19/12/13 12:44, Carlos E. R. escribió:

...

Both virtual machine and host were unusable, they both locked.

What virtualization system is this ? looks like a bug in a kernel module .. it goes without saying a guest should not lockup the host.. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R.

16:28

On 2013-12-19 16:49, Cristian Rodríguez wrote:

...

El 19/12/13 12:44, Carlos E. R. escribió:

...
Both virtual machine and host were unusable, they both locked.

What virtualization system is this ? looks like a bug in a kernel module .. it goes without saying a guest should not lockup the host..

Vmware player, installed from VMware-Player-5.0.2-1031769.x86_64.bundle. There is a more recent version. The entire desktop, including the guest system window, froze. Clicks inside or outside were ignored. The gkrellm applet inside the guest froze at 100% cpu. I could not see the host applet, it was on another desktop. There was a popup error from the virtual machine, something about an out of bounds widget or something. I should have taken a photo with a camera. There was no new xfce desktop display started, it did not show. I think the crash happened when I tried ctrl-alt-f8 on the guest. I had started "startxfce4" from an ssh session from host to guest, as root (instead of doing ctrl-alt-f1 on it) I ssh-ed from my laptop. CPU usage was nil. I just killed the ssh session from host to guest, and things restored to normal. I can try it again later, now I have to do other chores :-) -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)

David C. Rankin

17:30

On 12/19/2013 04:42 AM, ellanios82 wrote:

...

- as root , [ after CTL+ALT_F2 ] :

# startx -- :2 successfully starts KDE

.................

startx xfce -- :2 does not work : xfce GUI fails to initiate

{ not to worry }

That's because you have to define what desktop is started by default and how to start them in ~/.xinitrc. Examples: #!/bin/sh # # ~/.xinitrc # # Executed by startx (run your window manager from here) exec startfluxbox Otherwise, you need to use the correct desktop launch routine from the command line. I.e. (values from an older box): gnome-session startkde startxfce4 startfluxbox If you have multiple versions installed, you can provide full path information to the target you want: /opt/kde/bin/startkde If you are worried about a specific desktop, then look at the start file for that desktop. Usually found with something like rpm -ql <desktop> | grep start Yast usually set the default in /etc/sysconfig/windowmanager with the DEFAULT_WM= parameter. HTH -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

ellanios82

20:06

On 12/19/2013 07:30 PM, David C. Rankin wrote:

...

On 12/19/2013 04:42 AM, ellanios82 wrote:

...
- as root , [ after CTL+ALT_F2 ] :

# startx -- :2 successfully starts KDE

.................

startx xfce -- :2 does not work : xfce GUI fails to initiate

{ not to worry }

That's because you have to define what desktop is started by default and how to start them in ~/.xinitrc. Examples:

#!/bin/sh # # ~/.xinitrc # # Executed by startx (run your window manager from here) exec startfluxbox

Otherwise, you need to use the correct desktop launch routine from the command line. I.e. (values from an older box):

gnome-session startkde startxfce4 startfluxbox

If you have multiple versions installed, you can provide full path information to the target you want:

/opt/kde/bin/startkde

If you are worried about a specific desktop, then look at the start file for that desktop. Usually found with something like

rpm -ql <desktop> | grep start

Yast usually set the default in /etc/sysconfig/windowmanager with the DEFAULT_WM= parameter.

HTH

- many thanks regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Istvan Gabor

00:30

"Carlos E. R." írta:

...

On 2013-12-18 20:53, Istvan Gabor wrote:

...
init 3; init 5

This should work in any release.

Should it or not, it does not work on my system. oS 12.2. I issued "init 3" as root in vt2, waited ~ 20 secs, pressed ctrl+alt+f7 to get back to my kde3 session, where I am writing this message now. Should not init 3 result in a blank screen on vt7 if it kill x server? Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Anton Aylward

00:57

Istvan Gabor said the following on 12/18/2013 07:30 PM:

...

"Carlos E. R." írta:

...
On 2013-12-18 20:53, Istvan Gabor wrote:

...
init 3; init 5

This should work in any release.

Should it or not, it does not work on my system. oS 12.2. I issued "init 3" as root in vt2, waited ~ 20 secs, pressed ctrl+alt+f7 to get back to my kde3 session, where I am writing this message now.

Should not init 3 result in a blank screen on vt7 if it kill x server?

Istvan

And what does # file $(which init) return on YOUR system? Perhaps try # logger MARK-BEGIN # init 3 # logger MARK-END and tell us what is in the log files between that begin/end. Knowing that time you can also get the report from 'journalctl' using the --since and --until options. In fact you could run 'journalctl -f' at another terminal while you try the 'init 3'. Do tell us what the results are. Logs are often very revealing. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Istvan Gabor

10:11

Anton Aylward írta:

...

Istvan Gabor said the following on 12/18/2013 07:30 PM:

...
"Carlos E. R." írta:

...
On 2013-12-18 20:53, Istvan Gabor wrote:

...
init 3; init 5

This should work in any release.

Should it or not, it does not work on my system. oS 12.2. I issued "init 3" as root in vt2, waited ~ 20 secs, pressed ctrl+alt+f7 to get back to my kde3 session, where I am writing this message now.

Should not init 3 result in a blank screen on vt7 if it kill x server?

Istvan

And what does

# file $(which init)

return on YOUR system?

# file $(which init) /sbin/init: symbolic link to `../lib/systemd/systemd

...

Perhaps try

# logger MARK-BEGIN # init 3 # logger MARK-END

and tell us what is in the log files between that begin/end.

in /var/log/messages I see: Dec 19 10:47:34 linux user: MARK-BEGIN Dec 19 10:47:36 linux swapon[21134]: swapon: /dev/sda6: swapon failed: Device or resource busy Dec 19 10:47:37 linux systemd[1]: dev-sda6.swap swap process exited, code=exited status=255 Dec 19 10:47:37 linux systemd[1]: Unit dev-sda6.swap entered failed state. Dec 19 10:47:43 linux user: MARK-END

...

Knowing that time you can also get the report from 'journalctl' using the --since and --until options.

# journalctl --since "Dec 19 10:46:30" If 'journalctl' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf journalctl # systemd-journalctl --since "Dec 19 10:46:30" systemd-journalctl: unrecognized option '--since' Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Anton Aylward

13:36

Istvan Gabor said the following on 12/19/2013 05:11 AM:

...

Anton Aylward írta:

...
And what does

# file $(which init)

return on YOUR system?

# file $(which init) /sbin/init: symbolic link to `../lib/systemd/systemd

Good.

...

...
Perhaps try

# logger MARK-BEGIN # init 3 # logger MARK-END

and tell us what is in the log files between that begin/end.

in /var/log/messages I see:

Dec 19 10:47:34 linux user: MARK-BEGIN Dec 19 10:47:36 linux swapon[21134]: swapon: /dev/sda6: swapon failed: Device or resource busy Dec 19 10:47:37 linux systemd[1]: dev-sda6.swap swap process exited, code=exited status=255 Dec 19 10:47:37 linux systemd[1]: Unit dev-sda6.swap entered failed state. Dec 19 10:47:43 linux user: MARK-END

Good.

...

...
Knowing that time you can also get the report from 'journalctl' using the --since and --until options.

# journalctl --since "Dec 19 10:46:30" If 'journalctl' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf journalctl

# systemd-journalctl --since "Dec 19 10:46:30" systemd-journalctl: unrecognized option '--since'

RTFM --since=, --until= Start showing entries on or newer than the specified date, or on or older than the specified date, respectively. Date specifications should be of the format "2012-10-30 18:17:16". Perhaps you'd be better of using the "-f" approach :-( -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Istvan Gabor

20 Dec 20 Dec

18:34

Anton Aylward írta:

...

Istvan Gabor said the following on 12/19/2013 05:11 AM:

...
Anton Aylward írta:

...
And what does

# file $(which init)

return on YOUR system?

# file $(which init) /sbin/init: symbolic link to `../lib/systemd/systemd

Good.

...
...
Perhaps try

# logger MARK-BEGIN # init 3 # logger MARK-END

and tell us what is in the log files between that begin/end.

in /var/log/messages I see:

Dec 19 10:47:34 linux user: MARK-BEGIN Dec 19 10:47:36 linux swapon[21134]: swapon: /dev/sda6: swapon failed: Device or resource busy Dec 19 10:47:37 linux systemd[1]: dev-sda6.swap swap process exited, code=exited status=255 Dec 19 10:47:37 linux systemd[1]: Unit dev-sda6.swap entered failed state. Dec 19 10:47:43 linux user: MARK-END

Good.

Sorry, but I don't know how interpret this. What is good? Does the above error message explain why the systemctl command does not work, or is it an independent problem? If it is the cause of the fail, how can I fix it? I still don't know how I can stop and start x-server from a command line. Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R.

21 Dec 21 Dec

23:27

On 2013-12-20 19:34, Istvan Gabor wrote:

...

I still don't know how I can stop and start x-server from a command line.

Yes, you do, but your system is broken and it does not work. -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" (Elessar)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Istvan Gabor

22 Dec 22 Dec

23:22

"Carlos E. R." írta:

...

On 2013-12-20 19:34, Istvan Gabor wrote:

...
I still don't know how I can stop and start x-server from a command line.

Yes, you do, but your system is broken and it does not work.

I have installed openSUSE 12.2 on three different computers. I installed packages only from openSUSE repos using YaST, and the systems have no package dependency issues. Still the systmectl and or init command you are referring does not work in any of these 3 systems. That is, what you are saying can be translated as: openSUSE 12.2 system is broken and it does not work. Apart from the above there should be some solution to restart x server. Maybe by killing and starting the x-server directly. Is it possible? Which process should be killed/started? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R.

23:42

On 2013-12-23 00:22, Istvan Gabor wrote:

...

"Carlos E. R." <> írta:

...

Apart from the above there should be some solution to restart x server. Maybe by killing and starting the x-server directly. Is it possible? Which process should be killed/started?

The sequence "init 3 ; init 5" has been working since before SuSE 5.2 to openSUSE 13.1. I see no reason why it would not work on openSUSE 12.2. If this would not work on 12.2, people would know it and be mad complaining about it. I tested 12.2 for a brief time when it was released and I'm certain it worked (99%). What, I have no idea. You must have done something to break it. I know no other way to properly restart the graphical server. You can try ctrl-alt-backspace, twice. It is forced, fast kill. -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" (Elessar)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Ken Schneider - openSUSE

23:56

On 12/22/2013 06:42 PM, Carlos E. R. pecked at the keyboard and wrote:

...

On 2013-12-23 00:22, Istvan Gabor wrote:

...
"Carlos E. R." <> írta:

...
Apart from the above there should be some solution to restart x server. Maybe by killing and starting the x-server directly. Is it possible? Which process should be killed/started?

The sequence "init 3 ; init 5" has been working since before SuSE 5.2 to openSUSE 13.1. I see no reason why it would not work on openSUSE 12.2. If this would not work on 12.2, people would know it and be mad complaining about it. I tested 12.2 for a brief time when it was released and I'm certain it worked (99%). What, I have no idea.

You must have done something to break it.

I know no other way to properly restart the graphical server.

You can try ctrl-alt-backspace, twice. It is forced, fast kill.

I had 12.2 installed before I installed 13.1 and I can confirm that using init 3 & init 5 DID work. Apparently Istvan has a major problem somewhere. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Felix Miata

23 Dec 23 Dec

01:24

On 2013-12-23 00:22 (GMT+0100) Istvan Gabor composed:

...

...
Yes, you do, but your system is broken and it does not work.

...

I have installed openSUSE 12.2 on three different computers. I installed packages only from openSUSE repos using YaST, and the systems have no package dependency issues.

...

Still the systmectl and or init command you are referring does not work in any of these 3 systems.

Are any or all 3 actually upgrades from 12.1, rather than "installations"?

...

That is, what you are saying can be translated as:

...

openSUSE 12.2 system is broken and it does not work.

If upgrades, maybe it's actually the upgrade process that is/was broken.

...

Apart from the above there should be some solution to restart x server. Maybe by killing and starting the x-server directly. Is it possible? Which process should be killed/started?

Something to try, especially if upgrades: If sysvinit-init is installed, replace it with systemd-sysvinit. If systemd-sysvinit is installed, replace it with sysvinit-init. Systemd was still rather far from complete in 12.2, and might be poorly compatible with whatever your deviations from default may be. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Ken Schneider - openSUSE

04:25

On 12/22/2013 08:24 PM, Felix Miata pecked at the keyboard and wrote:

...

On 2013-12-23 00:22 (GMT+0100) Istvan Gabor composed:

...
...
Yes, you do, but your system is broken and it does not work.

...
I have installed openSUSE 12.2 on three different computers. I installed packages only from openSUSE repos using YaST, and the systems have no package dependency issues.

...
Still the systmectl and or init command you are referring does not work in any of these 3 systems.

Are any or all 3 actually upgrades from 12.1, rather than "installations"?

...
That is, what you are saying can be translated as:

...
openSUSE 12.2 system is broken and it does not work.

If upgrades, maybe it's actually the upgrade process that is/was broken.

...
Apart from the above there should be some solution to restart x server. Maybe by killing and starting the x-server directly. Is it possible? Which process should be killed/started?

Something to try, especially if upgrades:

If sysvinit-init is installed, replace it with systemd-sysvinit. If systemd-sysvinit is installed, replace it with sysvinit-init. Systemd was still rather far from complete in 12.2, and might be poorly compatible with whatever your deviations from default may be.

I should have added that I was using sysvinit in 12.2 as systemd was nothing but pre-alpha software passed off as something usable. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Felix Miata

04:36

On 2013-12-22 23:25 (GMT-0500) Ken Schneider - openSUSE composed:

...

Felix Miata composed:

...

...
Are any or all 3 actually upgrades from 12.1, rather than "installations"?

...

...
...
That is, what you are saying can be translated as:

...

...
...
openSUSE 12.2 system is broken and it does not work.

...

...
If upgrades, maybe it's actually the upgrade process that is/was broken.

...

...
Something to try, especially if upgrades:

...

...
If sysvinit-init is installed, replace it with systemd-sysvinit. If systemd-sysvinit is installed, replace it with sysvinit-init. Systemd was still rather far from complete in 12.2, and might be poorly compatible with whatever your deviations from default may be.

...

I should have added that I was using sysvinit in 12.2 as systemd was nothing but pre-alpha software passed off as something usable.

What you wrote differs from what I wrote only in being less gracious to the infant systemd. My point was his problem may well depend on which he has installed, and what he has installed may well depend on whether he installed or upgraded to reach 12.2. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Istvan Gabor

30 Dec 30 Dec

22:03

Felix Miata írta:

...

On 2013-12-23 00:22 (GMT+0100) Istvan Gabor composed:

[snip]

...

...
Still the systmectl and or init command you are referring does not work in any of these 3 systems.

Are any or all 3 actually upgrades from 12.1, rather than "installations"?

Sorry for the delayed reply. All installations are fresh from DVD. systemd-init was installed as default and I did not change it. [snip]

...

If sysvinit-init is installed, replace it with systemd-sysvinit. If systemd-sysvinit is installed, replace it with sysvinit-init. Systemd was still rather far from complete in 12.2, and might be poorly compatible with whatever your deviations from default may be.

I replaced systemd-sysvinit with sysvinit-init, rebooted, and it does not work. When I issue 'init 3' in a terminal (eg. vt2) it gives: # init 3 INIT: Switching to runlevel: 3 # 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 However the x-window is not stopped. I checked /etc/init.d/rc3.d directory and found there is no K*xdm file in it. I don't know if it is normal or not. I can not stop xdm manually either: # /etc/init.d/xdm stop 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 X server is not stopped. I also found something strange: When I switch from a terminal to vt7 by pressing ctr+alt+F7 the boot screen bacground image appears for a moment before getting the desktop. I don't know if this has to do with my problem or not. I have no idea what blocks stopping of x server. Might it be - KDM3 ? - lack of plymouth (I do not have it installed) ? This is very weird. Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R.

23:10

On 2013-12-30 23:03, Istvan Gabor wrote:

...

Felix Miata <> írta:

...

I replaced systemd-sysvinit with sysvinit-init, rebooted, and it does not work.

When I issue 'init 3' in a terminal (eg. vt2) it gives:

# init 3 INIT: Switching to runlevel: 3 # 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

However the x-window is not stopped.

I checked /etc/init.d/rc3.d directory and found there is no K*xdm file in it. I don't know if it is normal or not.

I can not stop xdm manually either:

# /etc/init.d/xdm stop 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

X server is not stopped.

There is some bug in that file. Are you really using xdm? Won't it be kdm, or kdm3, or kdm4, or gdm? The one you really use must match the "DISPLAYMANAGER" entry in the "/etc/sysconfig/displaymanager" file. -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" (Elessar)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Istvan Gabor

31 Dec 31 Dec

00:11

"Carlos E. R." írta:

...

On 2013-12-30 23:03, Istvan Gabor wrote:

...
Felix Miata <> írta:

...
I replaced systemd-sysvinit with sysvinit-init, rebooted, and it does not work.

When I issue 'init 3' in a terminal (eg. vt2) it gives:

# init 3 INIT: Switching to runlevel: 3 # 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

However the x-window is not stopped.

I checked /etc/init.d/rc3.d directory and found there is no K*xdm file in it. I don't know if it is normal or not.

I can not stop xdm manually either:

# /etc/init.d/xdm stop 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

X server is not stopped.

There is some bug in that file.

Are you really using xdm? Won't it be kdm, or kdm3, or kdm4, or gdm?

The one you really use must match the "DISPLAYMANAGER" entry in the "/etc/sysconfig/displaymanager" file.

That is set to kdm3. # cat /etc/sysconfig/displaymanager |grep DISPLAYMANAGER= DISPLAYMANAGER="kdm3" But there is no kdm3 script in /etc/init.d/ to start/stop kdm3. I can stop kdm3 by killing it (kill xxxx). init 5 then restarts kdm3, it seems that part is OK. Now I have to trace why kdm3 is not stopped by init 3. Thanks you, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R.

00:38

On 2013-12-31 01:11, Istvan Gabor wrote:

...

...
The one you really use must match the "DISPLAYMANAGER" entry in the "/etc/sysconfig/displaymanager" file.

That is set to kdm3.

# cat /etc/sysconfig/displaymanager |grep DISPLAYMANAGER= DISPLAYMANAGER="kdm3"

But there is no kdm3 script in /etc/init.d/ to start/stop kdm3.

I don't remember if there should be, and I don't have a 12.2 test system to verify it. It maybe script "xdm" which should stop/start the appropriate process. Maybe, as support for kdm3 was changing hands, there is a mistake there somewhere. Besides that, you have an error in script "/etc/init.d/before.local", that's the killproc error you see. -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" (Elessar)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Felix Miata

01:16

On 2013-12-31 01:11 (GMT+0100) Istvan Gabor composed:

...

...
Are you really using xdm? Won't it be kdm, or kdm3, or kdm4, or gdm?

...

...
The one you really use must match the "DISPLAYMANAGER" entry in the "/etc/sysconfig/displaymanager" file.

...

That is set to kdm3.

...

# cat /etc/sysconfig/displaymanager |grep DISPLAYMANAGER= DISPLAYMANAGER="kdm3"

...

But there is no kdm3 script in /etc/init.d/ to start/stop kdm3.

...

I can stop kdm3 by killing it (kill xxxx).

...

init 5 then restarts kdm3, it seems that part is OK.

...

Now I have to trace why kdm3 is not stopped by init 3.

I thought a possible workaround might be to look in kdmrc, find any instances of TerminateServer=false and if found, change it/them to true. I booted a 12.2/KDE3 system here with sysvinit-init installed directly to runlevel 5. Init 3 from tty3 root login fails to stop KDM here too. NAICT, it is /etc/init.d/xdm that starts whatever DM is configured in /etc/sysconfig/displaymanager's DISPLAYMANAGER. I tried copying the smaller xdm file from the host's 12.1 partition to 12.2's and repeating. Init 3 still fails to stop KDM. Looks like https://bugzilla.novell.com/show_bug.cgi?id=783862 needs some serious poking. I'm afraid our best solution may turn out to be not using runlevel 5 at all, startx instead. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R.

02:10

On 2013-12-31 02:16, Felix Miata wrote:

...

Looks like https://bugzilla.novell.com/show_bug.cgi?id=783862 needs some serious poking. I'm afraid our best solution may turn out to be not using runlevel 5 at all, startx instead.

I suggest not using kdm3 at all, but something else, and let each user choose kde3 if he wants. -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" (Elessar)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

David C. Rankin

18:16

On 12/30/2013 08:10 PM, Carlos E. R. wrote:

...

On 2013-12-31 02:16, Felix Miata wrote:

...
Looks like https://bugzilla.novell.com/show_bug.cgi?id=783862 needs some serious poking. I'm afraid our best solution may turn out to be not using runlevel 5 at all, startx instead.

I suggest not using kdm3 at all, but something else, and let each user choose kde3 if he wants.

Carlos, If I recall correctly, the kdm3 (default) in YAST is just a very very old default from 10.X days that probably has not changed in years. I scanned the bug and among the bickering over whether sysvinit is dead, blah... it is referred to as a "kde problem". I think the problem may be a yast default problem. (or /etc/sysconfig/displaymanager default problem) Just a thought... -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R.

18:22

On 2013-12-31 19:16, David C. Rankin wrote:

...

On 12/30/2013 08:10 PM, Carlos E. R. wrote:

...

...
I suggest not using kdm3 at all, but something else, and let each user choose kde3 if he wants.

Carlos,

If I recall correctly, the kdm3 (default) in YAST is just a very very old default from 10.X days that probably has not changed in years. I scanned the bug and among the bickering over whether sysvinit is dead, blah... it is referred to as a "kde problem". I think the problem may be a yast default problem. (or /etc/sysconfig/displaymanager default problem) Just a thought...

No, kdm3 is no longer the default. Unless you installed long ago and then upgraded the system in place. -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" (Elessar)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Felix Miata

19 Dec 19 Dec

01:11

On 2013-12-19 01:30 (GMT+0100) Istvan Gabor composed:

...

...
...
init 3; init 5

...

...
This should work in any release.

...

Should it or not, it does not work on my system. oS 12.2.

...

I issued "init 3" as root in vt2, waited ~ 20 secs, pressed ctrl+alt+f7 to get back to my kde3 session, where I am writing this message now.

It fails for me in 12.2 too. 12.2 shipped with an incomplete transition from sysvinit to systemd init. Look in 'ps -A' output to see what init 3 failed to terminate, terminate it manually, then you should be good to go, until you try the same thing again. Support for 12.2 won't be lasting much longer. You might wish to consider solving the problem by upgrading sooner rather than later if https://bugs.freedesktop.org/show_bug.cgi?id=39949 or other missing or broken features aren't a problem for you. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Anton Aylward

04:06

Felix Miata said the following on 12/18/2013 08:11 PM:

...

On 2013-12-19 01:30 (GMT+0100) Istvan Gabor composed:

...
...
...
init 3; init 5

...
...
This should work in any release.

...
Should it or not, it does not work on my system. oS 12.2.

...
I issued "init 3" as root in vt2, waited ~ 20 secs, pressed ctrl+alt+f7 to get back to my kde3 session, where I am writing this message now.

It fails for me in 12.2 too. 12.2 shipped with an incomplete transition from sysvinit to systemd init. Look in 'ps -A' output to see what init 3 failed to terminate, terminate it manually, then you should be good to go, until you try the same thing again.

Does # systemctl --failed work in 12.2? I does in 12.3. It will tell you what the 'init 3' aka 'systemctl isolate multi-user.target' failed to do. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Felix Miata

07:45

On 2013-12-18 23:06 (GMT-0500) Anton Aylward composed:

...

Felix Miata composed:

...

...
On 2013-12-19 01:30 (GMT+0100) Istvan Gabor composed:

...

...
...
...
...
init 3; init 5

...

...
...
...
This should work in any release.

...

...
...
Should it or not, it does not work on my system. oS 12.2.

...

...
...
I issued "init 3" as root in vt2, waited ~ 20 secs, pressed ctrl+alt+f7 to get back to my kde3 session, where I am writing this message now.

...

...
It fails for me in 12.2 too. 12.2 shipped with an incomplete transition from sysvinit to systemd init. Look in 'ps -A' output to see what init 3 failed to terminate, terminate it manually, then you should be good to go, until you try the same thing again.

...

Does # systemctl --failed work in 12.2?

Not on host gx150 at least. Only unit listed is dev-sda8.swap loaded failed failed /dev/sda8 After booting with 3 on cmdline, root login, init 5; init 3, ps -A shows Xorg still with PID 1630 on tty7, and three ? entries for kdm*, 1615 before, 1659 & 1660 after 1630.

...

I does in 12.3. It will tell you what the 'init 3' aka 'systemctl isolate multi-user.target' failed to do. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)

Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R.

09:38

On 2013-12-19 08:45, Felix Miata wrote:

...

On 2013-12-18 23:06 (GMT-0500) Anton Aylward composed:

...

...
Does # systemctl --failed work in 12.2?

Not on host gx150 at least. Only unit listed is

dev-sda8.swap loaded failed failed /dev/sda8

After booting with 3 on cmdline, root login, init 5; init 3, ps -A shows Xorg still with PID 1630 on tty7, and three ? entries for kdm*, 1615 before, 1659 & 1660 after 1630.

Well, 12.2 must be broken or missing something. I never installed it (save a vm somewhere), so I don't know. -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)

Anton Aylward

13:28

Felix Miata said the following on 12/19/2013 02:45 AM:

...

...
...
Does # systemctl --failed work in 12.2? Not on host gx150 at least. Only unit listed is

dev-sda8.swap loaded failed failed /dev/sda8

I'm confused. If it doesn't work then why does it report that? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Felix Miata

13:45

On 2013-12-19 08:28 (GMT-0500) Anton Aylward composed:

...

Felix Miata composed:

...

...
...
...
Does # systemctl --failed work in 12.2?

...

...
Not on host gx150 at least. Only unit listed is

...

...
dev-sda8.swap loaded failed failed /dev/sda8

...

I'm confused. If it doesn't work then why does it report that?

Your guess is probably better than mine. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Anton Aylward

14:18

Felix Miata said the following on 12/19/2013 08:45 AM:

...

On 2013-12-19 08:28 (GMT-0500) Anton Aylward composed:

...
Felix Miata composed:

...
...
...
...
Does # systemctl --failed work in 12.2?

...
...
Not on host gx150 at least. Only unit listed is

...
...
dev-sda8.swap loaded failed failed /dev/sda8

...
I'm confused. If it doesn't work then why does it report that?

Your guess is probably better than mine.

I meant 'if it doesn't work why does it report anything rather than SIGX or some other error message. Its reporting something meaningful therefore it does work. What I'd do now is look to the logs. Systemd has good logging facilities of you choose to make use of it. RTFM and the blog advisories on it. As a matter of course I check them after booting in case I'm missing something. -- In war, three quarters turns on personal character and relations; the balance of manpower and materials counts only for the remaining quarter. - Napoleon I -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Istvan Gabor

10:18

Felix Miata írta:

...

On 2013-12-19 01:30 (GMT+0100) Istvan Gabor composed:

...
...
...
init 3; init 5

...
...
This should work in any release.

...
Should it or not, it does not work on my system. oS 12.2.

...
I issued "init 3" as root in vt2, waited ~ 20 secs, pressed ctrl+alt+f7 to get back to my kde3 session, where I am writing this message now.

It fails for me in 12.2 too. 12.2 shipped with an incomplete transition from sysvinit to systemd init. Look in 'ps -A' output to see what init 3 failed to terminate, terminate it manually, then you should be good to go, until you try the same thing again.

ps -A list 149 lines like: 21229 ? 00:00:00 kio_uiserver 21233 pts/4 00:00:00 bash 21308 ? 00:00:00 kworker/3:0 21329 ? 00:00:00 kworker/2:0 but there's no indication which one failed.

...

Support for 12.2 won't be lasting much longer. You might wish to consider solving the problem by upgrading sooner rather than later if https://bugs.freedesktop.org/show_bug.cgi?id=39949 or other missing or broken features aren't a problem for you.

You know I am KDE3 fanatic. I installed oS 12.3 but I could not make HAL running. HAL is required for removable media automounting and removing. I reverted back to 12.2 since HAL works in it well. Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Alvin Beach

18 Dec 18 Dec

20:09

Hello, What I do is: systemctl isolate runlevel3.target systemctl isolate graphical.target If the runlevel3.target doesn't work, try multi-user.target. To get a list of "targets", try this: systemctl isolate <tab-key><tab-key> Auto-complete will list the targets. Cheers, Alvin On 18/12/13 15:53, Istvan Gabor wrote:

...

Hello:

As the subject says: I would like to stop and start x-server from a console window, eg vt1. Similar to what I could do in openSUSE 11.2 using init 3 init 5 [snip]

Istvan

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

John Andersen

20:12

On 12/18/2013 12:09 PM, Alvin Beach wrote:

...

What I do is:

systemctl isolate runlevel3.target systemctl isolate graphical.target

If the runlevel3.target doesn't work, try multi-user.target.

To get a list of "targets", try this:

systemctl isolate <tab-key><tab-key>

Auto-complete will list the targets.

Init 5 was obtuse enough. Whoever dreamed up all this nonsense needs a through bitchslap. Every morning. Till its fixed. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Jim Henderson

20:22

New subject: [opensuse] Re: stop and start x-server from console

On Wed, 18 Dec 2013 12:12:46 -0800, John Andersen wrote:

...

On 12/18/2013 12:09 PM, Alvin Beach wrote:

...
What I do is:

systemctl isolate runlevel3.target systemctl isolate graphical.target

If the runlevel3.target doesn't work, try multi-user.target.

To get a list of "targets", try this:

systemctl isolate <tab-key><tab-key>

Auto-complete will list the targets.

Init 5 was obtuse enough. Whoever dreamed up all this nonsense needs a through bitchslap. Every morning. Till its fixed.

How about creating two script files: #!/bin/bash systemctl isolate graphical.target #!/bin/bash systemctl isolate multi-user.target Call them what you want so you can remember how to switch. Problem solved, and no bitchslapping needed. Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

John Andersen

20:27

New subject: [opensuse] Re: stop and start x-server from console

On 12/18/2013 12:22 PM, Jim Henderson wrote:

...

Problem solved, and no bitchslapping needed.

Yes, by all means lets each create machine specific scripts to do something that use to be a world standard one liner. Way to go Jim. That way nobody will know how to do it, and we can all just reboot. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R.

20:40

New subject: [opensuse] Re: stop and start x-server from console

On 2013-12-18 21:27, John Andersen wrote:

...

On 12/18/2013 12:22 PM, Jim Henderson wrote:

...
Problem solved, and no bitchslapping needed.

Yes, by all means lets each create machine specific scripts to do something that use to be a world standard one liner. Way to go Jim.

You don't need to do anything at all. "init 3" and "init 5" both work fine, the openSUSE distro includes them by default. If your system does not have them, you have a problem. If you get an error, post it here. -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)

Christopher Myers

20:42

New subject: [opensuse] Re: stop and start x-server from console

Is it maybe possible that even though you kicked up "init 5" your console didn't switch over to the right screen for some odd reason? Once you do the init 5, wait a little bit and hit CTRL+ALT+F7 and see if it pops you over to the GUI. Chris -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Jim Henderson

20:43

New subject: [opensuse] Re: stop and start x-server from console

On Wed, 18 Dec 2013 12:27:29 -0800, John Andersen wrote:

...

On 12/18/2013 12:22 PM, Jim Henderson wrote:

...
Problem solved, and no bitchslapping needed.

Yes, by all means lets each create machine specific scripts to do something that use to be a world standard one liner. Way to go Jim.

That way nobody will know how to do it, and we can all just reboot.

Then propose a better solution rather than just whining about it, or proposing solutions that involve violence against those who made decisions you don't agree with. Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Linda Walsh

21:55

New subject: [opensuse] Re: stop and start x-server from console

Jim Henderson wrote:

...

On Wed, 18 Dec 2013 12:27:29 -0800, John Andersen wrote:

...
On 12/18/2013 12:22 PM, Jim Henderson wrote:

...
Problem solved, and no bitchslapping needed. Yes, by all means lets each create machine specific scripts to do something that use to be a world standard one liner. Way to go Jim.

That way nobody will know how to do it, and we can all just reboot.

Then propose a better solution rather than just whining about it, or proposing solutions that involve violence against those who made decisions you don't agree with.

violence? I think the term implies a bit of of the severity of being slapped w/wet noodles in this context... But to answer your question -- I propose sysVinit! then we can stay with something that, while a bit arcane, was fairly well known by most people using a *nix derivative. But I have to add (for O.Suse): -------- Original Message --------

...

From: Carlos E. R. You don't need to do anything at all. "init 3" and "init 5" both work fine, the openSUSE distro includes them by default.

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Jim Henderson

22:14

New subject: [opensuse] Re: stop and start x-server from console

On Wed, 18 Dec 2013 13:55:20 -0800, Linda Walsh wrote:

...

Jim Henderson wrote:

...
On Wed, 18 Dec 2013 12:27:29 -0800, John Andersen wrote:

...
On 12/18/2013 12:22 PM, Jim Henderson wrote:

...
Problem solved, and no bitchslapping needed. Yes, by all means lets each create machine specific scripts to do something that use to be a world standard one liner. Way to go Jim.

That way nobody will know how to do it, and we can all just reboot.

Then propose a better solution rather than just whining about it, or proposing solutions that involve violence against those who made decisions you don't agree with.

violence? I think the term implies a bit of of the severity of being slapped w/wet noodles in this context...

Sorry, but I don't see slapping someone - even with wet noodles (if indeed that's the intent) - every morning (and that's not what I took away from John's post) is a constructive way to get something you want changed changed. I am disturbed by this propensity that some people have to say "well, just smack them silly until they see it my way" rather than to consider that *maybe* there's a good reason for change. I'm not a fan of change for change's sake, and while I originally thought the move to systemd was perhaps not a good call, I'm happy with it now. I'm still learning it, but I enjoy learning new things. I understand that some people don't, though - that change is anathema to how some people operate. But that makes me wonder why they want to use a system (Linux) that is *always* changing.

...

But to answer your question -- I propose sysVinit! then we can stay with something that, while a bit arcane, was fairly well known by most people using a *nix derivative.

Well, go ahead and maintain sysvinit, then, Linda. Personally, I prefer the speed that systemd brings to the boot process, even though my systems don't boot very frequently (they're "always on" systems).

...

But I have to add (for O.Suse):

-------- Original Message --------

...
From: Carlos E. R. You don't need to do anything at all. "init 3" and "init 5" both work fine, the openSUSE distro includes them by default.

Indeed, those still work (generally) as well. So for those who are averse to learning new ways of doing things, the old way is still there if you want. Problem solved - and no need to bitchslap anyone, with noodles or with hands. Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R.

22:31

New subject: [opensuse] Re: stop and start x-server from console

On 2013-12-18 23:14, Jim Henderson wrote:

...

Indeed, those still work (generally) as well. So for those who are averse to learning new ways of doing things, the old way is still there if you want. Problem solved - and no need to bitchslap anyone, with noodles or with hands.

Actually, it is the new way with an old name ;-) Telcontar:~ # which init /sbin/init Telcontar:~ # file /sbin/init /sbin/init: symbolic link to `../usr/lib/systemd/systemd' Telcontar:~ # It is the systemd binary:

...

Telcontar:~ # file /usr/lib/systemd/systemd /usr/lib/systemd/systemd: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=0x5f6250d6572275eaa678a6b2689062290a90f639, stripped Telcontar:~ #

Simply, when it recognizes it is being called "init", it automatically does the trick, for compatibility. It is not the real old "init". Telcontar:~ # rpm -qf /sbin/init systemd-sysvinit-195-13.45.1.x86_64 Telcontar:~ # It is there for compatibility shake. And that's a good thing™ Yes, I know there is a new syntax for doing it, but I'm not going to learn that particular trick if I can avoid it. Other systemd tricks, yes, of course :-) -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)

Jim Henderson

19 Dec 19 Dec

00:51

New subject: [opensuse] Re: stop and start x-server from console

On Wed, 18 Dec 2013 23:31:51 +0100, Carlos E. R. wrote:

...

...
Indeed, those still work (generally) as well. So for those who are averse to learning new ways of doing things, the old way is still there if you want. Problem solved - and no need to bitchslap anyone, with noodles or with hands.

Actually, it is the new way with an old name ;-)

Well, yes, I knew that. But from the end user perspective, it's the same as it was with sysvinit, or should be. Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Cristian Rodríguez

00:51

New subject: [opensuse] Re: stop and start x-server from console

El 18/12/13 19:31, Carlos E. R. escribió:

...

Yes, I know there is a new syntax for doing it, but I'm not going to learn that particular trick if I can avoid it. Other systemd tricks, yes, of course :-)

init 5 and init 3 work in openSUSE 13.1, in previous releases there were problems, "runlevel change" (which isn't really, just a compat shim) could possibly be cancelled by other conflicting jobs and may malfunction, in current releases, the process is irreversible. If it does not work for someone, it is because there is still one race condition lingering around that I have seen in front of my eyes recently, I am not sure if it is a bug in plymouth or in the DRM stack but disabling plymouth workarounds it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Per Jessen

07:03

New subject: [opensuse] Re: stop and start x-server from console

Jim Henderson wrote: [snip]

...

I enjoy learning new things.

I understand that some people don't, though - that change is anathema to how some people operate. But that makes me wonder why they want to use a system (Linux) that is *always* changing.

Slightly OT, but we should consider that not every user of Linux chose to use it. It is simply a tool that is provided. -- Per Jessen, Zürich (2.6°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Jim Henderson

20 Dec 20 Dec

00:19

New subject: [opensuse] Re: stop and start x-server from console

On Thu, 19 Dec 2013 08:03:14 +0100, Per Jessen wrote:

...

Jim Henderson wrote:

[snip]

...
I enjoy learning new things.

I understand that some people don't, though - that change is anathema to how some people operate. But that makes me wonder why they want to use a system (Linux) that is *always* changing.

Slightly OT, but we should consider that not every user of Linux chose to use it. It is simply a tool that is provided.

That's probably not a normal use case, though - edge cases are a different topic. I'm talking about users like John, who seem to hate change and don't want to learn new stuff, but who seem to have made the choice to switch to Linux. Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Richard Creighton

10:15

New subject: [opensuse] Re: stop and start x-server from console

John Andersen wrote:

...

On 12/18/2013 12:22 PM, Jim Henderson wrote:

...
Problem solved, and no bitchslapping needed. Yes, by all means lets each create machine specific scripts to do something that use to be a world standard one liner. Way to go Jim.

That way nobody will know how to do it, and we can all just reboot.

Ah yes, the Mickeysoft 'Doze way of doing things :) Richard -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Istvan Gabor

18:39

Alvin Beach írta:

...

Hello,

What I do is:

systemctl isolate runlevel3.target systemctl isolate graphical.target

If the runlevel3.target doesn't work, try multi-user.target.

Unfortunatley none of the above works in my system.

...

To get a list of "targets", try this:

systemctl isolate <tab-key><tab-key>

systemctl isolate <tab> <tab> /that is pressing tab button twice/ in my system gives: # systemctl isolate Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit avahi-daemon.socket dev-disk-byx2duuid-ba2d6b29x2d0af9x2d4943x2d870bx2d152516a037dd.swap syslog.socket udev-control.socket Thanks, Istvan

...

Auto-complete will list the targets.

Cheers,

Alvin

On 18/12/13 15:53, Istvan Gabor wrote:

...
Hello:

As the subject says: I would like to stop and start x-server from a console window, eg vt1. Similar to what I could do in openSUSE 11.2 using init 3 init 5 [snip]

Istvan

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Alvin Beach

18:50

Hello Istvan, I'd say there is something wrong with systemd on your system. What version of openSUSE are your running (if you have already said, I apologise as I have missed that message)? I am running 12.3. Have you tried reinstalling systemd (in Yast, just force an update?) The versions I have installed are (using: rpm -qa '*systemd*') systemd-analyze-195-13.45.1.x86_64 systemd-sysvinit-195-13.45.1.x86_64 systemd-presets-branding-openSUSE-0.2.0-2.5.1.noarch systemd-195-13.45.1.x86_64 Alvin On 20/12/13 14:39, Istvan Gabor wrote:

...

Alvin Beach írta:

...
Hello,

What I do is:

systemctl isolate runlevel3.target systemctl isolate graphical.target

If the runlevel3.target doesn't work, try multi-user.target.

Unfortunately none of the above works in my system.

...
To get a list of "targets", try this:

systemctl isolate <tab-key><tab-key>

systemctl isolate <tab> <tab> /that is pressing tab button twice/ in my system gives:

# systemctl isolate Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit Failed to issue method call: Unknown unit [snip] Failed to issue method call: Unknown unit

avahi-daemon.socket dev-disk-byx2duuid-ba2d6b29x2d0af9x2d4943x2d870bx2d152516a037dd.swap syslog.socket udev-control.socket

Thanks,

Istvan [snip]

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Cristian Rodríguez

19:05

El 20/12/13 15:50, Alvin Beach escribió:

...

Hello Istvan,

I'd say there is something wrong with systemd on your system.

In this particular case, there is nothing wrong with systemd, but with the shell completion scripts . -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

3775

Age (days ago)

3788

Last active (days ago)

List overview

Download

62 comments

15 participants

participants (15)

Alvin Beach
Anton Aylward
Carlos E. R.
Christopher Myers
Cristian Rodríguez
David C. Rankin
ellanios82
Felix Miata
Istvan Gabor
Jim Henderson
John Andersen
Ken Schneider - openSUSE
Linda Walsh
Per Jessen
Richard Creighton