Menu ▾ ▴

#1801 Matrix Editor: zoom segfaults

None
open
nobody
None
5
2026-10-21
2026-10-17
No

render glyph failed err=62 face=0x55ed095a2d80, glyph=38
zsh: segmentation fault (core dumped) rosegarden

https://drive.google.com/drive/folders/1kpBHJ5qm1ryybLGunnmTSSCH-XyFEKpk?usp=sharing

Related

Bugs: #1801

Discussion

  • Kai Griswold

    Kai Griswold - 2026-10-17

    NOTE: Bug reporting guidelines are down with a 404 so I didn't know

     
  • Philip Leishman

    Philip Leishman - 2026-10-17

    Thanks for the bug report. I can see in the screencast what is happening but no idea why. I cannot reproduce the crash.
    The error message with "render glyph failed" seems to indicate a low level font rendering error (?)
    What Rosegarden version are you using ?
    What linux distribution are you using ?
    Do you have the possibility to compile Rosegarden as a Debug version ?

     
  • Philip Leishman

    Philip Leishman - 2026-10-17

    I can confirm the 404 on "Bug Submission Guidelines." on the rosegarden web site. @tedfelix ?

     
  • Philip Leishman

    Philip Leishman - 2026-10-17

    There used to be a limit to the matrix editor zooming. This was removed at the beginning of the year.
    See commit [566f98]

     

    Related

    Commit: [566f98]


    Last edit: Ted Felix 2026-10-19
  • Kai Griswold

    Kai Griswold - 2026-10-18
    ❯ fastfetch -l none --pipe true | cat
    tmp@kaispc
    ----------
    OS: Manjaro Linux x86_64
    Host: HP ProBook 430 G8 Notebook PC (SBKPF)
    Kernel: Linux 6.18.49-1-MANJARO
    Uptime: 1 hour, 16 mins
    Packages: 12 (flatpak), 2484 (pacman)[stable], 7 (snap)
    Shell: zsh 5.9.2
    Display (AUOCB8F): 1920x1080 in 13", 60 Hz [Built-in]
    Desktop Environment: KDE Plasma 6.7.4
    Window Manager: KWin (Wayland)
    WM Theme: Breeze
    Theme: Breeze (Dark) [Qt], Breeze-Dark [GTK2], Breeze [GTK3/4]
    Icons: breeze-dark [Qt], breeze-dark [GTK2/3/4]
    Font: Noto Sans (10pt) [Qt], Noto Sans (10pt) [GTK2/3/4]
    Cursor: breeze (24px)
    Terminal: konsole 26.8.0
    Terminal Font: Hack Nerd Font Mono (11pt)
    CPU: 11th Gen Intel(R) Core(TM) i7-1165G7 (8) @ 4.70 GHz
    GPU: Intel Iris Xe Graphics @ 1.30 GHz [Integrated]
    Memory: 7.45 GiB / 15.30 GiB (49%)
    Swap: 36.00 KiB / 512.00 MiB (0%)
    Disk (/): 288.91 GiB / 476.64 GiB (61%) - btrfs
    Local IP (wlp2s0): 192.168.1.76/24
    Battery (Primary): 61% (2 hours, 19 mins remaining) [Discharging]
    Locale: en_US.UTF-8
    ❯ rosegarden --version
    Rosegarden version: 26.06 ("Laura")
    Build key: 888fa4273c
    Built against Qt version: 5.15.19
    ❯ sudo pacman -Qv rosegarden
    Root      : /
    Conf File : /etc/pacman.conf
    DB Path   : /var/lib/pacman/
    Cache Dirs: /var/cache/pacman/pkg/  
    Hook Dirs : /usr/share/libalpm/hooks/  /etc/pacman.d/hooks/  
    Lock File : /var/lib/pacman/db.lck
    Log File  : /var/log/pacman.log
    GPG Dir   : /etc/pacman.d/gnupg/
    Targets   : rosegarden
    rosegarden 26.06-1
    

    Can't build it with DEBUG as far as I know

     
  • Philip Leishman

    Philip Leishman - 2026-10-18

    So the (good/bad) news - I have a Manjaro virtual machine and there I can reproduce the crash !!
    I will look into it further.

     
  • Kai Griswold

    Kai Griswold - 2026-10-19

    Good news. Definitely good news. YAY!!!

     

    Last edit: Kai Griswold 2026-10-19
  • Philip Leishman

    Philip Leishman - 2026-10-19

    Rosegarden crashes in PianoKeyboard.cpp at line 156 - this is a straightforward drawText call in the paintEvent.
    I believe this is some kind of bug/inconsistency in the qt render pipeline. I don't think we can directly fix it in Rosegarden.
    It only happens at extremely high zoom values. As mentioned above the zoom was extended back in January. I went back to the old values and I could not reproduce the crash.
    Also when compiled with qt6 Rosegarden does not crash even at the high zoom values.
    So maybe we should reduce the zoom limits again ?
    For the time being this means just avoiding the very high zoom values in the editor.

     
    • Kai Griswold

      Kai Griswold - 2026-10-20

      I mean this is an insane zoom level, more than anyone would need, I'd say
      maybe 2 128th notes would fit the viewport at that zoom level

      On Mon, Oct 19, 2026, 10:08 Philip Leishman lman@users.sourceforge.net
      wrote:

      Rosegarden crashes in PianoKeyboard.cpp at line 156 - this is a
      straightforward drawText call in the paintEvent.
      I believe this is some kind of bug/inconsistency in the qt render
      pipeline. I don't think we can directly fix it in Rosegarden.
      It only happens at extremely high zoom values. As mentioned above the zoom
      was extended back in January. I went back to the old values and I could not
      reproduce the crash.
      Also when compiled with qt6 Rosegarden does not crash even at the high
      zoom values.
      So maybe we should reduce the zoom limits again ?
      For the time being this means just avoiding the very high zoom values in
      the editor.


      [bugs:#1801] https://sourceforge.net/p/rosegarden/bugs/1801/ Matrix
      Editor: zoom segfaults

      Status: open
      Group: None
      Created: Sat Oct 17, 2026 03:49 AM UTC by Kai Griswold
      Last Updated: Mon Oct 19, 2026 06:00 AM UTC
      Owner: nobody

      render glyph failed err=62 face=0x55ed095a2d80, glyph=38
      zsh: segmentation fault (core dumped) rosegarden

      https://drive.google.com/drive/folders/1kpBHJ5qm1ryybLGunnmTSSCH-XyFEKpk?usp=sharing

      Sent from sourceforge.net because you indicated interest in
      https://sourceforge.net/p/rosegarden/bugs/1801/

      To unsubscribe from further messages, please visit
      https://sourceforge.net/auth/subscriptions/

       

      Related

      Bugs: #1801

  • Ted Felix

    Ted Felix - 2026-10-19

    Do we think anyone actually needs those high zoom levels? If not, maybe just limit them for qt5 and include a comment pointing to this bug report?

     
  • Philip Leishman

    Philip Leishman - 2026-10-21

    "I got the link from Help>Bug Reporting Guidelines in the Rosegarden app"
    Yes the link was wrong in the code.
    See codeberg pull request.

     

Log in to post a comment.