Skip to content
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

snap warning snap "brave" has bad plugs or slots: content (content plug must contain target path) #32506

Closed
knakamura8 opened this issue Aug 24, 2023 · 11 comments · Fixed by brave/brave-browser-snap#29

Comments

@knakamura8
Copy link

knakamura8 commented Aug 24, 2023

Description

snap warning:
snap "brave" has bad plugs or slots: content (content plug must contain target path)

Occurs with v. 1.57.53 rev. 268 latest/stable

DE is KDE Neon

ERROR:object_proxy.cc(590) Failed to call method: org.kde.KLauncher.start_service_by_desktop_name: object_path= /KLauncher: org.freedesktop.DBus.Error.ServiceUnknown: The name org.kde.klauncher was not provided by any .service files

Steps to Reproduce

  1. Update brave to latest/stable

Actual result:

Snap warning, but seems to run fine (non-breaking, non-showstopper). Happened after latest version update.

Expected result:

Not having a snap warning

Reproduces how often:

N/A (package related)

Brave version (brave://version info)

latest/stable 1.56.52 rev. 268

Version/Channel Information:

snap channel latest/stable

  • Can you reproduce this issue with the current release?
    Yes

Miscellaneous Information:

@knakamura8
Copy link
Author

knakamura8 commented Aug 25, 2023

@wknapik Pinging in case you saw this in your testing (noticed some changes recently, so am unsure)

Can't see all these commits but might be related to issues here of which some are patched and some maybe not. Apologies for the ping and my misunderstanding. Thank you and the other devs for all your hard work :) brave/brave-browser-snap#25

@wknapik
Copy link
Contributor

wknapik commented Aug 25, 2023

Hey @knakamura8. Thanks for the report. This is indeed caused by the most recent change. I asked about it in the snapcraft forum (https://forum.snapcraft.io/t/request-for-auto-connections-for-brave/36514). AFAIK this is just a warning and doesn't break anything, but we'll definitely get this sorted out. For now, let's see what the snapcraft folks have to say.

EDIT: Added a separate topic for this warning in the snapcraft forum.

@JaclynPandaGirl
Copy link

If you've ever changed the version from Latest/Stable in the Snapstore app to something like Latest/Beta, but then reverted back to Latest/Stable, the problem will go away if you switch back to a Latest/Beta

@Soft-where-micro
Copy link

I have been getting this error from Snap for a while now and it seems that the only thing broken is the connection to CUPS. Printing from Brave doesn't work - nor does it give any error. It just doesn't print. I can only print to a file and then open the file and send it to my printer.

@vieiraes
Copy link

just for feed... the same error here... I use Ubuntu 20;04 LTS and brave installed by snap ...

@DemonRx
Copy link

DemonRx commented Oct 21, 2023

I just recently did a full clean install of Ubuntu 22.04.3 LTS, and the warning still occurs under this issue.

I then came across this forum: https://forum.snapcraft.io/t/request-for-auto-connections-for-brave/36514/2

which references the line:

https://github.com/brave/brave-browser-snap/blob/af26aca7457648128fc72eb606a4571832e4ab5a/snapcraft.yaml#L61

Need to test. Can someone confirm ?

@DemonRx
Copy link

DemonRx commented Oct 28, 2023

Bump

@bsclifton
Copy link
Member

cc: @wknapik @mihaiplesa

@phuoc
Copy link

phuoc commented Nov 2, 2023

Same warning occurred in Ubuntu 16.04.7 LTS, Brave version 118.1.59.124

@wknapik
Copy link
Contributor

wknapik commented Nov 3, 2023

This should be resolved with the next snap release

@knakamura8
Copy link
Author

Fantastic! Thank you and the rest of the team(s) for your work and for the update!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants