Ist try in Live mode

ostrolek

First impressions;
1) conky stays stiff on top, and won't allow the fully opened window to overlap it,
2) there is no system tray,
3) tint2, if killed won't come back
Not complaining, just trying to learn FB and Vsido

PackRat

You should have a system tray (tint2) in the upper right corner. The strut policy of that tint2 panel prevents the window from maximizing over the panel; the conky resides in the gap.
I am tired of talk that comes to nothing.
-- Chief Joseph

...the sun, the darkness, the winds are all listening to what we have to say.
-- Geronimo

ostrolek

Quote from: PackRat on October 21, 2015, 01:15:15 PM
You should have a system tray (tint2) in the upper right corner. The strut policy of that tint2 panel prevents the window from maximizing over the panel; the conky resides in the gap.
System tray wasn't there. I'd check about tint2 on top right corner. What about the tint2 on the bottom? Are there 2 tint2 panels?

PackRat

#3
Yes, two tint2 panels.

You can check out the ~/.fluxbox/startup of the live session or /etc/skel/.fluxbox/startup file (similar to openbox autostart) to see what is run at fluxbox startup.

How did you configure your network, ceni?

I just tried the newest live cd and had the system tray - I used wicd for network so it was visible. I don't think either panel is set to autohide.

Try another app with a systray icon - like xchat - to see if it shows.

The vsido-exit script is broken on the live session I was using; could you logout/shutdown ok?
I am tired of talk that comes to nothing.
-- Chief Joseph

...the sun, the darkness, the winds are all listening to what we have to say.
-- Geronimo

ostrolek

Thanks pal.
Never thought of looking in /etc/skel/.fluxbox/startup Still new at FB. Lot to learn.
Yes, I tried Ceni.
The Exit didn't work. I posted a solution in another thread here, http://vsido.org/index.php?topic=1067.msg12163#msg12163
Also, you can see lot of solutions on session-logout here too, http://crunchbang.org/forums/viewtopic.php?pid=438291#p438291

Some time would go by, until I catch up with Fluxbox.

Snap

#5
Quote from: ostrolek on October 21, 2015, 06:01:29 PM
Also, you can see lot of solutions on session-logout here too, http://crunchbang.org/forums/viewtopic.php?pid=438291#p438291

I like this one

http://crunchbang.org/forums/viewtopic.php?pid=438308#p438308

Adapted for Fluxbox

[submenu] (Exit)
      [exit] (Logout)
      [exec] (Suspend) {systemctl suspend}
      [exec] (Reboot) {systemctl reboot}
      [exec] (Shutdown) {systemctl poweroff}
[end]


One of the beauties of FB is that it uses plain text for the configs instead of xml. Much cleaner and human readable.

VastOne

Quote from: Snap on October 22, 2015, 06:41:38 AM

I like this one

[submenu] (Exit)
      [exit] (Logout)
      [exec] (Suspend) {systemctl suspend}
      [exec] (Reboot) {systemctl reboot}
      [exec] (Shutdown) {systemctl poweroff}
[end]


One of the beauties of FB is that it uses plain text for the configs instead of xml. Much cleaner and human readable.

I can adapt that as the new vsido-exit in the next ISO release... after some testing..

Strangely enough I am not seeing any logout or exit issues...
VSIDO      VSIDO Change Blog    

    I dev VSIDO

VastOne

The logout fails from the LiveCD because it is using the live system demand for sysvinit.. That will not work with the systemd logout/reboot controls

On a full install where systemd is the default, everything works as it should... And is the reason why I am not seeing these failures (except in a liveCD situation)
VSIDO      VSIDO Change Blog    

    I dev VSIDO

ostrolek

For the reboot and poweroff, you don't need to write systemctl in front of them, as the executables are in /sbin and linked to systemctl..

Snap

Yes, in my particular systems they are

    [submenu] (Exit)
        [exit] (Logout)
        [exec] (Reboot) {reboot}
        [exec] (Shutdown) {shutdown}
    [end]