Ubuntu-Mate 17.10 with mate desktop 1.18 broken taskbar indicatior

I'm running Ubuntu-Mate 17.10 with Mate Desktop 1.18. I recently installed PIA 77 and the taskbar indicator was working. I logged out and logged back in, now it's broken. PIA is still working but the indicator just has a placeholder and no menu. How can I fix this?

Comments

  • Killing the entire process tree for the PIA app (look for ruby processes) and launching it again would probably do the trick. Alternatively, rebooting should also take care of that. Sometimes when logging out, a background process of the app remains and a new one can't start until that one is closed.
  • I've tried both and they didn't work.
  • Does anybody have any suggestions? I now have no taskbar icon. When I login and start PIA, all I can do is connect to the last connection I was on before.I have NO CONTROL over anything because I can't access ANY SETTINGS
  • missing package? filesystem permissions at /opt/pia gone wonky?
    with PIA running, your process table should look like ( ps ax | grep pia ):
     2452 tty2     S+     0:00 /bin/sh /opt/pia/ruby/ruby.sh /opt/pia/pia_manager/run.rb --startup
    2459 tty2 Sl+ 0:00 /opt/pia/ruby/64/ruby -I /opt/pia/ruby/64 /opt/pia/pia_manager/run.rb --startup
    2538 tty2 S+ 0:00 /bin/sh /opt/pia/ruby/ruby.sh /opt/pia/pia_manager/run.rb --run
    2542 tty2 Sl+ 13:57 /opt/pia/ruby/64/ruby -I /opt/pia/ruby/64 /opt/pia/pia_manager/run.rb --run
    2717 tty2 S+ 0:00 sh -c "/opt/pia/nwjs/64/pia_nw" "/opt/pia/frontend"
    2720 tty2 SLl+ 37:43 /opt/pia/nwjs/64/pia_nw /opt/pia/frontend
    2823 tty2 S+ 0:00 /opt/pia/nwjs/64/pia_nw --type=zygote --no-sandbox --enable-crash-reporter=, --user-data-dir=/home/ausername/.config/PrivateInternetAccess --nwapp-path=/opt/pia/frontend
    2897 tty2 Sl+ 0:23 /opt/pia/nwjs/64/pia_nw --type=zygote --no-sandbox --enable-crash-reporter=, --user-data-dir=/home/ausername/.config/PrivateInternetAccess --nwapp-path=/opt/pia/frontend


  • Sorry, a work project took me away from things for a while. Here's the output from mine, looks quite different:
    theking  10061  0.0  0.0   4592   864 ?        S    Mar16   0:00 /bin/sh /home/theking/.pia_manager/pia_manager/run.sh --startup
    theking  10079  0.0  0.1  37700  9424 ?        Sl   Mar16   0:00 /home/theking/.pia_manager/pia_manager/64/ruby -I /home/theking/.pia_manager/pia_manager -I /home/theking/.pia_manager/pia_manager/64 /home/theking/.pia_manager/pia_manager/run.rb --startup
    theking  10742  0.0  0.0   4592   856 ?        S    Mar16   0:00 /bin/sh /home/theking/.pia_manager/pia_manager/run.sh --run
    theking  10746  0.0  0.3 2175176 26012 ?       Sl   Mar16   0:56 /home/theking/.pia_manager/pia_manager/64/ruby -I /home/theking/.pia_manager/pia_manager -I /home/theking/.pia_manager/pia_manager/64 /home/theking/.pia_manager/pia_manager/run.rb --run
    theking  10830  0.0  0.0   4592   856 ?        S    Mar16   0:00 sh -c "/home/theking/.pia_manager/pia_tray_bin/nw-linux-64/pia_nw" "/home/theking/.pia_manager/pia_tray_files/" 
    theking  10834  0.0  1.2 913104 102336 ?       Sl   Mar16   0:10 /home/theking/.pia_manager/pia_tray_bin/nw-linux-64/pia_nw /home/theking/.pia_manager/pia_tray_files/
    theking  10911  0.0  0.4 331860 38656 ?        S    Mar16   0:00 /home/theking/.pia_manager/pia_tray_bin/nw-linux-64/pia_nw --type=zygote --no-sandbox --enable-crash-reporter --user-data-dir=/home/theking/.config/Private Internet Access
    theking  10944  0.0  1.2 1046848 101748 ?      Sl   Mar16   0:02 /home/theking/.pia_manager/pia_tray_bin/nw-linux-64/pia_nw --type=zygote --no-sandbox --enable-crash-reporter --user-data-dir=/home/theking/.config/Private Internet Access
    root     23375  0.2  0.0   9968  4316 ?        Ss   09:50   0:00 openvpn --client --persist-key --persist-tun --comp-lzo yes --dev tun --script-security 2 --remote 104.156.228.168 8080 --auth-user-pass /home/theking/.pia_manager/data/user_pass.txt --writepid /home/theking/.pia_manager/log/openvpn.pid --proto udp --nobind --management 127.0.0.1 31749 --log-append /home/theking/.pia_manager/log/openvpn.log --remote-cert-tls server --cipher aes-128-cbc --auth sha1 --ca /home/theking/.pia_manager/data/ca.crt --sndbuf 262144 --rcvbuf 262144 --tls-remote 96b829c90a5f6bf3eeed8c6b9bac7374 --pia-signal-settings --daemon
    theking  23898  0.0  0.0  14352  1084 pts/2    S+   09:52   0:00 grep --color=auto pia 
  • edited March 2018
    mine was with PIA running but no VPN set up. yours should have all the same as mine plus one or two more.
  • O I C ... you didn't take the default install destination. if your home directory is encrypted, you will have various problems (the solution for that situation has been documented in this Discussion Category).
  • I can't not run a vpn connection without killing all the pia processes. I'm using full disk encryption. I don't understand why the install destination would be different. I just followed the download instructions on the site.

    Moved the install to /opt/ but still having the same problem

    I don't know what PIA did but I don't have this issue on a fully encrypted install of Ubuntu-Mate 16.04
  • edited March 2018
    moving a busted/incomplete install won't fix it, of course. i would start over and accept the default destination /opt/pia

    oh, but i see in your other thread you appear to have a functioning install and you just need the environment variable 'fix'
  • @taskz This cannot possibly be a v77 installation. Since v76, PIA installs to /opt/pia. Having it running from your home directory strongly implies that it's still running an old version even if you think you have updated.

    These should remove everything:
    sudo rm -rf /opt/pia /opt/pia_manager ~/.pia_manager
    rm -rf ~/.{config,cache}/Private{InternetAccess," Internet Access"} ~/.local/share/applications/pia_*
  • Everything's in /opt/ now. Thanks for the help :)
Sign In or Register to comment.