williwaw wrote: ↑Fri Feb 16, 2024 8:42 pm

if apt is to be configured the puppy way instead of the gnome way, then puppy apt configs should be incorporated into woof-ce so that apt behavior remains consistent across all pups

This already exists,

https://github.com/puppylinux-woof-CE/w ... rv.sh#L127

wizard wrote: ↑Thu Feb 15, 2024 2:15 am

@Marv
@mikewalsh

Not the problem here. Even with those things in place, when you click the "Choose file" button it does not open a file management window (nothing happens).

Thanks
wizard

I'm going to be bold and bump this, knuckleslaps accepted. It seems that gtdialog-file_chooser will not open from any of the chromium portables in bookworm64 10.04. I also see a failure when saving to PDF from those browsers in that bookworm. The file_chooser opens correctly for me from all those browsers in jammypup64, any of the fossapup64s and derivatives, voidpup64, and LxPup64. I don't have any other browsers on board to test, someone with FF could try and import bookmarks and see. It will open when called from terminal in BW64. I've tried what I could with versions, changed themes etc. and can't get it to go.

If you've solved it wizard, give this hound a clue. Otherwise, I'll continue to workaround.

ThANKS,

@Marv

Same as you, found that the Chrome (ium) portables bookmark import function works on Fossapup64 and F96CE. My work-around was to use Fossa to do the import and then when I open in BW64 the bookmarks are there.

My Firefox portables work fine in BW64.

Thanks
wizard

In response to posts noting problems under various Package Managers, see Obtaining Alien & Difficult Applications, https://www.forum.puppylinux.com/viewto ... 44#p112044

In BookwormPup64 the package resolvconf will break DNS in simple network setup and frisbee. It will also damage the default connection manager's handling of the DNS

The only workaround I found that somewhat fixes SNS, Frisbee and Connection Manager it to replace the symlink /etc/resolv.conf with a file named resolv.conf and then add your own nameserver lines in that new file and make that file immutable.

something like this to set cloudlare DNS
nameserver 1.1.1.1
nameserver one.one.one.one

After adding what you want to the new resolv.conf file then set the immutable bit (prevents deletion) by opening a terminal window in /etc/ and run

chattr +i resolv.conf

After setting the immutable bit the file will not be able to be deleted until you unset the immutable bit using

chattr -i resolv.conf

The wireguard VPN program I use depends on resolvconf and the VPN was being assigned my wireless carrier's DNS through connection manager, it was supposed to be using cloudflare DNS. I changed the resolv.conf file entries to use the cloudflare DNS and then set the immutable bit, now everything (including SNS and Frisbee) is using the cloudflare DNS no matter which wireless or VPN used.

The basic problem with implementation of a uninstaller in Debian based on apt is that apt is fundamentally incapable of making sophisticated file distinctions because of its original conceptual basis.

Apt marks files in two ways, either "manually" installed or "automatically" installed. Apt autoremove removes "automatically" installed "orphan" files and ignores "manually" installed files, unless otherwise directed. It does a lookup on what Debian says is supposed to be a dependency for installed packages to try to guess which "automatic packages" are orphans, but it has no actual systemic knowledge. It is a method based on estimation.

This is a binary choice system which made sense back when 16K was a lot of memory. The problem is that it doesn't allow for complex interactions between file dependencies. Unfortunately it is the standard in Debian on which file managers have been constructed since then. Unless they implement their own type of file database, they simply use this binary means of making choices.

A better way of dealing with file manipulations would be to adopt a system of file ownership. When a new program package and dependencies are installed, the dependencies are tagged with the name of the calling package, as owner. If another program is installed and it also uses a couple of the same dependencies, it adds its owner nametag to to those dependencies as a co-owner.

When the first program is deleted, all of the dependencies that have ONLY its nametag are also deleted. The two jointly owned dependencies are not removed, only the ownership tag of the first program is deleted.

@vtpup

Your idea is really good.

You need to get involved in this topic:
viewtopic.php?t=10704

Just a little something

Simple-scan freezes - apparently

When you select settings, a window opens that appears to have no close button.
If you then click on the main window, the settings window closes, but simple-scan freezes and can only be ended with kill.

The other settings windows have a close button and work as expected.

fr-ke wrote: ↑Sun Feb 18, 2024 7:08 pm

When you select settings, a window opens that appears to have no close button.
If you then click on the main window, the settings window closes, but simple-scan freezes and can only be ended with kill.
The other settings windows have a close button and work as expected.

I believe this is a "known bug". Solution is to change your GTK theme.
See "Note-2" in the second post of this thread:-

"Note-2: When rendered by Puppy-specific GTK3 themes (such as Flat-grey-rounded) the Preferences dialog of the Simple-Scan Document Scanner may not correctly render widgets of the titlebar, in which case the vertical dimension of the titlebar appears markedly truncated and there is no button to close the Preferences dialog. In this scenario, you can close the dialog by pressing the keyboard ESC key. However, non-Puppy GTK3 themes such as Numix and Graphite will render the titlebar correctly and a button is available to close the Preferences dialog."

@OscarTalks Thanks, and sorry for the sloppy reading.

Trying to install BW64 for a friend, but no wifi device is recognized.
Laptop = HP 15-fd0081wm

The output of lspci shows: Realtek Device b85b

Any recommendations for firmware/kernels for that device?

Thanks
wizard

wizard wrote: ↑Sat Feb 24, 2024 10:27 pm

