Hi everyone!

Maybe someone can point me in the right direction of which component to
file a bug report against?

History:

Some months ago I did a fresh install of Mageia 9 x64 on a dual core
notebook, which formerly worked with MGA 7 x64 without any issue.

After install I saw that the machine crashes from time to time, sometimes
several times per day.

The crashes occured typically when the graphical system was under load,
mainly when playing an mp4 movie in firefox, or when the screensaver
started. When running teams(tm) video conferences, there were also
crashes.

Though these crashes are not so often any more these days, I can easily
reproduce a crash by simply playing supertuxkart, and, the likelyhood of
crashes is proportional to the GPU load.
Meaning, playing 'black forest' will 100% certainly crash the machine.

Some facts:

1.) Hardware / software:

[12 dimke@mga9bc-lb1 ~]$ neofetch
.°°. dimke@mga9bc-lb1
°° .°°. ----------------
.°°°. °° OS: Mageia 9 x86_64
. . Host: LIFEBOOK E8310
°°° .°°°. Kernel: 6.6.22-desktop-1.mga9
.°°°. '___' Uptime: 3 hours, 58 mins
.'___' . Packages: 2978 (rpm)
:dkxc;'. ..,cxkd; Shell: bash 5.2.15
.dkk. kkkkkkkkkk .kkd. Resolution: 1920x1080
..dkk. ';cloolc;. .kkd DE: Xfce 4.18
ckk. .kk; WM: Xfwm4
xO: cOd WM Theme: Silverado
xO: lOd Theme: Adwaita [GTK2/3]
lOO. .OO: Icons: Adwaita [GTK2/3]
..k00. .00x Terminal: xterm
.k00; ;00O. CPU: Intel Core 2 Duo T7100 (2) @ 1.801GHz
.lO0Kc;,,,,,,;c0KOc. GPU: Intel Mobile GM965/GL960
;d00KKKKKK00d; Memory: 1635MiB / 3919MiB
.,KKKK,.

2.) Kernel driver:

[14 dimke@mga9bc-lb1 ~]$ lspci -k
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory
Controller Hub (rev 03)
Subsystem: Fujitsu Limited. Device 13f2
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960
Integrated Graphics Controller (primary) (rev 03)
Subsystem: Fujitsu Limited. Device 13f5
Kernel driver in use: i915
Kernel modules: i915, intelfb

3.) Screensaver:

'xscreen saver' with 'themed'

4.) Tuning:

For testing purposes I temporarily turned xfce4 composit off, and there
were no crashes, but testing was short, so not saying too much

5.) Exclude hardware defect:

I took the harddisk (Samsung EVO SSD) out of this machine and put it into
another machine with exactly the same hardware.
Same outcome

6.) Other things observed:

When supertuxkart crashes, the screen freezes but the music keeps playing.
Some times the mouse pointer can be moved nevertheless, but with no impact
on nothing.

In the meantime I am used to do a reboot prior to joining important
meetings, and do not do anything else but just run chromium with
teams(tm). So, in most cases I can perform the conference without crash.

Can anyone tell me how to proceed?

I really like MGA and it would hurt having to switch to another distro.

Thanks in advance!

Best regards,

Markus

On Fri, 19 Apr 2024 10:31:19 -0400, Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:

> Hi everyone!
>
> Maybe someone can point me in the right direction of which component to
> file a bug report against?

Before filing a bug report, check to ensure the cpu and graphics card are not
overheating. I typically use gkrellm with lm_sensors to monitor the temperatures.

If it is overheating, clean the dust out.

After a crash/reboot, use "journalctl -b -1 --no-h" to view the log from the
crashed session. Depending on what groups your id is in, you may need to use
"su -" to become root before viewing the journal, in order to see all of the
journal entries.

What to file a bug report depends on what's crashing, which hopefully the log
will show.

Regards, Dave Hodgins

On Fri, 19 Apr 2024 12:07:55 -0400 David W. Hodgins wrote:

> On Fri, 19 Apr 2024 10:31:19 -0400, Markus Robert Kessler
> <no_reply@dipl-ing-kessler.de> wrote:
>
>> Hi everyone!
>>
>> Maybe someone can point me in the right direction of which component to
>> file a bug report against?
>
> Before filing a bug report, check to ensure the cpu and graphics card
> are not overheating. I typically use gkrellm with lm_sensors to monitor
> the temperatures.
>
> If it is overheating, clean the dust out.
>
> After a crash/reboot, use "journalctl -b -1 --no-h" to view the log from
> the crashed session. Depending on what groups your id is in, you may
> need to use "su -" to become root before viewing the journal, in order
> to see all of the journal entries.
>
> What to file a bug report depends on what's crashing, which hopefully
> the log will show.
>
> Regards, Dave Hodgins

Hi, thanks!

Assuming "--no-h" is short for "--no-hostname", I get the following:

Crash occured 19:42,

[...]

Apr 19 19:39:10 dbus-daemon[2670]: [session uid=1000 pid=2670] Activating
service na>
Apr 19 19:39:10 dbus-daemon[2670]: [session uid=1000 pid=2670]
Successfully activate>
Apr 19 19:39:15 systemd[1]: systemd-hostnamed.service: Deactivated
successfully.
Apr 19 19:40:01 systemd[1]: Started session-200.scope.
Apr 19 19:40:01 CROND[13355]: (dimke) CMD (date >> /var/tmp/log)
Apr 19 19:40:01 CROND[13350]: (dimke) CMDEND (date >> /var/tmp/log)
Apr 19 19:40:01 systemd[1]: session-200.scope: Deactivated successfully.
Apr 19 19:41:01 systemd[1]: Started session-201.scope.
Apr 19 19:41:01 CROND[13493]: (dimke) CMD (date >> /var/tmp/log)
Apr 19 19:41:01 CROND[13488]: (dimke) CMDEND (date >> /var/tmp/log)
Apr 19 19:41:01 systemd[1]: session-201.scope: Deactivated successfully.
Apr 19 19:42:01 systemd[1]: Started session-202.scope.
Apr 19 19:42:01 CROND[13597]: (dimke) CMD (date >> /var/tmp/log)
Apr 19 19:42:01 CROND[13592]: (dimke) CMDEND (date >> /var/tmp/log)
Apr 19 19:42:01 systemd[1]: session-202.scope: Deactivated successfully.
lines 4512-4550/4550 (END)

I write a logfile via crontab, 1 entry "date" per minute, to see if the
machine keeps on running while the desktop is dead:

Fr 19. Apr 19:39:01 CEST 2024
Fr 19. Apr 19:40:01 CEST 2024
Fr 19. Apr 19:41:01 CEST 2024
Fr 19. Apr 19:42:01 CEST 2024
Fr 19. Apr 19:44:01 CEST 2024
Fr 19. Apr 19:45:01 CEST 2024
Fr 19. Apr 19:46:01 CEST 2024
Fr 19. Apr 19:47:01 CEST 2024
Fr 19. Apr 19:48:01 CEST 2024

Also "sensors" do not show any suspicious value (around 60 °C both cores).

Honestly, I do not know how to get closer to the "root cause".

Best regards,

Markus

On Fri, 19 Apr 2024 13:52:41 -0400, Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
> Honestly, I do not know how to get closer to the "root cause".

Strange.

Try running something that crashes from a terminal emulator such as konsole.

$ application >debug.txt 2>&1

to see if there are any messages from that.

Regards, Dave Hodgins

On Fri, 19 Apr 2024 15:12:43 -0400 David W. Hodgins wrote:

> On Fri, 19 Apr 2024 13:52:41 -0400, Markus Robert Kessler
> <no_reply@dipl-ing-kessler.de> wrote:
>> Honestly, I do not know how to get closer to the "root cause".
>
> Strange.
>
> Try running something that crashes from a terminal emulator such as
> konsole.
>
> $ application >debug.txt 2>&1
>
> to see if there are any messages from that.
>
> Regards, Dave Hodgins

Thanks!

$ supertuxkart > /var/tmp/debug.txt 2>&1

[Crash]

