December 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 851393] New: systemd-journald spins with 100% cpu inside a lxc container
by bugzilla_noreply＠novell.com 09 Dec '13

09 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=851393 https://bugzilla.novell.com/show_bug.cgi?id=851393#c0 Summary: systemd-journald spins with 100% cpu inside a lxc container Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: werner(a)suse.com ReportedBy: mrueckert(a)suse.com QAContact: qa-bugs(a)suse.de CC: tbehrens(a)suse.com, fcrozat(a)suse.com Found By: --- Blocker: --- lxc container was created with 12.3 and then brought up to 13.1. since the switch to 13.1 the journald spins with 100% cpu load. strace showed: epoll_wait(7, {{EPOLLIN|EPOLLERR|EPOLLHUP, {u32=8, u64=8}}}, 1, -1) = 1 writev(2, [{"/dev/kmsg buffer overrun, some messages lost.", 45}, {"\n", 1}], 2) = 46 read(8, "", 8192) = 0 $ ls -ld /dev/{kmsg,console} crw--w---- 1 root tty 136, 10 Nov 20 17:27 /dev/console lrwxrwxrwx 1 root root 7 Nov 20 17:27 /dev/kmsg -> console $ lsof -n -p 13 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME [snip] systemd-j 13 root 0r CHR 1,3 0t0 2280686 /dev/null systemd-j 13 root 1w CHR 1,3 0t0 2280686 /dev/null systemd-j 13 root 2w CHR 1,3 0t0 2280686 /dev/null systemd-j 13 root 3u unix 0xffff8804394fbb00 0t0 2274149 /run/systemd/journal/stdout systemd-j 13 root 4u unix 0xffff8804325f9780 0t0 2274151 /run/systemd/journal/socket systemd-j 13 root 5u unix 0xffff88021ee67540 0t0 2274153 /dev/log systemd-j 13 root 6u unix 0xffff880126f2cc40 0t0 2283356 /run/systemd/journal/stdout systemd-j 13 root 7u 0000 0,9 0 3123 anon_inode systemd-j 13 root 8u CHR 136,10 0t0 13 /dev/console systemd-j 13 root 9u 0000 0,9 0 3123 anon_inode systemd-j 13 root 10u 0000 0,9 0 3123 anon_inode systemd-j 13 root 11u REG 0,38 3211264 2282663 /run/log/journal/8b3ef9aac360e8aeb8f1651e526fb833/system.journal systemd-j 13 root 12u unix 0xffff8803fd506440 0t0 2280923 /run/systemd/journal/stdout systemd-j 13 root 13u unix 0xffff8803e418c140 0t0 2283409 /run/systemd/journal/stdout systemd-j 13 root 14u unix 0xffff88041a259c00 0t0 2280925 /run/systemd/journal/stdout systemd-j 13 root 16u unix 0xffff880126f2c540 0t0 2283366 /run/systemd/journal/stdout systemd-j 13 root 17u unix 0xffff880171e24b40 0t0 2284729 /run/systemd/journal/stdout systemd-j 13 root 18u unix 0xffff88020d97d040 0t0 2290510 /run/systemd/journal/stdout systemd-j 13 root 19u unix 0xffff88020d83fc00 0t0 2283368 /run/systemd/journal/stdout -- 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 15

[Bug 849071] New: Boot cycle
by bugzilla_noreply＠novell.com 09 Dec '13

09 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=849071 https://bugzilla.novell.com/show_bug.cgi?id=849071#c0 Summary: Boot cycle Classification: openSUSE Product: openSUSE 13.1 Version: RC 2 Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: werner(a)suse.com QAContact: qa-bugs(a)suse.de CC: werner(a)suse.com, coolo(a)suse.de, fcrozat(a)suse.com Found By: Development Blocker: --- This happens on a virtual system but may also happen on a normal system if consoles are enabled and also I see several messages with [ *** ] A start job is running for dev-disk-by\x2d ... I see after booting into rescue mode from the RC2 boot image and mounting the root partition I have investigated /var/log/messages and /var/log/warn. -- 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 22

[Bug 851230] New: python3 packages (numpy, scipy, IPython, matplotlib) mising from 13.1 repo
by bugzilla_noreply＠novell.com 09 Dec '13

