Porteus

Could someone please help me build the reportedly best (?) tool for searching in files: Recoll https://www.lesbonscomptes.com/recoll/index.html . The old version found on USM is old and relies on Qt4. I have (a subset of, through https://forum.porteus.org/viewtopic.php?t=7799 ) Qt5 on my Porteus 4.0...

dear jssouza , hope you're still around and thank you again for the modules. I'm now trying to use a recoll package (https://altlinux.pkgs.org/sisyphus/classic-x86_64/recoll-1.27.3-alt1.x86_64.rpm.html) and it requires Qt5WebKitWidgets (at least, maybe some others). None of your modules contain thos...

ncmprhnsbl , thanks, I used your link and txz2xzm glibc-2.30. Activated the module. Waterfox runs well and no other programs have broken so far, although I suspect I essentially updated (some parts of) the system GLIBC. If something fails I can always deactivate the glibc-2.30-x86_64-1.xzm and try ...

Apparently I need the new GLIBC_2.30 on my Porteus 4, see the error below when I try to run Waterfox Classic. I think the system glic is 2.27. And I hope I don't have to replace it as it could break other things. Or is it okay to replace? Can I put it next to the waterfox binary so that it picks it ...

Kulle , for me it's always (twice so far) a consequence of improper shutdown it seems. (And my USB has 2 partitions to complicate things, the 1st is NTFS). So I have another (porteus) USB to boot into, then plug the problematic one (say, /dev/sdc), unmount and run: e2fsck -vf /dev/sdc2 and similarl...

After trying the GIMP module gimp-2.10.6+deps-x86_64-kde-lx-xfce-ob-stripped.xzm, on loading a very large image, my whole Porteus 4.0 64 OpenBox system was frozen, no keyboard even, so I had to restart the computer by long pressing PowerOff button. Now every time I boot (with an additional fsck chea...

Yes, Ed_P , I've read and done those I believe. Except I didn't use the Porteus Installer GUI. I used command line tools. If someone could find an error in my procedure I'd be most grateful. I can now add another UPDATE: On the first machine, in the same BIOS GUI as in snapshots above, I can actuall...

1. I followed https://youtu.be/Q_AXMoaRmdQ to partition and format my USB as follows: root@porteus:~# gdisk /dev/sdc GPT fdisk (gdisk) version 1.0.3 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Command (? for hel...

By the way, what's the minimum size for the first FAT32 partition for the porteus EFI? 100MB, 200, 300, 350MB?

I've installed those two packages. SpaceFM didn't pick it up when I plugged the phone. So I tried to do something manually: root@porteus:~# mkdir /mnt/A root@porteus:~# jmtpfs /mnt/A Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). At this stage I was asked for additional permissio...

Thanks, ncmprhnsbl . SpaceFM indeed has an interesting script in >devices>settings>protocol handlers>mtp with the following comment: "To mount mtp:// you must install jmtpfs, simple-mtpfs, mtpfs, or go-mtpfs, or add a custom protocol handler." Perhaps I should try to install one of the "jmtpfs, simp...

Can't connect my Samsung Galaxy A3 2017 to Porteus 4.0: no new disk in the SpaceFM, and a long error message on the smartphone saying Attention The connected device is unable to access data on this device ... and so on mentioning Android File Transfer for Mac OS X. There is a Android File Transfer f...

Thank you, jssouza : I was unsuccessful in trying to convert the packages to the modules, complaining that some files were missing. I don't think it's worth instigating in light of the upcoming Porteus 5 that will have it natively. I'm likely to stay on OpenBox even in Porteus 5, so I'd be needing a...

@jssouza, Thank you for these Qt packages that has enabled my work for all this time. I wonder whether you could easily upgrade it to the next version. The reason for me is that I'd like to upgrade some of my apps which begin to rely on the newer Qt, for example, the next version of qpdfview, `qpdfv...

I can't find the script setting "TERM=xterm-256color" on my system. And it seems to break wine related programs (complains: 'xterm-256color': unknown terminal type.) Setting it back to TERM=xterm seems to solve it. I say "back to" because on my previous USB with LXDE it is indeed TERM=xterm -- I've ...