Search Results for 'ppa'

[Member seaken64]

Okay, I tried to duplicate the troubles I had with the antiX-17 installer but something different happened. I knew I was able to get the live distro to work with the “failsafe” choice so I put the DVD in the drive and rebooted, then chose “failsafe”. The install of the live image started up and it came to the same “make-fstab” line and paused. I was expecting the same input/output errors and I was going to write up the errors and post it here.

But this time it came back with a message saying it put 15 hard disk entries and 1 removable entry into /etc/fstab. Then it continued and eventually completed the startup.

I soon realized that I had left the USB key drive in place from my last failed boot trying to use PLOP. And it seems that this install was now using the image off the USB instead of the DVD. Weird. I had used the DVD to boot with and that is where I got all the errors, even though I did get through with the “failsafe” choice. But when I tried to use the cli-installer it failed. I then tried to use the USB image along with PLOP to boot from the USB. It failed to boot at all, Just a blank screen with a blinking cursor.

But when I went back the antix-17 bootable DVD I did not take out the USB key. I used the DVD to boot and chose “failsafe”. And from there it appears that the install routine chose the USB to continue the install. And everything finished just fine. So maybe the problem was the DVD somehow not allowing the fstab to be created. Not sure. But anyway, this USB install seems to be the solution. I thought it was not going to be possible since this machine does not boot from USB. But apparently the install routine knew what to do.

So now I have antix-17 installed on this Pentium-III. (I used the gui install) But all is not good. More on that in another thread.

Thanks for all the ideas.

Sean

[Forum Admin rokytnji]

As far as I am concerned. You are on your own.

If You break it

By adding Ubuntu PPA’s Which is a default systemd distro.
We already have the MX team helping with rebuilding packages without systemd dependencies.
Like Stevo helping me out with non-sse2 palemoon browser for my P3 laptop.

Debian is a systemd distro and this is what they say

https://wiki.debian.org/DontBreakDebian

I was dumb/bored enough to make a FrankenAntiX box. I broke the control center 1st because /usr/local/bin was totally ignored. Everything started to default o using /usr/bin instead. I did not bring my breakage problems to the forum.
I figured out what I broke on my lonesome. Ended up doing a re-install after multiple error-code on dist-upgrade.

Ubuntu has their own file structure , places to put files, though based on Debian. Think of it as inviting a human being. Like you.They are red blooded like you. That is the only common thing between you 2. But they have different habits on how they are gonna live in your place.

Something small from Ubuntu. Using a .deb. With not a lot of dependencies. Might be OK. Something Big? with a PPA involved. You are on your own. Expect breakage. So I am with skidoo on this issue. But you being all grown, do what you wish. 🙂 Maybe you will figure out how to edit service files.

\

Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.

Linux Registered User # 475019
How to Search for AntiX solutions to your problems

[Moderator BobC]

Yes, its like a winding one lane road going down a steep hill that leads down into a darkening forest, then into a tunnel, which goes darker and deeper and becomes treacherous and slippery as it turns into a mine and then cave and descends to hell!

I’ve been avoiding many of those paths on the way down the hill, but the lure of potential solutions gets me headed that way.

Tilde is a PPA example. I ended up settling on Jed in CUA mode, and adding F1 for help and F2 to save, and still need to add F3 to exit, and have no clue what to do with buffers…

And they say not to compile your own…. But maybe that’s a better poison, at least you know its poison, and are thinking more of testing and such, but don’t think about maintaining till its a big problem.

Thanks for the thoughtful reply. I had already read one of your older posts on it.

PS: Why did I NEED a fancy editor to run it a terminal? Why would I choose jed for an editor? Well, I wanted an editor that could copy/paste that handles multiple files, has keyboard macros, search/replace features and undo capability, that could run in a terminal, and use what I would consider normal keys to drive it (keep in mind I work on MS and IBM systems all day), and from Midnight Commander I wanted it to be my Viewer and Editor. I wasn’t happy with Nano or VIM or EMACS or E3 or Leafpad or LibreOffice write type programs. Geany is actually pretty good, but being X only can be an issue. I’m using Spacefm more, but sometimes MC is just easier. Jed doesn’t work well with the mouse, but is still supported by its original author from way back when, and was in the standard repos, and those helped make my choice for me.

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

[Anonymous]

v—- just train of thought (not intended as a firm, ranked, list)

1. explore the range of programs pre-installed in antiX (reflecting proud curation, honed across a decade, of best-in-class lightweight appilcations)

2. (use synaptic package manager program to search/browse and) add something from the antix repos

