GNOME Konsol crashes

  • Open
  • quality assurance status badge
Details
3 participants
  • Liliana Marie Prikler
  • Maxim Cournoyer
  • Simon Josefsson
Owner
unassigned
Submitted by
Simon Josefsson
Severity
normal
S
S
Simon Josefsson wrote on 14 Jun 18:34 +0200
(address . bug-guix@gnu.org)
871q4zwkjc.fsf@kaka.sjd.se
Hi.

GNOME Konsol has crashed for me, bringing down all 10+ windows I had
open (and plenty of ongoing work halted...). I've now seen this twice,
so I suppose it counts as reproducible, even though I don't know how to
trigger it. I recall that it happened when I used the mouse to maybe
resize windows or switch workspace somehow.

This is guix v1.3.0-60008-g7e00fb9f31 with a fairly normal system
configuration [1] on a fairly ordinary amd64 desktop (MSI Z790P).
Syslog has these two crashes:

Jun 12 17:53:49 localhost vmunix: [244491.668326] .kgx-real[2161]: segfault at 29 ip 00007fd22dc31d6d sp 00007ffed19f0630 error 6 in crocus_dri.so[7fd22da94000+165b000] likely on CPU 10 (core 20, socket 0)
Jun 12 17:53:49 localhost vmunix: [244491.668348] Code: c0 75 42 48 8b 93 08 1a 00 00 48 8d 8b 08 1a 00 00 49 8d 44 24 08 66 48 0f 6e c9 66 48 0f 6e c2 66 0f 6c c1 41 0f 11 44 24 08 <48> 89 42 08 48 89 83 08 1a 00 00 f0 83 6d 00 01 75 31 5b 5d 41 5c

Jun 13 20:45:36 localhost vmunix: [96351.516581] .kgx-real[2371]: segfault at 8 ip 00007f34fc831d6d sp 00007ffe27647ae0 error 6 in crocus_dri.so[7f34fc694000+165b000] likely on CPU 30 (core 46, socket 0)
Jun 13 20:45:36 localhost vmunix: [96351.516595] Code: c0 75 42 48 8b 93 08 1a 00 00 48 8d 8b 08 1a 00 00 49 8d 44 24 08 66 48 0f 6e c9 66 48 0f 6e c2 66 0f 6c c1 41 0f 11 44 24 08 <48> 89 42 08 48 89 83 08 1a 00 00 f0 83 6d 00 01 75 31 5b 5d 41 5c

Anyone else seeing this? I know it is hard to debug based on this
information...

/Simon

-----BEGIN PGP SIGNATURE-----

iIoEARYIADIWIQSjzJyHC50xCrrUzy9RcisI/kdFogUCZmxxBxQcc2ltb25Aam9z
ZWZzc29uLm9yZwAKCRBRcisI/kdFokUuAP4hYsN3wUqjf6JZfUnGfDkweBHGekTu
WDDeO0P6z/zGiwEAprMiu8b7fPm83O6IRvFZGWsks8Lmb2nOLkBm3SZ6kQk=
=vcU+
-----END PGP SIGNATURE-----

L
L
Liliana Marie Prikler wrote on 21 Jun 06:32 +0200
7b837863a002e3ac2ec06f134eb12dfb7f9ecdc8.camel@gmail.com
Am Freitag, dem 14.06.2024 um 18:34 +0200 schrieb Simon Josefsson:
Toggle quote (11 lines)
> Hi.
>
> GNOME Konsol has crashed for me, bringing down all 10+ windows I had
> open (and plenty of ongoing work halted...).  I've now seen this
> twice, so I suppose it counts as reproducible, even though I don't
> know how to trigger it.  I recall that it happened when I used the
> mouse to maybe resize windows or switch workspace somehow.
>
> This is guix v1.3.0-60008-g7e00fb9f31 with a fairly normal system
> configuration [1] on a fairly ordinary amd64 desktop (MSI Z790P).
> Syslog has these two crashes:
… and a fairly normal GPU?

The crash indicates some driver issue, probably in Mesa. Since GNOME
is increasingly hardware accelerated, you tend to notice them in a lot
of places. You can twiddle the GSK_RENDERER environment variable to
something less buggy, potentially at the cost of performance.
Particularly the cairo one ought to do slow, but correct CPU rendering.


Cheers
S
S
Simon Josefsson wrote on 21 Jun 08:30 +0200
(name . Liliana Marie Prikler)(address . liliana.prikler@gmail.com)(address . 71556@debbugs.gnu.org)
BE683CBF-59C6-4A6F-8EB8-6CD2BD9A060B@josefsson.org
Toggle quote (16 lines)
> 21 juni 2024 kl. 06:32 skrev Liliana Marie Prikler <liliana.prikler@gmail.com>:
>
> ?Am Freitag, dem 14.06.2024 um 18:34 +0200 schrieb Simon Josefsson:
>> Hi.
>>
>> GNOME Konsol has crashed for me, bringing down all 10+ windows I had
>> open (and plenty of ongoing work halted...). I've now seen this
>> twice, so I suppose it counts as reproducible, even though I don't
>> know how to trigger it. I recall that it happened when I used the
>> mouse to maybe resize windows or switch workspace somehow.
>>
>> This is guix v1.3.0-60008-g7e00fb9f31 with a fairly normal system
>> configuration [1] on a fairly ordinary amd64 desktop (MSI Z790P).
>> Syslog has these two crashes:
> … and a fairly normal GPU?

Built-in UHD 770 in the Intel 14900K CPU (no overclocking). I am using Dasharo system firmware if that makes a difference.

I’ve used this system extensively and think some recent update may have introduced it as I started seeing it only recently. Hard to tell though since it only happened after 4+ hours of interactive work each time.

Toggle quote (6 lines)
> The crash indicates some driver issue, probably in Mesa. Since GNOME
> is increasingly hardware accelerated, you tend to notice them in a lot
> of places. You can twiddle the GSK_RENDERER environment variable to
> something less buggy, potentially at the cost of performance.
> Particularly the cairo one ought to do slow, but correct CPU rendering.

Ah this makes sense. I will try and see if I notice it again. It hasn’t happened for any other application.

/Simon
M
M
Maxim Cournoyer wrote on 22 Oct 08:56 +0200
Re: bug#71556: GNOME Konsol crashes
(name . Simon Josefsson)(address . simon@josefsson.org)
87o73caamz.fsf@gmail.com
Hi Simon,

Simon Josefsson <simon@josefsson.org> writes:

Toggle quote (28 lines)
>> 21 juni 2024 kl. 06:32 skrev Liliana Marie Prikler <liliana.prikler@gmail.com>:
>>
>> ?Am Freitag, dem 14.06.2024 um 18:34 +0200 schrieb Simon Josefsson:
>>> Hi.
>>>
>>> GNOME Konsol has crashed for me, bringing down all 10+ windows I had
>>> open (and plenty of ongoing work halted...). I've now seen this
>>> twice, so I suppose it counts as reproducible, even though I don't
>>> know how to trigger it. I recall that it happened when I used the
>>> mouse to maybe resize windows or switch workspace somehow.
>>>
>>> This is guix v1.3.0-60008-g7e00fb9f31 with a fairly normal system
>>> configuration [1] on a fairly ordinary amd64 desktop (MSI Z790P).
>>> Syslog has these two crashes:
>> … and a fairly normal GPU?
>
> Built-in UHD 770 in the Intel 14900K CPU (no overclocking). I am using Dasharo system firmware if that makes a difference.
>
> I’ve used this system extensively and think some recent update may have introduced it as I started seeing it only recently. Hard to tell though since it only happened after 4+ hours of interactive work each time.
>
>> The crash indicates some driver issue, probably in Mesa. Since GNOME
>> is increasingly hardware accelerated, you tend to notice them in a lot
>> of places. You can twiddle the GSK_RENDERER environment variable to
>> something less buggy, potentially at the cost of performance.
>> Particularly the cairo one ought to do slow, but correct CPU rendering.
>
> Ah this makes sense. I will try and see if I notice it again. It hasn’t happened for any other application.

Are you still having problems with GNOME Console (you do mean 'Console',
the default console application in GNOME (the one whose executable is
'kgx') ?)

--
Thanks,
Maxim
S
S
Simon Josefsson wrote on 22 Oct 10:21 +0200
(name . Maxim Cournoyer)(address . maxim.cournoyer@gmail.com)
411D1225-F639-467B-8ED0-765DCE95D094@josefsson.org
I saw the problem a couple of more times, but I have switched away from kgx (which I think is called Konsol not Console?) to the old Terminal app and haven’t had any issues since. I’m okay closing this bug report unless there is some more information from anyone else who have time to debug the kgx/Mesa issue further.

/Simon

