February 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 965475] openSUSE:13.1:Update/systemd: Bug "Found ordering cycle on fix.service/start"
by bugzilla_noreply＠novell.com 08 Feb '16

08 Feb '16

http://bugzilla.suse.com/show_bug.cgi?id=965475 http://bugzilla.suse.com/show_bug.cgi?id=965475#c3 --- Comment #3 from Franck Bui <fbui(a)suse.com> --- (In reply to Paolo Panto from comment #2) > I've found this posts > https://bugzilla.suse.com/show_bug.cgi?id=905639#c51 > https://bugzilla.suse.com/show_bug.cgi?id=905639#c52 > > after removing "nss-lookup.target" from "After=" in > /usr/lib/systemd/system/fix.service > postfix+ntp+named start properly on boot. > > don't know if this has other impacts, but for now this works for me. fix.service seems not needed anymore. Could you try to remove it completely instead ? Try something like: rm /usr/lib/systemd/system/remote-fs.target.wants/fix.service rm /usr/lib/systemd/system/fix.service Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 962295] X server crashs when user rotate monitor 90 degrees .
by bugzilla_noreply＠novell.com 08 Feb '16

08 Feb '16

http://bugzilla.novell.com/show_bug.cgi?id=962295 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|maint:planned:update |maint:planned:update | |obs:running:4651:moderate -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 960669] udev 228: after update from 13.2/leap 42.1, the network is not enabled
by bugzilla_noreply＠novell.com 08 Feb '16

08 Feb '16

http://bugzilla.opensuse.org/show_bug.cgi?id=960669 http://bugzilla.opensuse.org/show_bug.cgi?id=960669#c61 Marcus Rückert <mrueckert(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrueckert(a)suse.com --- Comment #61 from Marcus Rückert <mrueckert(a)suse.com> --- 2016-02-03 17:01:29|install|openSUSE-release-ftp|20160130-1.2|x86_64||repo-oss|d6f806eec9879899ceffb8ad471e4429e2385186| 2016-02-06 14:18:00|install|openSUSE-release-ftp|20160205-1.1|x86_64||repo-oss|9016720b7312590e54fa8f2eeb165f125dcfaed4| on the 2nd upgrade it also renamed my virtio-net device. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 965536] After update to nvidia 352.79 black screen or crash
by bugzilla_noreply＠novell.com 08 Feb '16

08 Feb '16

http://bugzilla.suse.com/show_bug.cgi?id=965536 http://bugzilla.suse.com/show_bug.cgi?id=965536#c5 --- Comment #5 from Egbert Eich <eich(a)suse.com> --- (In reply to Dr. Werner Fink from comment #4) > (In reply to Egbert Eich from comment #3) > > Please remember I had created my 99-local.conf below /etc/X11/xorg.conf.d/ > accordingly to the documentation I've found at nvidia: > > https://a248.e.akamai.net/f/248/10/10/us.download.nvidia.com/XFree86/Linux- > x86/319.12/README/installationandconfiguration.html Ok, in chapter 32 it talks about the 'modesetting' driver. Well, this would be something for NVIDIA to answer then. > Compare with the configuration for bug #960574 ... without the modesetting > there is no composite configuration possible which results in a black screen. > > With the configuration in attachment #660731 [details] is *was* possible to > switch the virtual consoles as well as suspend or hibernate and resume the > system. > > I had also tried an empty configuration with > > Option "AllowEmptyInitialConfiguration" > > but this does not work and cause a hanging nvidia X11 driver. Also with > 352.79 I had to add the > > Option "MetaModes" "DFP-0:1920x1080+0+0" > > in Section "Device" for nvidia and Section "Screen" as otherwise the nvidia > driver shows lines like > > ... (II) NVIDIA(0): Setting mode "NULL" > > in the log. Let's wait and see if Daniel can help you here. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 965499] mkinitrd fails after using 'yast2 bootloader'
by bugzilla_noreply＠novell.com 08 Feb '16

08 Feb '16

http://bugzilla.suse.com/show_bug.cgi?id=965499 http://bugzilla.suse.com/show_bug.cgi?id=965499#c4 Steffen Winterfeldt <snwint(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(snwint(a)suse.com) | --- Comment #4 from Steffen Winterfeldt <snwint(a)suse.com> --- The above fix is ok but there's also the misleading error message seen in comment 0. https://github.com/openSUSE/perl-bootloader/pull/91 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 965475] openSUSE:13.1:Update/systemd: Bug "Found ordering cycle on fix.service/start"
by bugzilla_noreply＠novell.com 08 Feb '16

08 Feb '16

http://bugzilla.suse.com/show_bug.cgi?id=965475 Manfred Hollstein <manfred.h(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |manfred.h(a)gmx.net -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 883565] New: Race condition in systemd startup/shutdown affecting CIFS remote mounts
by bugzilla_noreply＠novell.com 08 Feb '16

08 Feb '16

https://bugzilla.novell.com/show_bug.cgi?id=883565 https://bugzilla.novell.com/show_bug.cgi?id=883565#c0 Summary: Race condition in systemd startup/shutdown affecting CIFS remote mounts Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: rodney.baker(a)iinet.net.au 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 With the default service/unit-file dependencies as shipped with openSuSE 13.1, the remote-fs service is started before if-up controlled network interfaces are available, and is shut down after the network interfaces. This results in remote mounts that should be mounted by remote-fs.service (for example, cifs mounts defined in /etc/samba/cifstab) failing to mount at startup, and if mounted manually, not being unmounted cleanly at shutdown. The shutdown process also hangs until the unmount job times out since the network has been taken down before the remote file systems are unmounted. To fix this locally, I had to add the line: Requires=network(a)eth0.service to /usr/lib/systemd/system/remote-fs.service. This ensures that remote-fs.service is not started before the network interface is up and that the network interface is not stopped until remote-fs.service has exited during shutdown. I tried using "Requires=network.service" and "Requires=network.target" - these fixed mounting at start up but did not fix the delayed shutdown. Unforunately my hack is too system specific because it requires that the correct interface name is known when remote-fs.service is created. This will not be the same on every system and, in the case of multiple network interfaces, there may be multiple dependencies. Although it works as a short-term workaround a more permanent and more generic solution is needed. Reproducible: Always Steps to Reproduce: 1. Define remote smb mounts in /etc/samba/cifstab 2. Have LAN interface controlled by if-up 3. Startup the system - remote cifs mounts will not be mounted. 4. Manually mount the cifs shares (systemctl restart remote-fs will do it). 5. Shutdown the systme - the system will hang during shutdown because the network interface is stopped before the cifs shares are unmounted. Actual Results: As described above. Expected Results: The remote-fs service should only be started after the relevant network interface(s) are started and online. The remote shares should be unmounted before the relevant network interface(s) is/are shut down. -- 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 43

[Bug 965475] openSUSE:13.1:Update/systemd: Bug "Found ordering cycle on fix.service/start"
by bugzilla_noreply＠novell.com 08 Feb '16

08 Feb '16

http://bugzilla.suse.com/show_bug.cgi?id=965475 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fbui(a)suse.com, | |meissner(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 965536] After update to nvidia 352.79 black screen or crash
by bugzilla_noreply＠novell.com 08 Feb '16

08 Feb '16

http://bugzilla.suse.com/show_bug.cgi?id=965536 http://bugzilla.suse.com/show_bug.cgi?id=965536#c4 --- Comment #4 from Dr. Werner Fink <werner(a)suse.com> --- (In reply to Egbert Eich from comment #3) Please remember I had created my 99-local.conf below /etc/X11/xorg.conf.d/ accordingly to the documentation I've found at nvidia: https://a248.e.akamai.net/f/248/10/10/us.download.nvidia.com/XFree86/Linux-… Compare with the configuration for bug #960574 ... without the modesetting there is no composite configuration possible which results in a black screen. With the configuration in attachment #660731 is *was* possible to switch the virtual consoles as well as suspend or hibernate and resume the system. I had also tried an empty configuration with Option "AllowEmptyInitialConfiguration" but this does not work and cause a hanging nvidia X11 driver. Also with 352.79 I had to add the Option "MetaModes" "DFP-0:1920x1080+0+0" in Section "Device" for nvidia and Section "Screen" as otherwise the nvidia driver shows lines like ... (II) NVIDIA(0): Setting mode "NULL" in the log. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 965573] New: VUL-0: CVE-2015-8807, CVE-2016-2228: Horde: Two cross-site scripting vulnerabilities
by bugzilla_noreply＠novell.com 08 Feb '16

08 Feb '16

http://bugzilla.suse.com/show_bug.cgi?id=965573 Bug ID: 965573 Summary: VUL-0: CVE-2015-8807, CVE-2016-2228: Horde: Two cross-site scripting vulnerabilities Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: krahmer(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: Security Response Team Blocker: --- >From OSS-sec: >Cross-site scripting in XSS in Horde_Core_VarRenderer_Html: >https://github.com/horde/horde/commit/11d74fa5a22fe626c5e5a010b703cd46a136f… >https://bugs.debian.org/813590 > >horde/framework/Core/lib/Horde/Core/Ui/VarRenderer/Html.php _renderVarInput_number Use CVE-2015-8807. >Reflected cross-site scripting >https://bugs.horde.org/ticket/14213 >https://github.com/horde/horde/commit/f03301cf6edcca57121a15e80014c4d0f29d9… >https://github.com/horde/horde/commit/ab07a1b447de34e13983b4d7ceb18b58c3a35… >https://bugs.debian.org/813573 >menu bar >horde/templates/topbar/_menubar.html.php > >searchfield=[XSS] Use CVE-2016-2228. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-2228 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-8807 http://seclists.org/oss-sec/2016/q1/292 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-8807 -- You are receiving this mail because: You are on the CC list for the bug.

1 2