Fossapup64-9.6-CE built with Defaults by woof-CE (closed topic)

[mikeslr]

After having used and complained about it for a long time, I finally realized why peebee provides light-browser in an adrv.sfs. It is the only application --in fact the only thing-- included in the adrv.sfs. Once you use it to obtain a 'full-fledged' web-browser, you can simple delete the adrv.sfs. No mess, no bother. It's gone, it's desktop file and Menu entry and all links to it are gone. 'Though I still think it should be provided as a ydrv.sfs, just in case you want to keep it as the default for displaying html files.

[thinkpadfreak]

Hello.

I have installed fossapup64 9.6 and am testing if it works in the Japanese environment.
I noticed that we cannot use an IME (Japanese input system) with Chrome running on fossapup64 9.6.

As far as I know, there are only two puppies on which we can use an IME with Chrome. One is fossapup64 9.5 and the other is jammypup64 9.7b/9.8.

I have long been wondering what makes a difference.

[bigpup]

Frugal install, save folder

When I run the Network Wizard and get to the setup window.

It is very large and goes off the monitor screen.

Screenshot(3).jpg (51.45 KiB) Viewed 1770 times

[rockedge]

@bigpup that is the program was designed for gtkdialog-gtk2 and this Fossapup64 has gtk3.

What works is I copied a gtkdialog from fossapup64-9.5 (Bionic64 works also) renamed it to gtkdialog2 and put it in /usr/local/bin
Then I modified the lines in those programs that need it from gtkdialog to gtkdialog2 because the Simple SAMBA GUI is also out of sorts and the modification to use gtkdialog2 works to fix it

[Grey]

the program was designed for gtkdialog-gtk2 and this Fossapup64 has gtk3.

Wouldn't it help if you change the string PETBUILD_GTK=3 before building in _00build.conf ?
Replace 3 with 2. Or maybe it's more complicated there.

[rockedge]

@Grey Yes that is a good solution to try out. It might work. By adding the gtkdialog2 in this test model I can experiment with gtk2 and gtk3 on the same system. In QEMU I have KLV-Airedale-beta25 going and can play around with building gtkdialog in gtk4.

[Clarity]

Just a couple-few years ago, the WoofCE team embarked on the journey to update PUP programs to run within the GTK3 framework.The WoofCE development group has been active in insuring ALL subsystems and apps are modified to GTK3.

Questions

• Would we be helping them by identifying/correcting ANY occurrences where PUP apps are not working in GTK3 subsystem?

• Should this be helpful to them?

[rockedge]

Would we be helping them by identifying/correcting ANY occurrences where PUP apps are not working in GTK3 subsystem?

Yes that is a good idea.

[geo_c]

I was thinking about the browser thing. Is it possible to put @mikewalsh portables in a repository and include an install script that downloads, or an easier approach might be include one of them in it's own directory in the install folder, so that it can be used and simply deleted if not later wanted? Like Brave, or Firefox, or Chromium? Is it possible to include one of those in a folder iinside the iso that is unpacked to /home, and then include a symlink to the launch script accessed somewhere in the applications menu? The launch script could open a page in the browser on first run that explains it's a portable and can be deleted from home at any time.

[thinkpadfreak]

As far as I know, there are only two puppies on which we can use an IME with Chrome. One is fossapup64 9.5 and the other is jammypup64 9.7b/9.8.

I have long been wondering what makes a difference.

As an average user, I can't think of any workaround. This issue affects not only Japanese people but also other people who use IME to input their languages.

Judging from information found on the Internet, this kind of issue doesn't seem to happen in other distributions than puppy. I hope developers may know something about the difference.

[geo_c]

The intermittent non-responsive JWM desktop you describe is one I have observed many times with JWM 2.4.0 as implemented in the original FossaPup64 9.5

However, thanks to bug reports by dimkr and 01micko at jwm github, this issue was addressed and hopefully fixed in JWM >= 2.4.2.

PupMates
https://www.smokey01.com/radky/PupMates.html

I have been running very developed (lots of applictions and theming) versions of fossapup6.9.5 and jackalpup going on three years, so I always wondered about that bug. It's infrequent enough not to be a major concern, just a periodic annoyance.

Is JWM 2.4.2 available to try? I can make a new pupsave and give it a whirl.

[dimkr]

