Processing control commands:
> severity -1 important
Bug #1024438 [src:mutter] mutter: autopkgtest regression: segfault in
workspace-basic.metatest
Severity set to 'important' from 'serious'
--
1024438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024438
Debian Bug Tracking System
Contact
Control: severity -1 important
On Sun, 18 Dec 2022 at 15:58:06 +, Simon McVittie wrote:
> It looks as though the specific test-case that is segfaulting is
> consistently the one after stacking/unmaximize-new-size.metatest, which
> should be stacking/workspace-basic.metatest. That's consistent
Am 18.12.22 um 16:58 schrieb Simon McVittie:
I was unable to reproduce this in a test VM, ...
..., but it is reproducible
on my laptop. Perhaps it's only reproducible if mutter has access to
some resource that my ssh login session to my test VM lacks, or perhaps
there's a race condition that mak
Processing control commands:
> retitle -1 mutter: autopkgtest regression: segfault in
> workspace-basic.metatest
Bug #1024438 [src:mutter] mutter: autopkgtest regression: Segmentation fault
Changed Bug title to 'mutter: autopkgtest regression: segfault in
workspace-basic.metatest' from 'mutter:
Control: retitle -1 mutter: autopkgtest regression: segfault in
workspace-basic.metatest
Control: forwarded -1 https://gitlab.gnome.org/GNOME/mutter/-/issues/2559
It looks as though the specific test-case that is segfaulting is
consistently the one after stacking/unmaximize-new-size.metatest, whi
5 matches
Mail list logo
