SliTaz Forum
You are not logged in.
Hi,
I was testing this weeks slitaz-rolling.iso startet via grub4dos. I am impressed, that midori.video is now in the image of 50 MB and working so well.
There is a directory Packages SliTaz5.0 on my harddisk. It contains 5 GB of data. Trying to copy the directory with pcmanfm the system freezes always at 46 %. It does not matter to which USB-harddisk I copy it. It even freezes at 46 % even when copying the directory from my build in hardisk to itself. An iso with SliTaz 4.0 startet via grub4dos has no problems to copy those 5 GB with pcmanfm 0.5.2.
Offline
I can't get such bug. Can you please test latest livecd with some other GUI file manager installed: pcmanfm-legacy, thunar, caja or spacefm.
Offline
Hi az_ua,
copying those 5 GB using latest slitaz-rolling.iso of 2016-01-23 I get this freezing error with
pcmanfm, thunar and caja. But everything is OK with pcmanfm-legacy, spacefm and mc.
Copying those 5 GB using old slitaz-rolling.iso of 2015-08-23 everything is OK with pcmanfm, pcmanfm-legacy, thunar, spacefm and mc. I wasn't able to install caja on this old version.
All test were made on the same machine using a 400 GB ntfs partition on a build in SSD harddisk.
Testing slitaz-rolling of 2015-11-18 I also got the error copying those 5 GB with pcmanfm.
I am trying to find out, which version was the last good one for me.
Offline
Hi az_ua,
I found out, that old livecd slitaz-rolling.iso of 2015-08-23 booting via grub4dos was the last good one for me to copy those 5 GB with pcmanfm without error, because using the iso from 2015-08-30 I get the freeze. Should I test on a different machine or a different file system?
Offline
For latest rolling:
> everything is OK with pcmanfm-legacy, spacefm and mc.
> freezing error with pcmanfm, thunar and caja.
"pcmanfm, thunar and caja" - what is common for these fm? - "gvfs". Try " [c]tazpkg remove gvfs-fuse[/c] " before.
> slitaz-rolling.iso of 2015-08-23 everything is OK with pcmanfm
If there is no mistake in date, this is first version with 3.2.71 so it's not kernel bug.
> Should I test on a different machine or a different file system?
> using the iso from 2015-08-30 I get the freeze
Please test 2015-08-23 again and again to be sure that it's latest good version.
If you are sure - here may be source of trouble:
slitaz-boot-scripts
> init: /run is moved
> init: partitonless support
> init: log device creation
Offline
If this is boot-scripts bug, latest iso with old boot-scripts should not freeze.
# wget ftp://ftp.rz.uni-kiel.de/pub2/linux/slitaz/packages/cooking/slitaz-boot-scripts-409.tazpkg
# tazpkg -i slitaz-boot-scripts-409.tazpkg --forced
# tazlito writeiso
If this is "gvfs-fuse" package bug I forgot to tell about " [c]killall gvfsd-fuse[/c] " after removing this package and before testing.
I have no more no suggest. Maybe some special ssd kernel module?
Offline
Hi az_ua,
as You said I testet 2015-08-23 again and again, but unfortunately I found out, that it wasn't the last good version. The last good version was SliTaz 5.0 RC2, which I testet three times successfully copying 5 GB with pcmanfm. The error is already in SliTaz 5.0 RC3, which I also testet three times.
Removing the the gvfs-fuse package from latest slitaz-rolling of 2016-01-23 together with killall gvfsd-fuse didm't stop the freeze. Unfortunately the latest slitaz-rolling.iso with old boot-scripts was freezing too. Copying the 5 GB with latest slitaz-rolling.iso pcmanfm from a magnetic USB-harddisk to itself also produced the error.
Latest slitaz-rolling-core64.iso of 2016-01-24 worked fine. Its pcmanfm copied the whole 5 GB without freezing, which I testet three times.
Thank You for Your support. Any hints will be welcome. Maybe You know, which differences between latest slitaz-rolling.iso amd latest slitaz-rolling-core64.iso can explain, why the pcmanfm of the first shows the error and the pcmanfm of the second doesn't show it?
Offline
Maybe You know, which differences between latest slitaz-rolling.iso and latest slitaz-rolling-core64.iso
It's clear - no enough RAM, if your system has more than 3Gb RAM, only core64 can use all RAM.
When file reads on ntfs - file stay in Ram ~ for a hour, you can see this in "htop" scale. It's not slitaz-only issue. Just don't use ntfs under linux when possible.
> last good version was SliTaz 5.0 RC2
ntfs-3g was recompiled with internal fuse between RC2 and RC3. You can test repacked ntfs-3g from rc2, if not so bored, we never know.
Swap does matters too. Better to disable it, use "linux-zram".
Offline
Hi az_ua,
thank You for You hints and support. Using the repacked ntfs-3g from rc2 unfortunately did not work.
Further testing shows to me, that the freeze error happens while copying those 5 GB with pcmanfm to a ntfs partition only, but not to a Linux partition. The error exist in slitaz-rolling.iso but not in slitaz-rolling-core64.iso including the latest version of 2016-01-30 / 2016-01-31. With last weeks slitaz-rolling-core64.iso I copied yesterday 74 GB from ntsf to ntfs without any error.
The last good one was precisely slitaz-rollling of 2014-07-06. The version of 2014-07-13 was not usable and version of 2014-07-16 already shows the freeze error. Between 2014-07-06 and 2014-07-16 pcmanfm had the same version, but libfm was split into libfm and libfm-gtk.Among other packages gtk+ was updated and menu-cache was updated from 0.3.2 to 0.5.1. Since 2014-07-16 the package gamin isn't anymore in the isos, but it seems to be not responsible for the error. The updated libgio seems to be also not responsible for the error.
Thinking not having to disable swap on a live CD, I installed linux-zram, but I still get the freeze error while copying those 5 GB of all SliTaz 5.0 packages to a ntfs partition with pcmanfm of latest slitaz-rolling.iso
Offline
[ Generated in 0.018 seconds, 7 queries executed - Memory usage: 1.55 MiB (Peak: 1.77 MiB) ]