I pushed some changes (https://github.com/puppylinux-woof-CE/w ... 3571/files) to woof-CE:
1. GTK+ 3 everywhere -> GTK+ 2 where possible
2. Some audio-related packages that don't work with PulseAudio are dropped to save space
3. Better selection of fonts (fonts-liberation -> fonts-liberation2, fonts-emojione -> fonts-noto-color-emoji)
4. Fixed some package conflicts (libjack, CUPS filters)
5. Added notification-daemon-stub to make pairing work in Blueman
6. SNS, Frisbee, etc' are replaced with ConnMan, connman-gtk and connman-ui
7. acpid-busibox is replaced with woof-CE acpid_busybox

In addition, I hope to get https://github.com/puppylinux-woof-CE/woof-CE/pull/3573 merged soon, so pTheme can be removed from 9.6.

[Jasper]

Hi there

I am little confused as I read that there have been a number of changes, yet the 1st post retains the original ISO.

Will the changes made so far be incorporated and a fresh ISO available?

Or should I just download the ISO from the 1st post?

[dimkr]

A focal64 build with a fresh copy of woof-CE will include the changes, otherwise it won't.

[Jasper]

I downloaded the ISO and additional files today and installed it onto a USB flash drive. Worked effortlessly and saw the desktop.

I was not able to connect to the Internet as I use my onboard WiFi device which was not available in any of the Network setup applications.

Code: Select all

root# lspci -vv -s 02:00.0

02:00.0 Network controller: Intel Corporation Wireless 3165 (rev 81)
	Subsystem: Intel Corporation Dual Band Wireless AC 3165
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 128
	Region 0: Memory at df000000 (64-bit, non-prefetchable) [size=8K]
	Capabilities: [c8] Power Management version 3
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
		Address: 00000000fee002f8  Data: 0000
	Capabilities: [40] Express (v2) Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 unlimited
			ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 0.000W
		DevCtl:	CorrErr+ NonFatalErr+ FatalErr+ UnsupReq+
			RlxdOrd+ ExtTag- PhantFunc- AuxPwr+ NoSnoop+ FLReset-
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend-
		LnkCap:	Port #0, Speed 2.5GT/s, Width x1, ASPM L1, Exit Latency L1 <32us
			ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+
		LnkCtl:	ASPM Disabled; RCB 64 bytes Disabled- CommClk+
			ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s (ok), Width x1 (ok)
			TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Range B, TimeoutDis+, NROPrPrP-, LTR+
			 10BitTagComp-, 10BitTagReq-, OBFF Via WAKE#, ExtFmt-, EETLPPrefix-
			 
			 

I guess I could use the previous firmware to ensure I had a working connection.

[wizard]

@dimkr

I may have missed this, but have you and @rockedge teamed up on this 9.6 and it is the one to be submitted to Distrowatch ?

Thanks
wizard

[dimkr]

I'm trying to help here and there, especially when user requests for 9.6 align with my plans for dpup.

[Sofiya]

I'm trying to help here and there, especially when user requests for 9.6 align with my plans for dpup.

@dimkr
where did your fossapup64ce-9.6-alpha2 go?

[dimkr]

where did your fossapup64ce-9.6-alpha2 go?

It's deleted, to prevent confusion.

[rockedge]

I am using the latest woof-CE package to build Fossapup64-9.6-CE models then modifying that output and using @amethyst's nicOS-Utility-Suite-2022 to remaster and create F96_1-CE as well as techniques from building KLV-Airedale ISO's

This is model is F96_1-CE, which was built at midnight from woof-CE using the kernel huge-6.0.5-lxpup64.tar.bz2.
Modified under moon shadows to include JWMDesk-3.6 and nicOS-Utility-Suite-2022.
F96_1-CE uses pulseaudio and includes the latest developments in woof-CE for the production of Fossapup64-CE's and some adjustments to the desktop arrangements.

Ready for testing the ISO resides here -> https://rockedge.org/kernels/data/ISO/F ... 6_1-CE.iso
or https://rockedge.org/kernels/

Keep in mind the desktop "look" features and arrangements are not set in stone nor is any of the system. This release is for testing and evaluation.

For all those Lunatics, Werewolf aware and those with a general interest in Fossapup64-9.6-CE development.

New topic for F96-CE -> viewtopic.php?t=7325

[Jasper]

Thanks for building the ISO and for sharing a link.

Looking forward to it

[rockedge]

The most recent version of Fossapup64-9.6-CE is being tested as F96_2-CE and has a topic thread here -> viewtopic.php?t=7342

[pp4mnklinux]

https://forum.puppylinux.com/viewtopic.php?t=7888

I finally go to fossa

[rockedge]

@pp4mnklinux I can recommend using F96_4-radky5-CE which is built with Fossapup64-9.6-CE as the base.

More about it and the download link -> https://forum.puppylinux.com/viewtopic.php?t=7678

[pp4mnklinux]

@pp4mnklinux I can recommend using F96_4-radky5-CE which is built with Fossapup64-9.6-CE as the base.

More about it and the download link -> https://forum.puppylinux.com/viewtopic.php?t=7678

ok, thanks, I'll give it a try, but can you advance me the main characteristics, plz.

Thanks a lot for your help.- @rockedge

Have a nice day.

[bean]

This is freshly built with woof-CE using the defaults for the configuration. So far I've compiled several packages using a setup of this and all the runs were successful. Missing is some polished eye candy and several standard Puppy Linux tools and utilities.

Fossapup64-9.6-CE 378 MiB download size

what happened to the above 378Mib version above?
i downloaded the slightly larger Fossapup64-9.6-CE it is 538mb which runs great, see my post for my blurb. do i have your latest version? as some of the links did not work so downloaded what i thought to be the latest, forgive me i am just a bumbling oldy, trying to keep up in this racetrack life is becoming haha Ken

[bigpup]

All things to do with F96-CE have moved to it's own section of the forum.
https://forum.puppylinux.com/viewforum.php?f=197

F96-CE is basically Fossapup64 9.6 with a lot of improvements to Fossapup64.

This topic closed.