3. use the packageinstall utility (controlCenter contains a launcher) to check for additional software available from MX/antiX “testing” repos and from other (e.g. multimedia) repos which are not, should not be, left continually enabled within your sources.list(s)

4. Visit https://packages.debian.org and type in a known (to you) program name, then note the “similar” items listed in right-hand column. Continue exploring ~~ maybe debian repositories have program XYZ (but not for the release you’re using, so not shown to you by synaptic). Installation of a package from older or newer debian repository may introduce breakage on your system, BUT you can post to inquire with antiX/MX devs: Can the it be easily re-packaged, backported?

5. Visit “alternativeto.net” and “slant.com” and “opendesktop.org” and similar sites (see: forum topic I linked to in earlier post) to further research the existence of alternative programs. Each time you discover an appealing title, revisit “packages.debian.org” (or packageinstaller, or synaptic) to recheck its “native” availability

6. Become proficient at using “firejail”, then explore the prospect of installing sandboxed AppImage -packaged programs. (BTW, don’t believe their claim: “Linux apps that run anywhere”. YMMV)

7. Visit, and search “sourceforge.net” (aka “sf.net”) and “github.com” and “launchpad.net” ~~ after rechecking whether a given software is, in fact, already available “natively” (but you didn’t realize it)… read the README or INSTALL or whatever docs are provided on the project’s page. You’ll often discover that .deb packaging isn’t necessary to install the software. You’ll also have an opportunity to see/know, ahead of install: known issues, where to post support requests, and you’ll usually find “docs+protips” the software developer has provided which you’d probably not realize are available. Debfile (and rpm, and pacbert) installation SUCKS in this regard; you wind up with the program installed and (hopefully) a menu entry launcher, but zero indication of whatever provided docs have been installed.

8. If the software has a non-gitforgepad “domain website”, also visit there prior to installing. Screenshots, baby! Tips! Links to otherwise non-obvious download sites and/or availability of various packag(ing) formats.

9.
10.
11.
By the time you’ve considered all the above possibilities, you’ll probably discover that “use of PPAs” is seldom, if ever, necessary for a given software title.

Okay, okay, not NECESSARY… but what about “updates” ?

Sigh. And here we enter the realm of sad irony.
After rolling the dice, by installing a program not specifically designed for use with your system,
and never (prior to your install) tested to work with your system…
3 weeks (or months) later, when an automated “update” of the non-native PPA borks your system, you have no idea why your system is suddenly “borked”.

.
BobC, thanks for opening this discussion topic

[Anonymous]

xref: https://www.antixforum.com/forums/topic/questions-on-installing-programs-from-ppa/
^—- tl;dr ~= expect breakage… and YOU get to keep the pieces !

xref: https://www.antixforum.com/forums/topic/apt-fast-upgrade/
^—- tl;dr ~= opportunity to discover firsthand, the effects of Darwinism and Idiocracy

[Anonymous]

I hope you will click this to read and gauge the previously-expressed antiX culture/outlook regarding usage of PPAs.
https://www.antixforum.com/forums/search/ppa/
Beyond the specific posts returned by the search result, click to read the individual posts in the context of their respective topics.

.

please suggest dos and don’t’s and procedures to follow?

In a nutshell, the “suggest” must be: please don’t
Evident in the forum search results (and old forums archive, and other non-ubuntu forum sites):
• packages from PPAs, when installed to non-ubuntu systems, frequently do “cause breakage” (or, inexplicable to the user, refuse to run or immediately crash)
• affected users, instead of seeking help from the PPA maintainer/packager, frequently seek help from “non PPA -using” forum peers
• obviously, “non PPA -using” peers usually can’t effectively troubleshoot/diagnose PPA users’ random “plz help! fix my broke!” issues

It seems to me that if a PPA is like a repo, and its left there, the system is going to potentially install anything it finds from there when asked to install or update things.

Think about it:
The active repos in your “stock” sources.list(s) contain 30,000+ packages.
Obviously, ALL of those 30K packages don’t get “automagically shoved down your throat”.
Although enabling extra/frivolous sources.list entries (PPA or not) adds overhead and slows down each apt-get update operation,
even on a system where “unattended upgrades” is set — which is not the case with stock antiX — during an apt-get upgrade operation, only the already installed packages are upgraded.

However, unattended, or not — an upgrade operation will ALSO attempt to install any additional, newly-introduced, dependent packages.
Oops (ouch!), the PPA maintainer expects the target system contains, or has access to certain ubuntu-specific versions of dependent libraries,
has only tested whether the program works flawlessly in the presence of an exact set of libraries.
^— You’ll often notice separate ubuntu-release-specific PPAs for a given program, and that underscores the point:
“mix-n-match? Yer tempting fate, risking breakage, so… good luck with THAT ~~ and when it breaks, YOU get to keep the pieces {g}”

