Forum › Forums › Orphaned Posts › antiX-17 “Heather Heyer, Helen Keller” › Sceen blanking and preferred app setting issues
Tagged: preferredapplications
- This topic has 4 replies, 4 voices, and was last updated Dec 9-6:58 pm by Anonymous.
-
AuthorPosts
-
September 29, 2018 at 4:32 am #12257Member
movomo
Hi, all. I very recently installed antiX 17.1 on an ancient machine and so far generally satisfied, though with occasional hiccups.
I’m actually not entirely certain if this post is a bug report or a technical problem that I need a help with, but let me describe the problems anyway.
The first one is that I can’t seem to configure screen blank time through control panel. As seen in the screenshot(attached), the ui looks a bit out of order. At first I thought the time value (default 60 min) was a text input box, but I could not click on it or type any number into it.
So I examined the /usr/local/bin/set-screen-blank code. I am no programmer, but my short python knowledge led me to believe that the ui compoment for this was in fact intended to be a slider. I tried randomly clicking around the visible number, dragging it to see if that changes the value. But I could not manipulate the slider in any way. In the end I had to edit the config file manually. The screenshot was taken after that.
Note, the on/off buttons above are working fine, even though kinda-sorta invisible.
—-
The second problem is with the Control Centre -> Desktop -> Preferred Applications script. BTW this script’s ui is a bit puta too; so I’m almost starting to suspect that my gtk packages are broken for whatever unfathomable reason, in which case I could use some help, but that’s another story.
I discovered that the /usr/local/bin/desktop-defaults-set script fails when the existing default program link is broken. They are displayed as ‘None’, and can be set through the file dialog. But once I get back to Control Centre and run the script again, previously set default programs (that were None) are gone again. I needed to modify the script,
MakeLinks() { LinkFrom=$(echo $app_info |cut -d "|" -f"$1") LinkTo=$Desktop_Prefix"$2" # if [ -f "$LinkTo" ]; then if [ -L "$LinkTo" ]; then rm $LinkTo fi ln -s $LinkFrom $LinkTo 2>/dev/null UpdateMime $LinkFrom }such that it would purge the existing link even if it’s pointing to nothing. But I’m sure you guys would fix it whatever safe way.
That’s the end!
Movomo
- This topic was modified 4 years, 7 months ago by movomo.
Attachments:
September 29, 2018 at 6:51 am #12260Forum Admin
anticapitalista
::Try changing the theme (fluxbox?) to see if it has caused the missing slider.
Are you running full or base?Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
September 29, 2018 at 7:25 am #12263Membermovomo
::My installation is antiX base and space-fluxbox. Tested just now and it doesn’t work for all 3 wm’s: icewm, jwm, fluxbox, none of them, reboot or not, but this gave me motivation to cycle through graphic themes.
So… good news, it seems like some faulty gtk themes were causing it. So I found 2 themes not working:
Mediterranean~ series
RaleighAll others seem to work. Above 2 render several settings-related dialogs hideously.
December 9, 2018 at 4:55 pm #14101Membersimon
::@movomo
Thank you so mcuh for that script! I recently installed antiX on a PII with only 280mb ram and quickly found that Firefox woudln’t run and thus uninstalled it. This resulted in the error you describe where the deafault browser was set to “none” and could not be updated to Dillow via the “prferred applications” app in the control ceneter.
Your suggested edit to the script has fixed the issue instantly. Thank you so much! I really hope this gets noticed by the devs and added to the default install because this is quite an annoying bug to not be able to change the default program if you happen to uninstall it!
December 9, 2018 at 6:58 pm #14109Anonymous
::added to the default install
in this case, maybe “subtracted” is the fix
~~ as in, when building the iso… after the themes packages have installed within the buildroot, rm the poorly performing themes?MediterraneanNight
Apparently, that theme package is no longer maintained (receives no bugfixes) upstream.
Also, the names of the individual themes are ridiculously long and are light-dark-white-night counterintuitive.
Also, that package provides theme variants for “Unity” DE (useless for antiX users).MissTell and others have expressed an interest toward “prettying up” the pre-installed themes.
If someone is interested in maintaining a custom themes package, I would handle steps 1-6 below to get the ball rolling1) fork this repository: https://github.com/rbrito/mediterranean-gtk-themes
2) cherrypick 2 commits from here: https://github.com/Dvad/pkg-mediterranean-gtk-themes
3) cherrypick 4 commits from here: https://github.com/dodev/pkg-mediterranean-gtk-themes/commits/master
4) check this pull request: https://github.com/rbrito/mediterranean-gtk-themes/pulls
5) investigate which specific theme variants have “known issues” https://github.com/rbrito/mediterranean-gtk-themes/issues
6) prune the Unity-specific themefiles from the package
7) fix (or prune) and/or tweak the remaining themes, renaming each to a less ridiculous name along the way.
8) add a few more curated/tweaked themes into the package
9) distribute via a new deb package (and ??? mark it as provides/conflicts(?)replaces the package which provides the pre-existing meDiterAnEaNnIghT themes?) -
AuthorPosts
- You must be logged in to reply to this topic.
