[Bug 2375791] New: [abrt] blender: GHOST_NDOFManagerUnix::processEvents(): blender killed by SIGABRT

https://bugzilla.redhat.com/show_bug.cgi?id=2375791

Bug ID: 2375791
           Summary: [abrt] blender:
                    GHOST_NDOFManagerUnix::processEvents(): blender killed
                    by SIGABRT
           Product: Fedora
           Version: 41
          Hardware: x86_64
            Status: NEW
        Whiteboard: abrt_hash:c9951f2dace18574df221bd1fb233076e296f8e1;VAR
                    IANT_ID=workstation;
         Component: blender
          Assignee: [e-mail]
          Reporter: [e-mail]
        QA Contact: [e-mail]
                CC: [e-mail],
                    [e-mail],
                    [e-mail],
                    [e-mail], [e-mail],
                    [e-mail]
  Target Milestone: ---
    Classification: Fedora

Description of problem:
Program was idle at the time, was typing in another window when CPU suddenly
spiked, fans spun up and I knew Blender was going to dump.  It does this
frequently.

Version-Release number of selected component:
blender-1:4.4.3-1.fc41

Additional info:
reporter:       libreport-2.17.15
kernel:         6.14.11-200.fc41.x86_64
crash_function: GHOST_NDOFManagerUnix::processEvents
reason:         blender killed by SIGABRT
uid:            6669
backtrace_rating: 4
rootdir:        /
type:           CCpp
runlevel:       N 5
journald_cursor:
s=67253e327100462399eb5e5dab456e91;i=d02bbc;b=e79b438e79ce4cff825227442addd71c;m=145cc8370f;t=63804868cc679;x=b8bc288c86857079
package:        blender-1:4.4.3-1.fc41
cmdline:        /usr/bin/blender
/export/home/jas/Downloads/Games/3D/UK/WIP/Erebus/erebus-0.24.blend
executable:     /usr/bin/blender
comment:        Program was idle at the time, was typing in another window when
CPU suddenly spiked, fans spun up and I knew Blender was going to dump.  It
does this frequently.
dso_list:       /usr/bin/blender blender-1:4.4.3-1.fc41.x86_64 (Fedora Project)
1747244638

Truncated backtrace:
Thread no. 0 (5 frames)
 #4 GHOST_NDOFManagerUnix::processEvents at
/usr/src/debug/blender-4.4.3-1.fc41.x86_64/intern/ghost/intern/GHOST_NDOFManagerUnix.cc:128
 #6 GHOST_SystemX11::processEvents at
/usr/src/debug/blender-4.4.3-1.fc41.x86_64/intern/ghost/intern/GHOST_SystemX11.cc:738
 #7 GHOST_ProcessEvents at
/usr/src/debug/blender-4.4.3-1.fc41.x86_64/intern/ghost/intern/GHOST_C-api.cc:264
 #8 wm_window_events_process at
/usr/src/debug/blender-4.4.3-1.fc41.x86_64/source/blender/windowmanager/intern/wm_window.cc:1912
 #9 WM_main at
/usr/src/debug/blender-4.4.3-1.fc41.x86_64/source/blender/windowmanager/intern/wm.cc:636

[Bug 2375791] [abrt] blender: GHOST_NDOFManagerUnix::processEvents(): blender killed by SIGABRT

https://bugzilla.redhat.com/show_bug.cgi?id=2375791

Luya Tshimbalanga  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |needinfo?([e-mail]
                   |                            |)

--- Comment #13 from Luya Tshimbalanga  ---
Hello,

Based on the traceback, the issue seems occuring in X11 session. May I ask
which desktop environment you run and try running on a Wayland session to see
if the issue occurs?

[Bug 2375791] [abrt] blender: GHOST_NDOFManagerUnix::processEvents(): blender killed by SIGABRT

https://bugzilla.redhat.com/show_bug.cgi?id=2375791

--- Comment #14 from Jason Herring  ---
Program was idle at the time, was typing in another window when CPU suddenly
spiked, fans spun up and I knew Blender was going to dump.  It does this
frequently.

reporter:       libreport-2.17.15
kernel:         6.14.11-200.fc41.x86_64
crash_function: GHOST_NDOFManagerUnix::processEvents
reason:         blender killed by SIGABRT
uid:            6669
backtrace_rating: 4
rootdir:        /
type:           CCpp
runlevel:       N 5
journald_cursor:
s=67253e327100462399eb5e5dab456e91;i=d02bbc;b=e79b438e79ce4cff825227442addd71c;m=145cc8370f;t=63804868cc679;x=b8bc288c86857079
package:        blender-1:4.4.3-1.fc41
cmdline:        /usr/bin/blender
/export/home/jas/Downloads/Games/3D/UK/WIP/Erebus/erebus-0.24.blend
executable:     /usr/bin/blender
comment:        Program was idle at the time, was typing in another window when
CPU suddenly spiked, fans spun up and I knew Blender was going to dump.  It
does this frequently.
dso_list:       /usr/bin/blender blender-1:4.4.3-1.fc41.x86_64 (Fedora Project)
1747244638

[Bug 2375791] [abrt] blender: GHOST_NDOFManagerUnix::processEvents(): blender killed by SIGABRT

https://bugzilla.redhat.com/show_bug.cgi?id=2375791

Jason Herring  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|needinfo?([e-mail] |
                   |)                           |

--- Comment #15 from Jason Herring  ---
This machine was a fresh install of Fedora 41 using Wayland.  I have an Nvidia
3060 card with dual monitors.  I experienced all I can describe as a myriad of
problems across multiple applications including general window management in
the dual-monitor config, browsers crashing/graphic artifacts, and problems with
Blender and Kdenlive.  Hours were spent troubleshooting.  I even installed an
older graphics card as a test.  I have posts in Fedora forums I can link if you
like.  When one responder asked am I using "Wayland" and I replied yes, he said
that many of these issues are known with Wayland and Nvidia and I should switch
to X11.
I made the switch to X11 and everything worked basically flawlessly.  I can't
go to Wayland until it plays well with Nvidia.
The crashing I'm experiencing now I did not get with the version of Blender
installed at the time I built the Fedora 41 system - was 4.1 or 4.3, I don't
remember.  This has been an epidemic in 4.4.  Each Nvidia driver update I get I
hope will be a solution to the Blender crashing problem, but no joy.

[Bug 2375791] [abrt] blender: GHOST_NDOFManagerUnix::processEvents(): blender killed by SIGABRT

https://bugzilla.redhat.com/show_bug.cgi?id=2375791

--- Comment #16 from Adam Williamson  ---
This message is a reminder that Fedora Linux 41 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 41 on
2025-12-15.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with
a
'version' of '41'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 41 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

[Bug 2375791] [abrt] blender: GHOST_NDOFManagerUnix::processEvents(): blender killed by SIGABRT

https://bugzilla.redhat.com/show_bug.cgi?id=2375791

Samyak Jain (RedHat)  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |EOL
             Status|NEW                         |CLOSED
        Last Closed|                            |2025-12-17 05:29:59

--- Comment #17 from Samyak Jain (RedHat)  ---
Fedora Linux 41 entered end-of-life (EOL) status on 2025-12-15.

Fedora Linux 41 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora
Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.