[17 dimke@mga9bc-lb1 /var/tmp]$ cat debug.txt
[verbose ] main: Error messages and other text output will be logged to /
home/dimke/.config/supertuxkart/config-0.10/stdout.log.
[info ] [FileManager]: Data files will be fetched from: '/usr/share/
games/supertuxkart/data/'
[info ] [FileManager]: User directory is '/home/dimke/.config/
supertuxkart/config-0.10/'.
[info ] [FileManager]: Addons files will be stored in '/home/
dimke/.local/share/supertuxkart/addons/'.
[info ] [FileManager]: Screenshots will be stored in '/home/
dimke/.local/share/supertuxkart/screenshots/'.
[info ] [FileManager]: User-defined grand prix will be stored in '/home/
dimke/.local/share/supertuxkart/grandprix/'.
[info ] [FileManager]: Asset 0 will be loaded from '/usr/share/games/
supertuxkart/data/challenges/'.
[info ] [FileManager]: Asset 1 will be loaded from '/usr/share/games/
supertuxkart/data/gfx/'.
[info ] [FileManager]: Asset 2 will be loaded from '/usr/share/games/
supertuxkart/data/grandprix/'.
[info ] [FileManager]: Asset 3 will be loaded from '/usr/share/games/
supertuxkart/data/gui/icons/'.
[info ] [FileManager]: Asset 4 will be loaded from '/usr/share/games/
supertuxkart/data/gui/screens/'.
[info ] [FileManager]: Asset 5 will be loaded from '/usr/share/games/
supertuxkart/data/gui/dialogs/'.
[info ] [FileManager]: Asset 6 will be loaded from '/usr/share/games/
supertuxkart/data/replay/'.
[info ] [FileManager]: Asset 7 will be loaded from '/usr/share/games/
supertuxkart/data/shaders/'.
[info ] [FileManager]: Asset 8 will be loaded from '/usr/share/games/
supertuxkart/data/skins/'.
[info ] [FileManager]: Asset 9 will be loaded from '/usr/share/games/
supertuxkart/data/ttf/'.
[info ] [FileManager]: Asset 10 will be loaded from '/usr/share/games/
supertuxkart/data/po/'.
[info ] [FileManager]: Asset 11 will be loaded from '/usr/share/games/
supertuxkart/data/library/'.
[info ] [FileManager]: Asset 12 will be loaded from '/usr/share/games/
supertuxkart/data/models/'.
[info ] [FileManager]: Asset 13 will be loaded from '/usr/share/games/
supertuxkart/data/music/'.
[info ] [FileManager]: Asset 14 will be loaded from '/usr/share/games/
supertuxkart/data/sfx/'.
[info ] [FileManager]: Asset 15 will be loaded from '/usr/share/games/
supertuxkart/data/textures/'.
[info ] [FileManager]: Asset 16 will be loaded from '/usr/share/games/
supertuxkart/data/tracks/'.
[verbose ] translation: Env var LANGUAGE = 'de_DE.UTF-8:de'.
[verbose ] translation: Language 'German (Germany)'.
...:: Antarctica Rendering Engine 2.0 ::..
[info ] [IrrDriver Logger]: ..:: Antarctica Rendering Engine 2.0 ::..
[info ] [IrrDriver Logger]: SDL Version 2.26.2
[info ] [IrrDriver Logger]: Using renderer: OpenGL 2.1
[info ] [IrrDriver Logger]: Mesa Intel(R) 965GM (CL): Intel
[info ] [IrrDriver Logger]: OpenGL driver version is 1.2 or better.
[info ] [IrrDriver Logger]: GLSL version: 1.2
[info ] IrrDriver: OpenGL version: 2.1
[info ] IrrDriver: OpenGL vendor: Intel
[info ] IrrDriver: OpenGL renderer: Mesa Intel(R) 965GM (CL)
[info ] IrrDriver: OpenGL version string: 2.1 Mesa 23.3.6
[info ] GLDriver: ARB Buffer Storage Present
[info ] GLDriver: ARB Arrays of Arrays Present
[info ] GLDriver: ARB Texture Storage Present
[info ] GLDriver: EXT Texture Compression S3TC Present
[info ] GLDriver: ARB Explicit Attrib Location Present
[info ] GLDriver: EXT Texture Filter Anisotropic Present
[info ] GLDriver: ARB Texture Swizzle Present
[info ] GLDriver: ARB Pixel Buffer Object Present
[info ] GLDriver: ARB Sampler Objects Present
[info ] GLDriver: ARB Vertex Type 2_10_10_10_rev Present
[info ] GLDriver: ARB Instanced Arr

B.t.w., as mentioned in former message, same occurs when HD with OS is set
into second identical machine. The crashes occur in other apps like when
starting xscreensaver, or in firefox also, but sporadically.

The same kernel module, i915, is in use in MGA9-32, where supertuxkart
does not run at all, but there was never even one single crash.

To me, it looks as if above module has an issue with given hardware, see
neofetch.

Thanks again,
best regards,

Markus

On Fri, 19 Apr 2024 19:56:48 -0000 (UTC) Markus Robert Kessler wrote:

> On Fri, 19 Apr 2024 15:12:43 -0400 David W. Hodgins wrote:
>
>> On Fri, 19 Apr 2024 13:52:41 -0400, Markus Robert Kessler
>> <no_reply@dipl-ing-kessler.de> wrote:
>>> Honestly, I do not know how to get closer to the "root cause".
>>
>> Strange.
>>
>> Try running something that crashes from a terminal emulator such as
>> konsole.
>>
>> $ application >debug.txt 2>&1
>>
>> to see if there are any messages from that.
>>
>> Regards, Dave Hodgins
>
> Thanks!
>
> $ supertuxkart > /var/tmp/debug.txt 2>&1
>
> [Crash]
>
> [17 dimke@mga9bc-lb1 /var/tmp]$ cat debug.txt [verbose ] main: Error
> messages and other text output will be logged to /
> home/dimke/.config/supertuxkart/config-0.10/stdout.log.
> [info ] [FileManager]: Data files will be fetched from: '/usr/share/
> games/supertuxkart/data/'
> [info ] [FileManager]: User directory is '/home/dimke/.config/
> supertuxkart/config-0.10/'.
> [info ] [FileManager]: Addons files will be stored in '/home/
> dimke/.local/share/supertuxkart/addons/'.
> [info ] [FileManager]: Screenshots will be stored in '/home/
> dimke/.local/share/supertuxkart/screenshots/'.
> [info ] [FileManager]: User-defined grand prix will be stored in
> '/home/
> dimke/.local/share/supertuxkart/grandprix/'.
> [info ] [FileManager]: Asset 0 will be loaded from '/usr/share/games/
> supertuxkart/data/challenges/'.
> [info ] [FileManager]: Asset 1 will be loaded from '/usr/share/games/
> supertuxkart/data/gfx/'.
> [info ] [FileManager]: Asset 2 will be loaded from '/usr/share/games/
> supertuxkart/data/grandprix/'.
> [info ] [FileManager]: Asset 3 will be loaded from '/usr/share/games/
> supertuxkart/data/gui/icons/'.
> [info ] [FileManager]: Asset 4 will be loaded from '/usr/share/games/
> supertuxkart/data/gui/screens/'.
> [info ] [FileManager]: Asset 5 will be loaded from '/usr/share/games/
> supertuxkart/data/gui/dialogs/'.
> [info ] [FileManager]: Asset 6 will be loaded from '/usr/share/games/
> supertuxkart/data/replay/'.
> [info ] [FileManager]: Asset 7 will be loaded from '/usr/share/games/
> supertuxkart/data/shaders/'.
> [info ] [FileManager]: Asset 8 will be loaded from '/usr/share/games/
> supertuxkart/data/skins/'.
> [info ] [FileManager]: Asset 9 will be loaded from '/usr/share/games/
> supertuxkart/data/ttf/'.
> [info ] [FileManager]: Asset 10 will be loaded from '/usr/share/games/
> supertuxkart/data/po/'.
> [info ] [FileManager]: Asset 11 will be loaded from '/usr/share/games/
> supertuxkart/data/library/'.
> [info ] [FileManager]: Asset 12 will be loaded from '/usr/share/games/
> supertuxkart/data/models/'.
> [info ] [FileManager]: Asset 13 will be loaded from '/usr/share/games/
> supertuxkart/data/music/'.
> [info ] [FileManager]: Asset 14 will be loaded from '/usr/share/games/
> supertuxkart/data/sfx/'.
> [info ] [FileManager]: Asset 15 will be loaded from '/usr/share/games/
> supertuxkart/data/textures/'.
> [info ] [FileManager]: Asset 16 will be loaded from '/usr/share/games/
> supertuxkart/data/tracks/'.
> [verbose ] translation: Env var LANGUAGE = 'de_DE.UTF-8:de'.
> [verbose ] translation: Language 'German (Germany)'.
> ..:: Antarctica Rendering Engine 2.0 ::..
> [info ] [IrrDriver Logger]: ..:: Antarctica Rendering Engine 2.0 ::..
> [info ] [IrrDriver Logger]: SDL Version 2.26.2 [info ] [IrrDriver
> Logger]: Using renderer: OpenGL 2.1 [info ] [IrrDriver Logger]: Mesa
> Intel(R) 965GM (CL): Intel [info ] [IrrDriver Logger]: OpenGL driver
> version is 1.2 or better. [info ] [IrrDriver Logger]: GLSL version:
> 1.2 [info ] IrrDriver: OpenGL version: 2.1 [info ] IrrDriver: OpenGL
> vendor: Intel [info ] IrrDriver: OpenGL renderer: Mesa Intel(R) 965GM
> (CL)
> [info ] IrrDriver: OpenGL version string: 2.1 Mesa 23.3.6 [info ]
> GLDriver: ARB Buffer Storage Present [info ] GLDriver: ARB Arrays of
> Arrays Present [info ] GLDriver: ARB Texture Storage Present [info ]
> GLDriver: EXT Texture Compression S3TC Present [info ] GLDriver: ARB
> Explicit Attrib Location Present [info ] GLDriver: EXT Texture Filter
> Anisotropic Present [info ] GLDriver: ARB Texture Swizzle Present
> [info ] GLDriver: ARB Pixel Buffer Object Present [info ] GLDriver:
> ARB Sampler Objects Present [info ] GLDriver: ARB Vertex Type
> 2_10_10_10_rev Present [info ] GLDriver: ARB Instanced Arr
>
> B.t.w., as mentioned in former message, same occurs when HD with OS is
> set into second identical machine. The crashes occur in other apps like
> when starting xscreensaver, or in firefox also, but sporadically.
>
> The same kernel module, i915, is in use in MGA9-32, where supertuxkart
> does not run at all, but there was never even one single crash.
>
> To me, it looks as if above module has an issue with given hardware, see
> neofetch.

