Fossapup64-9.0.3 RC

[peebee]

For UPupEF:
Uses
:Xdialog:|pet|Packages-puppy-common32-official|Xdialog-2016.12-i686_common32|Xdialog|2016.12-i686_common32||BuildingBlock|116||Xdialog-2016.12-i686_common32.pet|+gtk+2|Xdialog is designed to be a drop in replacement for the dialog or cdialog programs|slackware|14.0||
From
http://distro.ibiblio.org/puppylinux/pe ... mmon32.pet
with date
Xdialog-2016.12-i686_common32.pet 2019-Aug-20 02:21:58

from Woof-CE:
wdlkmpx committed on Aug 27, 2019:

https://github.com/puppylinux-woof-CE/w ... a8cdb298c5

[rerwin]

Thanks, peebee.

I have swapped Xdialog versions between BionicPup64 and FossaPup64 and find that both versions' updating works in BionicPup64 but not in FossaPup64!

So it is not a problem with Xdialog, but with something else in the recent Puppies that impacts Xdialog.

This looks messy.

EDIT: I see the same issue in EasyOS-2.3.2; the tailbox updating does not occur.

[666philb]

Thanks, peebee.

I have swapped Xdialog versions between BionicPup64 and FossaPup64 and find that both versions' updating works in BionicPup64 but not in FossaPup64!

So it is not a problem with Xdialog, but with something else in the recent Puppies that impacts Xdialog.

This looks messy.

EDIT: I see the same issue in EasyOS-2.3.2; the tailbox updating does not occur.

hi richard,

can you test these two Xdialogs and see if they are any better

cheers
phil

[01micko]

Also, this Xdialog is compiled in Fossa from fatdog source (jamesbond does have a fossil repo for Xdialog - and is an experienced software engineer)

[rerwin]

Thank you for your help with this issue.

None of the Xdialog pets updated the display beyond the first line.

Although I don't expect that Xdialog-2.6.5-x86_64.pet will show anything but the first line, it actually did not get that far! It aborted with an exit code of 134. FWIW, here is the trace:

Code: Select all

+ Xdialog --center --wmclass pgprs --title 'Pgprs GPRS Connection Log' --backtitle 'NOTICE: If log shows a failure to connect, click DISCONNECT to exit.' --ok-label 'DISCONNECT or stop trying' --cancel-label 'CLOSE window but stay online' --fixed-font --tailbox /tmp/.gprs_connect.log 25 82
*** buffer overflow detected ***: terminated
/usr/local/pgprs/pgprs-connect: line 63: 12281 Aborted                 Xdialog --center --wmclass pgprs --title "$(gettext 'Pgprs GPRS Connection Log')" --backtitle "$(gettext 'NOTICE: If log shows a failure to connect, click DISCONNECT to exit.')" --ok-label "$(gettext 'DISCONNECT or stop trying')" --cancel-label "$(gettext 'CLOSE window but stay online')" --fixed-font --tailbox /tmp/.gprs_connect.log 25 82
+ local STATUS=134

I now suspect the 'tail' command, in case Xdialog uses it. I am about to look into that possibility, because I think I had trouble with it when I used it in an alternate implementation of that dialog. I assume that would implicate the kernel.

[666philb]

Thank you for your help with this issue.

None of the Xdialog pets updated the display beyond the first line.

Although I don't expect that Xdialog-2.6.5-x86_64.pet will show anything but the first line, it actually did not get that far! It aborted with an exit code of 134. FWIW, here is the trace:

Code: Select all

+ Xdialog --center --wmclass pgprs --title 'Pgprs GPRS Connection Log' --backtitle 'NOTICE: If log shows a failure to connect, click DISCONNECT to exit.' --ok-label 'DISCONNECT or stop trying' --cancel-label 'CLOSE window but stay online' --fixed-font --tailbox /tmp/.gprs_connect.log 25 82
*** buffer overflow detected ***: terminated
/usr/local/pgprs/pgprs-connect: line 63: 12281 Aborted                 Xdialog --center --wmclass pgprs --title "$(gettext 'Pgprs GPRS Connection Log')" --backtitle "$(gettext 'NOTICE: If log shows a failure to connect, click DISCONNECT to exit.')" --ok-label "$(gettext 'DISCONNECT or stop trying')" --cancel-label "$(gettext 'CLOSE window but stay online')" --fixed-font --tailbox /tmp/.gprs_connect.log 25 82
+ local STATUS=134

