You are not logged in.
Pages: 1
Topic closed
I have so far installed ardour5 from both testing and community, and ardour6-git from AUR. All behave the same on my system: I see some initialization logging in console. That's it. Process doesn't end, resources aren't used excessively, no error log, no GUI. Here is the console output
bind txt domain [gtk2_ardour6] to /usr/share/ardour6/locale
Ardour6.0.pre0.395 (built using 6.0-pre0-395-g7671268bc and GCC version 7.2.0)
ardour: [INFO]: Your system is configured to limit Ardour to only 4096 open files
ardour: [INFO]: Loading system configuration file /etc/ardour6/system_config
ardour: [INFO]: CPU vendor: GenuineIntel
ardour: [INFO]: AVX-capable processor
ardour: [INFO]: CPU brand: Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz
ardour: [INFO]: Using SSE optimized routines
ardour: [INFO]: Loading default ui configuration file /etc/ardour6/default_ui_config
Color shuttle bg not found
ardour: [INFO]: Loading color file /usr/share/ardour6/themes/dark-ardour.colors
I've also tried having JACK running on launch, same behavior. Anyone have ideas on how to diagnose/fix this issue?
Last edited by fiendfan1 (2018-01-08 00:23:13)
Offline
Using wayland or xorg? Have you created any per user configuration or changed anything system wide? Did you try with a new user to rule out stale configuration files?
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
Using wayland or xorg? Have you created any per user configuration or changed anything system wide? Did you try with a new user to rule out stale configuration files?
I am using xorg
I am using a tiling window manager - XMonad
I have not created or edited any files relating to Ardour
I tried with a new user AND new DE/WM (Xfce4), and got a different error message (progress!):
bind txt domain [gtk2_ardour5] to /usr/share/ardour5/locale
Ardour5.12.0 (built using 5.12 and GCC version 7.2.0)
ardour: [INFO]: Your system is configured to limit Ardour to only 4096 open files
ardour: [INFO]: Loading system configuration file /etc/ardour5/system_config
No protocol specified
ardour: [ERROR]: ** ERROR ** VSTFX: Failed opening connection to X
ardour: [ERROR]: could not initialize Ardour.
No protocol specified
(ardour-5.12.0:2504): Gtk-WARNING **: cannot open display: :0
The process now also does exit after displaying this message.
As you may see from the log, $DISPLAY is ":0".
The
No protocol specified
part is interesting...
Last edited by fiendfan1 (2018-01-08 05:25:14)
Offline
(ardour-5.12.0:2504): Gtk-WARNING **: cannot open display: :0
Output of
ps aux | grep Xorg
loginctl session-status | head
Offline
(ardour-5.12.0:2504): Gtk-WARNING **: cannot open display: :0
Output of
ps aux | grep Xorg loginctl session-status | head
[username@arch ~]$ ps aux | grep Xorg
username 693 0.8 0.4 518664 71812 tty1 Sl 15:09 2:59 /usr/lib/xorg-server/Xorg -nolisten tcp :0 vt1 -auth /tmp/serverauth.glOTKd0Osk
username 21694 0.0 0.0 10884 2316 pts/6 S+ 20:48 0:00 grep Xorg
c1 - username (1000)
Since: Mon 2018-01-08 15:08:34 PST; 5h 41min ago
Leader: 412 (login)
Seat: seat0; vc1
TTY: tty1
Service: login; type tty; class user
State: active
Unit: session-c1.scope
├─ 412 login -- username
├─ 536 -bash
That all looks good to me, no?
Offline
The loginctl says you're not in an X11 session (but a console login) so it's pretty pointless. The ps output however suggest that :0 belongs to your user.
Typical causes for the gtk message are
* no X11 server
* sudo (or other xauthority breakage)
* client hardcodes :0 while you're on :1 (gdm issue)
From the ardour logs i'd rather call #3 a step behind #1 - you simply (somehow) introduced an X11 breakage and don't even make it to where ardour "just" doesn't show a GUI.
=> revert that and run
xev -root -event substructure
Before starting ardour. If there's output from xev a window shows up - you just don't see it.
Offline
The loginctl says you're not in an X11 session (but a console login) so it's pretty pointless. The ps output however suggest that :0 belongs to your user.
I'm running terminator if that helps.
Typical causes for the gtk message are
* no X11 server
* sudo (or other xauthority breakage)
* client hardcodes :0 while you're on :1 (gdm issue)From the ardour logs i'd rather call #3 a step behind #1 - you simply (somehow) introduced an X11 breakage and don't even make it to where ardour "just" doesn't show a GUI.
=> revert that and run
revert what?
xev -root -event substructure
Before starting ardour. If there's output from xev a window shows up - you just don't see it.
It would appear a window is opening...
CreateNotify event, serial 18, synthetic NO, window 0x497,
parent 0x497, window 0x3200001, (10,10), width 10, height 10
border_width 0, override NO
How do I find this window / resize / send to correct workspace?
Last edited by fiendfan1 (2018-01-09 23:51:10)
Offline
I'm running terminator if that helps.
When you were running the loginctl command??
revert what?
new user / xfce
xwininfo -id 0x3200001
xprop -id 0x3200001
Obviously update the ID - you can control it with either xdotool or wmctrl, but this looks like a dummy window or maybe a systray icon.
Offline
I'm running terminator if that helps.
When you were running the loginctl command??
Yeah all command output shown here was run through terminator in either XMonad or Xfce4.
revert what?
new user / xfce
xwininfo -id 0x3200001 xprop -id 0x3200001
Obviously update the ID - you can control it with either xdotool or wmctrl, but this looks like a dummy window or maybe a systray icon.
[username@arch ~]$ xwininfo -id 0x1e00001
xwininfo: Window id: 0x1e00001 "ardour-5.12.0"
Absolute upper-left X: 10
Absolute upper-left Y: 10
Relative upper-left X: 10
Relative upper-left Y: 10
Width: 10
Height: 10
Depth: 24
Visual: 0x21
Visual Class: TrueColor
Border width: 0
Class: InputOutput
Colormap: 0x20 (installed)
Bit Gravity State: NorthWestGravity
Window Gravity State: NorthWestGravity
Backing Store State: NotUseful
Save Under State: no
Map State: IsUnMapped
Override Redirect State: no
Corners: +10+10 -1580+10 -1580-880 +10-880
-geometry 10x10+10+10
[fiendfan1@arch ~]$ xprop -id 0x1e00001
WM_CLASS(STRING) = "ardour-5.12.0", "Ardour-5.12.0"
WM_COMMAND(STRING) = { "ardour-5.12.0" }
_NET_WM_USER_TIME_WINDOW(WINDOW): window id # 0x1e00002
WM_CLIENT_LEADER(WINDOW): window id # 0x1e00001
_NET_WM_PID(CARDINAL) = 5273
WM_LOCALE_NAME(STRING) = "en_US.UTF-8"
WM_CLIENT_MACHINE(STRING) = "arch"
WM_NORMAL_HINTS(WM_SIZE_HINTS):
program specified size: 10 by 10
WM_PROTOCOLS(ATOM): protocols WM_DELETE_WINDOW, WM_TAKE_FOCUS, _NET_WM_PING
WM_ICON_NAME(STRING) = "ardour-5.12.0"
_NET_WM_ICON_NAME(UTF8_STRING) = "ardour-5.12.0"
WM_NAME(STRING) = "ardour-5.12.0"
_NET_WM_NAME(UTF8_STRING) = "ardour-5.12.0"
Offline
Looks like a legit window, but it's not mapped and the geometry is weird.
xdotool windowmap 0x1e00001
xdotool windowsize 0x1e00001 640 480
Offline
I solved it by changing my desktop GTK2 theme to Adapta-Nokto:
Xfce Settings > Appearance > Style (works with Adapta, Adwaita, Arc, ...)
It's a known bug: Ardour uses a Gtk2 theme with its own colour definitions that clashes with a current desktop Gtk2 theme ("AD-BlueAgave" in my case) if it has a colour definition file.
Tried-and-failed: Deleting or renaming '/usr/share/ardour6/themes/dark-ardour.colors',
that is Ardour's colour file definitions, results in Ardour displaying in harlequin colours.
Tried-and-failed: Disabling system GTK2 theme by setting the environment variable also didn't produce expected results:
$ GTK2_RC_FILES=/nonexistent ardour6 # Failed
$ env GTK2_RC_FILES=/nonexistent ardour6 # Failed
$ export GTK2_RC_FILES=/nonexistent # Failed
Failed with every path: /nonexistent, /dev/null, /usr/share/themes/<any_theme>/gtk-2.0/gtkrc
More on the topic and proposed solutions that didn't work for me:
>>> https://tracker.ardour.org/view.php?id=5605#c18109
>>> https://discourse.ardour.org/t/getting- … s/100424/3
Hope it helps. This is my first post. \(^o^)/
Stay creative and make music!
Offline
Thanks for the contribution, but please pay attention to the dates on threads. This thread is very old, so I am closing it now.
Offline
Pages: 1
Topic closed