September 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 893741] New: Typing the command "systemctl restart postf" and pressing tab to autocomplete shows a list of errors
by bugzilla_noreply＠novell.com 01 Sep '14

01 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=893741 https://bugzilla.novell.com/show_bug.cgi?id=893741#c0 Summary: Typing the command "systemctl restart postf" and pressing tab to autocomplete shows a list of errors Classification: openSUSE Product: openSUSE Factory Version: 201408* Platform: x86-64 OS/Version: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: freek(a)opensuse.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 Typing the command "systemctl restart postf" and pressing tab shows the following: # systemctl restart postfFailed to get properties: Unit name autovt@.service is not valid. Failed to get properties: Unit name configure-printer@.service is not valid. Failed to get properties: Unit name container-getty@.service is not valid. Failed to get properties: Unit name getty@.service is not valid. Failed to get properties: Unit name mdadm-grow-continue@.service is not valid. Failed to get properties: Unit name mdadm-last-resort@.service is not valid. Failed to get properties: Unit name mdmon@.service is not valid. Failed to get properties: Unit name openvpn@.service is not valid. Failed to get properties: Unit name serial-getty@.service is not valid. Failed to get properties: Unit name systemd-backlight@.service is not valid. Failed to get properties: Unit name systemd-fsck@.service is not valid. Failed to get properties: Unit name systemd-nspawn@.service is not valid. Failed to get properties: Unit name systemd-rfkill@.service is not valid. Failed to get properties: Unit name user@.service is not valid. Failed to get properties: Unit name wacom-inputattach@.service is not valid. ix.service Pressing Enter performs the requested action. This is a system which has been updated up to the latest repository 20140820. At the same time the file /var/log/messages shows: 2014-08-27T11:06:12.898465+02:00 eik132 systemd[1]: Configuration file /usr/lib/systemd/system/ipmiseld.service is marked executable. Please remove executable permission bits. Proceeding anyway. 2014-08-27T11:06:13.122251+02:00 eik132 systemd[1]: message repeated 2 times: [ Configuration file /usr/lib/systemd/system/ipmiseld.service is marked executable. Please remove executable permission bits. Proceeding anyway.] 2014-08-27T11:06:13.126394+02:00 eik132 systemd[1]: [/usr/lib/systemd/system/klog.service:26] Unknown lvalue 'Alias' in section 'Unit' 2014-08-27T11:06:13.572908+02:00 eik132 systemd[1]: Configuration file /usr/lib/systemd/system/ipmiseld.service is marked executable. Please remove executable permission bits. Proceeding anyway. 2014-08-27T11:06:13.813405+02:00 eik132 systemd[1]: message repeated 2 times: [ Configuration file /usr/lib/systemd/system/ipmiseld.service is marked executable. Please remove executable permission bits. Proceeding anyway.] 2014-08-27T11:06:13.822436+02:00 eik132 systemd[1]: [/usr/lib/systemd/system/klog.service:26] Unknown lvalue 'Alias' in section 'Unit' 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 4

[Bug 890511] VUL-0: CVE-2014-3522: subversion: Apache Subversion incorrectly handles wildcards in certificates
by bugzilla_noreply＠novell.com 01 Sep '14

01 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=890511 https://bugzilla.novell.com/show_bug.cgi?id=890511#c11 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #11 from Marcus Meissner <meissner(a)suse.com> 2014-09-01 09:55:57 UTC --- released -- 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 0

[Bug 809441] New: Boot-up to graphical environment fails when boot splash is enabled
by bugzilla_noreply＠novell.com 01 Sep '14

01 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=809441 https://bugzilla.novell.com/show_bug.cgi?id=809441#c0 Summary: Boot-up to graphical environment fails when boot splash is enabled Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: lassi.vaatamoinen(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=529757) --> (http://bugzilla.novell.com/attachment.cgi?id=529757) Nouveau lines from dmesg when error occurs (splash enabled) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 The system does not boot up to graphical environment when bootsplash is enabled. Boot is successful after disabling splash: /etc/default/grub: #GRUB_CMDLINE_LINUX_DEFAULT="quiet splash=silent" GRUB_CMDLINE_LINUX_DEFAULT="" The problem seems to be related to splash/plymouth/nouveau/kernel version. Reproducible: Always Steps to Reproduce: 1. Enable splash in grub settings 2. 'grub2-mkconfig -o /boot/grub2/grub.cfg' 3. reboot Actual Results: Boot-up fails, TTY8 is frozen. On most cases text console still works. Dmesg shows nouveau errors Expected Results: Boot-up successful with graphical splash enabled. -- 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 16

[Bug 892518] New: Feature Request: YaST2 - Factory Reset Button
by bugzilla_noreply＠novell.com 01 Sep '14

01 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=892518 https://bugzilla.novell.com/show_bug.cgi?id=892518#c0 Summary: Feature Request: YaST2 - Factory Reset Button Classification: openSUSE Product: openSUSE Factory Version: 201407* Platform: x86-64 OS/Version: openSUSE 13.2 Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers(a)suse.de ReportedBy: Antoine.Saroufim(a)gmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 YaST2 should have a "Factory Reset" button in case the user messes up the configs and ends with a broken system. Currently, the user can create backups to recover from in case of a system failure. However, a state 0 backup should be automatically created after the system first boots. This will save the user time in case of driver failures or configuration errors. The user will no longer have to reinstall the system if he/she cannot troubleshoot the problem. Instead, he/she can reset openSUSE to its initial state. On Factory, we can take it a step further. The reset button could automatically take the user back to the the state of the latest milestone. 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 3