MX Linux Forum

Posted: **Sat Apr 27, 2019 1:44 pm**

First alpha build of the upcoming antiX-19 release, based on Debian Buster.

Full announcement here: https://antixlinux.com/antix-19-a1-full ... available/

Posted: **Sat Apr 27, 2019 2:28 pm**

Downloaded!

Posted: **Sat Apr 27, 2019 2:59 pm**

Installed on my personal laptop so it screams! It looks awesome, conman works very well, first time I have seen the new installer--wowza! Now running my favorite fluxbox with space.

Fine work.

Posted: **Sat Apr 27, 2019 3:01 pm**

... I 'm waiting for the x32 alpha ... (for a frugal install) ...

Posted: **Sat Apr 27, 2019 3:52 pm**

oops wrote: Sat Apr 27, 2019 3:01 pm ... I 'm waiting for the x32 alpha ... (for a frugal install) ...

Sorry, but due to limited resources, there won't be one.

We will offer a x32 version for beta testing.

Posted: **Sat Apr 27, 2019 4:41 pm**

anticapitalista wrote: Sat Apr 27, 2019 3:52 pm
oops wrote: Sat Apr 27, 2019 3:01 pm ... I 'm waiting for the x32 alpha ... (for a frugal install) ...
Sorry, but due to limited resources, there won't be one.

We will offer a x32 version for beta testing.

Ah, no problem Anticapitalista . I will wait.

EDIT: Tried the x64 on virtual machine, and I like it, congratulations.

Posted: **Sat Apr 27, 2019 8:43 pm**

Request for Testing

1) Please test the rescue system on the live-media. It should be available via both Legacy and UEFI booting. If you boot legacy then you will have to first switch to grub in order to get to the rescue menus. The basic idea is it will find all of the Linux (and Windows?) systems on your machine and create a menu to boot into them.

2) We added a similar rescue feature called chroot-rescue-scan but it is command line only for now and there is no desktop file for it so it is easily overlooked. You should be able to run it from the command line:

Code: Select all

sudo chroot-rescue-scan

It too will look for all of the Linux systems on your computer, make a menu listing them all, and let you chroot into any one of them.

3) It would be good if a brave soul could test the live system built on fat32 such as what is made by Rufus on Windows. Test persistence and all that jazz.

Notes
There were a number of long and painful threads after the MX-18 release started by people who could not boot into their newly installed MX-18 system. The live rescue system (created by fehlix) and the chroot-rescue system are meant to be our firsts line of defence when someone can't boot into their system. These tools should let people get into an unbootable system and fix the problem. We want to make sure they work in most/all situations and are easy to use.

In addition, the chroot-rescue-scan program tries to identify the name of all the distros it finds. If it is not identifying a system correctly or just calling it "Linux", please let us know the distro so we can try to get the identification working for it.

Posted: **Sat Apr 27, 2019 9:26 pm**

BitJam wrote: Sat Apr 27, 2019 8:43 pm Request for Testing

1) Please test the rescue system on the live-media. It should be available via both Legacy and UEFI booting. If you boot legacy then you will have to first switch to grub in order to get to the rescue menus. The basic idea is it will find all of the Linux (and Windows?) systems on your machine and create a menu to boot into them.

I think it tries to find all Windows7-10 and generates menu entries to boo into. I haven't any WinXP to test it for this winos.
When it runs the generated rescue menus will present for all available grub install's and WindOS corresponding boot entries. For those who have GRUB2WIN installaed on Windows it shall also let you boot into that GRUB menu on Windows partiton.
So please report any feedback and findings.

BitJam wrote: Sat Apr 27, 2019 8:43 pm 2) We added a similar rescue feature called chroot-rescue-scan but it is command line only for now and there is no desktop file for it so it is easily overlooked. You should be able to run it from the command line:
Code: Select all
sudo chroot-rescue-scan
It too will look for all of the Linux systems on your computer, make a menu listing them all, and let you chroot into any one of them.

This chroot-rescue-scan system is extremely helpful also for fixing boot issues, e.g. due to corrupted grub settings,
It can help to fix to repair GRUB and UEFI or BIOS booted systems. With this tool run from a LiveSystem we are good position to quickly repair a broken boot-process on an installed system.

Posted: **Sat Apr 27, 2019 9:38 pm**

that chroot-rescue-scan is wonderful! That will be a real asset for system repair duties

