On 27/06/2011 14:15, Mag. Dr. Nikolaus Klepp wrote:

could you post your /var/log/Xorg.0.log and /etc/X11/xorg.conf ?

I don't have /etc/X11/xorg.conf (it the way X should be used nowadays) and /var/log/Xorg.0.log is very very long, are you looking for a specific part of this log? Can you explain a little more?

I think the answer might be around dcop but I can't understand where to find some doc for its options, etc.

Nicolas

Am Montag, 27. Juni 2011 schrieb Nicolas Bercher:

...

Hi,

Is there a way to properly close a trinity session from tty? I need it sometimes when my computers become weird, etc.

Nicolas

---

To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting

On 28/06/2011 15:27, David Hare wrote:

I use </etc/init.d/kdm-trinity stop> and </etc/init.d/kdm-trinity start>

OK, but I think this doesn't trigger the session saving stuff and is more like ctrl-alt-backspace to me.

Nicolas.

Hi Nicolas,

& save my current kde session?

I cannot guarantee that, therefore try $>kill 15 ... first. If this does not stop ked, use $>kill 9 ... What David suggested will certainly also help, but saving your session???

"dcop ksmserver default logout"

followed by three parameters, the parameters mean:

First parameter: confirm Obey the user's confirmation setting: -1 Don't confirm, shutdown without asking: 0 Always confirm, ask even if the user turned it off: 1

Second parameter: type Select previous action or the default if it's the first time: -1 Only log out: 0 Log out and reboot the machine: 1 Log out and halt the machine: 2

Third parameter: mode Select previous mode or the default if it's the first time: -1 Schedule a shutdown (halt or reboot) for the time all active sessions have exited: 0 Shut down, if no sessions are active. Otherwise do nothing: 1 Force shutdown. Kill any possibly active sessions: 2 Pop up a dialog asking the user what to do if sessions are still active: 3

Example: dcop ksmserver default logout 0 -1 -1

I can't test this on trinity but it worked in an old kde3 vm

I didn't, I found it on an old message board. I didn't keep the link but there wasn't any more info. I think the person that posted that looked at the source, but don't really know.

On Wed, Jun 29, 2011 at 10:43 AM, Nicolas Bercher nbercher@yahoo.fr wrote:

On 29/06/2011 17:33, Christopher J Kleinschmidt wrote:

...

"dcop ksmserver default logout"

followed by three parameters, the parameters mean:

First parameter:    confirm        Obey the user's confirmation setting:   -1         Don't confirm, shutdown without asking: 0        Always confirm, ask even if the user turned it off: 1

Second parameter:    type        Select previous action or the default if it's the first time: -1        Only log out: 0        Log out and reboot the machine: 1        Log out and halt the machine: 2

Third parameter:    mode        Select previous mode or the default if it's the first time: -1        Schedule a shutdown (halt or reboot) for the time all active sessions have exited: 0        Shut down, if no sessions are active. Otherwise do nothing: 1        Force shutdown. Kill any possibly active sessions: 2        Pop up a dialog asking the user what to do if sessions are still active: 3

Example: dcop ksmserver default logout 0 -1 -1

I can't test this on trinity but it worked in an old kde3 vm

Thank you for such a detailed answer!

Where did you got the doc for it?

Nicolas

---

To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting

I think that individual dcop services are started per user, (multiple per user is even possible). there should be a way to specify which dcop to send a signal on. There is, look at the man page for dcop, there is options like "--all-sessions" and "--all-users", also to be more selective as to where to send the signal there is "--user" and "--session". "--list-sessions" should help you find the combo you need. If you need help with that, I'll have some time later today to look closer.

On Fri, Jul 1, 2011 at 2:56 AM, Nicolas Bercher nbercher@yahoo.fr wrote:

On 29/06/2011 21:41, Christopher J Kleinschmidt wrote:

...

I didn't, I found it on an old message board. I didn't keep the link but there wasn't any more info.  I think the person that posted that looked at the source, but don't really know.

It seems to work only within the kdm session (e.g. from konsole or xterm).  From any tty (the way I want to close the session), it triggers an error:

"ERROR: Couldn't attach to DCOP server!".

I will read the docs to figure out how to connect to the server (I think via a kind of kdm session handler...?). The main goal is to be able to correctly shutdown a kdm session from anywhere (almost via ssh).

Nicolas

---

To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting

Glad I could help.

Have fun, Chris

On Sat, Jul 2, 2011 at 9:51 AM, Nicolas Bercher nbercher@yahoo.fr wrote:

On 01/07/2011 16:44, Christopher J Kleinschmidt wrote:

...

I think that individual dcop services are started per user, (multiple per user is even possible). there should be a way to specify which dcop to send a signal on.   There is, look at the man page for dcop, there is options like "--all-sessions" and "--all-users", also to be more selective as to where to send the signal there is "--user" and "--session".  "--list-sessions" should help you find the combo you need. If you need help with that, I'll have some time later today to look closer.

I've asked for the session id for my username and got two different ones:

.DCOPserver_localhost__0  .DCOPserver_localhost__1

I tried the first one from the tty1 and it did the job really well:

dcop --session .DCOPserver_localhost__1 --user <mylogin> \  ksmserver default logout 0 -1 -1

I went back on tty7 to see the kdm session closing (I've got a large number of kosonle, kpdf, etc. windows openend, so it actually takes a while to save & close the session).

Because having two dcop sessions worried me a little I rebooted to check if this could be a lost session handle, but after rebooting, I still have two sessions for my user.  I don't really understand if this is normal or not and what the second session is for.

Maybe next time I'll halt the machine, I'll try to logout using the second session handler, just to because I'm curious.

Thanks a lot for your help. I was on the way to read the dcop man page but you suggested the good options before I even type man ...

Nicolas

---

To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting