You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be really nice if the documentation could be updated to provide details of the snap package and how to get going with it in addition to the details about the flatpak. This will allow people to choose their favourite mechanism to install from either distro packages, flatpak or snap.
The instructions would need to (for the moment) explain that snapd cannot open the system browser until canonical/snapd#3260 is finished and released. For Ubuntu-derived systems there is an apt/deb package providing the browser-opening functionality for snapd, which must be manually installed with:
sudo apt install snapd-xdg-open
Once that package is installed, or the version of snapd on the system is updated to include the PR (linked earlier), then Corebird will work fine. The browser-launching ability is required for the user to login to Twitter to receive their PIN. To install from the store the user can run either of the following two scenarios:
To run the snap, the user can find the icon in their menu/dash, or they have three commandline options:
snap run corebird
OR
/snap/bin/corebird
OR, the system should place /snap/bin in the path so corebird can be started with a simple
corebird
There is currently only an AMD64 version of the snap available because the openh264 library which is a dependency of gstreamer and thus corebird and Cisco currently do not produce an ARM build. (The library is downloaded upon first-launch to provide the user with a licensed H.264 decoder protecting them from licensing costs because Cisco pay for every installation of their compiled binaries, provided that each end-user downloads them directly from Cisco's site. See http://www.openh264.org/ for details of the library and licensing.)
The text was updated successfully, but these errors were encountered:
I've been using your snap for a couple months, so I'm in favor of seeing this work upstream. Thank you for snapping this up and making it available.
The link to the snap doesn't work for me, though, but this does: https://uappexplorer.com/snap/ubuntu/corebird. I suspect it's because the snap's now available as corebird instead of corebird-diddledan.
I've created and am maintaining a Snap package for Corebird which is available in the Ubuntu Snap Store: https://uappexplorer.com/snap/ubuntu/corebird
It would be really nice if the documentation could be updated to provide details of the snap package and how to get going with it in addition to the details about the flatpak. This will allow people to choose their favourite mechanism to install from either distro packages, flatpak or snap.
The instructions would need to (for the moment) explain that snapd cannot open the system browser until canonical/snapd#3260 is finished and released. For Ubuntu-derived systems there is an apt/deb package providing the browser-opening functionality for snapd, which must be manually installed with:
Once that package is installed, or the version of snapd on the system is updated to include the PR (linked earlier), then Corebird will work fine. The browser-launching ability is required for the user to login to Twitter to receive their PIN. To install from the store the user can run either of the following two scenarios:
OR, without using sudo but requires the user to have an account at https://login.ubuntu.com:
To run the snap, the user can find the icon in their menu/dash, or they have three commandline options:
OR
OR, the system should place /snap/bin in the path so corebird can be started with a simple
There is currently only an AMD64 version of the snap available because the openh264 library which is a dependency of gstreamer and thus corebird and Cisco currently do not produce an ARM build. (The library is downloaded upon first-launch to provide the user with a licensed H.264 decoder protecting them from licensing costs because Cisco pay for every installation of their compiled binaries, provided that each end-user downloads them directly from Cisco's site. See http://www.openh264.org/ for details of the library and licensing.)
The text was updated successfully, but these errors were encountered: