Bug 2279636 - Upgraded from 39 to 40, geeqie has memory issue
Summary: Upgraded from 39 to 40, geeqie has memory issue
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: geeqie
Version: 40
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Matthew Miller
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-05-07 20:05 UTC by Ben
Modified: 2025-02-11 03:09 UTC (History)
3 users (show)

Fixed In Version: geeqie-2.5-5.fc41 geeqie-2.5-5.fc40
Clone Of:
Environment:
Last Closed: 2025-02-11 03:03:22 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ben 2024-05-07 20:05:00 UTC
When type geeqie in the terminal, I received:
Geeqie fatal error
Signal: Invalid memory reference
Code: Address not mapped
Address: 0x00007effb9442640
Segmentation fault (core dumped)



Reproducible: Always

Steps to Reproduce:
1. install geeqie
2. run geeqie



My fedora was run on vmware 17.5

Run with gdb and received the debug trace:

#0  0x00007fffe1564640 in ??? ()
#1  0x00007ffff582960f in XGetErrorText (dpy=0x55555579b6e0, code=2, buffer=0x7fffffffd280 "BadValue (integer parameter out of range for operation)", nbytes=63)
    at /usr/src/debug/libX11-1.8.9-1.fc40.x86_64/src/ErrDes.c:121
#2  XGetErrorText (dpy=0x55555579b6e0, code=2, buffer=buffer@entry=0x7fffffffd280 "BadValue (integer parameter out of range for operation)", nbytes=nbytes@entry=63)
    at /usr/src/debug/libX11-1.8.9-1.fc40.x86_64/src/ErrDes.c:100
#3  0x00007ffff7f3df32 in _gdk_x11_display_error_event (error=0x7fffffffd320, display=0x5555557acce0 [GdkX11Display]) at ../gdk/x11/gdkdisplay-x11.c:2744
#4  _gdk_x11_display_error_event (error=0x7fffffffd320, display=0x5555557acce0 [GdkX11Display]) at ../gdk/x11/gdkdisplay-x11.c:2711
#5  gdk_x_error (error=0x7fffffffd320, xdisplay=<optimized out>) at ../gdk/x11/gdkmain-x11.c:296
#6  gdk_x_error (xdisplay=<optimized out>, error=0x7fffffffd320) at ../gdk/x11/gdkmain-x11.c:258
#7  0x00007ffff584c576 in _XError (dpy=dpy@entry=0x55555579b6e0, rep=rep@entry=0x555555988820) at /usr/src/debug/libX11-1.8.9-1.fc40.x86_64/src/XlibInt.c:1494
#8  0x00007ffff584c68f in handle_error (dpy=0x55555579b6e0, err=0x555555988820, in_XReply=<optimized out>) at /usr/src/debug/libX11-1.8.9-1.fc40.x86_64/src/xcb_io.c:211
#9  0x00007ffff584c74d in handle_response (dpy=dpy@entry=0x55555579b6e0, response=0x555555988820, in_XReply=in_XReply@entry=0) at /usr/src/debug/libX11-1.8.9-1.fc40.x86_64/src/xcb_io.c:403
#10 0x00007ffff584c7d2 in _XEventsQueued (dpy=0x55555579b6e0, mode=mode@entry=1) at /usr/src/debug/libX11-1.8.9-1.fc40.x86_64/src/xcb_io.c:442
#11 0x00007ffff584c88e in _XFlush (dpy=<optimized out>) at /usr/src/debug/libX11-1.8.9-1.fc40.x86_64/src/xcb_io.c:611
#12 0x00007ffff584cb9d in _XGetRequest (dpy=dpy@entry=0x55555579b6e0, type=type@entry=4 '\004', len=len@entry=12) at /usr/src/debug/libX11-1.8.9-1.fc40.x86_64/src/XlibInt.c:1778
#13 0x00007ffff563ff02 in XRRSelectInput (dpy=0x55555579b6e0, window=712, mask=11) at /usr/src/debug/libXrandr-1.5.4-3.fc40.x86_64/src/Xrandr.c:443
#14 0x00007ffff528828c in _cogl_xlib_renderer_connect (renderer=renderer@entry=0x5555558fb5b0, error=error@entry=0x7fffffffd5d0) at /usr/src/debug/cogl-1.22.8-10.fc40.x86_64/cogl/cogl-xlib-renderer.c:547
#15 0x00007ffff5288406 in _cogl_winsys_renderer_connect (renderer=0x5555558fb5b0, error=0x7fffffffd5d0) at winsys/cogl-winsys-glx.c:744
#16 0x00007ffff524193f in cogl_renderer_connect (renderer=0x5555558fb5b0, error=error@entry=0x7fffffffd660) at /usr/src/debug/cogl-1.22.8-10.fc40.x86_64/cogl/cogl-renderer.c:687
#17 0x00007ffff706764a in clutter_backend_do_real_create_context (error=0x7fffffffd658, driver_id=COGL_DRIVER_ANY, backend=0x555555884c40 [ClutterBackendGdk])
    at /usr/src/debug/clutter-1.26.4-13.fc40.x86_64/clutter/clutter-backend.c:279