I now suspect the 'tail' command, in case Xdialog uses it. I am about to look into that possibility, because I think I had trouble with it when I used it in an alternate implementation of that dialog. I assume that would implicate the kernel.

hi richard,

i have a new iso that should be ready tonight or tomorrow. it has a different kernel, so maybe wait until it's uploaded

[666philb]

fossapup64 9.0.3 uploaded

Kernel 5.4.47 (dropped to a more mature kernel line)
Wallpaper setter fixed ..... step
Smaller iso, now 405mb
Quickpet added (get devx, kernel sources etc there)
lots of niggles fixed
QT theming fixed
Back to new ROX (we'll see how it goes)
Psip updated ... oscartalks
Fixed menu icons not refreshing when adrv added/removed
Swapped compton for picom compositor. vsync should now work OTB so no more screen tearing or messing with xorg.conf!!! (for the first time in6 years my netbook is tear free) tested with radeon, intel, nouveau & nvidia and working for me.
Controls for the compositor are now in menu>>setup>>>screen graphics wizard.
Recipe uploaded to woofce (should be available soon)

I happy with this one and it will be an RC (release candidate) so please test everything.

download on first post http://www.murga-linux.com/puppy/viewtopic.php?t=118605

[rerwin]

I installed 9.0.3 but see that it has a problem, maybe several.

The desktop icons do not appear. Only gatotray and a cpu-load monitor appear in the tray, along with the 'menu' and 3 desktop icons. The task bar has the running programs, at expected. Conky displays as expected.

Rox-filer does not appear to run, as no window appears.

There is a continuing set of warnings in the xerrs.log, which keeps growing.

I am sending this from 9.0.3 by working from only the menu, in a new pupsave. I saw the same problems with my upgraded pupsave (from 9.0.2).

[666philb]

I installed 9.0.3 but see that it has a problem, maybe several.

The desktop icons do not appear. Only gatotray and a cpu-load monitor appear in the tray, along with the 'menu' and 3 desktop icons. The task bar has the running programs, at expected. Conky displays as expected.

Rox-filer does not appear to run, as no window appears.

There is a continuing set of warnings in the xerrs.log, which keeps growing.

I am sending this from 9.0.3 by working from only the menu, in a new pupsave. I saw the same problems with my upgraded pupsave (from 9.0.2).

aaargh! ... uploaded the wrong iso

new one uploading .... should be done 1hr from now.

wrong iso md5 7547c4aedab196888b21a792e149f5c5
correct iso md5 9626d24fbe32fa4711a3575773f8d47e

[rerwin]

Thanks. But 9.0.3 does not change the misbehavior, as I expected.

I mentioned earlier about checking the tail command. It turns out that it seems to work. My "alternate implementation" of the dialog works as expected.

• Screenshot1:
  Xdialog --center --wmclass pgprs --title "$(gettext 'Pgprs GPRS Connection Log')" --backtitle "$(gettext 'NOTICE: If log shows a failure to connect, click DISCONNECT to exit.')" --ok-label "$(gettext 'DISCONNECT or stop trying')" --cancel-label "$(gettext 'CLOSE window but stay online')" --fixed-font --logbox /tmp/.gprs_connect.log 25 82 #200607
  
  Screenshot2:
  tail --pid=$CONNECT_PID --follow /tmp/.gprs_connect.log | \
  Xdialog --center --wmclass pgprs --title "$(gettext 'Pgprs GPRS Connection Log')" --backtitle "$(gettext 'NOTICE: If log shows a failure to connect, click DISCONNECT to exit.')" --ok-label "$(gettext 'DISCONNECT or stop trying')" --cancel-label "$(gettext 'CLOSE window but stay online')" --fixed-font --logbox - 25 82 #200607

And I can watch the lines as they are added to the list.

To get pgprs working again I can probably use the "tail" method. But that doesn't resolve the Xdialog regression.

If this is not a widespread problem among Linux distributions, maybe there is a woofCE factor. But the fact that the problem exists in EasyOS which was built with Barry's woofQ would seem to rule that out.

I guess I need to set up a test I can use in Linux Mint (which I have) to see if the problem is there, too.

[bigpup]

Fossapup64-9.0.3
Frugal, save folder, internal emmc drive.

Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter [10ec:b822]
• Kernel Driver: r8822be

Fossapup64-9.0.3 missing driver.
/lib/modules/5.4.47/kernel/drivers/staging/rtlwifi/
Need kernel driver module r8822be

[artsown]

Volume control has no effect. Here are some relevant lines from
/var/log/Xorg.0.log

82.261] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event10)
[ 82.261] (II) No input driver specified, ignoring this device.
[ 82.261] (II) This device may have been added with another device file.
[ 82.261] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event11)
[ 82.261] (II) No input driver specified, ignoring this device.
[ 82.261] (II) This device may have been added with another device file.
[ 82.261] (II) config/udev: Adding input device HDA Intel PCH Line Out (/dev/input/event12)
[ 82.261] (II) No input driver specified, ignoring this device.
[ 82.261] (II) This device may have been added with another device file.
[ 82.261] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event13)
[ 82.261] (II) No input driver specified, ignoring this device.
[ 82.261] (II) This device may have been added with another device file.
[ 82.261] (II) config/udev: Adding input device PC Speaker (/dev/input/event14)
[ 82.261] (II) No input driver specified, ignoring this device.
[ 82.261] (II) This device may have been added with another device file.

