After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 770177 - Rows texts do not respect the “Big Text” accessibility feature
Rows texts do not respect the “Big Text” accessibility feature
Status: RESOLVED FIXED
Product: gnome-logs
Classification: Other
Component: general
3.21.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-logs maintainer(s)
gnome-logs maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2016-08-20 19:32 UTC by Arnaud B.
Modified: 2016-10-20 09:53 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Screenshot. (70.27 KB, image/png)
2016-08-20 19:32 UTC, Arnaud B.
Details

Description Arnaud B. 2016-08-20 19:32:57 UTC
Created attachment 333769 [details]
Screenshot.

When using the “Big Text” accessibility feature, the text of the logs rows, already smaller than usual, are not changing size, being quite unreadable for people that need this tool.
Comment 1 Jonathan Kang 2016-09-19 09:33:12 UTC
(In reply to Arnaud B. from comment #0)
> Created attachment 333769 [details]
> Screenshot.
> 
> When using the “Big Text” accessibility feature, the text of the logs rows,
> already smaller than usual, are not changing size, being quite unreadable
> for people that need this tool.

Are you running the Logs in jhbuild environment? In that way, the texts of log entry row won't change the size according to the font size. I think that's due to jhbuild environment. I installed 3.21.90 in my system(under /usr), and it worked well.

You can try "jhbuild run ./configure && make && sudo make install" in gnome-logs directory in jhbuild environment.
Comment 2 Jonathan Kang 2016-09-21 12:24:45 UTC
Closing this bug as RESOLVED INVALID, since it's only reproducable while using jhbuild.

Feel free to reopen it if you can reproduce this after installing Logs to /usr.
Comment 3 Arnaud B. 2016-09-21 13:24:18 UTC
I find a little harsh to let me only two days for replying for a “need info”, notably during release times, as I usually try to make more tests when a difference of behaviour is spotted.

Anyway, I REOPENED, since it’s present on 3.21.92 (the more recent version available on my distribution), not using Jhbuild. The usual thing causing differences between computers is that I’m running Wayland (I have no way to test on Xorg).
Comment 4 Jonathan Kang 2016-09-22 02:07:14 UTC
(In reply to Arnaud B. from comment #3)
> I find a little harsh to let me only two days for replying for a “need
> info”, notably during release times, as I usually try to make more tests
> when a difference of behaviour is spotted.

Sorry for that.
> 
> Anyway, I REOPENED, since it’s present on 3.21.92 (the more recent version
> available on my distribution), not using Jhbuild. The usual thing causing
> differences between computers is that I’m running Wayland (I have no way to
> test on Xorg).

I just test 3.21.90 and 3.22.0 on wayland(Fedora 24), and it works well for me. The way I trigger "Large Text" is change "Scaling Factor" in gnome-tweak-tool to a value bigger than 1. I also tried the "Large Text" switch button in Universal Access panel of gnome-control-center. Both works well here.
Comment 5 Jonathan Kang 2016-09-26 02:20:29 UTC
I tested Logs 3.22 in openSUSE Tumbleweed which ships GNOME 3.22 right now. This issue does exist there.

I guess this is related with the issue described in bug#768985. When I get the error about parsing CSS, this issue will happen. There might be something in GTK changed, which caused this problem. I'll check.
Comment 6 Jonathan Kang 2016-09-27 07:49:20 UTC
It might be a bug of gtksourceview, see bug#771898.
Comment 7 Jonathan Kang 2016-10-11 08:38:30 UTC
During fix bug#768985, I found the patch generated for that bug can fix this one, too.
Comment 8 Jonathan Kang 2016-10-20 09:53:05 UTC
After fixing bug#768985, this bug should be fixed, too. So close this bug as RESOLVED FIXED.

The fix is commit bcf4307e2e22328c7f9d87df653a78c06f7f6a5a.