Description of problem: When displaycal selects pyglet for sound (instead of sdl2 when sdl2_mixer is not installed), the application stays in starting state. the error is like here: https://github.com/eoyilmaz/displaycal-py3/issues/225#issuecomment-1412783760 As workaround, we can install lib64sdl2_mixer2.0_0, to use SDL instead of pyglet.
Summary : A graphical user interface for the Argyll CMS display calibration Yves, please say exactly what version you are using. If Cauldron, it should be version: 3.9.11. Are you able to say whether this problem existed with earlier versions? The link above relates to 'displaycal-py3', which I cannot find...
Source RPM: (none) => displaycal-3.9.10-1.mga9.src.rpmCC: (none) => lewyssmith
I don't know with previous versions. I remember to to have launched it during Mageia 9 development without problem, but I can't say if SDL was installed or not. The error occurs in both 9 and cauldron.
Confirming what you say about Pyglet, from the Manjaro bug you referenced: "mizzack commented on Feb 3, 2023 I have another PC running the same versions of Python, Manjaro, and DisplayCAL and it works there. Comparing the startup logs, the only difference I could see is that the working instance shows Audio module: wx 4.2.0 and the non-working instance shows Audio module: pyglet 2.0.2." The suspicion there was about inconsistent Python bits from different sources, which should not be our case. It looks to have been closed prematurely: "Yes, please use a virtual environment to install DisplayCAL and not make your system python dirty... closing this issue then." The mystery remains about that bug being titled 'displaycal-py3' which I cannot see anywhere chez-nous. I wonder whether this turns on pkg 'python3-pyglet' (SRPM python-pyglet) which has been updated since M9 from 1.5.16-3 to 1.5.27-1, which accords with Yves' assertion that it used to work: python-pyglet-1.5.16-3.mga9.src.rpm python-pyglet-1.5.27-1.mga9.src.rpm However, 1.5.16 dated from May 1 2021, so how did it get into Mageia 9? Because there was a later intermediate version 1.5.23 Sep 7 2022. And 1.5.27 is from Dec 21 2023 in Cauldron, so how did it get into Mageia 9? Résumé of its history: version: 1.5.16, May 1 2021 Mageia 9 Mass Rebuild, Mar 23 2022 version 1.5.23, Sep 7 2022 Rebuild for python 3.12, Dec 21 2023 Actually add 1.5.23 sources, Dec 21 09:55:11 2023 v1.5.27, Dec 21 2023 CC'ing tv & neoclust who did these things
CC: (none) => mageia, thierry.vignaudSource RPM: displaycal-3.9.10-1.mga9.src.rpm => displaycal-3.9.10-1.mga9.src.rpm, python-pyglet-1.5.27-1.mga9.src.rpm
@Lewis displaycal-py3 is a fork of the original application which was only in Python 2, to port it in Python 3 that we use now exclusively. I don't think this bug is in Pyglet, but in displaycal. It includes means for selecting sound libraries. The installation through pip pulls always, I presume, SDL_mixer, thus the run never falls to use of pyglet. Except on distro installations. I will workaround this by adding the requires.
Update pushed in cauldron
Version: Cauldron => 9
Source: displaycal-3.9.10-1.1.mga9 RPM: displaycal-3.9.10-1.1.mga9 Advisory ========================== When sdk2_mixer was not installed, displaycal selected another sound backend. When pyglet is selected, the start is waiting forever. The update adds the sdk2_mixer dependence such that the start is fine in any case. ==========================
Source RPM: displaycal-3.9.10-1.mga9.src.rpm, python-pyglet-1.5.27-1.mga9.src.rpm => displaycal-3.9.10-1.mga9.src.rpmAssignee: bugsquad => qa-bugs
advisory added to SVN
Keywords: (none) => advisoryCC: (none) => marja11
MGA-64 Plasma Wayland on HP Pavillion No installation issues. displaycal starts OK at CLI: $ displaycal XDG: [Errno 2] No translation file found for domain: 'xdg-user-dirs' Acquired lock file: <DisplayCAL.main.AppLock object at 0x7f8942ec3b20> displaycal 3.9.10 2022-11-21T22:56:25Z mageia 9 mga9 x86_64 Python 3.10.11 (main, Apr 16 2023, 03:21:15) [GCC 12.2.1 20230415] Faulthandler wxPython 4.2.0 gtk3 (phoenix) wxWidgets 3.2.1 Encoding: utf-8 File system encoding: utf-8 listening writing to lock file: port: 15411 Starting up... SDL2: libSDL2-2.0.so.0 SDL2_mixer: libSDL2_mixer-2.0.so.0 Audio module: SDL 2.0 Enumerating display devices and communication ports... /usr/bin ArgyllCMS 2.3.1 Argyll has virtual display support ...ok. Checking video card gamma table access for display 1... ...ok. Initializing GUI... instrument_name: display_name : Monitor 1, Output XWAYLAND0 Discarding entries to work around wxGTK Wayland dropdown popup menu bug: /usr/share/DisplayCAL/ref/verify_xl.ti1, /usr/share/DisplayCAL/ref/verify_xxl.ti1, /usr/share/DisplayCAL/ref/verify_xxxl.ti1 ...ok. Ready. Setting up scripting host at 127.0.0.1:15411 (displaycal:26622): Gtk-CRITICAL **: 16:06:50.722: gtk_widget_set_allocation: assertion '_gtk_widget_get_visible (widget) || _gtk_widget_is_toplevel (widget)' failed That last message is repeated a lot I can navigate the tabs and displayed info seems sensible. As the original problem is a busted start, and this starts OK, good enough for me.
Whiteboard: (none) => MGA9-64-OKCC: (none) => herman.viaene
Validating.
Keywords: (none) => validated_updateCC: (none) => andrewsfarm, sysadmin-bugs
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2024-0011.html
Resolution: (none) => FIXEDStatus: NEW => RESOLVED