Bug 2336870 - Error (crash) with eglinfo when launching it (command line or GUI)
Summary: Error (crash) with eglinfo when launching it (command line or GUI)
Keywords:
Status: CLOSED DUPLICATE of bug 2337082
Alias: None
Product: Fedora
Classification: Fedora
Component: mesa
Version: 41
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-01-10 07:13 UTC by MicMor
Modified: 2025-01-13 15:38 UTC (History)
12 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-01-13 15:38:42 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description MicMor 2025-01-10 07:13:15 UTC
start eglinfo 

Device #2:

EGL device extensions string:
    EGL_EXT_device_drm, EGL_EXT_device_drm_render_node
Platform Device platform:
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
Erreur de segmentation (core dumped)

Reproducible: Always

Steps to Reproduce:
1. start eglinfo in command line or through GUI of the information center of plasma

Actual Results:  
crashed


config:

[42COS: Fedora Linux 41 (KDE Plasma) x86_64
[42CHost: GP72 7RE (REV:1.0)
[42CKernel: Linux 6.12.9-200.fc41.x86_64
[42CDisplay (2460G5): 1920x1080 @ 60 Hz in 24" [External]
[42CDisplay (CMN1735): 1920x1080 @ 60 Hz in 17" [Built-in] *
[42CDE: KDE Plasma 6.2.5
WM: KWin (Wayland)
WM Theme: Breeze
Theme: Breeze (Light) [Qt], Breeze [GTK3]
Icons: Papirus [Qt], Papirus [GTK3/4]
Cursor: breeze (24px)
Terminal: konsole 24.12.1
CPU: Intel(R) Core(TM) i5-7300HQ (4) @ 3.50 GHz
GPU 1: NVIDIA GeForce GTX 1050 Ti Mobile [Discrete]
GPU 2: Intel HD Graphics 630 @ 1.00 GHz [Integrated]
Battery (BIF0_9): 98% [AC Connected]
Locale: fr_FR.UTF-8

egl-utils Version:  9.0.0.8
mesa: 24.3.2.2
GPU nvidia: 565.77.1

Comment 1 José Expósito 2025-01-13 12:20:08 UTC
This looks similar to https://bugzilla.redhat.com/show_bug.cgi?id=2337082

Do you see a similar backtrace?

Comment 2 MicMor 2025-01-13 13:07:11 UTC
No, because I posted the bug (2337082) without finding a way to send the report. I found the solution later to send this report(2336870) by unchecking non-public sending.

But the backtrace must be the same, same hardware (same pc)

Comment 3 MicMor 2025-01-13 13:09:05 UTC
Inversion in report numbers

No, because I posted the bug (2336870) without finding a way to send the report. I found the solution later to send this report(2337082) by unchecking non-public sending.

But the backtrace must be the same, same hardware (same pc)

Comment 4 José Expósito 2025-01-13 15:38:42 UTC
Oh! I didn't notice that you created both reports. Let's close this one as duplicated of https://bugzilla.redhat.com/show_bug.cgi?id=2337082

*** This bug has been marked as a duplicate of bug 2337082 ***


Note You need to log in before you can comment on or make changes to this bug.