(old)Puppy Linux Discussion Forum

LxPupArtful-17.11 has been uploaded....
a derivative of ArtfulPup-17.11+3
so same kernel 4.9.59 32-bit pae
and same applications
and same repositories in PPM

YES ,
Installed without a hitch or a snort to my i5 based Fujitsu S761. As usual, a Frugal Grub4Dos install with a 256Mb unencrypted EXT2 savefile. SNS used for the wireless connection. Lid and button suspends work OOTB, rightclick and drives on desktop options installed. Slimjet 15.1.6.0 running from SFS with both its profile and that of Sylpheed symlinked to the profiles on the EXT2 data partition. RedshiftGUI 0.2.1 installed from a local pet just fine. I do pull the & at the end of line 5 in /root/Startup/1-lxde-startup.sh for a bit of delay so the drives on desktop pick up the correct background. Other than that, boots, reboots, WM restarts all perfect OOTB. Thanks!

LxPupXenial-17.11+3 has been uploaded

based on 666philb's new XenialPup-7.5

LxPupXenial-17.11+3 includes xenialfix-3

ISO

Delta

.pet to give LxPupArtful and LxPupXenial the look of RasperryPi Pixel v2.2:
https://sourceforge.net/projects/lxpup/ ... t/download

LxPupArtful running sucessfully with the 4.14.11 32b PAE kernel from LxPupSc 18.01 +1T. glxgears FPS and hardinfo CPUhash and FPUraytracing benchmarks pretty much unchanged from the stock kernel on this i5. By the release notes and kernel changelog the 4.14.11 should have kpti backported into it.

# inxi -bw
System: Host: puppypc15186 Kernel: 4.14.11-lxpup-32-pae i686 (32 bit)
Desktop: LXDE (Openbox 3.6.1) Distro: ArtfulPup 17.11
Machine: Device: laptop System: FUJITSU product: LIFEBOOK S761 serial: R2500459
Mobo: FUJITSU model: FJNB225
UEFI [Legacy]: FUJITSU // Phoenix v: Version 1.17 date: 03/14/2012
Battery CMB1: charge: 56.0 Wh 100.0% condition: 56.0/56.0 Wh (100%)
CPU: Dual core Intel Core i5-2520M (-HT-MCP-) speed: 2501 MHz (max)
Graphics: Card: Intel 2nd Generation Core Processor Family Integrated Graphics Controller
Display Server: X.org 1.19.5 drivers: modesetting (unloaded: fbdev,vesa)
tty size: 80x24 Advanced Data: N/A for root
Network: Card-1: Intel 82579LM Gigabit Network Connection driver: e1000e
Card-2: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express)
driver: ath9k
Drives: HDD Total Size: 64.0GB (25.4% used)
Weather: Conditions: 4 F (-15 C) - Clear Time: January 6, 11:33 AM CST
Info: Processes: 121 Uptime: 2:11 Memory: 171.7/4897.3MB
Client: Shell (bash) inxi: 2.3.7

cheers,

Edit: As in ArtfulPup, with the newer kernel on the i5 laptop hardware I add the following to rc.local to bring the grightness up on boot:

LxPupArtful-17.11+4 has been uploaded - based on ArtfulPup-17.11+11

iso

delta

peebee wrote:LxPupArtful-17.11+4 has been uploaded -

Hi Peebee,

Thanks for this latest. Installed to Core i3 laptop, intel graphics & 8gb ram. All is good, except for the below: Palemoon 27.1.2 was installed via PPM (after updating PPM). It runs fine if I just ignore this "dbus daemon" pop-up & close it out (this pop-up happens every time you start Palemoon). Phil's Xenials had this problem last year, and Phil had us installing Tahr's dbus-daemon as a fix. Is there still no proper, correct fix for this (running "ldconfig" in terminal does nothing to help either)??

At some point, I would think, running the tahr dbus daemon in xenial/artful pups (& above) is going to cause problems with something.

27.1.2 ????? that's a very old version of Palemoon.

Please try 27.7.1 obtainable via Internet -> Get Web Browser
or direct from:
https://sourceforge.net/projects/lxpup/ ... /browsers/

No such warnings with 27.7.1 here!

peebee wrote:27.1.2 ????? that's a very old version of Palemoon.

Please try 27.7.1 obtainable via Internet -> Get Web Browser
or direct from:
https://sourceforge.net/projects/lxpup/ ... /browsers/

No such warnings with 27.7.1 here!

Well, I'm open to new suggestions. I also re-downloaded LxPup, did another "fresh" frugal install, installed a fresh "Palemoon" 27.7.1 in /opt, also tried your linked Palemoon, and same behavior in all the OSes. For reference, this was discussed in Phil's Xenial thread (~pgs 15-20) and no resolution could be found. Phil did something in his last latest release, and the behavior went away. In Artful, for me, it has always been there. I just wanted to take a chance and see if it was fixed. Radky is the one who found this bug/problem, and having to revert back to the dbus-daemon from Tahr. Oh well....thanks again, Peebee. I'll come back down the road and try later iterations of LxPup to see if it is fixed.

