XenialPup64 With XFCE-4.12

[Dry Falls]

It looks like the component that's causing my many unnecessary icons is glib? When I compile it with --with-pcre=system I get about double (not duplicates, but more individual system mount points) the amount of icons as when I don't use the --with-pcre=system flag.

Does this mean it is something more to do with Pup-Volume-Monitor?

How do you normally compile GVFS? I'd love to hear more from you as you're seemingly the only person that has encountered this issue and solved it.

Hi battleshooter. Can't help you with the compiling gvfs. I use the system (base) packages from the slackware repo -- shouldn't there be ready-made ones for ubuntu? By analogy, I didn't have to change any puppy-specific files when I updated from glibc 1.23 to 1..26/gcc from 530 to 720. Had to add a few new dependencies like pcre2 and fontconfig2. The big one I forgot to mention before was udisk2 which I also had to reinstall.

df

[p310don]

I've made a lot of changes, overcome or worked around a number of challenges to get this Pup working (almost) how I want.

My progress report.

SFS-Get doesn't work OOTB - Installed RXVT from here to fix it:

http://distro.ibiblio.org/puppylinux/pe ... x86_64.pet

Downloaded and installed DEVX & Kernel Headers to compile Virtualbox -done

Chromium doesn't seem to work. As soon as I sign in to my google account, the computer no longer connects to the internet on reboot. Dunno why. Doesn't happen in Chrome. I got Chrome from here:

http://murga-linux.com/puppy/viewtopic. ... 4&t=107301

Printing took some getting going right. I installed the Samsung printer drivers from rcrsn51's Samsung printer thread. That didn't work. Then I downloaded the ULD driver from Samsung and ran the quick setup / install program. The printer only works when both are installed. Neither works on it's own.

http://murga-linux.com/puppy/viewtopic.php?t=66614

http://www.samsung-driver.com/download- ... 16130.html

Installed cairo-dock from the PPM.

Set up scheduled back ups from my windows system. Had to figure out about Samba vs Kernel 4.13. Sorted that:

http://murga-linux.com/puppy/viewtopic.php?t=112045

Got rid of desktop icons by deleting fstab as mentioned by Marv above. Seems to working, so far.

Got WINE working thanks to mikeslr. Works ok, but actually seems slower than native 32bit wine.

I haven't gotten the CUPS-PDF printer to work like I want.

I haven't gotten the media keys to work how I want.

I think that is the progresses I've made. So far I'm pretty happy with this release, but there are some niggles.

[rcrsn51]

I installed the Samsung printer drivers from rcrsn51's Samsung printer thread. That didn't work.

Because it's a 32bit driver.

[Marv]

r4 running well with peebees 4.14.0 kernel from here: http://www.murga-linux.com/puppy/viewto ... 272#974272 It eliminates some of the cpu frequency reporting problems in 4.13 and is a LTS kernel. Not much testing done yet but boot is clean, cpu reporting ok, video speed good, and generally seems 'snappy'. Still using the fstab kludge for drive icons. If mount.cifs is used, as with the 4.13 kernel, a SMB protocol version which is supported by your samba server must be explicitly stated ie. vers=2.1 as an option in YASSM for example.
Maybe 14 is a good number

Edit: Kernel number

[Dry Falls]

Downloaded iso 11/12. r4. booted right up. Clean first run experienced no problems with drive icons in thunar or xfce4 desktop. Very quick/snappy. Only problem was no rox-puppy pin in JWM so no backdrop or icons.

df

[Marv]

No extra icons like these? I've tried a lot of settings and can't get the drives without the extras unless I fiddle fstab. I doublechecked the r4 md5sum and the md5sum of the r4 I have matches the one listed in the first post. Any guidance in setup? I'm using the default XFCE4 desktop.

[Dry Falls]

Ok, back in Xenial and I do get the extra icons clicking 'other devices'. Should be able to untick that and leave drives checked, but no go. However, it does show vfat partitions which slackware xfce4 doesn't! Since pts, proc, sys & floppy don't show up in the left panel of thunar, I'd say it's a different problem than what I experienced in JL64. Easy enough to ignore but I think these shouldn't be mount points. The problem might be in thunar volume manager. Meanwhile, instead of removing fstab, you can comment out proc, sys (which are taken care of by init before X) and floppy if you haven't got one. commenting /dev/pts might present a problem rebooting a saved session. Will think on this some more.

df

[Pete22]

I'm stuck. I tried woofwoof but it did not work. Does anyone know what the password is?

[mikeslr]

Hi Pete22,

Are you trying to install something from /spot/Downloads? As far as I know, you can't.

What I think you can do is browse into /spot/Downloads, copy files from it into a folder not controlled by spot, and start them from that other folder.

But, I'm guessing. I've never used spot.

mikesLr

[battleshooter]

Just an update on the Wine situation, followed Mike's instructions, worked perfectly, thanks for that mate. I found though the /etc/ld.so.conf default file is exactly the same as the one in your pet so steps are amended to:

1. Install 32bit_compatibility_libs_xenial64.sfs

2. Run

Code: Select all

ldconfig

in a terminal

3. Install either Version2013 AKA greendome's wine64-2.0.3_v4.1.pet or Mike's Portable Wine

[battleshooter]

Hey p310don, thank you for the detailed feedback of what works and doesn't work, especially for mentioning what you discovered along the way. I see the issue with sfsget, it doesn't call the default terminal, it calls rxvt specifically in /usr/sbin/sfsget. Either I'll put rxvt back in for simplicity, or I'll change the code to work with any defaultterminal (hopefully).

I'm not sure about what Carolina used to use for its pdf printing, it may have used a different plugin all together, I might ask rg66 or Geoff via pm if they don't see this post. Or it might have been something Jemimah implemented from Saluki since we used the separate printer/scanner cups sfs.

What's the situation with the media keys p310don? Does using the xfce keyboard board settings not register them?

I'm not sure about the spot issue as I've never used it before either. I certainly didn't fiddle with any user passwords so it should be the same as any default woof pup?

That does help, it's still more hints, so thank you for mentioning it Dry Falls, the Udisks mention confirms my suspicion so I'll definitely look more into that. Thank you for your continual thoughts on the matter, the extra mind is much appreciated as this has confounded me for a long while now!

Hey Marv, thanks for testing the new kernel. I was planning to move to the 4.14 for the very reason it's LTS but wasn't sure if it would be too annoying to change kernels each release . Maybe just one

The when question is a bit tricky Belham but I think I've figured it out. The main thing that was holding me back from making the next release based on the new XenialPup64 was the fact I'd have to essentially recall all the fixes we've done here, reinstall and hopefully not forget any of them. I was really hoping to get a grip on git and all the rest of Puppy's automated scripting tools so I could just run a script over the top of Phil's releases and we'd have another build just like that. But the learning curve is giving me difficulty so I've settled for a compromise where I just get the petbuild scripts working perfectly and leave learning git to be understood in a more gradual pace.

Just throwing it out there but no promises, say a month from now will be what I'm aiming for. It's not bad timing so I can base it on Phil's final version too.

[battleshooter]

xfcexenial-R5.iso (761mb)
md5sum: abdc258a1ae797fc73b71df7e9509462

devx_xenialpup64_7.5.sfs
md5sum: 546a38c6005854e3ffe1edb605f63e63
kernel_sources-4.14.2-xenialpup64.sfs
md5sum: 0d8ac0163153d2bf82363cdc2bef3772

Well I haven't learnt git yet, so this was done the old fashion way with tons of copy pasting. In some ways, I'm really pleased with this release, at the same time, I'm disappointed I've gone over the 700mb mark.

I would definitely like to see if I can cut that back in the future, but for now, I'm happy with the progress. I suppose the compromise is for those that like it "light" now the adrv and ydrv can be removed leaving a more vanilla XenialPup64 with XFCE.

I like being able to plug in an android and having it identified immediately now that go-mtpfs is installed by default.

I went with Marv's fstab hack after fruitless attempts to pin down the cause of the multiple desktop icons. For such a dirty hack, it looks great

As some of you may have noticed, the latest Firefox version has killed sound again but made a slight edit to Bigpup's suggestion here and all was well again.

Carolina had FBReader and Evnice and I was requested by a user to reinclude them for reading ebooks and as qpdf can't select text.

A tiny update, but Libreoffice has been updated. The biggest change there is that it is now on the ydrv instead of the adrv in the previous release.

I'd say the most difficult thing about this release was keeping track of all the little changes I was making. Also accidentally destroying symlinks, that needlessly stumped me for about a week I can't wait till I have this all automated using Woof.



[url=hhttp://vanguardlinux.tk/ss/02xfcexenial-r5.png][/url]

R5 Change Log:
Rebased on Xenialpup64 CE 7.5
New kernel 4.14.2
Split "heavier" components to adrv
Libreoffice updated to LibreOffice_5.4.3 and moved to ydrv
Updated Firefox to 58
Skype version 8.11.0.4
Updated Smplayer 17.11.2
Added Qwinff
Added Evince
Removed qpdf
Added FBReader
Added Flash 27.0.0.187
Added go-mtpfs
Removed Dunst
Marv's fstab hack
New firmware

[Billtoo]

I installed to the hard drive of my Acer laptop:

# inxi -bw
System: Host: puppypc11044 Kernel: 4.14.2 x86_64 (64 bit) Desktop: Xfce 4.12.4
Distro: xenialpup64 7.5
Machine: Device: laptop System: Acer product: Aspire V5-571P v: V2.17 serial: NXM49AA03531512EC36600
Mobo: Acer model: Aspire V5-571P v: V2.17 serial: NBM491100831501E946600
UEFI [Legacy]: Phoenix v: V2.17 date: 02/27/2013
Battery BAT0: charge: 19.8 Wh 100.0% condition: 19.8/25.0 Wh (79%)
CPU: Dual core Intel Core i3-3227U (-HT-MCP-) speed/max: 900/1901 MHz
Graphics: Card: Intel 3rd Gen Core processor Graphics Controller
Display Server: X.org 1.18.4 driver: intel tty size: 104x20 Advanced Data: N/A for root
Network: Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
Card-2: Broadcom BCM43228 802.11a/b/g/n driver: bcma-pci-bridge
Drives: HDD Total Size: 500.1GB (3.5% used)
Weather: Conditions: 43 F (6 C) - light showers rain Time: November 30, 12:58 PM EST
Info: Processes: 150 Uptime: 19 min Memory: 333.9/5764.8MB Client: Shell (bash) inxi: 2.3.8
#

Added some applications with PPM.
Still getting used to it but no big problems so far.
Thanks.

[belham2]

xfcexenial-R5.iso (761mb)
md5sum: abdc258a1ae797fc73b71df7e9509462

Hi Battleshooter,

Am posting right now from my frugal Carolina 1.3 R2. Why?

Well, I downloaded R5, md5 checked out, installed it frugal along with my other pups, entered in the menu.lst, she booted right up, and looked pretty as heck with the subdued reddish brown wallpaper.

Went thru the motions of setting things up, all seemed fine, and the only thing I did was completely set up Firefox how I liked it, especially all the "about:config" settings, then opened and closed it a few times, it worked great. Then I went and immediately shutdown so a Savefile could be created.

Savefile was created, seemed no problems, but when things booted back up, it was like something had nuked the system.

1) Bottom XFCE tray was gone, nothing I could do to get it back

2) wallpaper completely gone, only a drab grey background

3) icons splayed all over the screen that were not there during the first initial boot up.

4) tried right-clicking on desktop to get into "Applications,", was hopeful for a minute, chose "Control Panel", so as to get at the XFCE Panel Control, and boom, it shut me down. It just froze solid....the DE and everything.

5) did different things, but there was no way to get around this freeze. Even tried Alt+SysRq+REISUB, nothing. Not one thing would respond anymore, desktop, mouse and/or keyboard.

6) so I was forced to "hard shutdown" the computer, and after the 3rd time I gave up.


Maybe I got a bad download, but the md5 checked out. I'll try again tomorrow, hope that was the problem. But given how beautifully everything worked "UNTIL" a SaveFile (in the frugal folder) was created, and all he!!---excuse my language---broke loose, I think something is screwed up in either init or something-related.

Interestingly, I posted today to Phil about the Savefile displaying that erratic behavior again that I posted and detailed to him about back in the summer. Hope these 2 things are not interrelated


P.S. Billtoo, did you post that pic again without first creating a Savefile? I don't see the Savefile button anywhere on the top portion of your screenshot. Seriously, check and tell us what you see. I tried 3 times, got the same "nuked" response

[Billtoo]

P.S. Billtoo, did you post that pic again without first creating a Savefile? I don't see the Savefile button anywhere on the top portion of your screenshot. Seriously, check and tell us what you see. I tried 3 times, got the same "nuked" response

Yes, I managed to get a savefile but there is a serious problem.

I got the same first screen as you did and I waited until the mouse moved and did cntrl-alt-backspace to get to the prompt then ran xorgwizard and specified my graphics etc, then entered startxfce4,

When I boot now I do the same but all the I installed is there.

[battleshooter]

Grrrr. You're not seeing things Belham, I can't believe I didn't test with a savefile. So sorry. I imagine that's why Marv didn't have any issues either as he doesn't run a save file either, at least from what I gather from his sig. That or I've implemented the hack wrong.

I'll pull the upload and reupload an isolated without the fstab hack

Edit: Looks like the problem is running deeper than expected. For some reason, the save file keeps restoring the original /root/.xinitrc file. For the life of me I can't figure out where on earth it's pulling it from

I really should have stuck to my one month release date schedule

[belham2]

Grrrr. You're not seeing things Belham, I can't believe I didn't test with a savefile. ....

I really should have stuck to my one month release date schedule

Haha, Battleshooter! All is good, seriously. Just glad to know I wasn't borking something up and/or possibly going insane staring at these old TFT/VGA screens too long. I need me a nice, big, shiny new whaleload-width-sized monitor like billtoo and bigpup have!

[Marv]

Grrrr. You're not seeing things Belham, I can't believe I didn't test with a savefile. So sorry. I imagine that's why Marv didn't have any issues either as he doesn't run a save file either, at least from what I gather from his sig. That or I've implemented the hack wrong.

I'll pull the upload and reupload an isolated without the fstab hack

Edit: Looks like the problem is running deeper than expected. For some reason, the save file keeps restoring the original /root/.xinitrc file. For the life of me I can't figure out where on earth it's pulling it from

I really should have stuck to my one month release date schedule

Just saw r5 now and did a first run. Something is odd with r5 indeed, at least wrt use of a save file. I got a nice clean pristine boot of r5, then created a fresh save file (I do always use savefiles) and got one reboot IIRC, then no panel etc. Ditto for updating an r4 savefile. You implement the hack a bit differently than I do , but both your rc.local, rc.shutdown and fstab.fake and .bak files and my rc.local, rc.shutdown, and just fstab.bak files (I use a mv instead of cp) work perfectly in r4. r5 borks with either of those sets or with a clean unaltered set of rc.shutdown and rc.local in the savefile. I'll unsquash, and revert the main SFS next. Could be the hack and something different in r5 interacting but dunno what. Seems unlikely. I was already running the 4.14.2 kernel in r4 and had lots and lots of reboots and saves there with no savefile problems, both with several trial versions of the hack and without it.

Edit: Unsquashed the main SFS, rc.local and rc.shutdown returned to stock. Resquashed and did a pristine Grub4Dos boot, setting timezone, UTC, and making SNS net connection. Created savefile, 256Mb EXT2 non-encrypted. Rebooted. Same exact behavior. Flash of icons, then no wallpaper or panel. Clicking and poking about blindly sometimes will get it up with wallpaper and panel (and the extra 'drive' icons to be expected) but either an X-restart or reboot gets the same failure again. Just now I also resquashed with my modded files from r4. Exact same result.

Also, if I pull that 'older' .xinitrc file from a savefile (not mounted, any one of MANY), all subsequent boots, X-restarts, reboots, logouts and xwins, etc., hack or no hack, freshly made or r4 update, are just fine. Almost seems like it is getting put in at save file creation or first boot thereafter but not on subsequent work once removed but how Like any boot related glitch, chasing is slow.

Edit: Looking in the main SFS. r4 has no .xinitrc file in /root/firstrun. r5 has an .xinitrc file there and it is not the same as that in /root. A clue?

[Marv]

Pulled the /root/firstrun/.xinitrc in the main SFS. No other changes, your implementation of 'the hack', resquashed. Pristine GrubforDos boot as usual, set up timezone, wifi connection with SNS. Rebooted, creating 256Mb EXT2 non-encrypted savefile as usual. Reboot was normal (no extra icons). Did multiple X-restarts, reboots, suspends. No flakey boots seen. Posting this as a new post, not another edit so with luck battleshooter will see it sooner. Quick look, seems to me like this is the source of the 'unwanted .xinitrc'.

[battleshooter]

Pulled the /root/firstrun/.xinitrc in the main SFS

Holy s*** Marv you are a beautiful genius!

I can't believe all the issues were caused by that one file!

Like any boot related glitch, chasing is slow.

Tell me about it! I spent all of yesterday rebuilding, the pup drv several times, with countless reboots and reextractions and was prepared to go through it all over again today....man you saved me, I was completely on the wrong track.

Thank you so much Marv