Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disappearing Panel Fonts #3442

Closed
mfreeman72 opened this issue Aug 22, 2014 · 110 comments
Closed

Disappearing Panel Fonts #3442

mfreeman72 opened this issue Aug 22, 2014 · 110 comments

Comments

@mfreeman72
Copy link

On a few of my LM systems, I'm seeing a problem with fonts on the Cinnamon panel. On occasion, some of the fonts (but not all) will either disappear (leaving blank space), or turn into solid rectangles/squares. This leaves panel text nearly unreadable in some cases. I've only seen this on systems running the AMD proprietary drivers. It does not happen using the open-source AMD/ATI driver. I had initially thought it was triggered by running WINE, as it appeared most often when running WINE software. However I just saw it happen on a system where WINE isn't installed. So, I'm not sure what triggers it. This is only affecting fonts on the panel. Other fonts on the desktop, windows, etc. are unaffected.

@mfreeman72
Copy link
Author

I've seen this on both Cinnamon 2.0 and 2.2, including 2.2.16.

@anandrkris
Copy link

Could you share some screenshots please?

@mfreeman72
Copy link
Author

Sorry it's taken a while. Here are a couple screenshots. Screenshot1.png shows the problem affecting the mouse-over labels. It also shows a problem with displaying icons (the "show desktop" icon is all white, and the wireless networking applet icon has a white bar across the top), which I had never seen until now. Screenshot2.png shows the problem affecting just the fonts one the panel itself, specifically the clock and the windows list (It should say "Simple Scan", but the S has disappeared, so it says " imple can"). When it happens, it can affect any part of the panel, including the applet pop-up menus. It requires a Cinnamon restart to get rid of, and eventually does come back over time.
screenshot1
screenshot2

@collinss
Copy link
Member

Sounds like a driver issue to me - not a Cinnamon one.

@leigh123linux
Copy link
Contributor

@collinss

I'm not sure it's a driver issue as it's happened to me (using 2.4.x) when using Intel graphics driver.

@leigh123linux
Copy link
Contributor

Here's another report using nvidia hardware also has missing fonts (see screenshots on link) .

linuxmint/cinnamon-desktop#15

@mfreeman72
Copy link
Author

I would agree about it being a driver problem if it were happening
elsewhere. But it's only happening on the Cinnamon panel, and not anywhere
else on the desktop, nor in any other program.
On Nov 12, 2014 2:41 PM, "Stephen Collins" notifications@github.com wrote:

Sounds like a driver issue to me - not a Cinnamon one.


Reply to this email directly or view it on GitHub
#3442 (comment).

@mfreeman72
Copy link
Author

I can confirm this is still present in Cinnamon 2.4.

@celebithil
Copy link

i confirm too ( Cinnamon 2.4.6 )
NVIDIA GeForce 210
xf86-video-nouveau 1.0.11
3.18.4-1-ARCH

@sruggier
Copy link

I just tried Cinnamon 2.2.16-5 in Debian Jessie for the last hour. I can reproduce this problem by activating the scaling effects (in other words, show all windows or show all workspaces). If I don't activate one of those, it doesn't seem to happen. Restarting cinnamon temporarily relieves the symptoms, as it were.

@xhpohanka
Copy link

Hi. I have similar issue using Cinnamon 2.4.7 on Arch Linux on ThinkPad T410 with Intel video card (i915 driver). I still not found a way to perfectly reproduce it, but the text disappears quite offten. There is also no way (known) to recover without restarting the session. It seems to me that it happens more often when I use external monitor. I also was suspicious about applications like Google Chrome or Eclipse, but probably there is no connection

Please check attached images.

cinnamon_missing_texts01
cinnamon_missing_texts02

@xhpohanka
Copy link

Just an update. It seems that in my case (Intel i915 driver) the issue is reproduced always when going from locked screen on external monitor.

@xhpohanka
Copy link

