Recent Posts

21

TCE Bugs / Re: blueman.tcz needs specific python3 version

« Last post by Juanito on February 13, 2026, 02:36:39 PM »

That’s not a bad idea - I’ll have a look in the next couple of days.

22

TCE Bugs / Re: blueman.tcz needs specific python3 version

« Last post by GNUser on February 13, 2026, 02:35:11 PM »

What do you think of the idea of using a more specific shebang? In the specific case of blueman.tcz, I'm suggesting replacing all occurrences of #!/usr/local/bin/python3 with #!/usr/local/bin/python3.9

EDIT: Let me test this idea and see if it works (to make sure there is no unexpected breakage if I leave /usr/local/bin/python3 pointing to /usr/local/bin/python3.14)

23

TCE Bugs / Re: blueman.tcz needs specific python3 version

« Last post by Juanito on February 13, 2026, 02:28:41 PM »

I’ve been wondering for a while how to deal with this

24

Raspberry Pi / Re: ' The Lumi H5P Desktop Editor'

« Last post by Juanito on February 13, 2026, 02:25:32 PM »

On ARM64, they simply don’t exist."

If you are speaking of the piCore64 16.x repo, most, if not all of those exist.

25

TCE Bugs / Re: nginx log path ---core x86 16.x

« Last post by Rich on February 13, 2026, 01:27:28 PM »

Hi andyj
Could it be this part from  nginx -V:

Code: [Select]

--http-log-path=/var/log/nginx
I saw it configured in a build tutorial as:

Code: [Select]

--http-log-path=/var/log/nginx/access.log

26

Raspberry Pi / ' The Lumi H5P Desktop Editor'

« Last post by geev03 on February 13, 2026, 12:56:55 PM »

🧠 Why TinyCore x86_64 can run Lumi (but ARM64 cannot)
TinyCore x86_64 has:

full Mesa + GBM
full DRM/KMS stack
complete GTK3
complete X11 libraries
Electron‑compatible sandboxing
working FUSE (for AppImage)
working debootstrap + gnutar + proot (if needed)
full glibc build environment
TinyCore ARM64 (PiCore) is missing all of these.

Electron apps like Lumi depend heavily on:

libgbm.so.1
libdrm.so.2
libxkbcommon.so.0
libnss3.so
libasound.so.2
GTK3
X11 composite/damage/randr
On x86_64, TinyCore ships all of them as .tcz extensions.

On ARM64, they simply don’t exist."

27

TCE Bugs / blueman.tcz needs specific python3 version

« Last post by GNUser on February 13, 2026, 12:44:33 PM »

I'm running blueman.tcz in TCL17 x86_64.

blueman.tcz depends on py3.9gobject.tcz. If /usr/local/bin/python3 is a symlink to python3.14 (or any python3 version other than 3.9) then blueman doesn't work because the modules it needs are located in /usr/local/lib/python3.9/site-packages/blueman:

Code: [Select]

$ blueman-applet &
eileen@blaptop:~$ Traceback (most recent call last):
  File "/usr/local/bin/blueman-applet", line 15, in <module>
    from blueman.Functions import create_logger, create_parser, set_proc_title
ModuleNotFoundError: No module named 'blueman'

$ tce-status -i | grep python
python3.14
python3.9
python3.9-olefile
python3.9-pillow

$ sudo ln -sf /usr/local/bin/python3.9 /usr/local/bin/python3

$ blueman-applet &
-> now it works
I've encountered this problem of /usr/local/bin/python3 not pointing to the expected python3 version several times before: Sometimes when using extensions, sometimes when building extensions.

I thought about different ways to prevent this kind of problem. One idea is to use a startup script (/usr/local/tce.installed/blueman in this case) that forces /usr/local/bin/python3 to point to the expected python3 version. This approach is risky because it would break applications that need a different python3 version.

Maybe the best solution would be for those python3 applications that depend on a specific python3 version to have a more specific shebang? So in blueman.tcz, for example, the python scripts would have  #!/usr/local/bin/python3.9  shebang rather than  #!/usr/local/bin/python3? That's the best solution I can think of at the moment.

28

TCE Bugs / Re: nginx log path ---core x86 16.x

« Last post by Rich on February 13, 2026, 10:50:32 AM »

Hi andyj
I ran through it again and can confirm Zhes findings.

Start with a clean  /var/log  directory:

Code: [Select]

