- This topic has 35 replies, 5 voices, and was last updated Nov 30-3:23 pm by caprea.
-
Posts
-
rej
Hi-
While installing indicator-keylock (posted Nov 2. 2022 #92119 – “Keylock Indicator? [solved]”), I noticed that in exchange, it removed some other applications – Redshift, Clipit, and PAsystray.
The following package was automatically installed and is no longer required: redshift Use 'sudo apt autoremove' to remove it. The following packages will be REMOVED: clipit gir1.2-ayatanaappindicator3-0.1 libayatana-appindicator3-1 pasystray redshift-gtk The following NEW packages will be installed: libappindicator3-1 0 upgraded, 1 newly installed, 5 to remove and 0 not upgraded. Need to get 0 B/53.5 kB of archives. After this operation, 1,388 kB disk space will be freed. Do you want to continue? [Y/n] Get:1 /home/rj/libappindicator3-1_0.4.92-7_amd64.deb libappindicator3-1 amd64 0.4.92-7 [53.5 kB] (Reading database ... 265994 files and directories currently installed.) Removing clipit (1.4.4+git20190202-2.0antix1) ... Removing redshift-gtk (1.12-4.2) ... Removing gir1.2-ayatanaappindicator3-0.1 (0.5.5-2+deb11u2) ... Removing pasystray (0.7.1-1) ... Removing libayatana-appindicator3-1 (0.5.5-2+deb11u2) ...It appears that Alsamixer no longer has pre-amp setting and PAsystray is an application for bumping up the volume on laptops that speakers with low sound levels.
Aside from pre-amp and PAsystray, is there some other option for volume control?
Thank you.
sybok
I am afraid I can ask questions but do not have the answers.
1) If you open alsamixer (a terminal pops up), did you press ‘F5’ (to show ‘All’)?
2) Are there any other sound cards available (and having effect when playing audio)?
3) Could you post a screenshot of the terminal with alsamixer after having pressed ‘F5’?
4) Is ‘pulseaudio’ installed (and activated/running)?My instance alsamixer (antiX-21, testing, ‘pulseaudio’ installed and used) does not show pre-amp as well.
Tip: You may check pulseaudio running via ‘pgrep pulseaudio’. It returns its pid if it is running, else: nothing.
caprea
posted Nov 2. 2022 #92119 – “Keylock Indicator? [solved]
This is the thread you are referring to here
https://www.antixforum.com/forums/topic/keylock-indicator/caprea
Hi Rey, I just installed indicator-keylock from MX-repos on antiX21 and did it the way I’m used to.
Enabling the MX-repos in /etc/apt/sources.list.d/various.list
by adding the lines
#MX-repos
deb http://mxrepo.com/mx/repo/ bullseye main non-freethen sudo apt update the system and installing indicator-keylock .And afterwards, very important, outcommenting or deleting the MX-lines.
During the installation of indicator-keylock it did not only install libindicator3-7:amd64 (0.5.0-4~mx21+1)
and libappindicator3-1:amd64 (0.4.92-8~mx21+1)
but also upgraded libayatana-appindicator3-1:amd64 to the MX-version libayatana-appindicator3-1:amd64 (0.5.5-2+mx21+1)Nothing was removed.
If I was in your shoes I wouldn’t bother with trying to patch up the dependency problems now.
A solution should bedeinstall the indicator-keylock and also libindicator3-7 and libappindicator3-1
reinstall the removed packages:
clipit gir1.2-ayatanaappindicator3-0.1
libayatana-appindicator3-1 pasystray redshift-gtkAfterwards install indicator-keylock the way described above, by adding the MX-repos just for the one installation.But for heaven’s sake don’t forget to remove the MX repo again afterwards.
Or install it by downloading the debs and installing them manually.Two you have already downloaded, but you need also
libayatana-appindicator3-1:amd64(0.5.5-2+mx21+1)
which you have to install first.If I wasn’t clear enough or something is not going as it should, just ask again.
Thank you sybok – Alsa has no pre-amp on the install boot media either. I have HDMI and PCH sound cards. Firefox sound only works with PCH sound card. Yes, Pulseaudio is what runs PAsytray.
——————
Hi caprea-That is the thread.
Your very last suggestion “downloading the mx debs and installing them manually” – I tried locating “libayatana-appindicator3-1:amd64(0.5.5-2+mx21+1)” online to download, with no success. Can you give me a link?
While reinstalling Redshift, Clipit, and PAsystray, it automatically removed indicator-keylock and dependencies – then ran apt autoremove.
Something went wrong with my MXRepo install – seemed pretty simple, but I must have taken a left somewhere – attachment is the image of the results.
Thank you for your help!
Attachments:
caprea
Here’s a link for libayatana-appindicator3-1 0.5.5-2+mx21+1 amd64.deb
http://mxrepo.com/mx/repo/pool/main/liba/libayatana-appindicator/Not sure what goes wrong with the MX-repo on your side.
Same lines are here in my various.list file working.# liquorix kernel #deb http://liquorix.net/debian/ sid main #MX-repos deb http://mxrepo.com/mx/repo/ bullseye main non-freeEdit:
This error message from your terminal is showing if main non-free is missing in the line- This reply was modified 5 months, 1 week ago by caprea.
caprea –
Hi – tried to post a reply, but it did not appear, then tried again and it said it was a duplicate, The second one I attached an image to, but neither appears and I have not found a way to fix it, or view it. If I try posting it again, it will again tell me that I already said that and it is a duplicate, so it is stuck…
caprea –
Thanks for the link – I got the file and am still coming up with an error. The attached image is of the (hopefully correct) packages installed and the error the package installer gave.
RE:
“Edit:
This error message from your terminal is showing if main non-free is missing in the line”The previous attached image contains the line added to the files which has “non-free” in it.
Do I need a key to enable the MXrepo?
My installation is the “full x64”, but as an experiment with the original boot media and updating the antiX 21 “full x64” and “base x64” boot install media, I tried to enable the MXrepo to it and this was the output in terminal [these are not installed on hardware]:
full x64:
demo@antix1:~ $ sudo apt update Hit:1 http://ftp.us.debian.org/debian bullseye-updates InRelease Hit:2 http://deb.debian.org/debian bullseye-backports InRelease Hit:3 http://security.debian.org bullseye-security InRelease Hit:4 http://la.mxrepo.com/antix/bullseye bullseye InRelease Get:5 http://mxrepo.com/mx/repo bullseye InRelease [19.9 kB] Hit:6 http://ftp.de.debian.org/debian bullseye InRelease Err:5 http://mxrepo.com/mx/repo bullseye InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY F942E0D4E1C726CD Reading package lists... Done W: GPG error: http://mxrepo.com/mx/repo bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY F942E0D4E1C726CD E: The repository 'http://mxrepo.com/mx/repo bullseye InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. demo@antix1:~ $Updated and installed Synaptic “antiX 21 “base x64” install boot media – again, tried to enable MX repo.
Terminal output:
demo@antix1:~ $ sudo apt update Get:1 http://deb.debian.org/debian bullseye-backports InRelease [49.0 kB] Hit:2 http://security.debian.org bullseye-security InRelease Get:3 http://mxrepo.com/mx/repo bullseye InRelease [19.9 kB] Hit:4 http://la.mxrepo.com/antix/bullseye bullseye InRelease Hit:5 http://ftp.de.debian.org/debian bullseye InRelease Get:6 http://deb.debian.org/debian bullseye-backports/main amd64 Packages [363 kB] Err:3 http://mxrepo.com/mx/repo bullseye InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY F942E0D4E1C726CD Get:7 http://deb.debian.org/debian bullseye-backports/main i386 Packages [361 kB] Get:8 http://deb.debian.org/debian bullseye-backports/main Translation-en [299 kB] Get:9 http://deb.debian.org/debian bullseye-backports/contrib i386 Packages [3,988 B] Get:10 http://deb.debian.org/debian bullseye-backports/contrib amd64 Packages [4,400 B] Get:11 http://deb.debian.org/debian bullseye-backports/contrib Translation-en [4,320 B] Get:12 http://deb.debian.org/debian bullseye-backports/non-free amd64 Packages [14.3 kB] Get:13 http://deb.debian.org/debian bullseye-backports/non-free i386 Packages [12.8 kB] Get:14 http://deb.debian.org/debian bullseye-backports/non-free Translation-en [26.6 kB] Hit:15 http://ftp.us.debian.org/debian bullseye-updates InRelease Reading package lists... Done W: GPG error: http://mxrepo.com/mx/repo bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY F942E0D4E1C726CD E: The repository 'http://mxrepo.com/mx/repo bullseye InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. demo@antix1:~ $ sudo apt-get update Hit:1 http://deb.debian.org/debian bullseye-backports InRelease Hit:2 http://security.debian.org bullseye-security InRelease Hit:3 http://la.mxrepo.com/antix/bullseye bullseye InRelease Hit:4 http://ftp.us.debian.org/debian bullseye-updates InRelease Hit:5 http://ftp.de.debian.org/debian bullseye InRelease Get:6 http://mxrepo.com/mx/repo bullseye InRelease [19.9 kB] Err:6 http://mxrepo.com/mx/repo bullseye InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY F942E0D4E1C726CD Reading package lists... Done W: GPG error: http://mxrepo.com/mx/repo bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY F942E0D4E1C726CD E: The repository 'http://mxrepo.com/mx/repo bullseye InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. demo@antix1:~ $- This reply was modified 5 months, 1 week ago by caprea.
- This reply was modified 5 months, 1 week ago by rej.
Attachments:
caprea
Yes, you need a gpg key. Sorry, I completely forgot about that because it’s been a while since I added the repo.
Easiest way is to install the package checkaptgpg-antix
Afterwards run it from terminal with
sudo checkaptgpg
It will fetch the key for you.Please don’t forget to outcomment the MX-repo line in the various list after you installed your indicator-keylock package.
Edit:Your reply was caught by the forum software, but could be freed.
Edit2: Which package-installer is it, is it gdebi? gdebi had various problems on antiX.The problem could also be due to the order of the installations.Also for libindicator 3-7 on my antiX21 system it installed
libindicator3-7:amd64 0.5.0-4~mx21+1- This reply was modified 5 months, 1 week ago by caprea.
- This reply was modified 5 months, 1 week ago by caprea.
I used gdebi and have noticed some bugs in it lately – mainly with opening files.
Would there an alternate way to get a key? It said “command not found”.
Thanks for the reminder – I won’t forget to either remove the line entirely or comment it out after the app is installed.
Attachments:
caprea
sudo checkaptgpg && sudo apt updateMaybe I have left something out or should not have put the code in the various.list before asking for the key?
I downloaded a package from this site and successfully installed it, only to get the same terminal response “command not found” from “sudo checkaptgpg && sudo apt update”. So I might have to enable it some other way or maybe I should not have done that? I can reload my system snapshot and undo it all
url:
http://mxrepo.com/mx/repo/pool/main/m/mx-gpg-keys/
package:
mx-gpg-keys_22.11.11_all.deb 2022-11-11 08:44 10K
Attachments:
caprea
The installation of the key should be enough. There’s no need for checkupgpg then..
Can you now update the system with the MX-repo enabled and install the indicator-keylock ?No – I think it might need to be enabled, once installed, but I searched online and found some complicated instructions for ubuntu and don’t know if they apply to antiX, but I would need the number to fix it anyway.
Attachments:
- You must be logged in to reply to this topic.
