SliTaz Forum
You are not logged in.
@ Aleksej,
I know you are very busy with the 64bit kernel.
The following reports are only for information.
Maybe they will be usefull for other users.
Offline
#1 Updating slitaz-base-files breaks the system
Did you install Next changing root password?
After you'll have updated slitaz-base-files, root password will be come back to root.
And if you've changed the default user tux (ie ceel), you can see after installation but before first boot that /home/ceel has been created. Well, what more normal?
Boot and have a look in /home; you'll see that a new user has been created: /home/tux @@ ??.
Now, update slitaz-base-files (but I think it's true with others slitaz-xxx packages) and you'll be able to boot only as tux (become default user) and no password; unable to boot as root.
Remember
Ceel - 2017-11-15
After update, ceel user has disappeared.
Reboot -> login as tux (no password), root password came back to root, user displayed in the upper right corner is user.directory.
Diplays a windows on desktop with error: Error initializing authority: Error calling bla bla bla...
Unable to run applications: ie for firefox light -> Profile Missing Your Light profile cannot be loaded. It may be missing or inaccessible.
and
# Ceel @ Wed, 22 Nov 2017 21:50:27 UTC
After tests, found that are the new builds of slitaz-base-files, slitaz-configs and slitaz-config-base that break my system. If I don't update them, my computer boots without any problems.
Install Next with root password= root and default user= tux/tux and all goes well... or almost.
Offline
#2 No access to other partitions after updating slitaz-base-files
boot.log after updating slitaz-base-files:
Processing /etc/init.d/local.sh
Starting X environment...
Starting message bus daemon: DBUS... Unknown username "polkitd" in message bus configuration file
Unknown username "polkitd" in message bus configuration file
[ Done ]
Starting all daemons...
Setting up kernel security rules... [ Done ]
WARNING: IPtables rules are disabled
Starting inetd daemon: inetd... [ Done ]
Starting ntpd daemon: ntpd... [ Done ]
Welcome to your box
Message at screen:
[attachment=45574,2596]
I can see my partitions in PCManFM; can't open them
[attachment=45574,2597]
but I can mount them from a terminal. Same with USB media 
It looks similar to the known problem you described in http://people.slitaz.org/~lexeii/forum/forum-posts2.html#post45415
[*]Codename: Restricted Super-User
Root user can't log in using SLiM.
[*]In the graphical session root user can't mount hard disk partitions.
[*]The problems are with UNIX groups, Polkit permissions, DBUS sessions, ConsoleKit2 and friends. I can't solve this problem soon. Any help is appreciated.
Offline
#3 Can't change the mirror if no packages list
Aleksej, you were right, I didn't connect to the good mirror. I found why.
You cannot change mirror with [c]tazpkg -sm [/c] as long as you didn't load the packages list:
root@next:/home/tux# tazpkg -sm
Creating folder "/var/cache/tazpkg"... [ Done ]
Recharging repository "Main"
================================================================================
Checking... [ Failed ]
Creating backup of the last packages list... [ Done ]
Getting "bundle.tar.lzma"... [ Failed ]
Restoring database files... [ Done ]
================================================================================
Recharging failed
Current mirror(s)
================================================================================
http://mirror.slitaz.org/packages/next/
Please enter URL of the new mirror (http, ftp or local path). You must specify
the complete address to the directory of the packages and packages.list file.
New mirror(s) URL: http://mirror1.slitaz.org/packages/next/
Setting mirror(s) to: "http://mirror1.slitaz.org/packages/next/"
root@next:/home/tux# tazpkg -sm
Recharging repository "Main"
================================================================================
Checking... [ Failed ]
Creating backup of the last packages list... [ Done ]
Getting "bundle.tar.lzma"... [ Failed ]
Restoring database files... [ Done ]
================================================================================
Recharging failed
Current mirror(s)
================================================================================
http://mirror.slitaz.org/packages/next/
Please enter URL of the new mirror (http, ftp or local path). You must specify
the complete address to the directory of the packages and packages.list file.
New mirror(s) URL:
Nothing has been changed.
root@next:/home/tux#
By the way, [c]Current mirror(s)[/c]
I always thought that mirror file contained the mirror where tazpkg must connect. Can I enter more than 1? I'll do the test.
Offline
Hi Ceel,
Sorry I can't deep into the problems at this time.
Currently I bootstrap native x86_64 environment, and currently 386 packages with x86_64 architecture are done now, but I not touched the Kernel yet...
By the way I have a draft for the mirror chooser 
Please download and examine it before using it.
You should execute it with root privileges.
And it depends on the netselect package.
What does the script do?
It selects the best mirror that satisfies all the next conditions:
[*]it contains actual packages (tested by comparing files IDs with mirror1 server),
[*]mirror is nearest to you (tested using [c]netselect[/c] by identifying the number of hops), and
[*]mirror is fastest (tested using [c]netselect[/c] too by identifying the mean response time).
Script works for 10-25 seconds and then changed your preferred mirror.
I plan to integrate this script to tazpkg and to run it once a 1-2 hours automatically before tazpkg commands that give info from the mirror.
Offline
Hi Ceel,
Thank you very much for what you are!
Problems #1 and #2 was caused to the same bug I think.
Once upon a time I've made a commit to Cookutils that recreate the receipts placed later to the packages. Problem is the variable $CONFIG_FILES was no more located in the receipt since then. So, all the files — and configuration files too! — was the subject to update. Many packages (about 60) was affected to this bug.
Now this bug is fixed (one line where [c]CONFIG_FILES[/c] added), all affected packages was repacked and transferred to the Mirror1 server. And you can update your packages now using mirror1.
I apologize for any inconvenience.
Offline
Touching the problem #3.
Tazpkg "-sm" command understand other syntax too:
[c]tazpkg -sm http://example.com/mirror[/c]
But I don't know if it will help here or not...
I'm not ready to patch this bug, sorry.
Offline
Hi Aleksej,
No problem, it was not a call for help. I kown Next is still in an experimental state. Thank you to have fixed #1 and #2; I'll update my system as soon as I have time. For #3, you just have to know, and [c]leafpad /var/lib/tazpkg/mirror[/c] works fine ;-)
I tried choose-mirror script; it has worked and selected http://download.tuxfamily.org/slitaz/. Maybe better to keep mirror1 for Next.
Offline
Hi Ceel,
SliTaz needs testers (between you and me and the lamppost, SliTaz needs users).
I'm happy you're here and point me to problems that I overseen, solving them make SliTaz better...
I should warn you problem #2 will not be solved if you just "update your system". Look, update of slitaz-base-files reverts some files (configs) to initial state. For example, /etc/group and /etc/shadow. So, now your system don't know nothing about "user" called "polkitd".
Package "polkit" in a post-install phase adds group and user "polkitd", and you can repeat that script using command
[c]tazpkg reconfigure polkitd[/c]
Package "dbus" adds group and user "messagebus". Your system may lack them as well. And so on...
> I tried choose-mirror script; it has worked and selected http://download.tuxfamily.org/slitaz/. Maybe better to keep mirror1 for Next.
Trust them :-) It selects really the best mirror for you. Another thing is that "the best #1" can differ from "the best #2, #3..." very insignificant.
I plan to use mirror1 as initial value and then mirror chooser will make its work. I'm almost sure, it will always choose Brazilian mirror for Brazilian users
But that's another story.
Offline
#4 tazx: Install or reconfigure Xorg
tazx doesn't display the driver in the alphabetic order and
browsing the list you'll find twice the drivers.
#5 tazx: Autotstart Xorg by SLiM on boot
When I launch SLiM from the console, my old friends etc, proc, sys and Co are come back on my desktop
#6 Unable to run links in graphic mode
It works correctly on Rolling 5.0 on the same computer.
I didn't find why it doesn't work on Next but I've broken my system :-/
I think it is because I've made a mistake and removed xorg-server. I've reinstalled it but now Next boot in text mode and when I try to launch SLiM:
Europe 2018 i686
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.76-slitaz root=/dev/sda6 nomodeset
Build Date: 28 August 2017 11:09:22AM
Current version of pixman: 0.34.0
Before reporting problem, check http://www.slitaz.org/
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (**) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log, Time: Thu Feb 8 22:14:51 2018
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using config system directory: "/usr/share/X11/xorg.conf.d"
(EE)
Fatal server error:
(EE) no screens found(EE)
(EE)
Please consult the The X.Org Foundation support
at http://www.slitaz.org/
for help.
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.
I will try to get out of there tomorrow night; any help will be appreciated.
Edit:This forum doesn't like me; I'm always unable to attach any .log or .txt files.
http://paste.slitaz.org/?0df7a9b3960d583b#0ea7KeDavPv8BBvihKKxwWFZESaPgqlEFQoBWBiYGKc=
Offline
Hi Ceel - now you dont have any more problems with attachments
and dont use tazx with next - there are two different mesa packages mesa and mesa17
http://pkgs.slitaz.org/?package=mesa&version=n
and tazx uses mesa, but the correct one is mesa17.......
you have a total mess, when you use tazx
Offline
@ kultex,
I think you are under the truth.
To be honest, I've broken the X-server and try to fix it with tazx. But it has been a total disastre Even passwords were "reseted" (no password for tux and root for root).
I haven't be able to restore my system and had to reinstall Next.
Are ther other tools that we mustn't use in Next?
This allow me to see 3 problems in TazPkg:
[*]Sometimes, TazPkg (last version) doesn't remove the package you ask it for but another one that the name starts like:
root@next:/home/tux# tazpkg -r syslinux
The following packages depend on package "syslinux-slitaz-repack":
syslinux-slitaz-extra-repack
Remove package "syslinux-slitaz-repack" (4.06)? (y/N) y
Removing package "syslinux-slitaz-repack"
================================================================================
Removing all files installed... [ Done ]
Restoring Busybox applet ar... [ Done ]
Removing package receipt... [ Done ]
================================================================================
Package "syslinux-slitaz-repack" (4.06) removed.
Remove packages depending on package "syslinux-slitaz-repack"? (y/N) n
Then it is OK:
root@next:/home/tux# tazpkg -r syslinux
The following packages depend on package "syslinux":
syslinux-extra
tazinst-gui
Remove package "syslinux" (4.06)? (y/N)
[*]TazPkg cannot update openbox:
root@next:/home/tux# tazpkg -gi openbox --forced
Package "openbox-max-3.6.1" already in the cache
Installation of package "openbox-max"
================================================================================
Small-footprint and standard compliant Window Manager (allow icons in menus +
SVG support)
--------------------------------------------------------------------------------
Copying package... [ Done ]
Extracting package... [ Done ]
Remember modified packages... [ Done ]
Installing package... [ Done ]
Removing all tmp files... [ Done ]
================================================================================
Package "openbox-max" (3.6.1) is installed.
I didn't notice any problems with other packages that have composed names too (ie: tazinst/tazinst-gui, libfm/libfm-extra/libfm-gtk ...)
[*]When installing a package using the [c]-i[/c] option, TazPkg claims (but installs correctly the package):
root@next:/home/tux# tazpkg -i openbox-3.6.1.tazpkg
/usr/libexec/tazpkg/install: line 424: can't open openbox-3.6.1.tazpkg: no such file
/usr/libexec/tazpkg/install: .: line 424: can't open './receipt'
Installation of package "openbox"
================================================================================
Small-footprint and standard compliant Window Manager
--------------------------------------------------------------------------------
Copying package... [ Done ]
Extracting package... [ Done ]
Remember modified packages... [ Done ]
Installing package... [ Done ]
Removing all tmp files... [ Done ]
================================================================================
Package "openbox" (3.6.1) is installed.
root@next:/home/tux# tazpkg -i light-42.tazpkg
/usr/libexec/tazpkg/install: line 424: can't open light-42.tazpkg: no such file
/usr/libexec/tazpkg/install: .: line 424: can't open './receipt'
Installation of package "light"
================================================================================
Light 42.0
--------------------------------------------------------------------------------
Copying package... [ Done ]
Extracting package... [ Done ]
Remember modified packages... [ Done ]
Installing package... [ Done ]
Removing all tmp files... [ Done ]
Update system databases... [ Done ]
================================================================================
Package "light" (42.0-1.20151031172618) is installed.
Offline
Hi Ceel,
> TazPkg ... remove ... another one that the name starts like
This is chronic bug in the TazPkg and I not fix it yet, sorry...
Packages name isn't matter. Clue is in the $PROVIDE variable.
Look for syslinux-slitaz-repack receipt:
[c]PROVIDE="syslinux"[/c]
openbox-max:
[c]PROVIDE="openbox openbox-imlib2"[/c]
What the idea of $PROVIDE variable?
Some packages may provide the same functioning: "openbox" is just strict package that can't understand SVG images and something else, while "openbox-max" is full featured package.
If you're already installed one of them, "openbox" or "openbox-max", then you'll don't need the other.
You may install the package "openbox-max", but it may occurred that some receipt require "openbox". In this case TazPkg will not install "openbox" because you already have "openbox-max" that [c]PROVIDE="openbox"[/c].
Excuse my bad language. I'll try to explain it more if required...
All described above touched the packages installing.
The same now is in the packages removing.
You may install "openbox-max" and then you may remove "openbox" (read: any package that provide "openbox").
Over the years, this feature make all worse than better.
I think I should to find and remove it.
> root@next:/home/tux# tazpkg -i openbox-3.6.1.tazpkg
> /usr/libexec/tazpkg/install: line 424: can't open openbox-3.6.1.tazpkg: no such file
In the 2017 (I can't recall better) there was significant change in the Busybox. In some cases you can't just specify filename in the current directory; you should prepend it with "./" like this:
[c]tazpkg -i ./openbox-3.6.1.tazpkg[/c]
or even:
[c]tazpkg -i /home/tux/openbox-3.6.1.tazpkg[/c]
There may be something relative.
Offline
Hi Aleksej,
Thank you for your explanations; they were perfectly clear.
Reading your post, I remembered I've read this (and forgot it since 
) in the recipes documentation this summer when I started to learn how to do packages. Unfortunately this "project" stayed in my to-learn-list because time misses to me.
Offline
Hello all,
After I've updated my system this evening (I didn't do it since May 31st) the upper panel has disappeared
I tried the old good method we used with SliTaz 4.0 (removed /home/tux/.config/lxpanel/slitaz/panels/*) but the panel doesn't come back.
Same when I login as root; and in this case, a right click on the desktop does not display the good context menu.
Any idea?
Offline
Hi Ceel,
I tried too to update an old ISO, and it fails too (Erkan Yilmaz forced me to do it ☺).
The update process was long, and during it, first, LXPanel's menu stops to work, then LXPanel itself, TazWeb fails, then all hangs :-(
I can only guess (because I'm too slow on things I not very interesting) that old ISO version has different Glibc and/or some very base packages (toolchain). Can you compare the versions of toolchain in that original ISO and that the link say?
It looks for me now, two solutions are exists: say old ISO is un-upgradeable and make new one; update (rebuild) all the packages contained in the ISO, maybe somewhere old dependency not updated (we have no tools currently to check this).
Offline
More or less same here, Slitaz Next from USB version 20170930, looks good, but there are some things made it unusable.
-Broadcom 4313 didn't work first (fixed downloading and reinstalling the driver/firmware from the mirror)
-Tazpanel was completely unusable/ mainly unckickable. Probably as it was ran on Netsurf browser. I tried installing Tazweb and Midori - both didn't start with terminal complaining of WebkitGtk missing, trying Tazpkg -gi WebkitGtk didn't bring any results.
-Tazpanel wifi section doesn't have any place to input WPA password, just SSID, needed to edit the config file manually.
-some other apps refused to start.
After all I tried the excercise and updated Slitaz Next. It went ok, but as in your case, lxpanel disappeared. In my case I even failed to login as root account (just tux)... Using F1 openbox didn't work too.
What is the issue with WebkitGtk? Is there any package around or you renamed it? How can Tazweb be workably installed?
By the way, what is the future plan for Next? You are going to stick with LXDE or rather jump over to LXQT. It seems that more and more distros switch to the last, and keeping in mind Slitaz rather rare releases...!?
P.S. the normal core or core64 version became unusable for me (Broadcom wifi and ATI/Radeon graphics before all, other crashes and annoyances) since few months ago kernel upgrade, so I'm looking towards Next. is there any iso backup on the server with older pre 3.16 kernel version?
Offline
Hi Alex,
Three+ evidences that old ISO isn't upgradeable.
I not plan to make new one in the near future, sorry.
SliTaz Next is a side project. Back to days when ISO was realized, it was not bad days.
Starting this year, I think you heard all that "hype" about many and many vulnerabilities: in the Intel CPUs, in the Linux kernels, in the GCC compilers, anywhere.
They said that 32-bit software, 32-bit Kernel — are dead, because no one have time to "protect" them.
They said that only Linux Kernel 4.14+ and GCC-7.3+ may protect you. And what? Kernel is OK, but, frankly I need to update it regularly (while I don't), about once a week. But GCC isn't OK. Seems like old (and not even old) software isn't compatible with GCC-7.3.
I don't know, I'm not a programmer. I can find and apply patches, that's all :-D
(OK, I can write shell scripts, but it don't make me programmer of any sort)
Many and many "tasty" things are stop to compile since I upgraded GCC to 7.3.
[*]Both versions of WebkitGTK (webkitgtk and webkit2gtk 32-bit, as well as webkitgtk and webkit2gtk for 64-bit).
[*]Qt v.4 and all packages based on it
[*]Qt v.5 and all packages based on it
I don't know what to do.
I think, while the SliTaz Next is side project, and looking for about-zero interest to it, I just continue to spend my time habitually: upgrading Cookutils and updating some packages here and there. It looks like it require few years to update them fully :-D
So.
[*]Old ISO isn't upgradeable.
[*]New ISO will not be created because of the broken WebkitGTK and Qt.
(Even SliTaz Tazpanel compatible only with WebkitGTK from the Cooking/Rolling repository; and was never compatible with Next/Next64, nevertheless you're using TazWeb or Midori based on WebkitGTK, or anything else...)
(PS. And SliTaz bootloader, Syslinux / Isolinux is very very changed, it looks like I have no knowledge how to adopt that heavy patched SliTaz version of it to be compiled using the new toolchain)
(PPS. SliTaz Next is dead? No, I don't think so ☺)
Offline
@Ceel @aledie
> the upper panel has disappeared
Could you check if you get some more clues from your LXDE/run.log ? (1)
What works for me is that I made it work now with OpenBox
but I think ratpoison, dwm, ... could also be an approach instead of lxde-session
> But GCC isn't OK. Seems like old (and not even old) software isn't compatible with GCC-7.3.
> ...
> Many and many "tasty" things are stop to compile since I upgraded GCC to 7.3.
Is it possible to downgrade gcc to a version that makes "less" trouble?
> (PPS. SliTaz Next is dead? No, I don't think so ☺)
Yeah, I think the same
@Aleksej
Thanks for all the work you do, not only in regards to Next!
(1) http://people.slitaz.org/~eyilmaz/blog/2018_06_12_using_openbox_for_the_moment_on_Next.txt
Offline
Hi Aleksej,
quite an optimist approach..., when all the things around are breaking, the hope is still here, and we will see Slitaz Next someday, even if its version 20.04
Anyway, tried it again with iso version 20170930, with following steps made it a bit more useful for me:
-installed firmware-brcmsmac-20170906.tazpkg
-installed libwebkit-1.8.3.tazpkg (from 5.0 rolling version)
-installed libpng12
-installed tazweb (and midori), both start properly. Setting tazweb as default browser.
-starting Tazpanel with tazweb instead of netsurf makes it usable and clickable.
@Erkan - installed fluxbox and jwm just in case and will try an upgrade later today.
Offline
> with following steps made it a bit more useful for me:
cool!
progress is step by step :-)
time to listen to NKOTB: https://en.wikipedia.org/wiki/Step_by_Step_(New_Kids_on_the_Block_album)
Offline
Hi Erkan,
-updated, same result - the LXpanel disappeared. At login an error message window complaining about "GDBus.Error:org.freedesktop.ConsoleKit.Manager.Error.General: Unable to lookup session information for process '5501'"
-Tazpanel/ Tazweb/ Midori work just fine also after the update.
-Openbox and Fluxbox as alternative work just fine, JWM doesnt log into.
-Posting the LXDE/run.log (both from lxsession and lxsession-default apps), as requested.
Offline
thx for the feedback!
P.S.
we definitely miss a "LIKE this post" feature in this forum :-(
Offline
Hmm... the culmination of this all, the test was done without rebooting, just logoff and on. Doing tazusb writefs lzma only worked from the terminal. Rebooting with the new rootfs.gz brought me - login into LXDE after a minute waiting (without panel), Openbox and Flux a bit faster. The themes in OB/FB seemed broken, wifi stopped working again (probably cuz kernel upgrade), total mess with mounts (were many slitaz partitions on the screen and file manager, no PC's HD partitions however, needed to mount from tazpanel). When i tried installing a .tazpkg package for wifi, package manager didnt open at all. Other buggy signs. Maybe Aleksej is right, the iso should not be updated.
P.S. By the way, trying reinstalling lxpanel after upgrade which made it disappear pulls quite some dependencies (wayland, xorg related, etc).
Offline
Ref:
slitaz-next64
Linux slitaz 4.16.0-slitaz
tux@slitaz:~$ uname -a
Linux slitaz 4.16.0-slitaz #2 SMP Thu Apr 5 11:07:34 UTC 2018 x86_64 GNU/Linux
http://forum.slitaz.org/topic/slitaz-uefi#post-46197
http://forum.slitaz.org/topic/slitaz-uefi?bb_attachments=46197&bbat=2655
Offline
[ Generated in 0.018 seconds, 7 queries executed - Memory usage: 1.63 MiB (Peak: 1.77 MiB) ]