Chromium package added to Alien Bob's repository!

1337_powerslacker · 11-23-2013, 04:46 PM

I just wanted to give a shout-out to Alien Bob for taking the time to build Chromium, and upload it for all and sundry to download. For a while now, I've wanted to try Chromium, but it's only been available in source form, and building the browser from source, while possible, is a serious pain in the posterior.

Where practical, I like to run open-source software on my computer, and I do. (Except for the AMD driver blob, that is!). But Chrome has been easier simply to download in the 64-bit .deb format, and run through the SlackBuild to produce a package to install. It works, but I've been bothered by the fact that Chrome is a closed-source package, not open to inspection. However, Chrome contains Flash, and while Flash has been universally condemned (perhaps rightly) as an outdated technology, a good percentage of websites still use it, and so we need something to help fill in the gap until Flash is finally extinct.

If I had gone ahead and downloaded the source for Chromium, built and installed it, it still wouldn't fill my needs, since Flash would be missing. Enter Alien Bob. His recent post helped cinch the decision for me. I took the plunge and downloaded both the browser and the plugin, and am happy to report that it is working fine for me, Flash and all.

A note to those who are running Chromium under KDE: When first launched, the kwallet program will appear shortly after Chromium launches. I first noticed this annoyance after I first installed Chrome, so I googled for a solution, and found this. However, for Chromium users, a small change is required. Instead of this:

Code:

[Auto Deny]
kdewallet=Google Chrome

Use this:

Code:

[Auto Deny]
kdewallet=Chromium

The same solution is achieved.

Thanks again, Alien Bob for taking the time to compile Chromium and giving us a tutorial on making it fully functional.

Regards,

Matt

samac · 11-23-2013, 05:50 PM

The other way you can do it is to set the kwallet password to a blank password, ie. no password at all.

samac

---------- Post added 11-23-13 at 11:50 PM ----------

The other way you can do it is to set the kwallet password to a blank password, ie. no password at all.

samac

samac · 11-24-2013, 04:20 AM

Strange, I can't edit the double post above.

samac

samac · 11-24-2013, 04:21 AM

Strange, when I post quick reply it submits the post twice, and I cannot edit it.

samac

samac · 11-24-2013, 04:24 AM

I cannot edit full stop. Using post reply sends once. Using post quick reply posts the reply and then comes up with the post reply screen, with a message saying that you have to wait 3 seconds before reposting.

I am going to send this one by post quick reply.

samac

---------- Post added 11-24-13 at 10:25 AM ----------

I cannot edit full stop. Using post reply sends once. Using post quick reply posts the reply and then comes up with the post reply screen, with a message saying that you have to wait 3 seconds before reposting.

I am going to send this one by post quick reply.

samac

Alien Bob · 11-24-2013, 06:49 AM

The whole idea behind integration with the Desktop Enviroment's encrypted password vaults (Kwallet in KDE and Gnome Keyring in other DE's) is that Chromium itself does not use any form of encryption when storing your passwords.

Try running this command when you do not use Kwallet or Gnome Keyring with Chromium:

Code:

sqlite3  ~/.config/chromium/Default/Login\ Data .dump

If Chromium is storing your passwords encrypted in Kwallet or Gnome Keyring, then that dump shows only the structure of the "logins" database. If you denied the use of an encrypted storage, you will see all your saved login data in cleartext.

For Google Chrome, that command would be:

Code:

sqlite3 ~/.config/google-chrome/Default/Login\ Data .dump

Eric

Speek · 11-24-2013, 07:11 AM

Thanks Eric! I have installed your package, but when I try to start chromium I get this:

Code:

[13770:13770:1124/140401:ERROR:shared_memory_posix.cc(213)] Creating shared memory in /dev/shm/.org.chromium.Chromium.pVJPdJ failed: Permission denied
[13770:13770:1124/140401:ERROR:shared_memory_posix.cc(216)] Unable to access(W_OK|X_OK) /dev/shm: Permission denied
[13770:13770:1124/140401:FATAL:shared_memory_posix.cc(218)] This is frequently caused by incorrect permissions on /dev/shm.  Try 'sudo chmod 1777 /dev/shm' to fix.

It's no problem for me to fix this, but I'm wondering if I'm the only one. I don't have an entry for /dev/shm in /etc/fstab.

Alien Bob · 11-24-2013, 07:55 AM

Quote:

Originally Posted by Speek

Thanks Eric! I have installed your package, but when I try to start chromium I get this:

Code:

[13770:13770:1124/140401:ERROR:shared_memory_posix.cc(213)] Creating shared memory in /dev/shm/.org.chromium.Chromium.pVJPdJ failed: Permission denied
[13770:13770:1124/140401:ERROR:shared_memory_posix.cc(216)] Unable to access(W_OK|X_OK) /dev/shm: Permission denied
[13770:13770:1124/140401:FATAL:shared_memory_posix.cc(218)] This is frequently caused by incorrect permissions on /dev/shm.  Try 'sudo chmod 1777 /dev/shm' to fix.

It's no problem for me to fix this, but I'm wondering if I'm the only one. I don't have an entry for /dev/shm in /etc/fstab.

I have this definition in /etc/fstab (Slackware's default, this is added by 'setup' during installation):

Code:

tmpfs            /dev/shm         tmpfs       defaults         0   0

And these are the permissions of /dev/shm :

Code:

$ ls -la /dev/ | grep shm
drwxrwxrwt  2 root root          60 Nov 24 14:52 shm/

I do not have the errors you are getting.

Eric

Speek · 11-24-2013, 08:22 AM

Quote:

Originally Posted by Alien Bob

I have this definition in /etc/fstab (Slackware's default, this is added by 'setup' during installation):

Code:

tmpfs            /dev/shm         tmpfs       defaults         0   0

I added the line to /etc/fstab, rebooted, and probllem solved! I must have removed this line some time. Many thanks!

frushiyama · 11-25-2013, 07:05 PM

I used the scripts with api from Alien`s to build the 31.0.1650.57 version.
Until now, all things working flawless, even the issue on this thread http://www.linuxquestions.org/questi...ox-4175474690/ is working with iced web.
Great work Eric!!
(This package is a great replacement for google chrome on Slackware tree)