I can also confirm @sruggier observation about scaling effects. It is not in 100% but very often. Also some 3rd party applications help to force issue with font disappearing. Krusader is an example in my case.

BTW: Is there any cinnamon developer who could reproduce this problem? I would like to provide more information but there is nothing uncommon in logs.

@xhpohanka
Copy link

I found another program that seems to help to triggering the issue: Meld.

@Xiol
Copy link

Xiol commented May 14, 2015

This happened to me after pushing PrintScreen whilst inside a Windows VM running on Virtualbox.

All my windows were minimised and I've lost text on the cinnamon menu, clock, taskbar, etc.

@Flyweightt
Copy link

Cinnamon 2.2.16 on Debian amd64 here. selecting the fonts menu via the desktop and then change a random setting and back, brings the fonts back.
This is what i did and the log is here.

file= $home/.xsession-errors

(nm-applet:23425): libnm-glib-CRITICAL **: nm_secret_agent_register: assertion 'priv->registered == FALSE' failed
Window manager warning: Trying to remove non-existent custom keybinding "magnifier-zoom-in".
Window manager warning: Trying to remove non-existent custom keybinding "magnifier-zoom-out".
JS LOG: Cinnamon started at Tue May 19 2015 15:36:18 GMT+0200 (CEST)

(cinnamon:23413): St-CRITICAL **: st_widget_get_theme_node called on the widget [0x7f7ff828b360 StBoxLayout.menu-selected-app-box] which is not in the stage.
JS LOG: network applet: Cannot find connection for active (or connection cannot be read)
JS LOG: network applet: Cannot find connection for active (or connection cannot be read)
Window manager warning: Log level 16: Symbolic icon /usr/share/cinnamon/applets/notifications@cinnamon.org/empty-notif-symbolic.svg is not in an icon theme directory
Window manager warning: Log level 16: Symbolic icon /usr/share/cinnamon/applets/windows-quick-list@cinnamon.org/windows-quick-list-symbolic.svg is not in an icon theme directory
Window manager warning: Log level 16: STACK_OP_ADD: window 0x2400006 already in stack
Window manager warning: Log level 16: STACK_OP_ADD: window 0x2400006 already in stack
JS LOG: Invalid network device type, is 14
JS LOG: network applet: Found connection for active
JS LOG: network applet: Found connection for active
Window manager warning: Log level 16: Symbolic icon /usr/share/cinnamon/applets/windows-quick-list@cinnamon.org/windows-quick-list-symbolic.svg is not in an icon theme directory
Window manager warning: Log level 16: Symbolic icon /usr/share/cinnamon/applets/notifications@cinnamon.org/empty-notif-symbolic.svg is not in an icon theme directory
Window manager warning: Log level 16: Symbolic icon /usr/share/cinnamon/applets/notifications@cinnamon.org/normal-notif-symbolic.svg is not in an icon theme directory
Window manager warning: Log level 16: value "-71.000122" of type 'gfloat' is invalid or out of range for property 'width' of type 'gfloat'
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
Window manager warning: Log level 16: _XEMBED_INFO property has wrong type