Also worth to mention:

I now deactivated composit in xfce4 and did the same as before:

[19 dimke@mga9bc-lb1 /var/tmp]$ supertuxkart > debug_no-composit.log 2>&1

==> [NO crash, normal program end after 2 laps]

[20 dimke@mga9bc-lb1 /var/tmp]$ cat debug_no-composit.log
[verbose ] main: Error messages and other text output will be logged to /
home/dimke/.config/supertuxkart/config-0.10/stdout.log.
[info ] [FileManager]: Data files will be fetched from: '/usr/share/
games/supertuxkart/data/'
[info ] [FileManager]: User directory is '/home/dimke/.config/
supertuxkart/config-0.10/'.
[info ] [FileManager]: Addons files will be stored in '/home/
dimke/.local/share/supertuxkart/addons/'.
[info ] [FileManager]: Screenshots will be stored in '/home/
dimke/.local/share/supertuxkart/screenshots/'.
[info ] [FileManager]: User-defined grand prix will be stored in '/home/
dimke/.local/share/supertuxkart/grandprix/'.
[info ] [FileManager]: Asset 0 will be loaded from '/usr/share/games/
supertuxkart/data/challenges/'.
[info ] [FileManager]: Asset 1 will be loaded from '/usr/share/games/
supertuxkart/data/gfx/'.
[info ] [FileManager]: Asset 2 will be loaded from '/usr/share/games/
supertuxkart/data/grandprix/'.
[info ] [FileManager]: Asset 3 will be loaded from '/usr/share/games/
supertuxkart/data/gui/icons/'.
[info ] [FileManager]: Asset 4 will be loaded from '/usr/share/games/
supertuxkart/data/gui/screens/'.
[info ] [FileManager]: Asset 5 will be loaded from '/usr/share/games/
supertuxkart/data/gui/dialogs/'.
[info ] [FileManager]: Asset 6 will be loaded from '/usr/share/games/
supertuxkart/data/replay/'.
[info ] [FileManager]: Asset 7 will be loaded from '/usr/share/games/
supertuxkart/data/shaders/'.
[info ] [FileManager]: Asset 8 will be loaded from '/usr/share/games/
supertuxkart/data/skins/'.
[info ] [FileManager]: Asset 9 will be loaded from '/usr/share/games/
supertuxkart/data/ttf/'.
[info ] [FileManager]: Asset 10 will be loaded from '/usr/share/games/
supertuxkart/data/po/'.
[info ] [FileManager]: Asset 11 will be loaded from '/usr/share/games/
supertuxkart/data/library/'.
[info ] [FileManager]: Asset 12 will be loaded from '/usr/share/games/
supertuxkart/data/models/'.
[info ] [FileManager]: Asset 13 will be loaded from '/usr/share/games/
supertuxkart/data/music/'.
[info ] [FileManager]: Asset 14 will be loaded from '/usr/share/games/
supertuxkart/data/sfx/'.
[info ] [FileManager]: Asset 15 will be loaded from '/usr/share/games/
supertuxkart/data/textures/'.
[info ] [FileManager]: Asset 16 will be loaded from '/usr/share/games/
supertuxkart/data/tracks/'.
[verbose ] translation: Env var LANGUAGE = 'de_DE.UTF-8:de'.
[verbose ] translation: Language 'German (Germany)'.
...:: Antarctica Rendering Engine 2.0 ::..
[info ] [IrrDriver Logger]: ..:: Antarctica Rendering Engine 2.0 ::..
[info ] [IrrDriver Logger]: SDL Version 2.26.2
[info ] [IrrDriver Logger]: Using renderer: OpenGL 2.1
[info ] [IrrDriver Logger]: Mesa Intel(R) 965GM (CL): Intel
[info ] [IrrDriver Logger]: OpenGL driver version is 1.2 or better.
[info ] [IrrDriver Logger]: GLSL version: 1.2
[info ] IrrDriver: OpenGL version: 2.1
[info ] IrrDriver: OpenGL vendor: Intel
[info ] IrrDriver: OpenGL renderer: Mesa Intel(R) 965GM (CL)
[info ] IrrDriver: OpenGL version string: 2.1 Mesa 23.3.6
[info ] GLDriver: ARB Buffer Storage Present
[info ] GLDriver: ARB Arrays of Arrays Present
[info ] GLDriver: ARB Texture Storage Present
[info ] GLDriver: EXT Texture Compression S3TC Present
[info ] GLDriver: ARB Explicit Attrib Location Present
[info ] GLDriver: EXT Texture Filter Anisotropic Present
[info ] GLDriver: ARB Texture Swizzle Present
[info ] GLDriver: ARB Pixel Buffer Object Present
[info ] GLDriver: ARB Sampler Objects Present
[info ] GLDriver: ARB Vertex Type 2_10_10_10_rev Present
[info ] GLDriver: ARB Instanced Arrays Present
[warn ] irr_driver: Using the fixed pipeline (old GPU, or shaders
disabled in options)
[info ] GUI: Loading skin data from file: /usr/share/games/supertuxkart/
data/skins/peach/stkskin.xml
[info ] HTTPRequest: Downloading https://online.supertuxkart.net/dl/xml/
online_news.xml
[info ] addons: Using cached addons.xml.
[info ] GrandPrixManager: Loading Grand Prix files from /usr/share/
games/supertuxkart/data/grandprix/
[info ] GrandPrixManager: Loading Grand Prix files from /home/
dimke/.local/share/supertuxkart/grandprix/
[warn ] OpenGL: OpenGL version is too old!
[warn ] LayoutManager: Statically sized widgets took all the place!!
[warn ] LayoutManager: Statically sized widgets took all the place!!
[warn ] LayoutManager: Statically sized widgets took all the place!!
[warn ] LayoutManager: Statically sized widgets took all the place!!
[warn ] LayoutManager: Statically sized widgets took all the place!!
[warn ] LayoutManager: Statically sized widgets took all the place!!
[warn ] LayoutManager: Statically sized widgets took all the place!!
[warn ] LayoutManager: Statically sized widgets took all the place!!
[warn ] LayoutManager: Statically sized widgets took all the place!!
[warn ] AbstractTopLevelContainer::addWidgetsRecursively: Widget target-
type-spinner of type 1 has no dimensions
[warn ] AbstractTopLevelContainer::addWidgetsRecursively: Widget target-
type-text of type 5 has no dimensions
[warn ] AbstractTopLevelContainer::addWidgetsRecursively: Widget ai-
blue-spinner of type 1 has no dimensions
[warn ] AbstractTopLevelContainer::addWidgetsRecursively: Widget ai-
blue-text of type 5 has no dimensions
[verbose ] RaceManager: Nb of karts=4, ghost karts:0 ai:3 players:1

On Fri, 19 Apr 2024 20:21:10 -0000 (UTC) Markus Robert Kessler wrote:

> On Fri, 19 Apr 2024 19:56:48 -0000 (UTC) Markus Robert Kessler wrote:
>
>> On Fri, 19 Apr 2024 15:12:43 -0400 David W. Hodgins wrote:
>>
>>> On Fri, 19 Apr 2024 13:52:41 -0400, Markus Robert Kessler
>>> <no_reply@dipl-ing-kessler.de> wrote:
>>>> Honestly, I do not know how to get closer to the "root cause".
>>>
>>> Strange.
>>>
>>> Try running something that crashes from a terminal emulator such as
>>> konsole.
>>>
>>> $ application >debug.txt 2>&1
>>>
>>> to see if there are any messages from that.
>>>
>>> Regards, Dave Hodgins
>>
>> Thanks!
>>
>> $ supertuxkart > /var/tmp/debug.txt 2>&1
>>
>> [Crash]
>>
>> [17 dimke@mga9bc-lb1 /var/tmp]$ cat debug.txt [verbose ] main: Error
>> messages and other text output will be logged to /
>> home/dimke/.config/supertuxkart/config-0.10/stdout.log.
>> [info ] [FileManager]: Data files will be fetched from: '/usr/share/
>> games/supertuxkart/data/'
>> [info ] [FileManager]: User directory is '/home/dimke/.config/
>> supertuxkart/config-0.10/'.
>> [info ] [FileManager]: Addons files will be stored in '/home/
>> dimke/.local/share/supertuxkart/addons/'.
>> [info ] [FileManager]: Screenshots will be stored in '/home/
>> dimke/.local/share/supertuxkart/screenshots/'.
>> [info ] [FileManager]: User-defined grand prix will be stored in
>> '/home/
>> dimke/.local/share/supertuxkart/grandprix/'.
>> [info ] [FileManager]: Asset 0 will be loaded from '/usr/share/games/
>> supertuxkart/data/challenges/'.
>> [info ] [FileManager]: Asset 1 will be loaded from '/usr/share/games/
>> supertuxkart/data/gfx/'.
>> [info ] [FileManager]: Asset 2 will be loaded from '/usr/share/games/
>> supertuxkart/data/grandprix/'.
>> [info ] [FileManager]: Asset 3 will be loaded from '/usr/share/games/
>> supertuxkart/data/gui/icons/'.
>> [info ] [FileManager]: Asset 4 will be loaded from '/usr/share/games/
>> supertuxkart/data/gui/screens/'.
>> [info ] [FileManager]: Asset 5 will be loaded from '/usr/share/games/
>> supertuxkart/data/gui/dialogs/'.
>> [info ] [FileManager]: Asset 6 will be loaded from '/usr/share/games/
>> supertuxkart/data/replay/'.
>> [info ] [FileManager]: Asset 7 will be loaded from '/usr/share/games/
>> supertuxkart/data/shaders/'.
>> [info ] [FileManager]: Asset 8 will be loaded from '/usr/share/games/
>> supertuxkart/data/skins/'.
>> [info ] [FileManager]: Asset 9 will be loaded from '/usr/share/games/
>> supertuxkart/data/ttf/'.
>> [info ] [FileManager]: Asset 10 will be loaded from
>> '/usr/share/games/
>> supertuxkart/data/po/'.
>> [info ] [FileManager]: Asset 11 will be loaded from
>> '/usr/share/games/
>> supertuxkart/data/library/'.
>> [info ] [FileManager]: Asset 12 will be loaded from
>> '/usr/share/games/
>> supertuxkart/data/models/'.
>> [info ] [FileManager]: Asset 13 will be loaded from
>> '/usr/share/games/
>> supertuxkart/data/music/'.
>> [info ] [FileManager]: Asset 14 will be loaded from
>> '/usr/share/games/
>> supertuxkart/data/sfx/'.
>> [info ] [FileManager]: Asset 15 will be loaded from
>> '/usr/share/games/
>> supertuxkart/data/textures/'.
>> [info ] [FileManager]: Asset 16 will be loaded from
>> '/usr/share/games/
>> supertuxkart/data/tracks/'.
>> [verbose ] translation: Env var LANGUAGE = 'de_DE.UTF-8:de'.
>> [verbose ] translation: Language 'German (Germany)'.
>> ..:: Antarctica Rendering Engine 2.0 ::..
>> [info ] [IrrDriver Logger]: ..:: Antarctica Rendering Engine 2.0 ::..
>> [info ] [IrrDriver Logger]: SDL Version 2.26.2 [info ] [IrrDriver
>> Logger]: Using renderer: OpenGL 2.1 [info ] [IrrDriver Logger]: Mesa
>> Intel(R) 965GM (CL): Intel [info ] [IrrDriver Logger]: OpenGL driver
>> version is 1.2 or better. [info ] [IrrDriver Logger]: GLSL version:
>> 1.2 [info ] IrrDriver: OpenGL version: 2.1 [info ] IrrDriver:
>> OpenGL vendor: Intel [info ] IrrDriver: OpenGL renderer: Mesa
>> Intel(R) 965GM (CL)
>> [info ] IrrDriver: OpenGL version string: 2.1 Mesa 23.3.6 [info ]
>> GLDriver: ARB Buffer Storage Present [info ] GLDriver: ARB Arrays of
>> Arrays Present [info ] GLDriver: ARB Texture Storage Present [info
>> ]
>> GLDriver: EXT Texture Compression S3TC Present [info ] GLDriver: ARB
>> Explicit Attrib Location Present [info ] GLDriver: EXT Texture Filter
>> Anisotropic Present [info ] GLDriver: ARB Texture Swizzle Present
>> [info ] GLDriver: ARB Pixel Buffer Object Present [info ] GLDriver:
>> ARB Sampler Objects Present [info ] GLDriver: ARB Vertex Type
>> 2_10_10_10_rev Present [info ] GLDriver: ARB Instanced Arr
>>
>> B.t.w., as mentioned in former message, same occurs when HD with OS is
>> set into second identical machine. The crashes occur in other apps like
>> when starting xscreensaver, or in firefox also, but sporadically.
>>
>> The same kernel module, i915, is in use in MGA9-32, where supertuxkart
>> does not run at all, but there was never even one single crash.
>>
>> To me, it looks as if above module has an issue with given hardware,
>> see neofetch.
>
>
> Also worth to mention:
>
> I now deactivated composit in xfce4 and did the same as before:
>
> [19 dimke@mga9bc-lb1 /var/tmp]$ supertuxkart > debug_no-composit.log
> 2>&1
>
> ==> [NO crash, normal program end after 2 laps]
>
> [20 dimke@mga9bc-lb1 /var/tmp]$ cat debug_no-composit.log [verbose ]
> main: Error messages and other text output will be logged to /
> home/dimke/.config/supertuxkart/config-0.10/stdout.log.
> [info ] [FileManager]: Data files will be fetched from: '/usr/share/
> games/supertuxkart/data/'
> [info ] [FileManager]: User directory is '/home/dimke/.config/
> supertuxkart/config-0.10/'.
> [info ] [FileManager]: Addons files will be stored in '/home/
> dimke/.local/share/supertuxkart/addons/'.
> [info ] [FileManager]: Screenshots will be stored in '/home/
> dimke/.local/share/supertuxkart/screenshots/'.
> [info ] [FileManager]: User-defined grand prix will be stored in
> '/home/
> dimke/.local/share/supertuxkart/grandprix/'.
> [info ] [FileManager]: Asset 0 will be loaded from '/usr/share/games/
> supertuxkart/data/challenges/'.
> [info ] [FileManager]: Asset 1 will be loaded from '/usr/share/games/
> supertuxkart/data/gfx/'.
> [info ] [FileManager]: Asset 2 will be loaded from '/usr/share/games/
> supertuxkart/data/grandprix/'.
> [info ] [FileManager]: Asset 3 will be loaded from '/usr/share/games/
> supertuxkart/data/gui/icons/'.
> [info ] [FileManager]: Asset 4 will be loaded from '/usr/share/games/
> supertuxkart/data/gui/screens/'.
> [info ] [FileManager]: Asset 5 will be loaded from '/usr/share/games/
> supertuxkart/data/gui/dialogs/'.
> [info ] [FileManager]: Asset 6 will be loaded from '/usr/share/games/
> supertuxkart/data/replay/'.
> [info ] [FileManager]: Asset 7 will be loaded from '/usr/share/games/
> supertuxkart/data/shaders/'.
> [info ] [FileManager]: Asset 8 will be loaded from '/usr/share/games/
> supertuxkart/data/skins/'.
> [info ] [FileManager]: Asset 9 will be loaded from '/usr/share/games/
> supertuxkart/data/ttf/'.
> [info ] [FileManager]: Asset 10 will be loaded from '/usr/share/games/
> supertuxkart/data/po/'.
> [info ] [FileManager]: Asset 11 will be loaded from '/usr/share/games/
> supertuxkart/data/library/'.
> [info ] [FileManager]: Asset 12 will be loaded from '/usr/share/games/
> supertuxkart/data/models/'.
> [info ] [FileManager]: Asset 13 will be loaded from '/usr/share/games/
> supertuxkart/data/music/'.
> [info ] [FileManager]: Asset 14 will be loaded from '/usr/share/games/
> supertuxkart/data/sfx/'.
> [info ] [FileManager]: Asset 15 will be loaded from '/usr/share/games/
> supertuxkart/data/textures/'.
> [info ] [FileManager]: Asset 16 will be loaded from '/usr/share/games/
> supertuxkart/data/tracks/'.
> [verbose ] translation: Env var LANGUAGE = 'de_DE.UTF-8:de'.
> [verbose ] translation: Language 'German (Germany)'.
> ..:: Antarctica Rendering Engine 2.0 ::..
> [info ] [IrrDriver Logger]: ..:: Antarctica Rendering Engine 2.0 ::..
> [info ] [IrrDriver Logger]: SDL Version 2.26.2 [info ] [IrrDriver
> Logger]: Using renderer: OpenGL 2.1 [info ] [IrrDriver Logger]: Mesa
> Intel(R) 965GM (CL): Intel [info ] [IrrDriver Logger]: OpenGL driver
> version is 1.2 or better. [info ] [IrrDriver Logger]: GLSL version:
> 1.2 [info ] IrrDriver: OpenGL version: 2.1 [info ] IrrDriver: OpenGL
> vendor: Intel [info ] IrrDriver: OpenGL renderer: Mesa Intel(R) 965GM
> (CL)
> [info ] IrrDriver: OpenGL version string: 2.1 Mesa 23.3.6 [info ]
> GLDriver: ARB Buffer Storage Present [info ] GLDriver: ARB Arrays of
> Arrays Present [info ] GLDriver: ARB Texture Storage Present [info ]
> GLDriver: EXT Texture Compression S3TC Present [info ] GLDriver: ARB
> Explicit Attrib Location Present [info ] GLDriver: EXT Texture Filter
> Anisotropic Present [info ] GLDriver: ARB Texture Swizzle Present
> [info ] GLDriver: ARB Pixel Buffer Object Present [info ] GLDriver:
> ARB Sampler Objects Present [info ] GLDriver: ARB Vertex Type
> 2_10_10_10_rev Present [info ] GLDriver: ARB Instanced Arrays Present
> [warn ] irr_driver: Using the fixed pipeline (old GPU, or shaders
> disabled in options)
> [info ] GUI: Loading skin data from file:
> /usr/share/games/supertuxkart/
> data/skins/peach/stkskin.xml [info ] HTTPRequest: Downloading
> https://online.supertuxkart.net/dl/xml/
> online_news.xml [info ] addons: Using cached addons.xml.
> [info ] GrandPrixManager: Loading Grand Prix files from /usr/share/
> games/supertuxkart/data/grandprix/
> [info ] GrandPrixManager: Loading Grand Prix files from /home/
> dimke/.local/share/supertuxkart/grandprix/
> [warn ] OpenGL: OpenGL version is too old!
> [warn ] LayoutManager: Statically sized widgets took all the place!!
> [warn ] LayoutManager: Statically sized widgets took all the place!!
> [warn ] LayoutManager: Statically sized widgets took all the place!!
> [warn ] LayoutManager: Statically sized widgets took all the place!!
> [warn ] LayoutManager: Statically sized widgets took all the place!!
> [warn ] LayoutManager: Statically sized widgets took all the place!!
> [warn ] LayoutManager: Statically sized widgets took all the place!!
> [warn ] LayoutManager: Statically sized widgets took all the place!!
> [warn ] LayoutManager: Statically sized widgets took all the place!!
> [warn ] AbstractTopLevelContainer::addWidgetsRecursively: Widget
> target-
> type-spinner of type 1 has no dimensions [warn ]
> AbstractTopLevelContainer::addWidgetsRecursively: Widget target-
> type-text of type 5 has no dimensions [warn ]
> AbstractTopLevelContainer::addWidgetsRecursively: Widget ai-
> blue-spinner of type 1 has no dimensions [warn ]
> AbstractTopLevelContainer::addWidgetsRecursively: Widget ai- blue-text
> of type 5 has no dimensions [verbose ] RaceManager: Nb of karts=4,
> ghost karts:0 ai:3 players:1
>
> [info ] Track: Overall scene complexity estimated at 4483 [info ]
> Singleton: Destroyed singleton.
> [info ] Singleton: Destroyed singleton.
> [info ] Singleton: Destroyed singleton.
>
>
> So, it's hard to believe that a USER setting like composit on/off in
> xfce4 can decide if the whole graphics system crashes or not.

On Fri, 19 Apr 2024 16:21:10 -0400, Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
<snip>
> So, it's hard to believe that a USER setting like composit on/off in xfce4
> can decide if the whole graphics system crashes or not.

Do you have all updates installed?

It was supposed to have been fixed for flightgear with
https://bugs.mageia.org/show_bug.cgi?id=32456
by turning off compositing.

Regards, Dave Hodgins

On Fri, 19 Apr 2024 17:00:29 -0400 David W. Hodgins wrote:

> On Fri, 19 Apr 2024 16:21:10 -0400, Markus Robert Kessler
> <no_reply@dipl-ing-kessler.de> wrote:
> <snip>
>> So, it's hard to believe that a USER setting like composit on/off in
>> xfce4 can decide if the whole graphics system crashes or not.
>
> Do you have all updates installed?
>
> It was supposed to have been fixed for flightgear with
> https://bugs.mageia.org/show_bug.cgi?id=32456 by turning off
> compositing.
>
> Regards, Dave Hodgins

Hi Dave,

yes, everything is current version.

As reported in former message, crash can be reproduced.
A different installation based on Ubuntu which never crashed before, also
DOES crash when HD is set into machine in question with Intel Mobile
GM965/GL960. I have two machines with this GPU type and both behave in
same way.

This GPU, 'Intel Mobile GM965/GL960' seems not to be fully supported.

I do not know if the relevant kernel driver is the only culprit, but at
least this seems to be PART of the problem.

Best regards,

Markus

On 2024-04-20 02:49, Markus Robert Kessler wrote:
> On Fri, 19 Apr 2024 17:00:29 -0400 David W. Hodgins wrote:
>
>> On Fri, 19 Apr 2024 16:21:10 -0400, Markus Robert Kessler
>> <no_reply@dipl-ing-kessler.de> wrote:
>> <snip>
>>> So, it's hard to believe that a USER setting like composit on/off in
>>> xfce4 can decide if the whole graphics system crashes or not.
>>
>> Do you have all updates installed?
>>
>> It was supposed to have been fixed for flightgear with
>> https://bugs.mageia.org/show_bug.cgi?id=32456 by turning off
>> compositing.
>>
>> Regards, Dave Hodgins
>
> Hi Dave,
>
> yes, everything is current version.
>
> As reported in former message, crash can be reproduced.
> A different installation based on Ubuntu which never crashed before, also
> DOES crash when HD is set into machine in question with Intel Mobile
> GM965/GL960. I have two machines with this GPU type and both behave in
> same way.
>
> This GPU, 'Intel Mobile GM965/GL960' seems not to be fully supported.
>
> I do not know if the relevant kernel driver is the only culprit, but at
> least this seems to be PART of the problem.
>
> Best regards,
>
> Markus

Just a thought, but...

The way I've read this, another thing all these tests have in common,
other than the GPU and i915 driver, is the hard drive you have been
switching from machine to machine. Are you sure THAT is OK?

TJ

On 2024-04-20 08:45, TJ wrote:
> On 2024-04-20 02:49, Markus Robert Kessler wrote:
>> On Fri, 19 Apr 2024 17:00:29 -0400 David W. Hodgins wrote:
>>
>>> On Fri, 19 Apr 2024 16:21:10 -0400, Markus Robert Kessler
>>> <no_reply@dipl-ing-kessler.de> wrote:
>>> <snip>
>>>> So, it's hard to believe that a USER setting like composit on/off in
>>>> xfce4 can decide if the whole graphics system crashes or not.
>>>
>>> Do you have all updates installed?
>>>
>>> It was supposed to have been fixed for flightgear with
>>> https://bugs.mageia.org/show_bug.cgi?id=32456 by turning off
>>> compositing.
>>>
>>> Regards, Dave Hodgins
>>
>> Hi Dave,
>>
>> yes, everything is current version.
>>
>> As reported in former message, crash can be reproduced.
>> A different installation based on Ubuntu which never crashed before, also
>> DOES crash when HD is set into machine in question with Intel Mobile
>> GM965/GL960. I have two machines with this GPU type and both behave in
>> same way.
>>
>> This GPU, 'Intel Mobile GM965/GL960' seems not to be fully supported.
>>
>> I do not know if the relevant kernel driver is the only culprit, but at
>> least this seems to be PART of the problem.
>>
>> Best regards,
>>
>> Markus
>
> Just a thought, but...
>
> The way I've read this, another thing all these tests have in common,
> other than the GPU and i915 driver, is the hard drive you have been
> switching from machine to machine. Are you sure THAT is OK?
>
> TJ
Never mind. I re-read the above post, and I see the crashing Ubuntu
install was on a different hard drive. Sorry for the noise.

TJ

On Sat, 20 Apr 2024 09:45:59 -0400 TJ wrote:

> On 2024-04-20 08:45, TJ wrote:
>> On 2024-04-20 02:49, Markus Robert Kessler wrote:
>>> On Fri, 19 Apr 2024 17:00:29 -0400 David W. Hodgins wrote:
>>>
>>>> On Fri, 19 Apr 2024 16:21:10 -0400, Markus Robert Kessler
>>>> <no_reply@dipl-ing-kessler.de> wrote:
>>>> <snip>
>>>>> So, it's hard to believe that a USER setting like composit on/off in
>>>>> xfce4 can decide if the whole graphics system crashes or not.
>>>>
>>>> Do you have all updates installed?
>>>>
>>>> It was supposed to have been fixed for flightgear with
>>>> https://bugs.mageia.org/show_bug.cgi?id=32456 by turning off
>>>> compositing.
>>>>
>>>> Regards, Dave Hodgins
>>>
>>> Hi Dave,
>>>
>>> yes, everything is current version.
>>>
>>> As reported in former message, crash can be reproduced.
>>> A different installation based on Ubuntu which never crashed before,
>>> also DOES crash when HD is set into machine in question with Intel
>>> Mobile GM965/GL960. I have two machines with this GPU type and both
>>> behave in same way.
>>>
>>> This GPU, 'Intel Mobile GM965/GL960' seems not to be fully supported.
>>>
>>> I do not know if the relevant kernel driver is the only culprit, but
>>> at least this seems to be PART of the problem.
>>>
>>> Best regards,
>>>
>>> Markus
>>
>> Just a thought, but...
>>
>> The way I've read this, another thing all these tests have in common,
>> other than the GPU and i915 driver, is the hard drive you have been
>> switching from machine to machine. Are you sure THAT is OK?
>>
>> TJ
> Never mind. I re-read the above post, and I see the crashing Ubuntu
> install was on a different hard drive. Sorry for the noise.
>
> TJ