with the rescue menus from grub, it also generates entries for the efi on the live stick. any way to exclude those? (or maybe we don't want too?)

Posted: **Sat Apr 27, 2019 11:49 pm**

Maybe this early alpha is meant to be a bare-bones release without all of the normal antiX stuff, meant just to test the boot repair tools, but in case that's not true I'll report this.

On my system, when I just boot from the LiveUSB normally (just hit enter at the first boot menu screen) I get the usual text boot messages, then I get a totally black screen for several minutes (I didn't time it but it was at least to to three minutes), then I finally get dropped back to a tty screen with a text login prompt. After I log in as demo and run startx I get the desktop, sort of, but with no icons, wallpaper or Conky, just a black desktop, a mouse cursor and a panel with the menu button and workspace switcher at the bottom. Apps and things worked but were rather slow to start, not snappy like the current stable antiX running on a live USB. Even loading websites in Firefox seemed slow.

I did a Conky toggle and the conky came up but with no data being presented, I went to the desktop properties and tried to select a wallpaper but nothing happened when I clicked on that.

I tried again in safe video mode: same thing. Same if I tell it to load the grub menu then do a normal boot with the default kernel.

I checked the md5 integrity of the ISO and it tests OK.

While I was in safe video mode I did an inxi -Fxz and saved its results to a file:

Code: Select all

$ inxi -Fxz
System:
  Host: mx Kernel: 4.9.170-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 8.3.0 
  Desktop: IceWM 1.4.3.0~pre-20181030 
  Distro: antiX-19.a1_x64-full Marielle Franco 27 April 2019 
  base: Debian GNU/Linux buster/sid 
Machine:
  Type: Desktop Mobo: ASRock model: A780GM-LE serial: <filter> 
  BIOS: American Megatrends v: P1.50 date: 05/25/2010 
CPU:
  Topology: Dual Core model: AMD Athlon 64 X2 5000+ bits: 64 type: MCP 
  arch: K8 rev.F+ rev: 3 L2 cache: 1024 KiB 
  flags: lm nx pae sse sse2 sse3 svm bogomips: 7236 
  Speed: 1800 MHz min/max: 1000/2600 MHz Core speeds (MHz): 1: 1800 2: 1800 
Graphics:
  Device-1: AMD RS780 [Radeon HD 3200] vendor: ASRock driver: N/A bus ID: 01:05.0 
  Display: tty server: X.Org 1.20.3 driver: vesa resolution: 720x480~N/A 
  OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.4 
  direct render: Yes 
Audio:
  Device-1: AMD SBx00 Azalia vendor: ASRock driver: snd_hda_intel v: kernel 
  bus ID: 00:14.2 
  Sound Server: ALSA v: k4.9.170-antix.1-amd64-smp 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASRock 
  driver: r8169 v: 2.3LK-NAPI port: e800 bus ID: 02:00.0 
  IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 1.06 TiB used: 1.11 GiB (0.1%) 
  ID-1: /dev/sda vendor: Seagate model: ST3160815AS size: 149.05 GiB 
  ID-2: /dev/sdb vendor: Seagate model: ST1000DM010-2EP102 size: 931.51 GiB 
  ID-3: /dev/sdc type: USB vendor: Generic model: Flash Disk size: 7.50 GiB 
Partition:
  ID-1: / size: 2.89 GiB used: 9.6 MiB (0.3%) fs: overlay source: ERR-102 
Sensors:
  System Temperatures: cpu: 37.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 132 Uptime: 17m Memory: 7.55 GiB used: 421.0 MiB (5.4%) Init: SysVinit 
  runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.33

Posted: **Sun Apr 28, 2019 12:07 am**

JayM wrote: Sat Apr 27, 2019 11:49 pm Maybe this early alpha is meant to be a bare-bones release without all of the normal antiX stuff, meant just to test the boot repair tools, but in case that's not true I'll report this.

This alpha is meant to catch problems like yours. I added some things to be checked that may not have been obvious but we certainly want to make sure it is booting properly, which for you it is not. I'm busy elsewhere ATM but I wanted to assure you and others that this is exactly the kind of bug we want reported.

Posted: **Sun Apr 28, 2019 2:18 am**

I was unable to connect to my wireless network using ceni. I tried on two different machines. The wireless hardware is detected but when I ask it to scan for networks it doesn't find any.

Here is the inxi -Fxx for each machine.

Code: Select all

System:    Host: antix1 Kernel: 4.9.170-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 8.3.0 Console: tty 2 dm: N/A 
           Distro: antiX-19.a1_x64-full Marielle Franco 27 April 2019 base: Debian GNU/Linux buster/sid 
Machine:   Type: Laptop System: Dell product: XPS 13 9350 v: N/A serial: 2M9Y562 Chassis: type: 9 serial: 2M9Y562 
           Mobo: Dell model: 076F9T v: A02 serial: /2M9Y562/CN1296363QA020/ UEFI [Legacy]: Dell v: 1.9.0 date: 08/31/2018 
Battery:   ID-1: BAT0 charge: 32.7 Wh condition: 57.2/57.5 Wh (99%) volts: 7.7/7.6 model: SMP DELL JHXPY53 serial: 1117 
           status: Discharging 
CPU:       Topology: Dual Core model: Intel Core i5-6200U bits: 64 type: MT MCP arch: Skylake rev: 3 L1 cache: 128 KiB 
           L2 cache: 3072 KiB L3 cache: 3072 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19200 
           Speed: 680 MHz min/max: 400/2800 MHz Core speeds (MHz): 1: 680 2: 2779 3: 2649 4: 2479 
Graphics:  Device-1: Intel HD Graphics 520 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:1916 
           Display: tty server: X.org 1.20.3 driver: i915 tty: 133x34 
           Message: Advanced graphics data unavailable in console for root. 
Audio:     Device-1: Intel Sunrise Point-LP HD Audio vendor: Dell driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
           chip ID: 8086:9d70 
           Sound Server: ALSA v: k4.9.170-antix.1-amd64-smp 
Network:   Device-1: Broadcom Limited BCM4350 802.11ac Wireless Network Adapter vendor: Dell driver: brcmfmac v: kernel 
           port: f040 bus ID: 3a:00.0 chip ID: 14e4:43a3 
           IF: wlan0 state: down mac: 30:52:cb:82:1b:ad 
Drives:    Local Storage: total: 149.12 GiB used: 1.09 GiB (0.7%) 
           ID-1: /dev/sda vendor: Samsung model: SSD CM871 M.2 2280 128GB size: 119.24 GiB speed: 6.0 Gb/s 
           serial: S26NNXAG738099 
           ID-2: /dev/sdb type: USB vendor: Samsung model: Flash Drive FIT size: 29.88 GiB serial: 0362315090012485 
RAID:      Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci v: 3.0 bus ID: 00:17.0 chip ID: 8086.282a 
Partition: ID-1: / size: 5.92 GiB used: 1.1 MiB (0.0%) fs: overlay source: ERR-102 
Sensors:   System Temperatures: cpu: 33.0 C mobo: 27.8 C 
           Fan Speeds (RPM): N/A 
Info:      Processes: 137 Uptime: 3m Memory: 7.46 GiB used: 134.6 MiB (1.8%) Init: SysVinit v: 2.93 runlevel: 3 default: 5 
           Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 running in: tty 2 inxi: 3.0.33

Code: Select all

System:    Host: antix1 Kernel: 4.9.170-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 8.3.0 Console: tty 2 
           dm: N/A Distro: antiX-19.a1_x64-full Marielle Franco 27 April 2019 base: Debian GNU/Linux buster/sid 
Machine:   Type: Portable System: Dell product: Inspiron 11 - 3147 v: N/A serial: FC5G812 Chassis: type: 8 v: A07 
           serial: FC5G812 
           Mobo: Dell model: 0VWN94 v: A00 serial: .FC5G812.CN7620648N00RK. UEFI [Legacy]: Dell v: A07 
           date: 07/20/2015 
Battery:   ID-1: BAT0 charge: 38.6 Wh condition: 43.0/43.8 Wh (98%) volts: 11.1/11.1 
           model: LGC-LGC3.95 DELL 0WF2847K serial: 34185 status: Discharging 
CPU:       Topology: Dual Core model: Intel Celeron N2830 bits: 64 type: MCP arch: Silvermont rev: 8 
           L1 cache: 56 KiB L2 cache: 1024 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 8663 
           Speed: 534 MHz min/max: 500/2416 MHz Core speeds (MHz): 1: 500 2: 500 
Graphics:  Device-1: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & Display vendor: Dell driver: i915 
           v: kernel bus ID: 00:02.0 chip ID: 8086:0f31 
           Display: tty server: X.org 1.20.3 driver: i915 tty: 120x30 
           Message: Advanced graphics data unavailable in console for root. 
Audio:     Device-1: Intel Atom Processor Z36xxx/Z37xxx Series High Definition Audio vendor: Dell 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:0f04 
           Sound Server: ALSA v: k4.9.170-antix.1-amd64-smp 
Network:   Device-1: Intel Wireless 7260 driver: iwlwifi v: kernel port: 1000 bus ID: 01:00.0 chip ID: 8086:08b1 
           IF: wlan0 state: down mac: e8:2a:ea:9c:c2:f5 
Drives:    Local Storage: total: 253.45 GiB used: 1.09 GiB (0.4%) 
           ID-1: /dev/sda vendor: SanDisk model: SDSSDHII240G size: 223.57 GiB speed: 3.0 Gb/s serial: 143670405375 
           ID-2: /dev/sdb type: USB vendor: Samsung model: Flash Drive FIT size: 29.88 GiB serial: 0362315090012485 
Partition: ID-1: / size: 6.12 GiB used: 1.1 MiB (0.0%) fs: overlay source: ERR-102 
Sensors:   System Temperatures: cpu: 35.0 C mobo: 31.0 C 
           Fan Speeds (RPM): cpu: 0 
Info:      Processes: 118 Uptime: 3m Memory: 7.69 GiB used: 113.9 MiB (1.4%) Init: SysVinit v: 2.93 runlevel: 3 
           default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 running in: tty 2 inxi: 3.0.33

Posted: **Sun Apr 28, 2019 3:45 am**

More info on my boot issue: I played around some more, tried various F4 boot parameters and options, and even tried using a different USB stick. I noticed that the last text I saw before I got the black screen was "starting display manager slim". I timed it this time and have that black screen for 4 minutes. When I get to the text login prompt, if I hit ctl+alt+delete to reboot I saw some text "stopping display manager" then "slim was not running" so slim is the culprit. It does the same thing in a failsafe boot too.

I also did an md5 integrity check from the antiX boot menu and it passed.

Posted: **Sun Apr 28, 2019 6:04 am**

dolphin_oracle wrote: Sat Apr 27, 2019 9:38 pm with the rescue menus from grub, it also generates entries for the efi on the live stick. any way to exclude those? (or maybe we don't want too?)

Well spotted. Actually I filtered it out first. But then could make it under some circumstances sometimes that the first partition on a hdd was filtered out too. So I disabled the filter again. As it meant to be a "rescue" tool, it might not matter to much to have it in the list anyway.

Posted: **Sun Apr 28, 2019 6:38 am**

JayM wrote: Sat Apr 27, 2019 11:49 pm Maybe this early alpha is meant to be a bare-bones release without all of the normal antiX stuff, meant just to test the boot repair tools, but in case that's not true I'll report this.

On my system, when I just boot from the LiveUSB normally (just hit enter at the first boot menu screen) I get the usual text boot messages, then I get a totally black screen for several minutes (I didn't time it but it was at least to to three minutes), then I finally get dropped back to a tty screen with a text login prompt. After I log in as demo and run startx I get the desktop, sort of, but with no icons, wallpaper or Conky, just a black desktop
Exactly the same on my computer

Posted: **Sun Apr 28, 2019 6:48 am**

I can't get to a desktop at all from the live environment in gnome-boxes (Debian buster host):

The console menu and tools seem to work though (and are very nice).

I tried an installation and networking wouldn't connect in the installed system but gnome-boxes is unfamiliar to me so I will try again in Alpine Linux under pure QEMU and report back.

EDIT: I reinstalled in gnome-boxes and networking is fine, I was being an idiot (as usual).

I will also test the ISO on the bare metal.

I'll be back...

Posted: **Sun Apr 28, 2019 7:01 am**

Attempting to add codecs from the Control Centre (running installed) results in this:

screenshot.jpg

Most of the wallpaper files are missing, but still appear in the wallpaper changer list.

Chris

Posted: **Sun Apr 28, 2019 7:57 am**

Live starts well. Installation works well. The fast installer is great.
Suspend to RAM leads to a freeze of the current desktop (Rox-Icewm).

Code: Select all

 inxi -Fxx
System:
  Host: antix1 Kernel: 4.9.170-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc 
  v: 8.3.0 Desktop: IceWM 1.4.3.0~pre-20181030 dm: SLiM 
  Distro: antiX-19.a1_x64-full Marielle Franco 27 April 2019 
  base: Debian GNU/Linux buster/sid 
Machine:
  Type: Desktop System: Dell product: OptiPlex 740 Enhanced v: N/A 
  serial: <root required> Chassis: type: 3 serial: <root required> 
  Mobo: Dell model: 0YP806 v: A02 serial: <root required> BIOS: Dell v: 2.2.7 
  date: 08/03/2011 
CPU:
  Topology: Dual Core model: AMD Athlon 64 X2 5800+ bits: 64 type: MCP arch: K8 rev.F+ 
  rev: 2 L2 cache: 1024 KiB 
  flags: lm nx pae sse sse2 sse3 svm bogomips: 4008 
  Speed: 1000 MHz min/max: 1000/3000 MHz Core speeds (MHz): 1: 1000 2: 1000 
Graphics:
  Device-1: NVIDIA C51 [GeForce 6150 LE] vendor: Dell driver: nouveau v: kernel 
  bus ID: 00:05.0 chip ID: 10de:0241 
  Display: x11 server: X.Org 1.20.3 driver: nouveau unloaded: fbdev,modesetting,vesa 
  alternate: nv resolution: 1680x1050~60Hz 
  OpenGL: renderer: NV4E v: 2.1 Mesa 18.3.4 direct render: Yes 
Audio:
  Device-1: NVIDIA MCP51 High Definition Audio vendor: Dell driver: snd_hda_intel 
  v: kernel bus ID: 00:10.1 chip ID: 10de:026c 
  Sound Server: ALSA v: k4.9.170-antix.1-amd64-smp 
Network:
  Device-1: Broadcom Limited NetXtreme BCM5754 Gigabit Ethernet PCI Express 
  vendor: Dell driver: tg3 v: 3.137 port: cc00 bus ID: 02:00.0 chip ID: 14e4:167a 
  IF: eth0 state: up speed: 100 Mbps duplex: full mac: 00:24:e8:3b:84:f3 
Drives:
  Local Storage: total: 447.10 GiB used: 3.20 GiB (0.7%) 
  ID-1: /dev/sda vendor: Seagate model: ST3160318AS size: 149.01 GiB speed: 3.0 Gb/s 
  serial: 9VY27FF2 
  ID-2: /dev/sdb vendor: Toshiba model: MK3263GSXN size: 298.09 GiB speed: 3.0 Gb/s 
  serial: Z989S14PS 
Partition:
  ID-1: / size: 19.05 GiB used: 3.20 GiB (16.8%) fs: ext4 dev: /dev/sda5 
  ID-2: swap-1 size: 3.04 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda6 
Sensors:
  System Temperatures: cpu: 37.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 143 Uptime: 22m Memory: 3.80 GiB used: 880.4 MiB (22.6%) Init: SysVinit 
  v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 
  running in: lxterminal inxi: 3.0.33

Posted: **Sun Apr 28, 2019 10:09 am**

Tried the ISO on the family AMD laptop and the live session worked well, I was able to connect wirelessly using connman.

The rescue system managed to find the several old UEFI loaders I had on my ESP and got my Debian stretch system running just fine.

It couldn't find grub.cfg but that's probably because that file was within a btrfs subvolume on the partition, which is a peculiarity of my setup.

Posted: **Sun Apr 28, 2019 10:30 am**

Downloading it now... thanks!

Edit: Did some quick run tests....

--- Booted like lightning in my 8GB of memory 10GB disk VirtualBox partition.
--- Installer is nicely laid out.
--- Progress bar is handy.
--- hmmm "Save Automation file to disk"
--- I like the icon choice. (I'm sure everyone is thrilled to know that.)

--- I am unable to link Virtualbox Guest-Additions.iso
--- Drag and drop files/folders Hangs in VirtualBox (VB) (I hang forever most of the time with the little 'hand' icon. Have to hard crash the system to get out of the error. btw. that happens in the current release 17.4 as well.
--- Many of the "Large" font size themes seem hover to medium font size. "Medium" font size themes hover size often shrinks to small but not on the standard Radiant theme. This is also a carry-over error from v. 17

Posted: **Sun Apr 28, 2019 1:48 pm**

chrispop99 wrote: Sun Apr 28, 2019 7:01 am Attempting to add codecs from the Control Centre (running installed) results in this:

screenshot.jpg

Most of the wallpaper files are missing, but still appear in the wallpaper changer list.

Chris

we probably need to add an "apt-get update" to this. the texture packs potentially have depends that aren't being full-filled.

Posted: **Sun Apr 28, 2019 1:52 pm**

First impression.

I don't like the icon set! :(

Tried to connect wifi, no luck there either. :(

(MSI Cubi-N trying it live.)

Will take another look when it gets to beta. :)

Posted: **Sun Apr 28, 2019 3:05 pm**

chrispop99 wrote: Sun Apr 28, 2019 7:01 am Attempting to add codecs from the Control Centre (running installed) results in this:

screenshot.jpg

Most of the wallpaper files are missing, but still appear in the wallpaper changer list.

Chris

Same error message here, nevertheless the codecs are installed.

Posted: **Sun Apr 28, 2019 3:16 pm**

In userspace Fluxbox on personal lap, little stuff:
--when I boot up, I need to log in twice: slim, login, slim. If I later log out, only once as normal.
--connman is not in the menu > Internet, also couldn't figure out how to run it in a terminal (tried both suppdo and su)
--bluetooth: has to be turned on in connman or on CLI, but no connection app or entry in menu so pairing etc obscure. Tried to install blueman but there is a dependency problem.

Posted: **Sun Apr 28, 2019 3:22 pm**

On my old machine grub rescue did not find Win XP nor systems with grub legacy

Control Center > Network > ConnectShares Configuration:
1 Find shares - OK, but
2,3,4 just return to 1

Earl

Posted: **Sun Apr 28, 2019 3:29 pm**

Jerry3904 wrote: Sun Apr 28, 2019 3:16 pm In userspace Fluxbox on personal lap, little stuff:
--when I boot up, I need to log in twice: slim, login, slim. If I later log out, only once as normal.
--connman is not in the menu > Internet, also couldn't figure out how to run it in a terminal (tried both suppdo and su)
--bluetooth: has to be turned on in connman or on CLI, but no connection app or entry in menu so pairing etc obscure. Tried to install blueman but there is a dependency problem.

connman is in settings (or system, I forget which) but its not in internet with the other stuff. the gui app is connman-gtk if you run from the terminal.

I have the same login problem on installed systems in virtualbox. I'm not seeing the issue on live.

Posted: **Sun Apr 28, 2019 4:13 pm**

Connman is in the Control Centre on the Network tab. (And works well here.)

Same issue installed needing to login twice.

Chris

Posted: **Sun Apr 28, 2019 4:39 pm**

old_guy wrote: Sun Apr 28, 2019 3:22 pm On my old machine grub rescue did not find Win XP nor systems with grub legacy

Unfortunately BOOT Rescue Menu is not implemented in the way to find GRUB legacy nor WinXP.
Simple reason: I had no system with those legacy OS's, so I a didn't put it into the OS-scanner :lipsrsealed:

Posted: **Sun Apr 28, 2019 4:45 pm**

chrispop99 wrote: Sun Apr 28, 2019 4:13 pm Connman is in the Control Centre on the Network tab. (And works well here.)

Same issue installed needing to login twice.

Chris

Thanks, I knew it was there but it needs to be repeated in the menu like the other apps.

Posted: **Sun Apr 28, 2019 5:05 pm**

Jerry3904 wrote: Sun Apr 28, 2019 4:45 pm
chrispop99 wrote: Sun Apr 28, 2019 4:13 pm Connman is in the Control Centre on the Network tab. (And works well here.)

Same issue installed needing to login twice.

Chris
Thanks, I knew it was there but it needs to be repeated in the menu like the other apps.

It is in the menu. Debian packagers put in under .... Preferences

Posted: **Sun Apr 28, 2019 5:33 pm**

Helpful of them...thanks.

Posted: **Sun Apr 28, 2019 8:51 pm**

Gotta say it works and looks VERY nice for me. I just wish conky-manager were available. My test is using Space-jwm, tint2, plank and compton.

Posted: **Mon Apr 29, 2019 7:45 am**

First, congratulations, it's a very nice distrib. too.
A suggestion:
packageinstaller
Maybe you can also add, for the item:
Remote Access : x2go ( or non-free: anydesk or teamviewer )or remmina, more efficient than VNC like.
viewtopic.php?f=108&t=49828&start=10#p499342

And maybe, synapse by default ?

PS: I would also like to have the ability to switch to an (some) other user (easily like into MX18) ... but maybe an other way already exist ?
mx-switchuser

... And to give a easy alternative to the too fine: Single-pixel window borders and similar situations
viewtopic.php?f=23&t=49963

Posted: **Mon Apr 29, 2019 12:36 pm**

I have an odd, repeatable, startup failure on this alpha.
I made the flash drive with mx-live-usb-maker.
With the normal text scrolling by, changing resolution twice, It boots into a GUI. Looks good. Conky is running. But the session is non-functional. The mouse works - you can open and navigate the menu but nothing you click on (or select & press Enter on) will open.
<Ctrl><Alt><F1> -> login as demo -> startx
That session works but has no wallpaper, conky or desktop icons. I'm typing from it now.

I did test the boot Rescue Entry (had to switch menus first as was indicated) and they work nicely. Was able to boot into (as root) an old forgotten MX-15 partition on my data drive from which the home partition had been wiped and reused for data.

Code: Select all

$ inxi -Fx
System:
  Host: Office Kernel: 4.9.170-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc 
  v: 8.3.0 Desktop: IceWM 1.4.3.0~pre-20181030 
  Distro: antiX-19.a1_x64-full Marielle Franco 27 April 2019 
  base: Debian GNU/Linux buster/sid 
Machine:
  Type: Desktop Mobo: Gigabyte model: GA-78LMT-USB3 R2 v: sex serial: <root required> 
  BIOS: Award v: F1 date: 11/08/2017 
CPU:
  Topology: 6-Core model: AMD FX-6300 bits: 64 type: MCP arch: Bulldozer 
  L2 cache: 2048 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 42278 
  Speed: 2000 MHz min/max: 1400/3500 MHz Core speeds (MHz): 1: 2000 2: 1400 3: 1400 
  4: 1400 5: 1400 6: 1400 
Graphics:
  Device-1: AMD RS780L [Radeon 3000] vendor: Gigabyte driver: radeon v: kernel 
  bus ID: 01:05.0 
  Display: tty server: X.Org 1.20.3 driver: ati,radeon 
  unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz 
  OpenGL: renderer: AMD RS780 (DRM 2.49.0 / 4.9.170-antix.1-amd64-smp LLVM 7.0.1) 
  v: 3.3 Mesa 18.3.4 direct render: Yes 
Audio:
  Device-1: AMD SBx00 Azalia vendor: Gigabyte driver: snd_hda_intel v: kernel 
  bus ID: 00:14.2 
  Device-2: AMD RS780 HDMI Audio [Radeon 3000/3100 / HD 3200/3300] 
  driver: snd_hda_intel v: kernel bus ID: 01:05.1 
  Device-3: Conexant Systems CX23885 PCI Video and Audio Decoder 
  vendor: Hauppauge works driver: N/A bus ID: 03:00.0 
  Sound Server: ALSA v: k4.9.170-antix.1-amd64-smp 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte 
  driver: r8169 v: 2.3LK-NAPI port: de00 bus ID: 04:00.0 
  IF: eth0 state: up speed: 100 Mbps duplex: full mac: e0:d5:5e:39:93:ac 
Drives:
  Local Storage: total: 2.30 TiB used: 1.13 GiB (0.0%) 
  ID-1: /dev/sda vendor: HP model: SSD S700 500GB size: 465.76 GiB 
  ID-2: /dev/sdb vendor: Western Digital model: WD20EFRX-68EUZN0 size: 1.82 TiB 
  ID-3: /dev/sdc type: USB vendor: Samsung model: Flash Drive size: 29.88 GiB 
Partition:
  ID-1: / size: 5.79 GiB used: 34.4 MiB (0.6%) fs: overlay source: ERR-102 
  ID-2: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 
  ID-3: swap-2 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sdb2 
Sensors:
  System Temperatures: cpu: 29.2 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 176 Uptime: 14m Memory: 7.29 GiB used: 661.3 MiB (8.9%) Init: SysVinit 
  runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.33

Posted: **Mon Apr 29, 2019 12:48 pm**

I just discovered that there is one thing that works - the Themes menu. Selecting a new theme drops me back to login. The session logged into works properly (and with the new theme).
So it's most likely related to the "have to log in twice" issue reported above except on this box the second login screen is hidden.

Posted: **Mon Apr 29, 2019 12:54 pm**

Well, I managed to duo-boot AntiX-19 and MX-18.2, now all I have to do is learn how to use AntiX. LOL
Any good suggestions?

Posted: **Mon Apr 29, 2019 7:19 pm**

timkb4cq wrote: Mon Apr 29, 2019 12:48 pm I just discovered that there is one thing that works - the Themes menu. Selecting a new theme drops me back to login. The session logged into works properly (and with the new theme).
So it's most likely related to the "have to log in twice" issue reported above except on this box the second login screen is hidden.

here's a little more on the "login twice" issue.

taking a look at /var/log/auth.log yields the following:

Code: Select all

Apr 29 19:14:53 antix1 slim: pam_unix(slim:session): session opened for user dolphin by (uid=0)
Apr 29 19:14:53 antix1 slim: pam_unix(slim:session): session closed for user dolphin
Apr 29 19:14:57 antix1 slim: pam_unix(slim:session): session opened for user dolphin by (uid=0)
Apr 29 19:15:25 antix1 sudo:  dolphin : TTY=pts/0 ; PWD=/home/dolphin ; USER=root ; COMMAND=/bin/cat /var/log/auth.log

note the close session open/close times, and the message from pam_unix about the issue. I'm not sure what it means yet, but it points toward session management.

as far as I can test, xorg doesn't even try to start first (nothing in the log anyway).

Posted: **Mon Apr 29, 2019 7:21 pm**

perhaps a clue from gentoo (home of elogind and such)

https://forums.gentoo.org/viewtopic-p-8 ... dd#8282050

Posted: **Mon Apr 29, 2019 7:45 pm**

further data:

with autologin enabled, the double-login problem does not occur.

on live, with autologin disabled, the double-login problem DOES occur.

Posted: **Mon Apr 29, 2019 7:57 pm**

dolphin_oracle wrote: Mon Apr 29, 2019 7:45 pm further data:

with autologin enabled, the double-login problem does not occur.

on live, with autologin disabled, the double-login problem DOES occur.

It seems to help me with my typing accuracy!

Edit: Has anyone tried changing from slim to lightdm to see if that clears things up?

Posted: **Mon Apr 29, 2019 8:01 pm**

manyroads wrote: Mon Apr 29, 2019 7:57 pm
dolphin_oracle wrote: Mon Apr 29, 2019 7:45 pm further data:

with autologin enabled, the double-login problem does not occur.

on live, with autologin disabled, the double-login problem DOES occur.
It seems to help me with my typing accuracy!
Edit: Has anyone tried changing from slim to lightdm to see if that clears things up?

I can tell you the problem does not occur with lightdm.

Posted: **Mon Apr 29, 2019 8:11 pm**

So my old brain says... I should swap out SLIM. I like LightDM better anyway.

Posted: **Mon Apr 29, 2019 8:12 pm**

manyroads wrote: Mon Apr 29, 2019 8:11 pm So my old brain says... I should swap out SLIM. I like LightDM better anyway.

perhaps, but slim is integrated with the antiX system in some tight ways. lightdm is not.

Posted: **Mon Apr 29, 2019 8:18 pm**

dolphin_oracle wrote: Mon Apr 29, 2019 8:12 pm
manyroads wrote: Mon Apr 29, 2019 8:11 pm So my old brain says... I should swap out SLIM. I like LightDM better anyway.
perhaps, but slim is integrated with the antiX system in some tight ways. lightdm is not.

I thought Slim was deprecated/ abandoned... see: https://wiki.archlinux.org/index.php/SLiM
Would it make sense to switch to something that is not abanddoned?

Posted: **Mon Apr 29, 2019 8:27 pm**

timkb4cq wrote: Mon Apr 29, 2019 12:36 pm I have an odd, repeatable, startup failure on this alpha.
I made the flash drive with mx-live-usb-maker.
With the normal text scrolling by, changing resolution twice, It boots into a GUI. Looks good. Conky is running. But the session is non-functional. The mouse works - you can open and navigate the menu but nothing you click on (or select & press Enter on) will open.
<Ctrl><Alt><F1> -> login as demo -> startx
That session works but has no wallpaper, conky or desktop icons. I'm typing from it now.

I did test the boot Rescue Entry (had to switch menus first as was indicated) and they work nicely. Was able to boot into (as root) an old forgotten MX-15 partition on my data drive from which the home partition had been wiped and reused for data.

Code: Select all

$ inxi -Fx
System:
  Host: Office Kernel: 4.9.170-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc 
  v: 8.3.0 Desktop: IceWM 1.4.3.0~pre-20181030 
  Distro: antiX-19.a1_x64-full Marielle Franco 27 April 2019 
  base: Debian GNU/Linux buster/sid 
Machine:
  Type: Desktop Mobo: Gigabyte model: GA-78LMT-USB3 R2 v: sex serial: <root required> 
  BIOS: Award v: F1 date: 11/08/2017 
CPU:
  Topology: 6-Core model: AMD FX-6300 bits: 64 type: MCP arch: Bulldozer 
  L2 cache: 2048 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 42278 
  Speed: 2000 MHz min/max: 1400/3500 MHz Core speeds (MHz): 1: 2000 2: 1400 3: 1400 
  4: 1400 5: 1400 6: 1400 
Graphics:
  Device-1: AMD RS780L [Radeon 3000] vendor: Gigabyte driver: radeon v: kernel 
  bus ID: 01:05.0 
  Display: tty server: X.Org 1.20.3 driver: ati,radeon 
  unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz 
  OpenGL: renderer: AMD RS780 (DRM 2.49.0 / 4.9.170-antix.1-amd64-smp LLVM 7.0.1) 
  v: 3.3 Mesa 18.3.4 direct render: Yes 
Audio:
  Device-1: AMD SBx00 Azalia vendor: Gigabyte driver: snd_hda_intel v: kernel 
  bus ID: 00:14.2 
  Device-2: AMD RS780 HDMI Audio [Radeon 3000/3100 / HD 3200/3300] 
  driver: snd_hda_intel v: kernel bus ID: 01:05.1 
  Device-3: Conexant Systems CX23885 PCI Video and Audio Decoder 
  vendor: Hauppauge works driver: N/A bus ID: 03:00.0 
  Sound Server: ALSA v: k4.9.170-antix.1-amd64-smp 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte 
  driver: r8169 v: 2.3LK-NAPI port: de00 bus ID: 04:00.0 
  IF: eth0 state: up speed: 100 Mbps duplex: full mac: e0:d5:5e:39:93:ac 
Drives:
  Local Storage: total: 2.30 TiB used: 1.13 GiB (0.0%) 
  ID-1: /dev/sda vendor: HP model: SSD S700 500GB size: 465.76 GiB 
  ID-2: /dev/sdb vendor: Western Digital model: WD20EFRX-68EUZN0 size: 1.82 TiB 
  ID-3: /dev/sdc type: USB vendor: Samsung model: Flash Drive size: 29.88 GiB 
Partition:
  ID-1: / size: 5.79 GiB used: 34.4 MiB (0.6%) fs: overlay source: ERR-102 
  ID-2: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 
  ID-3: swap-2 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sdb2 
Sensors:
  System Temperatures: cpu: 29.2 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 176 Uptime: 14m Memory: 7.29 GiB used: 661.3 MiB (8.9%) Init: SysVinit 
  runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.33

tim,

try using the debian testing version of slim. the version on the antiX iso is hosted on antiX. I've been getting better results with the debian testing version.

Posted: **Mon Apr 29, 2019 9:51 pm**

Problem trying to install LightDM, it needs systemd plus you cannot have two login managers running at the same time so one has to go bye bye.

Posted: **Mon Apr 29, 2019 10:36 pm**

ok, went back to the antiX slim due to some theme stuff that appears to be different, but I took the initscript from debian and am using that. working better...but I haven't been able to test enough to know if its a solution. one thing...slim starts earlier with the debian initscript, maybe too early.

Posted: **Mon Apr 29, 2019 11:07 pm**

one thing...slim starts earlier with the debian initscript, maybe too early.

yah, this observation reminds me of one of the tweaks seen in the GalliumOS fork:
https://github.com/GalliumOS-unmaintain ... 34e667381d
app.cpp
App::StartServer()
setpriority(PRIO_PROCESS, ServerPID, -19);

manyroads wrote: Mon Apr 29, 2019 8:18 pm I thought Slim was deprecated/ abandoned... see: https://wiki.archlinux.org/index.php/SLiM
Would it make sense to switch to something that is not abanddoned?

Something like this?
https://github.com/antix-skidoo/slim-antix
We've been using it locally since early '18. Mentioned it here topic/login-manager/#post-5364 but only "rust_collector" and scant few other users seemed interested, so I haven't really promoted its availability.

Posted: **Mon Apr 29, 2019 11:12 pm**

Thank you. The Buster slim with the antiX slim.conf (the first time I mistakenly let the debian conf file overwrite the antiX version) does work much better. One login - working session.

Posted: **Tue Apr 30, 2019 12:07 am**

I won't be that much help, but ISO appears to boot flawlessly in VirtualBox with the same virtual machine settings I use for an installation of MX. Remarkably error free kernel log. EVERYTHING works. Only issue detected is I can play a sound once in a terminal with play /usr/share/sounds/alsa/Front_Center.wav but the second time I try to play a sound the terminal locks up. Doesn't spawn any errors. I can x out of the terminal just fine. That ends sound for that session until I reboot. This problem does not manifest itself in the 17.3 or earlier or MX ISOs. VM sound settings are default ALSA ICH AC97.

Boots much faster than 17.3 ISO. In fact, fastest full ISO I've booted of any distro. Nice piece of work. That's all I have time for right now.

Posted: **Tue Apr 30, 2019 1:23 am**

Managed to get lightdm running, a bit difficult. You need to remove slim and consolekit, then, install lightdm, lightdm-gtk-greeter, lightdm-gtk-greeter-session and policykit-1. Before you reboot, put a picture in /usr/share/background for lightdm. Setup lighdm and reboot.
One boot and you are up and running.

Posted: **Tue Apr 30, 2019 1:49 am**

I don't know what happened to my earlier post, but second try: I booted the ISO in a Virtualbox VM and slim, the conky, all desktop items and the menu all worked, so whatever is wrong when I boot a bare-metal live USB seems to be an issue with slim vs. my onboard GPU.

Code: Select all

Graphics:  Device-1: AMD RS780 [Radeon HD 3200] driver: radeon v: kernel 
           Display: x11 server: X.Org 1.19.2 driver: ati,radeon unloaded: fbdev,modesetting,vesa 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: AMD RS780 (DRM 2.49.0 / 4.9.160-antix.1-amd64-smp LLVM 7.0.0) 
           v: 3.3 Mesa 18.2.6

Posted: **Tue Apr 30, 2019 6:03 am**

The double login to Slim already exists in 17.4
and must m.M. be caused by an update of antiX packages between March 12th and 24th...

Posted: **Tue Apr 30, 2019 7:04 am**

beardedragon wrote: Mon Apr 29, 2019 9:51 pm Problem trying to install LightDM, it needs systemd plus you cannot have two login managers running at the same time so one has to go bye bye.

Do you mean that MX is always using systemd? MX uses LightDM.

Edit: If folks have not seen this, it seems pretty helpful (option-wise).https://sysdfree.wordpress.com/2017/08/18/114/

Edit (next): I changed the setup to LightDM. Although the change itself went smoothly, I can report that the Desktop settings were 'borked'.

Removal of LightDM was graceful and jwm is back to where it was originally. Nice!!!

Posted: **Tue Apr 30, 2019 8:41 am**

male wrote: Tue Apr 30, 2019 6:03 am The double login to Slim already exists in 17.4
and must m.M. be caused by an update of antiX packages between March 12th and 24th...

interesting, thanks! I've only used 17.4 in live mode with autologin, so I missed it!

timkb4cq wrote: Mon Apr 29, 2019 11:12 pm Thank you. The Buster slim with the antiX slim.conf (the first time I mistakenly let the debian conf file overwrite the antiX version) does work much better. One login - working session.

Ok, good. I've currently got the antiX slim with the buster initscript, so that points to the init script needing changed perhaps, since that is the common point in our setups.

Posted: **Tue Apr 30, 2019 8:56 am**

I occasionally get the double login on MX as well (18, 18.1, 18.2). I can't reproduce this consistently, but when it occurs, it happens mainly when I unlock the screen (ie. already logged in). I wonder if there's something related here, it may not have anything to do with the DM at all.

Posted: **Tue Apr 30, 2019 9:01 am**

AK-47 wrote: Tue Apr 30, 2019 8:56 am I occasionally get the double login on MX as well (18, 18.1, 18.2). I can't reproduce this consistently, but when it occurs, it happens mainly when I unlock the screen (ie. already logged in). I wonder if there's something related here, it may not have anything to do with the DM at all.

I haven't seen it, so if you run across it, jot down the circumstances.

In the meantime, I'll set my session to lock the screen and see if it crops up.

Posted: **Tue Apr 30, 2019 9:07 am**

manyroads wrote: Tue Apr 30, 2019 7:04 am
beardedragon wrote: Mon Apr 29, 2019 9:51 pm Problem trying to install LightDM, it needs systemd plus you cannot have two login managers running at the same time so one has to go bye bye.
Do you mean that MX is always using systemd? MX uses LightDM.

Edit: If folks have not seen this, it seems pretty helpful (option-wise).https://sysdfree.wordpress.com/2017/08/18/114/

Edit (next): I changed the setup to LightDM. Although the change itself went smoothly, I can report that the Desktop settings were 'borked'. Removal of LightDM was graceful and jwm is back to where it was originally. Nice!!!

It looked like it when I was experimenting but I found out it was because the slim and it's dependencies pointed to that, as you can see below I am not using systemd. Thanks for the link, interesting.

bob@AntiX:~
$ inxi -Fxz
System:
Host: AntiX Kernel: 5.0.9-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc
v: 8.3.0 Desktop: Xfce 4.12.4
Distro: antiX-19.a1_x64-full Marielle Franco 27 April 2019
base: Debian GNU/Linux buster/sid
Machine:
Type: Desktop System: LENOVO product: 10181 v: Lenovo K450e
serial: <filter>
Mobo: LENOVO model: N/A v: 31900058 STD serial: <filter> BIOS: LENOVO
v: I1KT38AUS date: 06/10/2014
Battery:
Device-1: hidpp_battery_0 model: Logitech M570 charge: 90%
status: Discharging
CPU:
Topology: Quad Core model: Intel Core i5-4460 bits: 64 type: MCP
arch: Haswell rev: 3 L2 cache: 6144 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 25543
Speed: 798 MHz min/max: 800/3400 MHz Core speeds (MHz): 1: 799 2: 798
3: 799 4: 798
Graphics:
Device-1: NVIDIA GK208 [GeForce GT 720] vendor: Micro-Star MSI
driver: nvidia v: 410.104 bus ID: 01:00.0
Display: x11 server: X.Org 1.20.3 driver: nvidia
resolution: 1920x1080~60Hz
OpenGL: renderer: GeForce GT 720/PCIe/SSE2 v: 4.6.0 NVIDIA 410.104
direct render: Yes
Audio:
Device-1: Intel 8 Series/C220 Series High Definition Audio vendor: Lenovo
driver: snd_hda_intel v: kernel bus ID: 00:1b.0
Device-2: NVIDIA GK208 HDMI/DP Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel bus ID: 01:00.1
Sound Server: ALSA v: k5.0.9-antix.1-amd64-smp
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Lenovo driver: r8169 v: kernel port: d000 bus ID: 03:00.0
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 1.82 TiB used: 23.29 GiB (1.3%)
ID-1: /dev/sda vendor: Western Digital model: WD10EZEX-08M2NA0
size: 931.51 GiB
ID-2: /dev/sdd type: USB vendor: Western Digital model: WD Elements 25A2
size: 931.48 GiB
Partition:
ID-1: / size: 456.45 GiB used: 23.29 GiB (5.1%) fs: ext4 dev: /dev/sda3
ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2
Sensors:
System Temperatures: cpu: 39.0 C mobo: N/A gpu: nvidia temp: 49 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 28%
Info:
Processes: 182 Uptime: 7m Memory: 7.73 GiB used: 550.5 MiB (7.0%)
Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3
inxi: 3.0.33

Posted: **Tue Apr 30, 2019 9:25 am**

I have to say that I have been abusing antiX 19-a1 to the best of my abilities; and, things really are going well. I'm having fun and the alpha system is generous at regularly saving 'my bacon'. Almost every mistake, hack, etc I make has been easy to recover from. Most/many are gracefully handled by the software with simple uninstalls.

I need to say though, I have been exclusively beating up things in space-jwm. I wanted to learn jwm, customize it and get comfortable with it. It is light, fast, and can be made to look quite elegant (to my old eyes). Should I encounter any issues I'll post them. For now I'm documenting what I have built and will share my results, hacks, tricks, in a new separate thread.

:lipsrsealed:

Posted: **Tue Apr 30, 2019 9:35 am**

I'm testing with devuan version of slim. This will be on next alpha build.

Posted: **Tue Apr 30, 2019 10:42 am**

Here's the low-down on what I have been playing with. btw. there may be a bug on the spaceFM setting to manage the desktop wallpaper & menu. On 'some' logins I have noticed the setting revert to "unset" from "set".

Here's my other post: viewtopic.php?f=40&t=50011

Posted: **Tue Apr 30, 2019 12:45 pm**

Using dd to create a bootable USB flash drive, appears to work pefectly. Booting that to really humble hardware -- AMD Athlon(tm) 7850 Dual-Core 4 Gig RAM . No issue with playing sounds locking up the terminal as happened with booting the ISO into a VirtualBox VM. I get a flashing item on the panel that reads "Conky (antix1)" that disappears when I click on it. (This same thing happend booting the ISO into VirtualBox. I have also booted this "toram" (F4 option). Finally, created live usb with 19-a1 live-usb-maker.

Now, booting the full live-usb, noticed new options for persistence, p_static_root and f_static_root but no idea what they do. Same artifact on the panel that reads "Conky (antix1)" that disappears when I click on it. Default conky works as it's supposed to work. The gui upon shutdown when saving the dyamic persistence file is nice.

I set up a 2.5 G rootfs. Is -l shows it to be 2,684,354,560 bytes at /live/boot-dev/antiX, however, my 8 G flash drive still shows 6.4 G free from a total of 7.7 G on the ext4 partition. That doesn't compute. I didn't' realize it, but I conclude that the actual space consumption of rootfs may allocated to the file system on an as-filled-up basis. Can I be confident that the file system is really keeping track of available space, or is something wrong here? Upon shutdown, the GUI for saving the persistence file shows 7.4 G total, and 3.82 G free. That computes. :-)

apt update shows two debian.org repos not valid yet for another 1 hr 40 min. I did apt dist-upgrade for the three updates that were available and that went fine.

Posted: **Tue Apr 30, 2019 12:52 pm**

@firueroa, using the usb you can reconfigure things on your live system. For instance, you can take conky out of Sessions and Startup by unchecking the box for conky. It will not startup the next time you boot up live.

Posted: **Tue Apr 30, 2019 1:07 pm**

male wrote: Tue Apr 30, 2019 6:03 am The double login to Slim already exists in 17.4
and must m.M. be caused by an update of antiX packages between March 12th and 24th...

...FI: Here I have 2 locales languages (first priority: french, second us), the first login is always only with the us keybord and language, the second one is in french (after user logout, login).

Posted: **Tue Apr 30, 2019 5:09 pm**

beardedragon wrote: Tue Apr 30, 2019 12:52 pm @firueroa, using the usb you can reconfigure things on your live system. For instance, you can take conky out of Sessions and Startup by unchecking the box for conky. It will not startup the next time you boot up live.

That's not my intent. I do want conky and it works fine on this alpha antiX. The issue is a residual flashing conky task on the panel which goes away if clicked. I believe this is what is mentioned in the release notes.

Posted: **Tue Apr 30, 2019 10:14 pm**

figueroa wrote: Tue Apr 30, 2019 5:09 pm [...]
That's not my intent. I do want conky and it works fine on this alpha antiX. The issue is a residual flashing conky task on the panel which goes away if clicked. I believe this is what is mentioned in the release notes.

I see the flashing conky 'warning' in iceWM as well. Kind of weird...

Posted: **Thu May 09, 2019 11:11 am**

I'm a bit late to this thread, but I just now tested antiX 19 alpha 1, via Live USB
My opinion?
Very, very fast and stable. It's the first time I ever recall testing a Alpha version of any distro! It uses a tiny bit more ram on idle.
Finally, it comes with a newer version of LibreOffice ! :-) It no longer has the tray quickstarter but I tested it and Writer opens in 2 seconds, in a 10 y.o. pc, running in a USB 2 thumbdrive! What magic is this, Anticapitalista?
I tinkered a bit with antiX looks on previous versions. I do understand that antiX is meant to be fast and use the least resources possible, but it got a big face lift with the new theme (it looks almost perfect, some small bugs like the down arrow icon on the File manager not looking ok).
Looks matter, some users probably take a look at antiX and run away, thinking it's a kind of Windows XP clone from the 90's. Now it's a bit more newbie friendly- for example- Round icons are now common in modern Android phones, people are used to that. The new desktop images are some of the best I've ever seen!
Small things like Volume Icon having the "blue bar" available to display the volume in a more precise way is very handy (and I never noticed that feature before).
I do admit that in the menus, most new icons are hard to understand, I have to read the descriptions to really get their meaning... Most try to convey complex functions so... that's to be expected.
But antiX now has a more modern and unique "feel" to it, more uniform across all icons.
I can suggest adding a icon on the desktop so new users know how to quickly add a internet connection icon to their bar, I read a negative review about that, the user didn't even took the time to look for how to connect to his wireless connection in the OS options...
Bigger (by a bit- RAM wise), faster and more modern than ever.
I can't wait for the final version!

For me only one thing would make this version even greater- if, by some miracle, it included skidoo's Fluxbox version, I use (it adds a real start menu and quick start "icons" to Fluxbox bar)- I have to install that manually, so I can run my costumized antiX UI :-(

best antiX ever!
P.

Posted: **Thu May 09, 2019 3:21 pm**

figueroa wrote: Tue Apr 30, 2019 12:45 pmI set up a 2.5 G rootfs. Is -l shows it to be 2,684,354,560 bytes at /live/boot-dev/antiX, however, my 8 G flash drive still shows 6.4 G free from a total of 7.7 G on the ext4 partition. That doesn't compute. I didn't' realize it, but I conclude that the actual space consumption of rootfs may allocated to the file system on an as-filled-up basis. Can I be confident that the file system is really keeping track of available space, or is something wrong here? Upon shutdown, the GUI for saving the persistence file shows 7.4 G total, and 3.82 G free. That computes. :-)

You're right. The discrepancy is caused by us using "sparse" files for rootfs and homefs which is massively more efficient. We use the fallocate program to create sparse files but you can also use:

Code: Select all

dd if=/dev/zero of=$file bs=1M count=0 seek=$size

Many programs still report the free space in sparse files as free space for any file to use. The du program was recently fixed. In the past we had to use the --apparent-size option in order for it get the sizes of rootfs and homefs right. Now it works correctly even without that option. We tried hard to not use the overoptimistic free sizes when estimating the space available for creating new files so all the allocated space in rootfs and homefs would be available.

One of the reasons we like to use ext4 for the live-usb is because it supports sparse files. For a large $size compare the time of the "dd" command above with the same command when "count=0 seek=$size" is replaced with "count=$size".

IMO sending bug reports to the projects that haven't fixed their programs yet would be most welcome.

apt update shows two debian.org repos not valid yet for another 1 hr 40 min.

I bumped into this too.

Posted: **Thu May 09, 2019 6:05 pm**

BitJam wrote: Thu May 09, 2019 3:21 pm You're right. The discrepancy is caused by us using "sparse" files for rootfs and homefs which is massively more efficient. We use the fallocate program to create sparse files but you can also use:
Code: Select all
dd if=/dev/zero of=$file bs=1M count=0 seek=$size

Amazing. A user (like me) could be easily mislead by df to think they had more Live-usb-storage space because of what is reported, and du in the alpha release still requires the use of the --apparent-size option. I hadn't given it a moments thought before this test drive. Thanks for those details.

Added: BTW, if I use:

Code: Select all

sudo du -h --apparent-size --max-depth=0 /
du: cannot access '/proc/7464/task/7464/fd/3': No such file or directory
du: cannot access '/proc/7464/task/7464/fdinfo/3': No such file or directory
du: cannot access '/proc/7464/fd/4': No such file or directory
du: cannot access '/proc/7464/fdinfo/4': No such file or directory
129T	/

That would be a new record in usb flash memory size. So much for these everyday tools I've learned to love and trust.

MX Linux Forum

antiX-19-a1-full (64 bit) available

antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Suspend results in a freeze

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available

Re: antiX-19-a1-full (64 bit) available