mkdir ~/.cache should get you get going again until xterm is fixed.
On 6 September 2021 08:41:38 CEST, henkjan gersen wrote:
>That indeed gives much more output, but not sure it gives more clarity
>as it ends with this:
>
>--
>69930 xterm CALL mprotect(0xf4aab8c6000,0x1000,0x3)
>69930 xterm RET
That indeed gives much more output, but not sure it gives more clarity
as it ends with this:
--
69930 xterm CALL mprotect(0xf4aab8c6000,0x1000,0x3)
69930 xterm RET mprotect 0
69930 xterm CALL mprotect(0xf4aab8c6000,0x1000,0x1From the output just before this the only thing that stands out to me
is
It is setgid (privdrop) for utmp support, so ktrace stops reporting on
what the program is doing. If you temporarily chmod your utmp file a+w,
remove the setgid bit from the xterm binary, then you will likely be
able to ktrace further to get closer to identifying the issue.
henkjan gersen
Assuming I should run "ktrace -di xterm" it doesn't show any failure
condition at the end, i.e. the last lines from the kdump are
--
90075 ktrace NAMI "/usr/X11R6/bin/xterm"
90075 ktrace ARGS
[0] = "xterm"
--
To me that last line looks like the process launches successfully, yet
no xterm
henkjan gersen wrote:
> On this mornings snapshot that I just upgraded to I can no longer open
> an xterm window. Based on the .xsession-error this must be related to
> the unveil capabilities that got added last week as I see "xterm:
> unveil" appearing in that file.
>
> Can someone give a
henkjan gersen writes:
> On this mornings snapshot that I just upgraded to I can no longer open
> an xterm window. Based on the .xsession-error this must be related to
> the unveil capabilities that got added last week as I see "xterm:
> unveil" appearing in that file.
>
> Can someone give a
6 matches
Mail list logo
