Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#9834 - Ardour 2.3.1-1 segfaults!

Attached to Project: Arch Linux
Opened by Johannes Wegener (JoyFM) - Thursday, 13 March 2008, 23:09 GMT
Last edited by Tobias Kieslich (tobias) - Wednesday, 26 March 2008, 16:54 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Kieslich (tobias)
Architecture i686
Severity Medium
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
If you try to open a file or create a new one ardour segfaults after klicking "new" or "open".

Additional info:
* package version(s)
2.3.1-1
* config and/or log files etc.

error :
[code]
[johannes@ThinkpadT40Johannes ardour2]$ ardour2
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
Ardour/GTK 2.3
(built using 3029 and GCC version 4.2.3)
Copyright (C) 1999-2007 Paul Davis
Some portions Copyright (C) Steve Harris, Ari Johnson, Brett Viren, Joel Baker

Ardour comes with ABSOLUTELY NO WARRANTY
not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
This is free software, and you are welcome to redistribute it
under certain conditions; see the source for copying conditions.
loading default ui configuration file /etc/ardour2/ardour2_ui_default.conf
loading user ui configuration file /home/johannes/.ardour2/ardour2_ui.conf
Loading ui configuration file /etc/ardour2/ardour2_ui_dark.rc
theme_init() called from internal clearlooks engine
loading system configuration file /etc/ardour2/ardour_system.rc
loading user configuration file /home/johannes/.ardour2/ardour.rc
ardour: [INFO]: No H/W specific optimizations in use
ardour: [INFO]: looking for control protocols in /home/johannes/.ardour2/surfaces/:/usr/lib/ardour2/surfaces/
ardour: [INFO]: Control protocol Tranzport not usable
powermate: Opening of powermate failed - No such file or directory
ardour: [INFO]: Control protocol powermate not usable
ardour: [INFO]: Control surface protocol discovered: "Generic MIDI"
ardour: [INFO]: Control surface protocol discovered: "Mackie"
Segmentation fault
[/code]

Steps to reproduce:
Start ardour
enter a new name
klick "new"
This task depends upon

Closed by  Tobias Kieslich (tobias)
Wednesday, 26 March 2008, 16:54 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Well it is a bug, but upstream with specific surroundings. Nothing I can do a bout
Comment by Tobias Kieslich (tobias) - Saturday, 15 March 2008, 18:33 GMT
works for me, I need more information about your system and possible changes you made to it.
Comment by Johannes Wegener (JoyFM) - Thursday, 20 March 2008, 12:40 GMT
I have two systems with the same problem (desktop and laptop).

I haven't made any changes just updated ardour and it stopped working (version 2.2 worked perfectly)

So I don't know whats wrong. Please tell me which information you need ;)
Comment by Tobias Kieslich (tobias) - Thursday, 20 March 2008, 22:53 GMT
My system is pretty barebone and has no special tweaks, neither do I have fancy hardware. So my /etc/security/limits.conf is untouched. I have am old Soundblaster live Gold. And I always run qjackctl before I start ardour. So I need a little background of what you do with it, your hardware, your workflow. I tried it on both, my laptop and my desktop box and it wroks fine.
Comment by Johannes Wegener (JoyFM) - Friday, 21 March 2008, 13:43 GMT
I found the error...

Ardour (I think this splash screen becouse it is new in the new version) has a problem with tiling layouts in tiling mangers (like Xmonad, awesome or dwm).

So this is a Ardour related bug and i will post it into their forum.
Thank you for your assistance ;)
Comment by Tobias Kieslich (tobias) - Friday, 21 March 2008, 21:05 GMT
Hi, I'm glad you found it because for me it was only one big question mark. I know from many other programs they have problems with certain gtk engines but then I remembered that ardour shipps it's own version of gtkmm with a hardwired build in engine. Anyway, good you found it. maybe there is a way to disable the splahscreen temporarily?

Loading...