Window manager warning: Log level 8: meta_display_register_x_window: assertion 'g_hash_table_lookup (display->window_ids, xwindowp) == NULL' failed
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x32000a8 specified for 0x32000a6 (Initializi).
Window manager warning: Log level 8: meta_display_register_x_window: assertion 'g_hash_table_lookup (display->window_ids, xwindowp) == NULL' failed
Window manager warning: Log level 8: meta_display_register_x_window: assertion 'g_hash_table_lookup (display->window_ids, xwindowp) == NULL' failed
Window manager warning: Log level 8: meta_display_unregister_x_window: assertion 'g_hash_table_lookup (display->window_ids, &xwindow) != NULL' failed
Window manager warning: Log level 8: meta_display_unregister_x_window: assertion 'g_hash_table_lookup (display->window_ids, &xwindow) != NULL' failed
Window manager warning: Log level 16: STACK_OP_RAISE_ABOVE: sibling window 0x32000fc not in stack
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
Window manager warning: Log level 16: Symbolic icon /usr/share/cinnamon/applets/windows-quick-list@cinnamon.org/windows-quick-list-symbolic.svg is not in an icon theme directory
Window manager warning: Log level 16: Symbolic icon /usr/share/cinnamon/applets/notifications@cinnamon.org/normal-notif-symbolic.svg is not in an icon theme directory
Window manager warning: Log level 16: Symbolic icon /usr/share/cinnamon/applets/windows-quick-list@cinnamon.org/windows-quick-list-symbolic.svg is not in an icon theme directory
Window manager warning: Log level 16: Symbolic icon /usr/share/cinnamon/applets/notifications@cinnamon.org/normal-notif-symbolic.svg is not in an icon theme directory
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
Could not find bluetooth module; is the cinnamon-control-center package installed?
Loading Backgrounds module
init took 204.843 ms
Loading Fonts module
Window manager warning: Log level 16: Symbolic icon /usr/share/cinnamon/applets/notifications@cinnamon.org/normal-notif-symbolic.svg is not in an icon theme directory
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added
JS LOG: Removing an access point that was never added

@ManIVIctorious
Copy link

I don't think that there will be any backports to cinnamon 2.2 anymore, it would be far more interesting for the developers to know if this is still an issue with latest cinnamon (2.6 will be released in the next days)

@Flyweightt
Copy link

Good, point, i will upgrade first and see if the bug persists. thanks for the hint

@xhpohanka
Copy link

For Cinnamon 2.4.8 I can confirm that the fonts are brought back by changing Font scaling factor in settings. However I noticed that sometimes not only fonts disappear but also some parts of graphics.

Please check this picture of app finder (alt + f2)
cinnamon_missing_graphics

The same situation is with application switcher window, I just cannot take a screenshot when alt+tab is pressed.

@xhpohanka
Copy link

It seems that the issue is almost gone in 2.6.3. I just noticed that the font on desktop icons sometimes change its color from white to black.

@Neowizard
Copy link

Well, for those that can't upgrade to 2.6.x (read, Debian Jessie users) an odd workaround I found is to set and revert font scaling factor.
For some reason, changing the font scaling factor and reverting that change made the issue go away completely. I can't reproduce it anymore, after being able to consistently reproduce it for months now, regardless of any other attempt.
I just ran:
gsettings set org.cinnamon.desktop.interface text-scaling-factor 1.1
gsettings set org.cinnamon.desktop.interface text-scaling-factor 1
and that was it.
For some reason, after I ran it my background picture reverted to the default Debian Jessie one...no idea why.

Note that prior to Cinnamon 2.2 the commands to change and revert the scaling factor was (note gnome instead of cinnamon):
gsettings set org.gnome.desktop.interface text-scaling-factor 1.1
gsettings set org.gnome.desktop.interface text-scaling-factor 1

@N1kto
Copy link

N1kto commented Dec 4, 2015

Have same issue on cinnamon 2.6.13. Are there any plans to fix it?
fonts-issue-2
fonts-issue

P.S. Thanks @Neowizard for workaround. Created alias in .bashrc to reuse it if the issue happens again.

_UPDATE_: font scale hack helped only once. After a while the issue came back and font scaling doesn't help :)

@Neowizard
Copy link

@N1kto, I noticed that sometimes that workaround doesn't work.
A few other theme-related modifications that help:
Almost always works (but slowest):
gsettings set org.cinnamon.desktop.interface scaling-factor 2
gsettings set org.cinnamon.desktop.interface scaling-factor 1
works part of the time (almost instantly):
gsettings set org.cinnamon.desktop.interface text-scaling-factor 1.1 (can probably be omitted)
gsettings set org.cinnamon.desktop.interface text-scaling-factor 1
gsettings set org.cinnamon.desktop.interface gtk-theme temp
gsettings set org.cinnamon.desktop.interface gtk-theme BlackMATE_mod
gsettings set org.cinnamon.desktop.interface icon-theme temp
gsettings set org.cinnamon.desktop.interface icon-theme Fog

