Tiny Core Linux
Tiny Core Base => TCB Q&A Forum => Topic started by: hobophil on August 09, 2018, 11:36:27 AM
-
The Tiny Core logo disappeared from my desktop wallpaper. I checked through the control panel, and the check box is checked to display it. Toggling on and off does not do anything. I tried changing the wallpaper color and so forth and it still does not come back. Also, I am not able to set a background image either. Images are saved in the correct folder and the filenames show up in the wallpaper control panel GUI, but when a file is selected, the wallpaper turns black. I tried large and small images. Changing the settings and rebooting does not fix it either.
Only possible cause I can think is, I installed the GTK3 extension "onboot." I think the problems started after that. I removed the extension but the problem is still present. I also installed a .ttf emoji font, but I don't think that caused it (?). Can't get emojis to display either, but that seems to be separate issue? I also installed Opera, not sure if that was before the issue or after.
Extensions I have installed are nano, VLC2, alsamixer, Chromium, usbmuxd, and their dependencies. Maybe some others too, but I am away from my computer right now so not sure.
Can anyone please advise on how to fix this? Thanks in advance.
-
Hi
until you get a better reply as I am on 64 bit please post the output of these commands
cat .xsession
cat .setbackground
What window manager are you on?
below is what 64 bit might see if they are using a certain graphics card and Xorg
the background output is the default
tc@box:~$ cat .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 "$HOME/.X.d" ] && find "$HOME/.X.d" -type f -print | while read F; do . "$F"; done
tc@box:~$ cat .setbackground
#!/bin/sh
hsetroot -add "#0E5CA8" -add "#87C6C9" -gradient 0 -center /usr/local/share/pixmaps/logo.png
tc@box:~$
-
Thanks aus9,
I am on the default window manager. Here is the output:
tc@box:~$ cat .xsession
Xvesa -br -screen 1024x768x32 -shadow -2button -mouse /dev/input/mice,5 -nolisten tcp -I >/dev/null 2>&1 &
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 "$HOME/.X.d" ] && find "$HOME/.X.d" -type f -print | while read F; do . "$F"; done
tc@box:~$ cat .setbackground
#!/bin/sh
hsetroot -solid "#439537"
[ $(which wbar.sh) ] && wbar.shtc@box:~$
-
This is what is actually in my .setbackground when opened with nano:
#!/bin/sh
hsetroot -solid "#439537" -center /usr/local/share/pixmaps/logo.png
[ $(which wbar.sh) ] && wbar.sh
Which is weird because it has the logo.png inside, but the cat output did not.
-
Hi hobophil
Which is weird because it has the logo.png inside, but the cat output did not.
I don't have an explanation for that, but you are missing a carriage return on the wbar line.
-
Well, I'm not sure what happened, but I'm about to reinstall it to start from scratch. I'll try turning persistence off to prevent me from messing things up again, until I get used to TC. Noob here. Thanks to those who replied.
-
After reformatting the hard drive and reinstalling Core Plus from CD, it happened again. This was after updating extensions, and then putting VLC2, Chromium, and usbmuxd Ondemand, and rebooting. (I may have run Xsetup before rebooting, but I don't think so) Then the logo wasnt there. After that, I reinstalled Core Plus without reformatting the hard drive, and the logo came back.
-
Hi hobophil
This is what is actually in my .setbackground when opened with nano:
#!/bin/sh
hsetroot -solid "#439537" -center /usr/local/share/pixmaps/logo.png
[ $(which wbar.sh) ] && wbar.sh
Which is weird because it has the logo.png inside, but the cat output did not.
Enter the following command and post the result:
hexdump -C .setbackground
-
Hi
I am not sure if the OP has not resolved this issue...but one suggestion springs to mind is maybe he had a file in his backup.....the mydata.tgz file and so it got restored over writing his attempted changes
FWIW under /opt is the file that you can use to add or remove files to be backed up called
.filetool.lst
and your actual backup is under /mnt/<some-partition>/tce/mydata.tgz
to view the current contents of mydata.tgz you can either use the control panel or mc running in a terminal.
maybe you could post the contents of your current backup file?
cat /opt/.filetool.lst
cat /opt/.xfiletool.lst
The top file is for files to be added to backup
the bottom file is for files to be excluded from backup
#############################
I have a fully persistent home so for me home is not listed in that file.
That means I have to do my own spring cleaning especially any web browser cache.
So if I was forecast a possible reason for the issue repeating it might be because you have
home named somewhere in your .filetool.lst without an exclusion named in
/opt/.xfiletool.lst of .setbackground ?
-
Hi hobophil
This is what is actually in my .setbackground when opened with nano:
#!/bin/sh
hsetroot -solid "#439537" -center /usr/local/share/pixmaps/logo.png
[ $(which wbar.sh) ] && wbar.sh
Which is weird because it has the logo.png inside, but the cat output did not.
Enter the following command and post the result:
hexdump -C .setbackground
00000000 23 21 2f 62 69 6e 2f 73 68 0a 68 73 65 74 72 6f |#!/bin/sh.hsetro|
00000010 6f 74 20 2d 66 75 6c 6c 20 2f 6f 70 74 2f 62 61 |ot -full /opt/ba|
00000020 63 6b 67 72 6f 75 6e 64 73 2f 48 61 73 68 69 6b |ckgrounds/Hashik|
00000030 61 6e 2e 6a 70 67 0a 5b 20 24 28 77 68 69 63 68 |an.jpg.[ $(which|
00000040 20 77 62 61 72 2e 73 68 29 20 5d 20 26 26 20 77 | wbar.sh) ] && w|
00000050 62 61 72 2e 73 68 |bar.sh|
00000056
It doesn't come out formatted right when posting in the forum.
-
maybe you could post the contents of your current backup file?
cat /opt/.filetool.lst
cat /opt/.xfiletool.lst
The top file is for files to be added to backup
the bottom file is for files to be excluded from backup
#############################
I have a fully persistent home so for me home is not listed in that file.
That means I have to do my own spring cleaning especially any web browser cache.
So if I was forecast a possible reason for the issue repeating it might be because you have
home named somewhere in your .filetool.lst without an exclusion named in
/opt/.xfiletool.lst of .setbackground ?
tc@box:~$ cat /opt/.filetool.lst
opt
home
opt/eth1.sh
tc@box:~$ cat /opt/.xfiletool.lst
Cache
cache
.cache
XUL.mfasl
XPC.mfasl
mnt
.adobe/Flash_Player/AssetCache
.macromedia/Flash_Player
.opera/opcache
.opera/cache4
.Xauthority
.wmx
I can now say that the problem happens after I update these extensions in the App GUI:
-rw-rw-r-- 1 tc staff 24 Aug 10 22:13 wbar.tcz.dep
-rw-rw-r-- 1 tc staff 43 Aug 10 22:13 wbar.tcz.md5.txt
-rw-rw-r-- 1 tc staff 24 Aug 10 22:13 libxcb.tcz.dep
-rw-rw-r-- 1 tc staff 45 Aug 10 22:13 libxcb.tcz.md5.txt
-rw-rw-r-- 1 tc staff 11 Aug 10 22:13 libX11.tcz.dep
-rw-rw-r-- 1 tc staff 45 Aug 10 22:13 libX11.tcz.md5.txt
-rw-rw-r-- 1 tc staff 56 Aug 10 22:13 imlib2.tcz.dep
-rw-rw-r-- 1 tc staff 45 Aug 10 22:13 imlib2.tcz.md5.txt
-rw-rw-r-- 1 tc staff 11 Aug 10 22:13 imlib2-bin.tcz.dep
-rw-rw-r-- 1 tc staff 49 Aug 10 22:13 imlib2-bin.tcz.md5.txt
-rw-rw-r-- 1 tc staff 24 Aug 10 22:13 Xvesa.tcz.dep
-rw-rw-r-- 1 tc staff 44 Aug 10 22:13 Xvesa.tcz.md5.txt
-rw-rw-r-- 1 tc staff 38 Aug 10 22:13 Xprogs.tcz.dep
-rw-rw-r-- 1 tc staff 45 Aug 10 22:13 Xprogs.tcz.md5.txt
-rw-rw-r-- 1 tc staff 22 Aug 10 22:13 Xlibs.tcz.dep
-rw-rw-r-- 1 tc staff 44 Aug 10 22:13 Xlibs.tcz.md5.txt
-
hexdump changed after updating the above apps.
tc@box:~$ hexdump -C .setbackground
00000000 23 21 2f 62 69 6e 2f 73 68 0a 68 73 65 74 72 6f |#!/bin/sh.hsetro|
00000010 6f 74 20 2d 61 64 64 20 22 23 30 45 35 43 41 38 |ot -add "#0E5CA8|
00000020 22 20 2d 61 64 64 20 22 23 38 37 43 36 43 39 22 |" -add "#87C6C9"|
00000030 20 2d 67 72 61 64 69 65 6e 74 20 30 20 2d 63 65 | -gradient 0 -ce|
00000040 6e 74 65 72 20 2f 75 73 72 2f 6c 6f 63 61 6c 2f |nter /usr/local/|
00000050 73 68 61 72 65 2f 70 69 78 6d 61 70 73 2f 6c 6f |share/pixmaps/lo|
00000060 67 6f 2e 70 6e 67 0a |go.png.|
00000067
Also, I know when the showapps bootcode is used, it complains about an error with X11.
ln: /usr/share/X11/locale No such file or directory
Sounds like the error is caused by the X-related extensions being updated as noted above. There is no /usr/share/X11/locale on the system. But there is a /usr/local/share/X11/locale.
[EDIT]: Added code tags. Rich
-
I will leave it to others to comment on your hex stuff but lets re-look at
tc@box:~$ cat /opt/.filetool.lst
opt
home
opt/eth1.sh
You do realize that your back up is the entire home dir except for files named in the xfiletool.lst?
and do you realize that you have a redundancy IMHO in naming
opt dir and then also naming opt and a file in that dir.
If you do not wish to have opt as fully persistent....can I suggest you at least remove
opt/eth1.sh.
2) and because you have entire home in backup (except those files named in your exclusion file) then mydata.tgz contains a backup of both your
.xsession file and .setbackground file
If you swap from vesa to framebuffer to xorg etc....I suggest you consider not saving xsession file to your backup.
3) Are you aware that those 2 files if not found....are created by the TC boot up scripts.
Its easy to prove this, if interested.
Without scaring you about using the shutdown script....delete your current .xsession file
after looking at its timestamp such as with
ls -al .xsession
rm -rf .xsession
exittc
Use exittc to reboot which backs up your current home but won't find the xsession file, so it will be created by TC scripts
assuming I have not mucked you about...on reboot you can check that your new xsession file has a later timestamp.
I should have mentioned that the core PDF and wiki mention various layers of persistence.
They might help you in that
-
aus9,
Thanks for the reply.
1) Thanks for the explanation regarding xfiletool and filetool. As for the redundancy, I see what you are saying, but I did not edit the file directly (e.g. using Vi or nano). I can only assume stuff I am doing with the OS resulted in that.
2) If you swap from vesa to framebuffer to xorg etc....I suggest you consider not saving xsession file to your backup.
I will have to look into what that means. I never intended to swap anything. Right now I am just trying to use vanilla Core Plus with no persistence. I have norestore as a boot code.
3) I will have to look into this, like I said I am trying to use no persistence. Bottom line, I'm still confused why the no logo error persists.
-
well in Linux we like the idea of free choice...but only if that is an informed decision.
Maybe you could explain what you think you need to achieve with a norestore boot code?
I am not saying its wrong...please understand that....but it might change how we approach your current issue. See?
Let me try and explain the little I know on how things work on 64 bit without repeating the PDF, wiki or core concepts.
1) If a member has a boot code of "norestore" then /etc/init.d/tc-config will recognise that boot code and not action another script called
/etc/init.d/tc-restore.sh
and that last script attempts to unpack your mydata.tgz and place certain files into certain areas including over-writing possilbe system files
2) the net effect of norestore IMHO is start afresh....start with a clean slate....etc
That does not suit me...but that is my choice.
3) Can you be more verbose or explicit on whether you are attempting to have no persistent home, no persistent TCEDIR and where applicable,
no persistent opt dir.
For me, as a crude example....the unpacking of mydata....takes time....and the repacking of mydata on shutdown or reboot takes time.
so I have no home, no opt nor tce packages in mydata.....to speed that bit up.
That means, for me, if I make a mistake in any file under /opt or /home or /mnt/<partition-number>/tce (the TCEDIR) I may have troubles.
4) So if you like no persistence....as you booting with norestore....IMHO your Original Post where you thought you made gtk3 onboot and other stuff....they should not have persisted....and you will be forced to download and load them each and every boot.
And TC has invented Ondemand....which might be what you are looking for?
but as time goes on....why not have a tce dir as a persistent dir to save those downloads?
is that clearer?
-
Hi aus9
4) So if you like no persistence....as you booting with norestore....IMHO your Original Post where you thought you made gtk3 onboot and other stuff....they should not have persisted....and you will be forced to download and load them each and every boot.
The norestore boot code does not affect the TCE directory or the loading of extensions. The base boot code prevents
loading of extensions.
-
@ Rich
thanks for correcting me. feel free to correct more of my stray thoughts.
IMHO if he is not using mydata ...then no files should be over writing .xsession or .setbackground. That is what I was trying to establish if I type with my foot in mouth ;)
Did you have time to look at his hex output?
IMHO it will still be nice to know what level of persistence he has
ie no home....no opt....no tce.....as OP says he has no persistence. Does he mean all of these?
-
Hi aus9
I was hoping the hex dump might shed some light as to why cat and nano produced different results for .setbackground, but
I saw nothing suspicious.
-
Hi hobophil
Would you post the result of:
showbootcodes
-
Though not much important , but ...
Simple question : Suppose with a backup, mydata.tcz is created in default directory. A copy of this mydata.tcz is present in /tce/optional or any other directory in the same partition. The original mydata.tcz is deleted. Would the system restore all the backed-up file or not !
Just a posiblity. ... It had happened with me when I was a fresher. :)
-
Everyone, thanks for the support.
Rich, I have since reformatted the hard drive with different boot codes. However I did save the file /mnt/sda1/tce/boot/extlinux/extlinux.conf which was:
DEFAULT core
LABEL core
KERNEL /tce/boot/vmlinuz
INITRD /tce/boot/core.gz
APPEND quiet waitusb=5 norestore waitusb=5:UUID="387ce92a-7c48-4129-a30e-eeb6de6257c0" tce=UUID="387ce92a-7c48-4129-a30e-eeb6de6257c0"
Yes, I know waitusb=5 is duplicated. I don't know why.
At this point, I have decided just not to update the extensions that I think are causing the problem so I can move on and start configuring the computer for my use. Like, I have emojis working now...
Once I am done making my own remaster, I might go back and try to recreate this issue. Until then I probably won't be able to respond to any posts (at least not quickly - I will probably create new thread with concise info later), but again thanks for the help so far. To me the biggest hint was the error caused during boot, "ln: /usr/share/X11/locale No such file or directory." Also, my Core Plus 9.0 image iso is from March, if that matters? Another weird thing that was happening originally, was that there were duplicate instances of flwm_topside on the onboot list. I'm not sure what caused that.
A summary is: I had Core Plus 9.0 installed to a hard drive, with a persistent home. I did not mess with any files manually such as .filetool.lst and .xfiletool.lst. I have boiled the problem down to, I install Core Plus to hard drive using the GUI from a CD, and when I update the apps through GUI, (list posted previously), my background logo disappears and I also cannot set the background to an image. A workaround (for me) was to re-install Tiny Core from CD to hard drive, without reformatting the hard drive. This brought the logo back and the ability to set an image as a background. However I started completely over and reformatted the hard drive again to be safe.
4) So if you like no persistence....as you booting with norestore....IMHO your Original Post where you thought you made gtk3 onboot and other stuff....they should not have persisted....and you will be forced to download and load them each and every boot.
And TC has invented Ondemand....which might be what you are looking for?
but as time goes on....why not have a tce dir as a persistent dir to save those downloads?
is that clearer?
Thanks aus9. I first had a persistent home when the issue started. I then removed persistence (through the norestore boot code, I did not change any /opt files), but the issue was replicated (which makes me think it is a problem/incompatibility with the extensions). With experimentation, I am better understanding the benefits of Ondemand and I am using it more. I also agree with your explanation of norestore, and I am using it for boot up / shutdown speed and cleanliness.
-
Everyone, thanks for the support.
Rich, I have since reformatted the hard drive with different boot codes. However I did backup the file /mnt/sda1/tce/boot/extlinux/extlinux.conf which was:
DEFAULT core
LABEL core
KERNEL /tce/boot/vmlinuz
INITRD /tce/boot/core.gz
APPEND quiet waitusb=5 norestore waitusb=5:UUID="387ce92a-7c48-4129-a30e-eeb6de6257c0" tce=UUID="387ce92a-7c48-4129-a30e-eeb6de6257c0"
Yes, I know waitusb=5 is duplicated. I don't know why.
...
The Append commands would be less confusing if you changed it to:
DEFAULT core
LABEL core
KERNEL /tce/boot/vmlinuz
INITRD /tce/boot/core.gz
APPEND quiet waitusb=5:UUID="387ce92a-7c48-4129-a30e-eeb6de6257c0" tce=UUID="387ce92a-7c48-4129-a30e-eeb6de6257c0"
-
The Append commands would be less confusing if you changed it to:
DEFAULT core
LABEL core
KERNEL /tce/boot/vmlinuz
INITRD /tce/boot/core.gz
APPEND quiet waitusb=5:UUID="387ce92a-7c48-4129-a30e-eeb6de6257c0" tce=UUID="387ce92a-7c48-4129-a30e-eeb6de6257c0"
Thanks, what about norestore though? I've taken out the duplicate waitusb=5 in my current iteration of Tiny Core.
-
...
Thanks, what about norestore though? I've taken out the duplicate waitusb=5 in my current iteration of Tiny Core.
I believe the original intent of norestore bootcode was for diagnostic purposes.
If you don't wish to save a backup on shutdown, I believe the method is to edit /home/tc/.profile
export BACKUP=0
If you don't wish to restore a backup, then simply don't create one.
-
...
Thanks, what about norestore though? I've taken out the duplicate waitusb=5 in my current iteration of Tiny Core.
I believe the original intent of norestore bootcode was for diagnostic purposes.
If you don't wish to save a backup on shutdown, I believe the method is to edit /home/tc/.profile
export BACKUP=0
If you don't wish to restore a backup, then simply don't create one.
Ok, thanks for the tip.
I'm also thinking if I did base norestore and then updated the apps, it probably wouldn't break my system. I might try that later after remastering.
-
...
I'm also thinking if I did base norestore and then updated the apps, it probably wouldn't break my system. I might try that later after remastering.
iirc base norestore was also intended for diagnostics.
-
... I first had a persistent home when the issue started. I then removed persistence (through the norestore boot code, I did not change any /opt files), ...
When you set up your persistent home, did you remember to remove the home line from /opt/.filetool.lst file?
If it hasn't been mentioned yet, may I suggest you take an hour to read:
http://tinycorelinux.net/book.html
-
... I first had a persistent home when the issue started. I then removed persistence (through the norestore boot code, I did not change any /opt files), ...
When you set up your persistent home, did you remember to remove the home line from /opt/.filetool.lst file?
No, I did not.
-
Sorry to necro this post, but it was solved.
The problem was, I was updating the extensions while using X (gui) desktop. I updated through the command line and now everything is great. Noob error.