OK, fine :-)

So, I'd highly appreciate if someone could give me a hint how to proceed.

Well, from what I've seen so far, the probability of crashes can be
reduced by turning off compositing, but then your desktop looks like
Windows95. For showing your screen during video conferences at least a
little 'whistles and bells' would be fine.

What components to file a bug report against?

Thanks,
best regards,

Markus

On Sat, 20 Apr 2024 02:49:19 -0400, Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:

> On Fri, 19 Apr 2024 17:00:29 -0400 David W. Hodgins wrote:
>
>> On Fri, 19 Apr 2024 16:21:10 -0400, Markus Robert Kessler
>> <no_reply@dipl-ing-kessler.de> wrote:
>> <snip>
>>> So, it's hard to believe that a USER setting like composit on/off in
>>> xfce4 can decide if the whole graphics system crashes or not.
>>
>> Do you have all updates installed?
>>
>> It was supposed to have been fixed for flightgear with
>> https://bugs.mageia.org/show_bug.cgi?id=32456 by turning off
>> compositing.
>>
>> Regards, Dave Hodgins
>
> Hi Dave,
>
> yes, everything is current version.
>
> As reported in former message, crash can be reproduced.
> A different installation based on Ubuntu which never crashed before, also
> DOES crash when HD is set into machine in question with Intel Mobile
> GM965/GL960. I have two machines with this GPU type and both behave in
> same way.
>
> This GPU, 'Intel Mobile GM965/GL960' seems not to be fully supported.
>
> I do not know if the relevant kernel driver is the only culprit, but at
> least this seems to be PART of the problem.

Probably best to open a bug report. Other then bug reports I can search
through, and things I remember having seen, I have no experience with using
an intel gpu.

Regards, Dave Hodgins

On 2024-04-20 13:42, David W. Hodgins wrote:
> On Sat, 20 Apr 2024 02:49:19 -0400, Markus Robert Kessler
> <no_reply@dipl-ing-kessler.de> wrote:
>
>> On Fri, 19 Apr 2024 17:00:29 -0400 David W. Hodgins wrote:
>>
>>> On Fri, 19 Apr 2024 16:21:10 -0400, Markus Robert Kessler
>>> <no_reply@dipl-ing-kessler.de> wrote:
>>> <snip>
>>>> So, it's hard to believe that a USER setting like composit on/off in
>>>> xfce4 can decide if the whole graphics system crashes or not.
>>>
>>> Do you have all updates installed?
>>>
>>> It was supposed to have been fixed for flightgear with
>>> https://bugs.mageia.org/show_bug.cgi?id=32456 by turning off
>>> compositing.
>>>
>>> Regards, Dave Hodgins
>>
>> Hi Dave,
>>
>> yes, everything is current version.
>>
>> As reported in former message, crash can be reproduced.
>> A different installation based on Ubuntu which never crashed before, also
>> DOES crash when HD is set into machine in question with Intel Mobile
>> GM965/GL960. I have two machines with this GPU type and both behave in
>> same way.
>>
>> This GPU, 'Intel Mobile GM965/GL960' seems not to be fully supported.
>>
>> I do not know if the relevant kernel driver is the only culprit, but at
>> least this seems to be PART of the problem.
>
> Probably best to open a bug report. Other then bug reports I can search
> through, and things I remember having seen, I have no experience with using
> an intel gpu.
>
> Regards, Dave Hodgins

Interesting.

My Probook 6550b uses the Intel i915 driver, but the gpu is likely newer
than Marcus' as the processor is a first-generation i3. But, I installed
SuperTuxKart and ran it, anyway. This popup showed up:

Your graphics driver appears to be very old. Please check if an update
is available. SuperTuxKart recommends a driver supporting OpenGL 3.3 or
better. The game will likely still run, but in a reduced graphics mode.

The popup is wrong - it is not the driver that is at fault, as the i915
driver covers a number of different gpus with different abilities. It is
my gpu that doesn't support OpenGL 3.3, not the driver. It is likely the
same with Marcus' gpu.

My Plasma system didn't crash with SuperTuxKart, even when I ran the
kart into a stone wall, but that may just be that my gpu is a bit newer
than his.

I'm using Plasma, do not have xscreensaver installed, have twice as much
RAM. That could make a difference, too.

TJ

On Sat, 20 Apr 2024 18:29:08 -0400 TJ wrote:

> On 2024-04-20 13:42, David W. Hodgins wrote:
>> On Sat, 20 Apr 2024 02:49:19 -0400, Markus Robert Kessler
>> <no_reply@dipl-ing-kessler.de> wrote:
>>
>>> On Fri, 19 Apr 2024 17:00:29 -0400 David W. Hodgins wrote:
>>>
>>>> On Fri, 19 Apr 2024 16:21:10 -0400, Markus Robert Kessler
>>>> <no_reply@dipl-ing-kessler.de> wrote:
>>>> <snip>
>>>>> So, it's hard to believe that a USER setting like composit on/off in
>>>>> xfce4 can decide if the whole graphics system crashes or not.
>>>>
>>>> Do you have all updates installed?
>>>>
>>>> It was supposed to have been fixed for flightgear with
>>>> https://bugs.mageia.org/show_bug.cgi?id=32456 by turning off
>>>> compositing.
>>>>
>>>> Regards, Dave Hodgins
>>>
>>> Hi Dave,
>>>
>>> yes, everything is current version.
>>>
>>> As reported in former message, crash can be reproduced.
>>> A different installation based on Ubuntu which never crashed before,
>>> also DOES crash when HD is set into machine in question with Intel
>>> Mobile GM965/GL960. I have two machines with this GPU type and both
>>> behave in same way.
>>>
>>> This GPU, 'Intel Mobile GM965/GL960' seems not to be fully supported.
>>>
>>> I do not know if the relevant kernel driver is the only culprit, but
>>> at least this seems to be PART of the problem.
>>
>> Probably best to open a bug report. Other then bug reports I can search
>> through, and things I remember having seen, I have no experience with
>> using an intel gpu.
>>
>> Regards, Dave Hodgins
>
> Interesting.
>
> My Probook 6550b uses the Intel i915 driver, but the gpu is likely newer
> than Marcus' as the processor is a first-generation i3. But, I installed
> SuperTuxKart and ran it, anyway. This popup showed up:
>
> Your graphics driver appears to be very old. Please check if an update
> is available. SuperTuxKart recommends a driver supporting OpenGL 3.3 or
> better. The game will likely still run, but in a reduced graphics mode.
>
> The popup is wrong - it is not the driver that is at fault, as the i915
> driver covers a number of different gpus with different abilities. It is
> my gpu that doesn't support OpenGL 3.3, not the driver. It is likely the
> same with Marcus' gpu.
>
> My Plasma system didn't crash with SuperTuxKart, even when I ran the
> kart into a stone wall, but that may just be that my gpu is a bit newer
> than his.
>
> I'm using Plasma, do not have xscreensaver installed, have twice as much
> RAM. That could make a difference, too.
>
> TJ

Above message appears on my screen also. My only machine that does not is
a tower pc with NVidia PCIe card and driver downloaded from original site.

I took supertuxkart only as example, because it is quite easy to force a
crash with it.

B.t.w., you say you have more RAM. OK.
But Esprimo notebook, see former message, I took as a reference, has also
4 GB of RAM, has a different GPU and it does NOT crash.
So it's clearly a matter of properly supporting the GPU.

Interestingly, though canonical has implemented hooks to redirect you to a
kind of bug report app in case of a crash, in this case it does not even
realize that something crashed. As said, in supertuxkart the music keeps
playing, the mouse pointer can be moved, but the clock and every other
component of the desktop gets frozen. No bug report app pops up in ubuntu.

i915 driver seems to be the common / only driver for intel based GPUs,
while on a FSC Lifebook 8020 with i686 CPU and same driver, supertuxkart
completely refuses to run, but besides this, on that machine no crash
occured up to now in MGA9-32.

So, I am unsure against which component to file a bug report against.
Kernel? Xfce? Else?

Best regards,

Markus