@N1kto
Copy link

N1kto commented Dec 7, 2015

@Neowizard you are right. I tried using MATE with hope this issue doesn't happen there. But after a few times of suspending it appeared there too. So I start to think that maybe it has something to do with video card/driver. I have an integrated Intel graphics: Intel Corporation Broadwell-U Integrated Graphics (rev 09). The other guy claiming this issue on Reddit Mint blog seems to have the same card. What card do you have?
My co-worker running Mint of the same version as I do with Cinnamon as well doesn't have such issue (Nvidia card).

@Neowizard
Copy link

I'm also using Intel integrated, an "Integrated Intel HD graphics in QM57" (identified by lspci as "Corporation Core Processor Integrated Graphics Controller (rev 02)").

Seems like it could be an issue with the Intel drivers or the way Cinnamon interacts with them.

@agilob
Copy link

agilob commented Apr 5, 2016

I was experiencing this bug on laptop with Intel GPU. The fonts were disappearing when starting a Qt5 application with a tray icon. A solution I found is to change font anti-aliasing setting to greyscale, no need to modify shell rc. 3 weeks without the bug.

@dominichayesferen
Copy link

Shall we close this issue once Linux Mint ever gets Kernel 4.8.0? I know that'll be a while, but still...

@chrisonhub
Copy link

Ubuntu 16.04.2 will be released with Kernel 4.8 and that will be the LTS supported kernel. I guess that will mean it will become available to LM sometime soon, maybe when 18.2 comes out.

At least for Ubuntu, you can see their Kernel and LTS plans here:
https://wiki.ubuntu.com/Kernel/RollingLTSEnablementStack

@raph82
Copy link

raph82 commented Jul 14, 2017

I 'm sad to report that I have this issue with a 4.8 kernel :(

From a fresh install of Linux Mint 18.2 Sonya, on a recently acquired Toshiba Satellite A100 laptop (old laptop but new to me, so no older comparison points).

uname -sr
Linux 4.8.0-53-generic

cinnamon --version
Cinnamon 3.4.3

glxinfo | grep -i vendor
server glx vendor string: SGI client glx vendor string: Mesa Project and SGI Vendor: X.Org R300 Project (0x1002) OpenGL vendor string: X.Org R300 Project

lspci | grep VGA
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV515/M54 [Mobility Radeon X1400]

@petermoo
Copy link

I did an upgrade from my working 18.1/4.8 to 18.2 and the problem did not resurface. Have not tried fresh install. Will not try fresh install until this problem fixed.

@leigh123linux
Copy link
Contributor

leigh123linux commented Jul 15, 2017

In nearly three years no one has posted logging or a backtrace for the issue, closing it as 'Insufficient info' is provided!

@DavidNemeskey
Copy link

@leigh123linux I haven't seen any requests here about logging or backtrace, nor instructions how to produce one. People uploaded e.g. screenshots or the relevant part of the output of lshw, so maybe if you had asked for it, people would have provided said info...

@dominichayesferen
Copy link

I guess this is fixed in LM 18.2, as I've never got the bug since 18.1...

@leigh123linux
Copy link
Contributor

@DavidNemeskey

A few sceenshots and some random hardware info is useless when trying to find code issues.
We shouldn't be expected to ask for logs to be provided, could you imagine how long it would take to respond to 30+ reports asking for this basic info?
I used to see this issue occasionally with my T410 using Fedora 21 - 22 , the user logs didn't show anything related to the issue.
I haven't seen the issue on the T410 since updating to newer Fedora which indicates an issue in the Ubuntu graphics stack.
FTR I spent time trying the steps provided to reproduce, none of them produced the issue.

