Removal of hal breaks amazon's drm for flash video
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
No it's about using common sense and added levels of testing to make sure projects are not just unused, but aren't utilized in ways that are duplicated. However, this is why -current exists, to test things and make sure things work as they should without problems.
Even if a media distributor uses it still in a project, if it's a well circulated project like Adobe Flash, it's technically still being heavily utilized as a dependency.
HAL isn't even duplicated yet by the likes of udev, upower, udisks, etc. which is not only problematic but concerning. Because HAL was deprecated by it's developers, they failed to realize it's subsystems should have been carried over and duplicated by the newer system tools.
This is the problem of removing parts of a system that aren't replaced or haven't be completely phased out. You take something out, and you break it, but have nothing to duplicate it's function, it's broken until the required dependencies can be re-added by some means.
If I understand well, flash does not need HAL but in case of DRM, see T3Slider's post above.
Other than that I can't but agree with you that "this is why -current exists, to test things and make sure things work as they should without problems."
So IMHO the most constructive thing to do at this point of time is test and alert or warn if something in -current does not work as expected, giving as precise information as possible about the pitfalls.
Last edited by Didier Spaier; 07-24-2012 at 02:26 AM.
Reason: Typo corrected: s/taht/that/
I'm not looking to place blame, I just would like to be able to stream the video
Quote:
HAL does not belong in a default Slackware installation any longer and if you do need it for this I think it is better added manually...
This was the type of solution I was hoping for. I'm not against hal being removed. I just haven't had time to test it myself yet, and was wondering if anyone had. There seem to be conflicting "opinions" on the other forums as to whether this is possible.
If I understand well, flash does not need HAL but in case of DRM, see T3Slider's post above.
Other than taht I can't but agree with you that "this is why -current exists, to test things and make sure things work as they should without problems."
So IMHO the most constructive thing to do at this point of time is test and alert or warn if something in -current does not work as expected, giving as precise information as possible about the pitfalls.
So the skinny on flash is here. While removing support for Linux is hardly risky for Adobe (we are little fish in a big pond), removing support for Android and Mobile devices suggests that flash is not long for this world.
As to adding hal on top of the non-hal linux systems, I have seen conflicting reports and have not had the time to experiment on my own.
So I was unable to build the old hal on current, but installing the 13.37 hal package allowed me to view the Amazon DRM content. I have not noticed (yet?) any problems arising from running hal on -current. So it seems this problem is not (for now).
13.37 should have the build script in the /source directory. I had to build it also myself for the Flash media issue also. The Build script Patrick left works, but I do believe HAL has a dependency that needs to be resolved before you build it, but I don't remember what it was off hand.
Yeah it's video4linux. It should be in your kernel-headers unless it was removed.
There are a few patches on the internet you might be able to find that may work with HAL if you build it manually. Google it and see if you have any luck.
Not certain it will work (worked for me but I got tons of warnings), but copy the /sources/l/hal directory and all files to your folder and drop the file above into the /patches directory, and edit hal.Slackbuild to add these lines in the patches section:
Code:
# Patch HAL to use videodev2.h rather than videodev.h which is deprecated
# https://launchpadlibrarian.net/64645948/hal_0.5.14-5ubuntu1.debdiff
zcat $CWD/patches/hal_0.5.14-5ubuntu1.debdiff | patch -p1 --verbose || exit 1
It MAY work, but it might not. No support given on this one so you're on your own here.
Unfortunately that just moved me on to the next build error involving glib. As long as the old hal solves my problem, I don't have any more time at the moment to spend on getting the build to work on 14.0.
Since this is a touch near to my heart (I dunno, I just like my Amazon videos. If I can't use Linux for videos I want legally from a service I pay for, then I'm going to keep Windows around), I was befuddled when 14RC'n' started to give me errors with the streaming video on Amazon. "Adobe Flash Player crashed" was the error, nothing more.
So, I began to suspect hal. Originally, I simply installed the hal-0.5.14 from Slackware64-13.37, and it worked well. So figuring I needed to compile hal for this system, I popped over to my favorite mirror, and downloaded the source files, SlackBuild, patches, etc to build hal. (Note, you want to go to slackware-/slackware64-13.37/source/l/hal and copy the entire directory). As others have mentioned, there are various errors that one runs into.
The video4linux can be resolved by simply making a symlink:
The next thing to overcome are the glib errors. I found this page : https://bugs.freedesktop.org/show_bug.cgi?id=45094#c0 which offers a patch for the issues. I put that file in the appropriate spot in the source and modified the SlackBuild, but to no avail; there were still add-on files referencing glib incorrectly.
So I made a patch myself, merged it with the one mentioned above, edited the SlackBuild and ran it. Success! After installing, a tour of Amazon's instant video confirmed that it was working.
Obviously, this is a messy way to be doing this, and it's probably (surely?) not a 'best practice.' I have no idea if it's secure or not and make no guarantees, but I hope that if you try it, you'll find that it works for you. Also, please go to Amazon and submit feedback! Suggest that they remove the hal requirement because the project is not longer supported, and that they find a different way to stream content. (Also mention that you appreciate their service and that they - somewhat - support Linux!)
Oh! I also thought I should mention that this is all on Slackware64-current using AlienBob's flash package with seamonkey 2.12.
Riri
- Please copy fix_glib-headers.diff.txt to the patches folder in your hal sources. Remove .txt from the end and run gzip fix_glib-headers.diff Something like:
Code:
mv /path/to/fix_glib-headers.diff.txt /path/to/hal/patches/fix_glib-headers.diff
cd /path/to/hal/patches
gzip fix_glib-headers.diff
- Please remove .txt from the end of hal.SlackBuild.txt and replace the hal.SlackBuild in your hal sources with that file. You may need to chmod +x hal.SlackBuild in order to run it. Something like:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.