On 4/21/24 04:36, Markus Robert Kessler wrote:
>> Interesting.
>>
>> My Probook 6550b uses the Intel i915 driver, but the gpu is likely newer
>> than Marcus' as the processor is a first-generation i3. But, I installed
>> SuperTuxKart and ran it, anyway. This popup showed up:
>>
>> Your graphics driver appears to be very old. Please check if an update
>> is available. SuperTuxKart recommends a driver supporting OpenGL 3.3 or
>> better. The game will likely still run, but in a reduced graphics mode.
>>
>> The popup is wrong - it is not the driver that is at fault, as the i915
>> driver covers a number of different gpus with different abilities. It is
>> my gpu that doesn't support OpenGL 3.3, not the driver. It is likely the
>> same with Marcus' gpu.
>>
>> My Plasma system didn't crash with SuperTuxKart, even when I ran the
>> kart into a stone wall, but that may just be that my gpu is a bit newer
>> than his.
>>
>> I'm using Plasma, do not have xscreensaver installed, have twice as much
>> RAM. That could make a difference, too.
>>
>> TJ
> Above message appears on my screen also. My only machine that does not is
> a tower pc with NVidia PCIe card and driver downloaded from original site.
>
> I took supertuxkart only as example, because it is quite easy to force a
> crash with it.
>
> B.t.w., you say you have more RAM. OK.
> But Esprimo notebook, see former message, I took as a reference, has also
> 4 GB of RAM, has a different GPU and it does NOT crash.
> So it's clearly a matter of properly supporting the GPU.
>
> Interestingly, though canonical has implemented hooks to redirect you to a
> kind of bug report app in case of a crash, in this case it does not even
> realize that something crashed. As said, in supertuxkart the music keeps
> playing, the mouse pointer can be moved, but the clock and every other
> component of the desktop gets frozen. No bug report app pops up in ubuntu.
>
> i915 driver seems to be the common / only driver for intel based GPUs,
> while on a FSC Lifebook 8020 with i686 CPU and same driver, supertuxkart
> completely refuses to run, but besides this, on that machine no crash
> occured up to now in MGA9-32.
>
> So, I am unsure against which component to file a bug report against.
> Kernel? Xfce? Else?
>
> Best regards,
>
> Markus

There are more differences in our systems than just memory. Using the
same app you used on my testing install:

$ neofetch
.°°. tom@localhost
°° .°°. -------------
.°°°. °° OS: Mageia 9 x86_64
. . Host: HP ProBook 6550b
°°° .°°°. Kernel: 6.6.22-desktop-1.mga9
.°°°. '___' Uptime: 50 secs
.'___' . Packages: 2963 (rpm)
:dkxc;'. ..,cxkd; Shell: bash 5.2.15
.dkk. kkkkkkkkkk .kkd. Resolution: 1366x768
..dkk. ';cloolc;. .kkd DE: Plasma 5.27.10
ckk. .kk; WM: KWin
xO: cOd Theme: [Plasma], Breeze [GTK2/3]
xO: lOd Icons: oxygen [Plasma], oxygen [GTK2/3]
lOO. .OO: Terminal: konsole
..k00. .00x CPU: Intel i3 M 350 (4) @ 2.266GHz
.k00; ;00O. GPU: Intel Core Processor
.lO0Kc;,,,,,,;c0KOc. Memory: 1091MiB / 7744MiB
;d00KKKKKK00d;
.,KKKK,.

As you can see, Plasma DE, lower display resolution, newer processor,
gpu integrated with the processor. And beyond what you can see, my
install is on an SSD where from your posts I believe you are using a
rust drive.

My system doesn't crash. Ever. But then, aside from the differences in
hardware there are differences in what we do with our systems.

My point is that this is the type of problem that is likely to be very
difficult to track down unless one of the devs can reproduce it. And if
no one has the same hardware that won't be easy, so it is likely to take
time. Please be patient with us.

My advice would be to file a bug without specifying a particular
component. Explain what is happening, list your hardware, explain what
crashes every time, and what crashes only part of the time. Someone will
get back to you to ask for more information. What they'll want will
depend on more or less standard troubleshooting procedures designed to
narrow things down to the source.

It may be that the problem resides in the i915 driver, but leaping to
conclusions will very possibly delay an eventual solution. Following
procedures is usually the best way.

Dave Hodgins has been at this far longer than I have, and his knowledge
is far superior. If he adds his advice, and it differs from mine, follow
his, by all means.

TJ

On Sun, 21 Apr 2024 04:36:03 -0400, Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:

> On Sat, 20 Apr 2024 18:29:08 -0400 TJ wrote:
>
>> On 2024-04-20 13:42, David W. Hodgins wrote:
>>> On Sat, 20 Apr 2024 02:49:19 -0400, Markus Robert Kessler
>>> <no_reply@dipl-ing-kessler.de> wrote:
>>>
>>>> On Fri, 19 Apr 2024 17:00:29 -0400 David W. Hodgins wrote:
>>>>
>>>>> On Fri, 19 Apr 2024 16:21:10 -0400, Markus Robert Kessler
>>>>> <no_reply@dipl-ing-kessler.de> wrote:
>>>>> <snip>
>>>>>> So, it's hard to believe that a USER setting like composit on/off in
>>>>>> xfce4 can decide if the whole graphics system crashes or not.
>>>>>
>>>>> Do you have all updates installed?
>>>>>
>>>>> It was supposed to have been fixed for flightgear with
>>>>> https://bugs.mageia.org/show_bug.cgi?id=32456 by turning off
>>>>> compositing.
>>>>>
>>>>> Regards, Dave Hodgins
>>>>
>>>> Hi Dave,
>>>>
>>>> yes, everything is current version.
>>>>
>>>> As reported in former message, crash can be reproduced.
>>>> A different installation based on Ubuntu which never crashed before,
>>>> also DOES crash when HD is set into machine in question with Intel
>>>> Mobile GM965/GL960. I have two machines with this GPU type and both
>>>> behave in same way.
>>>>
>>>> This GPU, 'Intel Mobile GM965/GL960' seems not to be fully supported.
>>>>
>>>> I do not know if the relevant kernel driver is the only culprit, but
>>>> at least this seems to be PART of the problem.
>>>
>>> Probably best to open a bug report. Other then bug reports I can search
>>> through, and things I remember having seen, I have no experience with
>>> using an intel gpu.
>>>
>>> Regards, Dave Hodgins
>>
>> Interesting.
>>
>> My Probook 6550b uses the Intel i915 driver, but the gpu is likely newer
>> than Marcus' as the processor is a first-generation i3. But, I installed
>> SuperTuxKart and ran it, anyway. This popup showed up:
>>
>> Your graphics driver appears to be very old. Please check if an update
>> is available. SuperTuxKart recommends a driver supporting OpenGL 3.3 or
>> better. The game will likely still run, but in a reduced graphics mode.
>>
>> The popup is wrong - it is not the driver that is at fault, as the i915
>> driver covers a number of different gpus with different abilities. It is
>> my gpu that doesn't support OpenGL 3.3, not the driver. It is likely the
>> same with Marcus' gpu.
>>
>> My Plasma system didn't crash with SuperTuxKart, even when I ran the
>> kart into a stone wall, but that may just be that my gpu is a bit newer
>> than his.
>>
>> I'm using Plasma, do not have xscreensaver installed, have twice as much
>> RAM. That could make a difference, too.
>>
>> TJ
>
> Above message appears on my screen also. My only machine that does not is
> a tower pc with NVidia PCIe card and driver downloaded from original site.
>
> I took supertuxkart only as example, because it is quite easy to force a
> crash with it.
>
> B.t.w., you say you have more RAM. OK.
> But Esprimo notebook, see former message, I took as a reference, has also
> 4 GB of RAM, has a different GPU and it does NOT crash.
> So it's clearly a matter of properly supporting the GPU.
>
> Interestingly, though canonical has implemented hooks to redirect you to a
> kind of bug report app in case of a crash, in this case it does not even
> realize that something crashed. As said, in supertuxkart the music keeps
> playing, the mouse pointer can be moved, but the clock and every other
> component of the desktop gets frozen. No bug report app pops up in ubuntu.
>
> i915 driver seems to be the common / only driver for intel based GPUs,
> while on a FSC Lifebook 8020 with i686 CPU and same driver, supertuxkart
> completely refuses to run, but besides this, on that machine no crash
> occured up to now in MGA9-32.
>
> So, I am unsure against which component to file a bug report against.
> Kernel? Xfce? Else?

File it against the kernel, as it's likely the i915 driver in conjunction
with that model of gpu. If debuging later leads to a different package, the
bug report can be changed to the problem package.

Regards, Dave Hodgins

On Sun, 21 Apr 2024 11:05:25 -0400 TJ wrote:

