Search Results for 'ppa'

[Moderator BobC]

Modicia didn’t install. I got close, got it running live, then tried to install, and got 90% copied, then get an error and it aborts. Tried downloading and creating from Windows and Linux with same results. 2 separate downloads same mismatch from ISO to USB. Trying a 3rd time with a different flashdrive. Same exact error with 2nd flashdrive. Gotta give up on that one. Not much left I can do.

dd if=MODICIA_OS_light_181206.iso of=/dev/sdc && sync
4272128+0 records in
4272128+0 records out
2187329536 bytes (2.2 GB, 2.0 GiB) copied, 1390.99 s, 1.6 MB/s

cmp -n <code>stat -c '%s' MODICIA_OS_light_181206.iso</code> MODICIA_OS_light_181206.iso /dev/sdc

MODICIA_OS_light_181206.iso /dev/sdc differ: byte 208934, line 390

Even if I don’t get Modicia to load, I do like the concept of it being faster due to compression and better utilizing the ram, but its not apparent when running from USB. I think some of the later Puppy Linux’s uses that as well. I wonder if antiX would benefit from that as well?????

I will try your i3 configs when I get a little time. Was that for if I install i3 on antiX?

• This reply was modified 4 years, 5 months ago by BobC.
• This reply was modified 4 years, 5 months ago by BobC.
• This reply was modified 4 years, 5 months ago by BobC.

[Moderator caprea]

Yes, deinstalling xserver-xorg-input-wacom is a workaround for the bootdelay, but as you probably know, you will lose support for the wacom digitizer.
So it’s not a real solution.
Obviously the xserver-xorg-core 2.1.19.-1.0nosystemd2, which is the default on antix17.2, was patched for the bootdelay
and apparently the xserver-xorg-core 2.1.19.-1.0nosystemd4 is not.
Best is to pm anticapitalista and getting him aware of this thread.

Hi,
Please forgive, if this is a duplicate. I posted this topic. But after making an edit, it disappeared.

I’m running Antix 17 on an eeepc 900. It has a new 6600 mah battery, which keeps it going for a few hours. But, I would like more detail from a battery monitor.

At present, there is an graph bar icon on the right end of the bottom bar. It is green when charging, and yellow when discharging. (I don’t know what program drives this indicator. With Left or right click on icon, there is no popup info.) I also configured Conky to show battery status (charge/discharge, and percentage). Both show battery charge in 10% increments, until below 10%, when it goes to 1% increments.

I don’t know what program does the actual monitoring. The system includes acpid (but not acpi, apm, or upower).

I did install yacpi, which also reads in 10% increments. But it runs in a terminal window, and apparently must be polled periodically. So it is not a continual monitor.

Questions:
1. With the present system, is there a way to reconfigure, for 1% charge increments?
2. With the present system, is there a way to set a low battery alarm? (The eeepc seems to have a hardware alarm… an LED blinks when below 20% charge. But I haven’t found a way to set the limits.)

3. What Battery monitor do you recommend? Conky provides all the monitoring I need… except for more detail on the battery. So, I would avoid a monitor that depends on a whole suite of software.

Thanks, Dave

[Anonymous]

I can confirm the bug described in the OP. It only affects items displayed in the desktop menu “Personal” flyout.

Upon removing an item via MenuManager, I can see that its associated .desktop file within
~/.local/share/applications/TCM
has been removed, yet both the update operation initiated within MenuManager or using of “Update Menus” desktop menu item fails to remove the tested menu item.
(the strikeout bit is true, but set that aside for now and just troubleshoot a single piece of the puzzle.)

Toward troubleeshooting, I launched it from commandline
strace -eexecve /usr/local/bin/menu_manager.sh

Upon clicking the “Refresh” button displayed in MenuManager, the strace output showed:

{snip}
awk: fatal: cannot open file '/home//.desktop-session/desktop-code.0' for reading (No such file or directory)
+++ exited with 1 +++

Hmm… the file “~/.desktop-session/desktop-code.0” does exist

/usr/local/bin/menu-manager.sh

# Capture the name of the currently running window manager
CURRENT_WINDOW_MANAGER=$(awk -v FS='-' '$0=$2' /home/$SUDO_USER/.desktop-session/desktop-code.0)

apparently, for the context in which the awk command is executed, env var $SUDO_USER is undefined

[Member stevesr0]

Hi all,

I finally got around to purging the xserver synaptics package as recommended by Juan Hernandez on an Ubuntu forum and it has apparently eliminated the twitchiness and the moving around of the text insertion on my Fujitsu laptop. I did not do anything else in configuration except to add “natural scrolling” as an option on the libinput.conf file (recommended in the same thread).

