Thunderbird 60 black windows running as user
Hi,
I have been running Mozilla Thunderbird 52.8 as a user with no problems. I am running Slackware64-current and fully up to date. I installed Mozilla Thunderbird 60.0 using the latest slackware package and get black windows with the error message: "[GFX1-]: Failed to lock new back buffer." If I run it as root it works fine and if I run it as a user on another computer, also Slackware64-current, fully up to date, it also works fine. I have tried removing the .thunderbird directory, but no change. Googling for "[GFX1-]: Failed to lock new back buffer." gives little joy. So I think that there is something wrong/different/missing on the first computer. Suggestions on how to find the problem please? |
Quote:
Code:
~/.cache/thunderbird/ |
Quote:
https://www.mail-archive.com/debian-...sg1579071.html https://bugzilla.mozilla.org/show_bu...ult&id=1450169 |
running Thunderbird 60 as user Solved :-)
Thank you for the suggestions :-) :-)
I tried all of the suggestions! but I think it was the mount command which I tried last that did the trick :-) As the user I did: cd ~ rm -fr .cache rm -fr .thunderbird As root I did: chmod o+w /dev/shm chgrp users /dev/shm mount -t tmpfs tmpfs /dev/shm Running thunderbird as a user now works :) Cheers |
Quote:
/me think a better solution is to set /dev/shm for each regular user, as I have here in ~/.profile: Code:
export XDG_CACHE_HOME=/dev/shm/$(whoami) This also provides the advantage that you will never again have to clean ~/.cache, and results in less writes on disk. |
Thunderbird 60 black windows, on systemd
Hi all, I would like to attach additional information in case someone else has the same problem on a systemd-based system, in my case Gentoo. Apologies to the Slack users for hijacking your thread.
I had the same problem (black windows in thunderbird), which comes from thunderbird not being able to create /dev/shm files. However, /dev/shm has already generous permissions: Code:
$ ls -ld /dev/shm/ Classically this limit can be increased through /etc/security/limits.conf, but systemd loads limit settings differently. This was confusing for me because you get different ulimit results in the VTs. Redhat bug #1364332 has information how to set the limits per-user in systemd. I am copying from there: Code:
mkdir /etc/systemd/system/user@1000.service.d Create the file /etc/systemd/system/user@1000.service.d/limit.conf and have it contain Code:
[Service] Code:
systemctl daemon-reload Check that the new limit works: Code:
$ ulimit -n |
All times are GMT -5. The time now is 09:37 AM. |