search

keybase / client

Keybase Go Library, Client, Service, OS X, iOS, Android, Electron
BSD 3-Clause "New" or "Revised" License
8.88k stars 1.23k forks source link

gnome-shell crash on first running keybase Ubuntu 16.04.1 64 bit #4599

Open simon-brooke opened 7 years ago

simon-brooke commented 7 years ago

gnome-shell crash on first running keybase Ubuntu 16.04.1 64 bit

my log id: 5309e21f48aad41d1c97dc1c

What showed up in the Gnome terminal was as follows: Selecting previously unselected package keybase. (Reading database ... 1380575 files and directories currently installed.) Preparing to unpack keybase_amd64.deb ... Unpacking keybase (1.0.17-20161007160040.61672fe) ... Setting up keybase (1.0.17-20161007160040.61672fe) ... Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... Processing triggers for bamfdaemon (0.5.3~bzr0+16.04.20160824-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for desktop-file-utils (0.22-1ubuntu5) ... Processing triggers for gnome-menus (3.13.3-6ubuntu3.1) ... Processing triggers for mime-support (3.59ubuntu1) ... simon@fletcher:~/Downloads$ run_keybase Launching keybase service... Mounting /keybase... Launching Keybase GUI... Success!

I also got a rather nice ASCII-art squirrel, but no GUI launched.

The keybase filesystem is mounted:

simon@fletcher:~/Downloads$ mount | grep keybase
/dev/fuse on /keybase type fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)

There is a 'keybase' entry under 'Internet' in the 'Applications' menu in Gnome (gnome-shell 3.18.5-0ubuntu0.1); selecting it launches the GUI successfully.

So essentially the DEB installer worked but failed to launch the GUI, and, in failing, caused the operating system to believe there had been a crash in gnome-shell.

Note that most Ubuntu users are probably running Unity, not gnome-shell, so this issue (if reproducable) probably doesn't affect many users,

maxtaco commented 7 years ago

Cc: @oconnor663 on the gnome-shell crash

oconnor663 commented 7 years ago

I see an error in your log that looks interesting:

Couldn't touch startup.txt file: { Error: ENOENT: no such file or directory, open '/home/simon/.local/share/keybase/started.txt'

I bet we're causing that by not mkdir'ing ~/.local/share/keybase before we try to touch that file. cc @chrisnojima

However, I don't think that error's supposed to be fatal. @simon-brooke is it possible Keybase is actually running in a way you can't see? What does ps aux | grep /opt/keybase/Keybase show? Gnome Shell hides tray icons in a really hard to find place at the bottom of the screen, but if Keybase is running, our little dog/ferret/raccoon icon should be in that hidden mouse-move-activated tray.

oconnor663 commented 7 years ago

@chrisnojima I'm also seeing Error: Error: No installer path before the other error I mentioned above, so presumably that's not fatal either? But I wanted to make sure you saw it.

simon-brooke commented 7 years ago

I'm sorry, I've shut that machine down, so I'm not able to check processes; but, as stated above, I was subsequently able to start the GUI client from the Gnome3 application menu.

Also, note that I subsequently installed, using the same x64 DEB package, on a MacBook Air running Ubuntu 16.04.1 but with Unity rather than Gnome3 (Jeweller), and this installation completed successfully and launched the GUI client. So I'm guessing that whatever went wrong on Fletcher was specific to Gnome3, which is not the default GUI environment on Ubuntu.

chrisnojima commented 7 years ago

@gabriel thoughts?

gabriel commented 7 years ago

The installer error message in this case is non fatal (it's only logged), since on linux the package manager does installer stuff instead. (We should probably check platform since we only do installer on start on mac.)

The splash (started.txt) is also non-fatal.

Must be something else?