You are not logged in.
It does not get any more "layman's" than that ...
A.
Look above your post, I got it working.
But it looks like crap.
Well, I got it working, had to enable Vt in the bios. But it looks like crap. I don't know if it's because my machine is old (I think it's over 10 years old) or what.
I just installed VirtualBox. I never used it before (and don't really know what I'm doing) and I'm getting an error. The error is:
VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED).
Result Code: NS_ERROR_FAILURE (0X80004005)
Component: ConsoleWrap
Interface: IConsole {6ac83d89-6ee7-4e33-8ae6-b257b2e81be8}
Can anybody tell me what this means in layman's English, and does anybody know what I need to do to fix this? If it matters, I'm trying to run Windows 7 as the guest.
Thanks.
I don't know much about this but maybe what you want works in the search engine Mojeek?
A reboot seems to have fixed the volume button problem. Thanks again for the fix.
Welcome back. A year or so ago I used this post to enable a USB headset.
It works as far as now hearing the sound, so thanks for that, but, neither the volume control on the speakers nor the main system volume button works. I have to use the app's volume control to adjust volume. Is there anything that can be done to get these volume controls to work?
Greetings everyone. So I've been out of my country for about 10 months, without use of my computer. After arriving back, I installed all the updates for the last 10 months, and also had to buy some new computer speakers. I got inexpensive logitech which connects via USB. My problem is that I'm getting no sound. The speakers are being powered, so that's not the problem. The volume of the speakers are up, so that's not the problem either. I poked around in Sound Preferences but nothing I do there fixes the problem. Under the tab Output, it says Choose a device for sound output, and I see an option that says USB Audio, I check that, but it doesn't stick neither does it fix the sound. Do I need to buy a USB to audio 3.5 adapter?
Not sure if this is pertinent, but with my last pair of speakers, which had a 3.5mm audio jack, I was getting a popping sound, so someone gave me this fix below. Can this somehow be causing this problem?
Okay...I may have found an answer for your popping sound.
1. Open your terminal, and enter the following command as root (su or sudo). I'm assuming that you use Pluma as your text editor. If not, substitute Pluma with whatever text editor you do use.
sudo pluma /etc/modprobe.d/alsa.conf
Here's all that is in that file on my system, and I don't get the popping noise...
options snd_hda_intel index=1,0
2. This is the fix that a lot of people said worked for them. Add the following line to the alsa.conf file...
options snd-hda-intel power_save=0 power_save_controller=N
3. If that doesn't work for some reason, create another file in /etc/modprobe.d/ and name it...
alsa-base.conf
...and add that line in step 2 to that file.
I don't know if you'll need to reboot or not, but I'm guessing you may have to.
Good luck!
They look good to me Ron...
Thanks MiyoLinux.
I'm confused by this post. This is what my sources.list looks like. Do I need to remove any of the " #'s "? I have been getting security updates (at least for some things).
deb http://deb.devuan.org/merged/ chimaera main non-free contrib
# deb-src http://deb.devuan.org/merged/ chimaera main non-free contrib
deb http://deb.devuan.org/merged/ chimaera-security non-free contrib main
# deb-src http://deb.devuan.org/merged/ chimaera-security non-free contrib main
# chimaera-updates, to get updates before a point release is made;
# see https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_updates_and_backports
deb http://deb.devuan.org/merged/ chimaera-updates main contrib non-free
# deb-src http://deb.devuan.org/merged/ chimaera-updates main contrib non-free
# chimaera-backports, previously on backports.debian.org
deb http://deb.devuan.org/merged/ chimaera-backports main contrib non-free
# deb-src http://deb.devuan.org/merged/ chimaera-backports main contrib non-free
I wonder how it compares with Protonmail.
That's my biggest wonder as Protonmail is what I currently use.
Thanks for checking it out. You created a new account just to check it out? That is above and beyond the call of duty.
I'm thinking about switching my email. Does anybody here use swisscows? Thoughts on it? Thanks.
I think so, yes.
Great. I will mark as solved. Thanks once again HoaS for your help. Thanks also to aitor; your way did stop Synaptic from updating it.
Check
While waiting for your reply, I went ahead and deleted the preferences folder I created with that file in it, and kept the file you recommend in preferences.d, then rebooted. Synaptic is still showing the old version of sudoku I use as the latest version. I also checked apt update and apt policy gnome-sudoku and that checked out good also. So I guess all is well??
Looks good to me :-)
Great. Just one more thing. Now this is what I get in Synaptic. It shows the old version that I use as the latest version. Does this mean I can undo the first thing I did earlier? Or should I just leave well enough alone?
I added the file you said. I changed the version from what you wrote to this 1:3.22.2-1 because this is the version I'm using. I ran the commands and this is what happened:
ron@ron:~$ sudo apt update
[sudo] password for ron:
Hit:1 http://deb.devuan.org/merged chimaera InRelease
Get:2 http://deb.devuan.org/merged chimaera-security InRelease [21.5 kB]
Hit:3 http://deb.devuan.org/merged chimaera-updates InRelease
Hit:4 http://deb.devuan.org/merged chimaera-backports InRelease
Fetched 21.5 kB in 3s (7,144 B/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
ron@ron:~$ apt policy gnome-sudoku
gnome-sudoku:
Installed: 1:3.22.2-1
Candidate: 1:3.22.2-1
Version table:
1:3.38.0-1 500
500 http://deb.devuan.org/merged chimaera/main amd64 Packages
*** 1:3.22.2-1 501
100 /var/lib/dpkg/statu
Is everything now correct?
There is no pinning for that package. If you run apt update followed by apt list --upgradable I think gnome-sudoku will still be marked for upgrade to the chimaera version.
I only update via Synaptic, and here's what happens in it. It doesn't get updated. But are you saying if I do an update via the terminal it will get updated?
This is what I got from your commands:
ron@ron:~$ sudo apt update
[sudo] password for ron:
Hit:1 http://deb.devuan.org/merged chimaera InRelease
Get:2 http://deb.devuan.org/merged chimaera-security InRelease [21.5 kB]
Hit:3 http://deb.devuan.org/merged chimaera-updates InRelease
Hit:4 http://deb.devuan.org/merged chimaera-backports InRelease
Fetched 21.5 kB in 2s (9,148 B/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it.
ron@ron:~$ apt list --upgradable
Listing... Done
gnome-sudoku/stable 1:3.38.0-1 amd64 [upgradable from: 1:3.22.2-1]
N: There is 1 additional version. Please use the '-a' switch to see it
Either location should work.
Check the pinning with
apt policy apt policy gnome-sudoku
I would consider running the program from a chroot because pinning makes me nervous but that would take significantly more disk space.
Here's the output:
$ apt policy
Package files:
100 /var/lib/dpkg/status
release a=now
100 http://deb.devuan.org/merged chimaera-backports/non-free amd64 Packages
release v=4.0,o=Devuan Backports,a=stable-backports,n=chimaera-backports,l=Devuan Backports,c=non-free,b=amd64
origin deb.devuan.org
100 http://deb.devuan.org/merged chimaera-backports/contrib amd64 Packages
release v=4.0,o=Devuan Backports,a=stable-backports,n=chimaera-backports,l=Devuan Backports,c=contrib,b=amd64
origin deb.devuan.org
100 http://deb.devuan.org/merged chimaera-backports/main amd64 Packages
release v=4.0,o=Devuan Backports,a=stable-backports,n=chimaera-backports,l=Devuan Backports,c=main,b=amd64
origin deb.devuan.org
500 http://deb.devuan.org/merged chimaera-updates/main amd64 Packages
release v=4.0.0,o=Devuan,a=stable-updates,n=chimaera-updates,l=Devuan,c=main,b=amd64
origin deb.devuan.org
500 http://deb.devuan.org/merged chimaera-security/main amd64 Packages
release v=4.0,o=Devuan,a=stable-security,n=chimaera-security,l=Devuan-Security,c=main,b=amd64
origin deb.devuan.org
500 http://deb.devuan.org/merged chimaera/contrib amd64 Packages
release v=4.0,o=Devuan,a=stable,n=chimaera,l=Devuan,c=contrib,b=amd64
origin deb.devuan.org
500 http://deb.devuan.org/merged chimaera/non-free amd64 Packages
release v=4.0,o=Devuan,a=stable,n=chimaera,l=Devuan,c=non-free,b=amd64
origin deb.devuan.org
500 http://deb.devuan.org/merged chimaera/main amd64 Packages
release v=4.0,o=Devuan,a=stable,n=chimaera,l=Devuan,c=main,b=amd64
origin deb.devuan.org
Pinned packages:
refractainstaller-base -> 9.5.6 with priority 1001
refractainstaller-gui -> 9.5.6 with priority 1001
and
$ apt policy gnome-sudoku
gnome-sudoku:
Installed: 1:3.22.2-1
Candidate: 1:3.38.0-1
Version table:
1:3.38.0-1 500
500 http://deb.devuan.org/merged chimaera/main amd64 Packages
*** 1:3.22.2-1 100
100 /var/lib/dpkg/status
Why does pinning make you nervous? My concern is just to be sure that nothing else gets blocked from updating.
I forgot the extension. So, you don't need to create any additional folder, because /etc/apt/preferences.d is the right place to edit the file.
Well everything seems to be working right. I had some updates today, and sudoku was marked as not to be upgraded. Everything else updated okay. Should I just leave well enough alone, or put that file in preferences.d and delete the preferences folder I created?
It appears to have worked. Thanks, to both of you.
BTW, there was no "preferences" folder in /etc/apt, so I created one. Is that normal? There is a "preferences.d" folder.
I update via Synaptic, never from the terminal, so I don't see how this applies to me? I want Synaptic to not update sudoku, which is what I thought Lock Version was supposed to do. In Synaptic is there a way to pick and choose from among the list of updates that are presented (when there are updates)?
I like an older version of gnome-sudoku than the one in chimaera's repo, so I had that particular older one installed via a .deb file, then in Synaptic Package Manager I had it marked as "Lock Version" under Package in the menu. I know it got marked because the icon changed to "Installed (locked to current version)" in the icon legend. However, the last time I did an upgrade gnome-sudoku got updated along with all the rest that had updates [ironically it still has the "Installed (locked to current version)" icon]. Did I miss a step, or am I misunderstanding what Lock Version does? Once I go back to the older version is there a way I can prevent gnome-sudoku from updating again?
Marked as solved. No doubt it was bad RAM.
Any luck Ron? I'm thinking with double the memory you'll be getting a better experience all around.
So far, so good.
I only had one 4 gig stick. Just replaced it with one brand new 8 gig stick. Hopefully my browser crashes are now a thing of the past.