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.
I'm running 23.0.1271.97 here with no problems at all. I'm scratching my head on this one. Have you installed the google related package that is on extra? It contains a necessary library (PAM related). As for the errors, I get the same thing, so it should be fine.
I went back to /extra and reinstalled the pam package and used the /extra chrome slackbuild with a fresh a chrome 64-bit .deb file.
Nothing. Same result -- it makes absolutely no sense. It's so weird that I have the same setup (it sounds like) but am getting a different result than you stormtracknole. Are you on 64-bit? I'm not using any 32-bit compatibility either.
Last edited by smoooth103; 12-20-2012 at 04:19 AM.
I went back to /extra and reinstalled the pam package and used the /extra chrome slackbuild with a fresh a chrome 64-bit .deb file.
Nothing. Same result -- it makes absolutely no sense. It's so weird that I have the same setup (it sounds like) but am getting a different result than you stormtracknole. Are you on 64-bit? I'm not using any 32-bit compatibility either.
Got slackbuild and pam .txz from slackware.com /extra. Downloaded 64 bit .deb file from chrome website. Installpkg pam-library. Ran slackbuild. Installpkg google-chrome. Click on chromeicon in kde.
Last edited by smoooth103; 12-20-2012 at 08:49 PM.
Got slackbuild and pam .txz from slackware.com /extra. Downloaded 64 bit .deb file from chrome website. Installpkg pam-library. Ran slackbuild. Installpkg google-chrome. Click on chromeicon in kde.
Do you mind posting the SlackBuild file here? Also, have you tried using a different desktop environment, like XFCE? Just for the heck of it.
Ah, I have never used the SlackBuild before. I honestly didn't know there was one on the official Slackware mirror. Let me give you the SlackBuilds that I use. I don't take credit for them as I believe someone posted these right here on LQ. What I did do was for the script to build from the rpm instead of the deb package. I was getting poor flash performance with the deb package, but by using the rpm, those problems were fixed.
Major credit goes to someone here in LQ for creating that script. After a lot of tinkering around, I left the script mostly untouched. What I added was at the very bottom which in addition to download the dep package, it will download the rpm. As you can see, this is for a 64-bit box. Feel free to look around and adjust anything as you see fit. The script NEEDS the deb package in order to work correctly. Once you have installed the tgz package, you can keep running this script to check for new Chrome updates. Very handy!
Again, I don't take credit for this script. I basically modified to use the rpm instead of the deb. I'm sure it wasn't the cleanest way to do it, but it works.
Try that and see if it now works. It should since I have been using that script to build Chrome for quite a while now and I have never had a problem.
Thanks. I will check out your build scripts but honestly I really feel I shouldn't need to have to use specialized scripts to make a common program work. I guess I take some responsibility for living on the edge and using -current versus stable. Just seems like it should work with /extra and/or slackbuilds.org. have you considered submitting your build scripts to slackbuilds.org?
Thanks. I will check out your build scripts but honestly I really feel I shouldn't need to have to use specialized scripts to make a common program work. I guess I take some responsibility for living on the edge and using -current versus stable. Just seems like it should work with /extra and/or slackbuilds.org. have you considered submitting your build scripts to slackbuilds.org?
No, they weren't mine per say. I really don't know why it is not working with the script provided in /extra. Glancing over it, it is very different compared to the other script. Gremlins is about the only other explanation. ;-)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.