Re: [arch-general] Bug with CIFS mount
On Thu, 17 Dec 2020 at 00:12, Maarten de Vries wrote: > > On 16-12-2020 14:09, Tasnad Kernetzky via arch-general wrote: > > Hi All, > Hi, > > > > I suppose I hit this bug: https://bugs.archlinux.org/task/68963 and it > > seems it is not fully resolved. I didn't request to reopen the bug, > > because I'm not 100% sure it is really the same thing. > > > The bug you're linking is marked as duplicate of this one: > https://bugs.archlinux.org/task/68666 > > That one has been re-opened yesterday, so it seems likely that the > problem is not solved yet. But you also shouldn't re-open the duplicate > issue. Judging from the comments on the re-opened issue, an additional > patch has been sent upstream already. > > I hope this helps :) > > -- Maarten > > Oh well, it literally says "sorry for the duplicate", how could I miss that. Thank you very much and also thanks to/for the patche[r]s! Best, Tasnad
[arch-general] Bug with CIFS mount
Hi All,
I suppose I hit this bug: https://bugs.archlinux.org/task/68963 and it
seems it is not fully resolved. I didn't request to reopen the bug,
because I'm not 100% sure it is really the same thing.
I have a setup with kerberos/sssd/pam/autofs, authenticating with an
active directory, and cifs mounts stopped working.
Login and nfs with kerberos work fine, to the issue is quite likely with
cifs.
Mounting the cifs share works with libcap-ng-0.8-1, but not with
libcap-ng-0.8.2-1.
I have cifs-utils 6.11-2, sssd 2.4.0-2 and krb5 1.18.2-1.
Did I miss something or am I hitting something special due to the setup?
Does anybody have a clue what could be the issue?
I include lots of details about the config and logs, but tl;dr:
"mount -t cifs -o
domain=DOM,sec=krb5,soft,noserverino,cifsacl,username=theUser,cruid=1234567,vers=3.0
//nas.example.com/theUser /nas/home/theUser"
fails with
"cifs.upcall[532824]: drop_all_capabilities: Unable to apply capability
set: Success"
Best,
Tasnad
Substituted values
==
* myMachine: the client's hostname (not fqdn)
* theUser: the nonroot user trying to mount via autofs
* 1234567: uid of theUser (from Active directory)
* DOM: the AD domain
* DOM.EXAMPLE.COM: domain, fqdn
/etc/krb5.conf
==
[libdefaults]
default_realm = DOM.EXAMPLE.COM
udp_preference_limit = 0
default_ccache_name = FILE:/tmp/krb5cc_%{uid}
dns_lookup_realm = true
dns_lookup_kdc = true
rdns = false
ticket_lifetime = 10h
renew_lifetime = 7d
forwardable = true
sssd.conf
=
[sssd]
config_file_version = 2
domains = DOM.EXAMPLE.COM
services = nss, pam
[nss]
default_shell = /bin/bash
shell_fallback = /bin/bash
filter_groups = root
filter_users = root
[domain/DOM.EXAMPLE.COM]
id_provider = ad
auth_provider = ad
access_provider = simple
ldap_schema = ad
sudo_provider = none
cache_credentials = false
krb5_store_password_if_offline = false
dyndns_update = false
ldap_id_mapping = false
use_fully_qualified_names = false
enumerate = false
ignore_group_members = true
case_sensitive = preserving
ad_enable_gc = false
ad_hostname = myMachine
ldap_search_base = [...]
ldap_user_search_base = [...]
ldap_user_search_scope = [...]
ldap_group_search_base = [...]
ldap_group_search_scope = [...]
nsswitch.conf
=
passwd: files sss
group: files sss
shadow: files sss
gshadow: files sss
publickey: files
hosts: files mymachines myhostname resolve [!UNAVAIL=return] dns
networks: files
protocols: files
services: files sss
ethers: files
rpc: files
netgroup: files sss
automount: sss
homes.autofs
/nas/home /etc/autofs/auto.master.d/home.map
-domain=DOM,fstype=cifs,sec=krb5,soft,noserverino,cifsacl
home.map
* -username=$USER,cruid=$UID,vers=3.0 ://nas.example.com/&
cifs idmap plugin
/etc/cifs_utils/idmap-plugin -> /usr/lib/cifs-utils/cifs_idmap_sss.so
klist
=
Ticket cache: FILE:/tmp/krb5cc_
Default principal: theu...@dom.example.com
Valid starting Expires Service principal
12/16/2020 11:31:48 12/16/2020 21:25:18
krbtgt/dom.example@dom.example.com
renew until 12/23/2020 11:25:18
automount -fd
=
handle_packet: type = 3
handle_packet_missing_indirect: token 727, name theUser, request pid 532818
attempting to mount entry /nas/home/theUser
lookup_mount: lookup(file): looking up theUser
lookup_mount: lookup(file): theUser ->
-username=$USER,cruid=$UID,vers=3.0 ://nas.example.com/&
parse_mount: parse(sun): expanded entry:
-username=theUser,cruid=1234567,vers=3.0 ://nas.example.com/theUser
parse_mount: parse(sun): gathered options:
domain=DOM,fstype=cifs,sec=krb5,soft,noserverino,cifsacl,username=theUser,cruid=1234567,vers=3.0
parse_mount: parse(sun): dequote("://nas.example.com/theUser") ->
://nas.example.com/theUser
parse_mount: parse(sun): core of entry:
options=domain=DOM,fstype=cifs,sec=krb5,soft,noserverino,cifsacl,username=theUser,cruid=1234567,vers=3.0,
loc=://nas.example.com/theUser
sun_mount: parse(sun): mounting root /nas/home, mountpoint theUser, what
//nas.example.com/theUser, fstype cifs, options
domain=DOM,sec=krb5,soft,noserverino,cifsacl,username=theUser,cruid=1234567,vers=3.0
do_mount: //nas.example.com/theUser /nas/home/theUser type cifs options
domain=DOM,sec=krb5,soft,noserverino,cifsacl,username=theUser,cruid=1234567,vers=3.0
using module generic
mount_mount: mount(generic): calling mkdir_path /nas/home/theUser
mount(generic): calling mount -t cifs -o
domain=DOM,sec=krb5,soft,noserverino,cifsacl,username=theUser,cruid=1234567,vers=3.0
//nas.example.com/theUser /nas/home/theUser
>> mount error(126): Required key not available
>> Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and
kernel log messages (dmesg)
mount(generic): failed to mount //nas.example.com/theUser (type cifs) on
/nas/home/theUser
dev_ioctl_send_fail: token = 727
failed to mount /nas/home/theUser
journalctl
==
kernel: CIFS: fs/cifs/cifsfs.c: Devn
Re: [arch-general] 2x 1440p displays not working on thunderbold dock anymore
On 14.09.19 16:13, Ricardo Band wrote: > Ahoi, > > I use Arch on a Thinkpad T480 with the Lenovo Thunderbold 3 dock. I've > attached 2 1440p monitors to it and I was using them for a while now. > For a few days or so I can't get them to work anymore. Usually I > disable my Notebooks internal screen and enable the 2 1440p displays > like this: > > ``` > xrandr --output DP1-1 --mode 2560x1440 --refresh 144 > xrandr --output eDP --off > xrandr --output DP1-2 --mode 2560x1440 --refresh 144 --right-of DP1-1 > ``` > > This used to work quite nicely. No idea if the refresh rate actually > worked. I have no way to test that but the resolution sure did. > > Now when I do this I get this error: > > ``` > xrandr: Configure crtc 0 failed > ``` > > I can only drive both displays at 1920x1080. When I increase the > resolution to 2560x1440 I get this error and the higher resolution > can't be set. > > I don't know why this doesn't work anymore. Could it be a driver issue? > I've got a nvidia GPU with the proprietary driver and the integrated > intel with the open source driver and it wouldn't be the first time > intel or nvidia fucked their drivers up. > Hi Ricardo, I know this error message very well. For me, giving "--crtc" values to xrandr works perfectly for 3 years now: xrandr --output eDP1 --crtc 0 --mode 1920x1080 --output DP1 --crtc 1 --primary --mode 2560x1440 --pos 1920x0 --output DP2 --crtc 2 --mode 2560x1440 --pos 4480x0 You can check which virtual crtcs your GPU has with xrandr --verbose, but usually it's 0, 1 and 2 like above. I only have an integrated Intel GPU, but the error message sounds very familiar. Best, Tasnad signature.asc Description: OpenPGP digital signature
Re: [arch-general] Failed install rocketchat-desktop archlinux
Hi,
I had a similar issue with another package, it was related with old
versions of packages.
I could solve it with the following commands in the sources directory:
rm -rf node_modules # or backup, whatever
rm -rf package-lock.json # or backup, whatever
npm cache clean # I guess I had to use --force here
npm install # this was my command, yours will probably be different
Maybe this helps and maybe you'll have to adopt it to yarn, I'm really
not an expert with npm / gulp / yarn / whatever...
Regards,
Tasnad
On 30.04.2018 22:25, Maykel Franco via arch-general wrote:
> Hi, I get this error when install the rocketchat-desktop:
>
> [4/4] Building fresh packages...
> $ electron-builder install-app-deps
> • electron-builder version=19.56.0
> • loaded configuration file=package.json ("build" field)
> • rebuilding native production dependencies platform=linux arch=x64
> • rebuilding native dependency name=spellchecker
> • rebuilding native dependency name=@paulcbetts/system-idle-time
> Done in 17.92s.
> yarn run v1.6.0
> $ gulp build --env=production
> gulp[2126]: ../src/node_contextify.cc:631:static void
> node::contextify::ContextifyScript::New(const
> v8::FunctionCallbackInfo&): Assert
> ion `args[1]->IsString()' failed.
> 1: node::Abort() [gulp]
> 2: 0x55a77757c9db [gulp]
> 3: node::contextify::ContextifyScript::New(v8::FunctionCallbackInfo
> const&) [gulp]
> 4:
> v8::internal::FunctionCallbackArguments::Call(v8::internal::CallHandlerInfo*)
> [gulp]
> 5: 0x55a91ba7 [gulp]
> 6: 0x55a9233c [gulp]
> 7: 0x36bc07f0427d
> error Command failed with signal "SIGABRT".
> info Visit https://yarnpkg.com/en/docs/cli/run for documentation about
> this command
>
>
> Why this error? How to solved it?
>
> Thanks in advanced.
signature.asc
Description: OpenPGP digital signature
Re: [arch-general] Interesting Dual Boot Problems
Just a thought: Maybe windows changed some BIOS/UEFI setting without asking you triggering a power management or similar bug? On 10.04.2018 19:46, Hunter Jozwiak via arch-general wrote: > Nothing is being soft blocked when I ran rfkill this afternoon. A > second reboot still shows the same result. > > On 4/10/18, Marco via arch-general wrote: > I do not have a spare laptop or network card. Everything was working > perfectly fine before I installed Windows, so I have no idea what is > going on here. Interesting. Maybe windows turned something off? Broken power saving feature that turned off something in the card maybe? >> What does "rfkill -list" say? Some Win driver soft block the wifi card >> upon restart/shutdown. >>
