March 2016 - openSUSE Users - openSUSE Mailing Lists

[opensuse] network setup in leap 42.1
by Istvan Gabor 16 Jun '16

16 Jun '16

Hello: In openSUSE 13.2 the traditional network setup (ifup in yast) was removed and wicd (??) was introduced which I didn't like when I tried. Along with ifup kinternet/qinternet and related packages, eg smpppd (SuSE Meta PPP Daemon, the back-end for kinternet) have been removed too. I am curious how network manager independent network setup occurs in leap 42.1? Does it have kinternet on something similar? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 14

[opensuse] Does 13.2+ work with shorewall properly yet? Read about wicked/systemd woes
by cagsm 06 Jun '16

06 Jun '16

Good day, I am trying to find out of shorewall is supposed to work with 13.2 properly, as I read about systemd stuff being in the midst of creation and wicked and sort of that things that make it problematic to run something different from susefirewall2. Thanks for helping. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

8 20

[opensuse] Kernel 4.5 runs great!
by Anton Aylward 03 Jun '16

03 Jun '16

regular readers will recall that I've mentioned before: I'm on 13.1 and few leading repositories, one of which is Kernel_Stable. I've just upgraded to 4.5 and yes it is an improvement in many ways. The whole 4.x series has been pretty goo, each step along the way being in improvements, particularly with locking and blocking in the kernel, that result in better responsiveness. Discussion of same at http://www.phoronix.com/scan.php?page=article&item=linux-45-features&num=1 "The Many New Features & Improvements Of The Linux 4.5 Kernel" I'm looking forward to 4.6 :-) Given the stability of 13.1 (and its tumbling) and the continual teething troubles reported here with LEAP, I'm staying with this configuration for the foreseeable future. I'd advise anyone who has the spare resources or inclination to try the 4.x series kernels. At the very least, they have updates to BtrFS that offer stability an improvement over the 3.x series. Relevant to recent threads here: http://www.phoronix.com/scan.php?page=news_item&px=Btrfs-Pull-Linux-4.5 Of course that may not apply to desktop systems There's enough happening to make me consider actually forgetting about the palaeolithic hardware I normally spend time tweaking and hacking and getting a bleeding edge mobo and chipset. But then again, just having a fast desktop might be no fun :-( -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

12 60

[opensuse] I can not filter out some systemd messages in syslog
by Carlos E. R. 17 May '16

17 May '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have this in "/etc/rsyslog.conf": if ($programname == 'named' or $syslogtag == '[named]:') \ then -/var/log/named & stop ... if ($msg contains 'Started Session' and $msg contains 'of user') \ then -/var/log/systemdpurged & stop # # the rest in one file # *.*;mail.none;news.none -/var/log/messages I get the expected entries in "/var/log/systemdpurged": <3.6> 2014-03-01 16:30:01 Telcontar systemd 1 - - Started Session 93 of user cer. <3.6> 2014-03-01 16:33:01 Telcontar systemd 1 - - Started Session 94 of user news. But I'm also getting them in "/var/log/messages": <3.6> 2014-03-01 16:30:01 Telcontar systemd 1 - - Starting Session 93 of user cer. <3.6> 2014-03-01 16:33:01 Telcontar systemd 1 - - Starting Session 94 of user news. And they should not be there. So the "stop" line for those systemd entries is not acting. However, it works for other sections, like the "named" section shown above, and others I do not show for clarity. Are systemd entries special? - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlMSADcACgkQtTMYHG2NR9WCgwCdEgnb+Apy47tcjI31Dv5brA9X +TMAoIt87JaGgMoP5Zf11OZM0XevIjif =uI81 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] Is rsync broken?
by Felix Miata 07 Apr '16

07 Apr '16

# blkid /dev/sda30 # mkfs.ext3 -I128 -b1024 -L ostwEXT3k3 /dev/sda30 # tune2fs -c0 -i0 /dev/sda30 # mount -t ext3 -o noatime /dev/sda30 /mnt # cd /mnt # mount /dev/sda10 # df . (99% free, 1% used) # rsync -av --stats --progress --exclude 'lost+found' /disks/s133/ . # df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda8 7281115 5048620 1859709 74% / (13.1) /dev/sda10 5655815 4759270 605692 89% /disks/s133 (TW on ext4) /dev/sda30 5655815 5281956 87101 99% /mnt Given this sequence of events, what besides broken rsync could be responsible for source used being so much less than target used? This is not the first time I've seen this happen. Last time, used reached 100% and rsync aborted. I tried again, except booted to 42.1: Before: # df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda19 5655815 2928686 2436276 55% / (42.1 on ext4) /dev/sda10 5655815 4759270 605692 89% /disks/s133 (TW on ext4) /dev/sda30 5655815 3727 5365330 1% /mnt # rsync -av --stats --progress --exclude 'lost+found' /disks/s133/ . # df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda19 5655815 2928686 2436276 55% / (42.1 on ext4) /dev/sda10 5655815 4759270 605692 89% /disks/s133 (TW on ext4) /dev/sda30 5655815 5289173 87084 99% /mnt :-( -- "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

4 9

[opensuse] leap install messed up mint
by Dave Howorth 03 Apr '16

03 Apr '16

I had Mint installed on a machine, which also has W10, and it was all working fine. I installed Leap and that is working fine. When I reboot I get taken to openSUSE's boot menu, which is fine, and it reboots either Leap or W10 fine, but if I select the line for Mint it says error: vmlinuz.... has invalid signature. error: you need to load the kernel first. The machine has UEFI and is in secure mode and Mint was booting just fine using its own (well, Ubuntu's) grub so presumably has a good signature, so I'm currently thinking of this as an openSUSE problem. Anybody got any ideas? Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 50

[opensuse] gparted, btrfs, and xfs
by Tom Kacvinsky 01 Apr '16

01 Apr '16

I made the fundamental mistake of not giving enough space to the / partition, and now I find I cannot install further updates because I am out of disk space. gparted was recommended to me, and I have taken the live ISO and “burned” it onto a USB memory stick. I’m having problems booting my laptop with it (endless cycle of “rebooting in 30s”), but I think I can get around that with the latest pre-release of the ISO. In any case, what I would like to do is think /home (on an XFS partition) and use the extra space to grow the / file systems (btrfs). IS this even possible. I did not find any documentation on who to do this, but that’s probably because my search terms were not refined enough. Any help would be appreciated. Thanks, TomN��r��y隊Z)z{.�ﮞ˛��m�)z{.��+�:�{Zr�az�'z��j)h��Ǿ� ޮ�^�ˬz��

15 100

[opensuse] [opensuse-factory] Conflicts to update R-core-libs
by Edwin Aponte 01 Apr '16

01 Apr '16

Hi, When I try to update R-core-libs on openSUSE TW, zypper finds the following conflicts: Checking for file conflicts: ...............................................................................................................................................................................[error] Detected 3 file conflicts: File /usr/lib64/R/lib/libR.so from install of R-core-libs-3.2.4.1-33.6.x86_64 (R core components, supplements (like rkward), and CRAN packages (openSUSE_Tumbleweed)) conflicts with file from package R-base-libs-3.2.3-1.3.x86_64 (@System) File /usr/lib64/R/lib/libRblas.so from install of R-core-libs-3.2.4.1-33.6.x86_64 (R core components, supplements (like rkward), and CRAN packages (openSUSE_Tumbleweed)) conflicts with file from package R-base-libs-3.2.3-1.3.x86_64 (@System) File /usr/lib64/R/lib/libRlapack.so from install of R-core-libs-3.2.4.1-33.6.x86_64 (R core components, supplements (like rkward), and CRAN packages (openSUSE_Tumbleweed)) conflicts with file from package R-base-libs-3.2.3-1.3.x86_64 (@System) ============ So these are basically conflicts between the updated package and the installed package. I am able to continue the update but this should not be regarded as conflict. I am able to update other packages without conflict. Could this be due to some misconfiguration on my system or a packaging error? Thanks. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 4

[opensuse] My huawei ascend y221 only seen as mass storage after win xp in vbox has seen it.
by Dave Plater 01 Apr '16

01 Apr '16

Hi, I'm running Leap:42.1 Kde plasma5 and the device notifier only picks up my phone as mass storage after I've enabled and disabled the phone in a vbox win xp on my computer. If I connect as an mtp(media) device or a ptp(camera) it works fine. Here's a journalctl output when I go through this process : > Connect phone and select "turn on usb storage" on the phone. > > Mar 29 15:05:20 arbuthnot kernel: usb 2-1.3: new high-speed USB device number 7 using ehci-pci > Mar 29 15:05:21 arbuthnot kernel: usb 2-1.3: New USB device found, idVendor=12d1, idProduct=2350 > Mar 29 15:05:21 arbuthnot kernel: usb 2-1.3: New USB device strings: Mfr=2, Product=3, SerialNumber=4 > Mar 29 15:05:21 arbuthnot kernel: usb 2-1.3: Product: HUAWEI Y221 PHONE > Mar 29 15:05:21 arbuthnot kernel: usb 2-1.3: Manufacturer: MediaTek > Mar 29 15:05:21 arbuthnot kernel: usb 2-1.3: SerialNumber: RGTKVSZST46TIVWK > Mar 29 15:05:21 arbuthnot kernel: usb-storage 2-1.3:1.0: USB Mass Storage device detected > Mar 29 15:05:21 arbuthnot kernel: scsi host13: usb-storage 2-1.3:1.0 > Mar 29 15:05:21 arbuthnot mtp-probe[5665]: checking bus 2, device 7: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3" > Mar 29 15:05:21 arbuthnot mtp-probe[5665]: bus: 2, device: 7 was not an MTP device > Mar 29 15:05:21 arbuthnot usb_modeswitch[5689]: switch device 12d1:2350 on 002/007 > > Phone doesn't show in kde device notifier > Start vbox win xp and connect then disconnect phone in vbox > > Mar 29 15:06:33 arbuthnot kernel: vboxdrv: ffffffffa08c0020 VMMR0.r0 > Mar 29 15:06:33 arbuthnot kernel: vboxdrv: ffffffffa09ba020 VBoxDDR0.r0 > Mar 29 15:06:34 arbuthnot kernel: vboxdrv: ffffffffa0015020 VBoxDD2R0.r0 > Mar 29 15:06:34 arbuthnot kernel: vboxdrv: ffffffffa0029020 VBoxEhciR0.r0 > > On disconnecting the phone in vbox xp the phone is picked up and appears in device notifier. > sdg1 is the sd card and sdh is the phone > > > Mar 29 15:07:34 arbuthnot kernel: usb 2-1.3: reset high-speed USB device number 7 using ehci-pci > Mar 29 15:07:34 arbuthnot kernel: usb-storage 2-1.3:1.0: USB Mass Storage device detected > Mar 29 15:07:34 arbuthnot kernel: scsi host14: usb-storage 2-1.3:1.0 > Mar 29 15:07:35 arbuthnot kernel: scsi 14:0:0:0: Direct-Access Linux File-CD Gadget 0000 PQ: 0 ANSI: 2 > Mar 29 15:07:35 arbuthnot kernel: sd 14:0:0:0: Attached scsi generic sg8 type 0 > Mar 29 15:07:35 arbuthnot kernel: scsi 14:0:0:1: Direct-Access Linux File-CD Gadget 0000 PQ: 0 ANSI: 2 > Mar 29 15:07:35 arbuthnot kernel: sd 14:0:0:1: Attached scsi generic sg9 type 0 > Mar 29 15:07:35 arbuthnot kernel: sd 14:0:0:0: [sdg] 7747584 512-byte logical blocks: (3.96 GB/3.69 GiB) > Mar 29 15:07:35 arbuthnot kernel: sd 14:0:0:0: [sdg] Write Protect is off > Mar 29 15:07:35 arbuthnot kernel: sd 14:0:0:0: [sdg] Mode Sense: 0f 00 00 00 > Mar 29 15:07:35 arbuthnot kernel: sd 14:0:0:1: [sdh] 2235904 512-byte logical blocks: (1.14 GB/1.06 GiB) > Mar 29 15:07:35 arbuthnot kernel: sd 14:0:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > Mar 29 15:07:35 arbuthnot kernel: sd 14:0:0:1: [sdh] Write Protect is off > Mar 29 15:07:35 arbuthnot kernel: sd 14:0:0:1: [sdh] Mode Sense: 0f 00 00 00 > Mar 29 15:07:35 arbuthnot kernel: sd 14:0:0:1: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > Mar 29 15:07:35 arbuthnot kernel: sdg: sdg1 > Mar 29 15:07:35 arbuthnot kernel: sdh: > Mar 29 15:07:35 arbuthnot kernel: sd 14:0:0:0: [sdg] Attached SCSI removable disk > Mar 29 15:07:35 arbuthnot kernel: sd 14:0:0:1: [sdh] Attached SCSI removable disk > Mar 29 15:07:48 arbuthnot kernel: FAT-fs (sdg1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. > Mar 29 15:07:48 arbuthnot org.gtk.Private.UDisks2VolumeMonitor[1752]: disc.c:332: error opening file BDMV/index.bdmv > Mar 29 15:07:48 arbuthnot org.gtk.Private.UDisks2VolumeMonitor[1752]: disc.c:332: error opening file BDMV/BACKUP/index.bdmv > Mar 29 15:07:48 arbuthnot udisksd[1815]: Mounted /dev/sdg1 at /run/media/davepl/2A86-17E6 on behalf of uid 1000 > Mar 29 15:07:51 arbuthnot kernel: FAT-fs (sdh): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. > Mar 29 15:07:51 arbuthnot udisksd[1815]: Mounted /dev/sdh at /run/media/davepl/B4E0-0FE0 on behalf of uid 1000 > Mar 29 15:07:51 arbuthnot org.gtk.Private.UDisks2VolumeMonitor[1752]: disc.c:332: error opening file BDMV/index.bdmv > Mar 29 15:07:51 arbuthnot org.gtk.Private.UDisks2VolumeMonitor[1752]: disc.c:332: error opening file BDMV/BACKUP/index.bdmv Can anyone shed any light on this problem? Thanks Dave P. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 12

[opensuse] suse/open suse maintainers for Ring
by Nicolas Jäger 31 Mar '16

31 Mar '16

Hi, My name is Nicolas Jager, I'm working on the Ring project (https://ring.cx/) at Savoir Faire Linux. Ring is a secure and distributed voice, video and chat communication platform that requires no centralized server and leaves the power of privacy in the hands of the user. We want to make ring much more visible to all linux users. We are currently trying to find maintainers who can, and want, to make ring available to the official repository of suse/open suse. If you are interested, I would be happy to answer any of your questions. regards, Nicolas Jager -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2