Bug 1289351
Summary: | ardour4 won't start until passing `--no-hw-optimizations` option | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | fb.bugs.rh |
Component: | ardour4 | Assignee: | Nils Philippsen <nphilipp> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 23 | CC: | fb.bugs.rh, nphilipp |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-03-04 08:49:18 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
fb.bugs.rh
2015-12-07 22:28:48 UTC
Ardour4 starts with `--no-hw-optimizations` option, but abort later just after the first time configuration screens: [TERMINAL] $ ardour4 --no-hw-optimizations --debug all [TERMINAL] WARNING: Your system has a limit for maximum amount of locked memory! This might cause Ardour to run out of memory before your system runs out of memory. You can view the memory limit with 'ulimit -l', and it is normally controlled by /etc/security/limits.conf bind txt domain [gtk2_ardour4] to /usr/share/ardour4/locale Ardour4.4.0 (built using 4.4 and GCC version 5.1.1 20150618 (Red Hat 5.1.1-4)) ardour: [INFO]: Your system is configured to limit Ardour to only 4096 open files ardour: [INFO]: Loading system configuration file /etc/ardour4/system_config No H/W specific optimizations in use Cannot xinstall SIGPIPE error handler ardour: [INFO]: Loading default ui configuration file /etc/ardour4/default_ui_config ardour: [INFO]: Loading color file /etc/ardour4/dark.colors ardour: [INFO]: Loading ui configuration file /etc/ardour4/clearlooks.rc ardour: [INFO]: Loading ui configuration file /etc/ardour4/clearlooks.rc set default folder to /home/user [GUI] 'Welcome to Ardour' screen is displayed nothing to do > clic [Forward] button 'Default folder for new sessions' screen is displayed select a default folder > clic [Forward] button 'Monitoring Choices' screen is displayed leave untouched > clic [Forward] button 'Monitor Section' screen is displayed leave untouched > clic [Forward] button 'Ardour is ready for use' screen is displayed leave untouched > clic [Apply] button [TERMINAL] Found nothing along /home/user/.config/ardour4/templates:/usr/share/ardour4/templates run dialog [GUI] 'Session Setup' window is displayed Session name field filled with 'test' > clic [Open] button 'Audio/MIDI Setup' window is displayed Audio System: ALSA Stopped > clic [Start] button > clic [OK] button [TERMINAL] Scanning folders for bundled LV2s: /usr/lib/ardour4/LV2 Set cursor set to default [GUI] 'Warning' window about limit for maximum amount of locked memory > clic [OK] button Then... nothing more. [TERMINAL] Set cursor set to default Skip explicit buffer seconds, preset in use Skip explicit buffer seconds, preset in use Set buffering params to 262144|131072|10|10 (ardour-4.4.0:1061): Gtk-CRITICAL **: gtk_text_buffer_emit_insert: assertion 'g_utf8_validate (text, len, NULL)' failed Illegal instruction (core dumped) [user@localhost ~]$ watched PID no longer exists - releasing device. ^C [user@localhost ~]$ Then, restarting Ardour4 with `ardour4 --no-hw-optimizations --debug all` just shows: [TERMINAL] WARNING: Your system has a limit for maximum amount of locked memory! This might cause Ardour to run out of memory before your system runs out of memory. You can view the memory limit with 'ulimit -l', and it is normally controlled by /etc/security/limits.conf bind txt domain [gtk2_ardour4] to /usr/share/ardour4/locale Ardour4.4.0 (built using 4.4 and GCC version 5.1.1 20150618 (Red Hat 5.1.1-4)) ardour: [INFO]: Your system is configured to limit Ardour to only 4096 open files ardour: [INFO]: Loading system configuration file /etc/ardour4/system_config Loading user configuration file /home/user/.config/ardour4/config No H/W specific optimizations in use Cannot xinstall SIGPIPE error handler ardour: [INFO]: Loading default ui configuration file /etc/ardour4/default_ui_config ardour: [INFO]: Loading user ui configuration file /home/user/.config/ardour4/ui_config ardour: [INFO]: Loading color file /etc/ardour4/dark.colors ardour: [INFO]: Loading ui configuration file /etc/ardour4/clearlooks.rc ardour: [INFO]: Loading ui configuration file /etc/ardour4/clearlooks.rc Found nothing along /home/user/.config/ardour4/templates:/usr/share/ardour4/templates run dialog [GUI] The 'Session Setup', 'Audio/MIDI Setup' and 'Warning' windows are displayed. Then... nothing more. [TERMINAL] Set cursor set to default Skip explicit buffer seconds, preset in use Skip explicit buffer seconds, preset in use Set buffering params to 262144|131072|10|10 (ardour-4.4.0:3578): Gtk-CRITICAL **: gtk_text_buffer_emit_insert: assertion 'g_utf8_validate (text, len, NULL)' failed Illegal instruction (core dumped) [user@localhost ~]$ watched PID no longer exists - releasing device. ^C [user@localhost ~]$ So, for now, Ardour4 is just unusable on my computer. Hi, I don't have real 32 bit hardware available for testing. Running the program in a 32bit VM worked flawlessly for me, despite a similarly jumbled CPU vendor string. Can you reproduce this error with the current version of ardour4, i.e. 4.7.0? I've just submitted it as a testing update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-eb9c56ff0f If so, can you generate a stack trace? The easiest way would be to install abrt and let it do the work for you, other ways are described here: https://fedoraproject.org/wiki/StackTraces Hi, as Jérôme experiences the same issue and his bug contains stack traces etc., lets continue there. I'll close this bug as a duplicate of his. *** This bug has been marked as a duplicate of bug 1312551 *** |