Posted: Thu 14 Mar 2013, 12:00 Post_subject:
This is great! Works really wellSub_title: Created a script and .desktop to launch it

I am running Lucid 5.2.8 on a Motion M1300 tablet. My wife wanted to be able to read Kindle books using their Cloud Reader in Chrome, but I couldn't make it work with a new Chrome install. It was driving me nuts.

(Needed a new install because the .pet for Chrome does not support offline reading)

Neat. This could do with a wiki page listing offending applications that it works with (and any super offensive ones that it doesn't, if there are any) _________________DEATH TO SPREADSHEETS
- - -
Classic Puppy quotes
- - -
Beware the demented serfers!

I was able to get rid of the warning message in the vanilla ROX-Filer this way, too. I just had to override getgid instead of geteuid.

It looks (i.e. I tested that the programs start, but did not test all the features) like if you just override getuid() then you can use this to start bibledit as root, and to remove the warning message in the stock xsane.

I tried creating a single lib that overrides all three functions, and in the process demonstrated that there can be adverse effects: if geteuid is overridden then bibledit-gtk freezes on startup._________________DEATH TO SPREADSHEETS
- - -
Classic Puppy quotes
- - -
Beware the demented serfers!

I was able to get rid of the warning message in the vanilla ROX-Filer this way, too. I just had to override getgid instead of geteuid.

Weird - here I need to override geteuid for Rox.

Note that there are adverse effects with rox - it means when you open a terminal from rox it doesn't have root permissions._________________DEATH TO SPREADSHEETS
- - -
Classic Puppy quotes
- - -
Beware the demented serfers!

FWIW I can also get rid of an offensive running as root warning in mousepad by overriding geteuid. But it causes this error message, although I don't know what actual adverse effects there are:

Code:

Mousepad-Message: Failed to connect to the D-BUS session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Thanks! I also got the "can't run as root" message after installing Chrome (Version 31.0.1650.4 and the puppy-gc-001 pet worked. However I did have to modify /usr/bin/puppy-chrome line 3 to "google chrome-stable" to match the package. So far Chrome seems to be running fine however after launching I did get this: