TeXworks not saving conf in proot, migrated from Termux issues about termuxarch HOT 10 CLOSED

Thank you for contributing to make this project better😎 Keep up and follow to solve this issue.

from termuxarch.

Hi -

Got the invitation to join TermuxArch, but Imust decline it. I do not know how to program (only simply BASH scripts), and I do not have the Android SDK. Thanks, anyway.

from termuxarch.

Hello,

the invitation to join

Thank you anyway, and you are welcome @cargocultprog

how to program (only simply BASH scripts)

How to program BASH scripts is one of a few reasons I am working on this project. TeXworks is also available through yay:

$ yay TeXworks
1 community/texworks 0.6.5-3 (2.2 MiB 5.6 MiB)
    Unicode-based, TeX-aware editor with integrated PDF viewer
==> Packages to install (eg: 1 2 3, 1-3 or ^4)
==> 1
resolving dependencies...
:: There are 5 providers available for libgl:
:: Repository extra
   1) libglvnd
:: Repository alarm
   2) imx-gpu-viv-dfb  3) imx-gpu-viv-fb  4) imx-gpu-viv-wl  5) imx-gpu-viv-x11

Enter a number (default=1):
looking for conflicting packages...
warning: dependency cycle detected:
warning: harfbuzz will be installed before its freetype2 dependency
warning: dependency cycle detected:
warning: mesa will be installed before its libglvnd dependency

Packages (72) avahi-0.8+15+ge8a3dd0-1  cairo-1.17.2+25+gaee96d175-1
              double-conversion-3.1.5-2  fontconfig-2:2.13.91+48+gfcb0420-2
              freetype2-2.10.2-1  graphite-1:1.3.14-1  harfbuzz-2.7.1-1
              hunspell-1.7.0-3  lcms2-2.11-2  libcups-2.3.3-2  libdaemon-0.14-5
              libdrm-2.4.102-1  libevdev-1.9.1-1  libglvnd-1.3.2-1  libgudev-233-2
              libice-1.0.10-3  libinput-1.15.6-1  libjpeg-turbo-2.0.5-1
              libomxil-bellagio-0.9.3-3  libpciaccess-0.16-2  libpng-1.6.37-3
              libproxy-0.4.15+33+g454a499-2  libsm-1.2.3-2  libsynctex-2020.54586-4
              libtiff-4.1.0-2  libunwind-1.3.1-2  libwacom-1.4.1-1  libx11-1.6.11-1
              libxau-1.0.9-3  libxcb-1.14-1  libxdamage-1.1.5-3  libxdmcp-1.1.3-3
              libxext-1.3.4-3  libxfixes-5.0.3-4  libxi-1.7.10-3  libxkbcommon-0.10.0-1
              libxkbcommon-x11-0.10.0-1  libxmu-1.1.3-2  libxrender-0.9.10-4
              libxshmfence-1.3-2  libxt-1.2.0-2  libxxf86vm-1.1.4-4  llvm-libs-10.0.1-1
              lm_sensors-3.6.0-2  lzo-2.10-3  md4c-0.4.4-1  mesa-20.1.6-1
              mtdev-1.1.6-1  nspr-4.27-1  nss-3.55-2  openjpeg2-2.3.1-2
              pixman-0.40.0-1  poppler-0.90.1-1  poppler-qt5-0.90.1-1
              qt5-base-5.15.0-4  qt5-script-5.15.0-1  shared-mime-info-2.0+1+g6bf9e4f-2
              tslib-1.22-1  vulkan-icd-loader-1.2.148-1  wayland-1.18.0-2
              xcb-proto-1.14-1  xcb-util-0.4.0-3  xcb-util-image-0.4.0-3
              xcb-util-keysyms-0.4.0-3  xcb-util-renderutil-0.3.9-3
              xcb-util-wm-0.4.1-3  xdg-utils-1.1.3+19+g9816ebb-1
              xkeyboard-config-2.30-2  xorg-xprop-1.2.4-2  xorg-xset-1.2.4-2
              xorgproto-2020.1-1  texworks-0.6.5-3

Total Download Size:    56.44 MiB
Total Installed Size:  273.19 MiB

:: Proceed with installation? [Y/n]

I do not have the Android SDK.

The Android SDK is unnecessary for these projects. Do you know a good TeXworks primer?

from termuxarch.

can read, but not write or modify, its configuration file at ~/.config/TUG/TeXworks.conf.

chown: changing ownership of '/home/xd003/.cache/yay/heroku-cli/pkg/heroku-cli/usr/lib/node_modules/heroku/node_modules/treeify/examples/eukaryotes.js': Operation not permitted chown

The way permissions are configured has been revised; Hopefully this change will have a positive effect on our devices and heroku-cli will build for you as expected.

In this issue's case, this revision concerns TeXworks. The underlying cause of both these issues might be the same, file and directory permissions. File and directory permissions are revised. @cargocultprog can you check if TeXworks runs is expected with this new change please?

Executing setupTermuxArch re should be enough to update this change on your device. The command setupTermuxArch h[elp] has more information about system refresh options.

from termuxarch.

I use only the Arch version, not the yay build, so I cannot advise.

from termuxarch.

use only the Arch version

My last question was not about building TeXworks with ayay. Please let me elaborate so I will be a little clearer.

File and directory permissions are revised.

Executing setupTermuxArch re should be enough to update this change on your device.

TeXworks functions correctly, with exception: It can read, but not write or modify, its configuration file at ~/.config/TUG/TeXworks.conf

Does this new change in the file and directory permissions scheme have an effect on the file that we are discussing?

from termuxarch.

Numerous iterations, and at that nuance iterations requiring time consuming testing have given positive results. This commit and the preceding few have helped to make script makefakeroottcp and more importantly script makeyay functional again once more.

From SDRausty/TermuxArch#251 (comment)_, this has rewritten permissions through the PRoot init statement for the user accounts.

This means that the file you referenced that did not work might possibly work correctly in the PRoot environment on Android now! If you missed the updates in the last couple of days @cargocultprog, the simple setupTermuxArch re should update your system correctly.

Creating a new user account after refreshing to test TeXwork is advised as file permissions at creation is affected. If you are installing a new system, creating a new user account is unnecessary as a default user account with the name user will be created for you.

This is a subtle change which yields radical results for the better as far as I can tell. There have also been other subtle changes that fix permissions in the last week, a reinstallation of the system might be justified to fully test new changes. Please remember to backup your data from your user accounts before reinstalling.

from termuxarch.

In my case, not a permissions issue. I installed via my own script, and have full permissions. The problem sems to be have something to do with qt5, which does have some issues in proot and Termux. But this issue should be dropped. The user base is very small, and the configuraion file is easily edited manually. I do not have enough device space to do a test reinstall.

from termuxarch.

In my case, not a permissions issue.

It is great to hear that you got this issue resolved.

@cargocultprog thank you for replying so quickly.

I installed via my own script, and have full permissions.

Would you be apt to share this script at this webpage please?
https://github.com/TermuxArch/scripts.TermuxArch/pulls
The process is almost as simple as opening an issue:
a) Fork Repository
b) Make changes, in this case, an addition, a new file
c) Create PR

I do not have enough device space to do a test reinstall.

Enough device space makes me think of this issue:

#3 Can PRoot be used to access a Linux distribution from external storage such as an SD card?

Possibly, this topic should be revisited. What is your opinion? Do you have room in external SD card storage?

from termuxarch.

No, my method is not a modification of termuxArch. It is entirely different. A pull request cannot help. I only mentioned it here, because I thought it might affect your script. It is best to drop the issue. I may be the only person in the world using texworks on Android proot.

As for an SDcard, it would have to be formatted ext4 (or similar) for POSIX file permissions. Even then, it might not work. Most users cannot format to ext4, because Android will not allow it except for rooters. Not everyone has access to a desktop Linux or Mac machine (I do not).

from termuxarch.