esos wrote: Thu Feb 29, 2024 6:03 pm

Thanks fredx181,

dmesg | grep wlan0

[ 32.456136] wlan0: authenticate with 9c:c9:eb:dd:58:03
[ 32.456167] wlan0: 80 MHz not supported, disabling VHT
[ 32.457892] wlan0: send auth to 9c:c9:eb:dd:58:03 (try 1/3)
[ 32.464637] wlan0: authenticated
[ 32.466671] wlan0: associate with 9c:c9:eb:dd:58:03 (try 1/3)
[ 32.474184] wlan0: RX AssocResp from 9c:c9:eb:dd:58:03 (capab=0x431 status=0 aid=32)
[ 32.474722] wlan0: associated
[ 32.483293] wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by 9c:c9:eb:dd:58:03
[ 32.546988] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

That doesn't look wrong to me, but could be that at that point of time there was no disconnect , perhaps try a few more times (just after a disconnect happens).
(I had same problem (but could be because of my ancient router) and got every few minutes something like " de-associated" line in dmesg output)

For sure not the router, I have over 10 distros installed without wifi problem.

Just for diagnostic purposes, I installed peasywifi 4.9 (I don't have the official pet, cobbled one together from the current Devuan-daedalus live squashsfs) and then used the internet connection manager (Menu>Setup>internet connection manager) to switch to it. Comes up correctly with a viable resolve.conf on boot, survives suspends, a couple of reboots, and reloads of the window manager, and is almost as quick as connman, way faster than SNS to connect and reconnect. Sems solid. Up to now, version 4.6 has worked on all my pups & been rock solid but it wouldn't display scanned networks etc correctly in BW64 though I could make it connect.. Seemed like a gtk2/gtk3 thing. Ran the setup first with a bitty savefile and then moved it to my current ydrv. Both working well. Same hardware as in my post above, no added delays or fussing needed. Posting in portable Brave on that combo now.

Marv wrote:

.... version 4.6 has worked on all my pups & been rock solid but it wouldn't display scanned networks etc correctly in BW64 though I could make it connect.. Seemed like a gtk2/gtk3 thing.

Yes, BW64 has gtkdialog built with gtk3. The newest peasywifi from rcrsn51 is v4.9 and has gtk3 support, to install: (I tested on BW64 and works well, but installing should be done with petget, not gdebi, as gdebi doesn't know that gtkdialog is already installed on BW64 so gives error) :
wget https://github.com/doglinux/bookworm/raw/master/amd64/peasywifi_4.9_amd64.deb
petget peasywifi_4.9_amd64.deb

No internet connection although everything seems to be fine.

Unlike BookwormPup64 10.0.4, /run/connman/resolv.conf in BookwormPup64 10.0.5 is empty after startup.

Only after restarting connman /etc/init.d/connman restart will the DNS servers be recognized and entered.

Hi @Marv Is your PET available? Would it have Fred's suggestion?

Thanks.

Thanks Fredx,
I found the wifi problem, the connection is working only by choosing from the menu, can not choose from wifi-icon at the right bottom corner.

Now I have another problem, I can not import vivaldi bookmark from anywhere(HDD/Usb).

Clarity wrote: Fri Mar 01, 2024 11:01 am

Hi @Marv Is your PET available? Would it have Fred's suggestion?

Thanks.

Just use the one from @fredx181s' repository two posts up installed as he suggested. Mine is -as I said- cobbled though It (4.9) is still working very well here after a long suspend on this sometimes problematic laptop.

Just compared my cobble with the real thing. I had one redundant item, but close enough to fly. I'm glad to have the real thing in my arsenal now.

Does installing Chrome the default way with the .deb file from Google (which adds the google repo to the apt sources.list file and installs from there) still mess up the permissions in Puppy or is that an old issue?

RE: Failed /run/connman/resolv.conf in new internet connection scripts of BW64 10.0.5 when using ConnMan Connection Manager.

BW64 10.0.5 ISO is now removed from first post until above bug is fixed.

@rerwin, as time permits, please check your PM.

@radky would you consider the next version to be v10.0.6 so as to not get the replacement confused with the retired?

Thanks for any consideration

Scrcpy (share android phone screen with your pc screen, keyboard and mouse) didn't make it into Debian Bookworm. The Sid version is ancient.

I wrote a quick explanation of how to install it in Bookworm 64 Puppy, which requires compiling it, but it's easy.

viewtopic.php?t=10838

@Marv and others affected by the absent resolv.conf file,
Attached is a repaired network_default_connect script that avoids removing it for connman. Please unzip and place it into the /usr/sbin directory

Please verify that it works for you, so @radky can add it to BookwormPup. Thank you.

Also, someone having the startup issue requiring the restart of /etc/initd/connman, see if this also makes the restart unnecessary.

Sorry for not being able to catch the problem in testing, as my (2006-BIOS) PCs tolerate the missing resolv.conf. Apparently timing related.

Richard

@rerwin, That does the trick here on my Fujitsu S761 laptop circa 2012. resolve.conf is now populated correctly on boot and the connection survives lidsuspend and restarting the WM. I had put a script calling /etc/init.d/connman restart in my Startup directory as a workaround. That is no longer necessary. Only an hours testing or so but several reboots therein and no problems seen. connman is blazingly fast to connect as always.

Thanks,

@rerwin I can also confirm that after this change the DNS server is recognized right at startup.
No workaround necessary anymore. On a desktop computer with an i5-9400 CPU.

.

Jasper wrote: Wed Feb 28, 2024 1:38 pm

I am using a laptop with a display of 1368x768.

As a general observation, could the menu items fold onto themselves? ........ lol I will try to explain better.

At my end the Utility menu is more populated with applications than other headings. As a consequence it nearly fills the screen top to bottom.

This would not be an issue on a HD display.

I know I can hide items using the Desktop Manager.

Also, the Bluetooth Adapter appears to be in the wrong category.

@Jasper

In JWM (default window manager of BW64) the XDG Desktop Menus are scrollable. If the menu items are too numerous to display completely on screen, you can scroll the menu up or down to view all available items. Scroll by using the mouse wheel (or trackpad) -- or you can place the pointer (cursor) over the menu at the top or bottom screen edge to initiate up or down scrolling.

Also, in the next release of BW64, the Bluetooth Manager menu item will be assigned to the System category.

Note: The default Woof-CE Menu Manager application is available in the Setup menu category. However, in BW64 there is also an alternate Menu Manager that uses different algorithms to identify and assign menu items to specific categories, and the GUI provides separate columnar views of visible and hidden menu items. If interested, go to Menu -> Setup -> Puppy Setup -> select the Legacy menu manager checkbox (bottom left), then click the Menu Manager button.

@rerwin

The new networking scripts in BW64 have additional unresolved issues.

Please check your PM.

Thanks

dancytron wrote: Sat Mar 02, 2024 10:21 pm

Scrcpy (share android phone screen with your pc screen, keyboard and mouse) didn't make it into Debian Bookworm. The Sid version is ancient.

I wrote a quick explanation of how to install it in Bookworm 64 Puppy, which requires compiling it, but it's easy.

viewtopic.php?t=10838

Version 2.4 of scrcpy was released a couple of days ago. I have compiled it from source in BookwormPup64 and have made a .pet package. It contains the latest adb which is a pre-compiled binary downloaded from the official web page. This is a bit larger than using the Debian adb via apt but it is the latest version and does not seem to need shared libraries as dependencies (maybe statically linked in?).

Until recently I have hardly used android phones at all and even now the one I have is rather old with android-5.0.2 and because of this I compiled scrcpy with a meson setup option "old" for android versions earlier than 9. Not sure if this package will work for android versions later than 9. Audio is always automatically disabled on older android versions too.

Also be aware that there are a few steps that you will have to take (such as enabling the feature on your android device), plus some steps you might have to take (such as starting the program twice, unplugging and re-plugging the USB cable, and ticking a pop-up on your android device to authorise the connection). There is a menu entry in Utility but it is not just click and go every time so starting scrcpy from terminal at first at least might be helpful. Anyway, I am no expert in these things so I don't know if it is all working as it should, but it does display my screen and allow control of the phone from Puppy.

Uploading just for testing and/or any comments/suggestions
http://smokey01.com/OscarTalks/scrcpy-2 ... 4-bkwm.pet

BookwormPup64 10.0.6

• New Woof-CE build of BW64
• See first post for downloads and second post for changelog

I made a more compressed version of BookwormPup64 10.0.6, to fit on a CD (is 679mb). Also made a delta (4mb).
Used medium-high level compression: -b 1M -comp xz -Xdict-size 25% ; iso created via pCompress.
In brief test, ran fine on my 4yo Dell i5 laptop. Use at own risk.

Has updatesfsm (which I used for compression) added to /usr/local/bin.
(updatesfsm can edit sfs - place an sfs in an empty folder, in a terminal cd into that,
run updatesfsm, make small changes in utmp subfolder & click ok. Makes mynew.sfs)

10.0.7m released. See later post

@radky At first glance everything seems to be going well and smoothly.

I have installed a pack of .petfiles.
Samba, Syncthing, radicale-server, qemu, Libreoffice, network printer, network scanner and a lot more.
BW64 should be my new everyday OS.

Everything works as expected.

Great puppy, thank you

@radky Pulled all patches from my ydrv. rebooted into 10.0.6. So far so good. connman connection survives reboots and lidsuspends. Just normal daily operation so far, I haven't used the connection manager to switch from connman to SNS or one of the others yet. I'll do that later.

Thanks,

Update: Installed peasywifi 4.9 from a deb. Used menu>setup>Internet connection manager to switch to peasywifi. Ran peasywifi from menu>network and set up my connection. Rebooted using a small savefile to preserve this change. Sucess, came up running peasywifi, connected ok, populated resolve.conf, and put the peasywifi icon in the tray. Posting from that setup now. The connman icon remains in the tray, showing that it is disconnected but that's a very minor niggle.

Only issue is "tldr". Screens show VM operation booting success and err.

ELSE, things are well

QEMU (v8+ from @Jasper) stanza for the VM

qemu-system-x86_64 -name "BKWP64 v10 by Radky" -enable-kvm -smp 2 -m 2048 -vga std -device AC97 -net nic -rtc base=localtime -hda /dev/sdf

• Boots ISO file directly in VM as well as booting when launched from SG2D.

• Bare-metal boots with ease when ISO file is launched from either Ventoy or SG2D (see caveats at bottom of this post).

.
.
The Table of BookWormPup64 boot results are posted here.
.
Caveats

• For Ventoy boot, the boot stanza MUST have a PSAVE= parm to direct persistence

• For SG2D boots, no such is needed as the SAVESPEC file, if exist, automatically directs persistence

I noticed this bug in my s15ovrly pup - is here too. If an SFS file has a space in the filename, queueing fails, as EXTRASFSLIST uses space as a delimiter (see pic below - filename in it - flshgms s15o.sfs). Simple fix - NO SPACES IN SFS FILENAMES. Best fix - put each EXTRASFSLIST entry in double-quotes. My fix, stop user from trying to load such files (note - my fix affects iso files too). Needs code after line 76 in /usr/sbin/filemnt (my code in red):

------------------------------------------------------
imgFile="$1"
if ( echo "$1" | grep " " ); then
Xdialog --title "" --no-cancel --msgbox "NO SPACES ALLOWED IN FILENAMES - RENAME AND TRY AGAIN" 0 0
exit 1
fi
[ ! -f "$imgFile" ] && echo "No regular file: $imgFile" && exit 1
imgFileBASE=${imgFile##*/} ## imgFileBASE="`basename "$imgFile"`" #BK
[ "$(dirname "$imgFile")" = "." ] && imgFile=$(pwd)/${imgFileBASE}
-------------------------------------------------------

Clarity wrote: Wed Mar 06, 2024 3:29 am

Only issue is "tldr". ...

@Clarity

Concerning the issue with tldr, the screenshot is very small and the error you describe is difficult to read.

Please keep in mind the following features of the tldr utility as implemented in BW64:

1 - The TLDR (too long; didn't read) utility provides concise descriptions of Linux commands that are typically shorter than the comprehensive descriptions provided by conventional Linux 'man' pages.

2 - In BW64 >= 10.0.6, TLDR is accessible as a browser search utility via Menu -> Document -> TlDR Pages. Typically, the search is quick and convenient.

3 - Alternatively, you can run tldr as a bash script from the terminal command line (such as tldr ls). On first run, tldr requires an active internet connection to download a 20M resource database which provides local access to concise descriptions of Linux commands. Depending on your connection, the download may take a few moments and the tldr screen will remain blank until the download is complete. The tldr pages are cached locally in /root/.local/share/tldr.

4 - In BW64, the tldr pages are also functionally integrated with man page searches. Specifically, if a man page for a Linux command is not locally available, the 'man' search request is automatically transferred to tldr. For example, if you enter man ls in a terminal and there is no local man page for the 'ls' command, the search will be passed automatically to the tldr utility -- in which case, tldr will provide a concise description of the Linux 'ls' command. Used this way, the 'man' command will typically provide useful results -- even when the actual 'man' page is not available.

OscarTalks wrote: Tue Mar 05, 2024 12:23 am

dancytron wrote: Sat Mar 02, 2024 10:21 pm

Scrcpy (share android phone screen with your pc screen, keyboard and mouse) didn't make it into Debian Bookworm. The Sid version is ancient.

I wrote a quick explanation of how to install it in Bookworm 64 Puppy, which requires compiling it, but it's easy.

viewtopic.php?t=10838

Version 2.4 of scrcpy was released a couple of days ago. I have compiled it from source in BookwormPup64 and have made a .pet package. It contains the latest adb which is a pre-compiled binary downloaded from the official web page. This is a bit larger than using the Debian adb via apt but it is the latest version and does not seem to need shared libraries as dependencies (maybe statically linked in?).

/snip

Uploading just for testing and/or any comments/suggestions
http://smokey01.com/OscarTalks/scrcpy-2 ... 4-bkwm.pet

Installed on brand new 10.0.6 frugal install and it worked paired with my phone with Android 10.

Would you share what you ran to get it into a .pet file? I'd like to know how to do that.

dancytron wrote: Wed Mar 06, 2024 9:43 pm

Installed on brand new 10.0.6 frugal install and it worked paired with my phone with Android 10.
Would you share what you ran to get it into a .pet file? I'd like to know how to do that.

Thanks for the report, glad it works on later androids.
If you are compiling it yourself it would be "new" by default. I changed it by editing the meson_options text file in the source, so if that is left unaltered that setting would be theoretically what is optimum for later phones, but maybe not a critical thing.

Anyway the answer to making a .pet once everything is compiling and installing is to run new2dir ninja -C builddir install (equivalent of using "new2dir make install" if using autotools and gnu make) and then of course dir2pet on the package directory tree that is created.

I did have to tinker around with things a bit. Not all those dependencies in that list need to be installed as some are in the devx. When I tried to apt install libsdl2-dev it complained about some dependency version mismatch so I compiled latest libsdl2 from source. I did have to apt install libavdevice-dev with dependencies. The libusb-1.0-0-dev package goes in via apt but the shared library is already present.

In the install script I had to edit the download path to the prebuilt server from version 2.3.1 to version 2.4 as it was grabbing the wrong version which refused to run. I also had to edit the sha sum because the script does a check of that. I think the git master checkout has this corrected now, but in the release tarball it has not been updated.

I did initially use apt to install the Debian adb which did work and helped me to see where it went in the file system. It has a symlink into PATH. Sticking with this would have been an option but I decided to try substitution of the latest official version and removal of the then unneeded shared libs.

hello all,
i was playing around with some scripts and i realize a small bug on GTK some attributes looks like do take any affect at all ex: width-request height-request

here is an example how is final layout test it in lunapup, fossapup and CE, Bionic the only puppy that display extra height is bookworm and if you replace default-width to width-request gets more wierd it looks likes <text warp="true" width-char="35"> dont do nuthig as well

#!/bin/sh

GTKDIALOG="`which gtkdialog4 gtkdialog3 gtkdialog | head -1`"
export GTKDIALOG ; [ -z "$GTKDIALOG" ] && echo "$(gettext "GTKDIALOG is missing, please install it first.")" && exit

# grab Puppy name and version
[ -f "/etc/DISTRO_SPECS" ] && . /etc/DISTRO_SPECS ; P="$DISTRO_NAME - $DISTRO_VERSION " || P=
export JWM_VER=$(jwm -v | head -n1 | cut -d " " -f2- | cut -d " " -f1 | sed -e 's/[snvgit-]//g')

export JWM_LOGO=$(ls /usr/share/pixmaps/puppy/desktop.svg 2>/dev/null | head -n 1)
export COLOR="#FF0000"
export P_BTN_PATH="/usr/share/jwm/themes_window_buttons"

pixmap () { echo '<pixmap><variable>IMAGE</variable><height>'$2'</height><input file>'$1'</input></pixmap>' ; }
export -f pixmap

# width-request="450"  or default-width="450"
# height-request="300" or default-height="300"
export MAIN_GUI='
<window title="Window buttons theme" icon-name="gtk-convert" default-width="450">
	<vbox border-width="10">

	<hbox>
		<vbox homogeneous="true" space-expand="true" space-fill="true">'`pixmap "$JWM_LOGO" 64`'</vbox>
		<vbox>
			<text use-markup="true"><label>"<b><span size='"'large'"'>JWM THEME </span><span size='"'large'"' color='"'$COLOR'"'>SWITCHER</span></b>"</label></text>
			<text><label>"'$(gettext "For :")' '$P'"</label></text>
			<text><label>"'$(gettext 'Desktop Environment')': JWM v'$JWM_VER'"</label></text>
			<text warp="true" width-chars="45"><label>"'$(gettext 'The window buttons can be themed to your liking. If you want to build your own buttons, see')' '${P_BTN_PATH}'"</label></text>
		</vbox>
	</hbox>


	<hbox homogeneous="false" space-expand="false" space-fill="false">
		<button space-expand="false" space-fill="false" tooltip-text="Reinstates the stock standard icons">
			<label>"'$(gettext "Clear")'"</label>
			<input file icon="clear"></input>
			<action>clear_func</action>
		</button>
		<text space-expand="true" space-fill="true"><label>""</label></text>
		<button space-expand="false" space-fill="false">
			<label>"'$(gettext "Quit")'"</label>
			<input file icon="quit"></input>
			<action>exit:quit</action>
		</button>
	</hbox>

</vbox>
</window>'
$GTKDIALOG -pc MAIN_GUI

Best regards