Tiny Core Base > Final Releases
Tiny Core v15.0
Juanito:
Did you check your local copy of gdk-pixbuf2-dev.tcz.dep?
Juanito:
Instead of startx, enter the first line of .xsession to troubleshoot.
Rich:
Hi gadget42
--- Quote from: gadget42 on February 23, 2024, 11:28:56 AM --- ... i had time to write it to a thumbdrive and it fails to bring up the gui and reports "failed in waitforX" ...
--- End quote ---
At that time you are at the command prompt. If you now enter:
--- Code: ---startx
--- End code ---
Does the GUI come up? If it does, it's a timing problem, and
here are two ways of addressing it.
You can insert a time delay as described here:
https://forum.tinycorelinux.net/index.php/topic,26391.msg170331.html#msg170331
Or you can set up a loop that waits for your graphics card as described here:
https://forum.tinycorelinux.net/index.php/topic,26391.msg170335.html#msg170335
andyj:
--- Quote from: Juanito on February 23, 2024, 12:30:47 PM ---Did you check your local copy of gdk-pixbuf2-dev.tcz.dep?
--- End quote ---
That was it. Thanks.
Dies Irae:
--- Quote from: patrikg on February 23, 2024, 02:55:50 AM ---When I read this, I think of the shell's "readline", and that are using in app links.
--- End quote ---
What precisely is the issue if I may ask? What are the 'app links' ?
As for the broken busybox 1.36.1 shell (the double prompt bug),
In cases where users can not remaster the iso (for what-ever reason, such as their vps host only allowing official distribution media, or simply because they find it complicated enough already to just dd the iso onto their usbstick), I see no way how to replace it and work around the issue.
By the time we get our first and seemingly only chance to slip something in (the httplist boot parameter), busybox shell is already in use.
IF there is no way to fix it, that it is to late to change the official iso, I fear those users will have to resort to an additional separate static busybox-ash that is not version 1.36.1 for their prompt (though a bunch of native tools and scripts are set to 'busybox ash' and thus wouldn't trigger their separate standalone busybox ash, I think. I'm just trying to think of solutions here... (in case it is to late to fix the release/iso)).
Edit: Or learn to wait a good second before typing your next command (in case your current prompt just suddenly ends (holding the first part of what you typed) and new prompt appears).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version