This computer has separate touchpad and mouse buttons. My other laptop (a Lenovo Yoga) has only a “clickpad”, with segments of it acting as left and right mouse buttons. I haven’t done this as yet on that machine.

If this one is working well for a longer period of time, I will try the cure on that one. That might leave me without click tho (according to others with clickpads).

I will eventually follow up if this is a long term fix and also let people know if it works for the clickpad also.

[Member olsztyn]

Anonymous wrote:

antiX15 and/or antix16 betatesting discussions included attention to “better default font configuration”. IIRC, an improved fontconfig XML declaration (one which was nearly identical to what missTell has recently proposed) was presented, and agreed. That intended change apparently “fell through the cracks”, wound up being omitted from the build.

Thank you. This entire post is some great insight on what led to font quality falling though the cracks… I do not believe Mr. Anticapitalista is reading such periferal to the OS core topics as ‘Fonts’ but if someone close could convey this message this would be for significant benefit of AntiX. This would be for the benefit of all users in the first place, if such current poor quality fonts could be replaced by good quality ones. As it is now I owe this to missTell that I no longer need to put up with such deficiency, typing this now in clear, pleasant font…

On compromising OS quality in order to fit CD size: I think time has come to move beyond CD size. Even my oldest laptop Thinkpad T23 (year 2000), which came back to live with AntiX/Palemoon as AntiX showcase has DVD reader and most everyone nowadays is using USB sticks instead anyway…
Thanks again and Regards.

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Anonymous]

from recent reading, I’ve learned that
~/.fonts.conf is or will be deprecated (depends on OS version)
~/.config/fontconfig/fonts.conf is the futureproof path.

Also, per https://www.freedesktop.org/software/fontconfig/fontconfig-user.html
here’s the spec’ced search path order when the system looks for a fonts configuration file:
/etc/fonts/fonts.conf
/etc/fonts/fonts.dtd
/etc/fonts/conf.d
$XDG_CONFIG_HOME/fontconfig/conf.d
$XDG_CONFIG_HOME/fontconfig/fonts.conf
~/.fonts.conf.d
~/.fonts.conf

