← Back to team overview

torios-dev team mailing list archive

Re: 18Dec2016 - New testing ISO

 

On 12/19/2016 06:27 AM, Cinque Port Computers wrote:
>
> Hi Israel,
>
>
> New .iso install in VB:
>
>
> On the installed system I'm not seeing panel items for battery, eth0,
> or volume...these are visible on the Live session.
>
>
> Regards,
>
> JackT.
>
>
>
> ------------------------------------------------------------------------
> *From:* Torios-dev
> <torios-dev-bounces+jackdtrice=outlook.com@xxxxxxxxxxxxxxxxxxx> on
> behalf of Cinque Port Computers <jackdtrice@xxxxxxxxxxx>
> *Sent:* 19 December 2016 12:20
> *To:* Israel
> *Cc:* torios- dev
> *Subject:* Re: [Torios-dev] 18Dec2016 - New testing ISO
>  
>
> Hi Israel,
>
>
> New .iso installed in VB...
>
>
> Great news -- indeed now you did fix the disappearing desktop
> icons/shortcuts, well done.
>
>
> Can you explain briefly what the problem was that eluded us for so long?
>
>
> Thanks,
>
> JackT.
>
Hi Jack.
This is complicated, as I do not know why things fail the way they do.
The culprit in both cases is
/usr/bin/nice-start
previous I just ran the program in
<StartupCommand>nice-start</StartupCommand>
this resulted in PCManFM not always working visibly
now I use it differently
<Include>nice-start --include</Include>
On my computer this is what that command produces:
<JWM>
  <StartupCommand>~/.config/jsm-mouse</StartupCommand>
  <StartupCommand>/usr/lib/at-spi2-core/at-spi-bus-launcher
--launch-immediately</StartupCommand>
 
<StartupCommand>/usr/lib/x86_64-linux-gnu/deja-dup/deja-dup-monitor</StartupCommand>
  <StartupCommand>/usr/bin/gnome-keyring-daemon --start
--components=pkcs11</StartupCommand>
  <StartupCommand>/usr/bin/gnome-keyring-daemon --start
--components=secrets</StartupCommand>
  <StartupCommand>/usr/bin/gnome-keyring-daemon --start
--components=ssh</StartupCommand>
  <StartupCommand>nm-applet</StartupCommand>
  <StartupCommand>xset s off -dpms</StartupCommand>
 
<StartupCommand>/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1</StartupCommand>
  <StartupCommand>start-pulseaudio-x11</StartupCommand>
  <StartupCommand>torios-battery</StartupCommand>
  <StartupCommand>torios-volume</StartupCommand>
  <StartupCommand>jwm -restart</StartupCommand>
  <StartupCommand>update-notifier</StartupCommand>
  <StartupCommand>xdg-user-dirs-gtk-update</StartupCommand>
  <StartupCommand>zeitgeist-datahub</StartupCommand>
</JWM>
These are the programs that running nice-start as a <StartupCommand>
will run.  You can check to see what is run in ToriOS by running
nice-start --include
from the terminal

The battery and volume and nm-applet all included.
So, why does this fail one way or the other sometimes, but not every time?

It could be a memory issue?  My laptop where I never have this issue has
plenty of memory.  The VM probably does not.  How much memory do you
have in your VM?  The other computers I use ToriOS on are older, but
have around 1Gig of memory and never have these issues.

So... nice-start is the problem, however it is also a solution.... 
nice-start runs all the programs in the XDG autostart directories.  So
if nm-applet is removed JWM wont try to run it, as it is only included
from the XDG autostart.  This way traditional DE specific guidelines on
the internet about creating a desktop file in ~/.config/autostart will
work in ToriOS.

This is why it is complicated and I have tried so many different things.
Here is the actual code that runs on or the other:

[[ -n "$useJWMRC" ]] && EXEC=$(quoteXML "$EXEC") && printf "%s\n" " 
<StartupCommand>${EXEC}</StartupCommand>" 2> /dev/null
     [[ -z "$useJWMRC" ]] && bash -c "$EXEC" & 2>> "$LOG" &

I used to have 'echo' instead of printf "%s\n" but echo was causing
errors, and this now avoids errors.
I have posted on the JWM bugs a few times concerning this, and have not
really gotten to the bottom of why it doesn't always work.  The current
form works much better but still there are issues.

Not sure what else to do... can you post your ~/.starttorios.log and
~/.jwm/jsm-logs/nice-start.log
These might give more of a clue....

-- 
Regards


Follow ups

References