Bug 2023415 - HydraPaper version incompatible with Libadwaita version
Summary: HydraPaper version incompatible with Libadwaita version
Alias: None
Product: Fedora
Classification: Fedora
Component: hydrapaper
Version: 35
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Artem
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2021-11-15 16:21 UTC by qoheniac
Modified: 2021-11-16 16:35 UTC (History)
1 user (show)

Fixed In Version: hydrapaper-3.2.0-1.fc35
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-11-15 18:29:24 UTC
Type: Bug

Attachments (Terms of Use)

Description qoheniac 2021-11-15 16:21:39 UTC
Description of problem:

Version-Release number of selected component (if applicable): 3.1.0

How reproducible:

Steps to Reproduce:
1. Open Terminal
2. Run hydrapaper

Actual results:
(org.gabmus.hydrapaper:29282): Adwaita-WARNING **: 23:38:38.501: Using GtkSettings:gtk-application-prefer-dark-theme with libadwaita is unsupported. Please use AdwStyleManager:color-scheme instead.

(org.gabmus.hydrapaper:29282): Adwaita-ERROR **: 23:38:38.514: gtk_window_set_child() is not supported for AdwWindow
Trace/breakpoint trap (core dumped)

Expected results:
HydraPaper opens without error

Additional info:
Bug is fixed upstream, see: https://gitlab.gnome.org/GabMus/HydraPaper/-/issues/36

Comment 1 Fedora Update System 2021-11-15 17:44:33 UTC
FEDORA-2021-3bd60a26b1 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-3bd60a26b1

Comment 2 Artem 2021-11-15 17:44:55 UTC
Thanks for reporting! I've already reported this upstream long time ago [1]. Please test new version.

[1]: https://bodhi.fedoraproject.org/updates/FEDORA-2021-b95481ed41#comment-2231663

Comment 3 qoheniac 2021-11-15 18:29:24 UTC
Thank you for your quick reply. That build solves the issue.

Comment 4 Fedora Update System 2021-11-16 16:35:30 UTC
FEDORA-2021-3bd60a26b1 has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.

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