Fatdog64-700/701 [April 22 2015] [CLOSED]

Message

olinm · #221 Post by **olinm** » Tue 17 Mar 2015, 09:44

http://www.theregister.co.uk/2015/03/17 ... rity_hole/

The OpenSSL Project will repair a "high severity" security hole in updates due Thursday.

jamesbond · #222 Post by **jamesbond** » Tue 17 Mar 2015, 09:57

dbabits wrote:Xlock-lockscreen does not work.
Prompts me to enter password.
Then gives :

Segment violation
/root/.xlockrc: bad crypted password
Clicking the applet afterwords simply doesn't do anything. Must delete /root/.xlockrc to get the password prompt again, but then the situation repeats.

I can't reproduce.

1. Make sure you remove /root/.xlockrc
2. Try to run xlock directly (that is, in terminal, just type xlock).
3. Does it work?
4. If it does, continue, otherwise report.
5. remove /root/.xlockrc again
6. from terminal, type "echo ab12345678 | makekey". You should get a result of 78LSVeQGsxYPc.
7. If everything works, remove /root/.xlockrc again.
8. Then run xlock-gui from terminal.
9. Report.

Thanks.

Semme · #223 Post by **Semme** » Tue 17 Mar 2015, 11:40

Hey, quick request here..

Is there an easy way for me to prune off a few menu entries besides moving desktop files out of /usr/share/applications or using gmenu-simple-editor? The latter here's not doing it. I also have several *double* entries..

Thanks.

jamesbond · #224 Post by **jamesbond** » Tue 17 Mar 2015, 11:51

Semme wrote:Is there an easy way for me to prune off a few menu entries besides moving desktop files out of /usr/share/applications or using gmenu-simple-editor? The latter here's not doing it.

Sure, open the deskop file with text editor and add "NoDisplay=true" to end of the file.

I also have several *double* entries..

Same, edit the desktop file with geany, then modify the "Categories" line. Categories are separated by semicolons, delete as needed.

01micko · #225 Post by **01micko** » Tue 17 Mar 2015, 12:29

Ted Dog wrote:half day forum outage and prodigal coder 01micko returns.. wild Sunday. You should post in the where in the world is 01micko thread.

Aw.. shucks!

jamesbond wrote:The problems with xvkbd is fixed by editing its resource files in /etc/X11/app-defaults/XVkbd-* (mainly XVkbd-common for "us" layout), no compilation needed. Using Dejavu fonts, I can get it to work for all layouts except Korean because I don't know which font has the required characters. I'll upload the fixed package soon.

Ah.. yes should of known.. still defouling

. Thanks for updating.

Anyway, as a further report on Acer Iconia w500, the accelerometer works! The driver is really crap; it's just a part of the acer_wmi module and events go through acpi so the only way to really poll the thing is by the device node. I found a python script which almost worked ootb but it has a bug with remapping the input, probably bitrot as it is from 2012, so getting long in the tooth. I should be able to glean enough info from it to rewrite it in C so dispensing with the python and it's deps (which were all on the devx anyway, but why have the devx on a tablet?).

Multi-touch is another story. Drivers are in infancy so I don't think we go there for now. Plus gtk support is skinny in gtk+-2.0 so I might go with some fat scroll bars and rough work arounds.

On the down side, guvcview is broken since k3.15. I know the effort you (james) went to to patch the current version for gtk+-2.0. I took a look at some recent sources myself and it looks like a big job to backport to 1.7.1. I might see of old luvcview works and try to pretty it up with some theming and fonts. Not sure how I will approach the rear camera though but I'll figure something out.
EDIT: No, luvcview suffers the same, and the UI is truly awful! VLC should work ok although it seems to run a bit slow using the front and rear camera.

Well, at least this is a bit of fun

Cheers

L18L · #226 Post by **L18L** » Tue 17 Mar 2015, 12:40

jamesbond wrote:
dbabits wrote:Xlock-lockscreen does not work.
Prompts me to enter password.
Then gives :