The packages “fontconfig” and “fontconfig-config” are pre-installed in antiX full edition. (I didn’t research whether they’re also present in net//core//base editions.) Anklebone connected to the shinbone… during start of desktop session, in the absence of a per-user font configuration file, rules declared within /etc/fonts/conf.d/* files (provided by, installed by “fontconfig-config”) govern how fonts will be rendered and substituted and whatnot.

Why [..] has not been foreseen or cared about in the first place?

A search the Old Forum archive will probably confirm that the antiX15 and/or antix16 betatesting discussions included attention to “better default font configuration”. IIRC, an improved fontconfig XML declaration (one which was nearly identical to what missTell has recently proposed) was presented, and agreed. That intended change apparently “fell through the cracks”, wound up being omitted from the build.

dpkg-query -S /etc/skel/.config/fancy-prompts-bash.conf
desktop-defaults-base-antix: /etc/skel/.config/fancy-prompts-bash.conf

“desktop-session-antix” https://gitlab.com/antiX-Linux/desktop-session-antix/tree/master/skel
seems to be the appropriate package for providing a custom /etc/skel/.config/fontconfig/fonts.conf
but we should continue to research whether a custom /etc/skel/.config/fontconfig/conf.d/ (and select children) would also be beneficial.

some Linux distros do care to have good quality fonts and other distros do not

Prior to the antiX17 release, anticapitalista enforced a steadfast design goal: the antiX “full” release must fit on a single CD. Even under that constraint, antiX still managed to ship a selection of fonts providing broad multilingual coverage. IIRC, the increasing size of (cough, LibreOffice) other packages across versions wound up displacing most of the CJK font packages in the antiX17 release.

I do not mean just AntiX but also MX

From where I sit, seems like MX has already “embraced” esthetics.
Over in the MX forum, I’ve chimed in on the subject of gtk themes and, during MX 17 betatesting I called attention to blurred font displayed in WhiskerMenu.
MX is a separate experience. Here in antiX forum I won’t criticize their esthetic choices, except to mention:
The current MX release includes a default ICONSET package which “weighs” several hundred megabytes (yikes!)

[Moderator caprea]

Cool, the default desktop is rox-icewm. Maybe stick with it until you feel more confident.
Not all desktops (the more lighter one don’t) provide desktop-icons.
The antiX control-centre is always your friend to manage the most things.

BTW, I just looked for boinc. It is installable through the package-manager synaptic.It is not recommended to install ppas on antiX, better stick with debian and antix-repos.Then antiX is rock-solid.

• This reply was modified 4 years, 5 months ago by caprea.
• This reply was modified 4 years, 5 months ago by caprea.

[Member dudesplace]

Well thanks for the replay but, I’m stupid but neither of these work for me.
I feel like the first day I tried to install a Linux OS years ago.
I’m lost…. I can get apps from menu’s, even got Boinc up and running by using a PPA.
Just sorta weird to me something that basic shouldn’t be that hard to do.
And how to get to /usr/share/applications folder is not clear to me at this point.

• This reply was modified 4 years, 5 months ago by dudesplace.

[Member ex_Koo]

Anonymous wrote:

Apparently I understand only station here…

How can I recommend i3 after manjaro to a beginner? The developers of antiX could also set fluxbox as default Desktop…

You can easily set what ever default desktop you wish in AntiX just by editing a file.
etc/slim.conf

# Available sessions (first one is the default).
# The current chosen session name is replaced in the login_cmd
# above, so your login command can handle different sessions.
# see the xinitrc.sample file shipped with slim sources
sessions rox-fluxbox,space-fluxbox,fluxbox,herbstluftwm,i3,i3_with_debug_log_,rox-icewm,space-icewm,icewm,rox-jwm,space-jwm,jwm

And in the same file. = Are over typing your user name & password every time you log in to your desktop with slim.
Then do this for password only..

`
# Focus the password field on start when #default_user is set
# Set to “yes” to enable this feature
focus_password yes

# Automatically login the default user (without entering
# the password. Set to “yes” to enable this feature
#auto_login yes

# default user, leave blank or remove this line
# for avoid pre-loading the username.
default_user koo

Also have a look in your home folder .desktop-session folder lots of .conf to play with here. Just backup the folder first Just in case of an opps..

I would always recommend i3 to new users…

Code Cast i3 videos Great to learn i3

Luke Smith more Advanced i3 (GOD)

I have used manjaro i3 myself very nice indeed.But I would install i3 from debian buster server onto AntiX anytime over using manjaro as their kernel updates can be pretty unstable at times.
Who ever builds the kernels for AntiX you are my Stable Hero.

• This reply was modified 4 years, 5 months ago by ex_Koo.
• This reply was modified 4 years, 5 months ago by ex_Koo.

[Anonymous]

We can expect roxterm “latest version” will be undesirable.
A while back, when working on rox-filer I checked the prospect of also forking roxterm
https://github.com/realh/roxterm/commits/master/debian/control
and discovered that its later versions (compared to the version present in debian8 // antiX16)
— dropped gtk2 support
— use libvte2.91 (no transparency/opacity) and “depppppacate” other roxtern features related to libvte-2.90 functionality

Zero remarkable bugs were reported against the older version, and only 1 bugfix (insignificant, regarding callback in response to new tab events) is present in later roxterm version… so I decided it’s not (yet) worth the effort to fork ~~ just keep using the (debian8 // antiX16) version.

FWIW, Deepin project maintains a fork of the libvte2.91 package which is patched to restore transparency support. I haven’t investigated whether that can cleanly serve as a drop-in replacement for use in antiX.

[Member KouDy]

All right so i managed to install the system to CF from USB boot.
What did the trick was apparently that i unchecked GRUB option in 3rd step (i think it was 3rd step). I am not sure why this in particular is causing everything to fail.
But then i ended up with disk without grub (i guess). I guess i need to run apt-get install –reinstall grub-pc when chrooted to CF installation from live. So now after i solve not working network while chrooted it will maybe come to life. Or am i on completely wrong track here?

EDIT :
from live i mount –bind /sys /proc and /dev into /mnt (where /dev/sda1 is mounted)
then after chroot i get name or service not known when trying to ping google.com
there is /etc/resolv.conf when listing /etc (in chroot so really /mnt/etc/resolv.conf)
so from live again i tried mount –bind /etc/resolv.conf /mnt/etc/resolv.conf which after chroot into /mnt doesn’t do anything

finally i figured the network by copying /run/resolvconf/resolv.conf into chroot, apt-get install –reinstall grub-pc worked fine but did not fix the boot from CF (again back to black screen with blinking underscore)

• This reply was modified 4 years, 6 months ago by KouDy.
• This reply was modified 4 years, 6 months ago by KouDy.
• This reply was modified 4 years, 6 months ago by KouDy.

Today I discovered the seemingly-redundant “Other Desktops” menu item
Menu }} Applications }} Accessories }} Other Desktops

??? When clicked, a yad window opens, stating “Your window manager was not one of the supported window managers.”
( Identical result when tested from within both an iceWM session and a fluxbox session. )

We’re presented 4 buttons:
“Disable Window” seems to do absolutely nothing when clicked, aside from causing the yad window to close.
Choose herbsluftwm radio item, click “Disable Window”, relaunch… and herbsluftwm is still/again present in the list.

A radio list of “Session Name(s)” is displayed, its items are apparently read from a hard-coded list ~~ herbsluftwm is listed although that had been purged from this machine.
(EDITED TO ADD: I found /usr/share/desktop-session/wm-menus/RAW-wm-menu and removed the herbsluftwm reference. This static list could/should be updated automatically, via apt postinstall hook.)

The “ControlCenter” button launches ControlCenter. Okay, but why? What is the intended/expected task at hand?

Selecting icewm (or fluxbox) and clicking “OK” button does work (achieves the same result as using the Desktops }} Other Desktops flyout menu item). I’m guessing this windowed app was intended for eventual use within openbox or xfce session (or even herbsluftwm?). Okaybut… it’s counterintuitive, er confusing, to include this item within the menu-applications section of icewm/jwm/fluxbox.

related bug:
If ~/.desktop-session/desktop-session.conf contains the declaration NOTIFICATION_DIALOG=”true”,
the undecorated “Session is loading…” yad window is neverending & must be manually kill’ed.
This seems like a regression. I haven’t set “true” for months, so don’t know when the regression crept in. Today, after belatedly updating this machine, I had intended to display the start of session popup to advise folks of the updated status + invite feedback if they noticed anything wonky.

[Anonymous]

what has changed since Antix 15

Neither fluxbox nor the conky program experienced version upgrades between the time antiX15 and antiX17 was released, right?
Here you can browse the incremental changes to default .conkyrc History for desktop-defaults-core/skel/.conkyrc

https://github.com/brndnmtthws/conky/wiki/FAQ
re-reading this leads me to suggest diff’ing your earlier vs current .conkyrc, specifically check whether one (and not the other) contains
own_window_hints=’below’
and / or
double_buffer = true

Vaguely, I can recall that some nuisance detail about conky led me to set own_window=true. Still a nuisance when I sometimes accidentally right-click its window instead of an empty spot in the root window, which results in failure of that click to open the expected desktop menu… but apparently that was “the lesser evil” compared to how conky behaved when own_window=false.

Another thing to check (diff): the presence, and the content of ~/.fluxbox/apps file on your 15//17 systems.
On my system, a rule in that file specifies layer=bottom for conky windows (don’t recall if that rule was set by default, or I added a custom rule)

In any case, if your script watches for workspace change events, it should be able to just call fbsetbg or fbsetroot, without disturbing (stopping/restarting) the conky process. Manpages exist for both fbsetbg and fbsetroot, and here’s a workspace watcher script which is likely suitable: https://forums.bunsenlabs.org/viewtopic.php?id=657

[Moderator Brian Masinick]

Anonymous wrote:

Apparently I understand only station here…

How can I recommend i3 after manjaro to a beginner? The developers of antiX could also set fluxbox as default Desktop…

Regarding window managers, in the early days, fluxbox was the primary window manager. A few years later, IceWM was introduced and chosen as the default, thought to be slightly simpler for those just getting started, acknowledging that fluxbox is definitely still a favorite for many, especially those who have used antiX for more than a decade.

Regarding other distributions, Manjaro is certainly an interesting distribution, currently topping the recent DistroWatch charts. I can’t speak for i3; I have never tried it. For me, [Debian, MX, and antiX] are three *PRIMARY* distributions for my very specific needs. For what it’s worth, right now I have the following distributions installed on my aging Dell Inspiron 5558:

(in no particular order):
1) Xubuntu 18.04 LTS
2) OpenSUSE Leap 15.0
3) Peppermint 9
4) Manjaro Linux 18
5) MX 17
6) Debian GNU/Linux 9
7) PCLinuxOS
8) antiX 17
9) Fedora 29

Some of these distributions have the latest updates, so for instance, Debian, MX, and antiX are updated to the most current code, regardless of how the release numbers are reported in the GRUB identification strings. I can’t remember whether I’ve just used dist-upgrade or if I’ve reinstalled MX, antiX, or Debian since their most recent releases. I do know for certain that I did a RELEASE upgrade from Fedora 28 to Fedora 29 just this week, updated Manjaro from a test release of 18 to Manjaro 18, and I’ve KEPT Xubuntu at the LTS release rather than the new 18.10 release.

--
Brian Masinick