Puppy Linux Discussion Forum

I posted 5-6 days ago, version 3.1.9 got released, then withdrawn a few hours after uploading. Hopefully this time no show-stopper bugs!

Two very significant changes this time: firstly, both SeaMonkey and Firefox in the build, and secondly, have moved from an ALSA-only system to Pulseaudio, with Pipewire included in the build (but Pulseaudio set as the default).

I would have liked to bump the version to 3.2, but the move to Pulseaudio is bound to have issues that I have not yet discovered. So, we need one or two releases to find and fix these.

Well, there are other significant changes, not just those two. The kernel is now 5.10.78 and has been compiled with the 'wireguard' module, and the 'wireguard-tools' package is in the build.

Firefox can be run on the main desktop or in a container -- you will find "www" icons on the desktop for both of these. They are both very secure, as on the main desktop Firefox runs as user 'firefox' in its own sandbox.

You are welcome to test 3.1.10. I expect to refine further, then 3.2 will be the "final" that will be announced on distrowatch.

Blog announcement and download link here:

https://bkhome.org/news/202111/easyos-v ... eased.html

I hope that we can finally get Zoom working, see thread here:

viewtopic.php?t=3446

...the Firefox plugin seems like the best bet.

The new version has Firefox builtin, so if doing an update, have to get rid of the current FF.

I have just done an "update" of version 3.1 to 3.1.10. I already had Firefox SFS, running in container and on main desktop. Only deleted the firefox*.sfs as advised on the 3.1.10 blog announcement. After reboot, the "cleanup" did not work, still had "firefox" on desktop, leftover files in /home/firefox, and menu entries.

Another thing to fix. Anyway, manual cleanup is required. Quoting from the 3.1.9 release notes, modified:

If you are going to update an existing installation of EasyOS, before clicking on "update" on the desktop, if you have Firefox installed, get rid of it. Either roll back to an earlier snapshot before FF was installed, or...

If FF SFS is running on the main desktop:
Menu -> Filesystem -> Easy Boot Manager -> untick the FF checkbox
Delete /mnt/wkg/.session/home/firefox, /mnt/wkg/.session/usr/bin/firefox*, /mnt/wkg/.session/root/.mozilla/firefox

If FF SFS is running in a container:
Menu -> Filesystem -> Easy Container Management -> select firefox container and click "Delete & exit" button.

You can also delete the SFS in /mnt/wkg/sfs/easyos/oe/dunfell

Then reboot, then update.

EDIT:
And if perchance you already updated before reading this, no problem. Do all of the above before using the new FF. The last step will be to reboot, then the new builtin FF should be good to go.

Samba bug reported by Alfons, fixed:

https://bkhome.org/news/202111/samba-nm ... start.html

@BarryK
I installed EasyOS 3.1.10 to a magnetic hard drive of a BIOS Core Duo PC. Image burning went well, system worked well at the first boot. At second boot Easy will not auto logon to the wired internet.

Nov 16 16:52:36 EASYPC10281 daemon.info NetworkManager[3828]: <info>  [1636998756.5754] NetworkManager (version 1.22.10) is starting... (for the first time)
Nov 16 16:52:36 EASYPC10281 daemon.info NetworkManager[3828]: <info>  [1636998756.5755] Read config: /etc/NetworkManager/NetworkManager.conf
Nov 16 16:52:36 EASYPC10281 daemon.err NetworkManager[3828]: <error> [1636998756.5767] bus-manager: cannot connect to D-Bus: Could not connect: No such file or directory
Nov 16 16:52:36 EASYPC10281 daemon.info NetworkManager[3828]: <info>  [1636998756.5768] exiting (error)

I bet the time+date stamp is the reason for the problem. No, that ain't it. I changed the initrd. init script line 88 is now setup to export TZ='CET'. All time+date stamps are correct now but the problem is still the same.

/tmp/xerrs.log shows this:

(nm-applet:3647): nm-applet-WARNING **: 20:43:42.825: Verbindung ist gescheitert: Datei oder Verzeichnis nicht gefunden
(nm-applet:3647): libnm-CRITICAL **: 20:43:42.833: ((../NetworkManager-1.22.10/libnm/nm-client.c:3905)): assertion '<dropped>' failed
(nm-applet:3647): libnm-CRITICAL **: 20:43:42.833: ((../NetworkManager-1.22.10/libnm/nm-client.c:3859)): assertion '<dropped>' failed
(nm-applet:3647): libnm-CRITICAL **: 20:43:42.898: ((../NetworkManager-1.22.10/libnm/nm-client.c:4695)): assertion '<dropped>' failed

The complete 'message' file with fake 'gz' right here

HI.
having a network problem with this release. not loading the driver for the RTL8125b 2.5Gb network interface.
could you include it in the next release
thanks

BarryK wrote: ↑Mon Nov 15, 2021 1:41 am

Samba bug reported by Alfons, fixed:

https://bkhome.org/news/202111/samba-nm ... start.html

Another fix for samba. Have appended to the blog post.

FeodorF wrote: ↑Mon Nov 15, 2021 6:14 pm

@BarryK
I installed EasyOS 3.1.10 to a magnetic hard drive of a BIOS Core Duo PC. Image burning went well, system worked well at the first boot. At second boot Easy will not auto logon to the wired internet.

Network-icon-second-boot.png

Code: Select all

Nov 16 16:52:36 EASYPC10281 daemon.info NetworkManager[3828]: <info>  [1636998756.5754] NetworkManager (version 1.22.10) is starting... (for the first time)
Nov 16 16:52:36 EASYPC10281 daemon.info NetworkManager[3828]: <info>  [1636998756.5755] Read config: /etc/NetworkManager/NetworkManager.conf
Nov 16 16:52:36 EASYPC10281 daemon.err NetworkManager[3828]: <error> [1636998756.5767] bus-manager: cannot connect to D-Bus: Could not connect: No such file or directory
Nov 16 16:52:36 EASYPC10281 daemon.info NetworkManager[3828]: <info>  [1636998756.5768] exiting (error)

I bet the time+date stamp is the reason for the problem. No, that ain't it. I changed the initrd. init script line 88 is now setup to export TZ='CET'. All time+date stamps are correct now but the problem is still the same.

/tmp/xerrs.log shows this:

Code: Select all

(nm-applet:3647): nm-applet-WARNING **: 20:43:42.825: Verbindung ist gescheitert: Datei oder Verzeichnis nicht gefunden
(nm-applet:3647): libnm-CRITICAL **: 20:43:42.833: ((../NetworkManager-1.22.10/libnm/nm-client.c:3905)): assertion '<dropped>' failed
(nm-applet:3647): libnm-CRITICAL **: 20:43:42.833: ((../NetworkManager-1.22.10/libnm/nm-client.c:3859)): assertion '<dropped>' failed
(nm-applet:3647): libnm-CRITICAL **: 20:43:42.898: ((../NetworkManager-1.22.10/libnm/nm-client.c:4695)): assertion '<dropped>' failed

The complete 'message' file with fake 'gz' right here
messages.gz

I seems that your dbus daemon isn't starting:

Nov 16 16:52:36 EASYPC10281 daemon.info NetworkManager[3828]: <info>  [1636998756.5754] NetworkManager (version 1.22.10) is starting... (for the first time)
Nov 16 16:52:36 EASYPC10281 daemon.info NetworkManager[3828]: <info>  [1636998756.5755] Read config: /etc/NetworkManager/NetworkManager.conf
Nov 16 16:52:36 EASYPC10281 daemon.err NetworkManager[3828]: <error> [1636998756.5767] bus-manager: cannot connect to D-Bus: Could not connect: No such file or directory
Nov 16 16:52:36 EASYPC10281 daemon.info NetworkManager[3828]: <info>  [1636998756.5768] exiting (error)
Nov 15 18:52:39 EASYPC10281 user.warn pulseaudio[3865]: [pulseaudio] main.c: Dieses Programm sollte ohne die Option --system nicht als Administrator ausgeführt werden.
Nov 15 18:52:39 EASYPC10281 user.err pulseaudio[3868]: [pulseaudio] bluez5-util.c: Failed to get D-Bus connection: Failed to connect to socket /run/dbus/system_bus_socket: Datei oder Verzeichnis nicht gefunden

This looks like the problem:

Failed to connect to socket /run/dbus/system_bus_socket

A quick check that dbus-daemon is running:

# ps | grep dbus
or
# pidof dbus-daemon

The dbus daemon is started in /etc/init.d/messagebus
If it isn't running, perhaps try from a terminal, see if any error messages:

# /etc/init.d/messagebus restart

It has been awhile since I connected via ethernet. These days I connect via my phone.
So, on the Compaq Presario, replaced the wifi dongle with a TP-Link ethernet wireless range extender. So ethernet cable from the PC to the extender, then wireless to my phone. Connects, and still works after reboot.

Yeah, so it seems something is upsetting your dbus daemon.

Cherrypuppy wrote: ↑Mon Nov 15, 2021 11:05 pm

HI.
having a network problem with this release. not loading the driver for the RTL8125b 2.5Gb network interface.
could you include it in the next release
thanks

Is it a missing firmware, rather than missing driver?

# dmesg | grep -i firmware

@BarryK

# ps | grep dbus
1284 root 0:00 {rc.services_ipc} /bin/ash /etc/rc.d/rc.services_ipc bluetoothhw:dbus bluetooth:bluealsa
3667 root 0:00 dbus-launch --autolaunch=715310279e5dcfb1db46c9f76192066a --binary-syntax --close-stderr
3668 root 0:00 /usr/bin/dbus-daemon --syslog-only --fork --print-pid 5 --print-address 7 --session
4184 root 0:00 grep dbus
#

# /etc/init.d/messagebus restart
3668 ? Ss 0:00 dbus-daemon
#

/etc/init.d/messagebus Line 16: PIDFILE=/var/run/dbus/pid
The directory /pid does not exist.

I'm using the german version of EasyOS-3.1.10 . It does not matter - right?

FeodorF wrote: ↑Tue Nov 16, 2021 7:36 am

/etc/init.d/messagebus Line 16: PIDFILE=/var/run/dbus/pid
The directory /pid does not exist.

'pid' is not a directory, it is a file.
It contains the pid of the dbus daemon, in my case, the file has "3838"

# pidof dbus-daemon
5620 4092 3838

Interesting, I have more than one dbus-daemon running, and the 'pid' file only has pid of one of them.

BarryK wrote: ↑Tue Nov 16, 2021 1:30 am

This looks like the problem:

Code: Select all

Failed to connect to socket /run/dbus/system_bus_socket

This was your problem. Does the socket exist?

If it does, and NetworkManager is not running (as your earlier post reported it failed to run due to missing dbus socket), try starting it from a terminal:

# /usr/sbin/NetworkManager --pid-file=/run/NetworkManager/NetworkManager.pid

If it does start, then your network tray applet should work.
If it doesn't, the terminal may display useful error messages.

@BarryK
The error 'Failed to connect to socket /run/dbus/system_bus_socket' is still present. /run/dbus directory does not exist

At the first run of EasyOS I tested Firefox with success. After closing Firefox I started Menu->Internet->Seamonkey Browser also with success.
Would this cause any kind of trouble?

-----------------------------------
Found the problem!
Sound is the problem. I use a USB sound card to improve sound quality on this old BIOS PC. After I unplugged the USB device the NetworkManager started working. Posting of EasyOS-3.1.10 right now.

Using this one to output analogue sound:
viewtopic.php?p=38763#p38763
----------------------------------
About
# pidof dbus-daemon
3882 3160
#

FeodorF wrote: ↑Tue Nov 16, 2021 11:41 am

@BarryK
The error 'Failed to connect to socket /run/dbus/system_bus_socket' is still present. /run/dbus directory does not exist

At the first run of EasyOS I tested Firefox with success. After closing Firefox I started Menu->Internet->Seamonkey Browser also with success.
Would this cause any kind of trouble?

-----------------------------------
Found the problem!
Sound is the problem. I use a USB sound card to improve sound quality on this old BIOS PC. After I unplugged the USB device the NetworkManager started working. Posting of EasyOS-3.1.10 right now.

Using this one to output analogue sound:
viewtopic.php?p=38763#p38763
----------------------------------

Very interesting...
If dbus-daemon is running, does it crash if you plug in the usb snd device? You can run "pidof dbus-daemon" before and after.

If it is still running, run "mscw" and select the usb snd device, then see if the daemon is still running.

My guess is that a dbus rule for chip 0D8C:013C is causing the daemon to crash.

@BarryK
The only errors left after booting EasyOS this morning.

Nov 17 03:18:31 EASYPC10281 user.warn pulseaudio[3897]: [pulseaudio] main.c: Dieses Programm sollte ohne die Option --system nicht als Administrator ausgeführt werden.
Nov 17 03:18:32 EASYPC10281 user.err pulseaudio[3900]: [pulseaudio] module-console-kit.c: GetSessionsForUnixUser() call failed: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ConsoleKit was not provided by any .service files
Nov 17 03:18:32 EASYPC10281 user.err pulseaudio[3900]: [pulseaudio] module.c: Failed to load module "module-console-kit" (argument: ""): initialization failed.
Nov 17 03:18:32 EASYPC10281 user.err pulseaudio[3900]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.ServiceUnknown: The name org.bluez was not provided by any .service files
Nov 17 02:27:17 EASYPC10281 auth.notice su: + tty1 root:seamonkey(/code)

Before plugging in the USB audio:
# pidof dbus-daemon
3847 3125
# 

After plugging in the USB audio
# pidof dbus-daemon
3847 3125
# 

mscw:
[attachment=0]mscw.png[/attachment]

[code]Nov 17 02:27:17 EASYPC10281 auth.notice su: + tty1 root:seamonkey
Nov 17 02:38:13 EASYPC10281 kern.info kernel: [ 1218.156220] usb 5-2: new full-speed USB device number 2 using uhci_hcd
Nov 17 02:38:13 EASYPC10281 kern.info kernel: [ 1218.383248] usb 5-2: New USB device found, idVendor=0d8c, idProduct=013c, bcdDevice= 1.00
Nov 17 02:38:13 EASYPC10281 kern.info kernel: [ 1218.383254] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Nov 17 02:38:13 EASYPC10281 kern.info kernel: [ 1218.383258] usb 5-2: Product: USB PnP Sound Device
Nov 17 02:38:13 EASYPC10281 kern.info kernel: [ 1218.383262] usb 5-2: Manufacturer: C-Media Electronics Inc.      
Nov 17 02:38:13 EASYPC10281 kern.info kernel: [ 1218.390035] input: C-Media Electronics Inc.       USB PnP Sound Device as /devices/pci0000:00/0000:00:1d.3/usb5/5-2/5-2:1.3/0003:0D8C:013C.0004/input/input15
Nov 17 02:38:13 EASYPC10281 kern.info kernel: [ 1218.446421] hid-generic 0003:0D8C:013C.0004: input: USB HID v1.00 Device [C-Media Electronics Inc.       USB PnP Sound Device] on usb-0000:00:1d.3-2/input3
Nov 17 03:38:13 EASYPC10281 user.info mtp-probe: checking bus 5, device 2: "/sys/devices/pci0000:00/0000:00:1d.3/usb5/5-2"
Nov 17 03:38:13 EASYPC10281 user.info mtp-probe: bus: 5, device: 2 was not an MTP device
Nov 17 02:38:13 EASYPC10281 kern.info kernel: [ 1218.895932] mc: Linux media interface: v0.10
Nov 17 02:38:14 EASYPC10281 kern.info kernel: [ 1218.984046] usbcore: registered new interface driver snd-usb-audio
Nov 17 03:38:14 EASYPC10281 user.info mtp-probe: checking bus 5, device 2: "/sys/devices/pci0000:00/0000:00:1d.3/usb5/5-2"
Nov 17 03:38:14 EASYPC10281 user.info mtp-probe: bus: 5, device: 2 was not an MTP device