For those on mint 18.2 using newer Intel hardware could try removing the intel legacy driver and switch to modesetting driver instead

sudo apt-get remove xserver-xorg-video-intel

reboot

P.S 18.2 radeon users could also try modesetting driver as well, I have no idea how to switch to it.

https://www.phoronix.com/scan.php?page=news_item&px=Radeon-Modesetting-DDX-Xenial

@DavidNemeskey
Copy link

@leigh123linux You could always provide a link to a page somewhere (e.g. in the central README.md) that describes what information you would like to see for each report. I would gladly provide any info I can, but it's difficult without knowing what you might be needing.

The logs not providing enough data is of course, another matter altogether. It is also a bummer that you could not reproduce it, but before removing the driver, I could, consistently, with logging in and out, so at that point I could have acquired any info. If it turned out to be an Ubuntu bug, we would have been in a better position to file it upstream.

@allenerenee
Copy link

I have this issue frequently running LM Cinnamon 18.0 Sarah - usually once or twice a week, almost always when the computer wakes up after opening the lid. Kernel version 4.4, on a Toshiba Satellite C55-B5355. If someone could point me to the location of the log file I will post, but I haven't got the first clue where to find it.

@raph82
Copy link

raph82 commented Jul 24, 2017

As @allenerenee, I'd gladly provide more useful info.
Until instructed how to do so, I'm using the workaround cited by leigh123linux:

sudo apt-get remove xserver-xorg-video-intel

@Redsandro
Copy link
Contributor

@allenerenee this is fixed in Kernel 4.8 (linux-generic-hwe) and 4.10 (linux-generic-hwe-edge) as first referenced by @mikkorantalainen

sudo apt install linux-image-generic-hwe-16.04

@petermoo
Copy link

@allenerenee, there is syslog in /var/log/syslog. You can open Nemo, the file lister, and browse syslog using the text editor. Find the time where you closed the list and the time when you opened the lid.

To keep the log small, you could close every application, wait a minute, close the list, open, then select syslog. That section of the log will be free from distracting application related messages.

@raph82
Copy link

raph82 commented Jul 27, 2017

@Redsandro this is not fixed in kernel 4.8, see one of my previous comment.

The workaround cited by leigh123linux does not work. I tried it for a few days before commenting back and it was fine. Then I used Wine and I suspect it triggered the bug again. Will try to test and post relevant syslog.

@Redsandro
Copy link
Contributor

@raph82 I hear you. I wonder if there are two or more different causes for the same problem.

For me the problem does very clearly not occur on 4.8 or 4.10. When I switch back to 4.4, the problem is back immediately. "Something" is fixed for my hardware configuration quite observably so.

@raph82
Copy link

raph82 commented Aug 13, 2017

I've upgraded to a 4.10 kernel a few days ago and since I did not see this bug.

@raph82
Copy link

raph82 commented Aug 14, 2017

Funny how it's only after I post "it works again" messages that bugs resurface.
I've seen it yesterday in Nemo and today on the panel, both times after waking up the computer (reopening the lid).
In syslog I found lines about corrupted memory. The time frames seem to match the bug.
I'm attaching screen captures (including one with others, possibly related, bugs) and logs.
Does this report help?

toshiba-syslog-2017-08-13.log.txt
toshiba-syslog-2017-08-14.log.txt
capture du 2017-08-13 11-33-21
capture du 2017-08-14 13-56-42

@mscheper
Copy link

@raph82: I'm having a pretty severe case of this issue right now, but I don't see the words 'memory' or 'corrupt' in /var/log/syslog. Can you tell me the exact messages you're seeing? I'm just curious if your memory issues are related to the problem we're both apparently having.

I just typed grep -i '\(memory\|corrupt\)' /var/log/syslog /var/log/kern.log /var/log/auth.log /var/log/Xorg.*, which should cover all the files in /var/log that were changed today, and it didn't come up with anything interesting. I don't have a Toshiba, though, so there's no 'toshiba-syslog-*' file on my system.