use git? PPA? sourceforge? other repos?

In case you haven’t yet read this, please do so:
https://www.antixforum.com/forums/topic/where-do-you-learn-about-additional-apps-software/

also:
https://www.antixforum.com/forums/topic/apt-fast-upgrade/
^—- tl;dr ~= opportunity to discover firsthand, the effects of Darwinism and Idiocracy

Nope, I don’t place less trust in .deb packages hosted in PPAs, vs hosted on sourceforge. I distrust them equally.
{soapbox} Yeah, I realize that a “trust, but verify” rule-of-thumb (not “distrust, and verify”) is more approachable, but does “trust, but verify” even stand as the current norm, or does it amount to “do as I say, not as I do” lipservice? Yeah, rational ignorance in response to an overly complex world… but the emergent “new normal” (life’s too short. Just trust it — hey, it’s OpenSource) will likely bring significant consequences. {/soapbox} In the meantime:

with no internal drives mounted (nor cabled, when possible)…
a “quarantine” VM instance, or a “quarantine” LiveUSB, or daily-driver LiveUSB booted without persistence,
provides a relatively worry-free haven for us to install/explore “not-yet-verified” software.

use git? PPA? sourceforge? other repos?

Regardless the “other than stock repositories” source, anyone who colors outside the lines need to understand (and too few do) that any given package, any given program, that installs cleanly on YOUR system may not function properly (might not even install cleanly) on my system… or on the system of the next person who wanders through and reads our discussion regarding that program.

“Hi. I installed ABC, from PPA DEF, and it’s not working. Any ideas why? THanks in advance.”
^—— slim chance in, well, it’s highly unlikely that anyone reading can do anything beyond “playing 20 Questions” guessing toward a solution.

“but, but, I manually downloaded and used gdebi (or dpkg -i), and it reported ‘successfully installed’… so what’s up with that?”
^—— merits a separate topic, geared toward building a list of the “20 most common reasons why”

The healthy way forward, I believe, is for each of us to learn or re-learn a sense of self-reliance.
Learn to self-compile “stuff” rather than expecting, or hoping for, or asking for deb -packaged handouts.
Across the decade-long oldforum archives, I sense the antiX “culture” has drifted, away from individual self-reliance and toward bottle-feedings.
Thankfully, several among the “new crew” of forum participants have begun posting how-to writeups, inspiring a shift in the culture.

I see there are versions of programs that are not in the antix or debian repos that are available from PPA. A lot seem to be for Ubuntu 16.04 or its siblings that would be most likely to work for antix 17 was my guess.

I’m thinking the procedure should start with:
1. try to use something already in antix
2. add something from the antix repos

after that it gets fuzzy? use git? PPA? sourceforge? other repos? I guess I should avoid things that are too difficult to comprehend if I can’t just run it…

Can someone please suggest dos and don’t’s and procedures to follow?

It seems to me that if a PPA is like a repo, and its left there, the system is going to potentially install anything it finds from there when asked to install or update things. I also wonder how safe it is in terms of malicious intent, as well as susceptibility to accidental problems or conflict problems.

[Member rej]

Found the problem, maybe.

Pulseaudio is noted to be blacklisted by an application that I use which defaults to Alsa only.

Without it, the volume is perfect. Never had this issue with Pulseaudio and the app before, so never suspected it.

Since the release of the news regarding Specter and Meltdown, and reports of complications with kernel installs, I have Firejail setup to open immediately in MX17 and now in AntiX. Apparently it needs to not blacklist Pulseaudio. So Firejail will only access Alsa.

Would never have suspected Firejail was the issue because there is not a low/no volume problem in MX17 which also has Pulseaudio.

The only reason I discovered this was, yesterday, on a laptop freshly installed with X86 AntiX, set up with Firejail, the same way, there was no audio at all in Mozilla, yet in Chromium, there was audio. I use Chrome and Chromium, but to watch Netflix, need Firefox in 32bit. The Netflix page had a dialogue box that said it needs Pulseaudio, so I installed it. Now at least the video played, just with no sound. Both ran normally with sound outside of Firejail.

Searched the internet and saw a small note connecting Pulseaudio being blacklisted by Firejail. Could not find any files relating to this. And why would youtube videos x86 run Firejailed in Chrome, but not in Firefox- maybe FF uses different audio in 32bit?

In x64, both run in Firejail, just low volume. Both run perfectly outside of Firejail.

I have been researching how to fix this and have tried quite a few suggestions to no avail.

