SliTaz Forum
You are not logged in.
I have reinstalled Slitaz 5 with ext4 partition and no more "check forced" problems.
It seems that the problems is somehow related to ext2 ...
Regards,
Tibi
Offline
@sidini : I tried your suggestion and here is the result:
root@slitaz:/home/tux# alsactl init
alsactl: parse:1655: Unable to open file '/usr/share/alsa/init/00main': No such file or directory
My problem : no sound with Alsa player or VLC though the audio files are read and volume buttons active.
(audio card Intel N10 / ICH 7 High def. Controler )
NB sound Ok with Windows (dualboot with Slitaz 4.0)
Thanks for your help
Offline
@photino
Sorry man, I haven't seen this warning message before. I don't know what causes it but I guess ALSA is not installed on your system or it's broken.
Maybe some experienced Slitaz user could help you. XD
Have a nice day!
Offline
@photino
When the output from a command indicates a missing file or folder use the package manager to find the package that owns the file.
root@slitaz:/home/tux# [c]tazpkg search-pkgname 00main[/c]
Search result for package 00main
================================================================================
alsa-utils
================================================================================
1 package found with file: 00main
I use the package manager to download a fresh package to the current directory.
This prevents the reinstallation of a corrupt package if the package exists in /var/cache/tazpkg/5.0/packages
[c]tazpkg get alsa-utils[/c]
Install the package with the forced command:
[c]tazpkg install alsa-utils-1.0.27.2.tazpkg --forced[/c]
Offline
So today I just ran spk-dialog, clicked upgrade, and it decided that I needed to upgrade 488 packages (512 installed).
Did someone on the main server (in cooking) just cook everything again, or what happened? Most of it is just new builds, with a single new version.
I intend to install these updates, but I would like to hear first what happened.
Offline
Hi All 
just played with rc2, found 2 issues, probably already reported...just in case,under tux: 1) mouse pointer disappear after click 1 time anywhere inside PCMan,moving mouse it reappears again,doesnt happen in v4... 2) GUI Alsa player cant play files,tried many ways, but aplay from console works ok.
.... well anyway,my question was, when the next rc3? 
thanks
Hi everybody!
What is the best option: to install Slitaz 5.0 RC2 or to use the latest rolling version?
Thanks in advance. ^.^
Offline
Hi Genesis,
My opinion: rolling.
Offline
Thanks, Ceel! 
Offline
How to help me, helping debuging Slitaz 5 rc2?
I'm having several problems that happens when I update programs. Some time the update fix old problems and sometime it make it worse than before. Can't figure it out what cause the problems but I know that it has to do with the fact that something has change between updates. I have been updating many things at once and that have maked it harder to get an idea of what can be the causes of the malafunctioning or at least report something more specific. Want to change the way I work. Too time consuming. I want to start from the most simple and update step by step.
Is it a fast way to return to an old version of a package. In others words, If I think that a particular new version has worsen a problem, how can I installed the old version back to check if that is the case? Will this be a good strategy? Probably I installed slitaz to the hard disk to soon and I should try more live cd working in ram.
I see that there is the option to create a live cd from tazpanel. I would like to create several iso of a particular "state" of updating and compare then to see if I can ping point when a posible problem show up. I'm not interesting in creating flavors or some iso for small ram system, but when a problem occur after downloading a package that might have cause the problem. I'm no expert but I have some knowledge of linux.
Does the "Build a hybrid ISO" in tazpanel will be a good tool for this?
Never use tazlito or this option, but I could start to explore it.
Any advise that you can give me on this matter? It seem to me that updating in chuncks is not a good idea at this stage.
Now that I'm back from vacation I could dedicate more time helping slitaz.
Hoping that what I'm saying makes sense too. I'm open to any suggestions.
Thanks in advance.
Offline
Hello Compostela,
Is there an interest to know when update failed? I mean, RC2 is 3 months old today and rolling is probably much better.
Starting from an old ISO is possible but how do you want to reproduce the successive updates? Some packages have been updated several times; as soon as you'll update one of them you'll download the last update. Believe me, the best way is probably to install the last rolling.
Concerning me, I try to re-install systematically new ISOs after reformat the partition; it takes a few time but thus I can test ISO in frugal and full installation. I never keep rolling more than 2 or 3 updates.
Recently, I installed the 2014/08/04 rolling ISO; it still works perfectly after several updates, yet rolling ISOs from 2014/08/17 doesn't work properly on my computer, even after updates, but rolling ISO from 2014/80/18 works fine... So, it seems that after udate(s), SliTaz is not really like it'd be after an installation with a new ISO.
Offline
Hi Ceel:
Thanks for your comments. I will be trying this "rolling and rolling" strategy. It makes sense after some thinking.
My problem was that I decided to have the whole hard disk for slitaz and when some problems occured that mess up the system, I had to reinstall. At the same time, I needed a working distro for my daily use. Another important thing that I recommend to everybody is to get a NOTEBOOK and write everything you do of importance on it. Changes, error messages, etc. If you don't, it's very hard to know and remenber what's going on or report anything.
Regards
Offline
@compostela
--> I had to reinstall <--
Before I change something
I make an Image to avoid a reinstall if something went wrong.
Using "clonezilla" live-cd for this task will bring back the previous stage
in less than 5 min.
http://clonezilla.org/
Offline
Thanks sixofeight. I will check it out.
Offline
I stalled rolling 2014/08/20 and with a couple of minor exception everything work fine. I see there is a new section; "Slitaz bugs report". shall I open an account there to report presume bugs for now on and leave this section for more general questions and advices?
Thanks
Offline
I signed twice by mistake on the bug report and now I can not use it. Is a way to fix this. Thanks
Offline
Due to pulseaudio now being in the repositories, I decided to give them a shot. With my fully updated SliTaz 5.0-RC2 system, I get the following error when launching pulseaudio:
E: [pulseaudio] module-alsa-card.c: Failed to find a working profile.
E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="0" name="pci-0000_00_01.1" card_name="alsa_card.pci-0000_00_01.1" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1""): initialization failed.
E: [pulseaudio] module-alsa-card.c: Failed to find a working profile.
E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-0000_00_14.2" card_name="alsa_card.pci-0000_00_14.2" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1""): initialization failed.
E: [pulseaudio] module-console-kit.c: GetSessionsForUnixUser() call failed: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ConsoleKit was not provided by any .service files
E: [pulseaudio] module.c: Failed to load module "module-console-kit" (argument: ""): initialization failed.
E: [pulseaudio] main.c: Module load failed.
E: [pulseaudio] main.c: Failed to initialize daemon.
Offline
GUI Login as 'tux' error message: "Failure to execute login command."
Doing 'ctrl-alt-F1' slitaz login: tux ; Password: tux .
Welcome to the Open Source World!
tux@slitaz:~$ startx
/home/tux/.xsession: .: line 3: can't open `/home/tux/.config/slitaz/applications.conf'
The '.config' directory only contains 77 byte README, does not contain subdirectory 'slitaz' or any other subdirectory!
Can (GUI) boot to root by backspacing 'tux' login name and then entering 'root'.
In Terminal: root@slitaz: cat .xsession
Line 3: . /etc/slitaz/applications.conf
cd /etc
cp -ia slitaz /home/tux/.config/
cd /home/tux/.config
ls -al : root root slitaz
chown -Rv tux:tux slitaz
ls -al : is now set to : tux tux slitaz
logout
Login: tux ; Password: tux (ctrl-alt-F7 GUI Interface)
It should now work!
Frank, AC0XL
Offline
@AC0XL
Yeah, it seems that there is no .config/slitaz/applications.conf in the /etc/skel directory, and as such, any new users created will not have that file.
Maybe update the .xsession script to use
[[ -x "/etc/slitaz/applications.conf" ]] && . /etc/slitaz/applications.conf
[[ -x "$HOME/.config/slitaz/applications.conf" ]] && . $HOME/.config/slitaz/applications.conf
Offline
Regarding SliTaz for ARM and sat, specifically the sat 'vdisk' functionality (or lack thereof):
https://github.com/sabotage-linux/sabotage/blob/master/utils/write-hd-image.sh
Offline
[ Generated in 0.017 seconds, 9 queries executed - Memory usage: 1.57 MiB (Peak: 1.77 MiB) ]