SliTaz 5.0-rc2 « SliTaz Forum

SliTaz Forum » English Support » Live and installation

SliTaz 5.0-rc2

(145 posts) (43 voices)

Started 10 years ago by pankso
Latest reply from necrophcodr
This topic is not a support question

Tags:

No tags yet.

« Previous 1…910

Ceel

offline
Administrator

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.

Posted 10 years ago #
compostela

offline
Member

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

Posted 10 years ago #
sixofeight

offline
Member

@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/

Posted 10 years ago #
compostela

offline
Member

Thanks sixofeight. I will check it out.

Posted 10 years ago #
compostela

offline
Member

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

Posted 10 years ago #
compostela

offline
Member

I signed twice by mistake on the bug report and now I can not use it. Is a way to fix this. Thanks

Posted 10 years ago #
necrophcodr

offline
Member

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.

Posted 10 years ago #
AC0XL

offline
Member

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

Posted 10 years ago #
necrophcodr

offline
Member

@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

Posted 10 years ago #
necrophcodr

offline
Member

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

Posted 10 years ago #

RSS feed for this topic

« Previous 1…910

Reply

You must log in to post.