Segment violation
/root/.xlockrc: bad crypted password
Clicking the applet afterwords simply doesn't do anything. Must delete /root/.xlockrc to get the password prompt again, but then the situation repeats.
I can't reproduce.

1. Make sure you remove /root/.xlockrc
2. Try to run xlock directly (that is, in terminal, just type xlock).
3. Does it work?
4. If it does, continue, otherwise report.
5. remove /root/.xlockrc again
6. from terminal, type "echo ab12345678 | makekey". You should get a result of 78LSVeQGsxYPc.
7. If everything works, remove /root/.xlockrc again.
8. Then run xlock-gui from terminal.
9. Report.

Thanks.

Code: Select all

launch_xlock() {
    #xlock -mode ${MODE:-random} $PARAMS
	/usr/bin/xlock -mode ${MODE:-random} $PARAMS
}

Did the trick. (xlock is ELF and shell)

Should be in PUPPYPIN
because it does not make very much sense to launch it from /usr/local/apps
I have it in /usr/bin and linked to Xlock/AppRun

Semme · #227 Post by **Semme** » Tue 17 Mar 2015, 13:38

Tits JB, tits. Now sfs desktop's are in /usr/share/mimelnk/application, but they don't include categories.

Do I instead lose any extras from it's MimeType line >> application/vnd.oasis.opendocument.graphics for example?

The rt-clk menu's fine. It's the main menu that has the issue.

Thanks.

dbabits · #228 Post by **dbabits** » Tue 17 Mar 2015, 15:24

jamesbond,
at first, everything worked, except step 8, which gave me again

Segment violation
/root/.xlockrc: bad crypted password

Then I removed .xlockrc and tried step 8 again - and it worked(except it complained can't find font... using fixed..), but it did lock the screen!
So, not sure what to make of it, but let's close this for now, I'll report if I hit this problem again.
Thanks!

jamesbond wrote:
I can't reproduce.

1. Make sure you remove /root/.xlockrc
2. Try to run xlock directly (that is, in terminal, just type xlock).
3. Does it work?
4. If it does, continue, otherwise report.
5. remove /root/.xlockrc again
6. from terminal, type "echo ab12345678 | makekey". You should get a result of 78LSVeQGsxYPc.
7. If everything works, remove /root/.xlockrc again.
8. Then run xlock-gui from terminal.
9. Report.

Thanks.

Semme · #229 Post by **Semme** » Tue 17 Mar 2015, 19:49

And any chance we could get spot to execute wmexit without the password dialog? I can cheat if I have to..

I've gotta mention spots gtksu window *does NOT* consistently remember it's password.

Perhaps someone else experiences the same?

I'd prefer this user not to know roots pw.

jamesbond · #230 Post by **jamesbond** » Thu 19 Mar 2015, 15:06

@Semme: /usr/share/mimelnk/application/* are ignored.
Those multple entries in your screenshot comes from /usr/share/applications/libreoffice4.4-draw.desktop

@Semme: And any chance we could get spot to execute wmexit without the password dialog? I can cheat if I have to..

1. from terminal: chmod 0600 /etc/gtksudoer
2. edit /etc/gtksudoer and add a line at the bottom
spot spot /usr/bin/wmexit nopass

@all: it has been 3 weeks since 700 release and there have been few minor fixes since then. Do you reckon a 701 is necessary or useful? If released, 701 will only have fixes so far + perhaps new seamonkey/flash/openssl, that's it. No new kernel, etc.
The cons against releasing 701 is the effort probably needed to re-customise an existing 700 installation; if you already have a working 700 then why bother.

olinm · #231 Post by **olinm** » Thu 19 Mar 2015, 23:23

jamesbond wrote:The cons against releasing 701 is the effort probably needed to re-customise an existing 700 installation; if you already have a working 700 then why bother.

The Pros for releasing 701 is those that don't have a existing 700 installation , find is difficult to customise , security patch , fix audio and are waiting for Nvidia drivers that work , being a linux noob , need a working 700 to bother customising.

olinm · #232 Post by **olinm** » Thu 19 Mar 2015, 23:28

olinm wrote:http://www.theregister.co.uk/2015/03/17 ... rity_hole/

The OpenSSL Project will repair a "high severity" security hole in updates due Thursday.

The patches have now been released.

jamesbond · #233 Post by **jamesbond** » Fri 20 Mar 2015, 03:51

olinm wrote:
olinm wrote:http://www.theregister.co.uk/2015/03/17 ... rity_hole/

The OpenSSL Project will repair a "high severity" security hole in updates due Thursday.
The patches have now been released.

openssl 1.0.2a is now in the repo.

olinm · #234 Post by **olinm** » Fri 20 Mar 2015, 05:10

Would it be difficult or awkward to add an easy update option for openssl to the control panel?

The code is undergoing an audit and they seem to think there will more regular updates and patches as they work through it.

jamesbond · #235 Post by **jamesbond** » Fri 20 Mar 2015, 08:29

Openssl package, unlike firefox and chrome and flash, does not provide binary packages. One has to download and compile the openssl source package, pack it into a txz binary and upload it to the repo; it is not automatic.

olinm · #236 Post by **olinm** » Fri 20 Mar 2015, 08:35

BAH!

Shame Fatdog can't use standard slackware txz releases.

That would save a lot of time and work.

jamesbond · #237 Post by **jamesbond** » Fri 20 Mar 2015, 09:18

olinm wrote:Shame Fatdog can't use standard slackware txz releases.

Who says so? You can try, although not guaranteed to work

The package format is definitely fully compatible. You can even point out gslapt at Slackware's repository and you should be able to view them and install them (again - workability after installing is not guaranteed).

We did consider to build Fatdog from Slackware base (search this forum for Slackbones and you will find the thread) - but in the end we decided that building everything from scratch means that we have better control over package dependencies etc. E.g. the mplayer package from Slackware depends on samba (samba is a 40MB+ download, mplayer itself is only half that size - so, seriously?!). If we use Slackware as the base, and we don't like this, we will have to build our own version of mplayer and make sure it gets chosen over the Slackcware's one when people install it from the package manager. Tough stuff. And that it just one package. It turns out that we may want to update/modify many of the Slackware packages (about half of them) so in the end may as well we go the whole nine yard and build them all from scratch.

The idea has merits, though, if you're willing to live within the parent distro limitations. But why Slackware? If you want to build a Fatdog derived from some other distro, may as well go for Debian/Devuan or Ubuntu (or Fedora); they have a lot more packages than Slackware.

olinm · #238 Post by **olinm** » Fri 20 Mar 2015, 09:54

I did wonder why you didn't use *.deb files but it make sense now you have explained.

L18L · #239 Post by **L18L** » Fri 20 Mar 2015, 10:43

... and I did wonder why nobody seems to have read Fatdog's home page.

It is some how hidden and can be launched choosing Help from right click menu.

Let us put it into razor menu, too!

Just another icon would be nice.
..and another label? Home and FAQ

Semme · #240 Post by **Semme** » Fri 20 Mar 2015, 11:02

Well now JB, until I get my own 64bit box, I'll have to take your word on that.

My neighbors son pulled the plug on the project, opting for a more

impractical solution.

Hey, it's their money.

The spot exit tip's a good one.. One I'll be able to employ for the next round of KIS installs.

Thanks for your time.

As for a re-packaged distro, I think not. Whatever corrected additions you've made should be easy enough for any of us running Fatdog to find and apply, provided they're possibly in a central location and in their own FD-700 updates repo folder perhaps.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Fatdog64-700/701 [April 22 2015] [CLOSED]

Re: Xlock-lockscreen does not work

Re: Xlock-lockscreen does not work

Re: Xlock-lockscreen does not work

Fatdog's home page