Page 9 of 12
Posted: Sun 17 Mar 2019, 05:06
by ttuuxxx
Ok I went to compile inkscape lite because its usually in puppy and isn't in this one , and when it was compiling I had 2 errors one was it couldn't find the freetype config file, I looked and it wasn't there, So I recompiled the freetype that comes with Buster and looked in the folder and it wasn't copied so I added it to the folder and make a package for your next update. I also fixed the error with inkscape in the sources it was a typo.
http://smokey01.com/ttuuxxx/DpupBuster/ ... 1-i386.pet
http://smokey01.com/ttuuxxx/DpupBuster/ ... 1-i386.pet
http://smokey01.com/ttuuxxx/DpupBuster/ ... s-i386.pet <-- main app
http://smokey01.com/ttuuxxx/DpupBuster/ ... s-i386.pet <-- docs
http://smokey01.com/ttuuxxx/DpupBuster/ ... s-i386.pet <--language files
ttuuxxx
Posted: Sun 17 Mar 2019, 05:22
by greengeek
ttuuxxx wrote:Ok I ran out of space, lol I only run live, So when you compile so much, it doesn't take long, So I installed my gimp pet and guess what it didn't work, it was missing some .so links lol really guys didn't anyone try it?
Yes, I did. On Slacko 5.6
Linked a heap of .so.4077.whatever files to so.0, bt still endde up with a Glibc error so assumed it's just not compatible for me so no point posting.
Should I try again or am i likely to still be running the wrong glibc?
Posted: Sun 17 Mar 2019, 05:38
by ttuuxxx
Thanks for reminding me greengeek the .so files weren't copied to the freetype either so I deleted the one on the server and reuploaded it fixed. So anyone who downloaded freetype package I made delete it and redownload it
I'm going to have to check every time now.
ttuuxxx
Posted: Sun 17 Mar 2019, 06:03
by greengeek
Just tried the new one but same final issue:
Code: Select all
# gimp
(gimp:21707): GLib-WARNING **: goption.c:2179: ignoring no-arg, optional-arg or filename flags (8) on option of arg-type 0 in entry (null):debug-handlers
gimp: symbol lookup error: gimp: undefined symbol: g_type_check_instance_is_fundamentally_a
#
Ok, I'm not running Dpup Buster but I figured what the heck - Slacko 5.6 runs Debian stuff so I'll try it anyway.
I t was worth a go 'cos i love your trimmed down approach.
EDIT - Glib error, not GlibC error
cheers!
Posted: Sun 17 Mar 2019, 06:19
by greengeek
By the way - i did try DpupBuster but all i got when booting from CD was a blinking hyphen on a black background. Same as I got with rcrsn51's Deb stretch live starter kit Probably something I should be able to solve with the correct kernel parameter for video but i havent got that far yet.
gimp ttuuxxx
Posted: Sun 17 Mar 2019, 13:14
by josejp2424
ttuuxxx wrote:Ok I looked at the repo for gimp and it was like 110MB, really??, Naaa I don't need to waste that sort of space/memory on gimp, Plus I don't like the latest ones where you have to export image files, I like just saving them as they are. So I went back to my favourite series of gimp 2.4 series and well, to make it work on modern backends you have to patch a bunch of stuff but anyways I got it going, I did have 1 start up error but it looks like it went away once I made a basic .desktop file. I made a new splash screen using it so it looks more modern when opening, Compared to newer gimps, this one starts up lightning fast. The best Part its only 6MB a saving of 104MB over the repo vervsion, Its actually small enough to maybe have it included, I made it the default paint app also, I removed the gimp console since nobody really uses it and it just takes up space. Well give it a try and let me know what you think
Took me hours to get it compiling right.
ttuuxxx
http://smokey01.com/ttuuxxx/DpupBuster/ ... 7-i386.pet <-- main app
http://smokey01.com/ttuuxxx/DpupBuster/ ... 7-i386.pet <-- 105 extra brushes and 131 extra gradients
http://smokey01.com/ttuuxxx/DpupBuster/ ... 7-i386.pet <-- Dev files for compiling plugins
http://smokey01.com/ttuuxxx/DpupBuster/ ... 7-i386.pet <-- documents if needed
http://smokey01.com/ttuuxxx/DpupBuster/ ... 7-i386.pet <-- Other Language files
thanks ttuuxxx
Actually I prefer gimp2.4 to mtpait.
and I would put it in the iso.
but I do not know how they would take it.
gimp-splash
http://www.murga-linux.com/puppy/viewtopic.php?t=64564
Re: gimp ttuuxxx
Posted: Sun 17 Mar 2019, 15:54
by ttuuxxx
josejp2424 wrote:ttuuxxx wrote:Ok I looked at the repo for gimp and it was like 110MB, really??, Naaa I don't need to waste that sort of space/memory on gimp, Plus I don't like the latest ones where you have to export image files, I like just saving them as they are. So I went back to my favourite series of gimp 2.4 series and well, to make it work on modern backends you have to patch a bunch of stuff but anyways I got it going, I did have 1 start up error but it looks like it went away once I made a basic .desktop file. I made a new splash screen using it so it looks more modern when opening, Compared to newer gimps, this one starts up lightning fast. The best Part its only 6MB a saving of 104MB over the repo vervsion, Its actually small enough to maybe have it included, I made it the default paint app also, I removed the gimp console since nobody really uses it and it just takes up space. Well give it a try and let me know what you think
Took me hours to get it compiling right.
ttuuxxx
http://smokey01.com/ttuuxxx/DpupBuster/ ... 7-i386.pet <-- main app
http://smokey01.com/ttuuxxx/DpupBuster/ ... 7-i386.pet <-- 105 extra brushes and 131 extra gradients
http://smokey01.com/ttuuxxx/DpupBuster/ ... 7-i386.pet <-- Dev files for compiling plugins
http://smokey01.com/ttuuxxx/DpupBuster/ ... 7-i386.pet <-- documents if needed
http://smokey01.com/ttuuxxx/DpupBuster/ ... 7-i386.pet <-- Other Language files
thanks ttuuxxx
Actually I prefer gimp2.4 to mtpait.
and I would put it in the iso.
but I do not know how they would take it.
gimp-splash
http://www.murga-linux.com/puppy/viewtopic.php?t=64564
well in the past I've made a few puppies with gimp and no mtpaint and took some heat for it, lol Then other times I included both since mtpaint is so small and that went over fine, but I also had gimp as the defaultpaint app and that worked well. Don't forget to use the freetype packages I provided that fixes the missing config file.
ttuuxxx
Posted: Sun 17 Mar 2019, 17:03
by Terry H
Downloaded the gimp + brushes and feetype pets. Did a basic edit on a jpg. Working well. This is an excellent version of gimp.
Thanks ttuuxxx these contributions.
Changes to jwmrc-theme
Posted: Sun 17 Mar 2019, 17:22
by Terry H
One of gthe things I normally do manually, is change the background color of hte JWM Trays, by manually editing ~/.jwm/jwmrc-theme. In this puppy that change and other manual changes does not have any effect. What is different between this and other puppies?
JWMdesk
Posted: Sun 17 Mar 2019, 21:48
by josejp2424
Terry H wrote:One of gthe things I normally do manually, is change the background color of hte JWM Trays, by manually editing ~/.jwm/jwmrc-theme. In this puppy that change and other manual changes does not have any effect. What is different between this and other puppies?
The configuration is managed by JWMdesk
Kodi-17.6-Krypton
Posted: Sun 17 Mar 2019, 21:53
by josejp2424
Re: JWMdesk
Posted: Sun 17 Mar 2019, 23:15
by Terry H
josejp2424 wrote:Terry H wrote:One of gthe things I normally do manually, is change the background color of hte JWM Trays, by manually editing ~/.jwm/jwmrc-theme. In this puppy that change and other manual changes does not have any effect. What is different between this and other puppies?
The configuration is managed by JWMdesk
In JWM, for some time, the colors can be edited in the ~/.jwm/jwmrc-theme, which will be reflected on the desktop. I have done this in puppies for a while. The highlighted details below should display the tray backgrounds in a gradient white / black. This is not occurring in dpup buster. The default tray in dpup buster shows that a gradient background should be displayed, however it is showing only dark grey trays.
I'm just trying to find out why this is different in dpup buster.
<?xml version=1.0?>
<JWM> <!-- adapted from autogestion's Aurora -->
.
.
.
<TrayStyle>
<Font>Sans-10</Font>
<Foreground>#A2A2A2</Foreground>
<Background>#181920</Background>
<Active><Foreground>white</Foreground>
<Active><Foreground>white</Foreground>
<Background>#FFFFFF:#000000</Background></Active> < Changes made here
</TrayStyle>
Posted: Mon 18 Mar 2019, 02:32
by musher0
Hi Terry H.
Use another WM/traybar combination ?
Don't buck!
E.g.:
Icewm has 400 themes, I think.
bmpanel2 about 45?
waimea will let you "paint" all manner of tranparency and shading in the title bar
and menus. (Yeah, that's a plural: menuS!)
Etc.
There are a lot of themes, etc. for a lot of WMs at
https://www.box-look.org.
Just a thought. BFN.
Posted: Mon 18 Mar 2019, 03:08
by Terry H
musher0 wrote:Hi Terry H.
Use another WM/traybar combination ?
Don't buck!
E.g.:
Icewm has 400 themes, I think.
bmpanel2 about 45?
waimea will let you "paint" all manner of tranparency and shading in the title bar
and menus. (Yeah, that's a plural: menuS!)
Etc.
There are a lot of themes, etc. for a lot of WMs at
https://www.box-look.org.
Just a thought. BFN.
That's not the point. This is an alpha release, I'm raising something that appears to not be functioning correctly.
Posted: Mon 18 Mar 2019, 03:46
by musher0
Hi Terry H.
Ok. Blame it on my anything-but-jwm bias!
I'd be surprised if it was a bug created by DPupBuster, though. I'd suggest the bug is
upstream: in the Debian compilation or packaging, or even in the jwm code itself?
I say that because usually Puppy devs do not fiddle with the ready-made packages
they import from the respective repos. They just incorporate them.
BFN.
Re: JWMdesk
Posted: Mon 18 Mar 2019, 04:07
by MochiMoppel
Terry H wrote:I'm just trying to find out why this is different in dpup buster.
<?xml version=1.0?>
<JWM> <!-- adapted from autogestion's Aurora -->
.
.
.
<TrayStyle>
<Font>Sans-10</Font>
<Foreground>#A2A2A2</Foreground>
<Background>#181920</Background>
<Active><Foreground>white</Foreground>
<Active><Foreground>white</Foreground>
<Background>#FFFFFF:#000000</Background></Active> < Changes made here
</TrayStyle>
Take a close look at the syntax. This can't work.
2 <Active> opening tags and only 1 closing tag.
The settings for active Foreground and Background must be surrounded by Active tags:
<Active><Foreground>white</Foreground></Active>
<Active><Background>#FFFFFF:#000000</Background></Active>
Don't know if this makes sense and if it works. Depends on the JWM version and where the settings are stored. (if in /root/.jwm/jwmrc-personal it would override any settings in /root/.jwm/jwmrc-theme)
Posted: Mon 18 Mar 2019, 17:44
by musher0
Hi.
To come back to the bug that makes two freememapplet_tray icons appear in the tray,
which I briefly described
here:
I solved it by recreating the approach in the freememappletshell (in DPupStretch and
probably other Pups), i.e. kill freememapplet_tray before (re)starting it. Something like:
Code: Select all
killall -q freememapplet_tray
sleep 0.1s
freememapplet_tray &
sleep 0.1s
works.
Previously, I was using the approach:
Code: Select all
[ "`pgrep freememapplet_tray`" = "" ] && freememapplet_tray
which did not do anything to prevent the bug.
IHTH.
~~~~~~~~~~~~~~~~~
On the issue of swappiness, I have decided to set it like so:
Code: Select all
#!/bin/ash
# Set vm.swappiness:
sysctl vm.swappiness=50
# 10 # Ex-factory value.
ROX-Filer's performance was too sluggish for my taste with the value 10.
Description of my computer is attached, produced with
YMMV.
Again IHTH
~~~~~~~~~~~~~~~~~~
FWIW, I gave HardInfo the pink slip, for abusing my patience.
Why did HardInfo run through the whole series of tests when I had specifically asked
it to provide me with a summary in text format by un-ticking all the irrelevant boxes?
As I said, that is an abuse of my patience.
You'll find lshw via the PPM. It has a GUI too; but don't bother, it looks quite ugly
and amateurish (IMO), compared to what we are used to in PuppyLand.
BFN
Posted: Mon 18 Mar 2019, 19:26
by Terry H
musher0 wrote:
On the issue of swappiness, I have decided to set it like so:
Code: Select all
#!/bin/ash
# Set vm.swappiness:
sysctl vm.swappiness=50
# 10 # Ex-factory value.
ROX-Filer's performance was too sluggish for my taste with the value 10.
BFN
I noticed in ~/startup there is a script
set-swappiness to set swappiness to 10. I changed mine to 50 as you have. [/i]
Re: JWMdesk
Posted: Mon 18 Mar 2019, 19:36
by Terry H
MochiMoppel wrote:Terry H wrote:I'm just trying to find out why this is different in dpup buster.
<?xml version=1.0?>
<JWM> <!-- adapted from autogestion's Aurora -->
.
.
.
<TrayStyle>
<Font>Sans-10</Font>
<Foreground>#A2A2A2</Foreground>
<Background>#181920</Background>
<Active><Foreground>white</Foreground>
<Active><Foreground>white</Foreground>
<Background>#FFFFFF:#000000</Background></Active> < Changes made here
</TrayStyle>
Take a close look at the syntax. This can't work.
2 <Active> opening tags and only 1 closing tag.
The settings for active Foreground and Background must be surrounded by Active tags:
<Active><Foreground>white</Foreground></Active>
<Active><Background>#FFFFFF:#000000</Background></Active>
Don't know if this makes sense and if it works. Depends on the JWM version and where the settings are stored. (if in /root/.jwm/jwmrc-personal it would override any settings in /root/.jwm/jwmrc-theme)
Thanks MochiMoppel, your response made me realise my error, so my issue is now solved, it was my error, I made a mistake thinking I was changing the whole Panel color. However the <Active> .... </Active> is referring to the
Active Window coloring and is valid to set it as a grouping for foreground and backgropund. Each line does not have to be set individually.
Posted: Mon 18 Mar 2019, 22:12
by futwerk
new backgrounds.