Re: Various X problems
Le 14/08/2018 à 22:10, Samuel Thibault a écrit :
> MENGUAL Jean-Philippe, le sam. 11 août 2018 13:18:22 +0200, a ecrit:
>> When I use the cut-and-paste command of brltty, it works all right, but
>> randomly and for whatever reason, X crashes. I pasted the log here:
> Do you see any pattern in which strings could be making X crash? From
> looking at the backtrace (ProcXkbSetMap calling _XkbSetMapChecks), it
> would be when pasting characters which are not directly available in the
> key layout, e.g. ê, could that match what you get?
Yes, I have just done a new trial, it is a reproducible case. If the
pasted string contains an accent, X crashes. I think your piont is what
a searched, a good repro scenario.
Should I open a bug in X? What component?
>> Ih this log, several things make me surprised:
>> - the log is polluted by (EE) related to offsetting. What is this? If related
> I don't think it is related.
>> should I report to Debian so that we disable PageFlip by default?
> PageFlip is an important optimization, we don't want to disable it by
ok as it is not related to the crash, let's skip this.
>> Finally, maybe it is related, I use this script to make my screen black and my
>> screen no longer becomes black. More precisely, to make it black, after running
>> the script, I have to do alt-ctrl-f1 and alt-f7.
>> See the script: http://paste.debian.net/1037524
> That's odd. Perhaps you can send the output of xrandr (without option)
> before and after calling the script to have a better idea of what
Before script: http://paste.debian.net/1037969
After the script: http://paste.debian.net/1037970
After alt-ctrl-f1 then alt-f7 (black screen):
Note that when screen is black, when I re-run the script, the screen
becomes lighted immediately.
>> - should I report a bug and where? I planned to do on Xorg, but last time I had
>> no feedback on Debian bts. And upstream requested things I did not know to do
>> in Debian.
> The Debian Xorg staff is terribly understaffed indeed. But I can
> probably write a little program that reproduces brltty's behavior that
> upstream can use to reproduce the issue.
Many thanks. It would be easier than explaining the situation related to
brltty. We will need to do, but with a program it will me more
understandable for upstream.