Tiny Core Linux
Tiny Core Extensions => TCE Bugs => Topic started by: xor on March 20, 2020, 06:31:20 AM
-
TCL 11 "windowmaker" not working !!! :(
TCL 10.x "windowmaker" working ! :)
windowmaker.tcz
-
What happens when you enter the command “wmaker”?
-
What happens when you enter the command “wmaker”?
Core-10.1.iso
Core-11.0.iso
tc@box:~$ tce-load -wi xf86-video-ati wbar aterm windowmaker Xorg-7.7-3d alsa pavucontrol
tc@box:~$ startx
tc@box:~$ sudo /usr/local/etc/init.d/dbus start
TCL 11.x "windowmaker" not working !!! :(
TCL 10.x "windowmaker" working !
-
This is what I meant:
$ wmaker
wmaker: error while loading shared libraries: libgif.so.6: cannot open shared object file: No such file or directory
-
it should be OK now
-
This is what I meant: $ wmaker
wmaker: error while loading shared libraries: libgif.so.6: cannot open shared object file: No such file or directory
what should I do !?
-
it should be OK now
I assumed you were updating.
I tried to rebuild.
the existing problem continues! :(
-
sorry - dep file adjusted
-
it should be OK now
! :(
tc@box:~$ wmaker
wmaker: error while loading shared libraries: libtiff.so.5: cannot open shared object file: No such file or directory
tc@box:~$ tce-load -wi Xorg-7.7-3d firmware-radeon xf86-video-ati aterm wbar windowmaker
Xorg-7.7-3d is already installed!
firmware-radeon is already installed!
xf86-video-ati is already installed!
aterm is already installed!
wbar is already installed!
windowmaker is already installed!
tc@box:~$ startx
tc@box:~$ wmaker
wmaker: error while loading shared libraries: libtiff.so.5: cannot open shared object file: No such file or directory
tc@box:~$
-
Are you using tc-11.x x86 or x86_64?
-
Are you using tc-11.x x86 or x86_64?
I'm trying it in 32-bit version right now! it gives an error !
I haven't tried the 64-bit version! can you also check !?
-
libtiff added to dep file
-
libtiff added to dep file
it corrects when you type STARTX again!
what is the permanent solution to this problem !?
(http://forum.tinycorelinux.net/index.php?action=dlattach;topic=23639.0;attach=5279)
[attachment deleted by admin]
-
download the new dep file - either:
http://tinycorelinux.net/11.x/x86_64/tcz/windowmaker.tcz.dep
or
http://tinycorelinux.net/11.x/x86/tcz/windowmaker.tcz.dep
..and replace your existing dep file.
-
Hi Juanito
I see 2 odd things here:
... it corrects when you type STARTX again! ...
The pstree command in the left terminal appears to show wmaker starting a second instance of wmaker.
The wbar at the bottom of the screen appears to be overlaying a second set of icons, possibly supplied by wmaker. Maybe he
shouldn't be loading wbar.
-
Hi Juanito
I see 2 odd things here:
... it corrects when you type STARTX again! ...
The pstree command in the left terminal appears to show wmaker starting a second instance of wmaker.
The wbar at the bottom of the screen appears to be overlaying a second set of icons, possibly supplied by wmaker. Maybe he
shouldn't be loading wbar.
tc@box:~$ pstree
init-+-Xorg
|-sh
|-udevd---2*[udevd]
|-udhcpc
|-wbar-+-aterm---sh---pstree
| `-aterm---sh
`-wmaker---wmaker
tc@box:~$ startx
tc@box:~$ pstree
init-+-Xorg
|-aterm---sh---pstree
|-aterm---sh
|-sh
|-udevd---2*[udevd]
|-udhcpc
|-wbar
`-wmaker---wmaker
tc@box:~$
(http://forum.tinycorelinux.net/index.php?action=dlattach;topic=23639.0;attach=5280)
tc@box:~$ startx
(http://forum.tinycorelinux.net/index.php?action=dlattach;topic=23639.0;attach=5281)
-
the current problem continues!
I created and run the iso file.
after the desktop comes
like the last pictures I sent
Typing "startx" fixes the desktop WBAR.!
but I'm tired of doing this manually every time I open it.
tc@box:~$ pstree
init-+-Xorg
|-sh
|-udevd---2*[udevd]
|-udhcpc
|-wbar-+-aterm---sh---pstree
| `-aterm---sh
`-wmaker---wmaker
tc@box:~$ startx
tc@box:~$ pstree
init-+-Xorg
|-aterm---sh---pstree
|-aterm---sh
|-sh
|-udevd---2*[udevd]
|-udhcpc
|-wbar
`-wmaker---wmaker
-
Hi xor
When the system comes up, run these commands:
ps aux > before.txt
startx
ps aux > after.txt
Then attach the files before.txt and after.txt to your next post.
-
Hi xor
When the system comes up, run these commands:
ps aux > before.txt
startx
ps aux > after.txt
Then attach the files before.txt and after.txt to your next post.
-
Hi xor
Are you starting wbar in /opt/bootlocal.sh, /opt/bootsync.sh, or some other script?
-
Hi xor
Are you starting wbar in /opt/bootlocal.sh, /opt/bootsync.sh, or some other script?
no
-
Hi xor
When the system comes up, run these command:
sudo killall wbar
Does the background then get fixed?
-
Hi xor
When the system comes up, run these command:
sudo killall wbar
Does the background then get fixed?
I tried the command! WBAR is gone! :(
I don't want Wbar to go!
Re-type the startx command
it turns out this way
i like this shape!
(http://forum.tinycorelinux.net/index.php?action=dlattach;topic=23639.0;attach=5299)
but when it usually opens, I see this as follows
once in a while ! I do not want to write startx command at continuous boot
(http://forum.tinycorelinux.net/index.php?action=dlattach;topic=23639.0;attach=5280)
-
Hi xor
When the system comes up, run these command:
sudo killall wbar
Does the background then get fixed?
I thought my request was reasonable. Run a command, and tell me if it fixes the background.
I tried the command! WBAR is gone! :(
I don't want Wbar to go! ...
Instead of answering my question, you start yelling that the WBAR is gone.
I told you to kill the Wbar to see if it's blocking something else from happening.
Do you really believe I'm trying to deprive you of your Wbar?
Maybe you could try answering the question I ask.
Then attach the following files to your next post:
/op/bootsync.sh
/op/bootlocal.sh
~/.profile
~/.xsession
-
.profile
# ~/.profile: Executed by Bourne-compatible login SHells.
#
# Path to personal scripts and executables (~/.local/bin).
[ -d "$HOME/.local/bin" ] || mkdir -p "$HOME/.local/bin"
export PATH=$HOME/.local/bin:$PATH
ONDEMAND=/etc/sysconfig/tcedir/ondemand
[ -d "$ONDEMAND" ] && export PATH=$PATH:"$ONDEMAND"
# Environment variables and prompt for Ash SHell
# or Bash. Default is a classic prompt.
#
PS1='\u@\h:\w\$ '
PAGER='less -EM'
MANPAGER='less -isR'
EDITOR=vi
export PS1 PAGER FILEMGR EDITOR MANPAGER
export BACKUP=1
[ "`id -un`" = "`cat /etc/sysconfig/tcuser`" ] && echo "$BACKUP" | sudo tee /etc/sysconfig/backup >/dev/null 2>&1
export FLWM_TITLEBAR_COLOR="58:7D:AA"
if [ -f "$HOME/.ashrc" ]; then
export ENV="$HOME/.ashrc"
. "$HOME/.ashrc"
fi
TERMTYPE=`/usr/bin/tty`
[ ${TERMTYPE:5:3} == "tty" ] && (
[ ! -f /etc/sysconfig/Xserver ] ||
[ -f /etc/sysconfig/text ] ||
[ -e /tmp/.X11-unix/X0 ] ||
startx
)
.xsession
/usr/local/bin/Xorg -nolisten tcp &
export XPID=$!
waitforX || ! echo failed in waitforX || exit
"$DESKTOP" 2>/tmp/wm_errors &
export WM_PID=$!
[ -x $HOME/.setbackground ] && $HOME/.setbackground
[ -x $HOME/.mouse_config ] && $HOME/.mouse_config &
[ $(which "$ICONS".sh) ] && ${ICONS}.sh &
[ -d "/usr/local/etc/X.d" ] && find "/usr/local/etc/X.d" -type f -o -type l | while read F; do . "$F"; done
[ -d "$HOME/.X.d" ] && find "$HOME/.X.d" -type f | while read F; do . "$F"; done
bootsync.sh
#!/bin/sh
# put other system startup commands here, the boot process will wait until they complete.
# Use bootlocal.sh for system startup commands that can run in the background
# and therefore not slow down the boot process.
/usr/bin/sethostname box
/opt/bootlocal.sh &
bootlocal.sh
#!/bin/sh
# put other system startup commands here
(http://forum.tinycorelinux.net/index.php?action=dlattach;topic=23639.0;attach=5300)
Hi xor
When the system comes up, run these command:
sudo killall wbar
Does the background then get fixed?
I thought my request was reasonable. Run a command, and tell me if it fixes the background.
I tried the command! WBAR is gone! :(
I don't want Wbar to go! ...
Instead of answering my question, you start yelling that the WBAR is gone.
I told you to kill the Wbar to see if it's blocking something else from happening.
Do you really believe I'm trying to deprive you of your Wbar?
Maybe you could try answering the question I ask.
Then attach the following files to your next post:
/op/bootsync.sh
/op/bootlocal.sh
~/.profile
~/.xsession
-
Hi xor
See if this helps.
Change your .xsession file
From this:
/usr/local/bin/Xorg -nolisten tcp &
export XPID=$!
waitforX || ! echo failed in waitforX || exit
"$DESKTOP" 2>/tmp/wm_errors &
export WM_PID=$!
[ -x $HOME/.setbackground ] && $HOME/.setbackground
[ -x $HOME/.mouse_config ] && $HOME/.mouse_config &
[ $(which "$ICONS".sh) ] && ${ICONS}.sh &
[ -d "/usr/local/etc/X.d" ] && find "/usr/local/etc/X.d" -type f -o -type l | while read F; do . "$F"; done
[ -d "$HOME/.X.d" ] && find "$HOME/.X.d" -type f | while read F; do . "$F"; done
To this:
/usr/local/bin/Xorg -nolisten tcp &
export XPID=$!
waitforX || ! echo failed in waitforX || exit
"$DESKTOP" 2>/tmp/wm_errors &
while true
do
sleep 1
busybox ps | grep -q "wmaker \--for-real" || continue
sleep 1
break
done
export WM_PID=$!
[ -x $HOME/.setbackground ] && $HOME/.setbackground
[ -x $HOME/.mouse_config ] && $HOME/.mouse_config &
[ $(which "$ICONS".sh) ] && ${ICONS}.sh &
[ -d "/usr/local/etc/X.d" ] && find "/usr/local/etc/X.d" -type f -o -type l | while read F; do . "$F"; done
[ -d "$HOME/.X.d" ] && find "$HOME/.X.d" -type f | while read F; do . "$F"; done
-
:)
1. as;
First of all, I am trying to configure TCL on usb as a linux distribution running on iso.
I use ezremaster.
.xsession file
ezremaster.iso> boot> core.gz> core> home> tc> .xsession
I placed it!
wbar now works seamlessly with wmaker :)
If you add the patch you recommend to wbar.tcz, you will ensure that wmaker users do not have any problems while using wbar.
Thank you for your help
Hi xor
See if this helps.
Change your .xsession file
From this:
/usr/local/bin/Xorg -nolisten tcp &
export XPID=$!
waitforX || ! echo failed in waitforX || exit
"$DESKTOP" 2>/tmp/wm_errors &
export WM_PID=$!
[ -x $HOME/.setbackground ] && $HOME/.setbackground
[ -x $HOME/.mouse_config ] && $HOME/.mouse_config &
[ $(which "$ICONS".sh) ] && ${ICONS}.sh &
[ -d "/usr/local/etc/X.d" ] && find "/usr/local/etc/X.d" -type f -o -type l | while read F; do . "$F"; done
[ -d "$HOME/.X.d" ] && find "$HOME/.X.d" -type f | while read F; do . "$F"; done
To this:
/usr/local/bin/Xorg -nolisten tcp &
export XPID=$!
waitforX || ! echo failed in waitforX || exit
"$DESKTOP" 2>/tmp/wm_errors &
while true
do
sleep 1
busybox ps | grep -q "wmaker \--for-real" || continue
sleep 1
break
done
export WM_PID=$!
[ -x $HOME/.setbackground ] && $HOME/.setbackground
[ -x $HOME/.mouse_config ] && $HOME/.mouse_config &
[ $(which "$ICONS".sh) ] && ${ICONS}.sh &
[ -d "/usr/local/etc/X.d" ] && find "/usr/local/etc/X.d" -type f -o -type l | while read F; do . "$F"; done
[ -d "$HOME/.X.d" ] && find "$HOME/.X.d" -type f | while read F; do . "$F"; done
-
Hi xor
... If you add the patch you recommend to wbar.tcz, you will ensure that wmaker users do not have any problems while using wbar. ...
The purpose of this change was to delay running .setbackground and ${ICONS}.sh (Wbar) until after wmaker has started running.
The background of the screen was not getting painted blue which suggests .setbackground was also being affected.
If this patch gets placed in wbar.tcz , you would probably still have a problem with .setbackground.
If this patch gets placed in wbar.tcz , it will break wbar.tcz for all the other window managers.
-
Hi xor
... If you add the patch you recommend to wbar.tcz, you will ensure that wmaker users do not have any problems while using wbar. ...
The purpose of this change was to delay running .setbackground and ${ICONS}.sh (Wbar) until after wmaker has started running.
The background of the screen was not getting painted blue which suggests .setbackground was also being affected.
If this patch gets placed in wbar.tcz , you would probably still have a problem with .setbackground.
If this patch gets placed in wbar.tcz , it will break wbar.tcz for all the other window managers.
As the 2nd option; Would it be if the patch file was added in "windowmaker.tcz"?
Or does it make sense to create my 3rd option "yama_wbar_for_wmaker.tcz" file?
-
Hi xor
It belongs right where it is to pause the .xsessions file execution until after wmaker has started running.
-
Hi xor
It belongs right where it is to pause the .xsessions file execution until after wmaker has started running.
Wmaker is an app that works very well on resource usage and full screen VLC player,
but the conflict with wbar provides the patch solution you suggested.
To overcome the problem of using wbar with wmaker
I think a standard and fixed patch file should be created.
somehow I'm not the only TCL user. :)