Re: [kde] qdbus /ScreenSaver Lock fails
On Sun, Jan 5, 2014 at 8:55 AM, Kevin Krammer wrote: > On Sunday, 2014-01-05, 08:22:13, David L wrote: > > > > If I try to use the DBUS_SESSION_BUS_ADDRESS in the one file > > in ~/.dbus/session-bus, it doesn't work. The results I get are different > > in my local session and in that tmp file: > > > > echo $DBUS_SESSION_BUS_ADDRESS > > unix:abstract=/tmp/dbus-1i5RBi6cFV,guid=4a22a915e3c0a1082928620e52c238bf > > > > grep DBUS_SESSION_BUS_ADDRESS ~/.dbus/session-bus/* > > # If the DBUS_SESSION_BUS_ADDRESS environment variable is set, it will > > > DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-p7FI7sRDLO,guid=42d74b3a12b > > 87cd5e97149cd52c238bf > > Strange. If you look at that file's time stamp, is it approximately the > date/time when you started the session? > It looks like it's from the same time. I just exited and restarted and compared again: > date Sun Jan 5 19:34:42 PST 2014 > ls -l ~/.dbus/session-bus/583f7cbba6b4b3b7fd89fa0952c08115-0 -rw-r--r-- 1 dgl dgl 463 Jan 5 19:29 /home/dgl/.dbus/session-bus/583f7cbba6b4b3b7fd89fa0952c08115-0 > echo $DBUS_SESSION_BUS_ADDRESS unix:abstract=/tmp/dbus-IZwbZv9WUE,guid=32307fb949df48dcc91b6b6552ca2333 > grep ADDRESS ~/.dbus/session-bus/583f7cbba6b4b3b7fd89fa0952c08115-0 # If the DBUS_SESSION_BUS_ADDRESS environment variable is set, it will DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-VM7yvrW0Au,guid=3209f9250115954e2620e49752ca2333 Perhaps this inconsistency is why I have been having problems.? I'm up and running again with a startup script that saves the bus address variable. Thanks again. David ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] window snap ignores window border but open doesn't
Jerome Yuzyk posted on Sun, 05 Jan 2014 14:26:06 -0800 as excerpted: > I got annoyed with this pseudo-feature and turned off snapping for a > while, but that was more annoying too[.] So I looked into progress of > any bugs reported to see if it had been fixed but unfortunately I only > see that the developer who dropped this little turd of a change on a > very basic window-layout property spends more time justifying (thinly) > whatever rationale he had in doing it than considering any other > options. > > However, there is a KWin script that seems to work for me in making > things normal again so I can turn snapping back on: > > http://kde-look.org/content/show.php?content=160851 > > Note: I only use a single-monitor laptop and a decoration scheme with > square corners. Thank you. I'm headed to work ATM, but plan to look into that script, likely when I get home. I had thought something like that might work, but don't know enough about such scripts yet to know how to code it myself. This extra example, in addition to what kde already ships and perhaps others on kdelook, should help in that regard as well. =:^) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] window snap ignores window border but open doesn't
On Friday, November 22, 2013 05:20:34 AM Duncan wrote: > Wes Hardin posted on Thu, 21 Nov 2013 13:59:51 -0600 as excerpted: > > Don't let this make you think I like or agree with the change; I hate > > it. I fully support making it optional because some people do like it > > but for my work flow it is non-helpful at best and counterproductive in > > most instances. I don't even care if it's the default behavior, I just > > wish there was a way to turn it off. > > ++ > > I use kde because it's customizable. This smacks of gnome "there's only > one true way and it's our way" ideology. > > As I (believe I) said in the other thread, tho, one way to disable the > effect is to use window rules to hard-position things. I do that for > some windows, but it doesn't work well for windows like konsole where I > very often work with two side-by-side windows on my primary monitor, and > occasionally work with four windows, two on each of my main monitors (of > three, the third the same resolution but half the size, used for full- > time display of a near-full-monitor superkaramba theme). > > (Full screenshot of three full-hd monitors "stacked", 1920x3240, tho it > shows pan with the kde lists open and claws-mail with the LXer feeds > open, plus aurora/firefox in the background behind the semi-transparent > claws-mail window, not konsole. > > http://wstaw.org/m/2013/05/11/duncan-fullscreen.png ) I got annoyed with this pseudo-feature and turned off snapping for a while, but that was more annoying too, just like Windows' lack of window-snapping, so reminiscent of Win3.1. So I looked into progress of any bugs reported to see if it had been fixed but unfortunately I only see that the developer who dropped this little turd of a change on a very basic window-layout property spends more time justifying (thinly) whatever rationale he had in doing it than considering any other options. However, there is a KWin script that seems to work for me in making things normal again so I can turn snapping back on: http://kde-look.org/content/show.php?content=160851 Note: I only use a single-monitor laptop and a decoration scheme with square corners. ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] Why do you prefer KDE?
On Sunday 05 January 2014 02:14:51 PM Kevin Krammer wrote: > On Saturday, 2013-12-21, 18:45:13, Bruce Byfield wrote: > > As you may have heard, KDE recently topped the Linux Journal's Readers' > > Choice Awards. > > > > That got me thinking. Why do people prefer KDE? What advantages do you > > think it has over other desktop environments? > > > > Warning: If I get enough replies, I may use them in a blog entry for Linux > > Pro Magazine. > > Bruce has now published that article: > http://www.datamation.com/open-source/why-do-users-choose-kde.html > > > My thanks in advance for any replies. > > Indeed! > And thank you Bruce for combining them! :) > Thanks! I meant to mention the publication on the list. -- Bruce Byfield 604-421-7189 (on Pacific time) blog: https://brucebyfield.wordpress.com website: http://members.axion.net/~bbyfield/ ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] qdbus /ScreenSaver Lock fails
On Sunday, 2014-01-05, 08:22:13, David L wrote: > On Sun, Jan 5, 2014 at 7:53 AM, Kevin Krammer wrote: > > On Sunday, 2014-01-05, 07:16:51, David L wrote: > > > > Since you have confirmed in your other reply that it works if the D-Bus > > address is available to the script, do you get any error when you run > > qdbus in > > the SSH session and have just exported DISPLAY? > > My old script did not work from cron or ssh after upgrading Kubuntu and > Mint. It did work in a local session. So any output, error or otherwise, when you only set DISPLAY? > > Regarding your idea to write the address into a file, that actually > > already > > happens as well, see ~/.dbus/session-bus > > If I try to use the DBUS_SESSION_BUS_ADDRESS in the one file > in ~/.dbus/session-bus, it doesn't work. The results I get are different > in my local session and in that tmp file: > > echo $DBUS_SESSION_BUS_ADDRESS > unix:abstract=/tmp/dbus-1i5RBi6cFV,guid=4a22a915e3c0a1082928620e52c238bf > > grep DBUS_SESSION_BUS_ADDRESS ~/.dbus/session-bus/* > # If the DBUS_SESSION_BUS_ADDRESS environment variable is set, it will > DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-p7FI7sRDLO,guid=42d74b3a12b > 87cd5e97149cd52c238bf Strange. If you look at that file's time stamp, is it approximately the date/time when you started the session? > If I set the variable to the value in the file, my script stops working > even from the local session. Right, it seems to have come from an earlier/unrelated session. It would in all cases just be a workaround, dbus-launch should be able to find the XAtom with the address via DISPLAY. Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring signature.asc Description: This is a digitally signed message part. ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] qdbus /ScreenSaver Lock fails
On Sun, Jan 5, 2014 at 7:53 AM, Kevin Krammer wrote: > On Sunday, 2014-01-05, 07:16:51, David L wrote: > > Since you have confirmed in your other reply that it works if the D-Bus > address is available to the script, do you get any error when you run > qdbus in > the SSH session and have just exported DISPLAY? > My old script did not work from cron or ssh after upgrading Kubuntu and Mint. It did work in a local session. > > Regarding your idea to write the address into a file, that actually already > happens as well, see ~/.dbus/session-bus > If I try to use the DBUS_SESSION_BUS_ADDRESS in the one file in ~/.dbus/session-bus, it doesn't work. The results I get are different in my local session and in that tmp file: echo $DBUS_SESSION_BUS_ADDRESS unix:abstract=/tmp/dbus-1i5RBi6cFV,guid=4a22a915e3c0a1082928620e52c238bf grep DBUS_SESSION_BUS_ADDRESS ~/.dbus/session-bus/* # If the DBUS_SESSION_BUS_ADDRESS environment variable is set, it will DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-p7FI7sRDLO,guid=42d74b3a12b87cd5e97149cd52c238bf If I set the variable to the value in the file, my script stops working even from the local session. Thanks, David ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] qdbus /ScreenSaver Lock fails
On Sunday, 2014-01-05, 07:34:06, David L wrote: > Sorry if this wasn't an appropriate question for this list, but I thought > this was the way to lock the screensaver from the command line in KDE per > this (admittedly Ubuntu) answer: Don't worry, it was appropriate. See my explanation in the other reply :) Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring signature.asc Description: This is a digitally signed message part. ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] qdbus /ScreenSaver Lock fails
On Sunday, 2014-01-05, 07:16:51, David L wrote: > On Fri, Jan 3, 2014 at 10:28 PM, Duncan wrote: > > Seriously, a dbus call to org.FreeDesktop.ScreenSaver might happen to > > work on a kde desktop (or not, thus this thread), but it's not > > org.kde... , which should be a hint that perhaps either your distro lists/ > > forums or the freedesktop.org lists/forums might be more appropriate. > > (I'd try the distro first.) The service name or its prefix does not need to be org.kde in order to be relevant here. org.freedesktop prefixed service names usually refer to things that work across different desktops/worspace implementations. Whether the service in question is always the same (shared implementation) or vendor specific (shared interface/specification) is sometimes hard to tell. D-Bus viewers such as qdbusviewer, D-Feet or, on the commandline, qdbus usually enable us to see the difference. For example the relevant output of qdbus on my session is: :1.10 org.freedesktop.ScreenSaver org.kde.ksmserver org.kde.ksmserver-3932 org.kde.screensaver Meaning the D-Bus connection ":1.10" is also known as org.freedesktop.ScreenSaver, org.kde.ksmserver and so on. Since KDE applications that use D-Bus usually register their name-PID combination as one of those names automatically, we can identify the actual service implementor as KDE's session manager KSMServer. > Did that, no luck. And I thought qdbus was related to KDE, so I tried > here. qdbus is a tool shipped by Qt, a commandline tools to interact with D-Bus services. So it is not related to KDE but very likely present on a system that runs KDE Plasm workspace. > I guess a more appropriate question for here is how do I lock my KDE > desktop from a script run from cron? Since your script used to work and still works when run inside the KDE session then I guess the best way forward is to find out why it does not work anymore when run by cron. Since you have confirmed in your other reply that it works if the D-Bus address is available to the script, do you get any error when you run qdbus in the SSH session and have just exported DISPLAY? Regarding your idea to write the address into a file, that actually already happens as well, see ~/.dbus/session-bus Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring signature.asc Description: This is a digitally signed message part. ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] qdbus /ScreenSaver Lock fails
On Sat, Jan 4, 2014 at 4:17 AM, Kevin Krammer wrote: > > > David L wrote: > > > I just upgraded to Kubuntu 13.10 and a script that used to work for me > stopped > > > working. Specifically, I had a script that I ran from a cron job that > > > locked the screen. The script looks like this: > > > > > > #!/bin/bash > > > export DISPLAY=:0.0 > > > export PATH=/usr/lib/x86_64-linux-gnu/qt4/bin:$PATH > > > qdbus org.freedesktop.ScreenSaver /ScreenSaver Lock > > > > > > The same thing happened after upgrading from Mint 15 to Mint 16. > > > > > > Now I get this error when I use this previously working script from > ssh or > > > a cron job: > > > > > > Service 'org.freedesktop.ScreenSaver' does not exist. > > > > > > It still works from a local KDE session. > > > > > > > @David: just to see if it would work with the actual bus address being > available: > - in your main session, get the value of $DBUS_SESSION_BUS_ADDRESS > - in your ssh session, set that variable to that value and try qdbus again > > That worked. Thanks! So I guess if I run a startup script that copies that variable to a file and then read that file from my cron job, that should do it. I'll try it later and respond if it doesn't work. Sorry if this wasn't an appropriate question for this list, but I thought this was the way to lock the screensaver from the command line in KDE per this (admittedly Ubuntu) answer: http://askubuntu.com/questions/61339/what-is-the-screen-locking-mechanism-under-kde So, if there is a better way to lock/unlock the screen in KDE, let me know what it is. I use this to unlock: qdbus | perl -ne 'qx/kquitapp $1/ if /(kscreenlocker_greet-\d+)/' Thanks again, David ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] qdbus /ScreenSaver Lock fails
On Fri, Jan 3, 2014 at 10:28 PM, Duncan wrote: > David L posted on Fri, 03 Jan 2014 17:22:48 -0800 as excerpted: > > > I just upgraded to 13.10 and a script that used to work for me stopped > > working. > > 13.10? You're on a kde list, and kde is only up to 4.12.x. Where'd the > 13.10 come from (opensuse or kubuntu, maybe?, they use year-based > versions, which that appears to be), and shouldn't you be posting to that > list if you're using that version number? > Sorry, I copied the text from an unanswered Kubuntu post and forgot to add what distro I meant. > > Seriously, a dbus call to org.FreeDesktop.ScreenSaver might happen to > work on a kde desktop (or not, thus this thread), but it's not > org.kde... , which should be a hint that perhaps either your distro lists/ > forums or the freedesktop.org lists/forums might be more appropriate. > (I'd try the distro first.) > > Did that, no luck. And I thought qdbus was related to KDE, so I tried here. I guess a more appropriate question for here is how do I lock my KDE desktop from a script run from cron? Thanks, David ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] Why do you prefer KDE?
On 22/12/13 04:45, Bruce Byfield wrote: As you may have heard, KDE recently topped the Linux Journal's Readers' Choice Awards. That got me thinking. Why do people prefer KDE? What advantages do you think it has over other desktop environments? My reasons: * It looks nicer to me. I mean visually. I like eye candy. * I am very used to KDE's GUI conventions, from button order and keyboard shortcuts, to configuration dialog semantics, context menus and the "start menu." * Many of my favorite applications are written with Qt. As a result, they look and behave better in KDE (though in recent years this isn't much of a problem with Gtk-based desktops.) * The Dolphin file manager. I like it very, very much. * Extremely configurable keyboard shortcuts, like for suspending desktop compositing. Last time I checked, I couldn't see how to do that in Gnome. ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] Why do you prefer KDE?
On Saturday, 2013-12-21, 18:45:13, Bruce Byfield wrote: > As you may have heard, KDE recently topped the Linux Journal's Readers' > Choice Awards. > > That got me thinking. Why do people prefer KDE? What advantages do you think > it has over other desktop environments? > > Warning: If I get enough replies, I may use them in a blog entry for Linux > Pro Magazine. Bruce has now published that article: http://www.datamation.com/open-source/why-do-users-choose-kde.html > My thanks in advance for any replies. Indeed! And thank you Bruce for combining them! :) Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring signature.asc Description: This is a digitally signed message part. ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