Toggle quote (41 lines)
> 22 okt. 2024 kl. 08:56 skrev Maxim Cournoyer <maxim.cournoyer@gmail.com>:
>
> Hi Simon,
>
> Simon Josefsson <simon@josefsson.org <mailto:simon@josefsson.org>> writes:
>
>>> 21 juni 2024 kl. 06:32 skrev Liliana Marie Prikler <liliana.prikler@gmail.com>:
>>>
>>> ?Am Freitag, dem 14.06.2024 um 18:34 +0200 schrieb Simon Josefsson:
>>>> Hi.
>>>>
>>>> GNOME Konsol has crashed for me, bringing down all 10+ windows I had
>>>> open (and plenty of ongoing work halted...). I've now seen this
>>>> twice, so I suppose it counts as reproducible, even though I don't
>>>> know how to trigger it. I recall that it happened when I used the
>>>> mouse to maybe resize windows or switch workspace somehow.
>>>>
>>>> This is guix v1.3.0-60008-g7e00fb9f31 with a fairly normal system
>>>> configuration [1] on a fairly ordinary amd64 desktop (MSI Z790P).
>>>> Syslog has these two crashes:
>>> … and a fairly normal GPU?
>>
>> Built-in UHD 770 in the Intel 14900K CPU (no overclocking). I am using Dasharo system firmware if that makes a difference.
>>
>> I’ve used this system extensively and think some recent update may have introduced it as I started seeing it only recently. Hard to tell though since it only happened after 4+ hours of interactive work each time.
>>
>>> The crash indicates some driver issue, probably in Mesa. Since GNOME
>>> is increasingly hardware accelerated, you tend to notice them in a lot
>>> of places. You can twiddle the GSK_RENDERER environment variable to
>>> something less buggy, potentially at the cost of performance.
>>> Particularly the cairo one ought to do slow, but correct CPU rendering.
>>
>> Ah this makes sense. I will try and see if I notice it again. It hasn’t happened for any other application.
>
> Are you still having problems with GNOME Console (you do mean 'Console',
> the default console application in GNOME (the one whose executable is
> 'kgx') ?)
>
> --
> Thanks,
> Maxim
Attachment: file
L
L
Liliana Marie Prikler wrote on 22 Oct 19:24 +0200
(address . 71556@debbugs.gnu.org)
761f36a7f81638f3ecc9f4695d8d04aec9858f09.camel@gmail.com
Am Dienstag, dem 22.10.2024 um 10:21 +0200 schrieb Simon Josefsson:
Toggle quote (5 lines)
> I saw the problem a couple of more times, but I have switched away
> from kgx (which I think is called Konsol not Console?) to the old
> Terminal app and haven’t had any issues since.  I’m okay closing this
> bug report unless there is some more information from anyone else who
> have time to debug the kgx/Mesa issue further.
It might well be Konsol in some language – it's Console in English. As
for kgx/Mesa bugs, there might be some due to GTK using hardware
acceleration under the hood (which, in turn, is controlled by a few
variables and depends on whether your hardware works nice with libre
software/current Mesa).

Cheers
M
M
Maxim Cournoyer wrote on 23 Oct 08:20 +0200
(name . Liliana Marie Prikler)(address . liliana.prikler@gmail.com)
87a5ev1gtg.fsf@gmail.com
Hi,

Liliana Marie Prikler <liliana.prikler@gmail.com> writes:

Toggle quote (12 lines)
> Am Dienstag, dem 22.10.2024 um 10:21 +0200 schrieb Simon Josefsson:
>> I saw the problem a couple of more times, but I have switched away
>> from kgx (which I think is called Konsol not Console?) to the old
>> Terminal app and haven’t had any issues since.  I’m okay closing this
>> bug report unless there is some more information from anyone else who
>> have time to debug the kgx/Mesa issue further.
> It might well be Konsol in some language – it's Console in English. As
> for kgx/Mesa bugs, there might be some due to GTK using hardware
> acceleration under the hood (which, in turn, is controlled by a few
> variables and depends on whether your hardware works nice with libre
> software/current Mesa).

I've searched for similar reports and found none specific to GNOME
Console (kgx), although this one about the whole Xorg server crashing
looks similar [0]. One of the commenter there also mentions the problem
vanishing after upgrading their memory to 32 GiB, so perhaps it's
related to something being OOM'd ?

Anyway, if you can reproduce this, I think the best place to report the
issue would be upstream on that mesa tracker: they are more likely to
figure out the actual problem and come up with a fix.


--
Thanks,
Maxim
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 71556@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 71556
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch