Chrome: Prevent the Gnome-Keyring Dialogue (Chrome and Chromium)

You have once again entered the Chrome world of survival horror… Good Luck…

For the purposes of this post, I’ll be referring to Chrome & Chromium as Chromium because Chromium is the open source code-base from which your Chrome is built and I use the “Chromium” build so it makes my life easier to just call them both Chromium. Apply your own changes where needed. Now, to get rid of that annoying prompt…

It’s come to my attention that this is very poorly documented and many people are left wondering, “How do I get rid of that annoying dialogue when Chrome (or Chromium) starts?”

Do not despair, it’s actually quite simple. For the purpose of this exercise, I’ll refer to Chrome as Chromium, but they are essentially the same browser (the precise differences have to do with licencing and who exactly builds it). In a nutshell, you use the --password-store=basic argument. There’s a little more detail below.

If you’re using a launcher (that means an icon you click on), simply right-click it and select “edit” or the nearest equivalent. Now add the following to the end of the path --password-store=basic (yes, the space). Obviously if you’re launching it via the CLI, you’d type chromium --password-store=basic and problem solved.

You may want to make this change permanent, in which case (reasonably savvy users only) will edit the chromium execute script itself. Depending on your distro, it may be in an alternative location, but generally it is /usr/bin/chromium. This file is a plain old shell script so editing it is simple, and I’ll make it even simpler by saving you the hassle of finding what to edit. The variable you want is CHROMIUM_FLAGS and all you need to do is append --password-store=basic to it, after everything else in the script has modified the variable. So place the following line:
CHROMIUM_FLAGS="$CHROMIUM_FLAGS --password-store=basic"
above the last if-block, which reads so:
if [ $want_debug -eq 1 ] ; then
Protip: You can add any other arguments you wish to make permanent to CHROMIUM_FLAGS.
Notes: There’s always a danger with messing with a software’s launch script. Be careful what you add. Backing up the script is always recommended.
Whenever you update Chromium, it’ll overwrite your changes.
Don’t forget that you need to be root :p

As usual, feel free to leave comments, ask questions, or post death threats using the comment button below. If you found this post useful, it’s good to share or like it, or even both.

Share the Love:

Easy Print:

Advertisements

Mednafen: Dealing with CD Image Problems

This post assumes the following:

*. You’re running a Linux OS environment
*. You can install software
*. You’re not afraid of spending about two minutes in front of the CLI.
*. You’re having some sort of problem running a CD image. This post is specific to PlayStation games but it’s probably applicable to any other CD-based consoles too.
*. You’re a Mednafen user of any level (novice to expert).

Before we proceed with the real troubleshooting, it is important to note that with Mednafen, one does not open the actual image file. To play a game, you’ll need to open the accompanying cue sheet (a .cue file). So, firstly, make sure of the following:

*. You’re opening the accompanying .cue file, not the .bin or other image file

So, having gotten that out of the way, now we can actually start troubleshooting. The following is a list of common problems:

*. I have a .mdf and .mds file
*. I have no .cue file.
*. I only have a .iso file.
*. I only have a .bin file.
*. I have some other format that doesn’t work

To proceed, you need to install mdf2iso. If you don’t know how to, see your distribution’s documentation or glean this table (the Arch Wiki is one of the best information sources, even for non-Arch users). So:

*. Install mdf2iso. Read the man page too (yeah right).
*. Open the CLI in the same directory as your problem CD image. For this example, our game is called Example.

Now, back to the problems. Below are all your solutions in Q & A format:

Q: My file is Example.mdf
A: That’s what this was originally about. Issue the following command:
$ mdf2iso --cue Example.mdf
Short wait. A .cue file will be created. You do not need to convert the image, but simply generate the cue sheet. Open Example.iso.cue and play.

Q: My file is Example.iso
A1: Issue the following command:
$ mdf2iso --cue Example.iso
Somewhat of a wait. A .bin file and an accompanying cue sheet called Example.iso.bin and Example.iso.cue respectively will be generated from your ISO file. Open Example.iso.cue and play.

Q: I have some other format Mednafen won’t play
A: Try the procedure. If it works you’ll get one of the above results.

Q: I only have a .bin file
A: This is unlikely if you ripped it yourself (implicit accusation unto illegitimate dealings). Luckily there’s a an archive at redump.org that will likely have the cue sheet you need. You can select your system from the Discs menu. This is not intended to enable you if you obtained a rip illegally.

If mdf2iso does not work for you, don’t panic. There are many conversion tools out there and the easiest and safest way to find them is to search for the image’s format (usually indicated by the file extension) in your package manager’s database. You should find some tools, even if all they do is mount the image (note mounting the image should be a last resort and won’t be discussed further as it is outside the scope of this post).

If you found this post useful then please like it, tweet it, or whatever. Questions, queries and feedback welcome, simply leave a comment.

Share the Love:

Easy Print: