Search Results for 'ppa'

[Anonymous]

oops, are you unable to boot?
If not, your post doesn’t belong in this topic, yes?

From your pasted content, I see no “issue”.
You have apparently “gone looking for trouble (dmesg -k -l emerg,alert,crit,err,warn)” and have not websearched the output result(s) to understand what each of those lines indicates. If you’re averse to loading proprietary-licenced wl driver, blacklist it. Maybe you’ll lose wi-fi functionality but, hey, at least the “tainted kernel issue” would be solved…

[Member eugen-b]

anticapitalista wrote:

skidoo – the icon set is awful on fluxbox, I agree.
fluxbox must use png icons (or none) and there aren’t any ‘modern’ ones available.
If anyone has a better suggestion, please post (with a picture if possible)
(Faenza instead of Numix!)

I used to have Square-Beam icons on Fluxbox, JWM and Openbox. I used them exactly because they have many sizes in PNG format. This is good for fluxbox and saves a bit of RAM (about 10MB IIRC).
https://www.gnome-look.org/content/show.php/Square-Beam?content=165094
https://www.noobslab.com/2015/08/square-beam-icon-suite-looks-great-with.html
http://ppa.launchpad.net/noobslab/icons/ubuntu/pool/main/s/square-beam-icons/

• This reply was modified 4 years ago by eugen-b.

AFAICT, nothing currently passes -r or –root when calling desktop-defaults-run
and
the latter case is contrary to “lean and mean” ~~ it unnecessarily causes an intermediary gksu process to run throughout the duration of each launched item. 3x, 5x, 8x instances of items launched into “default terminal” and/or “default editor” winds up consuming an extra 35-50Mb for naught.

  #IFS="|"
if [ -z "$args" ]; then xtraargs=""; fi
if [ "$exec_root" = 1 ]; then
	gksu -u root "$Exec $xtraargs $args" 2>/dev/null &
	exit
else
	echo "$Exec $xtraargs $args"
	gksu -u $(whoami) "$Exec $xtraargs $args" 2>/dev/null &
	exit
fi

Is there _ever_ a valid reason, a valid use case for invoking
gksu -u demo desktop-defaults-run -b
( if there is, apparently I’m blind to it )
.

“-u myself” will not be supported in the forthcoming gksu version.
and “-u root” will similarly fail ~~ implicitly, invariably, ALL calls to gksu (and/or gksudo)
will invoke sudo to launch a requested program with elevated privileges.
(restated, for clarity: the -u option is deprecated)

Please test and confirm ~~ even under the current version of gksu, “-u root” is superfluous
gksu -u root “$Exec $xtraargs $args” 2>/dev/null &

^— If the result is equally effective, is identical, with or without explicitly passing the “-u root” option
the “-u root” can be removed (now, already) from existing commandstrings which invoke gksu.

[Anonymous]

Any quick way of upgrading individual apps?

Yup! You simply install and use Windows! There you need to update each and every single app individually. 😉

Seriously, it very much depends about on how did you install your app. Usually, there’s no way at all to upgrade a single app because of the all dependencies.

In ‘normal’ case, in Linux you’d install your apps through the repository which means, you’re getting the version that’s in repository and not the newest.

For example, the newest version of some app SOME_APP is on version 6.0.4 but you’re still using/getting the version 5.2.2 out of the repositories.

If you always want the newest versions of apps, you’ll not use Linux on the first place and if you do, you’ll not use anything Debian based.

Sometimes, you can get some apps directly from the developers website, like Telegram, for example. That’s the best way to get the apps.

Then, all you need is, download, unpack and run — the app itself will take care about all the rest (incl. updates/upgrades).

In case you’re installing the same app from the Distro repositories, you’ll be a couple of versions behind.

That’s why the PPA’s and recently AppImage, FlatPak and Snaps are getting so popular.

Every OS has it’s own advantages and disadvantages.

[Anonymous]

This example is pretty innocuous ~~ probably caused no widespread system breakage,
but what you are experiencing, first-hand, is an example of “why not add PPAs?”
aka
“why not install any ole’ stuff from sources other than the official repositories?”

Read the error output you pasted, beginning with the bottommost line, upward.
If you read it slowly, carefully (may need to websearch any unfamiliar term(s) mentioned)
you will discover that python is very good about telling us EXACTLY what the problem is, right down to the detail of which specific line within a specific file.

In a text editor, if you examine
aqt/qt.py
and
/home/dae/Local/py512/lib/python3.6/site-packages/PyInstaller/loader/pyimod03_importers.py
at the lines referenced in the error message
you can discover what exact operation is expecting presence of a libsystemd component.
Which component? idunno.
Can you workaround, maybe outcomment or edit a few lines toward disabling only the problematic operation? idunno.
Is it worth the effort to hack the program toward rendering it usable in the absence of libsystemd? I dunno.