#18 clutter_backend_real_create_context (backend=0x555555884c40 [ClutterBackendGdk], error=0x7fffffffd820) at /usr/src/debug/clutter-1.26.4-13.fc40.x86_64/clutter/clutter-backend.c:414
#19 0x00007ffff708dce7 in _clutter_backend_create_context (error=0x7fffffffd820, backend=<optimized out>) at /usr/src/debug/clutter-1.26.4-13.fc40.x86_64/clutter/clutter-backend.c:901
#20 _clutter_feature_init (error=0x7fffffffd820) at /usr/src/debug/clutter-1.26.4-13.fc40.x86_64/clutter/clutter-feature.c:107
#21 clutter_init_real (error=error@entry=0x7fffffffd820) at /usr/src/debug/clutter-1.26.4-13.fc40.x86_64/clutter/clutter-main.c:1418
#22 0x00007ffff708e088 in post_parse_hook (context=<optimized out>, group=<optimized out>, data=<optimized out>, error=0x7fffffffd820) at /usr/src/debug/clutter-1.26.4-13.fc40.x86_64/clutter/clutter-main.c:1584
#23 0x00007ffff7221201 in g_option_context_parse (context=context@entry=0x555555940120, argc=argc@entry=0x7fffffffd8cc, argv=argv@entry=0x7fffffffd8c0, error=error@entry=0x7fffffffd820) at ../glib/goption.c:2067
#24 0x00007ffff708e2e9 in clutter_parse_args (error=0x7fffffffd818, argv=0x7fffffffd8c0, argc=0x7fffffffd8cc) at /usr/src/debug/clutter-1.26.4-13.fc40.x86_64/clutter/clutter-main.c:1804
#25 clutter_init (argc=0x7fffffffd8cc, argv=0x7fffffffd8c0) at /usr/src/debug/clutter-1.26.4-13.fc40.x86_64/clutter/clutter-main.c:1866
#26 0x000055555557de6b in main (argc=<optimized out>, argv=<optimized out>) at ../src/main.cc:1352

Comment 1 Richard Nolde 2024-05-19 17:15:55 UTC
I am having the same problem on my main desktop machine but not my laptop, both of which were recently upgraded with dnf system-upgrade --releasever=40 download, etc. Both systems are now running Fedora 40 XFCE with full hardware level installs, ie, not VM instances. The laptop has fewer programs installed and isn't used for development due to limited screen size and 8 Gb Ram. The desktop is my development machine, with 16 Gb Ram, two HDPI displays and the proprietary Nvidia video driver for an older Nvidia 1650 GTX card. I have removed any "unknown" values from the geeqie XML configuration file. I've removed the thumbnail image cache. I've run rpm -qi requires geegie and checked to see that all the pre-reqesites are installed on the development machine.

Geeqie worked flawlessly on Fedora 39 and all earlier versions for as long as Geeqie has been around, with XFCE on this same machine. I played around with XFCE settings for HDPI monitors recently but the problem has been there since the upgrade even before I tweaked any display parameters. I can run ALL my other graphics editors, viewers, video editing software, browsers, etc, without crashing.

I've run dnf -y update multiple times and rebooted to clear everything over the last week.

Let me know if I can provide additional information on the hardware, software, or anything else.

Richard Nolde
rpm -qi --requires geeqie
Name        : geeqie
Version     : 2.2
Release     : 1.fc40
Architecture: x86_64
Install Date: Sun 19 May 2024 10:44:24 AM MDT
Group       : Unspecified
Size        : 5649556
License     : GPLv2+
Signature   : RSA/SHA256, Mon 29 Jan 2024 03:49:16 AM MST, Key ID 0727707ea15b79cc
Source RPM  : geeqie-2.2-1.fc40.src.rpm
Build Date  : Mon 29 Jan 2024 03:44:34 AM MST
Build Host  : buildhw-x86-05.iad2.fedoraproject.org
Packager    : Fedora Project
Vendor      : Fedora Project
URL         : https://www.geeqie.org
Bug URL     : https://bugz.fedoraproject.org/geeqie
Summary     : Image browser and viewer
....

geeqie

(geeqie:9655): GLib-GObject-CRITICAL **: 10:59:37.157: instance with invalid (NULL) class pointer

(geeqie:9655): GLib-GObject-CRITICAL **: 10:59:37.157: signal_emit_valist_unlocked: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(geeqie:9655): GLib-GObject-CRITICAL **: 10:59:37.157: g_object_set_qdata: assertion 'G_IS_OBJECT (object)' failed

(geeqie:9655): GLib-GObject-CRITICAL **: 10:59:37.157: instance with invalid (NULL) class pointer

(geeqie:9655): GLib-GObject-CRITICAL **: 10:59:37.157: g_signal_handlers_destroy: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(geeqie:9655): GLib-GObject-CRITICAL **: 10:59:37.157: instance with invalid (NULL) class pointer

(geeqie:9655): GLib-GObject-CRITICAL **: 10:59:37.157: g_signal_handlers_destroy: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Geeqie fatal error
Signal: Invalid memory reference
Code: Address not mapped
Address: 0x0000000000000030
geeqie(+0x91e28)[0x55f99d21ae28]
/lib64/libc.so.6(+0x40710)[0x7fd5d7453710]
/lib64/libgobject-2.0.so.0(g_object_unref+0x307)[0x7fd5d8a84a07]
geeqie(+0x6bd34)[0x55f99d1f4d34]
geeqie(+0x868ce)[0x55f99d20f8ce]
geeqie(+0x86d6f)[0x55f99d20fd6f]
geeqie(+0x7cbff)[0x55f99d205bff]
geeqie(+0xff4c5)[0x55f99d2884c5]
geeqie(+0x7f754)[0x55f99d208754]
geeqie(+0xb6a1f)[0x55f99d23fa1f]
geeqie(+0xb2658)[0x55f99d23b658]
/lib64/libglib-2.0.so.0(+0x60b7c)[0x7fd5d8b22b7c]
/lib64/libglib-2.0.so.0(g_markup_parse_context_parse+0x10b1)[0x7fd5d8b27151]
geeqie(+0xbaff1)[0x55f99d243ff1]
geeqie(+0xbb064)[0x55f99d244064]
geeqie(+0x2a8f6)[0x55f99d1b38f6]
/lib64/libc.so.6(+0x2a088)[0x7fd5d743d088]
/lib64/libc.so.6(__libc_start_main+0x8b)[0x7fd5d743d14b]
geeqie(+0x2bff5)[0x55f99d1b4ff5]

Comment 2 Richard Nolde 2024-05-19 18:50:05 UTC
Update: I checked two more Fedora 40 Xfce machines I have. 
First, a Toshiba Satellite laptop with a virgin install of Fedora 40 Xfce. This laptop works fine with Geeqie, just as the older Gateway laptop does. Both laptops use integrated CPU graphics processors, not dedicated video cards. 

Next, an older Dell Optiplex backup machine which has an Nvidia Gtx 530 card and all the Nvidia drivers installed but is using the Nouveau driver if lshw is to be believed. I confirmed this with the Nvidia-Xserver configuration application. Geeqie crashes when started via the desktop icon or the command line with the same reports as seen above.

Comment 3 Fedora Update System 2025-01-31 23:01:01 UTC
FEDORA-2025-4a42f61d77 (geeqie-2.5-3.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-4a42f61d77

Comment 4 Fedora Update System 2025-01-31 23:01:25 UTC
FEDORA-2025-d76719833b (geeqie-2.5-3.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-d76719833b

Comment 5 Fedora Update System 2025-02-01 06:00:16 UTC
FEDORA-2025-4a42f61d77 has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-4a42f61d77`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-4a42f61d77

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2025-02-01 17:45:03 UTC
FEDORA-2025-d76719833b has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-d76719833b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-d76719833b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2025-02-03 02:07:29 UTC
FEDORA-2025-4a42f61d77 has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-4a42f61d77`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-4a42f61d77

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2025-02-03 02:25:19 UTC
FEDORA-2025-d76719833b has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-d76719833b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-d76719833b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2025-02-11 03:03:22 UTC
FEDORA-2025-4a42f61d77 (geeqie-2.5-5.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2025-02-11 03:09:04 UTC
FEDORA-2025-d76719833b (geeqie-2.5-5.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.


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