@mscheper
Copy link

In case any expert on how Mint or Cinnamon render fonts is watching this bug but not #3811, I refer them to the comment I just posted there. I found that the issue isn't quite as simple as 'sometimes, the number 2 and letter Q stops rendering for a particular font'; the size, colour and whether the window has focus apparently affects which characters are rendered. This is a pretty debilitating issue on my system, so I'm happy to help try to solve it. (It'd be nice to minimise how often I have to reboot my system, though. ☺)

@allenerenee
Copy link

allenerenee commented Oct 12, 2017 via email

@mscheper
Copy link

Thanks, @allenerenee. I've seen reports that updating to 4.8 doesn't fix the problem, but I'll try 4.10.

@raph82
Copy link

raph82 commented Oct 16, 2017

@mscheper: the (possibly) relevant messages in the previously attached syslogs are:
Corrupted low memory
Memory corruption detected in low memory

IIRC those come from /var/log/syslog; toshiba-syslog* was the filenames I gave the extracts.

By the way I'm using 4.10 since August.

@Heycharger
Copy link

I just signed up to Github to make posts here...
I am having this trouble of text disappearing on the taskbar and menus - specifically when I use Clementine, the music player.

OS:
Linux Mint 18.2 64
Cinnamon 3.4.6
Kernel 4.10.0-38-generic

Hardware
Toshiba Tecra A11-12F
i3 M330 2.13ghz
Graphics - generic driver - (presumably intel graphics)

One fix, as suggested much earlier in this thread, is to do
gsettings set org.cinnamon.desktop.interface text-scaling-factor 1.1
followed by
gsettings set org.cinnamon.desktop.interface text-scaling-factor 1

For some people, it seems that subsequent kernel and other updates solved this, but it's still happening on my system.

@GuppyBubble
Copy link

Greets!
As like Heycharger, I joined to post regarding the same issue. My taskbar and menus do exactly the same (screenshot would be same as 'xhpohanka' posted back on on 13 Apr 2015).

I've done a few time consuming experiments to see where the issue may lie. I'm no tech wizard, although am mildly competent at getting around with the help of Google and various threads, and it seems in my case this issue occurs when I am running any type of audio player. I've tried VLC, Banshee, Clementine and Audacious and ran out of patience.

It's been suggested that this could be a graphics issue. Personally I don't see how this is the root cause as nothing else seems to create the issue. When using VLC to play video files, I've left the application running for a few hours with no change to the taskbar & menus, yet when I play audio (through VLC) the problem arises within 30 minutes of using the application. Again, this issue happens solely with the use of applications when playing audio files (WAV, FLAC & Mp3 specifically).

Not knowing anything about programming or writing scripts/code, I can't suggest a work around. However, may I be so incredibly bold as to suggest that the issue may be a conflict between audio and graphics somewhere (??) This issue never occurred with Ubuntu, only with Mint. Would be nice to get this one solved...

Lenovo ThinkPad-T410
Kernel: 4.10.0-40-generic x86_64 (64 bit gcc: 5.4.0)
Desktop: Cinnamon 3.4.6 (Gtk 3.18.9-1ubuntu3.3) dm: lightdm Distro: Linux Mint 18.2 Sonya
CPU: Dual core Intel Core i5 M 520 (-HT-MCP-) cache: 3072 KB
Graphics: Card: Intel Core Processor Integrated Graphics Controller bus-ID: 00:02.0 chip-ID: 8086:0046
Audio: Card Intel 5 Series/3400 Series High Definition Audio
driver: snd_hda_intel bus-ID: 00:1b.0 chip-ID: 8086:3b56
Sound: Advanced Linux Sound Architecture v: k4.10.0-40-generic

@Shankaraya
Copy link

Shankaraya commented Oct 14, 2018

