I agree with Norbert. Bugs like this which involve proprietary
hardware are quite common and unlikely to get attention from those
developers who could fix them. They often get fixed more by accident.
If you want to increase the chances, this is what you could do:
* Compile the most recent kernel
Processing control commands:
> severity -1 normal
Bug #983034 [plasma-workspace-wayland] plasma-workspace-wayland: hanging in
ksplashqml
Severity set to 'normal' from 'grave'
--
983034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983034
Debian Bug Tracking System
Contact ow...@bugs.debian
> dmesg shows a crash in the nouveau driver:
Well ... that is not something we can care for, so I suggest closing
this bug.
Best
Norbert
--
PREINING Norbert https://www.preining.info
Fujitsu Research Labs + IFMGA Guide + TU Wien + TeX Live + Debian Dev
GPG: 0x860C
Control: severity -1 normal
Change severity - nothing we can really deal with
> dmesg shows a crash in the nouveau driver:
Best
Norbert
--
PREINING Norbert https://www.preining.info
Fujitsu Research Labs + IFMGA Guide + TU Wien + TeX Live + Debian Dev
GPG: 0x860C
On 19.02.21 19:40, Dennis Filder wrote:
> Control: tag -1 + moreinfo bullseye sid
>
> If you cannot switch to console with Ctrl-Alt-F2 then this is a strong
> indicator that the bug is in the kernel, probably nouveau.
>
> If you can reproduce this reliably it would help a lot if you could
> provide
Control: tag -1 + moreinfo bullseye sid
If you cannot switch to console with Ctrl-Alt-F2 then this is a strong
indicator that the bug is in the kernel, probably nouveau.
If you can reproduce this reliably it would help a lot if you could
provide the output of these commands after the bug has happ
Package: plasma-workspace-wayland
Version: 4:5.20.5-3
Severity: grave
Dear Maintainer,
from SDDM I try to start a Wayland KDE session.
The whole GUI freezes.
CTRL-ALT-FN2 cannot be used to open a terminal session.
SSH login is still possible.
Top reports 100 % CPU load for ksplashqml.
Mainboa
7 matches
Mail list logo
