bitmask-dev issueshttps://0xacab.org/leap/bitmask-dev/-/issues2018-05-31T17:49:48Zhttps://0xacab.org/leap/bitmask-dev/-/issues/9203Buttons in UI produce no action (buster)2018-05-31T17:49:48ZBitmask FailsButtons in UI produce no action (buster)Installed bitmask on Debian buster via .deb per https://bitmask.net/en/install/linux/debs - when starting bitmask UI appears but buttons do nothing apart from "glowing" when clicked (normal UI effect, presumably). -d "debug" option has n...Installed bitmask on Debian buster via .deb per https://bitmask.net/en/install/linux/debs - when starting bitmask UI appears but buttons do nothing apart from "glowing" when clicked (normal UI effect, presumably). -d "debug" option has no apparent effect. Neither -l nor --logfile=~/bitmasklog.txt produces a log file.
I don't know of any other ways to diagnose this failure. Actionable suggestions actively solicited.0.10.3Kali KanekoKali Kanekohttps://0xacab.org/leap/bitmask-dev/-/issues/9165triage problems with gui on buster packages2018-01-25T13:54:07ZKali Kanekotriage problems with gui on buster packageson irc, user guido reports that after an upgrade today the UI ceased working. using buster packages; it might be related with updates to libqt5webkit5.on irc, user guido reports that after an upgrade today the UI ceased working. using buster packages; it might be related with updates to libqt5webkit5.0.10.3Kali KanekoKali Kanekohttps://0xacab.org/leap/bitmask-dev/-/issues/9152port systray icon to OSX2018-01-25T13:37:11ZKali Kanekoport systray icon to OSX0.10.3https://0xacab.org/leap/bitmask-dev/-/issues/9050show details for missing polkit failure2018-01-25T11:21:27ZKali Kanekoshow details for missing polkit failurea common error is that openvpn cannot be launched because there's no polkit agent running. after I merge some fixes, the UI will mark the error state as "failed", but it gives no verbose reason.
this probably will work on the second tim...a common error is that openvpn cannot be launched because there's no polkit agent running. after I merge some fixes, the UI will mark the error state as "failed", but it gives no verbose reason.
this probably will work on the second time (there's a timing issue with our attempt to launch the polkit agent), but I want to make sure that we are displaying **something** useful for the user in the case of unrecoverable errors.
this is the json that the ui will be receiving:
```
{
"result": {
"status": "failed",
"domain": "demo.bitmask.net",
"childrenStatus": {
"firewall": {
"status": "off",
"error": null
},
"vpn": {
"status": "failed",
"error": "No polkit authentication agent available. Please run one."
}
},
"error": "No polkit authentication agent available. Please run one."
},
"error": "No polkit authentication agent available. Please run one."
}
```0.10.3