February 2014 - openSUSE Users - openSUSE Mailing Lists

[opensuse] VPN question
by Koenraad Lelong 15 Feb '14

15 Feb '14

Hi, I want to make a vpn-connection to my home modem/router. I can do it using kvpnc, but for this you need the root-password. Is there a way to do it with Networkmanager, so without needing root ? The router uses ipsec to establish the vpn. Kvpnc can import a configuration-file from my router (a FritzBox). Looking at the resulting profile I see kvpnc has to use racoon. It seems for i-phone etc. I can use this : Description: vpn to fritzbox Server: server.example.com Account: some-user Password: Password of "some-user" Use certificate is disabled Group name: some-user Shared secret: some-secret For "Proxy", select the "off" setting. End the VPN configuration by clicking "Save". For Android I can use this : Name: vpn to fritzbox Type: IPSec Xauth PSK Server address : server.example.com IPSec identifier: some-user IPSec pre-shared key: some-secret End the VPN configuration by clicking "Save". Any suggestions ? I tried several options of Networkmanager, but I can't find what to use. On OS 12.2 I tried : StrongSwan, vpnc and openvpn, but none seem to have the right fields. I tried some others with OS13.1, same problem. Regards, Koenraad -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 3

[opensuse] deleting kernels, purge-kernel does not work]
by constant＠indo.net.id 15 Feb '14

15 Feb '14

My system, updated 13.1 Tumbleweed, is overcrowded with default kernels as shown below with "rpm -qa kernel-\*" kernel-firmware-20130714git-5.1.noarch kernel-default-3.13.1-12.1.gfc9498b.i586 kernel-default-3.11.6-4.1.i586 kernel-default-3.13.2-13.2.g97cc2ff.i586 kernel-default-3.13.2-13.1.g97cc2ff.i586 kernel-default-3.13.1-11.1.g5531b68.i586 kernel-default-3.13.2-14.1.gb59b809.i586 After using " systemctl start purge-kernels.service" and a reboot I found that nothing has changed. After a look into Yast> Service manager under purge-kernel> show details I got following info: purge-kernel purge-kernels.service - Purge old kernels Loaded: loaded (/usr/lib/systemd/system/purge-kernels.service; enabled) Active: inactive (dead) start condition failed at Wed 2014-02-12 15:05:52 WIB; 20min ago ConditionPathExists=/boot/do_purge_kernels was not met Feb 12 15:05:47 linux-4i6w systemd[1]: Stopped Purge old kernels. Feb 12 15:05:52 linux-4i6w systemd[1]: Started Purge old kernels What went wrong? Why is " systemctl start purge-kernels.service" notworking? What is this kernel-firmware-20130714git-5.1.noarch doing on my kernel list? -- Linux User 183145 using KDE4 and LXDE on a Pentium IV , powered by openSUSE 13.1 (i586) Kernel: 3.13.2-14.gb59b809-default KDE Development Platform: 4.12.2 15:34pm up 0:29, 3 users, load average: 2.97, 5.49, 4.10 ___________________________________________________________ indomail - Your everyday mail - http://indomail.indo.net.id ___________________________________________________________ indomail - Your everyday mail - http://indomail.indo.net.id -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 10

[opensuse] systemd: how do I get complete error messages?
by Joachim Schrod 15 Feb '14

15 Feb '14

Hi, "systemctl status" and "systemd-journalctl" shorten a line of a service message output to the line length of my terminal. What is the option to make them not nanny-nurse me and provide me with all information that I need to adress errors in service startups? Piping to cat or less even shorten it more, they seem to assume a line-length of 80. I read the man pages of "systemctl status" and systemd-journalctl, and found no information there. How do I get the whole error message out of systemd? AFAICS, there is no obvious way to deliver me my full error messages of my own services on my own system, at least not according to man pages. I'm just the admin, and I have to bow before the decision that every message must fit the line length of my (virtual) terminal. Well, super decision. FWIW; the error message that I wanted to acces was Feb 15 01:47:12 puma puppet-master[1422]: Could not parse for environment production: Syntax error at '.' at /etc/puppet...npc.de (output of systemd-journalctl_SYSTEMD_UNIT=puppetmaster.service. systemd status wouldn't tell me that much... :-/) Even in the largest window configuration of my terminal it has not enough information where the syntax error is. Not being able to read error message because a service wants to nanny me concerning my terminal line length sucks seriously. Please, tell me: what is the systemd/systemctl option to turn off this nanny-behavior and get me *all* of my error messages. Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod, Roedermark, Germany Email: jschrod(a)acm.org -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 6

[opensuse] Kmail & Exchange EWS
by Ciro Iriarte 15 Feb '14

15 Feb '14

Good afternoon, anybody knows if KMail/Kontact has EWS support?. I see Evolution has it, but I would like to keep my current mail client. Regards, -- Ciro Iriarte http://iriarte.it -- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] 12.3: yast2 *removes* apps when told not to upgrade them?
by jdebert 14 Feb '14

14 Feb '14

Did a small update using yast2 to see if there were any updates missed by zypper, because sometimes there are. In this case, there were several updates to ffmpeg with a vendor change. Yast2 complained about vendor changes to the newer versions, never warning that it was about to remove the installed packages. I told it to not upgrade anything. It went ahead and installed a new, unrelated package and then removed all the ffmpeg and related packages. This kind of theing happened before in 12.3 and I had to reinstall the removed packages. What is going on? I don't recall it behaving this way before 12.3. jd -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 5

[opensuse] 13.1 boot time/shutdown
by Wolfgang Rosenauer 14 Feb '14

14 Feb '14

Hi, let me first cite from another mail on the opensuse lists. > On the flipside, I own a machine that boots so fast, every time I > change the branding package for Plymouth, I need to build a second > version with enforced delays to purposefully slow the boot process > down in order to test whether or not the changes I've made are > working, because normally plymouth is finished and X is launching > before my LCD has changed it's resolution from Grub2 to Plymouth.. so > in my case, Plymouth is actually adding needless seconds to my boot > process and causing more flickers than if it wasn't there > > But as wolfgangs reply shows, my situation is not universal. > > If someone steps up and maintains it, great > > Wolfgang - have you installed systemd-analyze and run "systemd-analyze > blame" and "systemd-analyze plot > output.svg" to get a picture of > what is taking so long on your boot? So now I completely replaced my hardware with a very powerful completely new one. Latest Intel core i5 Haswell + SSD. No software raid anymore. Just a very simple setup with one disk. And I'm still really wondering how you can boot that fast. My boot time is regularly still 45 seconds (almost exactly the same as with my old hardware). Hygiea:~ # systemd-analyze blame 30.883s systemd-udev-settle.service 5.825s network.service 5.427s network(a)enp0s25.service 3.034s cifs.service 1.000s systemd-vconsole-setup.service ... What is this systemd-udev-settle.service doing? Nobody could tell me so far. Could it be related to USB devices? I have some of them connected which have card readers attached. The network service also is a bit strange given that it is a static configuration. In the log file the big pause looks like this: 2014-02-13T07:13:01.986838+01:00 Hygiea kernel: [ 3.514367] sd 7:0:0:1: Attached scsi generic sg5 type 0 2014-02-13T07:13:01.986838+01:00 Hygiea kernel: [ 3.606936] sd 7:0:0:0: [sdd] Attached SCSI removable disk 2014-02-13T07:13:01.986838+01:00 Hygiea kernel: [ 3.618720] sd 7:0:0:1: [sde] Attached SCSI removable disk 2014-02-13T07:13:01.986839+01:00 Hygiea kernel: [ 33.722749] usblp0: removed 2014-02-13T07:13:01.986840+01:00 Hygiea kernel: [ 33.875790] usb 3-3: reset high-speed USB device number 3 using xhci_hcd The other issue I still (or more again) have: shutdown does not work at all. It just stays on when it reached the final shutdown according to systemd's output and this is also after around 2 minutes. All that is really new since 13.1 and it got only worse with completely new hardware. This is really annoying. Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

10 18

[opensuse] Virtualization: Attaching USB in KVM
by Patrick Vanguardia 14 Feb '14

14 Feb '14

Hi, I am having problem attaching a usb device. I tried to search the net on how but I am unable to since I am getting error. lsusb output Bus 002 Device 003: ID 051d:0002 American Power Conversion Uninterruptible Power Supply my xml file. <hostdev mode='subsystem' type='usb'> <source> <vendor id='0x051d'/> <product id='0x0002'/> </source> </hostdev> Here's the exact command. Doing it as root. Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # attach-device Win8 /etc/libvirt/qemu/usb_device.xml error: Failed to attach device from /etc/libvirt/qemu/usb_device.xml error: Path '/dev/bus/usb/000/000' is not accessible: No such file or directory virsh # KVM patterns version Name: efont-unicode-bitmap-fonts Version: 0.4.2-223.1.2 Name: xorg-x11-fonts Version: 7.6-27.1.2 Name: libvirt Version: 1.1.2-2.14.2 Name: xorg-x11-fonts-core Version: 7.6-27.1.2 Name: tftp Version: 5.2-7.1.2 Name: virt-manager Version: 0.9.5-6.1.3 Name: libvirt-daemon-qemu Version: 1.1.2-2.14.2 Name: patterns-openSUSE-kvm_server Version: 13.1-13.6.1 Name: virt-viewer Version: 0.5.7-3.1.4 Name: xauth Version: 1.0.7-6.1.2 Name: tightvnc Version: 1.3.10-14.2.1 Name: fontconfig Version: 2.11.0-4.1 Name: fonts-config Version: 20080121-82.2.1 Name: bridge-utils Version: 1.5-16.1.2 Name: vm-install Version: 0.7.8-4.1 Name: kvm Version: 1.6.0-3.1.1 Any help would be appreciated. Thanks -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] failing samsung scx-3400 printer install on suse 13,1-86_64
by Julien Michielsen 13 Feb '14

13 Feb '14

I tried to install my samsung scx-3400 printer on my suse 13.1-86_64 but the installation fails. Below please find my machine's reaction on the instal- lationscript that comes with samsungs printer software for linux (ULD_Linux_V1.00.06): local/uld # ./install.sh **** Running install **** Press Enter to continue or q and then Enter to quit: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - **** Do you agree ? [y/n]: y ./noarch/packet.sh: line 310: 09: value too great for base (error token is "09") **** Install finished In the past I could install the samsung without problems. The problem might be caused by the 86_64-version of Suse. Anyone been able to install the samsung driver on a 86_64-version of Suse? Thanks Julien -- Julien Michielsen julien_at_michkloo.xs4all.nl -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 1

[opensuse] 12.3 64-bit KDE 4 (latest) - laptop hibernation failure
by Carl Hartung 13 Feb '14

13 Feb '14

Hi All, This has been working fine for a few months so I've no idea what the problem could be. Every morning, I suspend the system to disk so I can swap drives (it's a laptop) and boot to ... ahem ... Windows, which is a requirement for work. At the end of the day, I shut down, swap drives and boot back to my session. Well, this morning the progress bar stopped fairly early, at about ~10%, and it stayed there for a few minutes. Then the screen went dark for a few moments more and the hard drive was still 'working' ... then messages appeared on the screen which led me to believe it was waking back up ... which I'm fairly certain is what was happening. Those messages were identical to what I've seen when it's waking up. But it didn't wake up. It stalled in that state for a very long time. So long, in fact, that I had to give up waiting and power the system off, swap my drives so I could get on with my work. I'm hoping to get some pointers here about diagnosing what's happened and restoring the system to operation this evening. Thanks in advance for any tips or help you might offer. regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 5

[opensuse] how to turn off system updater
by Peter 13 Feb '14

13 Feb '14

I've just done my first install of 13.1 and noted this new System Updater applet in the system tray. As with previous iterations of such things, I find its functionality limited and I want to get rid of it. Previously with the Apper service I could stop that in KDE's System Services control. I've stopped and unticked that service again but this applet still pops up on reboot and seems independent. Its only configuration on a right-click is for setting a keyboard shortcut. I could hide it from the system tray but presumably that won't stop it running in the background. I do my updates in YaST and until the day I can get all the same functionality and level of detail in an applet then things shall remain that way. Though this applet finds and notifies of updates, clicking the + symbol next to any item always fails to retrieve further details, so it is redundant for me. Where can I turn it off? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

8 13