gnome 3 interface issues

c3h · 2019-01-18 17:20:07

How to fix problems in the gnome interface? According to the image, the gnome is not recognizing the "icons" of some areas of the system.

https://i.imgur.com/YnTXfri.jpg

https://i.imgur.com/sMI9nLh.jpg

Last edited by 2ManyDogs (2019-01-18 18:43:55)

2ManyDogs · 2019-01-18 18:44:29

Please read the Code of Conduct and post only thumbnails or links to images.

Moving to Newbie Corner.

c3h · 2019-01-18 19:02:30

I'm really sorry, and thanks for asking the question in the right place.

seth · 2019-01-18 21:44:02

That's not an icon, but a unicode glyph - the number in the box is important, but garbled by jpg artifacts :-(
Also: what fonts do you use and what's the output of "fc-match sans"?

c3h · 2019-01-18 22:11:06

hum, I understand, must be why I could not find result in google, I will search as described

installed fonts: ttf-dejavu ttf-bitstream-vera ttf-liberation

result fc-match sans:

Vera.ttf: "Bitstream Vera Sans" "Roman"

seth · 2019-01-18 22:13:12

purge bitstrem vera, deja vu is basically the superset of bitstream.
If you long to keep vera fro some reason, see https://wiki.archlinux.org/index.php/Fo … ault_fonts

c3h · 2019-01-20 23:57:40

Thanks for the tip, I removed the fountain vera.
I managed to solve it but I had to install some source, it follows the eating that I executed:

 pacman -S $(pacman -Ss ttf | grep -v ^” ” | awk ‘{print $1}’) && fc-cache

I do not know if I had a need for so much source rs, but it was what a user indicated to me in another forum, could you tell me if you have limit or remove this font extension that was installed?

loqs · 2019-01-21 00:13:32

pacman -S $(pacman -Ss ttf | grep -v ^” ” | awk ‘{print $1}’) && fc-cache

What do you think this does?

Trilby · 2019-01-21 00:20:31

Holy Horrible Pipelines Batman!

1. I doubt the end result of that pipeline is a good idea - actually I'm quite sure it's not as several of the resulting packages are not even fonts!

2. If that really is what you wanted to do do, though, that'd just be `pacman -S $(pacman -Ssq ttf)`.

3. I'm almost certain what you really wanted to do was just `pacman -S ttf-font`.

c3h · 2019-01-21 00:29:28

loqs wrote:

pacman -S $(pacman -Ss ttf | grep -v ^” ” | awk ‘{print $1}’) && fc-cache

What do you think this does?

I really do not know rs .. the command was kind of confusing for me

Trilby wrote:

Holy Horrible Pipelines Batman!
1. I doubt the end result of that pipeline is a good idea - actually I'm quite sure it's not as several of the resulting packages are not even fonts!
2. If that really is what you wanted to do do, though, that'd just be `pacman -S $(pacman -Ssq ttf)`.
3. I'm almost certain what you really wanted to do was just `pacman -S ttf-font`.

By the way I did something wrong, would I have undo what was accomplished ?

Trilby · 2019-01-21 00:35:55

c3h wrote:

I really do not know rs .. the command was kind of confusing for me

Then why did you run it? Where did you get it?

c3h wrote:

By the way I did something wrong, would I have undo what was accomplished ?

You installed 49 different packages, most of which you probably have no use for. There's no actual harm in that, but it clutters up your system. To undo it, you'd just have to remove all the packages you newly installed.

Never run random commands you don't understand.

Last edited by Trilby (2019-01-21 00:36:31)

loqs · 2019-01-21 00:45:56

On a minor point the command you posted is:

pacman -S $(pacman -Ss ttf | grep -v ^” ” | awk ‘{print $1}’) && fc-cache

The command I think you executed is:

pacman -S $(pacman -Ss ttf | grep -v ^” ” | awk '{print $1}') && fc-cache

Edit:
pacman uses the log file /var/log/pacman.log which will contain a record of the packages you just installed.

Last edited by loqs (2019-01-21 01:07:23)

qinohe · 2019-01-21 01:21:25

@loqs, I need to ask for I don't see it:
What indicates OP used apostrophes instead of right quot. mark?

c3h · 2019-01-21 01:34:44

loqs wrote:

On a minor point the command you posted is:
The command I think you executed is:
pacman -S $(pacman -Ss ttf | grep -v ^” ” | awk '{print $1}') && fc-cache
Edit:
pacman uses the log file /var/log/pacman.log which will contain a record of the packages you just installed.

This, for some reason, my notepad "corrected" the '' by ``

Trilby wrote:

You installed 49 different packages, most of which you probably have no use for. There's no actual harm in that, but it clutters up your system. To undo it, you'd just have to remove all the packages you newly installed.

I removed the installed packages but returned the problem shown in the image https://i.imgur.com/YnTXfri.jpg

Trilby wrote:

3. I'm almost certain what you really wanted to do was just `pacman -S ttf-font`.

I tried the above command but it still continues the problem with the unicode

loqs · 2019-01-21 01:41:13

@c3h see seth's answer in post #6
If you are still confused what fonts do you want to use as defaults?
@qinohe yes

qinohe · 2019-01-21 01:51:40

Hehe thanks for your answer loqs, but that's an impossible answer to my question

c3h · 2019-01-21 02:08:06

loqs wrote:

@c3h see seth's answer in post #6
If you are still confused what fonts do you want to use as defaults?

I'm still not very confident what I should do.

On the sources, it has been installed: ttf-dejavu ttf-bitstream-vera ttf-liberation (although ttf-bitstream-vera I uninstalled as commented above # 7) and I am satisfied with them, but what should I accomplish to run the unicode is that I'm a bit confused even reading the wiki that was indicated in # 6.

loqs · 2019-01-21 02:27:10

@c3h I am sorry I do not understand what "what should I accomplish to run the unicode" means.
@qinohe
The command from post #7

pacman -S $(pacman -Ss ttf | grep -v ^” ” | awk ‘{print $1}’) && fc-cache
grep: ”: No such file or directory
awk: cmd. line:1: ‘{print
awk: cmd. line:1: ^ invalid char '' in expression
error: you cannot perform this operation unless you are root.

The command that works for me

pacman -S $(pacman -Ss ttf | grep -v ^" " | awk '{print $1}') && fc-cache
error: you cannot perform this operation unless you are root.

Two changes from the working command to the command posted double quote to right double quote and single quote to backtick.
Edit:
@c3h if you mean there are some unicode code points you want coverage for other than the original issue then what font to install would depend on personal preference and the code points in question.
Edit2:
I was using the right quote by mistake in my correction in post #12 only changing backtick to a single quote.

Last edited by loqs (2019-01-21 02:35:43)

qinohe · 2019-01-21 03:01:35

Ah, that clears it thanks for the answer @ loqs

Trilby · 2019-01-21 03:17:53

Loqs, I'm pretty sure the OP is saying that installing all 49 of those packages fixed the original issue, but removing them returned to the original issue. They are looking for an appropriate solution - I gather at least one of those 49 packages should be needed, but I know nothing about gnome.

loqs · 2019-01-21 03:42:32

c3h what is the output of `fc-match sans` now?

c3h · 2019-01-22 01:11:20

loqs wrote:

c3h what is the output of `fc-match sans` now?

Vera.ttf: "Bitstream Vera Sans" "Roman"

loqs · 2019-01-22 01:35:51

What is the output of

pacman -Qo /usr/share/fonts

seth · 2019-01-22 08:05:33

In order to say which font resolves the glyph, we'd need to know the unicode point.
Unfortunately the screenshots are small and full of artiacts - the number looks like 23f0, but that's an alarm clock …

c3h · 2019-01-22 10:43:52

seth wrote:

In order to say which font resolves the glyph, we'd need to know the unicode point.
Unfortunately the screenshots are small and full of artiacts - the number looks like 23f0, but that's an alarm clock …

from what I have observed, it is only these two: 23fd, 2b58

Arch Linux

#1 2019-01-18 17:20:07

gnome 3 interface issues

#2 2019-01-18 18:44:29

Re: gnome 3 interface issues

#3 2019-01-18 19:02:30

Re: gnome 3 interface issues

#4 2019-01-18 21:44:02

Re: gnome 3 interface issues

#5 2019-01-18 22:11:06

Re: gnome 3 interface issues

#6 2019-01-18 22:13:12

Re: gnome 3 interface issues

#7 2019-01-20 23:57:40

Re: gnome 3 interface issues

#8 2019-01-21 00:13:32

Re: gnome 3 interface issues

#9 2019-01-21 00:20:31

Re: gnome 3 interface issues

#10 2019-01-21 00:29:28

Re: gnome 3 interface issues

#11 2019-01-21 00:35:55

Re: gnome 3 interface issues

#12 2019-01-21 00:45:56

Re: gnome 3 interface issues

#13 2019-01-21 01:21:25

Re: gnome 3 interface issues

#14 2019-01-21 01:34:44

Re: gnome 3 interface issues

#15 2019-01-21 01:41:13

Re: gnome 3 interface issues

#16 2019-01-21 01:51:40

Re: gnome 3 interface issues

#17 2019-01-21 02:08:06

Re: gnome 3 interface issues

#18 2019-01-21 02:27:10

Re: gnome 3 interface issues

#19 2019-01-21 03:01:35

Re: gnome 3 interface issues

#20 2019-01-21 03:17:53

Re: gnome 3 interface issues

#21 2019-01-21 03:42:32

Re: gnome 3 interface issues

#22 2019-01-22 01:11:20

Re: gnome 3 interface issues

#23 2019-01-22 01:35:51

Re: gnome 3 interface issues

#24 2019-01-22 08:05:33

Re: gnome 3 interface issues

#25 2019-01-22 10:43:52

Re: gnome 3 interface issues

Board footer