Art

[666philb]

Fossapup64-9.0.3
Frugal, save folder, internal emmc drive.

Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter [10ec:b822]
• Kernel Driver: r8822be

Fossapup64-9.0.3 missing driver.
/lib/modules/5.4.47/kernel/drivers/staging/rtlwifi/
Need kernel driver module r8822be

hi bigpup,
can you try this .pet .... might need a reboot

[666philb]

Volume control has no effect. Here are some relevant lines

hi artstown ,

does the mixer work? if not right click on the volume icon and choose multiple sound card wizard

if the mixer is working and it's just the volume slider, open /root/.retrovolrc
and scroll down to near the end and swap the comments on the tray_control section.
example ........

Code: Select all

#tray_control=37
tray_control=18

to

Code: Select all

tray_control=37
#tray_control=18

save the changes, then quit retrovol with right click & quit then restart from the menu

[escucha]

Hi,
Thank you for this release candidate, it's very worth it!
Solved many detail and Palemoon is really updated!

I very much lack the possibility of full install. Have an old-new PC for this to try. Are there any script for do it?

What is happen to gatotray? see the image.

[artsown]

Volume control has no effect. Here are some relevant lines

hi artstown ,

does the mixer work? if not right click on the volume icon and choose multiple sound card wizard

if the mixer is working and it's just the volume slider, open /root/.retrovolrc
and scroll down to near the end and swap the comments on the tray_control section.
example ........

Code: Select all

#tray_control=37
tray_control=18

to

Code: Select all

tray_control=37
#tray_control=18

save the changes, then quit retrovol with right click & quit then restart from the menu

Mixer is/was working. Changing to tray_control=37 fixed the problem.

I'll note that I see tray_control=2 where you say tray_control=18

Art

[666philb]

Hi,
Thank you for this release candidate, it's very worth it!
Solved many detail and Palemoon is really updated!

I very much lack the possibility of full install. Have an old-new PC for this to try. Are there any script for do it?

What is happen to gatotray? see the image.

hi escucha,

i don't see anything wrong with gatotray ... the blue lines are free memory.
you can change colors by right clicking on it

[rerwin]

I notice there is no screen saver in FossaPup64's menu. Is that omission intentional? Or am I looking for the wrong name?

I think it is good to let the user have the screen blanked when the computer is not being used, without having to install the package. Or is a screen-blacker no longer important to most people?


Regarding pgprs:
I changed the kernel to BionicPup64's but still saw the failure to update the log display. So, it is not a kernel issue.

That tells me that, in 2019, something was changed in the woofCE world that impacts Xdialog's ability to update the display in logboxes and tailboxes. It is time for me to get onto woofCE in github about this.

[artsown]

I notice there is no screen saver in FossaPup64's menu.

It's under Desktop - JWMDesk Manager

Art

[bigpup]

Fossapup64-9.0.3
Frugal, save folder, internal emmc drive.

Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter [10ec:b822]
• Kernel Driver: r8822be

Fossapup64-9.0.3 missing driver.
/lib/modules/5.4.47/kernel/drivers/staging/rtlwifi/
Need kernel driver module r8822be

hi bigpup,
can you try this .pet .... might need a reboot

That pet worked.
Posting this from Fossapup64-9.0.3, using the r8822be kernel driver.

I did have to reboot and save, after installing the pet.

Thanks!