Tiny Core Base > Release Candidate Testing
tinycore & microcore v2.0rc4.
roberts:
Thanks for feedback. Yes. That is an oops concerning wallpaper.
I forgot to update wallpaper again. With .desktop being depreciated breaks wallpaper.
I will be sure to have it fixed in 2.0 final. For temporary work around make a .desktop file in home directory with a single line of:
wm: jwm
Or other window manager that supports ..._setbackground interface.
meo:
Hi again Robert!
Thanks a lot for your quick response. I kind of like to have a nice wallpaper when I'm working on the pc. So thanks again and keep up your most appreciated work!
Have fun all you TC-fans out there,
meo
roberts:
I will post a bug I found this morning.
This only can happen if you are using the new shortcut method of storing your backup, mydata.tgz, inside your tce directory.
When doing so, the 'norestore' option is ignored. So, if you occasionally, use norestore and you have moved your backup to be located inside your tce directory. Be advised.
I have this fixed for 2.0 final.
mcewanw:
Using tc2rc2.4 with no mydata.tgz (i.e. clean)
I think this is a bug, but I thought I'd seek clarification before posting it as such:
There seems to be an extra "sh" process left behind after starting up any application (if exec was being used the application should overwrite the originating sh call surely?)
Here is my ps output after starting up a number of aterm's, firefox and emelfm2
Note all the sh -c processes still running for firefox and emelfm2 (and a separate sh process along with each aterm):
--- Code: --- 6748 tc /usr/bin/aterm
6749 tc sh
6760 tc /usr/bin/aterm
6761 tc sh
6778 tc sh -c /usr/local/firefox-official/firefox
6779 tc /bin/sh /usr/local/firefox-official/firefox
6782 tc /bin/sh /usr/local/firefox-official/run-mozilla.sh /usr/local/fi
6787 tc /usr/local/firefox-official/firefox-bin
6798 tc /usr/lib/gconf2/gconfd-2 13
6820 tc sh -c /usr/local/bin/emelfm2
6821 tc /usr/local/bin/emelfm2
6824 tc /usr/bin/aterm
6825 tc sh
6836 tc ps
--- End code ---
roberts:
There is some history as far as the aterm call from .jwmrc goes:
Currently aterm is called with the -e /bin/sh option (extra shell).
Originally TC, which uses busybox ash shell, had no .ashrc.
Users wanted to re-source .profile for any changes made after login, so -e /bin/sh was added.
Now after several updates to busybox and the addition of .ashrc (TC v1.1) calling solely aterm should source .ashrc so new items in .ashrc are available.
Subtle point, but perhaps now again another change in aterm's call in the JWM menu is needed.
Since RCs are about field testing, may I sugest that since .jwmrc is under your control, i.e., in your backup by default, remove in the three calls to aterm the -e /bin/sh and verify that .ashrc will be re-read for an updated environment in the new aterm, and finally post your results.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version