09 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=851230 https://bugzilla.novell.com/show_bug.cgi?id=851230#c0 Summary: python3 packages (numpy, scipy, IPython, matplotlib) mising from 13.1 repo Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Development AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: highwaystar.ru(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.11 Safari/537.36 SUSE/31.0.1650.11 13.1 repo missing python3-numpy, python3-scipy, python3-matplotlib, python3-IPython packages. There is python3-numpydoc (!) it is useless without python3-numpy at least. All this packages are stable with python3 and was included in 12.3 repo. Reproducible: Always Steps to Reproduce: 1. Try to search python3-numpy zypper se python3-numpy Actual Results: openSUSE repo miss essential scientific python3 packages. It is regression from 12.3. Expected Results: openSUSE 13.1 should provide numpy, scipy, IPython, matplotlib for python3. At least in update repo. -- 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 823645] New: scsi_dh* modules are loaded unconditionally
by bugzilla_noreply＠novell.com 09 Dec '13

09 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=823645 https://bugzilla.novell.com/show_bug.cgi?id=823645#c0 Summary: scsi_dh* modules are loaded unconditionally Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: mmarek(a)suse.com ReportedBy: jdelvare(a)suse.com QAContact: qa-bugs(a)suse.de CC: hare(a)suse.com, arvidjaar(a)gmail.com Found By: Community User Blocker: --- mkinitrd unconditionally includes and loads the following kernel modules: * scsi_dh * scsi_dh_alua * scsi_dh_emc * scsi_dh_hp_sw * scsi_dh_rdac This was done as a consequence of bug #727428. These modules are only needed when multipathing is in use, which only concerns a small number of systems. Thus these modules should not be loaded unconditionally. Doing so increases the size of the initrd, slows down the boot process, and eats memory for no good reason. Just because they are small is no excuse for not doing things properly. Loading 5 modules takes time, on every boot of every openSUSE system. The scsi_dh* modules should only be enabled on systems using multipath. -- 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 8

[Bug 802959] New: Screenlogger shows password field when not needed
by bugzilla_noreply＠novell.com 09 Dec '13

09 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=802959 https://bugzilla.novell.com/show_bug.cgi?id=802959#c0 Summary: Screenlogger shows password field when not needed Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: bart.otten85(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 My KDE has auto-inlog but also 'lock when resume' enabled. When the screen locker kicks in, there is a password input shown. As soon as I move the mouse, the locker disappears without me entering the password. Reproducible: Always Steps to Reproduce: 1. Auto inlog KDE (optional?) 1b. Set 'lock when resume' in KDE System > Energy > Advanced 2. Wait for screenlocker 3. Move mouse Actual Results: Screenlocker disappears Expected Results: 1.) User is asked for the password / locker does not disappear or 2.) There is no password input field shown I mark it as Major Feature broken as in case 1 this is a security risk. If the result should be 2, it's just a minor cosmetic/usability problem. -- 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 24

[Bug 847342] New: Create Project Application:ERP
by bugzilla_noreply＠novell.com 09 Dec '13

09 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=847342 https://bugzilla.novell.com/show_bug.cgi?id=847342#c0 Summary: Create Project Application:ERP Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: OBS Request AssignedTo: mrueckert(a)suse.com ReportedBy: axel.braun(a)gmx.de QAContact: adrian(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 I have build the OpenSource ERP System Tryton (www.tryton.org) in my private sandpit https://build.opensuse.org/project/show/home%3ADocB%3Apython_packages and would like to find a place in the 'official' repositories for it. Intention is to maintain multiple branches of Tryton in an official openSUSE repository. Other OS-ERP might be added 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 7

[Bug 824259] New: devel:languages:ruby:extensions/rubygem-passenger: Bug
by bugzilla_noreply＠novell.com 09 Dec '13

09 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=824259 https://bugzilla.novell.com/show_bug.cgi?id=824259#c0 Summary: devel:languages:ruby:extensions/rubygem-passenger: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: 3rd party software AssignedTo: mrueckert(a)suse.com ReportedBy: suse(a)ammler.ch QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- The nginx binary is missing, if you don't bring it back, we would need disable passenger for nginx, which is needed for webyast. -- 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 800365] New: systemd: rcnetwork start in YaST2-Second-Stage.service blocks
by bugzilla_noreply＠novell.com 09 Dec '13

09 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=800365 https://bugzilla.novell.com/show_bug.cgi?id=800365#c0 Summary: systemd: rcnetwork start in YaST2-Second-Stage.service blocks Classification: openSUSE Product: openSUSE Factory Version: 12.3 Beta 1 Platform: All URL: http://w3.suse.de/~mt/bnc798348/ OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: fcrozat(a)suse.com ReportedBy: mt(a)suse.com QAContact: jsrain(a)suse.com CC: locilka(a)suse.com, mfilka(a)suse.com Blocks: 798348 Found By: --- Blocker: --- This happens on factory + $OBS/home:mtomaschewski:tests/* packages also with systemd from Base:System -- most recent changelog entry: Tue Jan 22 17:02:04 UTC 2013 - fcrozat(a)suse.com - Add systemctl-options.patch: handle SYSTEMCTL_OPTIONS internaly (bnc#798620). ... The $OBS/home:mtomaschewski:tests/* are using network.service alias link instead of the NETWORKMANAGER=yes/no variable. While 2nd stage boot, YaST2-Second-Stage.service starts a script (and yast2-network which may restart it), which is trying to start the network. The service file is using "systemctl --ignore-dependencies" option for all services it starts/stops inside of the script via: [Unit] Before=[...]network.service[...] [Service] Type=oneshot Environment=SYSTEMCTL_OPTIONS=--ignore-dependencies TERM=linux [...] but the systemctl triggers a start of systemd-tty-ask-password-agent and it hangs then, see: http://w3.suse.de/~mt/bnc798348/network-start.console2.png Try to use "systemctl --ignore-dependencies --no-ask-password --no-block start network.service" does not help. The call returns and yast2 starts, but network is not started. It gets merged with the pending regular network.service start, see last boot in http://w3.suse.de/~mt/bnc798348/journal.txt: 2013-01-24T17:53:43.494104+01:00 linux rcnetwork[1734]: redirecting to "systemctl --ignore-dependencies --no-ask-password --no-block start network.service" 2013-01-24T17:53:43.496111+01:00 linux systemd[1]: Trying to enqueue job network.service/start/ignore-dependencies 2013-01-24T17:53:43.496113+01:00 linux systemd[1]: Merged into installed job network.service/start as 71 2013-01-24T17:53:43.496115+01:00 linux systemd[1]: Enqueued job network.service/start as 71 -- 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 31

[Bug 764336] New: systemctl does not deactivate start of network manager
by bugzilla_noreply＠novell.com 09 Dec '13

09 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=764336 https://bugzilla.novell.com/show_bug.cgi?id=764336#c0 Summary: systemctl does not deactivate start of network manager Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dieter.jurzitza(a)t-online.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20100101 Firefox/12.0 When configuring the network manually via yast, the network manager does not get deactivated in systemd. This causes error messages on every boot. This is not a problem but simply should not happen. Reproducible: Always Steps to Reproduce: 1. Configure network via ifup in yast 2. Restart computer 3. Error messages come up (network manager cannot be started ...) Actual Results: See above Expected Results: No errors -- 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 14

[Bug 754116] New: dbus-org.freedesktop.NetworkManager.service
by bugzilla_noreply＠novell.com 09 Dec '13

09 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=754116 https://bugzilla.novell.com/show_bug.cgi?id=754116#c0 Summary: dbus-org.freedesktop.NetworkManager.service Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bkorb(a)gnu.org QAContact: qa-bugs(a)suse.de CC: nabil83(a)snafu.de Depends on: 738596 Found By: Other Blocker: No +++ This bug was initially created as a clone of Bug #738596 +++ It is claimed that it is not a bug because it was intentional. Well, sorry, but it *IS* a bug to leave detritus like this around: Mar 26 09:42:54 beethoven dbus[1203]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.NetworkManager.service': Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.NetworkManager.service' for details. Mar 26 09:42:54 beethoven dbus-daemon[1203]: dbus[1203]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.NetworkManager.service': Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.NetworkManager.service' for details. Suppress the boot-up _error_ _messages_ and then all will be fine. -- 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 12