Bug 2171157 - lmms segmentation fault at start
Summary: lmms segmentation fault at start
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: lmms
Version: 36
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Thomas Moschny
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-18 12:32 UTC by Adam Pribyl
Modified: 2023-05-25 19:05 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-25 19:05:28 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Adam Pribyl 2023-02-18 12:32:43 UTC
Description of problem:
lmms won't start on f36:

$ lmms
Notice: could not set realtime priority.
VST sync support disabled in your configuration
Cannot load library /usr/lib64/lmms/libcarlarack.so: (libcarlabase.so: cannot open shared object file: No such file or directory)
Cannot load library /usr/lib64/lmms/libcarlapatchbay.so: (libcarlabase.so: cannot open shared object file: No such file or directory)
Cannot load library /usr/lib64/lmms/libcarlabase.so: (libcarla_native-plugin.so: cannot open shared object file: No such file or directory)
Segmentation fault (core dumped)


Name         : lmms
Version      : 1.2.2
Release      : 12.fc36
Architecture : x86_64
Size         : 26 M
Source       : lmms-1.2.2-12.fc36.src.rpm
Repository   : @System
From repo    : updates

the libraries it complains can not be found are in place.. at least the files.

Comment 1 Andrew Price 2023-02-26 22:57:06 UTC
I think it might be https://github.com/LMMS/lmms/issues/6587 - I've just encountered the same bug.

If possible can you uninstall kf5-kwidgetsaddons and try lmms again to confirm (and as a potential workaround)?

Comment 2 Adam Pribyl 2023-02-27 08:40:55 UTC
Yes,

dnf downgrade kf5-kwidgetsaddons

workarounds the problem, thanks.

Comment 3 Ben Cotton 2023-04-25 18:19:35 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 4 Ludek Smid 2023-05-25 19:05:28 UTC
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.