> On 4/21/24 04:36, Markus Robert Kessler wrote:
>>> Interesting.
>>>
>>> My Probook 6550b uses the Intel i915 driver, but the gpu is likely
>>> newer than Marcus' as the processor is a first-generation i3. But, I
>>> installed SuperTuxKart and ran it, anyway. This popup showed up:
>>>
>>> Your graphics driver appears to be very old. Please check if an update
>>> is available. SuperTuxKart recommends a driver supporting OpenGL 3.3
>>> or better. The game will likely still run, but in a reduced graphics
>>> mode.
>>>
>>> The popup is wrong - it is not the driver that is at fault, as the
>>> i915 driver covers a number of different gpus with different
>>> abilities. It is my gpu that doesn't support OpenGL 3.3, not the
>>> driver. It is likely the same with Marcus' gpu.
>>>
>>> My Plasma system didn't crash with SuperTuxKart, even when I ran the
>>> kart into a stone wall, but that may just be that my gpu is a bit
>>> newer than his.
>>>
>>> I'm using Plasma, do not have xscreensaver installed, have twice as
>>> much RAM. That could make a difference, too.
>>>
>>> TJ
>> Above message appears on my screen also. My only machine that does not
>> is a tower pc with NVidia PCIe card and driver downloaded from original
>> site.
>>
>> I took supertuxkart only as example, because it is quite easy to force
>> a crash with it.
>>
>> B.t.w., you say you have more RAM. OK.
>> But Esprimo notebook, see former message, I took as a reference, has
>> also 4 GB of RAM, has a different GPU and it does NOT crash.
>> So it's clearly a matter of properly supporting the GPU.
>>
>> Interestingly, though canonical has implemented hooks to redirect you
>> to a kind of bug report app in case of a crash, in this case it does
>> not even realize that something crashed. As said, in supertuxkart the
>> music keeps playing, the mouse pointer can be moved, but the clock and
>> every other component of the desktop gets frozen. No bug report app
>> pops up in ubuntu.
>>
>> i915 driver seems to be the common / only driver for intel based GPUs,
>> while on a FSC Lifebook 8020 with i686 CPU and same driver,
>> supertuxkart completely refuses to run, but besides this, on that
>> machine no crash occured up to now in MGA9-32.
>>
>> So, I am unsure against which component to file a bug report against.
>> Kernel? Xfce? Else?
>>
>> Best regards,
>>
>> Markus
>
> There are more differences in our systems than just memory. Using the
> same app you used on my testing install:
>
> $ neofetch
> .°°. tom@localhost
> °° .°°. ------------- .°°°. °° OS: Mageia 9
> x86_64 . . Host: HP ProBook 6550b
> °°° .°°°. Kernel: 6.6.22-desktop-1.mga9
> .°°°. '___' Uptime: 50 secs
> .'___' . Packages: 2963 (rpm)
> :dkxc;'. ..,cxkd; Shell: bash 5.2.15
> .dkk. kkkkkkkkkk .kkd. Resolution: 1366x768
> .dkk. ';cloolc;. .kkd DE: Plasma 5.27.10 ckk. .kk;
> WM: KWin xO: cOd Theme: [Plasma], Breeze [GTK2/3]
> xO: lOd Icons: oxygen [Plasma], oxygen [GTK2/3]
> lOO. .OO: Terminal: konsole .k00. .00x
> CPU: Intel i3 M 350 (4) @ 2.266GHz
> .k00; ;00O. GPU: Intel Core Processor
> .lO0Kc;,,,,,,;c0KOc. Memory: 1091MiB / 7744MiB
> ;d00KKKKKK00d;
> .,KKKK,.
>
>
> As you can see, Plasma DE, lower display resolution, newer processor,
> gpu integrated with the processor. And beyond what you can see, my
> install is on an SSD where from your posts I believe you are using a
> rust drive.
>
> My system doesn't crash. Ever. But then, aside from the differences in
> hardware there are differences in what we do with our systems.
>
> My point is that this is the type of problem that is likely to be very
> difficult to track down unless one of the devs can reproduce it. And if
> no one has the same hardware that won't be easy, so it is likely to take
> time. Please be patient with us.
>
> My advice would be to file a bug without specifying a particular
> component. Explain what is happening, list your hardware, explain what
> crashes every time, and what crashes only part of the time. Someone will
> get back to you to ask for more information. What they'll want will
> depend on more or less standard troubleshooting procedures designed to
> narrow things down to the source.
>
> It may be that the problem resides in the i915 driver, but leaping to
> conclusions will very possibly delay an eventual solution. Following
> procedures is usually the best way.
>
> Dave Hodgins has been at this far longer than I have, and his knowledge
> is far superior. If he adds his advice, and it differs from mine, follow
> his, by all means.

OK, I'll follow the advice.

B.t.w., all my machines for daily work have SSDs, since I do not want them
to get damaged while moving. Besides this, they are significantly faster.

Reason behind and why I'd really appreciate the issue to be solved, is
because it's not only about this single box. I have 3 of them :-)

Thanks,
best regards,

Markus

On Sun, 21 Apr 2024 11:04:19 -0400 David W. Hodgins wrote:

> On Sun, 21 Apr 2024 04:36:03 -0400, Markus Robert Kessler
> <no_reply@dipl-ing-kessler.de> wrote:
>
>> On Sat, 20 Apr 2024 18:29:08 -0400 TJ wrote:
>>
>>> On 2024-04-20 13:42, David W. Hodgins wrote:
>>>> On Sat, 20 Apr 2024 02:49:19 -0400, Markus Robert Kessler
>>>> <no_reply@dipl-ing-kessler.de> wrote:
>>>>
>>>>> On Fri, 19 Apr 2024 17:00:29 -0400 David W. Hodgins wrote:
>>>>>
>>>>>> On Fri, 19 Apr 2024 16:21:10 -0400, Markus Robert Kessler
>>>>>> <no_reply@dipl-ing-kessler.de> wrote:
>>>>>> <snip>
>>>>>>> So, it's hard to believe that a USER setting like composit on/off
>>>>>>> in xfce4 can decide if the whole graphics system crashes or not.
>>>>>>
>>>>>> Do you have all updates installed?
>>>>>>
>>>>>> It was supposed to have been fixed for flightgear with
>>>>>> https://bugs.mageia.org/show_bug.cgi?id=32456 by turning off
>>>>>> compositing.
>>>>>>
>>>>>> Regards, Dave Hodgins
>>>>>
>>>>> Hi Dave,
>>>>>
>>>>> yes, everything is current version.
>>>>>
>>>>> As reported in former message, crash can be reproduced.
>>>>> A different installation based on Ubuntu which never crashed before,
>>>>> also DOES crash when HD is set into machine in question with Intel
>>>>> Mobile GM965/GL960. I have two machines with this GPU type and both
>>>>> behave in same way.
>>>>>
>>>>> This GPU, 'Intel Mobile GM965/GL960' seems not to be fully
>>>>> supported.
>>>>>
>>>>> I do not know if the relevant kernel driver is the only culprit, but
>>>>> at least this seems to be PART of the problem.
>>>>
>>>> Probably best to open a bug report. Other then bug reports I can
>>>> search through, and things I remember having seen, I have no
>>>> experience with using an intel gpu.
>>>>
>>>> Regards, Dave Hodgins
>>>
>>> Interesting.
>>>
>>> My Probook 6550b uses the Intel i915 driver, but the gpu is likely
>>> newer than Marcus' as the processor is a first-generation i3. But, I
>>> installed SuperTuxKart and ran it, anyway. This popup showed up:
>>>
>>> Your graphics driver appears to be very old. Please check if an update
>>> is available. SuperTuxKart recommends a driver supporting OpenGL 3.3
>>> or better. The game will likely still run, but in a reduced graphics
>>> mode.
>>>
>>> The popup is wrong - it is not the driver that is at fault, as the
>>> i915 driver covers a number of different gpus with different
>>> abilities. It is my gpu that doesn't support OpenGL 3.3, not the
>>> driver. It is likely the same with Marcus' gpu.
>>>
>>> My Plasma system didn't crash with SuperTuxKart, even when I ran the
>>> kart into a stone wall, but that may just be that my gpu is a bit
>>> newer than his.
>>>
>>> I'm using Plasma, do not have xscreensaver installed, have twice as
>>> much RAM. That could make a difference, too.
>>>
>>> TJ
>>
>> Above message appears on my screen also. My only machine that does not
>> is a tower pc with NVidia PCIe card and driver downloaded from original
>> site.
>>
>> I took supertuxkart only as example, because it is quite easy to force
>> a crash with it.
>>
>> B.t.w., you say you have more RAM. OK.
>> But Esprimo notebook, see former message, I took as a reference, has
>> also 4 GB of RAM, has a different GPU and it does NOT crash.
>> So it's clearly a matter of properly supporting the GPU.
>>
>> Interestingly, though canonical has implemented hooks to redirect you
>> to a kind of bug report app in case of a crash, in this case it does
>> not even realize that something crashed. As said, in supertuxkart the
>> music keeps playing, the mouse pointer can be moved, but the clock and
>> every other component of the desktop gets frozen. No bug report app
>> pops up in ubuntu.
>>
>> i915 driver seems to be the common / only driver for intel based GPUs,
>> while on a FSC Lifebook 8020 with i686 CPU and same driver,
>> supertuxkart completely refuses to run, but besides this, on that
>> machine no crash occured up to now in MGA9-32.
>>
>> So, I am unsure against which component to file a bug report against.
>> Kernel? Xfce? Else?
>
> File it against the kernel, as it's likely the i915 driver in
> conjunction with that model of gpu. If debuging later leads to a
> different package, the bug report can be changed to the problem package.
>
> Regards, Dave Hodgins

OK, done

==> https://bugs.mageia.org/show_bug.cgi?id=33128

Thanks again,
best regards,

Markus