LxPupSc64 - 64bit version of Puppy with the LXDE desktop

[Billtoo]

Installed 18.06+9-uefi to the hard drive of HP desktop:

System: Host: puppypc9263 Kernel: 4.17.0-lxpup64 x86_64 (64 bit) Desktop: LXDE (Openbox 3.6.1)
Distro: LxPupSc64 18.06
Machine: Device: desktop System: Hewlett-Packard product: p7-1246s serial: MXX232077R
Mobo: Foxconn model: 2ADA v: 1.00 BIOS: AMI v: 7.12 date: 06/07/2012
CPU: Quad core Intel Core i5-3550 (-MCP-) speed/max: 1602/3301 MHz
Graphics: Card: Intel Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
Display Server: X.org 1.20.1 driver: intel tty size: 180x31 Advanced Data: N/A for root
Network: Card-1: Ralink RT5390 Wireless 802.11n 1T/1R PCIe driver: rt2800pci
Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
Drives: HDD Total Size: 2000.4GB (1.0% used)
Weather: Conditions: 72 F (22 C) - Mostly Cloudy Time: October 11, 5:05 PM EDT
Info: Processes: 146 Uptime: 1:22 Memory: 372.2/11901.7MB Client: Shell (bash) inxi: 2.3.8

Added Kpat and Smplayer/Smtube,no luck with Kodi.
Added Chromium64_69.0.3497.100+pepper_31.0.0.122_lx_spot.sfs

Thanks.

[ozsouth]

I have had trouble playing some videos via seamonkey 2.49.4 - works fine in Slacko64-6.9.9.9, Xenialpup64 7.5, Bionicpup64 7.9.5. Video advances to (at best) advert and stops, sometimes locking up. Main site I've noticed is afl.com.au (any video in middle of page). Have tried adding extra gtk3 packages, changing about:config, turning off acceleration - no avail. Versions of Palemoon before 28.0 & supplied Light browser work. Any ideas?

EDIT: this is a GTK3 problem. Seamonkey64-2.48 (gtk2) works fine. If only it was secure.

EDIT2: apulse libs are in /usr/lib64 - apulse executable points to /usr/lib/64/apulse folder. When moved there, videos work!
.

[peebee]

Interim delta to 18.06+11-uefi

iso md5 = 29fe9aa0fe97a5db3840f1ff2079be1e lxpupsc64-18.06+11-uefi.iso

Just Slackware64 Current updates to Sat Oct 27 18:22:46 UTC 2018 + reversion to pup-volume-monitor-0.1.15

Later 64-bit kernels (4.19.x) are available

[wadmalaw]

Mounted volumes disappear from desktop and pcmanfm panel when attach external drive (pcmanfm bookmarks remain and function though).

Since about k 4.18.10 (through subsequent kernel updates posted and OS updates). Various obvious gui setting changes had no positive effect (pcmanfm/event manager). Tested when new OS 18.06 updates posted (without save folder) and same result. Thought it might be particular to this system but recent load (no save folder) to laptop produced same result.

Checkums matched prior to install. No idea if kernel or OS upgrade specific but sometimes pmount automatically popped up and sometimes not. (Pmount always worked as expected though.)

Reinitializing pup-volume-monitor-starter consistently works for me. (Plug in external drive, wait for volume icons to disappear, reinitialize pup-volume-monitor-starter and all volumes show up and fully functional again in pcmanfm and desktop.)

This isn't a big deal, just a tip for anyone else who has adopted this as their main and experiencing same perplexing issue and is of similar dubious skill level. (I'd gotten really used to letting pcmanfm handle drive mounts/unmounts.) Bear in mind it could still be something weird I've done causing this...

Thanks for keeping so many things updated PeeBee, greatly appreciate your efforts.

[peebee]

Mounted volumes disappear from desktop and pcmanfm panel when attach external drive

Thank you for the report which I have verified....

Problem can be traced back to change to 64-bit pup-volume-monitor-0.1.17 on or about 15-sep-2018.

Have reverted back to pup-volume-monitor-0.1.15 in delta 18.06+11

The dmesg crash with 0.1.17 is:

Code: Select all

pool[7353]: segfault at 40 ip 00007f2127bb54f0 sp 00007f21263b6dd8 error 4 in libpupvm.so.0.0.0[7f2127ba9000+13000]
Code: 40 00 48 8b 05 11 6b 20 00 48 8b 00 48 85 c0 74 e4 ff d0 48 89 df 5b e9 de aa ff ff 0f 1f 40 00 66 2e 0f 1f 84 00 00 00 00 00 <8b> 47 40 85 c0 74 09 48 8b 07 ff a0 a0 00 00 00 c3 0f 1f 44 00 00

I'll report it on github.

[wadmalaw]

Thank you PeeBee, didn't expect you to look into it so quick, thought maybe it'd go in the lower levels of a punch list.

Volumes stay put with 18+11. Nice to have them arranged in the expected order. Pmount automatically popped up when attached external drives, doesn't bother me at all.