Clementine produces the scrambled taskbar effect. Years this is bothering me. Different versions of mint and clementine.
Linux mint 17.3 cinnamon 2.8.8, clementine 1.3.1 Thinkpad T410. Intel onboard graphics.
LMDE 3 "Cindy" cinnamon 3.8.9 same bug. Some files in clementine and strawberry mess up my menu and taskbar. For listening music cinnamon is a pain. Restarting cinnamon every theme. I like strawberry (clementine fork) and clementine for their database handling. In VLC does not happen, all ok. I don't like mate or Xcfe. It's probably cinnamon bug.
sudo apt-get remove xserver-xorg-video-intel does not change anything.
log says: Error while parsing CSS Style (Line:1 1, character: 38): Using Pango syntax for the font: style property is deprecated; please use CSS syntax
Error while parsing CSS Style (Line:1 1, character: 26): not a number
Don't know if that's connected.
Where to communicate with cinnamon developers?

@germanfr
Copy link
Contributor

log says: Error while parsing CSS Style (Line:1 1, character: 38): Using Pango syntax for the font: style property is deprecated; please use CSS syntax
Error while parsing CSS Style (Line:1 1, character: 26): not a number

@Shankaraya that looks like a theme parsing error caused by a property like font: bold or something like that. Can you reproduce with the default theme?

@Shankaraya
Copy link

Changed to mate desktop. Even deleted cinnamon.

@PlatinumLucario
Copy link

PlatinumLucario commented Dec 20, 2021

I can confirm that this issue is not just limited to Cinnamon DE, nor is it limited to just Linux Mint. I can confirm that this bug also occurs on GNOME Shell 3.36.9 and on Ubuntu 20.04.

And to make matters worse, when this bug occurs, it also breaks GNOME Settings function too! Which means if you try to open GNOME Settings, the application will immediately crash, every time the Settings app is opened.

OS Information:
Linux Kernel version: 5.4.0-91-generic
Distribution release: Ubuntu 20.04
Distribution version: 20.04.3 LTS

DE Information:
GNOME version: 3
GNOME Shell version: 3.36.9

Display Server Information:
Display Server: X11
Display Server Version: X.Org 1.20.11

Display Manager Information:
Display Manager: gdm3

Processor Information:
Hardware: Intel(R) Core(TM) i3-6100 CPU @3.70GHz
Cores: 2
Threads: 4

Video Card Information:
Hardware: NVIDIA Corporation: GM206 [GeForce GTX 950]
Driver: nvidia-driver-470 (proprietary, tested)

Here's one of the best ways to reproduce this issue:

  1. Open Discord
  2. Enter into any voice channel on Discord and just stay there for a day, it may range from 30 minutes to 24 hours for it to occur.

Expected results:
The text shouldn't vanish from the desktop environment and it shouldn't cause any graphical issues. Instead, if anything stops working, it should reload!

Actual results:
The text vanishes from the desktop environment and/or other graphical errors occur, and the GNOME settings app crashes upon attempting to open.

I'm also going to copy and paste this into Ubuntu's bug reporter too.
Screenshot from 2021-12-20 23-53-28
Screenshot from 2021-12-20 23-56-57
Screenshot from 2021-12-20 23-57-09

@mikkorantalainen
Copy link

Video Card Information: Hardware: NVIDIA Corporation: GM206 [GeForce GTX 950] Driver: nvidia-driver-470 (proprietary, tested)

As this bug is highly probably about GPU driver issue, if you cannot reproduce the problem with intel integrated graphics, your bug is probably some other issue.

Also, any issue with a test case where the steps include "wait for random delay between 30 min and 24 h" will be hard to fix. Do you have any evidence that it will happen for sure in 24 h?

In addition, the last screenshot shows crash with partial stacktrace suggesting that this crash happens within libglib which is not the software running the GPU nor display so it's probably not related to rendering issue. Have you been able to reproduce this issue with another similar computer to make sure the issue is not e.g. RAM corruption because of hardware issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests