November 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 847783] New: Bridge does not add ethX interfaces when they're marked "on cable connection" and offline during system start
by bugzilla_noreply＠novell.com 04 Nov '13

04 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=847783 https://bugzilla.novell.com/show_bug.cgi?id=847783#c0 Summary: Bridge does not add ethX interfaces when they're marked "on cable connection" and offline during system start Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: HP OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: spoil(a)spoilbase.zapto.org QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Firefox/24.0 1. Go to YAST2 - Network Devices. 2. Configure a couple of eth-interfaces (in my case: eth1, eth2, eth3, eth4 on an Intel igb board, eth5 on a Realtek-add-on-card, eth6 as an on-board-Broadcom) 3. Mark them as active "on cable connection" in YAST2 4. Add a bridge (in my case br0) 5. Mark that bridge as brought up "on boot". 6. Add the nethwork interfaces (see no. 2) as bridged devices. 7. Save. 8. Configure the dhcpd to serve br0, Save, reboot. Expected behaviour: The bridge should be permanent, while the eth-interfaces may be switched off for power saving. The eth-devices should become active as they detect a cable connection and start communicating with br0. Found behaviour: Those eth-devices that were plugged in during boot do work as expected. All others are not added to the bridge. When the formerly inactive eth-devices receive a cable, they do come up as expected, but they do not get added to the bridge and thus do not receive dhcp addresses. The remain connected but dead. Analysis: "brctl show" shows that only those devices that were plugged in during boot up get added to the bridge. Those that were offline during boot, never appear on the bridge, regardless of whether they're connected to a cable or not. Workaround: Add interfaces manually ("brctl addif ethX") somewhen after boot. I actually added a cron-job that waits for a minute after reboot and then adds all the required interfaces. Finding: The config scripts seem to handle this scenario very misleadingly. Reproducible: Always Steps to Reproduce: 1. Go to YAST2 - Network Devices. 2. Configure a couple of eth-interfaces (in my case: eth1, eth2, eth3, eth4 on an Intel igb board, eth5 on a Realtek-add-on-card, eth6 as an on-board-Broadcom) 3. Mark them as active "on cable connection" in YAST2 4. Add a bridge (in my case br0) 5. Mark that bridge as brought up "on boot". 6. Add the nethwork interfaces (see no. 2) as bridged devices. 7. Save. 8. Configure the dhcpd to serve br0, Save, reboot. Actual Results: Those eth-devices that were plugged in during boot do work as expected. All others are not added to the bridge. When the formerly inactive eth-devices receive a cable, they do come up as expected, but they do not get added to the bridge and thus do not receive dhcp addresses. The remain connected but dead. Expected Results: The bridge should be permanent, while the eth-interfaces may be switched off for power saving. The eth-devices should become active as they detect a cable connection and start communicating with br0. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 10

[Bug 843169] New: sysconfig: remove blacklist of dropped drivers
by bugzilla_noreply＠novell.com 04 Nov '13

04 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=843169 https://bugzilla.novell.com/show_bug.cgi?id=843169#c0 Summary: sysconfig: remove blacklist of dropped drivers Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: mt(a)suse.com ReportedBy: mmarek(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Several drivers are blacklisted in /etc/modprobe.d/50-blacklist.conf, but have been dropped from the upstream kernel: stradis dropped in 2.6.38 (39c3d48) eepro100 dropped in 2.6.29 (6b1abba) slamr, slusb OK, these are not mainline drivers, but 10.3 was the last release to ship smartlink-softmodem-kmp ich2rom replaced with ichxrom in 2.6.12 (304aa41). BTW, is there a bugzilla explaining why these drivers are blacklisted? eth1394 dropped in 2.6.37 (66fa12c) uhci both uhci and usb-uhci were dropped in 2.5.27 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 10

[Bug 843141] New: sysconfig: blacklist for sk98lin no longer needed
by bugzilla_noreply＠novell.com 04 Nov '13

04 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=843141 https://bugzilla.novell.com/show_bug.cgi?id=843141#c0 Summary: sysconfig: blacklist for sk98lin no longer needed Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: mt(a)suse.com ReportedBy: mmarek(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Please remove this part: # This driver is obsolete and should never be loaded as default. # See https://bugzilla.novell.com/show_bug.cgi?id=146930 blacklist sk98lin because the sk98lin driver has been dropped from the kernel in 2.6.26: $ git describe --contains 548c36e983f346621b5cb9ab031e4383e9996576 v2.6.26-rc1~1138^2~390^2~34 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 4

[Bug 826945] New: Temperature increase after S2Ram, but not after S2disk
by bugzilla_noreply＠novell.com 04 Nov '13

04 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=826945 https://bugzilla.novell.com/show_bug.cgi?id=826945#c0 Summary: Temperature increase after S2Ram, but not after S2disk Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: axel.braun(a)gmx.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0 I run a T520 under openSUSE 12.3, and use s2ram quite frequently. I noticed that in some cases the average CPU temperature rises from 44-48 degrees to 64-68 degrees after wake-up, and stays. I did not notice additional processes. After S2disk the CPU temperature remains around 44-48. This sounds to me like some registers or whatever are not properly reset after s2ram - can that be? Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 10

[Bug 843659] New: systemd: syslog.service vs. syslog-ng-service ?
by bugzilla_noreply＠novell.com 04 Nov '13

04 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=843659 https://bugzilla.novell.com/show_bug.cgi?id=843659#c0 Summary: systemd: syslog.service vs. syslog-ng-service ? Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: per(a)computer.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:11.0) Gecko/20100101 Firefox/11.0 I installed syslog-ng, and then started it with "systemctl start syslog", no problems. Then I tried to enable it: linux:~ # systemctl enable syslog Failed to issue method call: No such file or directory linux:~ # systemctl enable syslog.service Failed to issue method call: No such file or directory linux:~ # systemctl status syslog syslog-ng.service - System Logging Service Loaded: loaded (/usr/lib/systemd/system/syslog-ng.service; enabled) Active: active (running) since Wed 2013-10-02 11:08:12 CEST; 2min 16s ago Process: 6518 ExecStartPre=/usr/sbin/syslog-ng-service-prepare (code=exited, status=0/SUCCESS) Main PID: 6522 (syslog-ng) CGroup: /system.slice/syslog-ng.service └─6522 /usr/sbin/syslog-ng -F Oct 02 11:08:12 taggart7 systemd[1]: Starting System Logging Service... Oct 02 11:08:12 taggart7 systemd[1]: Started System Logging Service. linux:~ # systemctl enable syslog-ng.service Why? It doesn't seem very intuitive to have two names ? Reproducible: Always -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 3

[Bug 848819] New: libvirt can't start default network with apparmor enabled
by bugzilla_noreply＠novell.com 04 Nov '13

04 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=848819 https://bugzilla.novell.com/show_bug.cgi?id=848819#c0 Summary: libvirt can't start default network with apparmor enabled Classification: openSUSE Product: openSUSE 13.1 Version: RC 2 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: AppArmor AssignedTo: suse-beta(a)cboltz.de ReportedBy: dmacvicar(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- F, [2013-11-04T10:12:12.921061 #5719] FATAL -- : Call to virNetworkCreate failed: internal error: Child process (/usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf) unexpected exit status 3: dnsmasq: cannot read /var/lib/libvirt/dnsmasq/default.conf: Permission denied Disabling apparmor.service and everything works. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 1

[Bug 847488] New: Cannot login when LDAP authentication is chosen
by bugzilla_noreply＠novell.com 04 Nov '13

04 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=847488 https://bugzilla.novell.com/show_bug.cgi?id=847488#c0 Summary: Cannot login when LDAP authentication is chosen Classification: openSUSE Product: openSUSE 13.1 Version: RC 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: st-malcolm.moore(a)whsg.info QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 When you install select LDAP authentication Enter details etc When the machine finished and reboots you can't log in as anything as only the password box is shown. There is no option to enter your username Reproducible: Always Steps to Reproduce: 1. Install 2. Select LDAP for user auth 3. No box to enter username Actual Results: Cannot enter a user name Expected Results: Able to login -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 2

[Bug 842205] New: 'zypper dup' from 12.3 to 13.1 renders system unusable
by bugzilla_noreply＠novell.com 04 Nov '13

04 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=842205 https://bugzilla.novell.com/show_bug.cgi?id=842205#c0 Summary: 'zypper dup' from 12.3 to 13.1 renders system unusable Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: kkaempf(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Development Blocker: --- Since years ago, I use 'zypper dup' for major version upgrades. This time, upgrading from 12.3 to 13.1Beta1 failed and leaves my system unusable. I haven't rebooted yet. I can still type commands in (gnome-)shell, but they don't respond. I can switch consoles but login times out after 60 seconds. So I can't even login as root and initiate a proper shutdown :-( -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 4

[Bug 848449] New: systemsmanagement:puppet: Bug
by bugzilla_noreply＠novell.com 04 Nov '13

04 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=848449 https://bugzilla.novell.com/show_bug.cgi?id=848449#c0 Summary: systemsmanagement:puppet: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: SLES 11 Status: NEW Severity: Critical Priority: P5 - None Component: 3rd party software AssignedTo: boris(a)steki.net ReportedBy: jens.schanz(a)mueller.de QAContact: opensuse-communityscreening(a)forge.provo.novell.com CC: jatan(a)suse.com, nkrinner(a)suse.com, dlovasko(a)suse.com Found By: Integration Test Blocker: Yes File /etc/init.d/sysconfig contains a option port which is referenced in th init script but not known by puppet agent: /etc/sysconfig/puppet .. ## Type: integer ## Default: 8140 # # If you wish to specify the port to connect to do so here # PUPPET_PORT=8140 .. /etc/init.d/puppet .. PUPPET_OPTS="agent" [ -n "${PUPPET_SERVER}" ] && PUPPET_OPTS="${PUPPET_OPTS} --server=${PUPPET_SERVER}" [ -n "$PUPPET_LOG" ] && PUPPET_OPTS="${PUPPET_OPTS} --logdest=${PUPPET_LOG}" [ -n "$PUPPET_PORT" ] && PUPPET_OPTS="${PUPPET_OPTS} --port=${PUPPET_PORT}" .. Try to start puppet with the options from the init script: /usr/bin/puppet agent --server=puppet --logdest=/var/log/puppet/puppet.log --port=8140 Have a look in the logfile at "logdest": Thu Oct 31 08:21:43 +0100 2013 Puppet (err): Could not parse application options: invalid option: --port=8140 Puppet will not start with the option "--port", because the option is unknown by "puppet agent --help". Problem exists since upgrade to Puppet 3.3.1 6 days ago. Affected is SLES11 SP2 and SLES11 SP3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 2

[Bug 848216] New: apparmor fails to load libvirt profile
by bugzilla_noreply＠novell.com 04 Nov '13

04 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=848216 https://bugzilla.novell.com/show_bug.cgi?id=848216#c0 Summary: apparmor fails to load libvirt profile Classification: openSUSE Product: openSUSE 13.1 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: AppArmor AssignedTo: suse-beta(a)cboltz.de ReportedBy: rhafer(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Development Blocker: --- I get this when restarting apparmor on a System with the latest 13.1 code installed: Oct 30 09:20:01 farnsworth systemd[1]: Starting LSB: AppArmor initialization... Oct 30 09:20:01 farnsworth boot.apparmor[10917]: Starting AppArmor AppArmor parser error for /etc/apparmor.d/usr.sbin.libvirtd in /etc/apparmor.d/usr.sbin.libvirtd at line 52: Invalid mode, 'x' must be preceded by exec qualifier 'i', 'p', 'c', or 'u' Oct 30 09:20:01 farnsworth boot.apparmor[10917]: /etc/apparmor.d/usr.sbin.libvirtd failed to load..failed Oct 30 09:20:01 farnsworth boot.apparmor[10917]: ..done Oct 30 09:20:01 farnsworth systemd[1]: Started LSB: AppArmor initialization. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 4