Teams-for-linux: Blank screen on startup, removing ~/.config/teams-for-linux doesn't help

[bremner]

Describe the bug

I hesitate to report a "known issue", but I don't completely understand the mention of "on login".
In case that is different than "on startup", here is my report.

Initially I get just the icon in the status bar, but if I right click that and click run, I get a blank window titled "teams-for-linux".

Installing the snap with "snap install --channel=edge teams-for-linux" seems to work, although I don't know if that is built from the same source.

What's different?
1) I don't make it as far as a login screen
2) Removing ~/.config/teams-for-linux does not change anything.

To Reproduce
Steps to reproduce the behavior:

1. git checkout d7f3647ad30161
2. sudo apt install yarnpkg rpm
3. yarnpkg run dist:linux
4. start teams-for-linux, e.g. with "yarnpkg start"
5. Right click on icon, select "open"
6. see blank screen.

Expected behavior
I expect to see the teams login box

Desktop (please complete the following information):

• OS: Debian testing
• Installation package: source
• Version: d7f3647ad30161

Additional context

yarnpkg is probably called yarn other places

I'm running the tiling window manager i3

[IsmaelMartinez]

Hi @bremner,

If you are running from source, the folder to remove is slightly different and depends on your system.

Its normally called ~/.config/Electron/

[IsmaelMartinez]

also, yeah, it should be the same version. Travis is giving me a headache and snapcraft are ignoring me but edge has now d7f3647

[bremner]

IsmaelMartinez [e-mail] writes:

Hi @bremner,

If you are running from source, the folder to remove is slightly different and depends on your system.

Its normally called ~/.config/Electron/

Thanks for the information. I confirmed that ~/.config/Electron is
created by

% yarnpkg start

Unfortunately removing that directory does not seem to change anything;
the window is still blank.

[IsmaelMartinez]

can you try if the "master" branch works? That is the same one as if you use snap stable branch. Ta

[bremner]

IsmaelMartinez [e-mail] writes:

can you try if the "master" branch works? That is the same one as if you use snap stable branch. Ta

Seems to be exactly the same. Stable snap works, at least as far as
getting to the MS Sign in box, but self-compiled version just gives a
blank window. It seems logical that there is something about my build
environment that is breaking things. In case it's helpful I attach
"yarn.lock", which I guess has all the package versions in it

d

[IsmaelMartinez]

Not that I will recommend it for using always but, have you tried using
sudo? Sorry if you have already tried that. In the mobile...

On Thu, 9 Apr 2020, 18:12 bremner, [e-mail] wrote:

IsmaelMartinez [e-mail] writes:

can you try if the "master" branch works? That is the same one as if you
use snap stable branch. Ta

Seems to be exactly the same. Stable snap works, at least as far as
getting to the MS Sign in box, but self-compiled version just gives a
blank window. It seems logical that there is something about my build
environment that is breaking things. In case it's helpful I attach
"yarn.lock", which I guess has all the package versions in it

d

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/IsmaelMartinez/teams-for-linux/issues/339#issuecomment-611644394,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADJHEG7O33WMJSHJ6WA3DTRLX6ZVANCNFSM4MCWIF6A
.

[bremner]

IsmaelMartinez [e-mail] writes:

Not that I will recommend it for using always but, have you tried using
sudo? Sorry if you have already tried that. In the mobile...

I don't even get a status bar ico or window as root.

        convex# ./teams-for-linux 
        configPath = /root/.config/teams-for-linux
        Failed to get the config file, using default values
        configFile = {}
        processArgs [ '/home/bremner/software/upstream/teams-for-linux/dist/linux-unpacked/teams-for-linux' ]

        (teams-for-linux:2063226): libappindicator-WARNING **: 12:36:17.904: Unable to get the session bus: Unknown or unsupported transport “disabled” for address “disabled:”

        (teams-for-linux:2063226): LIBDBUSMENU-GLIB-WARNING **: 12:36:17.904: Unable to get session bus: Unknown or unsupported transport “disabled” for address “disabled:”
        ^R
        ^Cbefore-quit
        window close
        ^C

[IsmaelMartinez]

Have you tried just using yarn instead of yarnpkg? Not sure if there is a difference on them

[bremner]

IsmaelMartinez [e-mail] writes:

Have you tried just using yarn instead of yarnpkg? Not sure if there is a difference on them

As far as I know, yarnpkg is just the debian name for yarn (to avoid
conflicts). But I tried

    ./node_modules/yarn/bin/yarn start

and it does not seem make a difference

[IsmaelMartinez]

Can you put the yarnpkg version? It's pretty strange but I suspect it might be an older version of yarn. I think it's 1.22
Also, it's strange you have to "run" the app from the taskbar. Normally it just opens.
Also, another option is to try refreshing the window. I believe it's ctrl+r. Try and see how you get on. Ta

[bremner]

IsmaelMartinez [e-mail] writes:

Can you put the yarnpkg version? It's pretty strange but I suspect it might be an older version of yarn.

╭─ convex:~/software/upstream/teams-for-linux
╰─ (git)-[develop]-% yarnpkg --version
1.22.4

╭─ convex:~/software/upstream/teams-for-linux
╰─ (git)-[develop]-% ./node_modules/yarn/bin/yarn --version
1.22.0

I.e. the debian version is actually a bit newer.

BUT, the strangest thing is without knowing what changed, it seems both
running from source, linux/unpacked, aand the debian packages all seem
to work now. This machine is tracking debian testing, so it's possible
something being upgraded fixed things. The good news is that I think you
can close this bug. The bad news is that I don't know how to help
someone else with these symptoms, except maybe checking kernel logs for
something interesting, as the kernel is one of the things that updated
today.

Thanks for the effort you put in on this bug (and for maintaining
teams-for-linux).

d

[IsmaelMartinez]

glad that is fixed, intrigued that we will probably never know what was wrong. Cheers!

[bremner]

The issue is back for me. I have have (old) self-built .deb and app-images for 1.02 that work, and (new) 1.05 and 1.06 that exhibit the blank white screen behaviour. I wanted to try rebuilding v1.0.2 with my current toolchain, but I can't find a tag for it. Looking at the looks it looks like that should be d7f3647ad30, does that sound right?

EDIT: I did the rebuild of 1.0.2 with my current toolchain and it is also broken afaict. So I guess the good news from your point of view is that it seems to be some kind of toolchain issue.

[IsmaelMartinez]

have you tried with the packaged versions that I provide now in here? Added multiple architectures in 1.0.5 when I moved from Travis to github actions
https://github.com/IsmaelMartinez/teams-for-linux/releases/tag/v1.0.5

[bremner]

IsmaelMartinez [e-mail] writes:

have you tried with the packaged versions that I provide now in here?
Added multiple architectures in 1.0.5 when I moved from Travis to
github actions
https://github.com/IsmaelMartinez/teams-for-linux/releases/tag/v1.0.5

Yes, your app image for 1.0.5 also works. Are the build logs available
somewhere? Maybe I'll try to tease out what the difference in the build
environment is.

[IsmaelMartinez]

Added the logs in here:

logs_70.zip

Just using github actions so the configuration is here:
https://github.com/IsmaelMartinez/teams-for-linux/blob/develop/.github/workflows/build.yml

Not sure if I can help any much. That should give you enough to play around. Hope you find your tool-chain shenanigans issue!