kdialog --passivepopup in 4.2 has a nice new effect where it pops out of the system tray rather than appearing in the middle of the screen. Definitely nicely done.

But...
It only works like that if it's been issued by the user I'm logged into KDE with. Any other user displays it in the old way. I don't think this is a configuration issue, as if I log into another userid, then its kdialogs display this way, while those from my normal user come out in the old way.

Other than using "su", is there a way to persuade other users' kdialogs to work in the new way?

You would need to gain access to their DBus session bus somehow in order to do this. No idea how though ( probably will be possible )

bcooksley wrote:You would need to gain access to their DBus session bus somehow in order to do this. No idea how though ( probably will be possible )

Ah, DBus. :-O
Thanks for the suggestion; I suspect I'll be sticking with su...

Hi to all.
I have this test script which till 4.1 worked very well.
It opened a popup with a very long timeout and at the end of the backend work (which is simulated with the sleep 20) it closed kdialog by killing it.
Now with kde 4.2 it doesn't work anymore because kdialog dies soon after it starts the popup so the process I would like to close is alredy died and I can't close the popup anymore.
Can you explain me how to obtain the same behavior with kde4.2 namely how to open a popup which remains opened till I command it to close?
Thank you,
Xwang

Code: Select all

#!/bin/bash
# prova.sh
# v0.0.1 - 20080814
# Xwang
# Released under GPL 2.0 and following (can you help me and tell if it is GPL3 compliant?)
kdialog --title "backupMozillaData.sh" --passivepopup "Backup in progress..." 600 &
PIDkdialog=$! # popup PID
echo $PIDkdialog
sleep 20 # this sleep simulate a script which has a variable execution time
kill -9 $PIDkdialog
echo "ciao"
exit