I want to continue to use Firejail but cannot find files to edit regarding blacklisting.

Any idea of where they would be located? Or if this is even where the problem might be?

[Anonymous]

Well, thanks for providing opportunity for me to post here that cautionary “Public Service Announcement” (already posted to MX forum).
I’ve tried to present “both sides”; the practice of trading security for convenience is arguably not an issue of right vs wrong.

Use of (installation of software from) PPAs merits the same caution
(accountability ~~ can you even determine the given name of person(s) uploading to a PPA repository?)
(trustworthiness ~~ is a given PPA hosted on secure infrastructure or, eeeeek!, a vulnerable shared-hosting webserver?)
yet across the linux ecosystem we can notice growing acceptance of their use.

Sadly, across distros, this naïveté is often at play behind-the-scenes as well.
A “package maintainer” (or user of a distro employing source-pased pkg management) conveniently clicks/runs a pkgbuild script
which oh-so-conveniently downloads from github|ppa|wherever and compiles and installs, or crams into an installable package.
Even if downloaded “via https, from a trusted source”, doesn’t each package maintainer take pride in fulfilling the role entrusted to them
by AT LEAST inspecting the configurable default preferences within the downloaded source package?
No, too often they do not; they engage in “trading security for convenience” due to time constraints — much work, and too few (volunteer) packagers.

[Member lucbertz]

I only want to understand antiX developers’ choice.

Anyway PCManFM now:
– supports tabs;
– gvfs is recommended but not mandatory;
– even if it is developed under LXDE project, it doesn’t have dependency on a desktop environment (at least apparently).
I saw this comparing https://packages.debian.org/stretch/i386/pcmanfm with https://packages.debian.org/stretch/i386/spacefm .

