I missed a memo: Did alsa.conf move or did Frescobaldi start looking in the wrong place?

32 views
Skip to first unread message

Kevin Cole

unread,
Apr 30, 2023, 5:00:58 PM4/30/23
to Frescobaldi
TL;RL: I've fixed my problem for the moment, but I'm hoping for a
better understanding / more permanent solution going forward.

MIDI used to work okay, and then today when I tried it no longer did.
Investigating, I found:

$ frescobaldi
ALSA lib conf.c:4555:(snd_config_update_r) Cannot access file
/usr/local/share/alsa/alsa.conf
ALSA lib seq.c:935:(snd_seq_open_noupdate) Unknown SEQ default

But, it worked after I:

$ sudo ln -s /usr/share/alsa /usr/local/share/alsa

I dislike screwing around with /usr files and directories that way,
for fear that something else will trounce them and, despite my
OCD-quality documentation and logging, I'll forget to redo the above.

Any idea what changed when?

I'm on a Pop! OS 22.04 LTS system. I was running Frescobaldi 3.2, but
in the process of investigating the above, I've JUST upgraded to 3.3.
(Version 3.3 failed the same way without the symlink.)

P.S. The manual installation of 3.3 from the git repo failed with:

$ git clone g...@github.com:frescobaldi/frescobaldi.git
$ cd frescobaldi
$ python3 setup.py install --user
...
error: can't copy 'linux/org.frescobaldi.Frescobaldi.desktop':\
doesn't exist or not a regular file

But I was able to fix that with:

$ cp linux/org.frescobaldi.Frescobaldi.desktop.in \
~/.local/share/applications/org.frescobaldi.Frescobaldi.desktop
$ frescobaldi
frescobaldi: command not found
$ cp frescobaldi ~/.local/bin/
$ frescobaldi

It's all working now, but, as I say, I'm hoping for a less "throw crap
at the wall til it works" approach.

Jean Abou Samra

unread,
Apr 30, 2023, 5:07:12 PM4/30/23
to fresc...@googlegroups.com

Le dimanche 30 avril 2023 à 17:00 -0400, Kevin Cole a écrit :

TL;RL: I've fixed my problem for the moment, but I'm hoping for a better understanding / more permanent solution going forward.

MIDI used to work okay, and then today when I tried it no longer did. Investigating, I found:

    $ frescobaldi     ALSA lib conf.c:4555:(snd_config_update_r) Cannot access file /usr/local/share/alsa/alsa.conf     ALSA lib seq.c:935:(snd_seq_open_noupdate) Unknown SEQ default

But, it worked after I:

    $ sudo ln -s /usr/share/alsa /usr/local/share/alsa

I dislike screwing around with /usr files and directories that way, for fear that something else will trounce them and, despite my OCD-quality documentation and logging, I'll forget to redo the above.

Any idea what changed when?

It doesn't sound related to Frescobaldi itself.

Did you try reinstalling the ALSA-related packages? https://askubuntu.com/questions/1298557/broken-alsa-lib-and-missing-alsa-conf

I'm on a Pop! OS 22.04 LTS system. I was running Frescobaldi 3.2, but in the process of investigating the above, I've JUST upgraded to 3.3. (Version 3.3 failed the same way without the symlink.)

P.S. The manual installation of 3.3 from the git repo failed with:

    $ git clone g...@github.com:frescobaldi/frescobaldi.git     $ cd frescobaldi     $ python3 setup.py install --user     ...     error: can't copy 'linux/org.frescobaldi.Frescobaldi.desktop':
       doesn't exist or not a regular file

But I was able to fix that with:

    $ cp linux/org.frescobaldi.Frescobaldi.desktop.in
         ~/.local/share/applications/org.frescobaldi.Frescobaldi.desktop     $ frescobaldi     frescobaldi: command not found     $ cp frescobaldi ~/.local/bin/     $ frescobaldi

It's all working now, but, as I say, I'm hoping for a less "throw crap at the wall til it works" approach.

Hmm, the INSTALL file looks outdated, we need to update it a bit. You need

make -C linux

before the install step.

signature.asc

Kevin Cole

unread,
Apr 30, 2023, 7:10:23 PM4/30/23
to fresc...@googlegroups.com
On Sun, Apr 30, 2023 at 5:07 PM Jean Abou Samra <je...@abou-samra.fr> wrote:

> It doesn't sound related to Frescobaldi itself.
>
> Did you try reinstalling the ALSA-related packages? https://askubuntu.com/questions/1298557/broken-alsa-lib-and-missing-alsa-conf

Yeah, I saw that suggestion and tried it first -- even before cloning
the latest and greatest. No joy there. Since no other application is
complaining and it seemed odd that Frescobaldi would be looking in
/usr/local for something as "universal" as ALSA, I thought it must be
a Frescobaldi thing. But if it's not Frescobaldi, then I'll poke
around elsewhere to see why it used to work and then stopped until I
made the symlink.

> Hmm, the INSTALL file looks outdated, we need to update it a bit. You need
>
> make -C linux
>
> before the install step.

Ah. Much better there. Thanks. I've made a note of it.
Reply all
Reply to author
Forward
0 new messages