GTK BL-Lithium and hardinfo don't get on

johnraff · 2021-11-25 06:25:44

This looks like a bug in hardinfo, but I wondered if just possibly there might be a tweak to our Lithium themes that could work around it.

On a BL Lithium system:
Using BL-Lithium, BL-Lithium-light or BL-Fever_Room GTK themes, when launching hardinfo:
A smallish blank window opens in front of the (blank) main window. Close the small window and the app springs into life as normal.

Using any other GTK theme (including Yeti and the older BL themes) it works OK.

On a Beryllium system:
Using BL-Lithium, BL-Lithium-light or BL-Fever_Room GTK themes, hardinfo crashes. If launched in a terminal the message "Aborted" is shown. Again, the other themes are all OK.

BUT, on Be, if launched with eg:

GTK2_RC_FILES=/usr/share/themes/BL-Lithium/gtk-2.0/gtkrc hardinfo

it reverts to the Lithium behaviour, ie blank window in front. You can switch themes like this too. (From this I also learned that hardinfo is a GTK2 app.) If nothing else, that gives us a way to workaround in the menu if there's no easy fix for the theme files.

Related issue with ArcDarkest theme:
https://github.com/lpereira/hardinfo/issues/468

And a hint about why that blank window pops up:
https://github.com/lpereira/hardinfo/is … -932801356

So, we know it's probably only in the GTK2 files, and only in the above three themes. @hhh any chance of a tweak?

hhh · 2021-11-25 20:41:09

johnraff wrote:

So, we know it's probably only in the GTK2 files, and only in the above three themes. @hhh any chance of a tweak?

Not just those 3 themes, I just checked with my current theme and can confirm the "Aborted" crash. Tested with one of my old themes, Crocus-Remix, it worked perfectly.

Shit, I don't know. Oomox screwing it up? It's going to take some dirty research to figure it out, I suspect.

johnraff · 2021-11-26 01:57:50

If there isn't an easy tweak for the gtk2 themes, and no other package seems to be affected, then maybe we're better off focussing on hardinfo.

1) First off, the developer lpereira has put up a testing deb on Launchpad based off git at 20200612:
https://launchpad.net/~lafp/+archive/ub … /+packages
The .deb is marked "ubuntu" but I just test installed it on my Be VM. No dependency issues came up.

The "Aborted" crash is gone, but the blank-window thing remains, as on BL Lithium. We could possibly live with that.

2) As suggested, we could try building off the latest git., do you feel like trying that? Development on hardinfo continues, with plenty of commits in recent weeks, so if the gtk issue is fixed completely there we could ship that version.

3) Hardinfo is an easy to use GUI that new users might like, but we now also have the inxi terminal command in our BL menu, and the exhaustively complete hw-probe will be available in our "Install Favourite Packages" sub-menu, so just dropping hardinfo is another option.

hhh · 2021-11-26 04:20:30

Let me meld the GTK2 rc files and see if I can spot an obvious difference.

johnraff · 2021-12-17 08:00:33

johnraff wrote:

Hardinfo is an easy to use GUI that new users might like, but we now also have the inxi terminal command in our BL menu, and the exhaustively complete hw-probe will be available in our "Install Favourite Packages" sub-menu, so just dropping hardinfo is another option.

How about taking this route? Time isn't on our side at this point.

hhh · 2021-12-18 01:14:50

Sorry for the delayed response. Meld showed no difference in the rc files for GTK2 between Arc-Dark, Arc-Darker nor Arc (hardinfo works) and BL-Lithium built off of Arc using oomox (hardinfo aborts with no message) except for colors and me commenting out 3 of the rc files at the bottom of gtkrc in Lithium. Un-commenting those files changed nothing.

Proceeded to swapping the image files (assets and menu-toolbar) from Lithium for the Arc ones, presto! It's not the menutoolbar folder, since that is commented out in Lithium, so it's the assets.

So oomox is screwing with those images, I'm guessing. Next step is for me to hand-edit the 33 colored Arc png files in assets to Lithium colors and see if that works. Crikey, life is never easy, is it?

Last edited by hhh (2021-12-18 01:18:03)

hhh · 2021-12-18 02:33:01

