Samba config -
by Bob Goodwin
L am struggling with the configuration of the new server. Presently my
problem is that I attempted to create a link an made an error, I do not
understand perfectly what I have read!
[root@smb bobg]# ln -s /home/share /media/dd2
"# rm linkfile" is clear enough but,
[root@smb bobg]# ll /media/dd2
total 0
lrwxrwxrwx. 1 root root 11 Jun 29 17:25 share -> /home/share
Which one is the link name to be removed, what is the exact command to
do that and NOT DESTROY or damage the files in /media/dd2?
I could unplug the data cable on the drive while doing the removal but
even then Might there be something lurking to finish the removal when
restarted with the drive plugged in? I am confused and worried about
doing the removal correctly, some advice appreciated. Bob
--
Bob Goodwin - Zuni, Virginia, USA
http://www.qrz.com/db/W2BOD
FEDORA-32/64bit LINUX XFCE Fastmail POP3
5 days, 7 hours
Mount samba share using pam_mount
by Simon Colston
Fedora Workstation 32
I'm trying to mount a samba share at login using pam_mount. The steps I've taken so far after googling and man-page
reading are:
1. In /etc/security/pam_mount.conf.xml I uncommented the line:
<luserconf name=".pam_mount.conf.xml" />
2. Created the file ~/.pam_mount.conf.xml containing:
<?xml version="1.0" encoding="utf-8" ?>
<pam_mount>
<volume options="uid=%(USERUID),gid=%(USERGID)" user="%(USER)"
mountpoint="~/diskstation/home" path="home" server="diskstation.local" fstype="cifs" />
</pam_mount>
3. To add pam_mount.so to pam.d I changed /etc/pam.d/login to:
#%PAM-1.0
auth substack system-auth
auth optional pam_mount.so
auth include postlogin
account required pam_nologin.so
account include system-auth
password include system-auth
# pam_selinux.so close should be the first session rule
session required pam_selinux.so close
session optional pam_mount.so
session required pam_loginuid.so
session optional pam_console.so
# pam_selinux.so open should only be followed by sessions to be executed in the user context
session required pam_selinux.so open
session required pam_namespace.so
session optional pam_keyinit.so force revoke
session include system-auth
session include postlogin
-session optional pam_ck_connector.so
and /etc/pam.d/gdm-password to:
auth [success=done ignore=ignore default=bad] pam_selinux_permit.so
auth substack password-auth
auth optional pam_mount.so
auth optional pam_gnome_keyring.so
auth include postlogin
account required pam_nologin.so
account include password-auth
password substack password-auth
-password optional pam_gnome_keyring.so use_authtok
session required pam_selinux.so close
session optional pam_mount.so
session required pam_loginuid.so
session optional pam_console.so
session required pam_selinux.so open
session optional pam_keyinit.so force revoke
session required pam_namespace.so
session include password-auth
session optional pam_gnome_keyring.so auto_start
session include postlogin
I log out and back in again and... it does not work. (I can mount this share from the command line using the mount
command.)
So my question is... what am I doing wrong?
Simon
6 days, 14 hours
Audacity: "Error opening recording device"
by Matti Pulkkinen
Hello,
I'm trying to use Audacity to record the line in on my PC, but I always
get the following error:
Error opening recording device.
Error code: -9997 Invalid sample rate
Sounds like an easy-to-fix problem, but the same thing happens
regardless of what sample rate I choose. Checking with "pacmd
list-sinks" I found that the sample rate for my card is 44100 Hz, so
that's what I'm trying to use now that I've checked all possible sample
rate options Audacity offers. Also, Audacity offers a bunch of different
recording devices with names along the lines of "HDA Intel PCH: ALC892
Alt Analog (hw:0,2): Front Mic:0" but the same error happens with all of
them too.
Based on what I could find online, it seems like people have had this
issue mostly on Windows, and then it was to do with either not having
updated drivers or having set the device's sample rate incorrectly. Has
anyone here run into something like this before on Fedora? Any ideas
where to start trying to fix this?
--
Terveisin / Regards,
Matti Pulkkinen
1 week, 2 days
Steam erroneously marked as "Installed" in Gnome Software
by Sreyan Chakravarty
Hi,
I have NEVER installed Steam via Gnome Software on my notebook, in fact
I never installed it ever, but on Gnome Software it is marked as
"Installed".
Any way I can remove it from there ? That is mark it as "not installed" ?
When I click on "Remove" it says "no packages to remove" but it has
"Launch" and "Remove" options enabled. "Launch", does nothing.
Are there any command-line/debugging/troubleshooting options that I
should know about for Gnome Software Centre ? Seems like I haven't seen
the last of such annoying bugs.
Thanks.
--
Regards,
Sreyan
1 week, 3 days
Where are the microcode updates for Crosstalk in F32 ?
by Sreyan Chakravarty
Hi,
Well guys, its time to panic once again.
I just found out my system is vulnerable to the new Crosstalk
vulnerability by running the popular Meltdown OVH script.
More about the vulnerability over here:
https://www.vusec.net/projects/crosstalk/
These exploits get worse each time, this one affects all cores.
This is how I tested for the vulnerability.
Downloaded spectre-meltdown-checker.sh via :
wget https://meltdown.ovh -O spectre-meltdown-checker.sh
and then just executed with sudo.
This is the output I got:
* SRBDS mitigation control is enabled and active: NO
> STATUS: VULNERABLE (Your CPU microcode may need to be updated to mitigate the vulnerability)
CVE-2020-0543:KO
Full output here:
https://pastebin.com/raw/hyfFBbaF
As you can see the tool specifies that my microcode is not the latest.
That being said, where do I find the latest microcode from ?
My OS is fully updated, and the firmware and microcode is also latest
according to DNF:
$ sudo dnf update linux-firmware
Dependencies resolved.
Nothing to do.
Complete!
$ sudo dnf update microcode_ctl
Dependencies resolved.
Nothing to do.
Complete!
So where is the microcode update in Fedora for this ??
Canonical has already published microcode updates for this, as shown here:
https://youtu.be/UR-5vAZ1cGg?t=1160
<rant>
It kind of seems frustrating that a bleeding edge distro like Fedora still hasn't
provided updates yet. While Ubuntu a distro that doesn't always use the latest
software already has a fix.
</rant>
What can I do now ? What is progress for Fedora ?
Will the microcode from Canonical work for Fedora ? Dumb question I know but I
am desperate.
Let me know if any further info is required.
Some more info about my CPU:
https://pastebin.com/raw/TNJS930F
What is everyone else in the community doing about this ?
Thanks.
--
Regards,
Sreyan
1 week, 3 days
Strange Samba error
by Patrick O'Callaghan
My journal is full of these error messages, occurring every 15 minutes:
Jun 30 00:43:38 Bree nmbd[1301]: [2020/06/30 00:43:38.122397, 0] ../../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail)
Jun 30 00:43:38 Bree nmbd[1301]: find_domain_master_name_query_fail:
Jun 30 00:43:38 Bree nmbd[1301]: Unable to find the Domain Master Browser name SAMBA<1b> for the workgroup SAMBA.
Jun 30 00:43:38 Bree nmbd[1301]: Unable to sync browse lists in this workgroup.
Jun 30 00:43:38 Bree nmbd[1301]: [2020/06/30 00:43:38.122554, 0] ../../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail)
Jun 30 00:43:38 Bree nmbd[1301]: find_domain_master_name_query_fail:
Jun 30 00:43:38 Bree nmbd[1301]: Unable to find the Domain Master Browser name SAMBA<1b> for the workgroup SAMBA.
Jun 30 00:43:38 Bree nmbd[1301]: Unable to sync browse lists in this workgroup.
What I can't figure out is where 'SAMBA<1b>' is coming from (I assume
the <1b> is a non-printable byte at the end of the name). My smb.conf
file contains:
[global]
workgroup = SAMBA
netbios name = BREESHARE
wins support = yes
security = user
and no other instances of SAMBA. I attach the full file for
completeness.
Any thoughts?
poc
1 week, 3 days
Every second GDM login fails
by Michael Schwendt
Has anyone also had this before with GNOME Shell in Fedora 32?
It is new behavior compared with older releases of Fedora.
When I return to a locked screen, my usual habit is to press Return
and then to enter the passphrase. That fails even if unhiding the passphrase
and verifying that it has been entered correctly. The second time I enter
the passphrase, logging in works again. It seems as if the first Return press
breaks something.
1 week, 4 days
I need help with sudo.conf
by ToddAndMargo
Hi All,
I am trying to use sudo to work around the following bug
I posted:
ifdown access denied with USERCTL=yes
https://bugzilla.redhat.com/show_bug.cgi?id=1828100
I wish they'd fix the bug, but it does not seems like it
is every going to get any attention.
So anyway, I fired up `sudovi` and added the following
at the end of /etc/sudo.conf`:
## Allows members of the users group to down eno2
%users ALL=/usr/libexec/nm-ifdown eno2
Now when I run it from the command line, I get:
$ /usr/libexec/nm-ifdown eno2
Error: failed to load connection: access denied.
Questions:
1) I thought `sudovi` caused sudo to reread sudo.conf
on its exit. Am I mistaken? And if so, how do I
force a reread?
2) what is wrong with the syntax of the command I added
to sudo.conf?
Many thanks,
-T
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Computers are like air conditioners.
They malfunction when you open windows
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 week, 4 days
USB "insertion" for permanently-connected devices
by Patrick O'Callaghan
In other threads I've mentioned I have a USB-powered external SATA
dock, which I'm using mainly as a backup device. Currently, I have a
script to power it down by doing this sort of thing:
echo 1 > /sys/block/sdd/device/delete
I can then turn it on again using:
echo "- - -" > /sys/class/scsi_host/host6/scan
This works, but is a kludge. A cleaner way would be to use:
udisksctl power-off -b /dev/sdd
This works too, but unfortunately also removes the /sys/block/sdd
files, meaning I can't turn the thing on again. However, if I
physically switch it on and off, it reappears, IOW it causes a USB
"insertion" event.
Is there a way to cause an insertion event without physically doing
anything to the dock?
poc
1 week, 5 days
