WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Something weird happens in piCore64 (aarch64)  (Read 3142 times)

Offline mortegai

  • Jr. Member
  • **
  • Posts: 55
Something weird happens in piCore64 (aarch64)
« on: November 03, 2020, 04:11:38 AM »
When trying to access (e.g. to open a file) to the /tmp/tcloop directory with any application (firefox, leafpad, ...)  the error occurs:
Code: [Select]
Could not read the contents of tcloop.
Error when getting information for file "xxxxxxx". Numerical result out of range.
This does not happen in piCore (armv7)

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14849
Re: Something weird happens in piCore64 (aarch64)
« Reply #1 on: November 03, 2020, 04:20:46 AM »
Hmm - I'm able to open a file under /tmp/tcloop with beaver and emelfm, but not firefox..

Offline mortegai

  • Jr. Member
  • **
  • Posts: 55
Re: Something weird happens in piCore64 (aarch64)
« Reply #2 on: November 03, 2020, 04:45:51 AM »
beaver and emelfm are gtk1.
leafpad and firefox are gtk2/gtk3 applications.
...?

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14849
Re: Something weird happens in piCore64 (aarch64)
« Reply #3 on: November 03, 2020, 04:55:48 AM »
..and the same problem occurs with firefox in wayland/weston.

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11695
Re: Something weird happens in piCore64 (aarch64)
« Reply #4 on: November 03, 2020, 08:01:45 AM »
Hi Juanito
There recently was some talk about a very large block size being used by squashfs tools instead of 4096. Maybe related?
If I remember correctly, it only affected aarch64.

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11695
Re: Something weird happens in piCore64 (aarch64)
« Reply #5 on: November 03, 2020, 09:20:38 AM »
Hi Juanito
beaver and emelfm are gtk1.
leafpad and firefox are gtk2/gtk3 applications.
GTK1 uses glib1, GTK2 and 3 use glib2. I found this for glib 2.65.2 which is what aarch64 uses:
https://gitlab.gnome.org/GNOME/glib/-/issues/2189

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11695
Re: Something weird happens in piCore64 (aarch64)
« Reply #6 on: November 03, 2020, 09:25:59 AM »
Hi mortegai
...
Code: [Select]
Could not read the contents of tcloop.
Error when getting information for file "xxxxxxx". Numerical result out of range.
...
Is that the exact error message? When I say exact, I mean word for word, punctuation, uppercase/lowercase, etc.

Offline mortegai

  • Jr. Member
  • **
  • Posts: 55
Re: Something weird happens in piCore64 (aarch64)
« Reply #7 on: November 03, 2020, 09:53:41 AM »
Yes, that is the exact message. Juanito can confirm it.
The xxxxxxx varies in different boots.

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11695
Re: Something weird happens in piCore64 (aarch64)
« Reply #8 on: November 03, 2020, 09:58:38 AM »
Hi mortegai
OK, so the  "xxxxxxx "  is just a file name?

Offline mortegai

  • Jr. Member
  • **
  • Posts: 55
Re: Something weird happens in piCore64 (aarch64)
« Reply #9 on: November 03, 2020, 10:04:42 AM »
That's !
e.g.: /tmp/tcloop/graphics-5.4.51-piCore-v8

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14849
Re: Something weird happens in piCore64 (aarch64)
« Reply #10 on: November 03, 2020, 10:18:45 AM »
glib-2.66.2 fixes it - I'll upload shortly.

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14849
Re: Something weird happens in piCore64 (aarch64)
« Reply #11 on: November 03, 2020, 10:29:19 AM »
uploaded - well spotted Rich

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11695
Re: Something weird happens in piCore64 (aarch64)
« Reply #12 on: November 03, 2020, 10:31:54 AM »
Hi Juanito
... well spotted Rich
Thanks. I did the easy part, you had to fix it. ;D

Offline mortegai

  • Jr. Member
  • **
  • Posts: 55
Re: Something weird happens in piCore64 (aarch64)
« Reply #13 on: November 03, 2020, 10:41:28 AM »
Confirmed, now it works properly. 
Thank you very much to both.