trinity-users@lists.pearsoncomputing.net

Message: previous - next
Month: August 2013

Re: [trinity-users] kdeinit!

From: Felix Miata <mrmazda@...>
Date: Sun, 04 Aug 2013 20:07:31 -0400
On 2013-08-05 00:11 (GMT+0200) Jan LitwiƱski composed:

> I've just installed TDE and J have one problem. When I start TDE

"Start" exactly how?

> session error pops up: Could not start kdeinit. Check your
> installation. I click ok and system is starts normal. I run commend:

> janek@linux-fay4:~> ps -e|grep kdeinit
>   4707 ?        00:00:00 kdeinit
> kdeinit is running.

> System openSUSE 12.3 and TDE

> Any ideas?

It wouldn't surprise me if your problem and mine with 12.2 are related, even 
though I didn't "just" install TDE. It's been a problem since its 
installation at the end of last November (3.5.13.1). I don't recall any 
trouble as long as I boot straight to runlevel 5. The trouble comes with 
trying to exit runlevel 5 other than by rebooting or shutting down.

ISTR that openSUSE has some uniqueness WRT how it initiates any WM. If I'm 
remembering right, there may well be something in the Trinity build and/or 
configuration process that needs tweaking to match and have TDM start and 
exit properly, probably same as KDE3 has grown to need. Not only that, there 
would also be differences depending on whether init is systemd or sysvinit, 
which in both 12.2 and 12.3 allowed a choice (sysvint is gone in 13.1). 
You're probably using the systemd default, while in 12.2 I'm using sysvinit.

I do a lot of stopping and restarting of of Xorg. Normally I boot to runlevel 
3 (which under systemd technically does not exist), then start X via startx 
most often, bypassing the complication of the login manager. When using the 
login manager, I've been in the habit for many years of using the shortcut 
'init 3' to stop and 'init 5' to start. Stopping this way with TDM (or KDM3, 
which I have installed on several systems) is not working. This is what happens:

# init 3
INIT: Switching to runlevel: 3
Boot logging started on /dev/tty3(/dev/console) at <timestamp>
Master Resource Control: previous runlevel: 5, switching to runlevel:	3
Master Resource Control: Running /etc/init.d/before.local	done
killproc: Usage:
	killproc [-v] [-q] [-L] [-g|-G] [-N] [--p pid_file] [-i ingnore_file] \
		[-c root] [-t<sec>] [-SIG] /full/path/to/executable
	killproc -l
								done
Master Resource Control: Running /etc/init.d/after.local	done
Master Resource Control: runlevel 3 has been	reached
#

Excerpts from tail of 'ps -A':
   PID TTY          TIME CMD
  1717 ?        00:00:00 kdm
  1734 tty1     00:00:00 mingetty
  1735 tty2     00:00:00 mingetty
  1736 ?        00:00:00 login
  1737 tty4     00:00:00 mingetty
  1738 tty5     00:00:00 mingetty
  1739 tty6     00:00:00 mingetty
  1757 tty7     00:00:00 X
  1766 ?        00:00:00 kdm
  1767 ?        00:00:01 kdm_greet
  1771 ?        00:00:00 tsak
  1775 ?        00:00:00 krootimage
  1778 ?        00:00:00 kwin
  1781 ?        00:00:00 dcopserver
  1792 ?        00:00:00 console-kit-dae
  1858 ?        00:00:00 polkitd
  1869 tty3     00:00:00 bash
  1946 tty3     00:00:00 ps

Before systemd showed up on openSUSE, init3 always terminated everything 
X-related. X, kwin and those kdm lines should all be gone once "runlevel 3" 
is reached, and maybe some others.

KDE3 has the same (or very similar) problem, which I reported against 12.2 
last fall but has gotten zero traction:
https://bugzilla.novell.com/show_bug.cgi?id=783862
-- 
"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/