tc@box:~$ ls -l /var/log
total 208
-rw-r--r--    1 root     staff        58837 Feb 13 10:09 Xorg.0.log
-rw-r--r--    1 root     root             0 Feb 13 10:09 autologin
-rw-r--r--    1 root     root        147372 Feb 13 10:09 messages
-rw-rw-r--    1 root     staff         1536 Feb 13 10:09 wtmp
Load nginx:

Code: [Select]

tc@box:~$ tce-load -i nginx
nginx.tcz: OK
The  /var/log/nginx  directory is part of the nginx.tcz file structure:

Code: [Select]

tc@box:~$ ls -l /var/log
total 212
-rw-r--r--    1 root     staff        58837 Feb 13 10:09 Xorg.0.log
-rw-r--r--    1 root     root             0 Feb 13 10:09 autologin
-rw-r--r--    1 root     root        148146 Feb 13 10:12 messages
drwxr-xr-x    2 root     root            40 Dec 12 02:09 nginx/
-rw-rw-r--    1 root     staff         1536 Feb 13 10:09 wtmp
/var/log/nginx is empty:

Code: [Select]

tc@box:~$ ls -l /var/log/nginx
total 0
Version and configure options:

Code: [Select]

tc@box:~$ nginx -V
nginx version: nginx/1.29.4
built by gcc 14.2.0 (GCC)
built with OpenSSL 3.5.2 5 Aug 2025
TLS SNI support enabled
configure arguments: --prefix=/usr/local --sbin-path=/usr/local/sbin/nginx --modules-path=/usr/local/lib/nginx/modules --conf-path=/usr/local/etc/nginx/nginx.conf --error-log-path=/var/log/nginx/error.log --pid-path=/var/run/nginx.pid --lock-path=/tmp/nginx/lock --user=nobody --group=nogroup --with-threads --with-file-aio --with-compat --with-http_ssl_module --with-http_v2_module --with-http_realip_module --with-http_addition_module --with-http_xslt_module=dynamic --with-http_image_filter_module=dynamic --with-http_sub_module --with-http_dav_module --with-http_flv_module --with-http_mp4_module --with-http_gunzip_module --with-http_gzip_static_module --with-http_auth_request_module --with-http_random_index_module --with-http_secure_link_module --with-http_degradation_module --with-http_slice_module --with-http_stub_status_module --http-log-path=/var/log/nginx --http-client-body-temp-path=/tmp/nginx/client --http-proxy-temp-path=/tmp/nginx/proxy --http-fastcgi-temp-path=/tmp/nginx/fastcgi --http-uwsgi-temp-path=/tmp/nginx/uwsgi --http-scgi-temp-path=/tmp/nginx/scgi --with-mail=dynamic --with-mail_ssl_module --with-stream=dynamic --with-stream_ssl_module --with-stream_realip_module --with-stream_ssl_preread_module
Copy all of the .default files to the nginx config directory:

Code: [Select]

tc@box:~$ sudo cp /usr/local/etc/nginx/original/*.default /usr/local/etc/nginx/
Strip the  .default  extension from those files:

Code: [Select]

tc@box:~$ for F in /usr/local/etc/nginx/*.default; do sudo mv -- "$F" "${F%.default}"; done
Try to start nginx:

Code: [Select]

tc@box:~$ sudo nginx
nginx: [emerg] open() "/var/log/nginx" failed (21: Is a directory)
One slight twist. The file was written:

Code: [Select]

tc@box:~$ ls -l /var/log/nginx
total 4
-rw-r--r--    1 root     root            91 Feb 13 10:33 error.log
tc@box:~$ cat /var/log/nginx/error.log
2026/02/13 10:33:54 [emerg] 3920#3920: open() "/var/log/nginx" failed (21: Is a directory)

29

Raspberry Pi / Re: Wayland on piCore

« Last post by Juanito on February 13, 2026, 10:19:18 AM »

Added the labwc-config extension that will load labwc and a basic tinycore desktop.

30

Micro Core / Re: AMD XDNA device driver is missing

« Last post by Juanito on February 13, 2026, 10:08:52 AM »

I built amdxdna - it took 3h15m on my ancient laptop - see http://tinycorelinux.net/17.x/x86_64/release/src/kernel/amdxdna/

Boot bzImage instead of vmlinuz64 and then:

Copy the module to /usr/local/lib/modules/6.18.2-tinycore64/kernel/drivers/accel or similar
"sudo depmod -a"
Load graphics-KERNEL if not already loaded
"sudo modprobe amdxdna"