LXDE Displays Unwanted wbar

[SamK]

After installing Openbox/LXDE on TC, wbar is displayed each time startx has run.  A right-click on wbar removes it without any problem.  Is there a fix posted anywhere for this?

[curaga]

The bootcode "noicons"

[SamK]

Simple when you know how.  Thanks

[SamK]

When using Openbox and LXDE, is there a command that can be added to /opt/bootlocal.sh which performs the same function as the bootcode "noicons"?

[Kingdomcome]

If using the "noicons" bootcode is not desired, you can edit ~/.xsession and either comment out or remove the line

Code:

[ "$ICONS" == "wbar" ] && /usr/bin/wbar.sh

[SamK]

If using the "noicons" bootcode is not desired, you can edit ~/.xsession and either comment out or remove the line

Code:

[ "$ICONS" == "wbar" ] && /usr/bin/wbar.sh

Thanks for the useful pointer.

If I understand correctly, the use of the bootcode "noicons" prevents the creation of a variable "ICONS" which is then used in ~/.xsession.  Is it possible to boot without using the bootcode "noicons" and unset the variable "ICONS" with a command issued from /opt/bootlocal.sh?

I am not against commenting out the appropriate line in ~/.xsession but I try to keep the number of manually edited files to a minimum.  I have created other entries in /opt/bootlocal.sh and would also like to use it for this purpose if possible.

If this is a workable idea, how would the command be constructed to unset "ICONS"?
 

[bmarkus]

You can also kill WBAR process in the script, either in bootlocal.sh or ad to LXDE startup. However it is better not to start WBAR than start and kill. But works.

[SamK]

You can also kill WBAR process in the script, either in bootlocal.sh or ad to LXDE startup. However it is better not to start WBAR than start and kill. But works.

I am uncertain how to do this.  In a root console "kill wbar" generates 'bad pid wbar'.

I would still also like to learn how to unset $ICONS.

Edit:
I have tried adding

Code:

unset ICONS

to bootlocal.sh without success.
 

[danielibarnes]

Is it possible to boot without using the bootcode "noicons" and unset the variable "ICONS" with a command issued from /opt/bootlocal.sh?

No, because bootlocal.sh is a child script. Any changes to environment variables within it do not affect the init process.

If you do not want wbar to start, there is a hack (I verified it works on 2.8.1):
1) Open a root terminal.
2) rm -f /usr/share/wbar/dot.wbar
3) ln -s foo /usr/share/wbar/dot.wbar
4) Add usr/share/wbar/dot.wbar to /opt/.filetool.lst and make a backup

The key to this is that dot.wbar is now a symbolic link to a file which does not exist. This link in the backup will be restored on bootup before the following code is executed:

if [ -n "$NOICONS" ] || [ ! -f /usr/share/wbar/dot.wbar ]; then
   unset ICONS
fi

This will unset ICONS in the appropriate place and prevent wbar from starting.

Alternatively, you can create a "no-wbar" extension to remove the dot.wbar file:
1) Load squashfs-tools extension using Appbrowser.
2) Open a root terminal.
3) mkdir -p /tmp/no-wbar/usr/local/tce.installed/
4) echo rm -f /usr/share/wbar/dot.wbar > /tmp/no-wbar/usr/local/tce.installed/no-wbar
5) chmod +x /tmp/no-wbar/usr/local/tce.installed/no-wbar
5) mksquashfs /tmp/no-wbar /tmp/no-wbar.tcz -b 4096

Then, for TC 2.7 and earlier:
6) Copy no-wbar.tcz to your tce directory

Or for 2.8 and later:
6) Copy no-wbar.tcz to your tce/optional directory
7) Add "no-wbar.tcz" to tce/onboot.lst

There may be users like you which for one reason or another cannot use the noicons boot parameter,  so I will submit this extension to Jason for consideration. It's a bit of a hack, though, so no guarantees on acceptance.

However it is better not to start WBAR than start and kill.

True, but if you wish to try this, here is what you can add to bootlocal.sh:

while ! pidof wbar &>/dev/null; do sleep 1; done; killall wbar

[curaga]

I have to wonder why there are so many ways to get rid of wbar, when the simplest ones are the bootcode, or using MC where wbar is not included at all.

[bmarkus]

I have to wonder why there are so many ways to get rid of wbar, when the simplest ones are the bootcode, or using MC where wbar is not included at all.

Maybe the cleanest way is to build on MC. You are right.

[danielibarnes]

That is the beauty of Tinycore. There are so many ways (each with pros and cons) to do even a simple thing:

1) Use "noicons" boot parameter.
2) Build on microcore base instead of tinycore.
3) Create backup file to remove dot.wbar
4) Create extension to remove dot.wbar
5) Kill wbar in bootlocal.sh
6) Remove wbar startup in ~/.xsession

[SamK]

Is it possible to boot without using the bootcode "noicons" and unset the variable "ICONS" with a command issued from /opt/bootlocal.sh?

No, because bootlocal.sh is a child script. Any changes to environment variables within it do not affect the init process.

This has helped greatly; it is easy to understand .

In my view the rest of your reply is a model answer.  To provide a range of possible actions in a clear and concise manner is an example for us all.  Many thanks.

Although probably the least elegant solution I will probably adopt the killing of wbar from bootlocal.sh as it represents the closest answer to my requirements.  I have tested it and it fulfills what I requested.  Hopefully your extension will be accepted and I will adopt it at that time.
 

[SamK]

I have to wonder why there are so many ways to get rid of wbar, when the simplest ones are the bootcode, or using MC where wbar is not included at all.

I am reasonably new to TC and still exploring it.  I have not yet looked at MC.  Is there a guide to building an Openbox/LXDE environment using MC?
 

[Arslan S.]

I have to wonder why there are so many ways to get rid of wbar, when the simplest ones are the bootcode, or using MC where wbar is not included at all.

I am reasonably new to TC and still exploring it.  I have not yet looked at MC.  Is there a guide to building an Openbox/LXDE environment using MC?
 

http://wiki.tinycorelinux.com/tiki-index.php