March 2017 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Re: [OFF-LIST] retreat from TW to Leap 42.1 STATUS
by Carlos E. R. 08 Mar '17

08 Mar '17

On 2017-03-08 20:04, Anton Aylward wrote: > On 08/03/17 01:31 PM, Carlos E. R. wrote: >> On 2017-03-08 16:39, Anton Aylward wrote: >>> Well I have, after some vicissitudes battling with the result of using the42.1 >>> installation DVD, a usable system. That was not happy. >> >> Going to 42.1 you will find somethings too old. You should go to 42.2. >> >> And too big a jump to go down from TW. Don't you have a backup of 13.1 >> or 13.2 to go UP instead? > > I did not go down from TW, I installed in a new "partition" (==LV under LVM) So, it is a fresh install of 42.1. I take it that you did not add ANY repository. Or did you? > I tried 42.2 before 4.1 and that was even more of a disaster. If you have a *working* 13.2, clone it and upgrade it to 42.2, using the DVD. Ask me about repositories. > If I can stabilize 42.1 and overcome the cynicism I see on the list about 4.2. I > might try upgrading ....later in the year. You can not wait that long. >>> I've just finished battling with Wicked (and discarding it) and with >>> NetWorkmanager (which I may in turn discard). I think I'm booting with properly >>> assigned addresses. lets see if that's stable. I'm still trying to figure out >>> how to stop NM from starting a DHCP server. >> >> I can't imagine why it would start a dhcp server, unless it is a client >> daemon. A different thing. > > No, its there in the unit file for Wicked. its a requirement. I don't see any of that in the /usr/lib/systemd/system/wicked.service for 42.2. > > If I manually edit the unit file removing that requirement it doesn't happen. > (I love this text mode descriptive 'programming'!) You should not do that at this stage. > >>> Graphical login isn't working right. >>> I've had to jury righ things to get yast to work at all to configure that. >>> hey, this is weierd. >>> >>> Trying to start YAST from the menu segfaults: >>> >>> /sbin/yast2: line 440: 30032 Segmentation fault $y2ccbin $Y2UI_ARGS "$@" >> >> You probably have mixed rpms. > > Quite possibly. How do I debug the database? Email this file: rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \ | sort | cut --fields="2-" | tee rpmlist | less -S >> with startx somethings do not work. > > and your list is .... ? I don't have a list. Without a login manager you do not have permission to access sound, usb sticks, etc. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))

5 5

Re: [opensuse][OFF-LIST] retreat from TW to Leap 42.1 STATUS
by Felix Miata 08 Mar '17

08 Mar '17

[reply-to was set to list] Anton Aylward composed on 2017-03-08 14:04 (UTC-0500): >> That's not CLI. You are requesting graphical YaST. Just run "yast" in a >> terminal > You misread me> I mean, in at a CLI prompt, typing in "yast2 --qt" and "yast > --gtk". The former still segfaults, the latter ... >>> Weirdly "yast2 --gtk" produces a message saying that "gtk is depreciated, >>> starting qt" does work. >>> Weird. >> Not weird. There no longer exists a gtk version of YaST. > No, I meant that what is weird is that executing "yast2 --qt" this way works > whereas executing it from the command line doesn't. There are command lines in GUI terminals, and there are command lines on vttys. Which is it here? You can't expect qt to work on a vtty[1-6]. Are all your installed *yui*.rpm in version sync? Are any not installed that should be? Maybe you should try a new LV cloned from 13.2 and zypper dup it to 42.1 with selective locks set, trying to work up to something resembling 42.2. 42.1 is only weeks away from support termination. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Bluetooth controller powered off after resume from suspend
by John Andersen 08 Mar '17

08 Mar '17

I've had this problem on and off for several releases at least since 2008. Machine is an older Dell Inspiron 9400 with a built in Bluetooth, which is provided by the BCM4311 (wifi+bluetooth chip), but which the system sees as if it was part of the USB system: > jsa@poulsbo:~> lsusb > Bus 005 Device 024: ID 413c:8126 Dell Computer Corp. Wireless 355 Bluetooth Synopsis: Resume from suspend will often leave my Bluetooth controller in the powered off state. Not always, but usually, for and suspend over night, or long duration. My BT mouse will therefore not work. Luckily I have a touchpad which is good enough in emergencies. I've found over several years that simply using the keyboard key combo to toggle airplane mode on (killing all radios) and after a 3 seconds toggling it off again would solve this problem. Recent versions of the KDE Configure System Settings (the bluetooth option in KDE System settings, which Opensuse insists on labeling "Configure Desktop" in the kde menu), can determine this situation (bluetooth controller powered off) and will offer to fix it. See: image here: https://paste.opensuse.org/75459363 I want to find out what that KDE settings utility does when "Fix it" is clicked and build it into a systemd resume script, in /usr/lib/systemd/system-sleep/ (which I already have working for other things) But what exactly does the pictured "Fix It" option do? Anyone know: Where is the source for that module? -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] ntptimeset
by Carlos E. R. 08 Mar '17

08 Mar '17

Hi, On this laptop, when it had 13.1, I synced the clock by running an hourly cronjob: /usr/sbin/rcntp ntptimeset That does no longer work because the initd script does not exist. I copied that script from 13.1 and I'm trying to make ntptimeset work. It doesn't. I still have to investigate it more. Meanwhile... What is the consensus now for a one shot time sync? No, running the ntpd daemon is not an option here. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))

7 22

[opensuse] Yast Printer setup Problem. No ppd files / filters at all! listed.
by stakanov 08 Mar '17

08 Mar '17

This machine has been updated to 42.2 from 42.1. In 42.1 it worked perfectly with a Lexmark C543 Laser Printer which is branched on USB. Now the printer is listed in lsusb. It is found by yast. There is no printerdriver discovered of ANY sort. Even manually installing the printer driver does not change anything. I checked in /usr/shared/cups. All is there. Even the printer driver installed via yast manually. It also created his nice "folder" called downloaded printer drivers. Unfortunately no driver is selectable. I tried already to reinstall all cups related packages but nothing changes. BTW during the update must have been something "forgotten" because when I go on download.opensuse.org then the driver proposed is for 42.1 not for 42.2. However, I checked all repos twice: no 42.1 repo left since a long long time. Any suggestion on what that could ever be? This is driving me nuts. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 11

[opensuse] oSC17 IRC Meeting - Week 5
by ddemaio 08 Mar '17

08 Mar '17

Hi all, We will have a half hour meeting tonight at 1700 UTC on the openSUSE-project IRC Channel on freenode to discuss the following topics for the openSUSE Conference. Status Keynote T-Shirts Design Videos Status Pre-Party Summits Status TSP Posters Status cya there. v/r Doug Links for previous meetings Week 1 - https://community.opensuse.org/meetings/opensuse-project/2017/opensuse-proj… Week 2 - http://community.opensuse.org/meetings/opensuse-project/2017/opensuse-proje… Week 3 - http://community.opensuse.org/meetings/opensuse-project/2017/opensuse-proje… Week 4 - http://community.opensuse.org/meetings/opensuse-project/2017/opensuse-proje…

1 0

[opensuse] smbclient issues
by Roger Oberholtzer 08 Mar '17

08 Mar '17

I have two openSUSE machines that have joined the same Windows domain. Both have done this via yast. The 12.3 machine has no trouble verifying users against the domain. The Tumbleweed machine, however, fails. On the openSUSE 12.3 client where it works, I get something like this: smbclient --user=roropq //os12p3/roger WARNING: The "idmap gid" option is deprecated WARNING: The "idmap uid" option is deprecated Unknown parameter encountered: "mangle case" Ignoring unknown parameter "mangle case" Domain=[RAMBOLL] OS=[Unix] Server=[Samba 3.6.12-59.23.1-3256-SUSE-SL12.3-i386] smb: \> On the Tumbleweed machine, I see this: smbclient --user=roropq //Tumblereed/roger WARNING: The "idmap gid" option is deprecated WARNING: The "idmap uid" option is deprecated Unknown parameter encountered: "mangle case" Ignoring unknown parameter "mangle case" Domain=[RAMBOLL] OS=[Windows 6.1] Server=[Samba 4.5.3-0-SUSE-oS13.3-x86_64] tree connect failed: NT_STATUS_ACCESS_DENIED It is interesting that the 12.3 samba reports the OS as Unix, while the Tumbleweed samba reports as Windows 6.1. The Server strings match the installed Samba on each machine. When yast checks that the machine is a member of the domain, it is happy. And the domain admin sees both machine as expected (by him). The two machines, as far as I can tell, have samba configured the exact same way. I see this in the samba logs: [2017/02/09 13:42:51.306927, 0] ../source3/libads/kerberos_util.c:74(ads_kinit_password) kerberos_kinit_password STO-OPQ-SRC$(a)RAMBOLL.RAMBOLL-GROUP.GLOBAL.NETWORK failed: KDC has no support for encryption type I have googled this, but I cannot say that I have seen anything that makes sense in the context of samba. This is a bit outside my experience. FYI, the configuration for both machines is: [global] workgroup = RAMBOLL passdb backend = tdbsam printing = cups printcap name = cups printcap cache time = 750 cups options = raw map to guest = Bad User include = /etc/samba/dhcp.conf logon path = \\%L\profiles\.msprofile logon home = \\%L\%U\.9xprofile logon drive = P: usershare allow guests = No idmap gid = 10000-20000 idmap uid = 10000-20000 realm = RAMBOLL.RAMBOLL-GROUP.GLOBAL.NETWORK security = ADS template homedir = /home/%D/%U template shell = /bin/bash winbind refresh tickets = yes mangled names = no usershare max shares = 100 Where to start looking? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 19

[opensuse] Re: why is tumbleweed still using cron?
by L A Walsh 07 Mar '17

07 Mar '17

Anton Aylward wrote: > On 07/03/17 09:40 AM, Carlos E. R. wrote: > >> Is there a systemd index page? 150 pages is daunting. >> > > Indeed it is ... > > ... if you have to learn it ALL AT ONCE > --- In other words, it's not modular. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] IPv6 assignment delays on 42.2. 7minutes until global unicast
by cagsm 07 Mar '17

07 Mar '17

I read some weird bugs in the pest roughly speaking that opensuse leap, back then it had been 42.1, would only assign itself or be assigned an ipv6 global unicast address, after exactly 10minutes. I cant remember the bug or really find it any more and I think there was more to it than just bug, but some fundamental stuff touching all kinds of stuff, linux kernel networking stack, all that wicked stuff and all sorts of eerie stuff. Anyhow, these days I am seeing 42.2 delay with ipv6 in some soho lan with some standard isp and some standard cpe handing out ipv6 addresses. These addresses dont take 10minutes to arrive but still around 7minutes. As far as I understand the isp cpe, it doesnt do dhvp v6 on the lan, but some of these ipv6 router advertisement and neighbor discovery and all that which is the other way to assign oneself a global unicast, the non-dhcp-v6 way, dont ask me what it is called exactly. Anyone care to explain why this takes 7minutes, reproducible? the dualstack nat-ed ipv4 rfc1918 address and the fe80:xx address become set and assigned pretty much immediately when the interface comes up. Thank you for helping. Best regards. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2

[opensuse] Re: [opensuse-project] visa letter request
by ddemaio 07 Mar '17

07 Mar '17

Thank you for letting me know Amey. v/r Doug On 03/07/2017 08:36 AM, Amey Abhyankar wrote: > Hello Doug, > > I have raised 'visa letter request' today. > > This year, 3~4 openSUSE/SUSE/SAP system admins & 1 openSUSE woman user > from my city are attending #oSC17 > You will get visa letter requests from them this week just FYI:-) > They have booked their flight tickets already with my guidance. > Also have registered for the conference. > > All of us met at REDHAT conference in my city & realized we all are > openSUSE users & SUSE system admins;-) [ Due to my oSC16 t-shirt & > openSUSE carry bag they approached me ^_^ ] > > > Thanks & Regards, > Amey. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0