Everything else you said was way beyond me.

I am really liking this OS. Thanks again.

[peebee]

I have had trouble playing some videos via seamonkey 2.49.4

I downloaded the UNOFFICIAL 64-bit seamonkey-2.49.4......(only 32-bit seamonkey is official).....
I installed my 64-bit gtk+3 pet that I use in other browsers
I extracted seamonkey to a directory and ran it directly from there...

in my 2 standard tests (youtube and bbc-iplayer) videos and sound played correctly..........no changes to apulse were required.....

[norgo]

@ozsouth

to change settings on spec won't help you along.
find out what your SM version has included and what system components are used.

type about:buildconfig in address line of SM and press enter

look whether SM has been built with pulseaudio support or not
in case of built without pulseaudio you should find the entries ( --disable-pulseaudio --enable-alsa )

is system or internal libvpx used ?
in case of system libvpx usage you should find ( --with-system-libvpx ) and of course a recent version should be installed

whether SM has been built for gtk2 or gtk3 you can detect which toolkit is used
( --enable-default-toolkit=cairo-gtk2 ) or ( --enable-default-toolkit=cairo-gtk3 )

in case of trouble you could also look here
type about:support in address line of SM and look for messages

[ozsouth]

@norgo - thanks for your help. about:buildconfig makes no mention of pulse or vpx. SM64 2.49.4 uses gtk3. All I noticed is that videos didn't work until I put libs into /usr/lib64/apulse in lxpup64, & I had no video issue with xenialpup64 & bionicpup64, which both have their pulse libs in /usr/lib/apulse. And to confuse things further, slacko64 doesn't have pulse libs & videos play. All with the same Seamonkey setup. Peebee had the same issue with the same videos, but not in Chromium. I don't understand - it's not logical, but I'll have to make do with the workaround for now.

[norgo]

@ozsouth
for clarification, we are talking about 64 bit version of SM, right ?

did a short test in Slacko64 700RC3 and SM 2.49.4 (64bit) from official Website
build configuration shows:

Build platform
target
x86_64-pc-linux-gnu

Configure options
MOZ_AUTOMATION=1 --with-external-source-dir=/builds/slave/rel-c-esr-lnx64-bld/build --enable-application=suite --enable-update-channel=release PKG_CONFIG=/builds/slave/rel-c-esr-lnx64-bld/build/gtk3/usr/local/bin/pkg-config --with-ccache=/usr/bin/ccache CC=/builds/slave/rel-c-esr-lnx64-bld/build/gcc/bin/gcc CXX=/builds/slave/rel-c-esr-lnx64-bld/build/gcc/bin/g++ --enable-rust RUSTC=/builds/slave/rel-c-esr-lnx64-bld/build/rustc/bin/rustc CARGO=/builds/slave/rel-c-esr-lnx64-bld/build/cargo/bin/cargo --enable-js-shell --enable-default-toolkit=cairo-gtk3 --with-google-api-keyfile=/builds/google-api.key MAKE=make --enable-alsa --enable-crashreporter --enable-elf-hack --enable-release --enable-stdcxx-compat

this means:
gtk3 is needed
installation of alsa is sufficient for audio playback
internal libvpx is used

real 64 bit OS doesn't search for libs in /usr/lib they expect libs in /usr/lib64

if you are install apulse and the libs are going to /usr/lib Slacko will not find them
Ubuntu basing distros have a symbolic link from /usr/lib64 to /usr/lib
that's why they are working nevertheless if the needed libs are located in /usr/lib

[peebee]

Interim delta to 18.06+12-uefi

iso md5 = 1f9d9df6fc0718fcd78cdb7176615c6d lxpupsc64-18.06+12-uefi.iso

[belham2]

Interim delta to 18.06+12-uefi

iso md5 = 1f9d9df6fc0718fcd78cdb7176615c6d lxpupsc64-18.06+12-uefi.iso

Hi Peebee,

Downloaded +12 from the Sourceforge link, and md5 sums are very different. Just wanted to give you a heads up about it. Here's a pic:

[peebee]

md5 sums are very different.

You are confusing the iso md5 with the delta md5.....

[belham2]

md5 sums are very different.

You are confusing the iso md5 with the delta md5.....

So pupmd5sum won't read the delta and only reads the first part of the delta line and not anything after the "__"???

First time I've ever seen this. I opened the delta file specifically, as you can tell in the pic. None of the other deltas, all downloaded to their ISO folder, has ever done this.

Why is it starting now??

[belham2]

No, the ISO md5 in that folder is this:

0de72b2429437268df404838456af51a


3 different md5 numbers, two in the folder I have downloaded, and one in the post I referenced.

[peebee]

The delta has to be applied to the very original iso with md5=
0de72b2429437268df404838456af51a

[peebee]

Interim delta to 18.06+13-uefi

After generation: the iso md5=a56c5d2a2a161e7480925ea387eeb278 lxpupsc64-18.06+13-uefi.iso

The delta has to be applied to the original 18.06 iso with md5=
0de72b2429437268df404838456af51a

[davids45]

G'day peebee,

Still using JWM as my preferred Window Manager .

Used your latest delta (+13) then from the new iso, manually frugalled to my 64-bit Puppies partition.

Copied the savefile from 18.06+12, renamed to '13' from '12', and booted with no problem.

Better-Late-Than-Never Dept.?
Since 18.06+6, I have had no luck with my networked scanner (Epson WP-2501 multifunction) with Xsane unable to find it. There was no problem with LxPupSc18.06-6, but in 8, 9, 10, 12 & now 13, Xsane fails. I couldn't get Iscan (Epkowa) to work at all in these Pups - Iscan is Ok in some other 64-bit Pups (and all 32-bit Pups).

Did something happen after 18.06+6 to affect scanning? Anyone else tried scanning with LxPupSc64 recently?

Anything I could try to locate the problem or to copy from 18.06+6 to rectify my problem?

Thanks,

David S.

[Marv]

+12 updated to +13 using the delta. Pristine boot, then savefile update, then the 4.19.8 64b kernel swapped in and Slimjet 20.0.4.0 updated to 21.0.7.0 (downloaded the deb from slimjet and rolled a run-as-spot SFS adding the libs needed for slackware). Low level checks, sound, SNS connection, printing, USB drive mount behavior etc. are all good and the whole shebang is running just fine on:

Code: Select all

System:    Host: puppypc395 Kernel: 4.19.8-lxpup64 x86_64 bits: 64 Desktop: LXDE (Openbox 3.6.1)
           Distro: LxPupSc64 18.06
Machine:   Device: laptop System: FUJITSU product: LIFEBOOK S761 serial: R2500459
           Mobo: FUJITSU model: FJNB225 serial: N/A
           UEFI [Legacy]: FUJITSU // Phoenix v: Version 1.17 date: 03/14/2012
Battery    CMB1: charge: 50.5 Wh 98.0% condition: 51.5/62.2 Wh (83%)
CPU:       Dual core Intel Core i5-2520M (-HT-MCP-) speed/max: 904/3200 MHz
Graphics:  Card: Intel 2nd Generation Core Processor Family Integrated Graphics Controller
           Display Server: X.Org 1.20.3 drivers: intel (unloaded: modesetting,vesa) FAILED: fbdev
           Resolution: 1366x768@60.00hz
           OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile version: 3.3 Mesa 18.2.5
Network:   Card: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express) driver: ath9k
Drives:    HDD Total Size: 120.0GB (41.3% used)
Weather:   Conditions: 28 F (-2 C) - Overcast Time: December 13, 9:06 AM CST
Info:      Processes: 175 Uptime: 19:41 Memory: 524.2/4788.4MB Client: Shell (bash) inxi: 2.3.40 

Posting from that combo now.

12/21/2018 Update: Updated to the 4.19.11 kernel. Current lxpupsc64 and LxPupSc on both the i5 above and the Bay trail box.

Code: Select all

System:    Host: puppypc395 Kernel: 4.19.11-lxpup64 x86_64 bits: 64 Desktop: LXDE (Openbox 3.6.1)
           Distro: LxPupSc64 18.06
Machine:   Device: desktop Mobo: ASRock model: Q1900M serial: M80-44015700338
           UEFI [Legacy]: American Megatrends v: P1.20 date: 03/25/2014
CPU:       Quad core Intel Celeron J1900 (-MCP-) speed/max: 1428/2415 MHz
Graphics:  Card: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & Display
           Display Server: X.Org 1.20.3 drivers: intel (unloaded: modesetting,vesa) FAILED: fbdev
           Resolution: 1366x768@59.79hz
           OpenGL: renderer: Mesa DRI Intel Bay Trail version: 4.2 Mesa 18.2.5
Network:   Card: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169
Drives:    HDD Total Size: 500.1GB (6.5% used)
Weather:   Conditions: 30 F (-1 C) - Overcast Time: December 21, 2:02 PM CST
Info:      Processes: 148 Uptime: 7 min Memory: 237.4/3401.9MB Client: Shell (bash) inxi: 2.3.40 

As above, booting and running well. Did all the file transfers (using an external USB3 SSD) and pruning in lxpup64 for the updates on the Bay Trail using pcmanfm with no glitches seen on that hardware nor on the i5 in daily use... Posting from the Bay Trail box now in Slimjet 21.0.7.0 64b run-as-spot from SFS

Thanks,

[westwest]

I'm still experiencing freezes in pcmanfm...
LxPupSc64 frugal, 18.06+12, stock kernel.
Problem is completely random, seems to disappears, then pops up again.

The window freezes, process must be ended,
then upon reopening settings have reverted,
also some glitches in the rest of the system (toolbar, etc).

Could it be a video driver issue?

Also, impossible to install VirtualBox with the installer, as in other pups.
Installer cannot create symlinks.
Perhaps it is an LXDE specific issue...