[opensuse-kde] cannot restart kdm
Hi, I have a problem with kdm. After the latest update, 'sudo zypper ps' gives me PID | PPID | UID | Login | Befehl | Dienst | Dateien ------+------+-----+-------+--------+--------+-------------------------------- 1441 | 1 | 0 | root | kdm | | /usr/bin/kdm;54097cbe (deleted) 22103 | 1441 | 0 | root | kdm | | /usr/bin/kdm;54097cbe (deleted) Since recently, a $ sudo systemctl restart xdm.service would restart kdm. Not anymore. Even after $ sudo systemctl stop xdm.service kdm keeps running. I had the same problem a few days ago, then I decided to simply kill the kdm-process. Alas, that shut me out of the system (lost the text consoles completely, just a blank screen with a blinking underscore in the upper left corner, no reaction to keyboard) and I had to reboot. Below is the output of 'systemctl status xdm.service' Should this still work, or is there a new/other way of (re)starting the display manager? Any ideas to how I can get this working again? Regards mararm $ sudo systemctl status xdm.service xdm.service - LSB: X Display Manager Loaded: loaded (/etc/init.d/xdm) Active: inactive (dead) since Fri, 2014-09-05 11:10:24 CEST; 27min ago Process: 22085 ExecStop=/etc/init.d/xdm stop (code=exited, status=0/SUCCESS) Process: 21836 ExecStart=/etc/init.d/xdm start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/xdm.service ├ 1441 /usr/bin/kdm └ 22099 /usr/bin/Xorg -br :0 vt7 -nolisten tcp -seat seat0... Sep 05 11:09:09 08-15-i5.site kdm[1441]: Quitting Plymouth with transition Sep 05 11:09:09 08-15-i5.site kdm[1441]: Is Plymouth still running? no Sep 05 11:10:24 08-15-i5.site systemd[1]: Stopping LSB: X Display Manager... Sep 05 11:10:24 08-15-i5.site xdm[22085]: Shutting down service kdm..done Sep 05 11:10:24 08-15-i5.site systemd[1]: Stopped LSB: X Display Manager. Sep 05 11:10:28 08-15-i5.site kdm[21914]: :0[21914]: Abnormal termination of...0 Sep 05 11:10:28 08-15-i5.site kdm[1441]: plymouth should quit after server s...p Sep 05 11:10:28 08-15-i5.site kdm[1441]: Quitting Plymouth with transition Sep 05 11:10:28 08-15-i5.site kdm[1441]: Is Plymouth still running? no Sep 05 11:20:13 08-15-i5.site kdm[22103]: :0[22103]: pam_unix(xdm:session): ...) -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Hi, I completely forgot, this is opensuse 12.3 with KDE 4.14.0 from KDE:Current on Linux 3.15.8-2.g258e3b0-desktop #1 SMP PREEMPT Tue Aug 5 04:15:41 UTC 2014 (258e3b0) x86_64 x86_64 x86_64 GNU/Linux -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
I think it was renamed to display-manager.service I ran zypper verify recently and was surprised to have it recommend the removal of xdm, so something might have changed recently? I removed xdm and kdm still works. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
* Sean Watson <seanpwatson@live.com> [09-05-14 05:57]:
I think it was renamed to display-manager.service
I ran zypper verify recently and was surprised to have it recommend the removal of xdm, so something might have changed recently? I removed xdm and kdm still works. --
rather display-manager.service is provided by xdm.rpm -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 05.09.2014 12:04, Patrick Shanahan wrote:
* Sean Watson <seanpwatson@live.com> [09-05-14 05:57]:
I think it was renamed to display-manager.service
I ran zypper verify recently and was surprised to have it recommend the removal of xdm, so something might have changed recently? I removed xdm and kdm still works. --
rather display-manager.service is provided by xdm.rpm
I do not have such a service, $ sudo systemctl list-units --all | grep -i display xdm.service loaded inactive dead LSB: X Display Manager and $ zypper search display-manager returns nothing. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 09/05/2014 05:43 AM, mararm wrote:
Any ideas to how I can get this working again?
When xdm/kdm won't start for me, the reason usually lies in Xorg. Check your logs in /var/log/s for both {xk}dm.{log,error} and the Xorg.0.log -- 'A virus is what people who can't spell pneumonia get.' -- Eric Morecombe -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 05.09.2014 12:56, Anton Aylward wrote:
On 09/05/2014 05:43 AM, mararm wrote:
Any ideas to how I can get this working again?
When xdm/kdm won't start for me, the reason usually lies in Xorg.
Well, my problem at the moment is more that it won't _stop_ ;-)
Check your logs in /var/log/s for both {xk}dm.{log,error} and the Xorg.0.log
OK. I do not have xdm.log, but kdm.log is there. Xorg.0.log seems to be clean of errors. Sadly, neither Xorg nor kdm logs are timestamped. kdm.log shows Fatal server error: Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. but this seems to be an older message. The now existing /tmp/.X0-lock is dated today, 11:10, which is roughly the time I tried to restart kdm. Then there is failed to open /usr/lib64/dri/updates/i965_dri.so: /usr/lib64/dri/updates/i965_dri.so: cannot open shared object file: No such file or directory but according to the readme-file in /usr/lib64/dri/updates that shoul not be a problem. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 09/05/2014 09:14 AM, mararm wrote:
OK. I do not have xdm.log, but kdm.log is there. Xorg.0.log seems to be clean of errors. Sadly, neither Xorg nor kdm logs are timestamped.
Yes there are. Run 'ls'. The nature of these is that they start and if they fail as you've shown, the timestamp on the file is what counts. -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 05.09.2014 16:01, Anton Aylward wrote:
On 09/05/2014 09:14 AM, mararm wrote:
OK. I do not have xdm.log, but kdm.log is there. Xorg.0.log seems to be clean of errors. Sadly, neither Xorg nor kdm logs are timestamped.
Yes there are. Run 'ls'.
The nature of these is that they start and if they fail as you've shown, the timestamp on the file is what counts.
I do not quite understand. As for kdm.log: $ ls -al /var/log/kdm.log -rw-r--r-- 1 root root 522986 Sep 5 11:20 /var/log/kdm.log The timestamp is of the time I tried to restart xdm. But I am sure the file does contain stuff from earlier runs of kdm, the entries repeat over and over. But I cannot tell whether a message is from the last/current run or days old. Xorg.0.log is smaller $ l /var/log/Xorg.0.log-rw-r--r-- 1 root root 39747 Sep 5 11:20 /var/log/Xorg.0.log of the same time, and does not show (EE) lines. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 09/05/2014 10:17 AM, mararm wrote:
On 05.09.2014 16:01, Anton Aylward wrote:
On 09/05/2014 09:14 AM, mararm wrote:
OK. I do not have xdm.log, but kdm.log is there. Xorg.0.log seems to be clean of errors. Sadly, neither Xorg nor kdm logs are timestamped.
Yes there are. Run 'ls'.
The nature of these is that they start and if they fail as you've shown, the timestamp on the file is what counts.
I do not quite understand. As for kdm.log:
$ ls -al /var/log/kdm.log -rw-r--r-- 1 root root 522986 Sep 5 11:20 /var/log/kdm.log
The timestamp is of the time I tried to restart xdm. But I am sure the file does contain stuff from earlier runs of kdm, the entries repeat over and over. But I cannot tell whether a message is from the last/current run or days old.
Sad to say it doens't iterate as Xorg.N.log does its always the last entry ... and as you say, inadequaely timestamped. So you need to delete it and try again when there are problems.
Xorg.0.log is smaller $ l /var/log/Xorg.0.log-rw-r--r-- 1 root root 39747 Sep 5 11:20 /var/log/Xorg.0.log
And if there are more errors that becomes Xorg.1.log and you get a new Xorg.0.log, and so on.
of the same time, and does not show (EE) lines.
For me, it's usually an Xorg error that cascades back to kdm, but you seem to have an honest to goodness kdm error. It _may_ be that there is a server running. Under some weird conditions that I've never been able to replicate consistently enought to describe as a bug report I've had the server fail to connect to my screen and still show no errors. Reboot time! As your kdm.log says:
Fatal server error: Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again.
perhaps it is ONLY the lock file that is gumming things up. Xorg is very archaic in many ways and this is one aspect. Run 'ps' and see what's running. If you are 100% sure from that run that there is no 'X' of any form running, then delete the lock file and try again. Or reboot. And yes I hate 'reboot' as a cure. So Microsoftian. -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Friday 05 September 2014 15:07:58 Anton Aylward wrote:
So you need to delete it and try again when there are problems.
Maybe it's worth the effort to tweak logrotate to create a new kdm.log every on boot.
As your kdm.log says:
Fatal server error: Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock and start again.
perhaps it is ONLY the lock file that is gumming things up. Xorg is very archaic in many ways and this is one aspect.
OK. I hope I will remember to log in to a text console on my return to office and check for a the lock file. The machine is down and out now for the weekend.
Run 'ps' and see what's running. If you are 100% sure from that run that there is no 'X' of any form running, then delete the lock file and try again.
Or reboot.
Will have to, see above.
And yes I hate 'reboot' as a cure. So Microsoftian.
I could not agree more. -- More are taken in by hope than by cunning. -- Vauvenargues -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 09/05/2014 09:14 AM, mararm wrote:
OK. I do not have xdm.log, but kdm.log is there.
Do you have xdm.errors ? -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
* Anton Aylward <opensuse@antonaylward.com> [09-05-14 10:03]:
On 09/05/2014 09:14 AM, mararm wrote:
OK. I do not have xdm.log, but kdm.log is there.
Do you have xdm.errors ?
he removed xdm :^( -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 05.09.2014 16:04, Patrick Shanahan wrote:
* Anton Aylward <opensuse@antonaylward.com> [09-05-14 10:03]:
On 09/05/2014 09:14 AM, mararm wrote:
OK. I do not have xdm.log, but kdm.log is there.
Do you have xdm.errors ?
he removed xdm :^(
Did I say so? Well, I did not: $ rpm -qi xdm Name : xdm Version : 1.1.10 Release : 14.10.1 Architecture: x86_64 Install Date: Di 02 Jul 2013 17:41:58 CEST Group : System/X11/Utilities Size : 462217 License : MIT Signature : RSA/SHA256, Di 02 Jul 2013 11:19:06 CEST, Key ID b88b2fd43dbdc284 Source RPM : xdm-1.1.10-14.10.1.src.rpm Build Date : Mo 24 Jun 2013 14:27:01 CEST Build Host : build32 Relocations : (not relocatable) Packager : http://bugs.opensuse.org Vendor : openSUSE URL : http://xorg.freedesktop.org/ Summary : X Display Manager Description : Xdm manages a collection of X displays, which may be on the local host or remote servers. Distribution: openSUSE 12.3 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 09/05/2014 10:10 AM, mararm wrote:
On 05.09.2014 16:04, Patrick Shanahan wrote:
* Anton Aylward <opensuse@antonaylward.com> [09-05-14 10:03]:
On 09/05/2014 09:14 AM, mararm wrote:
OK. I do not have xdm.log, but kdm.log is there.
Do you have xdm.errors ?
he removed xdm :^(
Did I say so? Well, I did not:
As it turns out, I never restart 'kdm.service', it always 'xdm.service'. I don't know why this is, but that's the way it is on my 13.1 And yes, what I manipulate under systemetttings _says_ its kdm, but ... so what. -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 05.09.2014 16:02, Anton Aylward wrote:
On 09/05/2014 09:14 AM, mararm wrote:
OK. I do not have xdm.log, but kdm.log is there.
Do you have xdm.errors ?
No: ls: cannot access /var/log/x* -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 09/05/2014 09:14 AM, mararm wrote:
kdm.log shows
Fatal server error: Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again.
but this seems to be an older message. The now existing /tmp/.X0-lock is dated today, 11:10, which is roughly the time I tried to restart kdm.
*sigh* Then remove it and try again. If it gets recreated you know it pertains to your current situation. And pay attention to the time on the files! -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 05.09.2014 16:06, Anton Aylward wrote:
On 09/05/2014 09:14 AM, mararm wrote:
kdm.log shows
Fatal server error: Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again.
but this seems to be an older message. The now existing /tmp/.X0-lock is dated today, 11:10, which is roughly the time I tried to restart kdm.
*sigh*
Then remove it and try again.
The 'try again' part is what bothers me. kdm won't stop. And rebooting is no option for the moment (this is @work). -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Fri, 5 Sep 2014 16:19, mararm <mararm@...> wrote:
On 05.09.2014 16:06, Anton Aylward wrote:
On 09/05/2014 09:14 AM, mararm wrote:
kdm.log shows
Fatal server error: Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again.
but this seems to be an older message. The now existing /tmp/.X0-lock is dated today, 11:10, which is roughly the time I tried to restart kdm.
*sigh*
Then remove it and try again.
The 'try again' part is what bothers me. kdm won't stop. And rebooting is no option for the moment (this is @work).
To give a little light into the display-manager workings: Start: the DM (here kdm) starts, pulls up and starts X11, waits for login. Login: DM validates the creditales (Account / pw), starts the user session (here possible start_kde) Logout: The user session ends, DM takes over X11 displays login again. Stop: Only possible during wait for login, kills X11, ends DM (here kdm) Take-out from running session, using "ps auxf", here lxdm / xfce : USER PID TTY STAT TIME COMMAND root 1969 ? Ss 0:00 /usr/bin/lxdm -d root 1971 tty7 Ss+ 1124:46 \_ /usr/bin/X :0 vt07 -nolisten tcp mf 2213 ? Ss 0:00 \_ /bin/sh /etc/xdg/xfce4/xinitrc -- /etc/X11/xinit/xserverrc So without logging out of X11, a restart of the DM (here kdm) is not possible. Should kdm stand on the login screen, the is usually a option to restart kdm / X11 (can be disabled via config). Otherwise with kdm at the login screen, try to kill kdm from a tty as root with "killall kdm", either kdm respawns (with the fresh binary) or try to use "systemctl stop xdm.service", wait for error messages, and "systemctl start xdm.service" afterwards if no errors are shown. - Yamaban. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 05.09.2014 17:21, Yamaban wrote:
To give a little light into the display-manager workings:
Start: the DM (here kdm) starts, pulls up and starts X11, waits for login. Login: DM validates the creditales (Account / pw), starts the user session (here possible start_kde) Logout: The user session ends, DM takes over X11 displays login again. Stop: Only possible during wait for login, kills X11, ends DM (here kdm)
Yes.
Take-out from running session, using "ps auxf", here lxdm / xfce : USER PID TTY STAT TIME COMMAND root 1969 ? Ss 0:00 /usr/bin/lxdm -d root 1971 tty7 Ss+ 1124:46 \_ /usr/bin/X :0 vt07 -nolisten tcp mf 2213 ? Ss 0:00 \_ /bin/sh /etc/xdg/xfce4/xinitrc -- /etc/X11/xinit/xserverrc
$ ps auxf | grep kdm USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1441 0.0 0.0 28752 2036 ? Ss Sep03 0:00 /usr/bin/kdm root 22099 3.0 1.4 292340 118460 tty7 Ss+ 11:10 11:53 \_ /usr/bin/Xorg -br :0 vt7 -nolisten tcp -seat seat0 -auth /var/lib/kdm/AuthFiles/A:0-ypVKia So, X is from this morning, but kdm is two days old.
So without logging out of X11, a restart of the DM (here kdm) is not possible.
Yes.
Should kdm stand on the login screen, the is usually a option to restart kdm / X11 (can be disabled via config).
Otherwise with kdm at the login screen, try to kill kdm from a tty as root with "killall kdm", either kdm respawns (with the fresh binary) or try to use "systemctl stop xdm.service", wait for error messages, and "systemctl start xdm.service" afterwards if no errors are shown.
What I did this morning was 1) installing latest updates (via apper-plasmoid) 2) log out of KDE 3) log in to console 4) sudo zypper ps, which listed kdm 5) sudo systemctl restart xdm.service Normally, this would restart kdm and take me to the graphical login on vt 7. It did not. It did not report anything either. 'zypper ps' still listed kdm I saw this behaviour already two or three days ago. Then, I did the 'kill <pidofkdm>', which pretty much "ruined" my system and I had to reboot. I have no idea, why that happend, but I did not want to do it again. On the graphical console I could get the screen to flash by pressing Ctrl-Alt-Backspace twice, which in my opinion should restart X. But the kdm process stayed. Normally, stopping kdm should disable the graphical login. It did not. Then I tried stopping it. $ sudo systemclt stop xdm.service did not report errors. kdm stays alive. $ systemctl status xdm.service xdm.service - LSB: X Display Manager Loaded: loaded (/etc/init.d/xdm) Active: inactive (dead) since Fri, 2014-09-05 11:10:24 CEST; 6h ago Process: 22085 ExecStop=/etc/init.d/xdm stop (code=exited, status=0/SUCCESS) Process: 21836 ExecStart=/etc/init.d/xdm start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/xdm.service ├ 1441 /usr/bin/kdm └ 22099 /usr/bin/Xorg -br :0 vt7 -nolisten tcp -seat seat0... I did not understand this. Hence, I logged back in KDE and wrote my first mail of this thread. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Friday 05 September 2014 17:50, mararm wrote:
What I did this morning was
1) installing latest updates (via apper-plasmoid) 2) log out of KDE 3) log in to console 4) sudo zypper ps, which listed kdm 5) sudo systemctl restart xdm.service
Is KDM at this moment still working ? If yes, then why would restart it ? Just because zypper ps shows that the kdm package was updated through zypper ? KDM is one of the KDE Applications that wasn't touched for quite a long time and the packages were just rebuild due to the 4.14 update which caused dependent packages to be rebuild. So if KDM is still working, then I wouldn't bother too much in trying to get it restarted. With a bigger KDE update, it is more important that you logoff and login again to at least ensure you are using the latest libraries, etc. For KDM (which is in LTS mode), this doesn't really apply. As you indicated you are still on openSUSE 12.3, which had one of the first systemd implementations and I know that quite some improvements were made with 13.1. As far as I remember the display-manager service was also introduce only with 13.1 Regards Raymond -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 05.09.2014 18:35, Raymond Wooninck wrote:
On Friday 05 September 2014 17:50, mararm wrote:
What I did this morning was
1) installing latest updates (via apper-plasmoid) 2) log out of KDE 3) log in to console 4) sudo zypper ps, which listed kdm 5) sudo systemctl restart xdm.service
Is KDM at this moment still working ?
At least I have a running KDE session. I do not think this would be possible without kdm (or a different display manager) working, so I would say "yes" to that.
If yes, then why would restart it ? Just because zypper ps shows that the kdm package was updated through zypper ?
That was the initial reason, yes. Now I also want to find out what is happening here and why it is not working anymore. The systemclt restart xdm.service used to work flawlessly since recently.
As you indicated you are still on openSUSE 12.3, which had one of the first systemd implementations and I know that quite some improvements were made with 13.1. As far as I remember the display-manager service was also introduce only with 13.1
I see. And I just noticed that 12.3 will reach end of life in 10 days. So maybe it is time to upgrade. Regards mararm -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 2014-09-05 19:22 (GMT+0200) mararm composed:
I just noticed that 12.3 will reach end of life in 10 days. So maybe it is time to upgrade.
If you were reading that from https://en.opensuse.org/Lifetime you might have noticed an inconsistency in it. In addition to "Sep 15th 2014", it also says "2 months after release of 13.2". The 13.2 development period was extended, and so it isn't due for release until November. Thus, 12.3 should remain in support at least into next year. If not, there would be only one supported release from 15 September until actual 13.2 release. -- "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-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Friday 05 September 2014 14:30:30 Felix Miata wrote:
I just noticed that 12.3 will reach end of life in 10 days. So maybe it is time to upgrade.
If you were reading that from https://en.opensuse.org/Lifetime
exactly
you might have noticed an inconsistency in it.
I did indeed.
In addition to "Sep 15th 2014", it also says "2 months after release of 13.2". The 13.2 development period was extended, and so it isn't due for release until November. Thus, 12.3 should remain in support at least into next year. If not, there would be only one supported release from 15 September until actual 13.2 release.
Do you, or does anyone else, know of an "official" statement about this issue? Will the support of 12.3 be prolongued till 13.2 sees light of day? Regards mararm -- I love being married. It's so great to find that one special person you want to annoy for the rest of your life. -- Rita Rudner -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 2014-09-05 19:23 (GMT-0400) mararm composed:
https://en.opensuse.org/Lifetime ... Do you, or does anyone else, know of an "official" statement about this issue?
I think the first line under that page's title may be as official as it gets. -- "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-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 09/05/2014 11:50 AM, mararm wrote:
Stop:
Only possible during wait for login, kills X11, ends DM (here kdm) Yes.
NO! Systemctl can stop the session even when you are logged in. I know this becuase I'v done it on many occassions. -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 09/05/2014 11:50 AM, mararm wrote:
What I did this morning was
1) installing latest updates (via apper-plasmoid)
Well OK, but I normally use 'zypper up' at the console so I can see what's going on.
2) log out of KDE
Generally I don't do this. Why? Many updates don't affect KDE. No need to log out in that case.
3) log in to console 4) sudo zypper ps, which listed kdm
Right!
5) sudo systemctl restart xdm.service
Normally, this would restart kdm and take me to the graphical login on vt 7.
Ah, yes; sounds like, generally, you've done what I do, so here it gets ... /interesting/ I wish you had started with this detailed description! Details are good. If you'd told us this in your first post quite a few of the previous posts, mine included, would never have happened :-)
It did not. It did not report anything either.
'zypper ps' still listed kdm
/_Very_ interesting/
I saw this behaviour already two or three days ago. Then, I did the 'kill <pidofkdm>', which pretty much "ruined" my system and I had to reboot. I have no idea, why that happend, but I did not want to do it again.
Now wanting to reboot is good. It means you haven't been brainwashed into being a Microserf :-)
On the graphical console I could get the screen to flash by pressing Ctrl-Alt-Backspace twice, which in my opinion should restart X. But the kdm process stayed.
Even more ... /interesting/
Normally, stopping kdm should disable the graphical login. It did not. Then I tried stopping it.
$ sudo systemclt stop xdm.service did not report errors. kdm stays alive.
$ systemctl status xdm.service xdm.service - LSB: X Display Manager Loaded: loaded (/etc/init.d/xdm) Active: inactive (dead) since Fri, 2014-09-05 11:10:24 CEST; 6h ago Process: 22085 ExecStop=/etc/init.d/xdm stop (code=exited, status=0/SUCCESS) Process: 21836 ExecStart=/etc/init.d/xdm start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/xdm.service ├ 1441 /usr/bin/kdm └ 22099 /usr/bin/Xorg -br :0 vt7 -nolisten tcp -seat seat0...
I did not understand this. Hence, I logged back in KDE and wrote my first mail of this thread.
"Curiouser and curiouser..." -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- Perhaps I am a dinosaur, but if I saw the word "hacker" used positively on a resume, I would have trouble continuing. Hacking means using "quick and dirty" means to achieve an objective without concern for "collateral damage" and is totally opposite to my philosophy of "first, do no harm". -- Pagett Peterson, Wednesday, January 18, 2006 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 09/05/2014 11:21 AM, Yamaban wrote:
On Fri, 5 Sep 2014 16:19, mararm <mararm@...> wrote:
On 05.09.2014 16:06, Anton Aylward wrote:
On 09/05/2014 09:14 AM, mararm wrote:
kdm.log shows
Fatal server error: Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again.
but this seems to be an older message. The now existing /tmp/.X0-lock is dated today, 11:10, which is roughly the time I tried to restart kdm.
*sigh*
Then remove it and try again.
The 'try again' part is what bothers me. kdm won't stop. And rebooting is no option for the moment (this is @work).
To give a little light into the display-manager workings:
Start: the DM (here kdm) starts, pulls up and starts X11, waits for login. Login: DM validates the creditales (Account / pw), starts the user session (here possible start_kde) Logout: The user session ends, DM takes over X11 displays login again. Stop: Only possible during wait for login, kills X11, ends DM (here kdm)
Take-out from running session, using "ps auxf", here lxdm / xfce : USER PID TTY STAT TIME COMMAND root 1969 ? Ss 0:00 /usr/bin/lxdm -d root 1971 tty7 Ss+ 1124:46 \_ /usr/bin/X :0 vt07 -nolisten tcp mf 2213 ? Ss 0:00 \_ /bin/sh /etc/xdg/xfce4/xinitrc -- /etc/X11/xinit/xserverrc
So without logging out of X11, a restart of the DM (here kdm) is not possible.
While there is a similar structure for running KDE root 1365 0.0 0.0 24616 444 ? Ss Sep04 0:00 /usr/bin/kdm root 1380 1.8 4.5 397256 180056 tty7 Ss+ Sep04 29:15 \_ /usr/bin/Xorg -br :0 vt7 -nolisten tcp -auth /var/lib/kdm/AuthFiles/A:0-ztNU1b root 1389 0.0 0.0 76100 836 ? S Sep04 0:00 \_ -:0 anton 1475 0.0 0.0 13092 388 ? Ss Sep04 0:00 \_ /bin/sh /usr/bin/startkde anton 1671 0.0 0.0 17056 304 ? Ss Sep04 0:02 \_ /usr/bin/gpg-agent --sh --daemon --write-env-file /home/anton/.gnupg/agent.info /etc/X11/xinit/xinitrc anton 1785 0.0 0.0 4224 48 ? S Sep04 0:00 \_ kwrapper4 ksmserver I disagree about the need to log out of X11. Man times after a zypper update I've simply restarted 'xdm.service', which is how my DM is controller, even though it is named kdm. What happens is that the signal propagates down to shut down all the applications running under KDE, then KDE shuts down, certainly cleanly enough to allow the apps to be restarted, then X11 shuts down then kdm shuts down, and then restarts. How do I kow this? After the zypper update I run 'zypper ps' and it tells me that many running binaries need to be restared AMONG THEM KDM. After doing the 'systemctl restart xdm.xervice' I run 'zypper ps' again and it gives me an all clear. so the 'new' version of kdm is running. Not need to use 'kill' or 'killall'. Systemctl manages things quite well thank you. Of course you may have unit files miconfigured to the dependency tree isn't aware of things, but that's a different problem. -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ - -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
participants (7)
-
Anton Aylward -
Felix Miata -
mararm -
Patrick Shanahan -
Raymond Wooninck -
Sean Watson -
Yamaban