After plugging in the USB sound device there is no more sound using card 0. If I assign card 0 there is still no sound through the PC audio plug. dbus daemon is still using the same pids. mscw outputs this message: 'Audio is set to use this card: hw:0,0'

But I do pick up sound using the USB audio plug at the same time. Card 0 is still prompted as audio source. Changing the volume works on the USB plug too

Now I am trying card1. mscw outputs: 'Audio is set to use this card: hw:1,0' Sound output is still the USB card - volume adjustable. Reverting it back to card0 doesn't change anything - the USB has still priority over the output.

I have one of these, not that exact same vendor, just searched for the "5hv2 usb sound card" and the photo is the same as mine, except mine is white:

https://www.aliexpress.com/item/32823081232.html

I will test it.

There is one thing I should add if you do a software reset (X server restart) sound and NetworkManager will still work but doing a hard reset results in a none functioning NetworkManager.

Quick initial test of 3.1.10 and have to report that my ethernet connection is dead after first reboot as well. NetworkManager not running and does not want to start. Will investigate further when I get more time.

Also, this machine has the 3 soundcards, intel integrated, pci and usb. The usual fix for me to get the order right is editing /etc/modprobe.d/alsa-base.conf but that edit does not persist now. I have added a fix.conf in the new /etc/modprobe.d.NUMBER directory with the settings and that works. The intel now is the default (which is what I want) and not the pci card. Not sure if this has any implications more widely

options snd-hda-intel index=0
options snd-cmipci index=1
options snd-usb-audio index=2

dbus-daemon, networkmanager, fixed!

It was great to have the same, or similar, hardware that you guys were getting the problem.
I plugged in my usb snd adapter, and got the same problem after a reboot.

I found the cause, fix posted here:

https://bkhome.org/news/202111/show-sto ... fixed.html

...a syntax error in /etc/init.d/10alsa, the "[0-9]" in line 39 has to be changed to just "0".

FeodorF wrote: ↑Wed Nov 17, 2021 2:48 am

Now I am trying card1. mscw outputs: 'Audio is set to use this card: hw:1,0' Sound output is still the USB card - volume adjustable. Reverting it back to card0 doesn't change anything - the USB has still priority over the output.

Yes, that is another problem.
The "test sound" button in mscw works, plays to the selected card. But, looks like it is not being set as default.

BarryK wrote: ↑Thu Nov 18, 2021 1:55 pm

FeodorF wrote: ↑Wed Nov 17, 2021 2:48 am

Now I am trying card1. mscw outputs: 'Audio is set to use this card: hw:1,0' Sound output is still the USB card - volume adjustable. Reverting it back to card0 doesn't change anything - the USB has still priority over the output.

Yes, that is another problem.
The "test sound" button in mscw works, plays to the selected card. But, looks like it is not being set as default.

OK, seem to have fixed it:

https://bkhome.org/news/202111/pulseaud ... k-fix.html

More changes were made to /usr/sbin/mscw than shown in the blog post.
I am expecting to get 3.1.11 out soon, with this fix.

Why wait until the next release...
Attached are /etc/init.d/10alsa and /usr/sbin/mscw scripts, with false .gz

Would it be a good idea to remove "GetFlash - install Flash Player" now? Flash Player is dead and no longer supported. If you try to install the latest version it gives an error. The really old version (11) does install from somewhere, but the browsers no longer recognise it as a plugin anyway.

OscarTalks wrote: ↑Sat Nov 20, 2021 1:31 am

Would it be a good idea to remove "GetFlash - install Flash Player" now? Flash Player is dead and no longer supported. If you try to install the latest version it gives an error. The really old version (11) does install from somewhere, but the browsers no longer recognise it as a plugin anyway.

OK, removed.