I’m running os42 12cpu gtx970 16gb tower
I have three problems
1)failed to activate context library for activation-generator
2)yast2 dumps as soon as I hit “ok try again” -works perfectly if you don’t need to and yast in command line mode works
If I start yast2 via the command line in a terminal it still dumps
3)I cannot get cifs working - some searching led me to a problem with cifs unloading properly so I uninstalled everything cifs and samba and found cifsiod still loaded as a single thread from Kthreadd and cannot get rid of it to see if it is the problem
I also have tumbleweed set up on its own drive with its own file system and although I have run 2 systems like this before it doesn’t seem to like it now -not sure if I have done something different
I tried to post some logs but it didn’t work - happy to try again if needed
Thank you in advance
???
More details please.
2)yast2 dumps as soon as I hit “ok try again” -works perfectly if you don’t need to and yast in command line mode works
If I start yast2 via the command line in a terminal it still dumps
That’s a known problem in the Qt interface at the moment, affects both Tumbleweed and Leap 42.1M2.
It has been fixed already though, so it should work in the next Milestone/Beta.
3)I cannot get cifs working - some searching led me to a problem with cifs unloading properly so I uninstalled everything cifs and samba and found cifsiod still loaded as a single thread from Kthreadd and cannot get rid of it to see if it is the problem
Again, more details please.
How do you try to get cifs working?
And what exactly do you want to do in the first place?
cifs is part of the kernel, you cannot “uninstall” it. To mount a share via cifs, a simple “mount //HOST/SHARE mountpoint” should work, unless you need to supply a username/password of course.
Also, in general it’s better to create separate threads for separate problems.
no problem wolfi - I shall remember
The first problem - that is the message I get at boot
Near as I could work out on the web is it has something to do with systemd
I always do manually through fstab and apart from when I first put 13.2 on and didn’t know about sec=ntlm I never had a problem
e.g. //192.168.0.2/e /media/x cifs sec=ntlm,credentials=XXX,file access permission,directory access permission 0
I tried to send output in html tags but it was to much and my posting permissions say I can’t send attachments - is there a way around this?
Actually, googling for the message you posted suggests a problem with LVM.
I always do manually through fstab and apart from when I first put 13.2 on and didn’t know about sec=ntlm I never had a problem
e.g. //192.168.0.2/e /media/x cifs sec=ntlm,credentials=XXX,file access permission,directory access permission 0
Isn’t there a digit missing at the end?
And the options “file access permission,directory access permission” don’t look ok either. I don’t think spaces are allowed there, and I don’t find them being mentioned in “man mount.cifs” here on my 13.2 system.
And what is your problem now?
Does the mount fail? Do you get an error message? Which one?
Does a manual “mount” work?
You probably should add the mount “option” _netdev to tell systemd that this needs a working network, but I think it should be able to figure out itself.
I tried to send output in html tags but it was to much and my posting permissions say I can’t send attachments - is there a way around this?
No.
You have to upload it to some sharing site like http://susepaste.org and post a link.
URL: http://susepaste.org/41117350
And the options “file access permission,directory access permission” don’t look ok either. I don’t think spaces are allowed there, and I don’t find them being mentioned in “man mount.cifs” here on my 13.2 system.
And what is your problem now?
Does the mount fail? Do you get an error message? Which one?
Does a manual “mount” work?
sorry wasn’t thinking
e.g. //192.168.0.2/e /media/x cifs sec=ntlm,credentials=XXX,file_mode=0775,dir_mode=0775, 0 0
That is just my normal fstab entry - I have tried all manner of others from the web and from scratch using man cifs - all coming up with the same error just different numbers
I forgot to say that no amount of coaxing can get samba or nfs working through yast either
Actually, googling for the message you posted suggests a problem with LVM.
Yes it was LVM but I can’t work it out
There’s a stray ‘,’ now. I hope that’s just a typo in your post…
That is just my normal fstab entry - I have tried all manner of others from the web and from scratch using man cifs - all coming up with the same error just different numbers
You mean “CIFS VFS: cifs_mount failed w/return code = -121”?
It would probably have been easier to just post that error message… 
Anyway, so running mount manually in the booted system does not work either?
I forgot to say that no amount of coaxing can get samba or nfs working through yast either
No idea what you mean with that. Please write what you do exactly and how it fails.
Does stopping/disabling AppArmor help?
Yes it was LVM but I can’t work it out
What can you not “work out”?
There’s a bug report here that might be related: http://bugzilla.opensuse.org/show_bug.cgi?id=945821
A suggestion is to add “use_lvmeta = 0” to /etc/lvm/lvm.conf, this has helped in other cases.