SliTaz Forum
You are not logged in.
Pages: 1
Trash can doesn't appear anymore on desktop and in PCManFM.
PCManFM doesn't display HD anymore.
slitaz-rolling.iso 20140804 + update works fine
On both ISO, icons in Application Launch Bar are not in the defined order: first time you click on the up arrow, the icon goes up from 2 positions and first time you click on down ... Don't know how long we hang out this.
Offline
Hi Ceel,
I can't understand about “Application Launch Bar”. Is screenshot will help me?
Offline
Hi Aleksej,
For this example, I've placed 7 applications in Launch bar in the order below:
1. Midori
2. PCManFM
3. Sakura
4. TazPanel
5. Galculator
6. Screenshot
7. Leafpad
I want to place TazPanel just before Sakura; I select TazPanel and click Up.
The order in the left part of the Application Launch Bar window is correct but in the launch bar, PCManFM is now in the second place, before PCManFM.
I did it with only 5 applications (PCManFM-Sakura-Galculator-Screenshot-Leafpad) and it worked...
[attachment=32878,1626]
Offline
... and always with iso 20140815, PCManFM doesn't show USB drives and doesn't mount them automatically.
Offline
Thank you, Ceel.
I not used LXPanel so not touched this problem. (I use Stuurman as PCManFM clone, and Waterline as LXPanel clone. Sad, but author discontinued it's development.)
Seems like it's bug from PCMan.
Anyway I plan to try latest Rolling, maybe tomorrow night.
Offline
2014-08-17 00:58 : Cook pkgdb: Creating all flavors
2014-08-17 00:45 : Cook pkgdb: Creating all packages lists
ssh://tank.slitaz.org/home/slitaz/cooking/iso
All files updated except 3 *.flavor files. Date: May 26
Used old version of packages.
http://cook.slitaz.org/cookiso.cgi?distro=rolling-core-4in1
[c]Cookiso started: 2014-08-17 01:10[/c]
[c]No core-4in1 flavor in /home/slitaz/cooking/flavors[/c]
Previous 20140815 log was NOT contained this 'No flavor' message
Need to create link of this dir?
[c]/home/slitaz/cooking/chroot/home/slitaz/flavors/[/c]
Or better ln -s *.flavor file from
[c]/home/slitaz/cooking/chroot/home/slitaz/live/core.flavor[/c]
to
[c]/home/slitaz/cooking/iso/core.flavor[/c]
Offline
http://cook.slitaz.org/cookiso.cgi
After 3 hours iso was built again. I saw this week ago.
Differences in ssh://tank.slitaz.org/home/slitaz/cooking/iso
*.flavor files are fresh, but core4in1 flavor file missing.
These files are generated and 1-hour newer than flavor-files in /home/slitaz/cooking/chroot/home/slitaz/live/
After first iso-build tazlito.conf was 977 bytes - now 957 b.
/home/slitaz/cooking/chroot/home/slitaz/live/tazlito.conf : 961 b.
@Ceel
Are you starting pcmanfm as root? I forgot about auto-updating /root/.xinitrc in slitaz-configs-base receipt. I did changes to ~/.xinitrc and found no problems, even more: less dbus* processes in memory. iso build log contains 'cp can't stat xinitrc' but usb drive auto-mounted correctly with rolling-core 20140815.
Offline
@ az_ua,
No, as tux; problem appear as well as in frugal mode than on a full install.
Offline
To be clear: talking about volumes in pcmanfm-sidepanel. Don't know about Application Launch Bar(you can try
/etc/lxpanel/default)
Check this:
[c]tazpkg -l | grep slitaz-configs[/c]
[c]slitaz-configs 5.5.2 base-system[/c]
[c]slitaz-configs-base 5.5.4 base-system[/c]
This is default in rolling-core 20140815 and no any troubles with HD+USB.
Now dbus-launch moved from [c]/etc/xdg/autostart/pcmanfm.desktop[/c] to ~/.xinitrc
version slitaz-configs-base (5.5.4) was made to auto-overwrite /home/*/.xinitrc including /home/tux/.xinitrc
New .xinitrc must be 566 bytes (old was 512)
[c]ls -l ~/.xinitrc[/c]
Try latest 20140817 ISOs. can't reproduce this... All drives are visible.
if boot with [c]home=[/c] option ~/.xinitrc will be old until manually updated.
Offline
@az_ua
[c]/home/slitaz/cooking/chroot/home/slitaz/flavors/[/c]
tank.slitaz.org mirror of http://hg.slitaz.org/flavors/file/tip
Last commit to http://hg.slitaz.org/flavors/ was May 29
Everytime cookiso gens a flavor it cd to /home/slitaz/flavors,[c]hg pull -u[/c],rebuilds $flavor.flavor (tazlito pack $flavor),tazlito gen-flavor $flavor
This guarantees an iso with up to date package versions.
Is this your commit?
http://hg.slitaz.org/wok/rev/a10a76a8f97e
--- a/slitaz-configs-base/receipt Sun Aug 10 21:05:42 2014 +0000
+++ b/slitaz-configs-base/receipt Mon Aug 11 01:56:38 2014 +0200
3.3 @@ -1,7 +1,7 @@
3.4 # SliTaz package receipt.
3.5
3.6 PACKAGE="slitaz-configs-base"
3.7 -VERSION="5.5.3"
3.8 +VERSION="5.5.4"
3.9 CATEGORY="base-system"
3.10 SHORT_DESC="SliTaz config files for text based systems."
3.11 MAINTAINER="pankso@slitaz.org"
3.12 @@ -53,3 +53,12 @@
3.13 chown -R root.root $fs
3.14 chmod 0750 $fs/root
3.15 }
3.16 +
3.17 +post_install()
3.18 +{
3.19 +echo "Updating ~/.xinitrc"
3.20 + for i in [c]ls -d /home/*[/c]
3.21 + do
3.22 + cp /etc/skel/.xinitrc $i/.xinitrc
3.23 + done
3.24 +}
If yes please nest it inside a conditional so it stops this error when building an iso:
[c]cp: can't stat '/etc/skel/.xinitrc': No such file or directory[/c]
Offline
@ az_ua,
[c]tazpkg -l | grep slitaz-configs [/c]gives
[c]slitaz-configs 5.5.4 base-system[/c] and not[c] slitaz-configs 5.5.2 base-system
slitaz-configs-base 5.5.4 base-system[/c]
I gave you a wrong information: trash an HD problems don't exist on a frugal install, just on full install.
I tested last ISO (20140817) -> same as 20140815, no trash and no HD in PCManFM with full installation.
Below, 2 screenshots.
The first, 4in1-140804.png is last ISO that doesn't have any problem (except Application Launch Bar but I agree with Aleksej, I think it' a bug in PCManFM).
The second, 4in1-140815 shows the problem I meet with the two last ISOs.
I've made my full installation with the 4in1 iso; I'm going to see if problem exists with installation from core ISO.
[attachment=32896,1627] [attachment=32896,1628]
EDIT: No chance with the last ISO of the day.
Offline
Hi,
I tried the rolling of the day (20140818) and... that's OK for trash and PCManFM shows HD !
I don't know if you found a bug or if problems were caused by a big BIG error in my menu.lst. I'll try to re-install the previous rolling next week end with a correct setting in menu.lst and tell you what you must never do if it was the cause.
Offline
I cannot wait the week end. I needed to know.
Yes it was my mistake. What I've done? This:
[c]
# SliTaz 5.0 - full install #1
#
title SliTaz 5.0 rolling 04/08/2014 - full install on sda5 (kernel 3.2.53)
root (hd0,2)
kernel /boot/vmlinuz-3.2.53-slitaz root=/dev/sda5 nomodeset
# SliTaz 5.0 - full install #2
#
title SliTaz 5.0 rolling 15/08/2014 - full install on sda3 (kernel 3.2.53)
root (hd0,4)
kernel /boot/vmlinuz-3.2.53-slitaz root=/dev/sda3 nomodeset
[/c]
The loaded kernel didn't correspond to the file system...
Strangely, it didn't seem to have an incidence on the 04/08/2014 version; it always displayed trash on desktop and HD in PCManFM.
Sorry for this wrong alarm and the inconvenience caused, az_ua.
Offline
Pages: 1
[ Generated in 0.017 seconds, 8 queries executed - Memory usage: 1.56 MiB (Peak: 1.77 MiB) ]