SliTaz Forum
You are not logged in.
Hello Aleksej,
As you are the father of Next64, maybe you are the best guy to answer this question.
I installed Next64 for fun; bad idea, isn't it ;-)
Well, the result seems promising. I installed first console only, then JustX and to finish lxde. Hmm this last step was a total failure.
So I came back to more modest ambitions; as the computer is a 10" and Next64 recognizes its touchscreen, I installed LXLauncher, slitaz-icons-nuovext, modified [c]gtk-icon-theme-name="SliTaz"[/c] by [c]"SliTaz-nuoveXT2"[/c] in the .gtkrc-2.0 file for root / .gtkrc-2.0 for tux.
LXLauncher works perfectly excepted it doesn't display any icons in tabs and on the desktop. In the terminal I can see:
[c](lxlauncher:1234): Gtk-WARNING **: 12:34:56.789: Error loading theme icon 'image-missing' for stock: Unrecognized image file format[/c]
Similar messages when I run apps from the terminal; ie Leafpad:
[c](leafpad:1234): Gtk-WARNING **: 12:34:56.789: Error loading theme icon 'document-new' for stock: Unrecognized image file format[/c]
and most of the icons (document-open, document-save...)
I tryed with different icons themes, adapting the .gtkrc-2.0/.mine files each time and got the same result 
When I specify the name of an uninstalled/inexistant icons theme in [c]gtk-icon-theme-name[/c], Leafpad finds its usual icons.
Using [c]gtk-demo[/c], most of the icons appear as a white square with a red cross inside whatever the icons theme used; for an uninstalled icons theme, I view all the icons inside GTK2+.
My deduction is that GTK2+ in Next64 cannot read .png file (no problem in Rolling).
I would just like to know if the problem comes from GTK2+, and I'll find another game, or did I forget to install a package? (but I really don't see which one)
Here attached, the installed packages list.
Offline
Hi Ceel,
Currently I'm so far from the SliTaz development at all.
SliTaz Next is still broken, even in it's basis.
I believe that Unrecognized image file format error is related to the gdk-pixbuf package. And there some inconsistency, it's hard to say more precise...
The key is dependencies.
1) It may be that gdk-pixbuf should be recompiled if it's dependencies was updated, but gdk-pixbuf was compiled prior to that updates and it depends on the old versions not existed anymore.
2) It may be that gdk-pixbuf was updated, but packages that depends on gdk-pixbuf was not updated.
Looking thru gtk2 log I see red exclamation sign near to gdk-pixbuf in the line 72. It means that gdk-pixbuf was updated since that, i.e. gdk-pixbuf is newer than gtk2.
But... Version of gdk-pixbuf the same — 2.38.0. The probability exists, but I don't think it's so high: you can "to recook" gtk2 package (using the button at the bottom of the gtk2 package page [but you need the SliTaz browser {TazWeb} and need to follow this link from the same cooker site, not from this forum - protection from the bots] ) and then download and install updated package manually (SliTaz Next packages on the mirror will not update).
Sorry for dropping the SliTaz Next development.
Offline
Hi Aleksej,
Thank you for your answer. I'm going to have a look at this this week end.
Offline
@Aleksej
Does Slitaz Next64 supports multilib (ability to install and run 32-bit packages) too?
Offline
Hi Aleksej,
I followed your instructions but probably not correctly: entered [c]http://cook.slitaz.org/next64/gtk2[/c] in the address bar of TazWeb, connected to the gtk2 package page but didn't find any button to "recook" the package. :-/
I tryed to recook gtk2 with cookutils, cloning wok-next but meat an error with the cooking of gtk2-demo :-(
(tryed with other packages without any problems)
Anyway, late in the evening yesterday I came back on the first computer on which I've tryed to install LXDE, removed all the packages to come back to a justX version, keeping only Leafpad.
Just to confirm the problem with gtk2, I modified [c]gtk-icon-theme-name[/c] and... new icons appeared in dialog boxes and Leafpad.
I installed LXLauncher and @@ all worked fine!
Maybe, doing so many tests on the second computer, I've broken something. I'm going to reinstall Next64 and let you know if I get a happy end.
Offline
Hi there,
@mistfire
No, SliTaz Next doesn't support multilib. When I made it back in time, I followed Linux From Scratch "recipes". LFS doesn't support multilib, so SliTaz doesn't support it too.
Sorry, the development of SliTaz Next stopped. It's hard to non-programmer to follow all the updates on the one hand, and to find reliable patches to the legacy on the other hand. About a week ago I tried to follow LFS to update the toolchain. No luck. Every time gcc failed to make the new version of itself after long, more than a hour, runs.
I think I can't cope with the software. And I think I should not repeat the things already resolved on other Linux distributions by myself. I think it will better if I'll use some other small Linux distro, most-least actively developed, with good package base and without systemd 
Well, I think I'll use its packages to make SliTaz clone (like made tower using cubes) and will make SliTaz native packages to it if I will need them.
I think Adelie Linux is a good candidate. It is Musl based instead of widespread Glibc, but I think it's not the problem. Adelie actively updated providing packages for many platforms. Packages are well splitted. I hope I'll find some time sometimes to test it
@Ceel
There a weird system on the cook server, but I think we can't make it better. Direct link will not work, the button will be hidden. Your web browser should send the server correct HTTP REFERER. In few words, it contains the URL address of the page you leave. So, you should 1) open any relevant page on the cook server, and 2) click the link on that page to go to gtk2 page. Better if you 1) just search for gtk2, and then 2) click on gtk2 link on the search page.
It is not 100% guarantee against the malicious (or curious) web bots that may click on the "Recook" buttons and to load cook server with unwanted work. But it works and no false triggerings since there.
Offline
Hi Aleksej,
Understood; direct link doesn't work, search for gtk2 from the next64 cooker page works. But I share your point of view; GTK2 is probably not the culprit.
(BTW, TazWeb (Rolling 32) cannot dowload files? I had to use another web browser to dowload the recooked package. Normal or bug?)
I reinstalled Next64 and went into the same trouble.
I installed it a new time after I've changed the partition format from EXT4 to EXT3 (like on the computer where GTK2 works correctly, who knows?), but no
I reinstalled it a last time without conviction, installing packages exactly in the same order I did on the other computer, following its tazpkg.log file and... that's it.
I guess 2 (or more) packages modifies each other; depending which one is installed first, GTK2 will work or not. I'll take time to see more clearly at this later; for the moment, I'm going to install some apps and see what Next64 is able to do.
Offline
[ Generated in 0.018 seconds, 7 queries executed - Memory usage: 1.55 MiB (Peak: 1.77 MiB) ]