PCManFM is only GTK2 and probably it will be no longer evolved, due to PCManFM-QT under LXQT project.
But also SpaceFM project seems o be in a sort of dormant development status ( no changes since 2016 : https://github.com/IgnorantGuru/spacefm/releases ).

I used to be familiar with PCManFM because I come from lubuntu, but I can consider to switch to SpaceFM if I can see it’s in some way better.
So I will investigate in “a stupefying number of customization options”. 😉

Thank you.

[Member boombaby]

Hi, Anticapitalista…

somedumbname@someotherdumbname ~ $ inxi -r
Repos: Active apt sources in file: /etc/apt/sources.list.d/libreoffice-ppa-xenial.list
deb http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial main
deb-src http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial main
Active apt sources in file: /etc/apt/sources.list.d/official-package-repositories.list
deb http://packages.linuxmint.com serena main upstream import backport #id:linuxmint_main
deb http://archive.ubuntu.com/ubuntu xenial main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu xenial-updates main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu xenial-backports main restricted universe multiverse
deb http://security.ubuntu.com/ubuntu/ xenial-security main restricted universe multiverse
deb http://archive.canonical.com/ubuntu/ xenial partner
Active apt sources in file: /etc/apt/sources.list.d/vivaldi.list
deb http://repo.vivaldi.com/stable/deb/ stable main

Oops. Yes; I’m on Mint at the moment.
B.

• This reply was modified 5 years, 3 months ago by boombaby.

[Forum Admin Dave]

rej wrote:

The only problem I had a lot of trouble resolving on the new install, is auto-login. Wouldn’t do it through the regular route [control center-maintenence-user manager].

What worked: …….
=================================
As far as installing the “desktop-defaults-rox-antix 0.4.5” directory, I have either done it wrong or ……..
….this is the result:(E: Unable to correct problems, you have held broken packages.)- where are they? could not find any “broken packages” in synaptic

This may be not within-reason fixable.

[Mountbox result – below the panel entry (has been working all along).]

rj@antix17:~
$ su
Password:
root@antix17:/home/rj# =desktop-defaults-rox-antix 0.4.5
Reading package lists… Done
Building dependency tree
Reading state information… Done
Note, selecting ‘libghc-binary-prof-0.8.3.0-4351e’ for regex ‘0.4.5’
Note, selecting ‘libghc-vector-space-dev-0.10.4-5487b:i386’ for regex ‘0.4.5’
Note, selecting ‘libghc-pcap-dev-0.4.5.2-d01ab:i386’ for regex ‘0.4.5’
…. LONG LIST OF PACKAGES …….
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
libghc-appar-dev:i386 : Depends: libghc-base-dev-4.9.0.0-1bac3:i386
Depends: libghc-bytestring-dev-0.10.8.1-3ddfb:i386
…. LONG LIST OF PACKAGES …….
E: Unable to correct problems, you have held broken packages.
root@antix17:/home/rj#

==================
rj@antix17:~
$ su
Password:
root@antix17:/home/rj# apt-get install mountbox-antix:amd64 (0.1.5)
bash: syntax error near unexpected token `(‘
root@antix17:/home/rj#

The autologin settings in the control centre will not update lightdm; being designed and built to update the default slim should it? So your manual edit of /etc/lightdm/lightdm.conf to add the autologin lines is the correct way to do this. Could we add the ability for the autologin script to account for the installation of lightdm and set lightdm to autologin as well… Perhaps, should we also add to this for other login managers such as kdm, gdm and xdm? We could… however at what point is it considered outside of the intended design?

As to the missing desktop-defaults-rox-antix you can search for that in synaptic and reinstall it or type as root in terminal
apt-get -f install desktop-defaults-rox-antix
In terminal would probably be better as you can put the output here, but from what you posted above you tried to install half of the repo on a regex search! As you may notice is states
"Note, selecting ‘...Insert package name here...’ for regex ‘0.4.5’"
Likely from copying and pasting the version number “0.4.5” into the terminal along with the package name “desktop-defaults-rox-antix” in the apt-get command. It is hard to say because this
root@antix17:/home/rj# =desktop-defaults-rox-antix 0.4.5
does not make much sense to me. However
root@antix17:/home/rj# apt-get install mountbox-antix:amd64 (0.1.5)
Does and it should be
root@antix17:/home/rj# apt-get install mountbox-antix

I am not sure as I have not done the procedure of installing xfce on antiX lately (as MX now exists) but my guess would be to install antiX, update antiX
apt-get update && apt-get dist-upgrade
then in the package installer Control Centre -> System -> Package installer
Select Desktop Environment -> Check XFCE4 -> Press Install
Then Menu -> Desktop -> Other Desktops -> xfce

• This reply was modified 5 years, 3 months ago by Dave. Reason: Trimmed readout

Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown

[Member rej]

rj@antix17:~
$ sudo apt-cache policy desktop-defaults-rox-antix
[sudo] password for rj:
desktop-defaults-rox-antix:
Installed: (none)
Candidate: 0.4.5
Version table:
0.4.5 500
500 http://repo.antixlinux.com/stretch stretch/main amd64 Packages
500 http://repo.antixlinux.com/stretch stretch/main i386 Packages
100 /var/lib/dpkg/status
rj@antix17:~
$

Yes, I totally agree. Good advice.

And I did just that, but here’s the “however” – The new installation had some hiccups – most were easily resolvable, except for “auto-login” in Xfce desktop. On all 5 fresh installs I have since done, this same issue appears.

I “fixed” it so it would log-in, as I had this problem on the broken install also. This newest install did not fix so easily. It may have been because the apt-get update & ugrade was done right away – the only difference.

Here is what I wrote in the above post reply above:
—————————————————

Added these lines below as sudo nano
in:

lightdm-gtk-greeter.conf.d
and
lightdm/lightdm/conf.d /

added (as the 2 last lines in each file as sudo in nano editer):

autologin-user=rj
autologin-user-timeout=0

———————–
Added last 2 entries on both files – it worked and hoping it does not cause further problems from changing both files.

It was not necessary to change the “lightdm/lightdm/conf.d /“ file on the first broken original install (with no rox panel toggle) – only the “dm/lightdm-gtk-greeter.conf.d” file.

————————————————–
Made a snapshot before trying this. There are so many posts in various forums regarding Xfce auto-login issues, about how it was fixed for them. As you can see something that “works” – as with the broken install “fix” – which was apparently removing important directories, later surfaced as unfixable and would not work throughout the system. And maybe I am being a little too over-cautious now. It appears to be working quite well otherwise and I could take a chance and use just this one and see what the future brings with it.

Just wouldn’t want to load another broken installation over the existing ones on 5 machines, that is fraught with more hidden issues and will damage other files, if possible.

As far as the “broken installation” goes – just thought, if I knew what I did wrong, there would not be a repeat. You are right though – give it up and focus on the auto-login fix (it might be okay) on the new install – it is probably not going to snowball, but before loading it, I would like to attempt to be fairly certain. And maybe no-one knows the answer to this, except to try it.

I have been generously provided with enough (valuable and useful) information here, now and for anything that might be needed for the new install, to surmise that this missing panel and what is behind it, is not easily salvagable and would be a waste of time to keep trying.

This should probably be in a separate post regarding “Enable auto-login Xfce”, but if you have any insight into this auto-login fix, please let me know.

Thank you very much!

[Member rej]

Again thank you all for trying to resolve this for me.

If it had teeth…Can’t believe after rifling through loads of files, previous installed snapshots, settings, apps for searching, there it was right in front of my eyes.. So sorry I missed that! Not that I would have known what to do about it…

“There is more going on here than meets the eye” is very accurate.

Armed with all the information you have generously provided, I have put a completely fresh install on another computer to retrace my moves, make system comparisons and hope to see where I derailed it.

After fresh installation, before doing anything but setting wifi, I upgraded and updated, which was not done at first on the original install. The same issues turned up which were easily correctable – wifi, firewall, xscreensaver not starting. But the larger issue occured when switching desktops after installing Xfce. When I tried to log in – no go. Would not accept login password. Went back to IceWM and took a look in synaptic – which immediately, turned out the broken package – gvfs. On the previous install the gvfs problem did not turn up at that login point – it was later with using thunar and it was “backends”. Maybe because of the upgrade-update timing. However when I fixed it, the login worked and I could get to the Xfce desktop. And this is the point where I think I went wrong in the original (panel-missing install), after many tries at fixing, (as I cannot remember ever uninstalling anything besides Hexchat and Thunderbird – and that was in MX17), I must have been looking through desktop programs as a last ditch effort to make it work and somehow chose to uninstall this important directory and got Xfce to run by doing so, yet unknowingly missing features. I can’t find any records that I keep as I make changes regarding this and cannot remember doing this, but the evidence is quite clear.
======================

The only problem I had a lot of trouble resolving on the new install, is auto-login. Wouldn’t do it through the regular route [control center-maintenence-user manager].

What worked:

(attached files did not load correctly – tried to delete them and could not) added these lines below as sudo nano
in:

lightdm-gtk-greeter.conf.d
and
lightdm/lightdm/conf.d /

added (as the 2 last lines in each file as sudo in nano editer):

autologin-user=rj
autologin-user-timeout=0

———————–
Added last 2 entries on both files – it worked and hoping it does not cause further problems from having to change both.

I was not necessary to change the “lightdm/lightdm/conf.d / “ file on the first original (with no rox panel toggle) – only the “dm/lightdm-gtk-greeter.conf.d” file

I hope I have not yet again initiated more problems by doing so. I did make a snapshot prior, but don’t want to find down the road on 5 laptops that it is causing an issue(s) with something else.

=================================
As far as installing the “desktop-defaults-rox-antix 0.4.5” directory, I have either done it wrong or “There is more going on here than meets the eye” or both, as my skills at the terminal and understanding script and the terminology, are pretty limited to say the least – trying to improve that as I go along. But, this is the result:(E: Unable to correct problems, you have held broken packages.)- where are they? could not find any “broken packages” in synaptic

This may be not within-reason fixable.

[Mountbox result – below the panel entry (has been working all along).]

rj@antix17:~
$ su
Password:
root@antix17:/home/rj# =desktop-defaults-rox-antix 0.4.5
Reading package lists… Done
Building dependency tree
Reading state information… Done
Note, selecting ‘libghc-binary-prof-0.8.3.0-4351e’ for regex ‘0.4.5’
Note, selecting ‘libghc-vector-space-dev-0.10.4-5487b:i386’ for regex ‘0.4.5’
Note, selecting ‘libghc-pcap-dev-0.4.5.2-d01ab:i386’ for regex ‘0.4.5’
Note, selecting ‘libghc-pcap-prof-0.4.5.2-d01ab:i386’ for regex ‘0.4.5’
Note, selecting ‘libghc-tasty-dev-0.11.0.4-51977’ for regex ‘0.4.5’
Note, selecting ‘libghc-cassava-prof-0.4.5.0-e91f9:i386’ for regex ‘0.4.5’
Note, selecting ‘libghc-cassava-dev-0.4.5.0-e91f9:i386’ for regex ‘0.4.5’
Note, selecting ‘libghc-haskell-qrencode-dev-1.0.4-540dc:i386’ for regex ‘0.4.5’
Note, selecting ‘libghc-appar-prof-0.1.4-01465:i386’ for regex ‘0.4.5’
Note, selecting ‘libghc-binary-dev-0.8.3.0-4351e’ for regex ‘0.4.5’
Note, selecting ‘libghc-haskell-qrencode-prof-1.0.4-540dc:i386’ for regex ‘0.4.5’
Note, selecting ‘libghc-enumerator-dev-0.4.20-415f8’ for regex ‘0.4.5’
Note, selecting ‘libghc-cassava-prof-0.4.5.0-628f8’ for regex ‘0.4.5’
Note, selecting ‘libghc-enumerator-prof-0.4.20-415f8’ for regex ‘0.4.5’
Note, selecting ‘libghc-vector-space-prof-0.10.4-5487b:i386’ for regex ‘0.4.5’
Note, selecting ‘libghc-cassava-dev-0.4.5.0-628f8’ for regex ‘0.4.5’
Note, selecting ‘libghc-pcap-dev-0.4.5.2-3c791’ for regex ‘0.4.5’
Note, selecting ‘libghc-pcap-prof-0.4.5.2-3c791’ for regex ‘0.4.5’
Note, selecting ‘libghc-appar-dev-0.1.4-01465:i386’ for regex ‘0.4.5’
Note, selecting ‘libghc-tasty-prof-0.11.0.4-51977’ for regex ‘0.4.5’
Note, selecting ‘ghc’ instead of ‘libghc-binary-dev-0.8.3.0-4351e’
Note, selecting ‘ghc-prof’ instead of ‘libghc-binary-prof-0.8.3.0-4351e’
Note, selecting ‘libghc-enumerator-dev’ instead of ‘libghc-enumerator-dev-0.4.20-415f8’
Note, selecting ‘libghc-enumerator-prof’ instead of ‘libghc-enumerator-prof-0.4.20-415f8’
Note, selecting ‘libghc-cassava-dev’ instead of ‘libghc-cassava-dev-0.4.5.0-628f8’
Note, selecting ‘libghc-cassava-prof’ instead of ‘libghc-cassava-prof-0.4.5.0-628f8’
Note, selecting ‘libghc-pcap-dev’ instead of ‘libghc-pcap-dev-0.4.5.2-3c791’
Note, selecting ‘libghc-pcap-prof’ instead of ‘libghc-pcap-prof-0.4.5.2-3c791’
Note, selecting ‘libghc-tasty-dev’ instead of ‘libghc-tasty-dev-0.11.0.4-51977’
Note, selecting ‘libghc-tasty-prof’ instead of ‘libghc-tasty-prof-0.11.0.4-51977’
Note, selecting ‘libghc-appar-dev:i386’ instead of ‘libghc-appar-dev-0.1.4-01465:i386’
Note, selecting ‘libghc-appar-prof:i386’ instead of ‘libghc-appar-prof-0.1.4-01465:i386’
Note, selecting ‘libghc-cassava-dev:i386’ instead of ‘libghc-cassava-dev-0.4.5.0-e91f9:i386’
Note, selecting ‘libghc-cassava-prof:i386’ instead of ‘libghc-cassava-prof-0.4.5.0-e91f9:i386’
Note, selecting ‘libghc-pcap-dev:i386’ instead of ‘libghc-pcap-dev-0.4.5.2-d01ab:i386’
Note, selecting ‘libghc-pcap-prof:i386’ instead of ‘libghc-pcap-prof-0.4.5.2-d01ab:i386’
Note, selecting ‘libghc-vector-space-dev:i386’ instead of ‘libghc-vector-space-dev-0.10.4-5487b:i386’
Note, selecting ‘libghc-vector-space-prof:i386’ instead of ‘libghc-vector-space-prof-0.10.4-5487b:i386’
Note, selecting ‘libghc-qrencode-dev:i386’ instead of ‘libghc-haskell-qrencode-dev-1.0.4-540dc:i386’
Note, selecting ‘libghc-qrencode-prof:i386’ instead of ‘libghc-haskell-qrencode-prof-1.0.4-540dc:i386’
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
libghc-appar-dev:i386 : Depends: libghc-base-dev-4.9.0.0-1bac3:i386
Depends: libghc-bytestring-dev-0.10.8.1-3ddfb:i386
libghc-appar-prof:i386 : Depends: libghc-base-prof-4.9.0.0-1bac3:i386
Depends: libghc-bytestring-prof-0.10.8.1-3ddfb:i386
libghc-cassava-dev : Depends: libghc-attoparsec-dev-0.13.1.0-b6c9d
Depends: libghc-vector-dev-0.11.0.0-b15f0
Conflicts: libghc-cassava-dev:i386 but 0.4.5.0-3+b1 is to be installed
libghc-cassava-dev:i386 : Depends: libghc-array-dev-0.5.1.1-fa350:i386
Depends: libghc-attoparsec-dev-0.13.1.0-5b945:i386
Depends: libghc-base-dev-4.9.0.0-1bac3:i386
Depends: libghc-blaze-builder-dev-0.4.0.2-dec3a:i386
Depends: libghc-bytestring-dev-0.10.8.1-3ddfb:i386
Depends: libghc-containers-dev-0.5.7.1-0ba60:i386
Depends: libghc-deepseq-dev-1.4.2.0-4eba0:i386
Depends: libghc-hashable-dev-1.2.4.0-8ff6e:i386
Depends: libghc-text-dev-1.2.2.1-c3fe5:i386
Depends: libghc-unordered-containers-dev-0.2.7.1-97ad8:i386
Depends: libghc-vector-dev-0.11.0.0-e4dd3:i386
Conflicts: libghc-cassava-dev but 0.4.5.0-3+b1 is to be installed
libghc-cassava-prof : Depends: libghc-attoparsec-prof-0.13.1.0-b6c9d
Depends: libghc-vector-prof-0.11.0.0-b15f0
Conflicts: libghc-cassava-prof:i386 but 0.4.5.0-3+b1 is to be installed
libghc-cassava-prof:i386 : Depends: libghc-array-prof-0.5.1.1-fa350:i386
Depends: libghc-attoparsec-prof-0.13.1.0-5b945:i386
Depends: libghc-base-prof-4.9.0.0-1bac3:i386
Depends: libghc-blaze-builder-prof-0.4.0.2-dec3a:i386
Depends: libghc-bytestring-prof-0.10.8.1-3ddfb:i386
Depends: libghc-containers-prof-0.5.7.1-0ba60:i386
Depends: libghc-deepseq-prof-1.4.2.0-4eba0:i386
Depends: libghc-hashable-prof-1.2.4.0-8ff6e:i386
Depends: libghc-text-prof-1.2.2.1-c3fe5:i386
Depends: libghc-unordered-containers-prof-0.2.7.1-97ad8:i386
Depends: libghc-vector-prof-0.11.0.0-e4dd3:i386
Conflicts: libghc-cassava-prof but 0.4.5.0-3+b1 is to be installed
libghc-pcap-dev : Conflicts: libghc-pcap-dev:i386 but 0.4.5.2-11+b1 is to be installed
libghc-pcap-dev:i386 : Depends: libghc-base-dev-4.9.0.0-1bac3:i386
Depends: libghc-bytestring-dev-0.10.8.1-3ddfb:i386
Depends: libghc-network-dev-2.6.3.1-313d4:i386
Depends: libghc-time-dev-1.6.0.1-790c4:i386
Conflicts: libghc-pcap-dev but 0.4.5.2-11+b1 is to be installed
libghc-pcap-prof : Conflicts: libghc-pcap-prof:i386 but 0.4.5.2-11+b1 is to be installed
libghc-pcap-prof:i386 : Depends: libghc-base-prof-4.9.0.0-1bac3:i386
Depends: libghc-bytestring-prof-0.10.8.1-3ddfb:i386
Depends: libghc-network-prof-2.6.3.1-313d4:i386
Depends: libghc-time-prof-1.6.0.1-790c4:i386
Conflicts: libghc-pcap-prof but 0.4.5.2-11+b1 is to be installed
libghc-qrencode-dev:i386 : Depends: libghc-base-dev-4.9.0.0-1bac3:i386
Depends: libghc-bytestring-dev-0.10.8.1-3ddfb:i386
libghc-qrencode-prof:i386 : Depends: libghc-base-prof-4.9.0.0-1bac3:i386
Depends: libghc-bytestring-prof-0.10.8.1-3ddfb:i386
libghc-vector-space-dev:i386 : Depends: libghc-boolean-dev-0.2.3-b3626:i386
Depends: libghc-memotrie-dev-0.6.7-650a7:i386
Depends: libghc-numinstances-dev-1.4-76c23:i386
Depends: libghc-base-dev-4.9.0.0-1bac3:i386
libghc-vector-space-prof:i386 : Depends: libghc-boolean-prof-0.2.3-b3626:i386
Depends: libghc-memotrie-prof-0.6.7-650a7:i386
Depends: libghc-numinstances-prof-1.4-76c23:i386
Depends: libghc-base-prof-4.9.0.0-1bac3:i386
E: Unable to correct problems, you have held broken packages.
root@antix17:/home/rj#

==================
rj@antix17:~
$ su
Password:
root@antix17:/home/rj# apt-get install mountbox-antix:amd64 (0.1.5)
bash: syntax error near unexpected token `(‘
root@antix17:/home/rj#

• This reply was modified 5 years, 3 months ago by rej.
• This reply was modified 5 years, 3 months ago by rej.
• This reply was modified 5 years, 3 months ago by rej. Reason: to remove notation re attachment deletion

[Member mizpa]

synclient apparently isn’t available, since a search in the package manager, as well as trying to get that package at a terminal is not available (cant find synclient.) I was able to download the document on it from the internet tho. So is there a fancy name for it other than synclient?