New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cockpit-[bridge|system] from your repo breaks cockpit-dashboard on Ubuntu 20.04 LTS #10
Comments
I experienced the same problem. Not much of a techie myself, but rerunning the same command I originally used to install cockpit after having installed the plugin seemed to solve the problem. |
Wish I saw this page before I attempted to install this package. If I had a working Cockpit Manager before trying to install this what steps would get be back to a working Cockpit Manager? Right now I lost my Docker plugin, and the Samba plugin just gives me "Samba must be configured to include registry. Add |
Luckily I was able to uninstall cockpit-file-sharing. I tried installing the original cockpit manager and docker plugin but I kept being told that the there was a required package that could not be found. So then I just restored my cockpit, apt and samba directories from this morning's backup. I had to remove the file /etc/apt/sources.list.d/45drives.sources, then reboot. Now I'm back to a working cockpit manager. Next time I'll read the issues to make sure someone hasn't already reported that a new tool will break what was working. |
@pweaver2019 ....I just felt your pain fortunately I took a snapshot, but for a min there I wasn't happy lol. |
Context
I installed cockpit from Ubuntu source and added your repo
to manage my Samba (which works marvellously)
but in your repo you're more than just your add-ons, you also have
cockpit-*
which under Ubuntu focal, at least break few packagesDetail
Possible workaround
1
I was thinking of pinning your repo with a lower priority, but apparently my pinning simply won't want to work, which any will only fix the issue for myself.
2
You come with a solution which could be removing those file from your repo or a better one if you know it.
3
You tell me
The text was updated successfully, but these errors were encountered: