Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 2177697 - Privacy policy link doesn't work
Summary: Privacy policy link doesn't work
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-initial-setup
Version: 38
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kalev Lember
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: RejectedBlocker AcceptedFreezeException
Depends On:
Blocks: F38FinalFreezeException
TreeView+ depends on / blocked
 
Reported: 2023-03-13 12:23 UTC by Kamil Páral
Modified: 2023-03-24 16:28 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-03-24 16:28:38 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME gnome-initial-setup issues 181 0 None opened Privacy policy link doesn't work 2023-03-13 12:23:32 UTC

Description Kamil Páral 2023-03-13 12:23:33 UTC
See here:
https://gitlab.gnome.org/GNOME/gnome-initial-setup/-/issues/181

Proposing for a blocker discussion.

Comment 1 Adam Williamson 2023-03-13 16:10:59 UTC
-6 blocker / +5 FE in https://pagure.io/fedora-qa/blocker-review/issue/1089 , marking rejected/accepted.

Comment 2 Adam Williamson 2023-03-24 15:57:30 UTC
mclasen upstream wrote "This should be fixed in gtk 4.10.1", but I just tested with yesterday's F38 nightly which has gtk4-4.10.1-1.fc38.x86_64 , and it still doesn't work. Will report upstream.

Comment 3 Adam Williamson 2023-03-24 16:13:51 UTC
Seems the upstream comment was in error and this should actually be fixed in g-i-s 44.0, which went stable yesterday. Testing again now.

Comment 4 Adam Williamson 2023-03-24 16:28:38 UTC
Confirmed fixed.


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