[Desktop-packages] [Bug 2058409] Re: Install of tevlive-full hangs: tex/context/base/mkiv/l-sandbox.lua:180: module 'socket.core' not found
The postinstall runs fails because luatex now has the 'socket' functionality disabled by default. [CVE-2023-32668] The upstream source for mtxrun has --socket added to the luatex command line to reenable the functionality while running 'mtxrun --make'. See lines having '--socket' in https://source.contextgarden.net/mtxrun.lua I think that there are two bugs here: 1) The mismatch between luatex and context regarding --socket, and 2) The post-install hangs indefinitely rather than returning an error. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-32668 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/2058409 Title: Install of tevlive-full hangs: tex/context/base/mkiv/l-sandbox.lua:180: module 'socket.core' not found Status in texlive-base package in Ubuntu: Confirmed Bug description: Before 3 weeks at least it was possible to install texlive-full without any issues. Now this is not possible anymore. So the bug was probably introduced with one of the latest updates. How to reproduce: Install package texlive-full $ apt install texlive-full Install hangs: texlive-lang-japanese (2021.20220204-1) wird eingerichtet ... context (2021.03.05.20220211-1) wird eingerichtet ... Running mtxrun --generate. This may take some time... done. Pregenerating ConTeXt MarkIV format. This may take some time... Related running processes: root 18747 0.4 0.0 13936 7456 pts/2Ss+ 17:47 0:01 /usr/bin/dpkg --status-fd 43 --configure --pending root 20584 0.0 0.0 2892 960 pts/2S+ 17:48 0:00 /bin/sh /var/lib/dpkg/info/context.postinst configure root 20592 0.0 0.0 2892 1064 pts/2S+ 17:48 0:00 /bin/sh /usr/bin/luatools --make cont-en root 20593 0.1 0.9 92868 79952 pts/2S+ 17:48 0:00 texlua /usr/bin/mtxrun --script base --make cont-en root 20596 0.0 0.0 2892 1004 pts/2S+ 17:48 0:00 sh -c /usr/bin/luatex --ini --lua=/usr/share/texmf/tex/context/base/mkiv/luat-cod.lua /usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv root 20597 0.0 0.3 40816 28684 pts/2S+ 17:48 0:00 /usr/bin/luatex --ini --lua=/usr/share/texmf/tex/context/base/mkiv/luat-cod.lua /usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv Run luatex manually: # /usr/bin/luatex --ini --lua=/usr/share/texmf/tex/context/base/mkiv/luat-cod.lua /usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv This is LuaTeX, Version 1.14.0 (TeX Live 2022/dev/Debian) (INITEX) system commands enabled. (/usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv (/usr/share/texmf/tex/context/base/mkiv/context.mkiv (/usr/share/texmf/tex/context/base/mkiv/syst-ini.mkiv) (/usr/share/texmf/tex/context/base/mkiv/norm-ctx.mkiv) (/usr/share/texmf/tex/context/base/mkiv/syst-pln.mkiv) (/usr/share/texmf/tex/context/base/mkiv/syst-mes.mkiv) (/usr/share/texmf/tex/context/base/mkiv/luat-cod.mkiv<+ /usr/share/texmf/tex/context/base/mkiv/luat-cod.lua>) (/usr/share/texmf/tex/context/base/mkiv/luat-bas.mkiv loading: ConTeXt Lua Macros / Basic Lua Libraries<+ /usr/share/texmf/tex/context/base/mkiv/l-bit32.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-lua.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-macro.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-sandbox.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-package.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-lpeg.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-function.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-string.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-table.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-boolean.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-number.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-math.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-io.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-os.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-file.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-gzip.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-md5.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-sha.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-dir.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-unicode.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-url.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-set.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-macro-imp-optimize.lua>) (/usr/share/texmf/tex/context/base/mkiv/luat-lib.mkiv loading: ConTeXt Lua Macros / Libraries<+ /usr/share/texmf/tex/context/base/mkiv/util-str.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-tab.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-fil.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-sac.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-sto.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-pck.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-prs.lua><+
[Desktop-packages] [Bug 1740406] [NEW] Login fails with no error message when NFS home directory is over quota
Public bug reported: If a user is over quota, or if the home directory disk is full, they get logged out straight after logging in, when the home directory is on NFS. No information is presented to the user that would let them know the problem. This is because of an error in the way that lightdm writes to the ~/.Xauthority file in src/x-authority.c. It does check that each write() succeeds, but in the NFS case, the data isn't actually written by the client until fsync() is called; the status of that system call isn't checked so the quota problem is undetected. Calling fsync() is not necessary; the effect of committing the data to disk is implied by close(), which is done on the next line anyway. Ubuntu 14.04.5 LTS lightdm 1.10.6-0ubuntu1 ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Patch added: "lightdm-check-close-status.patch" https://bugs.launchpad.net/bugs/1740406/+attachment/5028428/+files/lightdm-check-close-status.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1740406 Title: Login fails with no error message when NFS home directory is over quota Status in lightdm package in Ubuntu: New Bug description: If a user is over quota, or if the home directory disk is full, they get logged out straight after logging in, when the home directory is on NFS. No information is presented to the user that would let them know the problem. This is because of an error in the way that lightdm writes to the ~/.Xauthority file in src/x-authority.c. It does check that each write() succeeds, but in the NFS case, the data isn't actually written by the client until fsync() is called; the status of that system call isn't checked so the quota problem is undetected. Calling fsync() is not necessary; the effect of committing the data to disk is implied by close(), which is done on the next line anyway. Ubuntu 14.04.5 LTS lightdm 1.10.6-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1740406/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