Instead of wrestling with it, you might consider installing an older version of Anki (in which the libsystemd dependency did not yet exist)
https://apps.ankiweb.net/downloads/archive/

I take it I’m missing some Python stuff in there somewhere.

The pasted errors do not mention any missing python libraries (modules), so we probably shouldn’t jump to that conclusion.

[Member stevesr0]

Today, many forum links seem not to work for me. No “404”, just can’t find that site. Using two different computers and no apparent dns problem.

I want to download 17.4.1 for a live usb for a new computer, so this is kind of bad…

Anyone else having problem downloading iso?

(I haven’t gone to “outside” sites (sourceforge); I prefer to stick with the “official” download sites.

hope this clears up soon.

stevesr0

[Anonymous]

Sorry, but I don’t think I’m gonna make it on this one.
Searches on forums only give me a lot of inxi and command, not always the same, there is nothing clear and precise, and I don’t know how to add a ppa to antix because debian is new to me, and I only found samsung-tools packages for ubuntu, I installed one (for bionic) but nothing works.
However I know samsung-tools on ubuntu & co, I have always used it without problems, but on antix it is another story apparently. Nothing in synaptic, that’s why I posted on this forum.
Anyway…… I give up, and I leave my luminosity as it is. Maybe I will find a solution later.
Thanks for your help;)

[Anonymous]

websearch “linux samsung R520/R522/R620 backlight”
first search result was an Ubuntu Forums topic Solutions for Samsung Laptop problems (Backlight, Sleep, Keyboard issues, Hotkeys)
plenty of other matching search results.

So, it’s a known issue, and is an issue observed across various linux distributions, and apparently (i.e. I didn’t continue reading the websearch results on your behalf) one or more solutions do exist.

Hi, All!

Thing is, I’ve got an ASUS X55U that I would like to put antiX on. I’ve tried a couple of times. It looked like it was working, until I tried to boot it up. All I got was the BIOS giving me some sort of invalid hard drive or drive access message.

This particular make and model was made just as that UEFI business was coming out, so I think the BIOS is a bit fiddly compared to others. And when I did try to install antiX the first time I got a message in the installation process that the hard drive wasn’t in very good shape. So, I bought me a solid state drive (on sale at a good price) to try and extend the life of this older machine. Unfortunately, got the same result; some sort of drive error message when I tried booting it up without the live USB installer.

Just in case it matters, the live boot on a USB stick works just fine.

Could someone tell me what I might be missing? I tried installing antiX using the MBR thing when asked where I wanted the boot loader. I thought that would work, but apparently not in this case. I’m sure I’m missing something in the installation problem that should be obvious. But I just can’t see it.

Any helpful advice would be much appreciated.

Let me know if it would help to have some sort of input from the computer itself.

Thanks in advance!

• This topic was modified 4 years, 1 month ago by Mynaardt.

What have the Romans ever done for us?
Apart from: sanitation, medicine, education, wine, public order, irrigation, roads, fresh water, and public health?

[Anonymous]

The debian project formally publishes ReleaseNotes for each version.
Currently, the buster document, ReleaseNotes section 5.1.2: noteworthy-obsolete-packages
it mentions keepass2 …and omits mentioning synaptic.
Suuuuure, no one will notice, no one will care, because synaptic doesn’t merit “noteworthy package” status?!?

The apparent point of view by Debian Gnome Team:
Technically it’s not “obsolete”, rather it has just been relegated to testing/unstable… so we’re not obliged to mention it.

I tried today to install antix 17.4 as a frugal install alongside Windows 7. Windows is in /dev/sda2 and antix in /dev/sda3 (sda1 is reserved for Dell). The drive is 500 gb. I selected F5 then chose Frugal_Persist from the menu. The frugal install completed with no apparent errors, but it never installed a bootloader. I can boot from usb with no problem, without the usb, it simply boots into Windows. Is there a way to manually install grub or is there an issue with the installer?

[Forum Admin BitJam]

seaken64 wrote:

I started with an 8GB Live USB and chose Persist-all. When the persist routine ran I chose 5GB for root and 1GB for home. I later did an dist-upgrade and I was going to do a remaster after the upgrade. But I’m getting a size error:

“Have: 368 megs available Need: 831”

This makes sense. I have an easy solution for you.

SpaceFM says I have 4.7GB free on the disk. But the rootfs is 5.0G and homefs is 1024.0M and linuxfs is 965.6M.

Different programs have different ideas of what “free space” means. You can see the difference with these two commands:

sudo du -sch /live/boot-dev
sudo du -sch --apparent-size /live/boot-dev

The difference is because we create rootfs and homefs as sparse files. The first command reports only the amount of space that has been used in these files. The 2nd one reports the “actual” size of the file even if all the space in the file system has not yet been used. We use the 2nd, otherwise it would be really easy to run out of space inside your rootfs file before all the space allocated was used. This would be bad. Trust me.

The simple solution is to boot with persistence *disabled* and then download and use the version of live-usb-maker from my git repo: https://github.com/BitJam/live-usb-maker When you clone with this version, it will copy the persistence files as long as they are not in use. This feature was added to help people who are the bind you find yourself. They need more room to do a remaster but they don’t want to lose their changes in persistence.

You need to disable persistence (or only use dynamic root persistence) to use this feature because we will not copy an active file system because that would be a bad thing to do.

HTH

• This reply was modified 4 years, 1 month ago by BitJam.

Context is worth 80 IQ points -- Alan Kay

[Member seaken64]

I experimented with two separate LiveUSB drives. One is a drive I’ve had for awhile and was started with antiX-17. The second is new and using the current 17.3.1. Both are 32-bit and installed on 8Gb USB with persistence. The older one is set to persist-all. The newer one is set to persist-static. The older drive gives an error when booted on a computer with less than 2Gb of RAM but I choose to “C”ontinue and it continues to boot with no apparent problems. (I’m assuming it uses a general static file instead of the root persistance file. But I don’t really know this).

I have several computers that have a Broadcom ethernet or Wifi adapter. Sometimes the LiveUSB does not detect either the ethernet or wireless adapter. I noticed that with my older LiveUSB it detects the wireless on one of my computers where the new one does not. But that same older USB does not detect the ethernet on a computer I have not tried it on yet. Once when I setup the blacklist file correctly and manually entered the correct driver using the modprobe command the wifi networking came to life.

After shutting down I looked at the saved state files and I can see the settings are saved for each machine. I put it in another machine and that machine also gets it’s own settings files. When I put the older USB back in a machine it has already been in, and reboot, the network does not start automatically. But I can run Ceni and reconfigure and it works. This may be because the root persistance file is not loaded if I have to enter “C” to continue.

On the Ceni screen is a list of Logical Interfaces in the lower right portion of the Ceni screen. On the older USB this list includes at least two logical names that do not hold to the typical “wlanx” naming scheme. They are named wlx001nnnnnnnnn and wlx002nnnnnnnnn where the n’s are a bunch of letters and numbers. There is also eth1, eth2, eth3, and wlan2. On the new USB that list has eth0, eth3, wlan1, wlan2 and wlan3.

I do usually get the network interface to be either eth0, eth1, or wlan0 or wlan1. On some of my computers I have two ethernet adapters or two wireless adapters. On one laptop I have a third adapter named wmx1 assigned as ethernet.

So I get that the persistance routines are saving settings for each machine and that the interface is usually named eth0 or wlan0. But it does not seem to always work out that way. I have had both eth3 and wlan2 used. I can’t say it was not me who made that assignment. I may have played with selecting one of those Logical Devices from the list in an attempt to get the networking on when it didn’t happen automatically. But I don’t recall doing that or being successful at assigning one of those ID’s. All I can say is I have had eth3 or wlan2 and they do not show on the Conky by default.

It is not a problem. I have figured out a way to deal with it if the interface does not come up automatically or gets a device name other than the standard four ID’s. What I was hoping for was a more dynamic indicator on either the Conky or the task bar that will show whatever ID is in play. I haven’t found such a widget yet. As long as I get one of the four device ID’s used by Conky I don’t need to worry about it. I will try to pay closer attention in the future as to what I did that may have led to an eth3 or wlan2 ID assignment. I am curious as to how those non-standard Logical interface ID’s got on the Ceni list. Where did they come from?

Seaken64

[Member pourpier]

anticapitalista wrote:

Use ceni to set up networking again and see if it survives a reboot.

This is exactly what I am doing but I have to do it each time.
Apparently the system doesn’t keep that information permanently.
I don’t have that issue on MX.
Cheers

Hello
When I did an update yesterday I got the message that some URL doesn’t have any Release file on it.
I checked the URL and saw that now there is a folder packages between the folder mx and the folder antix which wasn’t the case before.
I did edit the sources but I wanted to mention this here for some new users who might have the same issue.
Another very annoying issue is that each time I shut the computer down and I reboot I have to configure the network interfaces as everything apparently was flushed when I do the shutdown.
Cheers,
pourpier