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

[BUG] guide isn't working for drm enabling #174

Closed
Andre96ggitalia opened this issue Sep 11, 2023 · 4 comments
Closed

[BUG] guide isn't working for drm enabling #174

Andre96ggitalia opened this issue Sep 11, 2023 · 4 comments
Labels
bug Something isn't working

Comments

@Andre96ggitalia
Copy link

Hello, today i wanted to enable drm for spotify player. I used this guide: https://github.com/blueboxd/chromium-legacy/wiki/DRM

On the installing support libraries process i found that the folder libraries isn't there, i have only a Libraries file that finder says its a unix executable document.
/Applications/Chromium.app/Contents/Frameworks/Chromium\ Framework.framework/Libraries/

OS: Mac OS X 10.7.5 Macbook4,1 early 2008
Build: #1610 Stable

@Andre96ggitalia Andre96ggitalia added the bug Something isn't working label Sep 11, 2023
@Wowfunhappy
Copy link

Wowfunhappy commented Sep 12, 2023

Duplicate of #149. Spotify is doing some sort of extra DRM check.

Unfortunately, I wouldn't expect this to be fixed. Other music streaming services such as Apple Music work fine in Chromium Legacy if you would consider switching.

@Andre96ggitalia
Copy link
Author

Yeah, cause when i start a song it plays for about 1-2 seconds and then skips to other songs and does the same thing

@Andre96ggitalia
Copy link
Author

@Wowfunhappy
Copy link

Did you re-open this by accident? As I said, it's a duplicate, so it should be closed.

blueboxd pushed a commit that referenced this issue Nov 6, 2023
Automatic update for 2023-10-08 UTC

Change-Id: I0b831a9290d5b53607b29693fad5b6784e323cc8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4915783
Commit-Queue: PKI Metadata Updates Bot <mdb.chrome-pki-metadata-release-jobs@google.com>
Bot-Commit: PKI Metadata Updates Bot <mdb.chrome-pki-metadata-release-jobs@google.com>
Cr-Commit-Position: refs/branch-heads/6045@{#174}
Cr-Branched-From: 905e8bd-refs/heads/main@{#1204232}
blueboxd pushed a commit that referenced this issue May 16, 2024
Roll Chrome Win32 PGO profile from chrome-win32-6367-1711250628-5ff044cd2aec2e4b9444087bcfc9bed26ff00939-1a14b7ce485b2803db7225fc525f89e90de9c261.profdata to chrome-win32-6367-1711274584-dc24fda366bac9b86baca567ad934d83eb6a5793-ff5e8991c67c9e18ee112963d786c2c0c4525fba.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-win32-chromium-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Cq-Include-Trybots: luci.chrome-m124.try:win-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I36ace7bf273c0ad9ab58e4e324f5e88c029382fb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5390478
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6367@{#174}
Cr-Branched-From: d158c6d-refs/heads/main@{#1274542}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants