Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-6894

GIMP shouldn't be trying to debug warnings

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • gimp
    • None
    • None
    • rhel-sst-cs-base-utils
    • ssg_core_services
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • If docs needed, set a value
    • None

      Description of problem:
      Currently when GIMP encounters a warning it tries to debug and launches gdb, which results in the program hanging up for a while. Users might assume the program has crashed and force quit, resulting in a lot of data. etc/gimprc.in should be patched to change "(debug-policy warning)" to "(debug-policy critical)"

      Version-Release number of selected component (if applicable):
      2.99.8-3.el9

      How reproducible:
      Whenever GIMP encounters an non-critical warning

      Actual results:
      GIMP tries to attach gdb, resulting in high CPU usage and a period of non-responsiveness.

      Expected results:
      GIMP should not try to debug a non-critical warning in a production environment.

      Solution:
      Patch etc/gimprc.in to change the debug-policy setting from "warning" to "critical".

              jridky Josef Řídký
              prandrews09 Phillip Andrews (Inactive)
              Josef Řídký Josef Řídký
              Desktop QE Desktop QE
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: