Bug 343778 - GTK Font settings not respected
Summary: GTK Font settings not respected
Status: RESOLVED FIXED
Alias: None
Product: QtCurve
Classification: Frameworks and Libraries
Component: gtk2 (other bugs)
Version First Reported In: git
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Yichao Yu
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-04 16:49 UTC by beojan
Modified: 2021-03-09 20:35 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Illustration (925 bytes, image/png)
2015-02-04 16:49 UTC, beojan
Details
Illustration (44.88 KB, image/png)
2015-02-04 16:51 UTC, beojan
Details
gtk-chtheme with 1.8.18-76-ge3e2325 (left) vs. 1.8.18-240-g721fcf3 (right) (77.49 KB, image/png)
2015-05-03 17:26 UTC, RJVB
Details
sylpheed with 1.8.18-76-ge3e2325 (left) vs. 1.8.18-240-g721fcf3 (right) (98.49 KB, image/png)
2015-05-03 17:28 UTC, RJVB
Details

Note You need to log in before you can comment on or make changes to this bug.
Description beojan 2015-02-04 16:49:56 UTC
Created attachment 90912 [details]
Illustration

QtCurve doesn't seem to respect the gtk font settings
Comment 1 beojan 2015-02-04 16:51:33 UTC
Created attachment 90913 [details]
Illustration
Comment 2 RJVB 2015-05-03 17:24:46 UTC
Same here on OS X, and in addition the "no icons in buttons" setting is not honoured (I'll file a separate bug for that).

All was still fine with commit e3e2325e from 20150127 (1.8.18-76-ge3e2325), as can be seen in the screenshots I'll be uploading, where the 1.8.18-76-ge3e2325 version is shown on the left.
Comment 3 RJVB 2015-05-03 17:26:15 UTC
Created attachment 92394 [details]
gtk-chtheme with 1.8.18-76-ge3e2325 (left) vs. 1.8.18-240-g721fcf3 (right)
Comment 4 RJVB 2015-05-03 17:28:33 UTC
Created attachment 92395 [details]
sylpheed with 1.8.18-76-ge3e2325 (left) vs. 1.8.18-240-g721fcf3 (right)
Comment 5 Justin Zobel 2021-03-09 07:30:34 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.