Announcement and links here:
https://bkhome.org/news/202203/easyos-v ... eased.html
Feedback welcome!
Moderator: BarryK
Announcement and links here:
https://bkhome.org/news/202203/easyos-v ... eased.html
Feedback welcome!
Hi!
Problems with synaptic driver on my Acer Spin 1.
Born to lose; live to win
Same problem when I update using 2 different USB sticks and tried them on
samsung n210 plus and lenovo yoga 530.
With a normal usb mouse it is no problem.
I did not , so far, experienced another problem.
@BarryK For the positve part, keep going on, thanks for your enthusiasm!!!
I have received an email from eps, that gparted doesn't work.
Yes, for gparted 1.3.1, the author has moved files around, compared with the version we had previously.
/usr/libexec/gpartedbin is missing.
Get it from here:
https://distro.ibiblio.org/easyos/amd64 ... n.false.gz
Take off that ".false.gz", place it at /usr/libexec, make sure it is executable.
From your photo above, I see a problem. The tray width is supposed to automatically adjust, depending on the screen resolution. The default is 1024, but it is bigger when the screen width is bigger, see code in /root/.xinitrc:
Code: Select all
if [ "$SCRN_X" != "$oldSCRNX" ];then
#may need to display app icons without labels...
/usr/local/ui/jwm/jwmrc-insert-icons
#20220311 adjust tray width to suit screen...
if [ $SCRN_X -le 1366 ];then
trayX=$SCRN_X
elif [ $SCRN_X -le 1600 ];then
trayX=1366
else
trayX=1440 #$(($SCRN_X*3/4)) #3/4 ex: 1920 becomes 1440
#...no need to go wider.
fi
PTNt='s%\(<Tray .*width="\)[0-9][0-9][0-9][0-9]"%\1'"${trayX}"'"%'
sed -i -e "$PTNt" /root/.jwmrc-tray
fi
...it seems that either that section of code isn't getting triggered, or the code has a bug.
Note, you can manually increase tray width. Edit /root/.jwmrc-tray, change the width="1024" in the <Tray> tag, to something bigger.
Should do.
But then, as I recall, you have strange laptop hardware.
But, 3.4.3 has an updated kernel, might have improved the situation, as long as suitable driver is builtin to the kernel, not as a module.
Built a fresh memory stick, all ok
rebooted it on the workstation and all was ok
however I moved the stick to one of my legacy boxes, and it fails, not even from powerdown works.
Successfully updated from version 3.4.1 using the inbuilt tool.
The bug with Geany spell checker reported viewtopic.php?p=52131#p52131 also is present in 3.4.3.
@BologneChe ,
I found the cause of the problem, it is the new kernel:
https://bkhome.org/news/202203/kernel-5 ... -work.html
Recompiling the kernel right now.
scsijon wrote: Sun Mar 20, 2022 10:25 pmBuilt a fresh memory stick, all ok
rebooted it on the workstation and all was ok
however I moved the stick to one of my legacy boxes, and it fails, not even from powerdown works.
@scsijon ,
On that legacy box, does it start to boot, and get to the "switch_root"?
If so, what GPU does it have?
There may be a problem with some old video cards, as was unable to compile some xorg video drivers
-- some of them are not being maintained, and won't compile with the 21.x xserver.
Version 3.4.4 should be out very soon. See above posts for some fixes.
Also, I have been working on the user interface, lots of tweaks. Flipping between ROX icons-on-desktop and JWM icons-in-tray much improved.
As one person reported, had to put on his sunglasses to watch the setting sun wallpaper. Well, 3.4.4 will have a new theme, much easier on the eyes.
Very interesting that, the current theme does seem to be hard on the eyes. Purely psychological?
proebler wrote: Mon Mar 21, 2022 1:33 amSuccessfully updated from version 3.4.1 using the inbuilt tool.
The bug with Geany spell checker reported viewtopic.php?p=52131#p52131 also is present in 3.4.3.
This is a problem, I don't know why enchant won't work with geany.
I looked at the enchant docs, it seems to be configured correctly, to find the dictionaries.
@BarryK
Thumb up on my side for an old 2009 bios box with Intel CPU and Nvidea GK208B (MSI GT710 from 2018) graphics card. The HDMI output with 1680x1050 pixels (quirk Samsung screen) can be used without problem.
BarryK wrote: Tue Mar 22, 2022 1:25 amproebler wrote: Mon Mar 21, 2022 1:33 amSuccessfully updated from version 3.4.1 using the inbuilt tool.
The bug with Geany spell checker reported viewtopic.php?p=52131#p52131 also is present in 3.4.3.This is a problem, I don't know why enchant won't work with geany.
I looked at the enchant docs, it seems to be configured correctly, to find the dictionaries.
Think now fixed:
There hasn't been any feedback running with radeon/amd video.
I have one PC with an old ati/amd video card (Radeon HD 6870), and it works OK.
There is a potential conflict as the kernel has two ati/amd drivers, radeon.ko and amdgpu.ko, and in some cases both may load, causing potential conflict, though this is supposed to fix the conflict:
https://bkhome.org/news/202203/amdgpu-v ... dules.html
I guess will go ahead and release 3.4.4 without having definite feedback that recent amd GPUs work.
I forget who reported this: Osmo starting as a regular window when the desktop starts, rather than minimized as a systray applet.
Anyway, seems to be fixed:
https://bkhome.org/news/202203/jwm-fail ... stray.html
Version 3.4.4 is ready to go. But, will wait, in case any more feedback, especially about whether 3.4.3 works with amd GPUs. So, looking at uploading tomorrow afternoon.
The new theme is very interesting, totally different, a jet-black theme.
I have an older laptop with a Radeon HD 6700M graphics card. Radeon driver loaded ok, no problems. A while back I was messing about with graphics drivers on Fatdog, and had both radeon.ko and amdgpu.ko loaded at the same time with no ill effects (or benefits). Not tried it on EasyOS though.
Keef wrote: Wed Mar 23, 2022 7:49 pmI have an older laptop with a Radeon HD 6700M graphics card. Radeon driver loaded ok, no problems. A while back I was messing about with graphics drivers on Fatdog, and had both radeon.ko and amdgpu.ko loaded at the same time with no ill effects (or benefits). Not tried it on EasyOS though.
Thanks for doing the test. Yeah, the older radeon video cards seem ok. They use radeon.ko, and I presume that amdgpu.ko doesn't interfere.
I have sent an email to Holden, asking if he can test 3.4.3. Holden is very keen on the modern Ryzen PCs, and will be able to test with recent AMD GPUs.
Holden already gave the thumbs-up to an earlier test build with 5.15.16 kernel and lots more amdgpu firmware.
3.4.3 is pretty much the same, except I took out 'aldebaran' AMD firmware, as I think those GPUs are not yet widely released.
Also, 3.4.3 has newer mesa and xorg packages, which are supposed to improve amdgpu compatibility.
Note: esmourguit has just sent me updates for the fr langpack.
Reckon still on track to release 3.4.4 tonight or tomorrow.
Switching wallpapers works now, maybe I was the only one who had problems to keep the different wallpaper
through reboots. Scrollbars on EasyApps are working now.
But now I experience problems with the defaultapp-chooser, the list seems to be incomplete, see screenshot
Just to make sure I checked to see what's in the default apps folder, see below
I was unable to load the red marked apps as text per right-click in Rox, the green ones work.
Not sure what happened?
And one more thing, starting sakura gives me following results. And this just happens without
me typing anything. Started it from the tray icon.
The only changes I made to the system are as follows. Uninstalled Firefox per "Remove Builtin".
Set SeaMonkey as default browser (the above listed problems appeared after those changes).
Changed Wallpaper ... should not be the problem?
Modified .xinitrc, just uncommented the section that keeps the tray to grow bigger than 1440.
Just wanted the tray to go all the way across.
BarryK wrote: Tue Mar 22, 2022 1:14 amscsijon wrote: Sun Mar 20, 2022 10:25 pmBuilt a fresh memory stick, all ok
rebooted it on the workstation and all was ok
however I moved the stick to one of my legacy boxes, and it fails, not even from powerdown works.@scsijon ,
On that legacy box, does it start to boot, and get to the "switch_root"?If so, what GPU does it have?
There may be a problem with some old video cards, as was unable to compile some xorg video drivers
-- some of them are not being maintained, and won't compile with the 21.x xserver.
sorry for the delay, no it doesn't seem to even see the stick and starts up the box.