LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Thunderbird 60 black windows running as user (https://www.linuxquestions.org/questions/slackware-14/thunderbird-60-black-windows-running-as-user-4175637823/)

myoung 09-05-2018 07:34 AM

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?

Gordie 09-05-2018 11:37 AM

Quote:

Originally Posted by myoung (Post 5900102)
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?

Maybe try removing
Code:

~/.cache/thunderbird/
EDIT - You didn't make a full install?

abga 09-05-2018 12:16 PM

Quote:

Originally Posted by myoung (Post 5900102)
Hi,
Googling for "[GFX1-]: Failed to lock new back buffer." gives little joy.

The first 2-3 results point to issues (both Thunderbird & Firefox 60) related to /dev/shm/, have you read those/tried the fix?
https://www.mail-archive.com/debian-...sg1579071.html
https://bugzilla.mozilla.org/show_bu...ult&id=1450169

myoung 09-05-2018 09:51 PM

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

Didier Spaier 09-06-2018 04:22 AM

Quote:

Originally Posted by myoung (Post 5900351)
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


/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)
mkdir -p /dev/shm/$(whoami)
chmod 700 /dev/shm/$(whoami)
export XDG_RUNTIME_DIR=$XDG_CACHE_HOME

This setting is fully compliant with the XDG Base Directory Specification. The last line is optional, but can help two apps communicate together, as some software rely on XDG_RUNTIME_DIR and others on XDG_CACHE_HOME for the same purpose.

This also provides the advantage that you will never again have to clean ~/.cache, and results in less writes on disk.

buchner.johannes 11-28-2018 11:56 AM

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/
drwxrwxrwt 2 root root 40 Nov 28 14:41 /dev/shm/

The problem was the number of allowed open files (ulimit -n was giving 1024).
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
(If your user uid is something other than 1000 change to that )

Create the file /etc/systemd/system/user@1000.service.d/limit.conf and have it contain

Code:

[Service]
LimitNOFILE=10240

Reload the systemd daemon to pick up the changes
Code:

systemctl daemon-reload
Logout or reboot.

Check that the new limit works:
Code:

$ ulimit -n
10240

I hope this saves someone a few hours of debugging when only having "[GFX1-]: Failed to lock new back buffer." to work with.


All times are GMT -5. The time now is 09:37 AM.