- This topic has 102 replies, 17 voices, and was last updated Oct 21-12:55 pm by BobC.
-
Posts
-
calciumsodium
Do other themes show the same issue?
papirus-mini-antiX:
on Rox-ICEWM Clearview Blue Medium (default): works
on Rox-ICEWM SunnyDay Medium: works
on Rox-fluxbox: shows that errornumix square antix:
on Rox-ICEWM Clearview Blue Medium: works
on Rox-fluxbox: shows that errorROX:
on Rox-ICEWM Clearview Blue Medium: works
on Rox-fluxbox: shows that error- This reply was modified 1 year, 7 months ago by calciumsodium. Reason: Edit: new test data
olsztyn
on Rox-ICEWM SunnyDay Medium: works
This becomes very interesting…
I just set my environment to (I think) similar to yours: Papyrus-mini-antix Icon theme with Arc-EvoPro2 (which I think you have) widget and with such setting I do get these drop-down menu issues. The only difference I see in environment is that you use ROX-IceWM and I use just strait IceWM.
So in addition to GTK themes, is desktop ROX-IceWM vs. IceWM makes such difference?
Since I never used ROX-IceWM I deleted that desktop (among others) so cannot test to confirm such difference…- This reply was modified 1 year, 7 months ago by olsztyn.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersAnonymous
So themes other than the original default must be ‘imperfect’ as skidoo indicated.
‘imperfect’ would be an inaccurate description.
The GTK project introduced breaking changes across its various 3.xx API versions.
We might generically say “suchandsuch theme suports gkt3″… but, whoops, does it target gtk v3.12, or v3.24 (without the theme author caring to check whether the theme’s behavior gracefully displays when rendered by a lesser version theme engine?Instead of installing//testing NN different themes (and, FWIW, I suspect we can disregard which iconset is used)
you can launch the program from terminal emulator and, in real-time, view the error messages and warning messages spewed by the gtk engine when the program loads. Alternatively, you can inspect the content of the desktop session errorlog.^— The messages are fairly detailed and will let you see details like
“theme states an invalid value for suchandsuch property. ignored.”Someone needs to check dependencies of the (installed from debian stable? oldstable? repository) Chromium browser to determine which 3.xx version of the gtk engine it expects… and investigate which gtk3 versions the pre-installed themes are reputed to gracefully support. Yes, this can be a PITA ~~ try to find the “project page” (often a github project repo) and read the stated README.md… check how recently the theme’s author has updated the files, whether “known bugs” exist (per open issue tickets)… and whether any child forks of the project have incorporated fixes (fixes that have not been merged into the master project).
For many gtk3 themes, the upstream (beyond debian) authors are often, if not usually, ONLY using//testing against higher versioned gtk 3.xx theme engines, compared to the version provided from debian stable repository… so you may need to rely on the debian package maintainers to provide (or not!) fixes for a given debian-packaged theme.
…the issue greatly depends on [the active, aka currently selected] GTK theme
installedA system can have countless themes currently installed
but the theme engine consults only the currently ACTIVE theme (and the global per-user configuration files, e.g. settings.ini)maybe remove the old gtk2-only themes
Please don’t remove them.
antiX is, already, specifying a GTK2+GTK3 -compatible default theme.
Repeated studies have shown {rolleyes} that 97% of users never bother to change the preconfigured default theme…The gtk2 themes continue to work, as expected, as ever. Some of us go out of our way to choose “good ole” gtk2 programs, using gtk2 themes for which no gtk3 equivalent version has ever been created. Example: intentionally installing the (built for use with) gtk2 zzzFM package, and choosing to use NOX theme which provides dense, tightly-packed, space efficient rendering of listview elements and treeview elements.
Thank you skidoo for this in-depth analysis. Greatly appreciated. From your analysis I realize as you point out that review of dependencies is much more methodical approach than just blindly test NN themes to determine which work in such case and which do not.
Would you be so kind to shed some light on this mystery:
Given a selected GTK theme that exhibits the afore mentioned issue in IceWM desktop, when under DWM or Herbstluftwm, instead of IceWM, there is not a trace of this issue. Drop-down menus work perfectly there each time.
Would GTK themes be used differently under those WMs, so the said issue does not exists?
Thanks again for your insight and best regards…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersThank you skidoo for this in-depth analysis. Greatly apprThank you skidoo for this in-depth analysis. Greatly appreciated. From your analysis I realize as you point out that review of dependencies is much more methodical approach than just blindly test NN themes to determine which work in such case and which do not.
Would you be so kind to shed some light on this mystery:
Given a selected GTK theme that exhibits the afore mentioned issue in IceWM desktop, when under DWM or Herbstluftwm, instead of IceWM, there is not a trace of this issue. Drop-down menus work perfectly there each time.eciated. From your analysis I realize as you point out that review of dependencies is much more methodical approach than just blindly test NN themes to determine which work in such case and which do not.
Would you be so kind to shed some light on this mystery:
Given a selected GTK theme that exhibits the afore mentioned issue in IceWM desktop, when under DWM or Herbstluftwm, instead of IceWM, there is not a trace of this issue. Drop-down menus work perfectly there each time.I am not technical in the area of GTK themes but I have no doubt that skidoo’s analysis explains this malfunctioning.
I still fail to understand the following:
– On IceWM the issue with drop-down menus happens when browser is first started – clicking on drop-down menu item is ignored. Upon browser restart drop-down menu items do work. How is this possible? It is using still the same theme… On Fluxbox it is more clear – it never works.
– When using DWM or Herbstluftwm this issue does not happen at all. How come? In my understanding the same GTK theme is used after all…
Thanks again and Regards…- This reply was modified 1 year, 7 months ago by olsztyn.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersI still fail to understand the following:
– On IceWM the issue with drop-down menus happens when browser is first started – clicking on drop-down menu item is ignored. Upon browser restart drop-down menu items do work. How is this possible? It is using still the same theme… On Fluxbox it is more clear – it never works.How come?
I would also like to learn why this is so? I am a user of chromium and chrome and would like to learn why they have this behavior.
Thanks.
namida12
My 1440 monitor is not recognized I get a resolution: 1280×1024
Going to control center> Session> Set Screen Resolution (ARandR) There is only the one resolution 1280×1024 listed. Have never had this problem recently…
$ inxi -F System: Host: antix1 Kernel: 4.9.0-279-antix.1-amd64-smp x86_64 bits: 64 Desktop: IceWM 2.8.0 Distro: antiX-21-b2_x64-full Grup Yorum 6 September 2021 Machine: Type: Desktop Mobo: ASRock model: B450M Pro4 serial: <superuser required> UEFI: American Megatrends v: P3.90 date: 12/09/2019 CPU: Info: Quad Core model: AMD Ryzen 5 3400G with Radeon Vega Graphics bits: 64 type: MT MCP cache: L2: 2 MiB Speed: 1400 MHz min/max: 1400/3700 MHz Core speeds (MHz): 1: 1400 2: 2300 3: 2300 4: 1400 5: 1400 6: 1400 7: 1400 8: 1400 Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Picasso driver: N/A Display: x11 server: X.Org 1.20.11 driver: loaded: N/A unloaded: fbdev resolution: 1280x1024 OpenGL: renderer: llvmpipe (LLVM 11.0.1 256 bits) v: 4.5 Mesa 20.3.5 Audio: Device-1: Advanced Micro Devices [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio driver: snd_hda_intel Device-2: Advanced Micro Devices [AMD] Family 17h HD Audio driver: snd_hda_intel Sound Server-1: ALSA v: k4.9.0-279-antix.1-amd64-smp running: yes Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 IF: eth0 state: up speed: 1000 Mbps duplex: full mac: (removed by user) Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 IF: eth1 state: down mac: a8:a1:59:0d:db:5a Drives: Local Storage: total: 946.42 GiB used: 1.35 GiB (0.1%) ID-1: /dev/nvme0n1 vendor: PNY model: CS2130 1TB SSD size: 931.51 GiB ID-2: /dev/sda type: USB vendor: SanDisk model: Cruzer U size: 14.91 GiB Swap: ID-1: swap-1 type: partition size: 16 GiB used: 0 KiB (0.0%) dev: /dev/nvme0n1p2 Sensors: Message: No sensor data found. Is lm-sensors configured? Info: Processes: 214 Uptime: 28m Memory: 13.63 GiB used: 2.21 GiB (16.2%) Shell: Bash inxi: 3.3.06 demo@antix1:~Running from USB: Maybe because I am using older Kernel with Ryzen CPU? I did not see a way to boot with preferred resolution. Maybe I was blind…
My error, booted with newer kernel resolution is good.
$ inxi -F System: Host: antix1 Kernel: 5.10.57-antix.1-amd64-smp x86_64 bits: 64 Desktop: IceWM 2.7.0 Distro: antiX-21-b2_x64-full Grup Yorum 6 September 2021 Machine: Type: Desktop Mobo: ASRock model: B450M Pro4 serial: <superuser required> UEFI: American Megatrends v: P3.90 date: 12/09/2019 CPU: Info: Quad Core model: AMD Ryzen 5 3400G with Radeon Vega Graphics bits: 64 type: MT MCP cache: L2: 2 MiB Speed: 3056 MHz min/max: 1400/3700 MHz Core speeds (MHz): 1: 3056 2: 3045 3: 3057 4: 3067 5: 1374 6: 3064 7: 3063 8: 3003 Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Picasso driver: amdgpu v: kernel Display: x11 server: X.Org 1.20.11 driver: loaded: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 2560x1440~60Hz OpenGL: renderer: AMD Radeon Vega 11 Graphics (RAVEN DRM 3.40.0 5.10.57-antix.1-amd64-smp LLVM 11.0.1) v: 4.6 Mesa 20.3.5 Audio: Device-1: Advanced Micro Devices [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio driver: snd_hda_intel Device-2: Advanced Micro Devices [AMD] Family 17h HD Audio driver: snd_hda_intel Sound Server-1: ALSA v: k5.10.57-antix.1-amd64-smp running: yes Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 68:1c:a2:13:05:64 Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 IF: eth1 state: down mac: a8:a1:59:0d:db:5a Drives: Local Storage: total: 946.42 GiB used: 1.35 GiB (0.1%) ID-1: /dev/nvme0n1 vendor: PNY model: CS2130 1TB SSD size: 931.51 GiB ID-2: /dev/sda type: USB vendor: SanDisk model: Cruzer U size: 14.91 GiB Swap: ID-1: swap-1 type: partition size: 16 GiB used: 0 KiB (0.0%) dev: /dev/nvme0n1p2 Sensors: System Temperatures: cpu: 42.1 C mobo: N/A gpu: amdgpu temp: 42.0 C Fan Speeds (RPM): N/A Info: Processes: 207 Uptime: 7m Memory: 13.59 GiB used: 1.63 GiB (12.0%) Shell: Bash inxi: 3.3.06 demo@antix1:~JR
- This reply was modified 1 year, 7 months ago by namida12. Reason: added new kernel info
Then I started google-chrome-stable and launched antixforum.com. I found out that the dropdown menu could NOT launch, even though I am able to see them.
Then I closed google-chrome-stable and started it again and launched antixforum.com again.
This time I can launch the items in the dropdown menu.This is exactly how you described.
My testing of this IceWM failure to react on drop-down menus was originally performed using antixforum site. My test report was based on this site.
However now I have done further testing of this malfunctioning with some other sites and unfortunately restarting browser does not help. Just as in Fluxbox, drop-down menus do not seem to work with IceWM as well, no matter restarts of browser. Example to test is Bank of America site. So restarting browser helps on antixforum site but not necessarily on other sites.
Switched session to DWM or Herbstluftwm – drop-down menus work perfectly each time with the same themes.
Now, I wonder… I will try to dig into the past posts in this forum, where such issue was fixed relatively quickly on both Fluxbox and IceWM antiX.
I am not sure we should expect any breaking news from antiX tech team on this as Chrome/Chromium is not provided or supported with with antiX standard edition…
My conclusion is that if someone is using Chrome/Chromium on antiX then IceWM or Fluxbox is out of the picture for now. Only reliable WM is DWM or Herbstluftwm.- This reply was modified 1 year, 6 months ago by olsztyn.
- This reply was modified 1 year, 6 months ago by olsztyn.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters
anticapitalista
What about the shipped JWM?
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
What about the shipped JWM?
I could not quickly test JWM as I had removed WM’s I am not using. I will re-install JWM and test shortly.
Update!!!
Good news… I tested JWM for drop-down menus malfunctioning on both antixforum and Bank of America (not working IceWM and Fluxbox). From brief testing, so far no such issues on JWM. Unlike IceWM and Fluxbox, JWM appears to work perfectly fine even using Adwaita theme.
So now I should add JWM to DWM and Herbstluftwm as working.
Test was very brief, several tries, booting each time straight to JWM but this issue would show by now if JWM was not working. I will continue checking out JWM as an option.- This reply was modified 1 year, 6 months ago by olsztyn.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parametersanticapitalista
BTW it is a chromium/google-chrome problem
See this thread: https://bugs.chromium.org/p/chromium/issues/detail?id=713746
One workaround.
Workaround to run chromium with “–disable-features=SendMouseLeaveEvents”
That’s two dashes and a space before disable
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
Xecure
BTW it is a chromium/google-chrome problem
[…]My guess is that olsztyn already tried this, as it was recommended also by you in the other thread, but for what I understood (in this current thread) it didn’t work, so a different theory was provided.
I saw this on the Internet. Might work, might not. Can you try opening chrome in a terminal with the following.
google-chrome --disable-features=SendMouseLeaveEvents- This reply was modified 1 year, 6 months ago by Xecure.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.@ anticapitalistaa:
OK. So this Chromium problem affects IceWM and Fluxbox but not JWM…
I vaguely recall from the past this drop-down menu issue reported with early antiX 19 and the same link and workaround was posted. This issue was fixed shortly afterwards. So the fix at that time was on Chromium side, not on antiX/IceWM/Fluxbox?
I am not denying this determination. I am just curious. I have been also checking out the same version of Chrome/Chromium on non-antiX Linux and no such drop-down menu issues there.- This reply was modified 1 year, 6 months ago by olsztyn.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters
- You must be logged in to reply to this topic.
