Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Mon 20 Aug 2018, 07:02
All times are UTC - 4
 Forum index » Advanced Topics » Cutting edge
[FIXED but UNSOLVED] Problem with LXDE / run-as-spot / D-Bus
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 1 [6 Posts]  
Author Message
peebee


Joined: 21 Sep 2008
Posts: 3429
Location: Worcestershire, UK

PostPosted: Sun 28 Jan 2018, 11:54    Post subject:  [FIXED but UNSOLVED] Problem with LXDE / run-as-spot / D-Bus
Subject description: but not with JWM
 

FIX below

Help needed!!

A challenge for somebody clever to investigate and solve - please!

Concerns a difference in behaviour in an LXDE/Openbox scenario compared to a JWM scenario.

Base system can be either LxPupSc or LxPupArtful - both behave similarly. (LxPupXenial and LxPup-16.07.1-s likewise)

Do a pristine frugal install and boot - when system is up and running (under LXDE/Openbox) open a terminal and type:
Code:
run-as-spot light

Note the error messages -
Quote:
GConf Error or Warning: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

and that the Default Browser configuration answers are not saved between invocations

Now switch to JWM using Menu -> Setup -> Switch LXDE <> JWM....

Repeat the "run-as-spot light" test and note the absence of GConf/D-Bus messages in the terminal and that the configuration answers are now stored and remembered correctly.

So the question needing an answer is "How is the system started differently in the 2 cases such that the D-Bus message bus works correctly in run-as-spot mode under JWM but fails under LXDE/Openbox?"

I'm flummoxed and need some help! Here's hoping!
Thanks
peebee

_________________
LxPup = Puppy + LXDE

Last edited by peebee on Mon 05 Feb 2018, 12:23; edited 1 time in total
Back to top
View user's profile Send private message Visit poster's website 
musher0


Joined: 04 Jan 2009
Posts: 12580
Location: Gatineau (Qc), Canada

PostPosted: Sun 28 Jan 2018, 16:50    Post subject:  

Hi peebee.

The Light browser runs under both WMs, yes? Then... cheat!!! Wink

Make a secure copy of the config (aka profile) you got when loading Light from jwm.
The Light browser and all mozilla browsers have console parameters to force
configuration (aka profile) X or Y to be used. Use that. (Pls see screen cap.)

Then always run Light from a wrapper with
Code:
run-as-spot light -P so-and-so 2>/dev/null
That will prevent any error messages from being displayed in the console.

One sometimes gets error messages when using an application (such as the non-
jwm WM) that was not compiled for the Pup. Could that be the case?

As well, they are probably "warnings" rather than real error messages. If they were
actual errors, the app would simply not run.

That type of verbosity exists only on Ubuntu builds. You can check, it is
documented in Ubuntu forums. Ubuntu users have complained about it, but Ubuntu
is staying put, it will not change its policy about this.

My build of the xenialPup gave me many such headaches before I figured it out.

Just a few thoughts. IHTH. TWYL.
Light-browser-parms.jpg
 Description   You may want to try the -P or --profile parameters.
 Filesize   145.26 KB
 Viewed   297 Time(s)

Light-browser-parms.jpg


_________________
musher0
~~~~~~~~~~
Siempre será canción nueva... (V. Jara, Manifiesto)
Back to top
View user's profile Send private message 
musher0


Joined: 04 Jan 2009
Posts: 12580
Location: Gatineau (Qc), Canada

PostPosted: Sun 28 Jan 2018, 20:59    Post subject:  

Hello again peebee.

I tested the above theory empirically on LxPupArtful-17.11+4. This is my report:
Quote:
Under jwm (called with xwin jwm; normal jwm panel and bar displayed):
# run-as-spot light
(light:19132): GLib-GIO-WARNING **: Failed to execute child process
“update-desktop-database” (No such file or directory)

###########
Under openbox (called with xwin openbox; no panel or bar displayed):

# run-as-spot light
(No errors)

###########
Under lxde (called with xwin startlxde; normal lxde panel displayed):
# run-as-spot light

(light:28853): GConf-WARNING **: Client failed to connect to the D-BUS
daemon: Did not receive a reply. Possible causes include: the remote
application did not send a reply, the message bus security policy
blocked the reply, the reply timeout expired, or the network connection
was broken. GConf Error: No D-BUS daemon running
(Three times!)

###########
running geany to create this text file:
# geany &
[1] 29687 # Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.UDisks2VolumeMonitor:
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited:
Process org.gtk.vfs.UDisks2VolumeMonitor exited with status 127
(g-dbus-error-quark, 25)

Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.AfcVolumeMonitor:
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
org.gtk.vfs.AfcVolumeMonitor exited with status 127 (g-dbus-error-quark,
25)

###########
Under lxde (called with xwin startlxde; normal lxde panel displayed):
# run-as-spot light 2>/dev/null
(no errors)

###########
Under lxde (called with xwin startlxde; normal lxde panel displayed):
# run-as-spot light -P /root/.light/light/j5mun7hn.default 2>/dev/null
(no errors. The profiles mini-window is displayed and asks for a choice, however.)
I also sent you a PM on a related matter.

IHTH. TWYL, hopefully.

_________________
musher0
~~~~~~~~~~
Siempre será canción nueva... (V. Jara, Manifiesto)
Back to top
View user's profile Send private message 
peebee


Joined: 21 Sep 2008
Posts: 3429
Location: Worcestershire, UK

PostPosted: Mon 29 Jan 2018, 06:46    Post subject:  

Hi @musher0

Many thanks for your testing which has given me some ideas to try myself .... however I don't want to "cheat" or to hide error messages - I want to understand what aspect of LXDE/Openbox is causing the different behaviour compared to JWM.....given that the code base is identical....

_________________
LxPup = Puppy + LXDE
Back to top
View user's profile Send private message Visit poster's website 
musher0


Joined: 04 Jan 2009
Posts: 12580
Location: Gatineau (Qc), Canada

PostPosted: Mon 29 Jan 2018, 10:07    Post subject:  

HI peebee.

Come to think of it. it might just be the way the lxde launcher and the jwm launcher
launches the app.

It would be worth checking with a "neutral" launcher. From different WM's but with
this same "neutral" launcher. And we look at what happens. From urxvt or this other
little app called "runner". Not from the lxde terminal because it is part of lxde.

It would be interesting to see what shows up in the xerrs.log file when light -- or
geany -- is run from the jwm menu and then from the lxde menu? And we compare.
Are errors or warnings logged? When we do it this way and not that way?

~~~~~~~~~~~

However, if I have any advice to give on this subject, it is: do not waste your time.
What I mean is: "it's a Ubuntu 'attitude', we cannot fight it." We can only "cheat it".

By all the accounts that I read on this subject, Ubuntu does a lot of this kind of
babble, whereas Debian doesn't. But you are not believing me, boo-hoo-hoo. Sad Wink
This Ubuntu "feature" is documented, all can search and read those articles and
forum posts.

Hey, Ubuntu wants to play with My nerves, to rise MY anxiety level by making ME
believe those warnings are errors ?

MY revenge is to coldly manipulate THEIR output and send it to the land of lost
bytes -- where it should have gone in the first place. I have absolutely no qualms
about doing this.

BFN.

_________________
musher0
~~~~~~~~~~
Siempre será canción nueva... (V. Jara, Manifiesto)
Back to top
View user's profile Send private message 
peebee


Joined: 21 Sep 2008
Posts: 3429
Location: Worcestershire, UK

PostPosted: Mon 05 Feb 2018, 12:21    Post subject: Fixed - but not solved.....  

I've still no idea why this problem occurs - but I do now have a fix....

The key is symbol DBUS_SESSION_BUS_ADDRESS which is null under JWM but has a value under LXDE.....

Therefore the fix for LXDE is to patch both /usr/sbin/run-as-spot at line 35 and /usr/sbin/setup-spot at line 22 to:
Code:
DBUS_SESSION_BUS_ADDRESS="" ; exec su spot -s /bin/sh -c "\"$APP\" $ARGS"


I will submit a pull request to woof-ce.
Cheers
peebee

_________________
LxPup = Puppy + LXDE
Back to top
View user's profile Send private message Visit poster's website 
Display posts from previous:   Sort by:   
Page 1 of 1 [6 Posts]  
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Cutting edge
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0542s ][ Queries: 15 (0.0140s) ][ GZIP on ]