October 2013 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] openQA
by Guido Berhoerster 21 Oct '13

21 Oct '13

Hi, why haven't there been any openQA runs on Factory and 13.1? At Beta/RC time it is more important than ever and there are e.g. problems net-installing the Xfce desktop post-Beta1 where openQA would really be helpful. -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

15 33

[opensuse-factory] RC 13.1 nfs, autofs problem
by Paweł Wieczorkiewicz 21 Oct '13

21 Oct '13

Hi, Is this a known issue? I am trying to restart (systemctl) autofs. If so, could someone point me to the bug regarding this: /var/log/messages:2013-10-20T15:07:29.338919+02:00 pc kernel: [24755.614327] traps: automount[7643] general protection ip:7f075cf823d8 sp:7fffec21f668 error:0 in libpthread-2.18.so[7f075cf71000+18000] Thanks! BR, Pawel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 4

Re: [opensuse-factory] Re: 2 questions about 13.1 RC1
by "Stefan Brüns" 20 Oct '13

20 Oct '13

Am 19.10.13, schrieb Jan Engelhardt <jengelh(a)inai.de>: > > In XFCE, the same occurs and was only "fixed" by installing gvfs. > (wtf does udisks need gvfs?) > Of course I could just manually mount(8) them, which I fathom Dolphin > might just do (which would also explain why it needs root, if it does). XFCE might depend on gvfs, udisks does not. You can mount devices using udisk (iirc the CLI tool is called udiskctl), who is allowed to do what depends on your policykit settings (/etc/polkit-default-privs.*) Dolphin uses udisks via its solid library. On KDE, you can (un)mount partitions from Dolphin, from the Device Notifier, from Konqueror ... Policykit settings apply here as well. Regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen phone: +49 241 53809034 mobile: +49 151 50412019 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 2

[opensuse-factory] Two XFCE problems on 13.1 RC1
by Carlos E. R. 20 Oct '13

20 Oct '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have two problems with XFCE. 1) Log out is impossible. Solution seems to be install "iceauth" (bug 845264) 2) Once "iceauth" is installed, I can log out, but it doesn't ask to save settings on log out (setting to "ask on log out" is set). Is there a report on (2) ? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlJhy+QACgkQtTMYHG2NR9VL9ACgiTASVdnHsWmAUDUgydJTslbU cckAnA7FaFgstMyGoYAuCQR9vdQElOub =ccZq -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 10

[opensuse-factory] [13.1 RC1] XFCE - of two installs, one gets ibus, one not.
by Carlos E. R. 20 Oct '13

20 Oct '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, On two installs, one of the two gets ibus installed and activated. What for? AFAIK, the Spanish keyboard does not need that. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlJivXsACgkQtTMYHG2NR9WzpACfVnmGGDs7mWDQ76hOq2lIBRTT m14AniJpPIH7e1zZsAWa+U9OGqdUST1c =kHPh -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 3

[opensuse-factory] 13.1: no NIC configured at boot after zypper dup upgrade
by Greg Freemyer 18 Oct '13

18 Oct '13

On Wed, Oct 16, 2013 at 4:52 PM, lynn <lynn(a)steve-ss.com> wrote: > On Wed, 2013-10-16 at 16:18 -0400, Greg Freemyer wrote: >> On Wed, Oct 16, 2013 at 2:40 PM, Cristian Rodríguez >> <crrodriguez(a)opensuse.org> wrote: >> > El 16/10/13 15:29, Rich Coe escribió: >> >> I'm running 13.1. >> >> I have a fixed ip-address configured for eth0 and it supposed to config with ifup. >> >> >> >> On boot, eth0 does not get configured. >> >> Running 'ifup eth0' does not configure eth0 either. >> >> >> >> Any tips to configure eth0 at boot or diagnose the issue? >> >> >> >> Thanks. >> >> >> > >> > There is no eth0 or eth1 or whatever eth.. by default now. interfaces >> > are named according to >> > http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfac… >> > .. that document contains instructions to "go back" to the old names.. >> >> >> Christian, >> >> I opened a bugzilla yesterday because after a 12.3 => 13.1 >> upgrade I didn't have a configured interface of any name. >> >> <https://bugzilla.novell.com/show_bug.cgi?id=845886> >> >> I had to go into yast and configure it before it showed up with any name. >> >> After configuring via yast, it showed up when I ran ifconfig. I >> assumed it was VMware related, but I don't know. >> >> Greg > > Hi > 12.3 to 13.1 upgrade same here but on vbox. The upgrade knocked out what > was usually eth0. ifup failed. I too ran yast where I found that the > default route had been deleted. I re-entered it and yast completed > whereupon ifup eth0 began working again. > > Will this be the norm for the upgrade to 13.1? > Thanks, > L x Lynn, Did you open a bugzilla? If this is not a pure VMware related bug, this is seeming like a major / potential showstopper bug to me. My bugzilla again is: <https://bugzilla.novell.com/show_bug.cgi?id=845886> I have it set as priority "none" currently because I thought it only impacted VMware installs. I repeated my upgrade test of VWware appliance from 12.3 => 13.1 on another VM. I used: - Set Repos to 12.3 OSS and 12.3 OSS upgrade repos only. - zypper dup to ensure a pure 12.3 environment was in place - change the 2 repos to the 13.1 equivalents - zypper dup - choose uninstall vmware client packages (2 different interactions with zypper) - let it run to completion - reboot - login as root - ifconfig The only interface displayed is lo (loopback). I don't need this VM to be functional, so I'll leave it like that if anyone wants me to do any troubleshooting. If you want it properly tracked, please ask via bugzilla. Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 7

[opensuse-factory] 2 questions about 13.1 RC1
by Roman Bysh 18 Oct '13

18 Oct '13

Two (2) questions about 13.1 RC1 which I installed (clean install) on my wife's computer: 1. Where in blue-blazes does one find a USB stick when it is mounted in an USB port?! 1b Answer Click on up arrow in the system tray to see your Device Notifier. 2. How does one login as another user - as root for instance - when either (a) booting the system or (b) when one goes to Logout and then login as, say, root?! 2b Answer I always set in in Yast-->Security and Services-->User and Group Management-->Select the Expert Options-->click on dropdown arrow and select Login Settings A Display Manager Login Settings window appears. Under _User_ Login to Log In--> and select a different user for auto login. Click on the OK buttons. Cheers! Roman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] 13.1: no eth0 configured at boot
by Rich Coe 18 Oct '13

18 Oct '13

I'm running 13.1. I have a fixed ip-address configured for eth0 and it supposed to config with ifup. On boot, eth0 does not get configured. Running 'ifup eth0' does not configure eth0 either. Any tips to configure eth0 at boot or diagnose the issue? Thanks. -- Rich Coe rcoe(a)wi.rr.com -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

7 14

[opensuse-factory] Packman repository for 13.1 RC1
by Bob Williams 18 Oct '13

18 Oct '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Is there a Packman repository for openSUSE 13.1? I need the broadcom wifi drivers, which are usually available from Packman. The version of broadcom.wl in the Packman 12.3 repo fails to provide one dependency. Bob - -- Bob Williams System: Linux 3.7.10-1.16-desktop Distro: openSUSE 12.3 (x86_64) with KDE Development Platform: 4.10.5 "release 4" Uptime: 18:00pm up 3 days 7:23, 3 users, load average: 0.25, 0.20, 0.23 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJgY2UACgkQ0Sr7eZJrmU6IaQCfSnCUCck+p1a3ERxAe0WvmZD3 IOIAnR6/ft9bYZtvAOiI4uAhdSPFvr8I =1a/A -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 4

[opensuse-factory] 13.1 rc1 YaST2 NFS client configuration error. bug 845620
by Steven Hess 17 Oct '13

17 Oct '13

bug 845620 I raised this bug and it says it's unresolved. On a clean install of 13.1 rc1 Hangs at 50% then fails. I did a clean install as my previous install never would properly shut down after I fiex it by adding the server to my hosts file. It would hit the Plymouth shut doen screen and just stop. How do I proceed since this is not fixed I can really use this machine for much or really do any testing? If you want testing it's got to be something I can more or less use as my general computing desktop I'd really like to keep testing. 2013-10-17T18:22:30.833114+00:00 linux-8vd9 rpcbind[7851]: Cannot open '/var/lib/rpcbind/rpcbind.xdr' file for reading, errno 2 (No such file or directory) 2013-10-17T18:22:30.833591+00:00 linux-8vd9 rpcbind[7851]: Cannot open '/var/lib/rpcbind/portmap.xdr' file for reading, errno 2 (No such file or directory) 2013-10-17T18:22:31.444803+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: unable to resolve 192.168.1.100 to hostname: Name or service not known 2013-10-17T18:22:31.445256+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: failed to read service info 2013-10-17T18:22:31.465269+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: unable to resolve 192.168.1.100 to hostname: Name or service not known 2013-10-17T18:22:31.465781+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: failed to read service info 2013-10-17T18:22:31.480243+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: unable to resolve 192.168.1.100 to hostname: Name or service not known 2013-10-17T18:22:31.480669+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: failed to read service info 2013-10-17T18:22:31.494420+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: unable to resolve 192.168.1.100 to hostname: Name or service not known 2013-10-17T18:22:31.494821+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: failed to read service info 2013-10-17T18:22:31.508608+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: unable to resolve 192.168.1.100 to hostname: Name or service not known 2013-10-17T18:22:31.508970+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: failed to read service info 2013-10-17T18:22:31.522730+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: unable to resolve 192.168.1.100 to hostname: Name or service not known 2013-10-17T18:22:31.523147+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: failed to read service info 2013-10-17T18:22:31.536442+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: unable to resolve 192.168.1.100 to hostname: Name or service not known 2013-10-17T18:22:31.536783+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: failed to read service info 2013-10-17T18:22:31.550556+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: unable to resolve 192.168.1.100 to hostname: Name or service not known 2013-10-17T18:22:31.550928+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: failed to read service info 2013-10-17T18:22:31.564544+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: unable to resolve 192.168.1.100 to hostname: Name or service not known 2013-10-17T18:22:31.565059+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: failed to read service info 2013-10-17T18:22:31.585006+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: unable to resolve 192.168.1.100 to hostname: Name or service not known 2013-10-17T18:22:31.585447+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: failed to read service info 2013-10-17T18:22:31.600394+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: unable to resolve 192.168.1.100 to hostname: Name or service not known 2013-10-17T18:22:31.600731+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: failed to read service info 2013-10-17T18:22:31.614629+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: unable to resolve 192.168.1.100 to hostname: Name or service not known 2013-10-17T18:22:31.615094+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: failed to read service info 2013-10-17T18:22:31.628290+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: unable to resolve 192.168.1.100 to hostname: Name or service not known 2013-10-17T18:22:31.628712+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: failed to read service info 2013-10-17T18:22:31.645018+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: unable to resolve 192.168.1.100 to hostname: Name or service not known 2013-10-17T18:22:31.645418+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: failed to read service info 2013-10-17T18:22:31.658285+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: unable to resolve 192.168.1.100 to hostname: Name or service not known 2013-10-17T18:22:31.658652+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: failed to read service info 2013-10-17T18:22:31.672487+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: unable to resolve 192.168.1.100 to hostname: Name or service not known 2013-10-17T18:22:31.672898+00:00 linux-8vd9 rpc.gssd[7881]: ERROR: failed to read service info 2013-10-17T18:27:30.902288+00:00 linux-8vd9 systemd[1]: nfs.service operation timed out. Terminating. 2013-10-17T18:27:30.903219+00:00 linux-8vd9 systemd[1]: Failed to start LSB: NFS client services. Steven -- ____________ Apply appropriate technology. Use what works without prejudice. Steven L Hess ARS KC6KGE DM05gd22 openSUSE Linux 12.3 KDE Known as FlameBait and The Sock Puppet of Doom. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0