Search Results for 'ppa'

[Anonymous]

FYI, the dependency on pkg “yudit-common” is bogus, is unwarranted.
The upstream source (as well as the debian feh package) already provides a copy of the yudit.ttf file.
Debian’s “team” apparently felt compelled to bundle (depend on) that other package because feh source lacks a copyright file and/or LICENSE file for yudit.ttf

(tested) removed the debian/control Depends: yudit-common declaration
rebuilt and installed the package, purged yudit-common (9.4Mb), and feh still runs without errors.

[Anonymous]

BobC, check out “mousepad” editor. It is now tabbed. Also, it has both lighter dependencies and lesser memory overhead than “medit”.

One shocking//weird detail that I discovered today:
the the buster “feh” package it’s installed package is only “is only 357kb” …
…but now depends on “yudit-common” which is 9.4Mb !
(yudit-common provides the guts of “yudit”, a unicode text editor which is not pre-installed)

git clone https://salsa.debian.org/debian-phototools-team/feh
cd feh
grep -inr ‘yudit’

src/feh.h:95:#define DEFAULT_FONT "yudit/11"
src/feh.h:96:#define DEFAULT_MENU_FONT "yudit/10"
src/feh.h:97:#define DEFAULT_FONT_BIG "yudit/12"
src/feh.h:98:#define DEFAULT_FONT_TITLE "yudit/14"
Binary file share/fonts/yudit.ttf matches
man/feh.pre:546:.Pq truetype, with size, like Qq yudit/12
debian/feh.links:2:usr/share/yudit/fonts/yudit.ttf	usr/share/feh/fonts/yudit.ttf
debian/control:25:         yudit-common
debian/changelog:85:  * Use yudit.ttf from yudit-common package
ChangeLog:1330:  * stick in yudit.ttf. it's not as pretty, but it is, apparently, DFSG

[Anonymous]

melodie, the snapshot tool contains a longstanding bug (reported across years) described as “I specify a custom namelabel for the boot menu, but the custom name is not displayed when I boot a system produced via the snapshot tool“. However, the symptoms of _that_ bug case do not include presence of % percent placeholders in the labelname. From a troubleshooting standpoint, we can’t guess whether you have encountered a separate, newly introduced, bug ~~ without hearing exact O/S version (e.g. antiX Full 17.4.1) (and, dist-upgrade was performed immediately prior to running the snapshot tool?) along with the exact installed versions of packages: “iso-snapshot-antix”, “remaster-antix”, “iso-template-antix”. During troubleshooting I would also ask: is the package “xorriso” currently installed on the machine performing the snapshot operation.

Skip the troubleshooting.
The following instructions should enable you to achieve the desired result.

1) Prior to launching isosnapshot, edit /etc/isosnapshot.conf and ensure that it contains this declaration:
edit_boot_menu=yes

2) Launch isosnapshot. During the workflow, when the “will now pause” dialogbox is displayed
and an editor window populated with “isosnapshot.cfg” opens…
ignore minimize (do not close/exit) that editor window.
(Do not close, because the snapshot operation will immediately resume upon closure of that editor window.)

3) While the isosnapshot program is paused, use a file manager (asRoot), and browse to /tmp directory.
Look for a /tmp subdirectory named “snapshot-123abc” (tailend is randomly chosen each time isosnapshot runs).
If you do not find it under /tmp, look for it under /home/snapshot/ ( e.g. /home/snapshot/snapshot-123abc/ )

To perform customizations, you will need to edit various (multiple) files.
After performing all desired edits, close that “auto-opened” editor window instance and the isosnapshot process will resume.

4) Don’t shoot the messenger. I’m attempting to coach you toward a successful outcome ~~ replies stating “should be easier” or “bugs should be fixed” will not be helpful here.

{work_dir}/iso-template/boot/syslinux/syslinux.cfg
{work_dir}/iso-template/boot/syslinux/readme.msg
    ^---- applicable to liveUSB boot menu
    
{work_dir}/iso-template/boot/isolinux/isolinux.cfg
{work_dir}/iso-template/boot/isolinux/readme.msg
    ^---- applicable to LiveCD boot menu
    
{work_dir}/iso-template/boot/grub/theme/theme.txt
{work_dir}/iso-template/boot/grub/grub.cfg

FWIW, these files wind up residing in the /boot subdirectory of the liveboot media, and they can be edited in place to customize an already-made liveUSB device. (This bit of trivia is not useful for someone intending to redistribute a customized ISO though.)

================

I believe the longstanding bug is due to the fact that only isosnapshot.cfg is presented for editing.
During liveboot, that cfg file is only referenced if isolinux (liveCD) is the bootloader.
The devs probably test in virtualbox, with the ISO set as a liveboot CD, and find “Hey, it works for me”.
However, for anyone booting liveUSB the syslinux bootloader is invoked.
Perhaps the configuration setting “make_isohybrid=yes” is expected to cause the syslinux bootloader to load isolinux.cfg (instead of syslinux.cfg)… but apparently, in practice, it is not doing so. Because the user never had easy opportunity to edit the copy of syslinux.cfg residing in the snapshot “work_dir”, the stock version of that file is perpetuated, and its content is evident during syslinux (liveUSB) boot sessions.

Because bugfixes and improvements to the upstream (MX) version of the snapshot tool have not been ported to the antiX 0.3.7 version (shipped in antiX19 beta, but absent from antiX gitlab repo), for local use I created a bespoke derivative version. Its workflow still remains a bit awkward but, yes, it does attempt to provide better inline instruction regarding customization. Many of the changes I’ve incorporated may not be regarded as desirable by the antiX/MX devs (the ui and helptext drown the user in details, are quite verbose), so I haven’t yet published the source code to gitlab.

[Anonymous]

The pre-existing Help page for persistence is already 69chars x 20lines (per page).
FYI, the F1 help content is authored as an html document (one entire helpdoc, per each language).
That content gets ‘munged’ and rolled into a cpio blob during the process of compiling the gfxboot component.
At runtime, the wordwrap applied by the gfxboot presentation will depend on the (pre)configured fontsize and dialogbox size.

Refer to the screenshot in my earlier post. Apparently gfxboot wraps based on whole words (vs exact char column).
v—– wordwrap occurs after 66 chars
Only save changes to files and directories under /home. This will
include all of your bookmarks and personal settings. Changes are
^—– wordwrap occurs after 64 chars

This portion (as would the table) contains linebreak tags. Above, when I mentioned “50..62char?”, that was from from foggy memory of having suggested alternative verbiage for the painfully short righthand descriptions (necessary to avoid forced linewrap)

<em>off</em> ......... No Persistence/No frugal<br/>
<em>persist_all</em> ..... Save root in RAM, save home on disk (save root at shutdown)<br/>
<em>persist_root</em> .... Save root and home in RAM then saved at shutdown<br/>
<em>persist_static</em> .. Save root and home on disk with home separate on disk<br/>
<em>p_static_root</em> .... Save root and home on disk together<br/>

the 2-dimension table above can comfortably fit…
maybe that is a low hanging fruit?

sudo apt install git
cd (or mkdir, your choice of path)
git clone https://gitlab.com/antiX-Linux/antiX-Gfxboot

The helptext document will be available for inspection and editing
…Help/antiX/en.html

After editing the document, if you move to the toplevel git project directory and type
make antix
the “built” content will be generated in the project’s …/Output/ subdirectory.
Those files, if you overwrite the same-named files on a stock liveboot pendrive
you can boot the customized pendrive to test the visual result.
(If an easier way to “preview//test” exists, I missed seeing that in the inline docs)

When you are confident that your revised helpdoc content is “ready”,
you can fork the gitlab.com/antiX-Linux/antiX-Gfxboot repository, add your changed file
and send a pull request to the upsream project.

(At gitlab or github, you can even do it all via browser UI: fork, edit the en.html file, send pull request)

Another question. What is the length limit of each menu option?
The “F5 Persist” menu locates at the middle of the screen,
therefore I think it still have enough room to contain some longer option names

I skimmed through the gfxboot source code files and did not find a “hard limit”. The set of textlabels for each option are parsed (into an array) as string data. The number of items determines (at runtime) the height of the popup box for that optiongroup. The width of the popup box is calculated based on the longest charlength item in the group.

Similarly, the set of labelnames for the options are concatenated and displayed to a horizontal box at runtime.
If you edit “Language” to a shorter string (“Lang”) and rebuild… in the result you would see that all the subsequent labels are automagically shifted leftward. If you replace “Language” with an overly-long string (for the sake of testing) e.g “Please select Language”… you’ll notice that the subsequent option names have been pushed rightward. Depending on your display resolution width, it’s entirely possible that the rightmost items will have become inaccessible (they are displayed, but displayed to coordinates which are offscreen out-of-bounds for your screen). Prior to antiX 17, the stated goal was to ensure the legacyBIOS bootmenu rendered correctly for (was accessible to) users with 800×600 displays. As of antix 17, the stated goal (IIRC) is to ensure the bootmenu fits a 1024px wide display.

Possibly the bootmenu could be revised to present “Language|Timezone|…” via a vertical (vs horizontal) box. Possibly you have the patience (admittedly, I do not) to wrestle with the task of achieving a “re-themed” bootmenu presentation layout.

ps (ocurred to me while proofreading):
Configuring gfxboot to use a smaller font size is probably an available way to “fit more onscreen”, but I can’t guess “how small is TOO small” for users with HiDPI displays.

[Member DaveW]

I think the issue has been resolved… I apologize for the false alarm.

Sometime ago, I installed a program from one of the Testing Repositories via Synaptic. However, I forgot to uncheck that repository before running the upgrade. So, it was trying to upgrade to the Testing versions of various programs. There were apparently some incompatibilities. After unchecking that repository, it looks like the upgrade has succeeded. Hopefully, nothing important was messed up in the process.

I would delete this thread, but don’t know how.

Thank you, DaveW

[Member NewfieDawg53]

caprea wrote:

It’s great Leo’s up and running .
Would be pretty interesting to feed it the latest and greatest antiX19, have you tried it already ? Will it boot with the xorg=intel parameter ?

I was planning on waiting until I received a 64MB ATI graphics card before installing something on Leo. However, I did try the 19b3 release on the box. It did not make it to a live desktop. Perhaps the newer kernel even when the xorg=intel parameter was set apparently doesn’t like Leo. I then popped in an AntiX 17.4.1 i386-full disc which booted to a live desktop with out problems (other than pebcak issues) and a wonky PS2 port for the keyboard. I’ve now installed 17.4.1 and will spend some time tweaking and setting up access to network printer.

Regards and Thankye Kindly,
Newfie

[Moderator Brian Masinick]

anticapitalista wrote:

BobC wrote:

I loaded Manjaro I3 to be able to install the newest IceWM from the Arch repos.

My effort is to make antiX the goto distro for IceWM. That’s why I want the newest code with the bug fixes etc.

but it’s really not mine to decide, so if I can, I help it along, and reap the benefits of it everytime I turn on my PC’s.

Every lap a little better line, a little faster, a little better time…

I successfully built icewm-1.6.1 debs for antiX-19 (and antiX-17). Just testing them out and if all is ok, we can ship antiX-19 with the latest and greatest icewm-1.6.1

I’m really looking forward to the antiX 19 and the MX Linux 19 releases. I’ve been using the various builds of antiX 19 for quite some time. On my Dell Inspiron 5558, I’ve had excellent success over the years using both distributions. Even if there are a few defects here and there, the overall appearance, quality, and usability of both distributions are already apparent, and I happily continue to endorse these two excellent distributions every time a discussion arises. Keep up the great work and I look forward to using both of them through the testing cycles and into the release. For my relatively “simple” use cases – pretty much all I do these days is run a couple of different browsers, use either IceWM or Xfce on the desktop, and I use a terminal and a file browser in addition to the browsers. On fairly rare occasions I’ll use a few other tools. With that simple set of uses, there’s not too much that goes wrong. Nevertheless, antiX and MX Linux outperform most of the other software out there, and I notice that MX in particular is finally getting some much deserved recognition!

Those of us who really understand things realize that the underlying antiX and Debian work have plenty to do with the outcome. The main thing to know is that both of these efforts, even though they are still considered “test” releases are superior even now to the majority of commercially released products, and by that I mean they perform better, contain quality work, and even the issues are managed with excellence. Continued thanks and congratulations to everyone who makes this possible, including developers, testers, users with ideas and suggestions, along with the upstream applications that are vital to the overall success.

--
Brian Masinick

[Member ModdIt]

Hallo and welcome to Antixia, the International community of AntiX.

Looking at your readout I see following lines.
Active apt repos in: /etc/apt/sources.list.d/graphics-drivers-ubuntu-ppa-eoan.list
1: deb http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu eoan main

Please be aware that bringing in an Ubuntu PPA is not a good idea if you want a stable system. You may be lucky but likely not..
If you need some software but are unable to find it as a non PPA debian package please do not be afraid to ask for assistance.

This forum is very friendly and helpful in contrast to some others I have experienced. The developers are reading and surely among the most competent on planet earth. AntiX is I think the best distro I have ever encountered.

[Member md4]

Hi i managed to get Synaptic and all my source errors fixed.
My package installer only initially accepted two of the three kernel updates mentioned as must for Antix 19.1 Next i ran in terminal apt-get update and upgrade once again and after that i went back to the package installer and tried once again to get the third kernel to install using the RESUME command in Terminal. I remember i reinstalled my laptop keyring using sudo apt-get reinstall antix-archive-keyring now everything seems to be running fine.
The funny brown and white cross in synaptic is something new i hadn’t noticed it represents apparently something not installed. Funny though i thought an empty tick box did that??
Many thanks to all who have helped — problem solved.

• This reply was modified 3 years, 8 months ago by md4.
• This reply was modified 3 years, 8 months ago by md4.
• This reply was modified 3 years, 8 months ago by md4.

I’m an old coot, and been using XP Pro for about five years now. Past couple years I been trying to learn Linux for online shopping & banking. Started out with Puppy Linux which was a bust. Setting up the network connection was a hurdle I couldn’t jump, so I started looking through Youtube review videos to find a distro I could handle. Came up with MX Linux, AntiX, Linux Mint, and TAILS. I went with MX Linux, and had been using it nearly a year in LiveCD mode before I noticed it was making my HDD spin into overdrive, which freaked me out enough to stop using it. I tried Linux Mint but it did the same. AntiX and TAILS seem to be the only ones that leave my HDD alone, so these are the only distros I use now (both as Live CD). I have a secondary HDD for an AnitX install, but waiting to see if I can learn it. It’s a lot more difficult than MX Linux was.

My setup is a used Dell Optiplex 755 I bought off Ebay, which I had modified (and checked for nasties) at the local computer shop. I had the CD-Rom replaced with a DVD burner, the 4GB RAM upped to 8 GB, and a mobile rack put into the spare 5.25 bay. It came per-installed with a corporate version of XP Pro, the sort that does not have to be activated, and all that rot. I’m on VDSL, and apparently it’s a slow speed, or so I’m told by the speedchecker sites. Seems as fast as the library or printshop computers, so fine by me. At least I ain’t on no dang timeclock, nor other limits. Internet has been a great boon to me. I replaced my $90 a month Comcast cable-TV with this $50 month VDSL. Now I watch ‘free’ movie/TV shows, get to explore the internet & darknet, shop online, etc., which I’d call a major bargain! I will be needing help with this AntiX though, but nothing is perfect.

Since Debian 10 Buster includes AppArmor enabled by default, I was mucking about with it on MX 19 Beta 1, and it works well without any additional configuration. It even works on the live system (snapshot, default kernel only). However, by default, it won’t work like this if you install other kernels. Same situation with the antiX default kernel.

To fix this I edit /etc/default/grub changing GRUB_CMDLINE_LINUX_DEFAULT from: GRUB_CMDLINE_LINUX_DEFAULT="quiet" to: GRUB_CMDLINE_LINUX_DEFAULT="quiet security=apparmor apparmor=1"
Without this change it tries to load SELinux which seems to conflict with AppArmor.
After that, run sudo update-grub and reboot.

On the live system you need to add the security=apparmor apparmor=1 to the kernel command line when you boot.

On vanilla antiX Full, the installation of apparmor, apparmor-profiles and apparmor-utils all ads up to an extra 3.2MB (as reported by apt install).

Testing on antiX, it doesn’t appear to take much memory. When starting antiX and loading into the desktop, Conky reports ~143-145MB of RAM used for the default x86-64 kernel after the whole desktop is loaded. It seems the addition of apparmor-profiles-extra adds a negligible amount (occasionally bringing it up a megabyte or two).

Since antiX includes Firejail by default, that works with AppArmor too: $ firejail --apparmor --noprofile firefox
I found the –noprofile is necessary under antiX.

Checking it all out with aa-status reveals:

$ sudo aa-status
[sudo] password for user: 
apparmor module is loaded.
38 profiles are loaded.
20 profiles are in enforce mode.
   /usr/bin/man
   /usr/bin/pidgin
   /usr/bin/pidgin//sanitized_helper
   /usr/bin/totem
   /usr/bin/totem-audio-preview
   /usr/bin/totem-video-thumbnailer
   /usr/bin/totem//sanitized_helper
   /usr/lib/cups/backend/cups-pdf
   /usr/sbin/apt-cacher-ng
   /usr/sbin/cupsd
   /usr/sbin/cupsd//third_party
   /usr/sbin/haveged
   firejail-default
   libreoffice-senddoc
   libreoffice-soffice//gpg
   libreoffice-xpdfimport
   man_filter
   man_groff
   nvidia_modprobe
   nvidia_modprobe//kmod
18 profiles are in complain mode.
   /usr/bin/irssi
   /usr/sbin/dnsmasq
   /usr/sbin/dnsmasq//libvirt_leaseshelper
   avahi-daemon
   identd
   klogd
   libreoffice-oopslash
   libreoffice-soffice
   mdnsd
   nmbd
   nscd
   ping
   smbd
   smbldap-useradd
   smbldap-useradd///etc/init.d/nscd
   syslog-ng
   syslogd
   traceroute
6 processes have profiles defined.
4 processes are in enforce mode.
   /usr/sbin/cupsd (1977) 
   /usr/lib/firefox-esr/firefox-esr (3700) firejail-default
   /usr/lib/firefox-esr/firefox-esr (3754) firejail-default
   /usr/lib/firefox-esr/firefox-esr (3871) firejail-default
2 processes are in complain mode.
   /usr/sbin/avahi-daemon (1890) avahi-daemon
   /usr/sbin/avahi-daemon (1891) avahi-daemon
0 processes are unconfined but have a profile defined.

There are fewer profiles here than on MX even with apparmor-profiles-extra. On MX there are 4 more profiles in enforce mode:

• /usr/lib/x86_64-linux-gnu/lightdm/lightdm-guest-session
• /usr/lib/x86-64-linux-gnu/lightdm/lightdm-guest-session//chromium
• /usr/sbin/ntpd
• /usr/sbin/cups-browsed

As you can see getting it to work is pretty straightforward. I have only tested this on antiX 19 Beta 3 so I am not sure it will work in antiX 17.x or older. I haven’t tested it on an antiX live environment yet, however it works very well with the MX live environment so I would be surprised if it doesn’t work.

I reckon it’s worth considering enabling by default if there are no issues with old systems.

[Anonymous]

caprea wrote:

antiX without a clear antifascist statement for reason of popularity
??
Maybe I would cry all day and leave it far behind me.

More like, for reason of common sense. Deep down they’re just as bizarre as bookmarks to YouTwitFace, but there is no context or apparent reason as to why the links appear in the bookmarks, and it looks like some lunatic has hijacked the browser. Why unnecessarily piss off users or scare them away?

@manyroads: have you looked into i3 or sway for tiling WMs? Note that sway is just a Wayland-based analog of i3.
See if running sudo sh ./VBoxLinuxAdditions.run gets around the noexec business.

[Member rej]

noClue-

Thanks for the explanation.

used:

rj@antix19rj:~
$ su
root@antix19rj:/home/rj# chown -R $USER:$USER /home/$USER
root@antix19rj:/home/rj# chmod -R 755 /home/$USER
root@antix19rj:/home/rj#

Nothing changed (that is apparent) – permissions still the same.

For proper understanding of Linux rights management, you should read some thorough explanations first!

Thanks – Found some tutorials for this. One is specifically Debian.

[Anonymous]

“It will be cool to press one obvious key and have the right program just pop up almost effortlessly.”

The unbearable lightness of being

(L’Insoutenable Légèreté de l’être / Milan Kundera)

Isn’t that something completely normal that you get things pop up effortlessly?

That’s why you’re using Microsoft Windows (TM) with fully functional software and a programmable keyboard.

Something like Microsoft Sidewinder X6 (TM) will do almost anything you want.

(It doesn’t make me coffee and brings it, so I don’t really get the most needed programmable function though.)

Image Gallery: Sidewinder Keyboard and Mice

— —

@masinick

“I consider the feel of most common keyboards to be “spongy”.”

That’s truth, but there are some “spongy” mechanical ones too and, there are also some hybrids, “half-mechanical” keyboars around.
Those are using “spongy” membrane technology underneath, but are having nice klicky feel because of well executed mechanics.

— —

@ile

“Have you ever helped someone with their computer to find that the markings are worn off the keys? all blank.”

Some people even pay extra, not to get any markings printed on their keyboards!

That’s what you get for a couple of hundreds …

(I heard that keycaps printing technique is so sophisticated that the letters never wear out.) 😉

— —

Since many years, still my favorite: Cherry G84-4100 mechanical mini keyboard.

Best Mechanical Keyboards For Typing (2019)

[Member DaveW]

rej,
My original post was late last night. When I reviewed it later, I found several errors, and made numerous edits. I suspect you took action based on an early version. I’m sorry.

You are correct. /etc/firejail/firefox.profile is the default file (not firefox.desktop). It looks like firefox-esr.profile refers to firefox.profile. For me, either one seems to do the same thing (in default mode).

For the private mode, firefox.desktop will reside in your /home/yourusername/.config/firetools/

There may be some difference in the way Firetools 9.44 and 9.58 work. I did not experiment much with the older version before upgrading. There is a configuration “Wizard” in 9.58. It looked promising, but after going through the custom setup dialog, firejail still would not run firefox in private mode. (By the way, Firefox has its own private mode, which may be what you activated, after you started firefox in default mode. I don’t know the differences between the two private modes.)

As noted, in my final edit to the previous post, the command line (in firefox.desktop) needs to have double dashes before ‘private’. Also, the “Exec” line in your firefox2.desktop is missing a space after firejail.

Have you tried to enter these commands in a terminal? (Use a non-root terminal.) If those commands bring up Firefox, you can check that it is actually running in Firejail, by opening “Tools” in Firetools. You can also check from a root-terminal, by typing on the command line: firejail --list
The program will list all running firejail sessions.

If that works, try this experiment. Create a /home/yourusername/.config/firetools/firefox.desktop file. Or, change the name of your firefox2.desktop and correct space and dashes as needed. Then, right click on your entry in the Firetools icon box, click ‘edit’ and enter the same information, as in this file. I don’t know why, but I think I had to do that. Then, turn Firetools “off” (right click the tab in the tray, and click “close”). Wait a few seconds, and restart Firetools. Right click the Firefox private icon in the firetools box, click “edit”. The data should be the same as in your firefox.desktop file. (Firetools apparently reads the .desktop files only when it starts.)

Also, right click on your Firefox default mode icon, click “edit” and verify that the Exec line is simply “firejail firefox” (without quotes).

Then, try to start firefox from either firejail icon and see what happens. (I run firefox in one mode or the other, not both at once in different firejail sessions.)

• This reply was modified 3 years, 9 months ago by DaveW.
• This reply was modified 3 years, 9 months ago by DaveW.
• This reply was modified 3 years, 9 months ago by DaveW.