@belham2: I think it was fixed by recompiling dbus --with-x ? Not sure but here is the fixed pet for stretch:
http://01micko.com/wdlkmpx/puppylinux/p ... dpup-2.pet

I don't know if it works in anything else and/or if there's more that needs to be done though.

edit Found more info here: https://github.com/puppylinux-woof-CE/w ... -359250179

The panels shown in your screenies seem to indicate that you've got other apps installed?

Have you tried Palemoon on a pristine install of LxPupArtful?

I'm not able to reproduce your problem ATM I'm afraid.....anybody else seeing what @belham2 observes??

peebee wrote:The panels shown in your screenies seem to indicate that you've got other apps installed?

Have you tried Palemoon on a pristine install of LxPupArtful?

I'm not able to reproduce your problem ATM I'm afraid.....anybody else seeing what @belham2 observes??

hi Peebee,

I refused to give up on this, 'cause I like LxPupArtful.

Yes, have done maybe 5 fresh, pristine 'frugal' installs now. Two different downloaded ISOs. Not a thing added to these 'frgual' installs except Palemoon. Sadly, same behavior...but only in "Run-As-Spot" mode. When running as "root" all is well.

What is queer is that Palemoon runs like a champ in all instances (SFS and/or installed direct to /opt) as long as everything stays "root". The moment I click "Login and Security Manager" and ask it to set up Palemoon as "Spot", the behavior I described starts again---for both an SFS-loaded Palemoon and/or direct installed.

Could something be screwed up in the Run-as-Spot thing? Maybe it is outdated? Or not compatible with LxPupArtful?

Drives me nuts that in Phil's Xenial, I can't reproduce this problem, nor can I reproduce it in LxPupSc (or any other pups and/or ddogs).

The problem has become unique for me in LxPupArtful. Usually, i had ignored it, but thought I post the other day and ask you. I wonder what in heck did Phil do to stop this behavior for Palemoon during the middle of last year in his Xenials? After July/August, once the next iterations of Xenialpup came out (all the way up to the final 7.5), the problem just disappeared without us having to do anything (no dbus swapping from Tahr).

belham2 wrote:...but only in "Run-As-Spot" mode. When running as "root" all is well.

Aaaaaahhhhh .... significant extra information not mentioned previously....

Palemoon when run-as-spot in both LxPupArtful and LxPupXenial produces the warning on startup.

Palemoon in LxPupSc run-as-spot does not exhibit this warning.

Other web browsers run-as-spot in LxPupArtful do not exhibit this warning - i.e. Light, Firefox and Chromium (always runs-as-spot).

My advice is therefore do not run Palemoon as run-as-spot in Ubuntu based LxPups.....either run Palemoon as root or run another browser as spot.

belham2 wrote:It runs fine if I just ignore this "dbus daemon" pop-up & close it out (this pop-up happens every time you start Palemoon).

For fix see:
http://murga-linux.com/puppy/viewtopic. ... 274#982274

Will find it's way into next LxPupArtful and LxPupSc updates....

LxPupArtful-17.11+5 has been uploaded - based on ArtfulPup-17.11+14

iso

delta

includes the fix to run-as-spot for mozilla webbrowsers

Both LxPupArtful (+4 to +5) and ArtfulPup (+13 to +14) updated on two of my i5 laptops using the deltas. md5sums correct, No issues expected, none seen in a days use of both. I am running the 4.14.17 64-bit kernel from the most recent LxPupSc uneventfully in these, mostly for the meltdown & spectre mitigation. I use pretty much the stock disk-drive icon placement in Artful and set up my own desktop layout in LxPupArtful where it's pie-simple. Right now, LxPupArtful seems to be my top dog. I'm always amazed when I commit some error like not loading a browser SFS or something that goofs up a .desktop and the LXDE panel just quietly hides the associated item in the panel launchers and when I miss it, scritch my head, fix the .desktop and restart the WM it's back. I've blown any number of XFCE4 panels and 'reverted' more than a few jwm panels doing similar things

peebee wrote:

belham2 wrote:...but only in "Run-As-Spot" mode. When running as "root" all is well.

Aaaaaahhhhh .... significant extra information not mentioned previously....

Palemoon when run-as-spot in both LxPupArtful and LxPupXenial produces the warning on startup.

Palemoon in LxPupSc run-as-spot does not exhibit this warning.

Other web browsers run-as-spot in LxPupArtful do not exhibit this warning - i.e. Light, Firefox and Chromium (always runs-as-spot).

My advice is therefore do not run Palemoon as run-as-spot in Ubuntu based LxPups.....either run Palemoon as root or run another browser as spot.

Hi Peebee,

Got your message. Have been running Palemoon run-as-spot no problems now.

Thanks!

LxPupArtful-17.11+6 has been uploaded - based on ArtfulPup-17.11+16

iso

delta

peebee wrote:LxPupArtful-17.11+6 has been uploaded - based on ArtfulPup-17.11+16

Wow! Great! (Updating...) Thanks so much!