Trying to install BW64 for a friend, but no wifi device is recognized.
Laptop = HP 15-fd0081wm

The output of lspci shows: Realtek Device b85b

Any recommendations for firmware/kernels for that device?

Thanks
wizard

Maybe this :https://packages.debian.org/ca/bookworm ... re-realtek

@wizard - googling, I found this:

Searching for "0bda:b85b Realtek Semiconductor" seems to match a Realtek RTL8852BE chipset. According to and the previous discussion , it seems that your WiFi/BT device is supported as of Linux kernel 6.2. Since Debian Bookworm is released with Linux kernel 6.1, you probably need to install a newer kernel.

Later: 6.7.5 kernel with rtw89 drivers compiled in fixed problem.

@ozsouth

Thanks oz, late here so will be tomorrow before I can test it and report.

wizard

@ozsouth

The rtw8852be found the wifi, did have to copy the .ko files into /lib/modules/6.1.67 before modprobe would find them. Will test more later.

Thanks
wizard

@wizard -

did have to copy the .ko files into /lib/modules/6.1.67 before modprobe would find them

Ah, so you are running bookworm as non-usrmerge? This .pet has .ko's in /usr/lib/modules, as per usrmerge.

@ozsouth

Just a standard 10.0.4 install. Wifi and Bluetooth are working except when the computer wakes up from suspend it looses wifi and has to be rebooted. Lsmod shows the module is still loaded, but when you open Connman no networks are shown. Any ideas on how to solve that?

Thanks
wizard

wizard wrote: ↑Sun Feb 25, 2024 11:53 pm

@ozsouth

Just a standard 10.0.4 install. Wifi and Bluetooth are working except when the computer wakes up from suspend it looses wifi and has to be rebooted. Lsmod shows the module is still loaded, but when you open Connman no networks are shown. Any ideas on how to solve that?

Thanks
wizard

I had this issue in BW64 until I went to a 6.6.x kernel from the 6.1.x in the BW64 isos (2nd gen i5 all intel laptop circa 2012). It has not recurred using kernels from 6.6.1 to 6.6.17 (all usrmerge structure adjusted). Try running @ozsouths' 6.6.13aoum kernel and see if connman will stay connected for you.

@wizard @Marv - this wireless driver is available in kernels 6.2 on, but must be compiled in. I didn't do that, but will make a 6.7 usrmerge kernel in the next few hours, with the rtw89 drivers.

@wizard LATER: Usrmerge Kernel 6.7.5 is in forum Kernels section.

@ozsouth

Have it up and running, thanks for your help. Forum is lucky to have someone with your skills.

wizard

BookwormPup64 10.0.5

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

BookwormPup64 10.0.5 running smoothly. Thank you radky and all who have contributed.

been using BW64 since last months. I am a linux user since 2005 and I can tell, this is really a great distro, puppy linux the final destination for the linux desktop distro-hoppers

Hardware report:

Lenovo Gen 3 Chromebook 11e - all works as before. No microphone (all linux is like that as far as I can tell) and the touchpad sensitivity is too low so it seems to be failing. The correct setting to make the touchpad usable out of the box in psynclient are Touch 15, Release 10.

Problem HP15 Cheap Walmart bargain bin AMD laptop continues to fail as before with the new kernel. I set it up with the 5.x kernel later to make sure that still works. I have an idea what it might be...

v10.0.6m will replace this.

Also made a more generic CPU temp1 data display (some cpus didn't like my previous one). Has Utility menu entry.

@ozsouth

Thanks for the Mediafire link

@radky

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.

ALERT: v10.0.5 has been retired due to a LAN adapter problem; under review.

Being launched via either not only gets to desktop but ALL BKWP64 features behave as expected.

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

Legend for 'N' (No) in table

• (1) - Drops out to GRUB prompt

• (2) - Stops at Console w/o Desktop

• (3) - TRAP/Abend during boot

• (4) - IMG Not Supported by Launcher

• (5) - Requires session-save parm, manually added, to GRUB2 Menu stanza for boot

• (6) - Not tested

Annoying wifi problem random on/off every minutes/seconds

02:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4313 802.11bgn Wireless Network Adapter [14e4:4727] (rev 01)

dmesg | grep irmware

[ 0.560169] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[ 23.231622] wmi_bus wmi_bus-PNP0C14:00: [Firmware Info]: 8232DE3D-663D-4327-A8F4-E293ADB9BF05 has zero instances
[ 23.231630] wmi_bus wmi_bus-PNP0C14:00: [Firmware Info]: 8F1F6436-9F42-42C8-BADC-0E9424F20C9A has zero instances
[ 23.231633] wmi_bus wmi_bus-PNP0C14:00: [Firmware Info]: 8F1F6435-9F42-42C8-BADC-0E9424F20C9A has zero instances
[ 25.578933] platform regulatory.0: firmware: direct-loading firmware regulatory.db
[ 25.579166] platform regulatory.0: firmware: direct-loading firmware regulatory.db.p7s
[ 30.869507] r8169 0000:01:00.0: firmware: direct-loading firmware rtl_nic/rtl8168d-2.fw
[ 31.042750] brcmsmac bcma0:1: firmware: direct-loading firmware brcm/bcm43xx-0.fw
[ 31.042891] brcmsmac bcma0:1: firmware: direct-loading firmware brcm/bcm43xx_hdr-0.fw
#

@esos Better show also output of dmesg | grep wlan0 (if wlan0 is your wifi device)

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