>> > Hi, that was all good advice. I'd add that before making a bug report,
>> > I'd suggest checking something like:
>> >
>> > $ sudo journalctl -b -g 'not supported'
>> >
>> > because if the GPU driver is reporting that certain graphics capabilities
>> > are not supported, then the bug would be in the software that attempts
>> > to use those capabilities when they aren't available.
>> 
>> If it crashes the whole OS, the bug is not just in the application but
>> further down (somewhere in the stack, as described by the Wanderer).
>
> Usually, but not always, I can ssh in, send a few signals to some
> applications and then type 'poweroff'.

Aha: I assumed "crashes Trixie" means the whole OS crashed.

If you can still access the machine via SSH, then presumably only the
video part is wedged.  Still: if the whole user session is made unusable
and the graphics stack is sufficiently confused that you can't "log out and
log back in" (as seems to be the case based on your description), then
the problem is not just in the application but somewhere within the
graphics stack.


=== Stefan

Reply via email to