June 2018 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Friday quiz - ping: socket: Operation not permitted
by Per Jessen 03 Jun '18

03 Jun '18

On Leap15 as a plain user: per@discompi2:~> ping discompi3 ping: socket: Operation not permitted With an strace - socket(AF_INET, SOCK_DGRAM, IPPROTO_ICMP) = -1 EACCES (Permission denied) socket(AF_INET, SOCK_RAW, IPPROTO_ICMP) = -1 EPERM (Operation not permitted) socket(AF_INET6, SOCK_DGRAM, IPPROTO_ICMPV6) = -1 EACCES (Permission denied) socket(AF_INET6, SOCK_RAW, IPPROTO_ICMPV6) = -1 EPERM (Operation not permitted) Nothing to be seen in apparmor. -- Per Jessen, Zürich (21.2°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 14

[opensuse] a little help with Leap 5
by don fisher 02 Jun '18

02 Jun '18

I have been having a lot of trouble with upgrade, so pardon this if stupid question. I do not use LVM. When I boot the Leap 15 DVD and try to set up partitions, I get 6 rather that the usual 3 generated under 14.3. For some reason, that I can probably research on google, it sets up partition 1 as a BIOS boot partition. Not sure why this is required. But then it sets up partitions 2 and 3 as BtrFS partitions, then partition 5 as another BtrFS partition mounted as root. Then partitions for the usual swap and home file systems. Why are there 3 BtrFS partitions? The only comment I can find, all the way in Release notes:7 technical, is that there is a single subvolume for all of /var. I changed the root file system type to xfs and was able to generate the 3, (4 with BIOS boot), partition layout I am familiar with. Comments please. Don -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 9

[opensuse] Asterisk
by suse＠a-domani.nl 02 Jun '18

02 Jun '18

Hi all, Perhaps I'm looking in the wrong places, like: ../repositories/network/openSUSE_Leap_15.0/x86_64/ ../repositories/network:/telephony/openSUSE_Leap_15.0/x86_64/ ../repositories/network:/telephony:/ (here are asterisk-14 and asterisk-15 completely missing) but I can't find asterisk-15.x while in /repositories/network:/telephony/openSUSE_Leap_42.3/x86_64/ I see: asterisk-15.4.0-2.1.x86_64.rpm build at: 30-May-2018 13:05 Looking at the wrong places, or looking too early? HtH, Hans -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] Connection doesn't work with some wifi networks
by Charles Robert 02 Jun '18

02 Jun '18

Hello, I'm on Tumbleweed with network manager and KDE. With some wifi networks (now 2), network manager can connect but it has no data flux and the ping doesn't work. I haven't connection issue with another wifi networks. I can use these wifi networks with an Ubuntu live USB. Thanks for your helping. Charles -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

10 30

[opensuse] Problem with leap 15 upgrade
by don fisher 02 Jun '18

02 Jun '18

I started to perform an upgrade from 43.2 to Leap 15 and received an error warning: "Some partitions on the system on /dev/sdc2 are mounted by kernel-device name" I had mounted the partitions by UUID. Is UUID that what is meant by a kernel device name? Because I was under the impression that the UUID belonged to the device. Should that cause the system upgrade to fail? I get message Execution of Command ""[["?usr.sbin.grub2-mkconfig","-o","/boot/grubd/grub.cfg"]]" failed Error output: Generating grub configuration file... and more., Then: ERROR:failed to lookup rootid:inappropriate ioctl for device. Is this a problem with the use of UUIDs? The first warning suggests changing the "mount-by" method to any other method. Don't know which other one to pick. Using google it appears that UUID is the most recommended. But another link says that the it you recreate the partitions they will get different UUIDs. I looked in /dev/disk and see by-id, by-label, by-path and by UUID. I would use by-id, but am concerned that all of the devices may not be known. Like 4GB SSD drives. By-path appears vulnerable to the pci id changing if one moves the drive. I usually do not put labels on all of my partitions, so do not know how what by label would look like. What is the best approach? And is this my problem? Don -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 37

[opensuse] please use the new opensuse-support list ??
by Per Jessen 01 Jun '18

01 Jun '18

Knurpht @ openSUSE wrote: > For support questions, both Leap and Tumbleweed, please use the new > opensuse- support(a)o.o list. Gertjan, I have mostly stayed out of this discussion, but this is a bit much. Given that no change of purpose for opensuse(a)o.o has been announced, proposed nor discussed, I think you are being insincere in attempting to reroute traffic, thereby unnecessarily splitting our community. The new support list has been announced, now leave it to the community to decide. If people find the support offered on opensuse-support(a)o.o to be more readily available or perhaps even better than here, they will migrate by themselves. -- Per Jessen, Zürich (18.9°C) member, openSUSE Heroes. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 6

[opensuse] Re: [opensuse-factory] Re: Mailinglist changes going forward
by Fraser_Bell 01 Jun '18

01 Jun '18

On 05/28/2018 09:39 AM, Neil Rickert wrote: > On 05/28/2018 09:50 AM, Anton Aylward wrote: > >> My experience has been that reporting my own mistakes and >> misconfiguration on bugzilla simply ends up in a WONTFIX. It may >> be that the developer didn't have time or patience to explain what >> *I* was doing wrong and that there really wasn't a bug, or it may >> be that (s)he didn't want to bothered tracing why this bug happens, >> what fringe/test-case brings it up. > > For users in this situation, my best advice would be to post to the > opensuse forums (forums.opensuse.org) Quite a few people do that > already. And theyare advised to open a bug report when that is > appropriate. Exactly. It is a great Forum, with great Volunteer Support, and is Moderated so that the garbage that floods these mail lists tends to be almost totally absent. -- -Gerry Makaro openSUSE Member openSUSE Forum Moderator openSUSE Contributor aka Fraser_Bell on the Forums, OBS, IRC, and mail at openSUSE.org Fraser-Bell on Github -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2