Bug 2089001 - files from sub packages not found
Summary: files from sub packages not found
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: librecad
Version: epel7
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2022-05-22 11:06 UTC by Armin (LordOfBikes)
Modified: 2022-10-21 22:24 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-10-21 22:24:52 UTC
Type: Bug

Attachments (Terms of Use)

Description Armin (LordOfBikes) 2022-05-22 11:06:41 UTC
Description of problem:
After install/update of librecad package the data from sub packages librecad-fonts, librecad-langs, librecad-parts and librecad-patterns are no longer found by the running application.

Version-Release number of selected component (if applicable):
LibreCAD 2.2.0-rc3

How reproducible:
Run librecad and then:
- go to Application Preferences, the combo boxes for gui and command language are empty
- insert a text entity, the font combo box is empty
- go to the Library tab, there are no libraries

Additional info:
This issue was just reported upstream:

The cause is:
which was reported Jan 1. 2022

The Fedora code base uses 2.2.0-rc3 from Nov 2021.
Issue #1488 was solved on Jan 6. 2022

So a code update should solve this issue.

Final release of 2.2.0 is expected to come in the next couple weeks.
If you won't wait for the final release, I can tag 2.2.0-rc4 now.

Comment 1 todd_lewis 2022-07-04 18:50:55 UTC
Any chance of getting movement on this?

Comment 2 Richard Shaw 2022-09-14 23:42:06 UTC
We're working on updating to 2.2.0 RC4.

Comment 3 Richard Shaw 2022-09-26 11:58:10 UTC
I didn't set the update to close this bug in case it doesn't fix it, but can you try the update in testing and report if it's fixed?


Comment 4 Richard Shaw 2022-10-21 22:24:52 UTC
The update is stable and no response so closing for now. Please reopen if needed.

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