Ticket #350 (reopened defect)

Opened 1 year ago

Last modified 4 months ago

Aeolus segfaults on first run

Reported by: parkland99@hotmail.com Assigned to: free
Priority: normal Milestone: 2.2
Component: packages Version: 2.0
Severity: normal Keywords:
Cc:

Description

AMD64 1.4.2

Reproduceable : Always

Steps to reproduce:

-> Boot system

-> Run Jack

-> Wait for Jack to start

-> open terminal 

tux@64studio:~$ aeolus
JACK tmpdir identified as [/dev/shm]
Enhanced3DNow! detected
SSE2 detected
Connected to JACK with 0 inputs and 2 outputs.
Reading '/usr/share/aeolus/stops/Aeolus/definition'
Reading '/home/tux/.aeolus-presets'
Segmentation fault
tux@64studio:~$

Two overrun notifications are recorded on the JACK panel

All subsequent invokes of Aeolus work perfectly.

Change History

(in reply to: ↑ description ; follow-up: ↓ 2 ) 06/20/07 18:45:19 changed by parkland99@hotmail.com

  • status changed from new to closed.
  • resolution set to worksforme.

Thanks for the Info Quentin,

Good to know it works for you on a Fresh 1.4.0.

I'll try uninstalling and re-installing Aeolus - maybe there is something screwy in my heavily upgraded system! (Plus I had previously built Aeolus from source on this machine)

I'll close this one for the timebeing - looks like a local problem with my config.

(in reply to: ↑ 1 ) 07/14/07 18:06:51 changed by parkland99@hotmail.com

  • priority changed from low to lowest.
  • status changed from closed to reopened.
  • resolution deleted.
  • severity changed from minor to trivial.

Fresh install 2.0pre1 master 13/jul/07

This problem persists in a fresh install -

First run of aeolus generates 2 xruns for jack Second and subsequent run of aeolus works correctly

07/15/07 18:54:12 changed by parkland99@hotmail.com

  • milestone set to 2.0.

07/16/07 22:34:55 changed by free@64studio.com

I can replicate the problem, but have no idea of why it happens. I'll investigate further.

07/27/07 12:08:01 changed by daniel@64studio.com

  • milestone changed from 2.0 to 3.0.

I can reproduce this with a fresh install of 2.0-rc2. We'll have to ask upstream.

08/13/07 14:13:34 changed by daniel@64studio.com

  • priority changed from lowest to normal.
  • version changed from 1.4.0 to 2.0.
  • severity changed from trivial to minor.
  • milestone changed from 3.0 to 2.1.

02/20/08 12:13:19 changed by daniel@64studio.com

  • severity changed from minor to normal.

The segfault is due to the absence of the ~/.aeolus-presets file on the first run.

A simple workaround is to create an empty file manually before the first run:

$ touch .aeolus-presets

Aeolus will complain e.g. 'File '/home/daniel/.aeolus-presets' is not a valid preset file' but it then creates a valid file itself, without the segfault. The better alternative would be to modify Aeolus so that it creates an empty preset file for the user that runs the program.

02/25/08 14:33:33 changed by qharley@wbs.co.za

on a fresh install of 2.1 pre9 I did not get the annoying segfault. Aeolus opened straight away.

Anyone to confirm?

02/28/08 10:39:57 changed by daniel@64studio.com

Quentin - did the fresh install have a blank /home partition, or did you re-use an existing /home partition? If it's the latter, this bug would not be triggered, as it only affects machines where the user preset file does not exist.

03/07/08 14:19:40 changed by daniel@64studio.com

Still present in a fresh install of 2.1-rc1 AMD64 with a blank /home

Can we do a touch ~/.aeolus-presets on new installs, i.e. if the file does not exist? Can we use /etc/skel or similar during the install?

04/09/08 11:46:16 changed by daniel@64studio.com

Fons believes this is fixed in Aeolus 0.8.1 - now available at http://www.kokkinizita.net/linuxaudio/downloads/index.html

04/16/08 15:37:08 changed by daniel@64studio.com

  • milestone changed from 2.1 to 2.2.

New version of Aeolus requires JACK 0.109, which still has some reports of instability.