Forum › Forums › Orphaned Posts › antiX-17 “Heather Heyer, Helen Keller” › AntiX 17.3.1 doens't change configuration
- This topic has 20 replies, 6 voices, and was last updated Mar 4-4:21 pm by Anonymous.
-
AuthorPosts
-
March 3, 2019 at 6:01 am #19007Member
aledosim
Hello all.
I’ve been using AntiX for music production for about 3 month now. Recently I installed the version 17.3.1. Initially I couldn’t edit the personal menu at Fluxbox with the menu editor. Posted a thread at LinuxQuestions.org (https://www.linuxquestions.org/questions/antix-mx-linux-127/personal-menu-doesnt-change-4175648986/). Then I tried to change the keyboard shortcuts but just the default ones works. I think there are something wrong with the update of these configurations, since I can edit the theme and the behavior of the taskbar.
Any help is appreciated.
Thanks.March 3, 2019 at 7:32 am #19011Forum Admin
rokytnji
::Seems like a bug to me.
Nope. At least I don’t think so. Could be wrong as usual though. Looks like your answer was posted by Anti and D.O. in that LQ thread. All I can add is sometimes I see new linux users don’t md5sum check their downloaded isos for file integrity first. I have personally seen a browser down-loader only give a partial iso download. But in file manager it, < iso file > looks complete with a icon.
Howdy and Welcome.
Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.Linux Registered User # 475019
How to Search for AntiX solutions to your problemsMarch 3, 2019 at 7:37 am #19012Forum Admin
rokytnji
::Plus. Forgot to mention. You should have said yes when asked about changing config on /etc/skel stuff on this latest update.
Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.Linux Registered User # 475019
How to Search for AntiX solutions to your problemsMarch 3, 2019 at 9:51 am #19013Anonymous
::Since I can think, I have always used only fluxbox with antiX. That may have been a coincidence at the time, but I just thought it was cool.
However, I confess that I never really used the GUI’s offered in antiXCC. I love working with the terminal or the files directly.
Actually I only copied the principle. That’s how I created this template for the personal menu, which I use again and again and, with a right click, I can immediately see if I did it right.
antiX-personal[exec] (Thunar) {thunar } </usr/share/icons/hicolor/48x48/apps/Thunar.png> [exec] (Opera beta) {opera-beta } </usr/share/icons/hicolor/128x128/apps/opera-beta.png> [exec] (Claws Mail) {claws-mail } </usr/share/pixmaps/claws-mail.png> [exec] (ROXTerm) {roxterm} </usr/share/pixmaps/roxterm.xpm> [exec] (Leafpad) {leafpad } </usr/share/icons/hicolor/32x32/apps/leafpad.png> [exec] (Mirage) {mirage } </usr/share/pixmaps/mirage.png> [exec] (xmms) {xmms} </usr/share/icons/xmms.png> [exec] (GNOME MPlayer) {gnome-mplayer } </usr/share/icons/hicolor/32x32/apps/gnome-mplayer.png> [separator]March 3, 2019 at 9:52 am #19014Anonymous
::As a troubleshhoting step, switch to icewm session and determine whether its menu is also affected (or the problem exists only withing the fluxbox menu).Maybe you have edited something “AsRoot” and now your normal user lacks read/write permission for one or more files in your home directory. To check:cd ~ && find . -user rootAnother troubleshooting step would be to diff the contents of:
/etc/skel/.fluxbox/menu
~/.fluxbox/menu
and
/etc/skel/.fluxbox/personal
~/.fluxbox/personal
to check whether a syntax error has crept in during editing===========================
I just tested a fully updated antiX17.3.1 and found
yes, there’s a bug.
It’s the same bug reported/fixed a year ago, so apparently an older version of
/usr/local/bin/menu_manager.sh or /usr/local/bin/menu_manager_personal.sh
was added into the menu-manager-antix package
To see the error output, launch from a terminal prompt:
/usr/local/bin/menu_manager.shMarch 3, 2019 at 10:35 am #19019Member
aledosim
::sha256sum Downloads/antiX-17.3.1_x64-base.iso | grep dbd997f470c6ac68db720392e8d51746d40d3b1c5cc3da1e6c84a0e7f66d43b7 dbd997f470c6ac68db720392e8d51746d40d3b1c5cc3da1e6c84a0e7f66d43b7 Downloads/antiX-17.3.1_x64-base.isoMy iso is OK.
- This reply was modified 4 years, 2 months ago by aledosim.
- This reply was modified 4 years, 2 months ago by aledosim.
March 3, 2019 at 11:41 am #19025Member
aledosim
March 3, 2019 at 1:46 pm #19030Forum Admin
anticapitalista
::I’ll have time tomorrow to fix this bug.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
March 4, 2019 at 11:15 am #19073Forum Admin
anticapitalista
::Is it only an error via control centre?
Typing sudo /usr/local/bin/menu_manager.sh works
Running app from the menu works
Can anyone confirm?
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
March 4, 2019 at 11:43 am #19078Anonymous
::clarifying what I had tested, in virtualbox:
pristine antiX-17.3.1_x64-full.iso ( but /etc/lsb-release states DISTRIB_DESCRIPTION=”antiX 17.2.1″ )from terminal:
/usr/local/bin/menu_manager.shThe app launches and, upon clicking “Personal”, the terminnal output shows
mkdir: cannot create directory ‘/home//.local'” Permission denied
chown: cannot access ‘/home//.local/share/applications/TCM’: No such file or directoryThe app allows us to continue.
Click “Add”, choose an item to add, and upon clicking “OK”, terminal output shows
/usr/local/bin/menu_manager_personal.sh: line 483: /home//.local/share/applications/TCM…
… filenameofselecteditem.desktop: No such file or directory
chown: cannot access… no such file or directoryFWIW, identical result with the as-shipped ISO… and after apt full-upgrade has been performed
Running app from the menu works
aha, previously I hadn’t found a desktop menu item for “Menu Manager”.
Rechecking today, I found it (Preferences) submenu, but only after choosing a “small” theme variant.
With default theme, that item and quite a few others (SystemTools) were displaying offscreen
and “scroll to see more” (seriously, not sarcasm) didn’t occur to me.^———- Yes, launched from the desktop menu, “Menu Manager” is working properly.
(note: full-upgrade has been performed. I haven’t retested this booting from as-shipped ISO)
Also tested today, launching “Menu Manager” via ControlCenter and that too is working properly.March 4, 2019 at 11:49 am #19079Forum Admin
anticapitalista
::skidoo – app must be run as sudo from terminal
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
March 4, 2019 at 11:52 am #19080Moderator
caprea
::Yes,
sudo /usr/local/bin/menu_manager.sh
worksbut gksu /usr/local/bin/menu_manager.sh
doesn’tI’m not on antix 17.3 in time so I can’t remember the right term, anyway in antix-control-center.sh
is used gksu for menu-manager.March 4, 2019 at 12:37 pm #19083Forum Admin
rokytnji
::Mine is okay.
gksu /usr/local/bin/menu_manager.sh
What do you want me to test? This install started as version 17.1 I think originally. Fully updated stretch version right now.
Edit: launching from menu> control cemtre > menu editor > works ok here also.
Like Male. I cheat also sometimes with saved text files. Like my quick launch arrow on the taskbar. I keep cheat files in my free pastebin account.
- This reply was modified 4 years, 2 months ago by rokytnji.
- This reply was modified 4 years, 2 months ago by rokytnji.
Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.Linux Registered User # 475019
How to Search for AntiX solutions to your problemsMarch 4, 2019 at 12:44 pm #19085Moderator
caprea
::Roky, yes it runs and there are even no errors shown, but did you try to add an entry ?
March 4, 2019 at 12:45 pm #19086Anonymous
::skidoo – app must be run as sudo from terminal
So put it to rest, as “not a bug”?
Seems odd to require elevated permissions to edit one’s home -pathed menu files
and
odd (compared to the other antiX utils) that it doesn’t check/prompt/exit advising the user to relaunch using sudocaprea, it would not have occurred to me to use “gksu” to launch a shell script…
…but (OMG) the launchstring provided by antixcc.sh is, in fact, “gksu menu_manager.sh”Behind-the-scenes, the commandstring passed through gksu would be:
sudo -H -S -u root –– /usr/local/bin/menu_manager.shHow that same commandstring succeeds via antixcc, yet fails from within lxterminal… idunno
-
AuthorPosts
- You must be logged in to reply to this topic.
