Description of problem: ardour5 does not start in KDE as it cannot locate the gtk2 theme Version-Release number of selected component (if applicable): 5.12.0 How reproducible: every time you start the application Steps to Reproduce: 1. open application 2. note it doesn't start 3. try in terminal, note it still doesn't start Actual results: Ardour5 does not start Expected results: application starts Additional info: Cannot load ArdourMono TrueType font. bind txt domain [gtk2_ardour5] to /usr/share/ardour5/locale Ardour5.12.0 (built using 5.12 and GCC version 10.0.1 20200126 (Red Hat 10.0.1-0.6)) ardour: [INFO]: Your system is configured to limit Ardour to only 524288 open files ardour: [INFO]: Loading system configuration file /etc/ardour5/system_config ardour: [INFO]: Loading user configuration file /home/stealthcipher/.config/ardour5/config ardour: [INFO]: CPU vendor: GenuineIntel ardour: [INFO]: AVX-capable processor ardour: [INFO]: CPU brand: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz ardour: [INFO]: Using SSE optimized routines ardour: [INFO]: Loading default ui configuration file /etc/ardour5/default_ui_config ardour: [INFO]: Loading user ui configuration file /home/stealthcipher/.config/ardour5/ui_config Color shuttle bg not found ardour: [INFO]: Loading color file /usr/share/ardour5/themes/dark-ardour.colors after configuring the following environment variable, it works: export GTK2_RC_FILES='/usr/share/themes/Adwaita/gtk-2.0/gtkrc'
This is still happening in ardour-6.3.0-1.fc33.x86_64
Same issue. I'm running Plasma 5.22. This is what I get: $ ardour6 Ardour6.9.0 (built using 6.9 and GCC version 11.2.1 20210728 (Red Hat 11.2.1-1)) Ardour: [INFO]: Your system is configured to limit Ardour to 1048576 open files Ardour: [INFO]: Loading system configuration file /etc/ardour6/system_config Ardour: [INFO]: CPU vendor: GenuineIntel Ardour: [INFO]: AVX-capable processor Ardour: [INFO]: AVX with FMA capable processor Ardour: [INFO]: CPU brand: Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz Ardour: [INFO]: Using AVX and FMA optimized routines Ardour: [INFO]: Loading plugin meta data file /usr/share/ardour6/plugin_metadata/plugin_tags Ardour: [INFO]: Loading default ui configuration file /etc/ardour6/default_ui_config Ardour: [INFO]: Loading 452 MIDI patches from /usr/share/ardour6/patchfiles Ardour: [INFO]: Loading colour file /usr/share/ardour6/themes/dark-ardour.colors and stays there. The process keeps spinning at 100% CPU, but the GUI won't open.
Apparently, the file ~/.gtkrc-2.0-kde4 created a strange loop. Removing it solved the issue for me.
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. 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 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
This issue is still present. The workaround above applies, but still, that file is created by KDE and reappears, so I believe that this is a bug in how Ardour parses and/or uses the configuration files.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle. Changing version to 37.
Sorry for not spotting this earlier. Can anybody attach the offending "~/.gtkrc-2.0-kde4" file to this bug please?
Created attachment 1922729 [details] Offending ~/.gtkrc-2.0-kde4 With this file present, ardour doesn't start.
Ugh, dropped it again. I can now reproduce this, but only under KDE Plasma (which will create the file) – even if the file is present, I have no issue starting this in GNOME.
OK, I haven’t made any progress in finding out why this happens. However, in the meantime Ardour version 8 came out which is available as the ardour8 package in Fedora (as well as the intermediate ardour7). Can you please check if you have the same issue with it? Thanks!
Same issue with ardour8 when ~/.gtkrc-2.0-kde4 is present.
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. 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 'version' of '37'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
yes, I can confirm this still happens in Ardour8 on Fedora39
Fedora Linux 37 entered end-of-life (EOL) status on None. Fedora Linux 37 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.
Reopening and assigning it to rawhide and the latest version of ardour.
I think that this issue may be the same one that [this user](https://discourse.ardour.org/t/ardour-7-gui-does-not-show-up-with-kde-plasma-breeze-theme/108025) experienced. It may be possible to fix this by building Ardour such that it ignores system GTK settings, similarly to how the Ardour team builds the official binaries.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 40 development cycle. Changing version to 40.
I think, as a workaround, the start script could unset GTK2_RC_FILES to ensure the “offending” gtk theme isn’t pulled for Ardour. Before I push it as an update, I would like to find out if it makes Ardour start for you. Would you please try this …: GTK2_RC_FILES= ardour8 … and report if it works then? Thanks!
I cannot tell because with the current version I cannot reproduce the issue anymore. So maybe they solved it upstream?
(In reply to Iñaki Ucar from comment #19) > I cannot tell because with the current version I cannot reproduce the issue > anymore. So maybe they solved it upstream? I don’t think so – I can reproduce it in a Rawhide VM with the current version 8.4.0.
FEDORA-2024-c9490c254c (ardour8-8.4.0-3.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-c9490c254c
FEDORA-2024-c9490c254c (ardour8-8.4.0-3.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-da5e06e0f7 (ardour8-8.4.0-3.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-da5e06e0f7
FEDORA-2024-0e0986a72b (ardour8-8.4.0-3.fc38) has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2024-0e0986a72b
FEDORA-2024-da5e06e0f7 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-2024-da5e06e0f7` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-da5e06e0f7 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-2cd08277f3 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-2cd08277f3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-2cd08277f3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-0e0986a72b has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-0e0986a72b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-0e0986a72b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-2cd08277f3 (ardour8-8.4.0-3.fc39) has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-0e0986a72b (ardour8-8.4.0-3.fc38) has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
seems to be working for me, i tested the environment var set to ardour8 and it launched fine, i noted prior to this with the updated version that it was set to /home/<username>/.gtkrc-2.0-kde4 and I was able to launch the application like that as well
FEDORA-2024-da5e06e0f7 (ardour8-8.4.0-3.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.