Hide Forgot
Description of problem: pinpoint application crashes instantly when executed in the speakermode. Version-Release number of selected component (if applicable): pinpoint-0.1.8-2.fc24.x86_64 How reproducible: 100% Steps to Reproduce: 1. pinpoint --speakermode /usr/share/doc/pinpoint/introduction.pin 2. speakermode window pops-up and then crashes Additional info: $ pinpoint --speakermode /usr/share/doc/pinpoint/introduction.pin (pinpoint:12899): Gdk-ERROR **: The program 'pinpoint' received an X Window System error. This probably reflects a bug in the program. The error was 'GLXBadDrawable'. (Details: serial 476 error_code 169 request_code 154 (GLX) minor_code 29) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Trace/breakpoint trap (core dumped) $ gdb --args pinpoint --speakermode /usr/share/doc/pinpoint/introduction.pin gdb$ run gdb$ backtrace #0 0x00007ffff1cb715b in g_logv () at /lib64/libglib-2.0.so.0 #1 0x00007ffff1cb72cf in g_log () at /lib64/libglib-2.0.so.0 #2 0x00007ffff5dae55a in _gdk_x11_display_error_event () at /lib64/libgdk-3.so.0 #3 0x00007ffff5dba7c3 in gdk_x_error () at /lib64/libgdk-3.so.0 #4 0x00007ffff3f2e57d in _XError () at /lib64/libX11.so.6 #5 0x00007fffede1cd94 in __glXSendError () at /lib64/libGL.so.1 #6 0x00007fffede1fc7d in GetDrawableAttribute () at /lib64/libGL.so.1 #7 0x00007ffff62cea49 in _cogl_winsys_onscreen_get_buffer_age () at /lib64/libcogl.so.20 #8 0x00007ffff6b95669 in clutter_stage_cogl_redraw () at /lib64/libclutter-1.0.so.0 #9 0x00007ffff6b988dd in clutter_stage_gdk_redraw () at /lib64/libclutter-1.0.so.0 #10 0x00007ffff6c025c7 in _clutter_stage_do_update () at /lib64/libclutter-1.0.so.0 #11 0x00007ffff6b980d5 in clutter_master_clock_gdk_update () at /lib64/libclutter-1.0.so.0 #12 0x00007ffff1f843e5 in g_closure_invoke () at /lib64/libgobject-2.0.so.0 #13 0x00007ffff1f96432 in signal_emit_unlocked_R () at /lib64/libgobject-2.0.so.0 #14 0x00007ffff1f9f05f in g_signal_emit_valist () at /lib64/libgobject-2.0.so.0 #15 0x00007ffff1f9f43f in g_signal_emit () at /lib64/libgobject-2.0.so.0 #16 0x00007ffff5d90051 in gdk_frame_clock_paint_idle () at /lib64/libgdk-3.so.0 #17 0x00007ffff5d7e418 in gdk_threads_dispatch () at /lib64/libgdk-3.so.0 #18 0x00007ffff1cb1133 in g_timeout_dispatch () at /lib64/libglib-2.0.so.0 #19 0x00007ffff1cb06ba in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #20 0x00007ffff1cb0a70 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #21 0x00007ffff1cb0b1c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #22 0x00007ffff249848d in g_application_run () at /lib64/libgio-2.0.so.0 #23 0x00005555555592f4 in main () $ lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b) $lshw *-display description: VGA compatible controller product: Haswell-ULT Integrated Graphics Controller vendor: Intel Corporation0 physical id: 2 bus info: pci@0000:00:02.0 version: 0bz width: 64 bitsvga_controller bus_master cap_list rom clock: 33MHzn: driver=i915 latency=0 capabilities: vga_controller bus_master cap_list rom000000-cfffffff ioport:3000(size=64) mem configuration: driver=i915 latency=0 resources: irq:47 memory:d0000000-d03fffff memory:c0000000-cfffffff ioport:3000(size=64) mem
pinpoint pretty much crashes for me in any desktop environment except for MATE. I filed a bug report against GNOME once and they made me file it upstream where it got ignored forever. I think pinpoint is basically dead these days... which is a shame because when using it in MATE, it does what you want it to do quite well. (reasonable looking presentations from a text file with a minimal amount of markup)
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Closing this bug is wrong since it applies to all releases shipping pinpoint.