November 2014 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] (how) are if-up.d/* scripts managed under opensuse 13.2-RELEASE's wicked?
by grantksupport＠operamail.com 13 Nov '14

13 Nov '14

(how) are if-up.d/* scripts managed under opensuse 13.2+ wicked? I'm not yet clear if this "TODO" (https://github.com/openSUSE/wicked/issues/56) implies that they are not. currently, in my /etc/sysconfig/network i've an if-up.d script if-up.d/99-ethX-setup which, on 13.1, prior to an upgrade to 13.2 -- with its 'wicked' package -- would always exec as expected, no matter the script's content. now, after the 13.2 upgrade, the script no longer execs on boot. after boot, once @ shell, if I exec manually sh -x /etc/sysconfig/network/if-up.d/99-ethX-setup it works without issue. in journalctl -xb, I don't see any evidence of the scripts' exec on boot. Is there a config change needed, or is support for preexisting if-up.d/* scripts lacking in wicked? This message from 'mge@suse' in a prior @factory thread http://lists.opensuse.org/opensuse-factory/2013-12/msg00084.html suggests "... wicked will read and use the existing configuration files from /etc/sysconfig/network and configure your network accordingly. ..." which I read as you CAN still use old if-up.d/* scripts, and they'll be handled accordingly Is that the case in 13.2's wicked? or must my config be changed? -- 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] ipv6 over sit1 tunnel (via he.net/tunnelbroker.net) FAILs after 13.1(w/o wicked)->13.2(w/ wicked) upgrade
by grantksupport＠operamail.com 13 Nov '14

13 Nov '14

continuing to test/troubleshoot network after 13.1 -> 13.2 upgrade, on 13.1, ipv6 on my external intfc, over an HE.net IPv6 tunnel, is completely functional for both inbound & outbound traffic. after the 13.1 -> 13.2 upgrade, ipv6 connectivity over the tunnel is non-functioning the external and tunnel interface configs, used across dozens of machines here, cat ifcfg-eth0 STARTMODE='auto' BOOTPROTO='static' BROADCAST='' BRIDGE='no' DHCPCLASS='' MTU='' NETWORK='' NM_CONTROLLED='no' REMOTE_IPADDR='' USERCONTROL='no' IPADDR='X.X.X.A/24' GATEWAY='X.X.X.1' NETMASK='255.255.255.0' IPV6INIT='yes' IPV6_AUTOCONF='no' IPADDR6='2001:hhh:hhhh:hhh::2/64' PREFIXLEN6='64' cat ifcfg-sit1 STARTMODE='onboot' BOOTPROTO='static' TUNNEL='sit' TUNNEL_LOCAL_IPADDR='X.X.X.A' TUNNEL_REMOTE_IPADDR='H.H.H.H' IPADDR='2001:hhh:hhhh:hhh::2/64' TUNNEL_TTL='64' testing, ping6 to google: FAIL ( host nuq05s01-in-x00.1e100.net nuq05s01-in-x00.1e100.net has IPv6 address 2607:f8b0:4005:800::1000 ) ping6 -c1 2607:f8b0:4005:800::1000 PING 2607:f8b0:4005:800::1000(2607:f8b0:4005:800::1000) 56 data bytes From 2001:hhh:hhhh:hhh::2 icmp_seq=1 Destination unreachable: Address unreachable --- 2607:f8b0:4005:800::1000 ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms and, ping6 to gateway @ he.net: FAIL ping6 -c1 2001:hhh:hhhh:hhh::1 56 data bytes From 2001:iii:iiii:iii::7 icmp_seq=1 Destination unreachable: Address unreachable --- 2001:iii:iiii:iii::1 ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms and, ping6 to self: OK ping6 -c1 2001:hhh:hhhh:hhh::2 PING 2001:hhh:hhhh:hhh::2(2001:hhh:hhhh:hhh::2) 56 data bytes 64 bytes from 2001:hhh:hhhh:hhh::2: icmp_seq=1 ttl=64 time=0.445 ms --- 2001:hhh:hhhh:hhh::2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.445/0.445/0.445/0.000 ms and, ping6 to lan: OK ping6 -c1 2001:hhh:hhhh:hhh::7 ping6 -c1 2001:iii:iiii:iii::7 PING 2001:iii:iiii:iii::7(2001:iii:iiii:iii::7) 56 data bytes 64 bytes from 2001:iii:iiii:iii::7: icmp_seq=1 ttl=64 time=0.020 ms --- 2001:iii:iiii:iii::7 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.020/0.020/0.020/0.000 ms where routes are ip -6 route show 2001:hhh:hhhh:hhh::/64 dev sit1 proto kernel metric 256 2001:hhh:hhhh:hhh::/64 dev eth0 proto kernel metric 256 2001:iii:iiii:iii::/64 dev eth1 proto kernel metric 256 fe80::/64 dev sit1 proto kernel metric 256 fe80::/64 dev eth0 proto kernel metric 256 fe80::/64 dev eth1 proto kernel metric 256 fe80::/64 dev ifb0 proto kernel metric 256 default via 2001:hhh:hhhh:hhh::1 dev sit1 metric 1024 again, wicked's supposed to be drop-in, using prior configs. something's clearly off here. question: is it config ? or a bug? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 5

[opensuse-factory] state of 13.2+wicked [was:ipv6 over sit1 tunnel (via he.net/tunnelbroker.net) FAILs after 13.1(w/o wicked)->13.2(w/ wicked) upgrade]
by grantksupport＠operamail.com 12 Nov '14

12 Nov '14

On Wed, Nov 12, 2014, at 07:52 AM, Pawel Wieczorkiewicz wrote: > Could you please open a bug and attach logs as described here: > https://en.opensuse.org/openSUSE:Bugreport_wicked > > We will then take a look and decide what is happening. But among other > this one is not needed (red hat style): > IPV6INIT='yes' I'll start gathering info. Atm, here, wicked's a disaster. After upgrade of fully working/functional 13.1 systems to 13.2, currently (1) fails to exec/use /etc/syconfig/network/if-{up,down}.d/* scripts (2) fails to init/use tun* interfaces (3) fails to init IPv6 over sit tunnels (4) hardcodes dependencies in its systemd unit files on susefirewall -- ignoring any provision for, e.g., shorewall or other fw solutions (5) neglects correct usage of opensuse 13.2 systemd v210's network-pre.target for systemd unit/service ordering The only thing that works is 'simple' IPv4 functionality in /etc/sysconfig/network/ifcfg-* configs. It's difficult to isolate the problems to report cleanly. What's clear is that the upgrade has dropped production machines 'to their knees'. The fact (?) that the old/traditional 13.1 ifup/ifdown alternative has not just been replaced as default by wicked, but completely disabled/removed is -- a real concern for a release. If I'm wrong, I'm very happy to have that demonstrated. -- 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] digital clock's calender holiday settings are not saved when changed
by Roman Bysh 12 Nov '14

12 Nov '14

Hello List Mates, I noted that holidays or upcoming events did not show up in the systray's clock as they did with openSUSE 13.1. A bug report was submitted. See: https://bugzilla.novell.com/show_bug.cgi?id=902657 I was informed that it wasn't a bug but an omission to add it as part of installation. You have to install the package "kdebase4-workspace-plasma-calendar". Can this package be added as part of the mandatory installation (a dependency) or integrated into the base rpm? Cheers! Roman ------------------------------------------------ openSUSE -- Open Minds Open Sources Open Future ------------------------------------------------ http://linuxcounter.net/ #179293 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

[opensuse-factory] INFO: New reminder mails for openSUSE Tumbleweed build failures
by Dimstar / Dominique Leuenberger 12 Nov '14

12 Nov '14

Hi all, As apparently some maintainers are not aware of their packages failing in openSUSE:Factory (openSUSE Tumbleweed), I implemented a quick script today that finds all the current failures and sends a notification to the maintainer(s) (as defined in the metadata, same info as osc maintainer gives) in the hope that the maintainers will realize this. The notification is sent out after the package failed for 7 days. If there is already a submit request pending to Factory (which hopefully fixes the issue), the notification is suppressed (the staging process can sometimes take longer, and I think it would be annoying to be reminded in this case). The message looks like the one below. Feel free to let me know your thoughts about this; if you think it's useful or not. The aim, of course, is to get Tumbleweed in the best possible shape for our users. Cheers, Dominique -------- Forwarded Message --------From: DimStar To: Dominique Leuenberger <dimstar> Subject: openSUSE Tumbleweed - open-vm-tools - Build fail notification Date: Tue, 11 Nov 2014 21:25:56 -0000 Dear Dominique Leuenberger Please be informed that the package 'open-vm-tools' in openSUSE Tumbleweed has not have a successful build since Sat Oct 18 07:52:54 2014. This can be due to an error in your package directly or could be caused by a package you depend on to build. In any case, please do your utmost to get the status back to building. You will get another reminder in a week if the package still fails by then. *** NOTE: This is an attempt to raise awareness of the maintainers about broken builds in Tumbleweed. Please let me know if you think this is useless and a waste of resources Kind regards, Dominique Leuenberger a.k.a DimStar -- Dimstar / Dominique Leuenberger <dimstar(a)opensuse.org> -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

7 16

[opensuse-factory] Which TW iso to use.
by Ken Schneider - Factory 12 Nov '14

12 Nov '14

I currently am using TW on my laptop. I always download the latest/newest install ISO but now I am not sure which one that should be. In the ISO folder the are ISO's for "current" and Snapshot_20141107. Which one is correct? And if they are both the same why offer both? -- Ken Schneider -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

[opensuse-factory] TW : Yast Bootloader : to see large Text whilst booting
by ellanios82 12 Nov '14

12 Nov '14

Hello List , - how please to adjust in yast , the Bootloader Grub2 to see Large Text for processes whilst booting : 1). Must i use the character-size Top-Box , or the character-size Lower Box ? 2). How to select size-Large ? [ i previously tried selecting "Text" and subsequently was unable to Boot! { something like error 'unrecognized character-code'} ] 3). then presumably i must : Delete "quiet splash=silent" from kernel command line .......... thanks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 5

[opensuse-factory] Dr. Racket crashes on launch
by alanbortu 11 Nov '14

11 Nov '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 As the title says, Dr. Racket crashes whenever I try to launch it and I get the following errors. I cannot seem to figure out what is wrong, it crashes regardless of nvidia or nouveau driers. Direct rendering works (confimed via glxinfo | grep direct). Currently using nvidia drivers on (new) Tumbleweed. This also happens when I try to use the text tool in GIMP. Output: http://paste.opensuse.org/view/raw/57350994 Any help would be appreciated. - -- Regards, Uzair Shamim -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJUYBO3AAoJEM66EOTZRH6+vhcQAI73DnA5+TEIERw4SOwukhCP mCsWxANDOX4UR180fCWH1dojf93/rvieSI1GXgty2Rs2ZXpStQTlkCjt7TFOKSEk MMu7l5P0sgLMnLdPxHIwPZ1EQv/tY/InXByRcv/kG1Sk+Xr553P1Iog4t/K8jYpP LXG56Z43cO7pOs5an7Z++A/yw1Rj1eg2LuBO42j24lZe80OwqmqVmdPK9x9u7OuH fDg7VvDncXsjsb7IoFZR5bIMbAmf0TdIbR47m6ZQzBbSPC5TZBppxMzCw9AoT+47 85Noe5HAfxZVzyNkqKJpu07nkKGgQr6lwilYg4gIvnUoFrCLftutOlGwajG3HrMf BY6VPa3a19kodXHz6E+EuZge01Gl/48yfXMvmDsSb5BVVPRU20M3twlti5G9Zz5R WMKAM1c3Nuz3AxUnczpf3JzdyXMKj8NIgYRT8JJ9gLadGD9ONB/wYUqcTqq4obwx bbl9qLZVZCYBVbpsMmSzXTmtlmExOHX3pkXR4Hi1GR6xbwoElSQmUaLABAH9yMyu caVfvApT6dYLVmH6U45GbGdeLnC+BHRWLviNbeRq/Z5Eyee0PPTlEqn0oI7Nog1E cgPuz1s74lV+kSf4mJX7ySw2Hcxy0Z2H8ae7I4sBXSSpwy+UM5xPVThcNjJK05Kz 67W+mgazSuSmUrOdyB1n =tR2N -----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

1 1

[opensuse-factory] shutdown or Leave restart do not work
by Constant Brouerius van Nidek 11 Nov '14

11 Nov '14

Have my fully updated Tumbleweed upgraded to the new Tumbleweed. Most things seem to work. My main problem is though that I cannot restart my computer. With #shutdown -r now the screen freezes and a hard reset is my only way out. Same goes for the Leave function in the KDE menu. Somebody knows where to look for the culprit? -- Linux User 183145 using KDE4 and LXDE on a Pentium IV , powered by openSUSE 20141107 (i586) Kernel: 3.17.1-1.g5c4d099-default KDE Development Platform: 4.14.2 19:57pm up 1:20, 2 users, load average: 1.04, 0.61, 1.14 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 4

[opensuse-factory] cannot print
by Patrick Shanahan 11 Nov '14

11 Nov '14

Something has happened to my printing. I can print test pages from the printer but nothing from my desktop computer. Following error log with debugging on for failed print job. error log: http://wahoo.no-ip.org/~paka/cups.error.log /etc/cups/cups.conf http://wahoo.no-ip.org/~paka/cups.conf openSUSE-Factory hp color laserjet 2840 hplip-hpijs-3.14.10-120.4.x86_64 hplip-sane-3.14.10-120.4.x86_64 hplip-3.14.10-120.4.x86_64 python-cupshelpers-1.4.5-5.1.noarch cups-devel-1.7.5-1.4.x86_64 cups-1.7.5-1.4.x86_64 cups-libs-1.7.5-1.4.x86_64 cups-client-1.7.5-1.4.x86_64 cups-pk-helper-0.2.5-5.1.x86_64 liboyranos0-cups-0.9.5-49.14.x86_64 cups-pdf-2.6.1-1.62.x86_64 python-cups-1.9.66-3.1.x86_64 cups-filters-ghostscript-1.0.58-35.6.x86_64 cups-ddk-1.7.5-1.4.x86_64 cups-libs-32bit-1.7.5-1.4.x86_64 how to trouble-shoot ?? ps: printer is networked and works fine from other work-stations including windows. tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 15