Page 10 of 13
volume control issue
Posted: Sat 27 Jun 2020, 13:40
by artsown
@Phil
Concerning the volume control bug, I installed 9.0.3 on two more
quite different machines and they did not have the problem. My
main machine that did have the problem is a Dell Optiplex 3020
having i5-4570 cpu quad core and 8 gig ram. On all machines I
install frugal to internal hard drive.
IIRC, initially my main machine had all (four) sound cards shown
as installed ... if that is any kind of clue. But simply making sure
only the analog and not a hdmi one was not enough to fix the problem.
Hope this helps.
Art
md5sum of 9.0.3 iso
Posted: Sat 27 Jun 2020, 14:00
by Marv
I've downloaded the 9.0.3 iso several times in the course of getting my ff install updated. I haven't as yet been able to match the md5sum in the link on the first post.
That is: 607841fad7308c4b4b1fcf619ace4369
The md5sum I get on the re-uploaded isos is consistently : 9626d24fbe32fa4711a3575773f8d47e
I was able to get the original 9.0.3 to boot after a bit of library repair and the re-uploaded iso boots and runs well OOTB on my i5 based Fujitsu S761 laptop. Posting from Slimjet Version 26.0.10.0 run-as-spot from SFS in 9.0.3 now.
Thanks,
Posted: Sat 27 Jun 2020, 14:05
by bigpup
Fossapup64 9.0.3
No menu entry for anyway to control Conky.
Pburn is not installed.
Not going to have Pburn in Fossapup?
Re: md5sum of 9.0.3 iso
Posted: Sat 27 Jun 2020, 17:10
by artsown
Marv wrote:I've downloaded the 9.0.3 iso several times in the course of getting my ff install updated. I haven't as yet been able to match the md5sum in the link on the first post.
That is: 607841fad7308c4b4b1fcf619ace4369
The md5sum I get on the re-uploaded isos is consistently : 9626d24fbe32fa4711a3575773f8d47e
Thanks,
The md5sum starting with 962... is correct. It's given correctly at the
d/l site. I don't see the old one starting with 607... anywhere.
Art
Posted: Sat 27 Jun 2020, 17:47
by 666philb
bigpup wrote:Fossapup64 9.0.3
No menu entry for anyway to control Conky.
Pburn is not installed.
Not going to have Pburn in Fossapup?
good catch with pburn .... it's supposed to be in, need to figure out why it isn't.
i'll make a small gui for conky ... at least a start/stop thing anyway
edit: added pburn quickpet updates
Posted: Sat 27 Jun 2020, 18:03
by artsown
666philb wrote:bigpup wrote:Fossapup64 9.0.3
Pburn is not installed.
Not going to have Pburn in Fossapup?
good catch with pburn .... it's supposed to be in, need to figure out why it isn't.
For those (like me) who may just wind up using 9.0.3 for a long time
and want it to be complete .... it's available via PPM ... and it appears
in the usual menu location.
Art
Posted: Sun 28 Jun 2020, 00:28
by bigpup
Fossapup64 9.0.3
I am seeing some strange icons in a lot of program windows.
These are clickable items in the program.
This is one example, but not the only program having this problem.
Update:
This is being caused by choosing Rox icon theme in
menu->Desktop->JWMdesk Manager->GTK Theme->Icon theme
I was using Rox theme.
Changed to PMaterial
This fixed icons in programs.
Posted: Sun 28 Jun 2020, 07:27
by bigpup
V9.0.3
After Quickpet->Info->Fossapup updates
Program windows, the menu, etc... are unstable.
They display cycle visible not visible.
This is a listed item for updates bug fixes.
27/06/2020 updated picom gui and added menu entry.
I opened menu->Desktop->Window Effects
Selected stop.
This fixed it.
Everything visibly stable and normal, now.
Update:
This does not seem to totally fix the problem.
Next cold boot.
The problem returned.
I opened menu->Desktop->Window Effects
Selected remove autostart
This seems to help on reboot.
Posted: Sun 28 Jun 2020, 15:13
by foxpup
I thought I might join in testing.
Frugal install on a dell vostro 1510 laptop.
I have the same as bigpup with flickering menu and taskbar items.
It is back at every new startup.
Do we need picom?
I do not have the problem with the strange icons (missing?).
Background for conky is black. Shouldnt it be transparant?
(I am not a fan of widgets like that anyway.)
Isn't qbat using too much memory?
The battery is eol so this laptop is always on the electric cord.
I would like to have cpu temperature instead.
Just my 2 pennies.
I run fossapup with adrv.
It is a bit more resource hungry than easypup from Barry.
Maybe I should not compare the two.
I haven't found big flaws for now.
It looks good and reliable and has everything I want from a Puppy.
(I've just added xfe for a dual pane filemanager.)
.
Posted: Mon 29 Jun 2020, 03:38
by bigpup
See my update, to 2 previous posts, about strange icons in programs and flashing windows.
Posted: Mon 29 Jun 2020, 04:00
by bigpup
v9.0.3
Tried to check xerrs.log
Get this:
logging of X errors is disabled
remove /var/local/xwin_disable_xerrs_log_flag to enable it, then restart X
Sure you want it set this way to not log errors?
Posted: Mon 29 Jun 2020, 08:08
by ETP
bigpup wrote:v9.0.3
Tried to check xerrs.log
Get this:
logging of X errors is disabled
remove /var/local/xwin_disable_xerrs_log_flag to enable it, then restart X
Sure you want it set this way to not log errors?
Hi bigpup,
Probably best to have it turned on for testing purposes as there are
errors showing in it such as :
- libpng warning: iCCP: known incorrect sRGB profile
/usr/sbin/dunst-config: line 311: uint32: command not found
/usr/sbin/dunst-config: line 312: uint32: command not found
/usr/sbin/dunst-config: line 313: uint32: command not found
/usr/sbin/dunst-config: line 314: uint32: command not found
/usr/sbin/dunst-config: line 315: uint32: command not found
Posted: Mon 29 Jun 2020, 10:39
by 666philb
bigpup wrote:V9.0.3
After Quickpet->Info->Fossapup updates
Program windows, the menu, etc... are unstable.
They display cycle visible not visible.
This is a listed item for updates bug fixes.
27/06/2020 updated picom gui and added menu entry.
I opened menu->Desktop->Window Effects
Selected stop.
This fixed it.
Everything visibly stable and normal, now.
Update:
This does not seem to totally fix the problem.
Next cold boot.
The problem returned.
I opened menu->Desktop->Window Effects
Selected remove autostart
This seems to help on reboot.
hi bigpup,
can you do some testing with picom. i've attached a .pet that may fix the flickering issue. i've also fixed some problems with the GUI.
first test is with GLX & Vsync selected. is the flickering now fixed?
second try the Hybrid backend.
if you still have flicker try the Xrender backend as that is what the default was in bionicpup.
note that vsync doesn't work with the xrender backend (even if ticked).
concerning xerrs.log, this is now the default setting in woofce. some apps spam the log (chrome based browsers and some gnome apps) . here's the quote in woofce
use Boot Manager to enable or disable logging to /tmp/xerrs.log
I once ran out of ram when for some reason xerrs.log had 1GB of garbage
boot params:
xerrs - enable logging
noxerrs - disable logging
Posted: Mon 29 Jun 2020, 10:45
by 666philb
foxpup wrote:I thought I might join in testing.
Frugal install on a dell vostro 1510 laptop.
I have the same as bigpup with flickering menu and taskbar items.
It is back at every new startup.
Do we need picom?
I do not have the problem with the strange icons (missing?).
Background for conky is black. Shouldnt it be transparant?
(I am not a fan of widgets like that anyway.)
Isn't qbat using too much memory?
The battery is eol so this laptop is always on the electric cord.
I would like to have cpu temperature instead.
Just my 2 pennies.
I run fossapup with adrv.
It is a bit more resource hungry than easypup from Barry.
Maybe I should not compare the two.
I haven't found big flaws for now.
It looks good and reliable and has everything I want from a Puppy.
(I've just added xfe for a dual pane filemanager.)
.
hi foxpup,
the black square around conky can be fixed by resetting the background or restarting x. if you are still getting a square try increasing the second sleep duration in /root/Startup/conkystart.
also concerning the flickering, can you see my reply to bigpup above and give the .pet a test.
none of the temperature tray .pets work on all setups so i'm not including one in fossapup.
cheers
Posted: Mon 29 Jun 2020, 11:20
by 01micko
ETP wrote:bigpup wrote:v9.0.3
Tried to check xerrs.log
Get this:
logging of X errors is disabled
remove /var/local/xwin_disable_xerrs_log_flag to enable it, then restart X
Sure you want it set this way to not log errors?
Hi bigpup,
Probably best to have it turned on for testing purposes as there are
errors showing in it such as : (snip)
See woof-CE commit
a298623 where I add the option to enable/disable xerrs.log at woof build, with appropriate recommendations, IMHO, in the config file(s).
Code: Select all
## XERRS_FLG if set to 'yes' enables logging of X errors in /tmp/xerrs.log
## if unset or or any value other than 'yes' X logging is disabled. User can change this in 'Startup Manager'
## For testing builds XERRS_FLG=yes is recommended. If the target device is low RAM suggest to leave this unset, especially for release
XERRS_FLG=yes
Posted: Mon 29 Jun 2020, 12:21
by bigpup
can you do some testing with picom. i've attached a .pet that may fix the flickering issue. i've also fixed some problems with the GUI.
first test is with GLX & Vsync selected. is the flickering now fixed?
second try the Hybrid backend.
if you still have flicker try the Xrender backend as that is what the default was in bionicpup.
Installed pet.
Only setting that fixed it was Xrender.
Still had flickering in any of the other settings.
Posted: Mon 29 Jun 2020, 13:20
by 666philb
bigpup wrote:can you do some testing with picom. i've attached a .pet that may fix the flickering issue. i've also fixed some problems with the GUI.
first test is with GLX & Vsync selected. is the flickering now fixed?
second try the Hybrid backend.
if you still have flicker try the Xrender backend as that is what the default was in bionicpup.
Installed pet.
Only setting that fixed it was Xrender.
Still had flickering in any of the other settings.
i'll go with the xrender backend as default then.
Posted: Mon 29 Jun 2020, 14:07
by 666philb
bigpup wrote:can you do some testing with picom. i've attached a .pet that may fix the flickering issue. i've also fixed some problems with the GUI.
first test is with GLX & Vsync selected. is the flickering now fixed?
second try the Hybrid backend.
if you still have flicker try the Xrender backend as that is what the default was in bionicpup.
Installed pet.
Only setting that fixed it was Xrender.
Still had flickering in any of the other settings.
hi bigpup,
can you try this ...
open window effects then click on 'settings' and change line 327 to
and then try picom again with vsync ticked and GLX selected
Posted: Mon 29 Jun 2020, 18:44
by foxpup
intel graphics (GM965/GL960) and modesetting Xorg driver.
First the flickering. On my laptop:
After quickpet update and with the pet, all combinations are good, except
Hybrid and Vsync checked still has flickering.
With "use-damage = false" this flickering disappears as well.
The black field for conky disappears after X restart,
but not after resetting the wallpaper nor with sleep 20 in the startup script.
It's not nice to have to restart X to have transparency for conky.
"poorercputemp", recent .pets by 01micko, works well on this dell.
Posted: Mon 29 Jun 2020, 19:14
by Marv
I5 based Fujitsu S761 laptop with modesetting Xorg Driver and Intel HD Graphics 3000
No flickering OOTB in 9.0.3 on this laptop.
I do have the 'missing' icons in geany for example. Doesn't seem to be a function of changing theme or icon theme. I didn't try all, but did add in a theme or two and try most of the icon theme sets in the process.
No sound in the stock 9.0.3 on this hardware, no soundcard found by retrovol or using either soundcard wizard. Changing the active line in this portion of the .retrovolrc file from 18 to 37 has no effect.
Code: Select all
# Which slider to link with the tray_icon, identified by numid
#tray_control=37
tray_control=18
Doublechecked both in a pristine install and in my 9.0.2 update.
Going back to the 5.6.7 kernel from 9.0.2 gets the sound back immediately on this hardware. No fiddling with .retrovolrc or any other changes required.
Thanks,