- This topic has 203 replies, 24 voices, and was last updated Jul 7-11:37 am by Anonymous.
-
Posts
-
Anonymous
antiX still complains whenever I try copying from VM to a file share.
It shows error where there is no one.And …
Moving the files around over the Terminal, still produces some crazy users and groups.
antiX still complains whenever I try copying from VM to a file share.
no problems when using spacefm but, yes, I tested rox-filer and met the same “One error”
rox-filer AsRoot
attempt to copy some file into /media/shar_sf/a squished screenshot of the current virtualbox Shared Storage settings:
NOTED: within the antiX19b1 virtualbox instance, user “demo” is not a member of “vboxsf” group.
To add, via GUI:
For me, the above change was sufficient to fix the “unexpected” behavior (which I wouldn’t have noticed unless using rox-filer), but I do not wish to grant SharedFolder access to non-root-permissioned users//processes. If you do, the additional step is to chmod /media/shar_sf/
PPC
@ dev team: It seems that still (like in A2) trying to activate the firewall blocks all internet access?
@ dev team: not any more “bugs” just some very small suggestions…
-About quick launch icons- I believe that in a previous version (maybe b1 and b2, I’m not sure) IceWM came OOTB with many quick launch icons in it’s toolbar. Now it comes with the “eject USB device” icon only.
Just for commodity, not only for newbies but also for long time users, at least having quick launchers in the toolbar for the file manager and the internet browser, as well as the already provided “eject USB device” on both IceWM and JWM (the default antiX Fluxbox desktop can provide a start menu “icon” -kind of- but not quick launchers on it’s toolbar, so no need mentioning it).
Also the “show desktop” icon could be enabled on JWM too (and it would be less confusing for newbies if the start menu saying “Menu” and not “antiX”, just to have a bit more coherence between desktops).
Some icons that may be worth having in the toolbar by default include “terminal” and even “Exit”, but that may overcrowd the toolbar a bit.@ dev team: another suggestion I believe I already made in another thread:- antiX comes without any GUI calendar or a gui way to search for applications (other than the menu)- but it comes out of the box with yad (providing “yad –calendar” and dmenu, that can easily, in a script with only a single line, be configured to search and run most installed applications (with some exceptions, like synaptic- that does not run with the needed authorizations, etc.). Also a Gui way to see almost all installed applications by icon, is provided out of the box with yad (a menu entry like “All Applications” that fired up something like ” yad –icons –read-dir=/usr/share/applications –fullscreen –sort-by-name –undecorated –single-click –skip-taskbar” (I “stole” that from https://forums.bunsenlabs.org/viewtopic.php?id=1978&p=4) would be a nice feature, once again adding zero bloat to the OS, and offering a feature most modern OS usually provide.
No bloat, just easy ways to access options that are already available and the “normal” user does not know about (took me well over a year to find about them).
I added, in JWM, a “feature”- I click the clock and a GUI calendar window pops up. Hey, if I add a text file with dates and events and add a button to “yad –calendar” to open the date text file in the default text editor, it also acts as a kind of very simple agenda/events calendar (without, unfortunatetly, any alarm function- you just click the day and see the scheduled events).– I’ve been following (and even participating) in the forum threads about “modernizing” antiX’s looks. antiX is quite ok as it is now. Yes, it’s almost as light on resources as it can be and still be a full fledged OS, That’s why I started using antiX… But, even is your daily driver is Herb…’s without a desktop wallpaper, you understand even people with very few system resources like having a little bit of “eye candy”- in my case, I like having some quick launch icons on the bar, but do fine without desktop icons and volume icon on the bar. Also I almost never look at my desktop wallpaper, but mostly I like to have one that matches my color scheme, or a family picture, even if that one does not match with the rest :-).
@ not newbie users:
– One can have a way more “modern” looking desktop without installing anything an adding bloat to the OS. Users can test this: for example, start antiX using JWM desktop. Edit JWM’s settings, adding a file manager and a internet browser quick launchers to the tool bar (copy and past the relevant entries from the menu file). Select the “black” JWM theme. Select the “back” wallpaper and restart JWM. There. A way more stylish desktop, using the same system resources ( I believe adding 2 icons to the toolbar has no meaningful impact, right?). If you want antiX to look “flater” and Darker (that it’s all the rage right now) and you don’t mind a bit of extra work, you can even download one of the very good wallpaper’s available in the forum and set it as your default wallpaper, from the Control Centre. The same goes if you want to use a different “icon” as a start menu- there are loads of good ones in the forum, and also some very good icons already provided out of the box as part of antiX icons themes.
I did some of this myself, but I realize it’s not that “easy” to a newbie, even less if he/she is a windows refugee- you do have to know where to look, how to edit the desktop settings, it’s not all done via GUI like in other OS’s. It’s not very hard, but is has a learning curve, it’s not mostly point and click…P.
- This reply was modified 3 years, 10 months ago by PPC.
model99
I have found two issues using antiX-19.b1_x64-full as a live USB device.
Both of these issues have already been mentioned in this thread, but I have additional information that may be useful.
The issues:
– Connman not working initially
– UFW firewall does not enable properlyFirst, here is some information about my 12 year old laptop computer:
System: Host: antix1 Kernel: 4.9.176-antix.1-amd64-smp x86_64 bits: 64 Desktop: IceWM 1.5.5+git20190610 Distro: antiX-19.b1_x64-full Marielle Franco 12 June 2019 Machine: Type: Portable System: Gateway product: MT6451 v: 3408447R Mobo: Gateway model: N/A v: 84.05 serial: <root required> BIOS: Phoenix v: 84.05 date: 11/01/2006 CPU: Dual Core: AMD Turion 64 X2 Mobile TL-50 type: MCP speed: 800 MHz min/max: 800/1600 MHz Graphics: Device-1: AMD RS482M [Mobility Radeon Xpress 200] driver: radeon v: kernel Display: x11 server: X.Org 1.20.4 driver: ati,radeon unloaded: fbdev,modesetting,vesa resolution: 1280x800~60Hz OpenGL: renderer: ATI RS480 v: 2.1 Mesa 18.3.6 Network: Device-1: Marvell 88E8038 PCI-E Fast Ethernet driver: sky2 Device-2: Broadcom Limited BCM4311 802.11b/g WLAN driver: b43-pci-bridgeConnman does not initially work. When you click on the wireless icon in Connman and then click to enable it, it does not show any access points to select.
But if you toggle the “connmand” daemon with a command like:$ sudo kill $(ps -C connmand -o pid=); sudo connmandit will start working, shows access points and is successful in making a wifi connection.
The second issue is with the firewall (UFW) being unable to be enabled.
Here is the output from trying to enable the firewall:demo@antix1:~ $ sudo ufw enable ERROR: problem running ufw-init iptables-restore v1.8.2 (nf_tables): unknown option "--icmp-type" Error occurred at line: 34 Try iptables-restore -h' or 'iptables-restore --help' for more information. ip6tables-restore v1.8.2 (nf_tables): unknown option "--icmpv6-type" Error occurred at line: 36 Try ip6tables-restore -h' or 'ip6tables-restore --help' for more information. Problem running '/etc/ufw/before.rules' Problem running '/etc/ufw/before6.rules'Here is some additional diagnostic information using the check-requirements utility from the ufw folder.
demo@antix1:/usr/share/ufw $ sudo ./check-requirements Has python: pass (binary: python2.7, version: 2.7.16, py2) Has iptables: pass Has ip6tables: pass Has /proc/net/dev: pass Has /proc/net/if_inet6: pass This script will now attempt to create various rules using the iptables and ip6tables commands. This may result in module autoloading (eg, for IPv6). Proceed with checks (Y/n)? y == IPv4 == Creating 'ufw-check-requirements'... done Inserting RETURN at top of 'ufw-check-requirements'... done TCP: pass UDP: pass destination port: pass source port: pass ACCEPT: pass DROP: pass REJECT: pass LOG: pass hashlimit: pass limit: pass ctstate (NEW): pass ctstate (RELATED): pass ctstate (ESTABLISHED): pass ctstate (INVALID): pass ctstate (new, recent set): pass ctstate (new, recent update): pass ctstate (new, limit): pass interface (input): pass interface (output): pass multiport: pass comment: pass addrtype (LOCAL): pass addrtype (MULTICAST): pass addrtype (BROADCAST): pass icmp (destination-unreachable): FAIL error was: iptables v1.8.2 (nf_tables): unknown option "--icmp-type" Try iptables -h' or 'iptables --help' for more information. icmp (source-quench): FAIL error was: iptables v1.8.2 (nf_tables): unknown option "--icmp-type" Try iptables -h' or 'iptables --help' for more information. icmp (time-exceeded): FAIL error was: iptables v1.8.2 (nf_tables): unknown option "--icmp-type" Try iptables -h' or 'iptables --help' for more information. icmp (parameter-problem): FAIL error was: iptables v1.8.2 (nf_tables): unknown option "--icmp-type" Try iptables -h' or 'iptables --help' for more information. icmp (echo-request): FAIL error was: iptables v1.8.2 (nf_tables): unknown option "--icmp-type" Try iptables -h' or 'iptables --help' for more information. == IPv6 == Creating 'ufw-check-requirements6'... done Inserting RETURN at top of 'ufw-check-requirements6'... done TCP: pass UDP: pass destination port: pass source port: pass ACCEPT: pass DROP: pass REJECT: pass LOG: pass hashlimit: pass limit: pass ctstate (NEW): pass ctstate (RELATED): pass ctstate (ESTABLISHED): pass ctstate (INVALID): pass ctstate (new, recent set): pass ctstate (new, recent update): pass ctstate (new, limit): pass interface (input): pass interface (output): pass multiport: pass comment: pass icmpv6 (destination-unreachable): FAIL error was: ip6tables v1.8.2 (nf_tables): unknown option "--icmpv6-type" Try ip6tables -h' or 'ip6tables --help' for more information. icmpv6 (packet-too-big): FAIL error was: ip6tables v1.8.2 (nf_tables): unknown option "--icmpv6-type" Try ip6tables -h' or 'ip6tables --help' for more information. icmpv6 (time-exceeded): FAIL error was: ip6tables v1.8.2 (nf_tables): unknown option "--icmpv6-type" Try ip6tables -h' or 'ip6tables --help' for more information. icmpv6 (parameter-problem): FAIL error was: ip6tables v1.8.2 (nf_tables): unknown option "--icmpv6-type" Try ip6tables -h' or 'ip6tables --help' for more information. icmpv6 (echo-request): FAIL error was: ip6tables v1.8.2 (nf_tables): unknown option "--icmpv6-type" Try ip6tables -h' or 'ip6tables --help' for more information. icmpv6 with hl (neighbor-solicitation): FAIL error was: ip6tables v1.8.2 (nf_tables): unknown option "--icmpv6-type" Try ip6tables -h' or 'ip6tables --help' for more information. icmpv6 with hl (neighbor-advertisement): FAIL error was: ip6tables v1.8.2 (nf_tables): unknown option "--icmpv6-type" Try ip6tables -h' or 'ip6tables --help' for more information. icmpv6 with hl (router-solicitation): FAIL error was: ip6tables v1.8.2 (nf_tables): unknown option "--icmpv6-type" Try ip6tables -h' or 'ip6tables --help' for more information. icmpv6 with hl (router-advertisement): FAIL error was: ip6tables v1.8.2 (nf_tables): unknown option "--icmpv6-type" Try ip6tables -h' or 'ip6tables --help' for more information. ipv6 rt: pass FAIL: check your kernel and that you have iptables >= 1.4.0Looks like a problem with the kernel.
- This reply was modified 3 years, 10 months ago by model99. Reason: fix formatting
- This reply was modified 3 years, 10 months ago by model99.
@Model99
” sudo kill $(ps -C connmand -o pid=); sudo connmand` ”
Thanks for sharing that workaround. I’ll change my “connman” quick launch icon accordingly and try that out when I have the chance!
P.
- This reply was modified 3 years, 10 months ago by PPC.
SamK
antiX still complains whenever I try copying from VM to a file share.
It shows error where there is no one.It is attributable to ROX rather than antiX.
The ROX developer has been aware of the matter for some years. After such a time it is unlikely the developer will address it.
A potential workaround might be to append the option nounix to the mount command when mounting the share. When tested some years ago using Samba/CIFS, it allowed ROX to complete the task without displaying the error message. Be aware it may introduce unwanted effects, have a look at the mount manual for further info.
BitJam
” sudo kill $(ps -C connmand -o pid=); sudo connmand` ”
Thanks for sharing that workaround. I’ll change my “connman” quick launch icon accordingly and try that out when I have the chance!
Instead of sneaking around the back, I suggest you first try using the front door:
sudo service connman restartContext is worth 80 IQ points -- Alan Kay
” sudo kill $(ps -C connmand -o pid=); sudo connmand` ”
Thanks for sharing that workaround. I’ll change my “connman” quick launch icon accordingly and try that out when I have the chance!
Instead of sneaking around the back, I suggest you first try using the front door:
sudo service connman restartThanks, if it works, it’s even better!
Do you have any idea why connman sometimes fails to detect wi-fi networks and why restarting it (using whatever way) helps? The workaround I accidentally found out was deleting wlan configuration in Ceni (no, I didn’t use Ceni to configure my network, only connman) and suddently noticed connman started then picking up wi-fi networks and connecting to mine… There have been some complaints about connman- when it works its wonderfull, when it doesn’t, we have to find work arounds or reboot until it detects networks…P.
Xecure
Sorry guys. I think I have done something stupid but just in case I will report this a bug?. I know the solution is in changing the Individual source list, but still I will report what happened.
Reproducibility: antiX 19b1 64bit liveUSB, live CD and installed on Virtualbox
Step 1. Go to Repo Manager (Control Center > Mantenance > Repo Manager)
Step 2. Hit “Select Fastest antiX repo for me” (I was just stupid and hit it because I thought the conexion was slow, forgetting there was probably only 1 repo for buster).
2.1 Result: The test gives me a repo that doesn’t have buster.
Step 3. I see in the tab “Individual sources” that the antix.list package source has changed.
Step 4 (Optional). Any sudo apt-get update tells me it cannot reach the repo.
Step 5. Changing the repo in “antiX repos” tab does not change the repo in antix.list
Step 6. “Restore Original APT sources” does not work.As a result, I need to go to /etc/apt/sources.list.d/antix.list and change it manually (the active one at least) to
deb http://repo.antixlinux.com/buster buster main nonfreeIs this just me being stupidt or does this also happen to you people, that you cannot “fix” it with “Restore Original APT sources”?
antiX Live system enthusiast.
General Live Boot Parameters for antiX.BitJam
Do you have any idea why connman sometimes fails to detect wi-fi networks and why restarting it (using whatever way) helps?
I have a guess. So far, I’ve only used connmanctl from the command line and it works like a champ as long as you know the secret handshake:
agent on enable wifi services connect wifi_<tab> [wait for connection to appear] quit ifconfig -sMy guess is that in the GUI version you are missing the equivalent of “agent on” from the cli version. Perhaps if there is a way of doing “agent on” then you won’t need to restart the server.
Context is worth 80 IQ points -- Alan Kay
FYI, my net connection is generally reliable but connection attempts to both debian and antiX repos has been hit-n-miss during the past few days. (someone mentioned that debian had an announced maintenance event?)
“Select Fastest antiX repo for me”
“Restore Original APT sources”
In your shoes, I too would have expected those to work same as ever…
…but I hadn’t buster-tested those prior to reading your post.Yes, testing now, I get the same (broken) result you described.
No, (during beta) I wouldn’t label this as a bug ~~ why not working right now seems kinda obvious, but wait for other replies… maybe it truly is a bug that would carryover beyond betatesting.BobC
I can’t do “sudo apt-get update” keep getting errors saying to wait X hours. Sorry, I’m just setting an alarm and trying again, then…
anticapitalista
Try changing the repos
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
I agree using “sudo service connman restart” is the best way to restart the connman daemon.
Been looking through /var/log/syslog to see if any error messages are generated by connmand on initial start. Did not find anything that stood out.
But I did see in syslog after the connman restart was done and I went into connman to enable wifi that the firmware for my b43 wifi card was loaded.
I did a grep on syslog for “Loading firmware” with 7 lines printed before the hit and 7 lines after the hit.
Here it is:
——————————————————————————Jun 17 16:52:36 antix1 connmand[6406]: Adding interface wlan0 [ wifi ]
Jun 17 16:52:36 antix1 connmand[6406]: eth0 {update} flags 36867 <UP>
Jun 17 16:52:36 antix1 connmand[6406]: eth0 {newlink} index 2 address 00:E0:B8:D3:8A:8A mtu 1500
Jun 17 16:52:36 antix1 connmand[6406]: eth0 {newlink} index 2 operstate 2 <DOWN>
Jun 17 16:52:36 antix1 connmand[6406]: The name net.connman.vpn was not provided by any .service files
Jun 17 16:52:36 antix1 dbus-daemon[3886]: [system] Successfully activated service ‘fi.w1.wpa_supplicant1’
Jun 17 16:52:36 antix1 wpa_supplicant[6419]: Successfully initialized wpa_supplicant
Jun 17 16:53:16 antix1 kernel: [ 597.895144] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
Jun 17 16:53:16 antix1 connmand[6406]: wlan0 {update} flags 36931 <UP,RUNNING>
Jun 17 16:53:16 antix1 connmand[6406]: wlan0 {newlink} index 3 address 00:1A:73:27:F2:B3 mtu 1500
Jun 17 16:53:16 antix1 connmand[6406]: wlan0 {newlink} index 3 operstate 0 <UNKNOWN>
Jun 17 16:53:16 antix1 kernel: [ 597.966217] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jun 17 16:53:16 antix1 connmand[6406]: wlan0 {update} flags 36867 <UP>
Jun 17 16:53:16 antix1 connmand[6406]: wlan0 {newlink} index 3 address 00:1A:73:27:F2:B3 mtu 1500
Jun 17 16:53:16 antix1 connmand[6406]: wlan0 {newlink} index 3 operstate 2 <DOWN>——————————————————————————
I am wondering if someone who is having this same problem with connman and has already has done some type of install could turn off the connman service at boot and then manually bring it up.
It would be interesting to see if connman would start up cleanly without the need for a restart.
I forgot about the “disable=c” being available as a boot parameter to not start up connman using a Live USB device.
Used “disable=c” when booting the Live USB.
I then did “sudo service connman start” command.
Connman worked when I enabled wireless in connman.
Maybe there is some kind of dependency needs to be set for connman before it is allowed to start up in the boot process.
- The topic ‘antiX-19-b1-full (64 and 32 bit) available’ is closed to new replies.
