Re: [kde] qdbus /ScreenSaver Lock fails

2014-01-06 Thread Kevin Krammer
On Sunday, 2014-01-05, 19:39:12, David L wrote:
 On Sun, Jan 5, 2014 at 8:55 AM, Kevin Krammer kram...@kde.org 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=42d74b3a1
  2b 
   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=3209f925011
 5954e2620e49752ca2333
 
 
 
 Perhaps this inconsistency is why I have been having problems.?

Yes, that is quite possible.
If you look into the session bus file, it also contains a PID. Do you have a 
process with that PID?
If you check the process list, do you have more than one dbus-daemon running?

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

2014-01-06 Thread David L
On Mon, Jan 6, 2014 at 2:39 AM, Kevin Krammer wrote:

 On Sunday, 2014-01-05, 19:39:12, David L wrote:
 
  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=3209f925011
  5954e2620e49752ca2333
 
 
 
  Perhaps this inconsistency is why I have been having problems.?

 Yes, that is quite possible.
 If you look into the session bus file, it also contains a PID. Do you have
 a
 process with that PID?
 If you check the process list, do you have more than one dbus-daemon
 running?


Yes and yes:
mdm   1580  0.0  0.0  30380   964 ?Ss   Jan05   0:00
//bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
dgl   1671  0.0  0.0  30380   488 ?Ss   Jan05   0:00
//bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
dgl   1685  0.0  0.0  31580  1932 ?Ss   Jan05   0:00
//bin/dbus-daemon --fork --print-pid 6 --print-address 9 --session

1671 is the pid in the .dbus/session-bus/* file.

Regards,

  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.