I;m onto something. Remove the gtk2/assets folder, hardinfo opens with error messages about the missing images. There are missing files in the Lithium assets folder. Why this worked with the old themes? Different oomox version using an older Arc theme as it's base? Anyways, still testing...

hhh · 2021-12-18 03:04:05

I'm pretty sure I found it. I didn't have to edit any image files, just copy/paste row-by-row till I found the culprit (still a PITA). Test this please...

Copy gtk-2.0/assets/frame.png from a working theme (say, Arc-Dark) to a broken theme (say, BL-Lithium), profit...

You can see the frame images are different if you preview them, and you can see it in lxappearance too, a half-border thing around the Demo box.

I'm already editing the GTK2 rc file that Oomox puts out, it has the wrong highlight foreground color and the tooltip colors are reversed compared to the GTK3 theme, copying over one image file as well is no problem, assuming I'm right about this being the fix. Almost 2 hours to find one tiny broken image file, please let me be right.

Last edited by hhh (2021-12-18 03:11:39)

johnraff · 2021-12-18 05:38:16

^go hhh!
Sounds like you're onto it, and we'll be able to ship hardinfo after all.
(not to mention avoiding some possible future issues we haven't found yet)

---
right now Beryllium has a menu entry "Quick System Info" running 'inxi -Fxrz', the output of which is somewhat similar to what you posted, plus/minus a few details. We could easily change it pre-release though.

hhh · 2021-12-18 08:15:53

^ right, like me now noticing that the dark themes don't have visible outlines around check boxes in Conky Manager again. I fixed that before though, IIRC, so some more trial and error with Oomox should do it.

hhh · 2021-12-18 09:52:42

Right, a simple border-color fix in Oomox. I have time this weekend, I'll upload the updated BL-Lithium themes to GitHub and hopefully add a few more.

rbh · 2021-12-18 11:25:50

nobody wrote:

I'd one-up inxi; the output is very tweakable.
inxi -F -d -f -i -J -l -m -o -p -t -u -x
or is it too much?

No, do not think it is to much. But, add -z, to filter out sensitive info, is good

Last edited by rbh (2021-12-18 11:26:08)

johnraff · 2021-12-19 06:42:52

Talking here about the best output for the popup terminal from the "Quick System Info" menu item:

Let's keep the currently proposed -r , for the repo info.

And possibly drop:
-f ? How important is that long list of CPU flags?
-i ? With -z the ip addresses are sanitized, so little use.
-m ? Without running as root, shows no extra info over what appears with -F anyway.
-t ? List of running processes: a bit bulky?

So that would boil down to:

inxi -F -d -J -l -o -p -r -t -u -x -z

???

johnraff · 2021-12-20 09:21:37

hhh wrote:

Right, a simple border-color fix in Oomox. I have time this weekend, I'll upload the updated BL-Lithium themes to GitHub and hopefully add a few more.

I've just been playing with Be-Penguin{,-light} on Lithium and Beryllium and:

1) Hardinfo's "aborted" crash on Be has gone away, even using the current BL-Lithium theme!! Hardinfo hasn't had any updates - maybe it's a GTK library?
2) The anonymous-window-in-front issue remains though, for Lithium Penguin and Fever. That's livable because the user can just close it to see the hardinfo window, but annoying.
3) Yeti doesn't have the issue, and its colour scheme looks sort of compatible with where Beryllium seems to be going. Consider tweaking Yeti as our Beryllium theme?
4) Bunsen-themes/themes/ now has some unwanted directories: assets gtk-2.0 gtk-3.0 Did they get unintentionally uploaded?
5) Personal opinion: Be-Penguin is very purple. Desaturate a bit if we stay with this? Bit darker? Bit bluer? Maybe the dark areas are OK, just the light parts need attention? (But Yeti...)

Last edited by johnraff (2021-12-20 09:23:27)

rbh · 2021-12-20 12:26:18

johnraff wrote:

Let's keep the currently proposed -r , for the repo info.

I don't think anyone disagree with that. Just think 'nobody' forgot it...

And possibly drop:
-f ? How important is that long list of CPU flags?
-i ? With -z the ip addresses are sanitized, so little use.
-m ? Without running as root, shows no extra info over what appears with -F anyway.
-t ? List of running processes: a bit bulky?

You suggest to drop from <webmaster>'s proposal... Agree, but maybe keep -m, but set sudo-rights?

So that would boil down to:
-F -d -J -l -o -p -r -t -u -x -z

Or "-F -d -J -l -o -p -r -u -x -z", without -m and -t

johnraff · 2021-12-21 05:33:44

rbh wrote:

johnraff wrote:
Let's keep the currently proposed -r , for the repo info.
I don't think anyone disagree with that. Just think 'nobody' forgot it...

OK

And possibly drop:
-f ? How important is that long list of CPU flags?
-i ? With -z the ip addresses are sanitized, so little use.
-m ? Without running as root, shows no extra info over what appears with -F anyway.
-t ? List of running processes: a bit bulky?
You suggest to drop from the original proposal... Agree, but maybe keep -m, but set sudo-rights?

-m running under sudo produces, for me, the following extra data:

  Array-1: capacity: 32 GiB slots: 4 EC: None 
  Device-1: DIMM4 size: 2 GiB speed: 1600 MT/s 
  Device-2: DIMM3 size: 2 GiB speed: 1600 MT/s 
  Device-3: DIMM2 size: 2 GiB speed: 1600 MT/s 
  Device-4: DIMM1 size: 2 GiB speed: 1600 MT/s

But running inxi with sudo would require the user to enter a password every time, for an output with only a little extra info. Maybe keep that for support cases when people have RAM issues?

So that would boil down to:
-F -d -J -l -o -p -r -t -u -x -z
Or "-F -d -J -l -o -p -r -u -x -z", without -m and -t

Thanks! I meant to remove the -t.

Last edited by johnraff (2024-04-21 05:11:25)

brontosaurusrex · 2021-12-21 09:33:47

Personally I'd probably remove the colorization (-c 0), otherwise

inxi -F -d -J -l -o -p -r -t -u -x -z -c 0

looks good imho.

johnraff · 2021-12-26 02:23:19

brontosaurusrex wrote:

Personally I'd probably remove the colorization (-c 0)

Other opinions?

hhh · 2021-12-26 02:42:05

^ I was actually going to comment that I prefer that (colorization option removed). It's a little less monochrome.

johnraff · 2021-12-26 07:09:03

Personally, I find it easier to read when the titles and content are different colours.

#1 2021-11-25 06:25:44

GTK BL-Lithium and hardinfo don't get on

#2 2021-11-25 20:41:09

Re: GTK BL-Lithium and hardinfo don't get on

#3 2021-11-26 01:57:50

Re: GTK BL-Lithium and hardinfo don't get on

#4 2021-11-26 04:20:30

Re: GTK BL-Lithium and hardinfo don't get on

#5 2021-12-17 08:00:33

Re: GTK BL-Lithium and hardinfo don't get on

#6 2021-12-18 01:14:50

Re: GTK BL-Lithium and hardinfo don't get on

#7 2021-12-18 02:33:01

Re: GTK BL-Lithium and hardinfo don't get on

#8 2021-12-18 03:04:05

Re: GTK BL-Lithium and hardinfo don't get on

#9 2021-12-18 05:38:16

Re: GTK BL-Lithium and hardinfo don't get on

#10 2021-12-18 08:15:53

Re: GTK BL-Lithium and hardinfo don't get on

#11 2021-12-18 09:52:42

Re: GTK BL-Lithium and hardinfo don't get on

#12 2021-12-18 11:25:50

Re: GTK BL-Lithium and hardinfo don't get on

#13 2021-12-19 06:42:52

Re: GTK BL-Lithium and hardinfo don't get on

#14 2021-12-20 09:21:37

Re: GTK BL-Lithium and hardinfo don't get on

#15 2021-12-20 12:26:18

Re: GTK BL-Lithium and hardinfo don't get on

#16 2021-12-21 05:33:44

Re: GTK BL-Lithium and hardinfo don't get on

#17 2021-12-21 09:33:47

Re: GTK BL-Lithium and hardinfo don't get on

#18 2021-12-26 02:23:19

Re: GTK BL-Lithium and hardinfo don't get on

#19 2021-12-26 02:42:05

Re: GTK BL-Lithium and hardinfo don't get on

#20 2021-12-26 07:09:03

Re: GTK BL-Lithium and hardinfo don't get on

Board footer