May 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 913996] Applying Critical Updates Causes System to no longer boot (ucode-intel / ucode-amd problem?)
by bugzilla_noreply＠novell.com 12 May '15

12 May '15

http://bugzilla.suse.com/show_bug.cgi?id=913996 Borislav Petkov <bpetkov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #100 from Borislav Petkov <bpetkov(a)suse.com> --- (In reply to Adam Liebermann from comment #97) > Well, i didn't find this workaround for a few months and therefore > thought that it's just suse not working again. And it's just that > I tried installing a few times again and again and there was no > resolution. Now I see that the problem is known and the workaround is > not distributed automatically.. Just a bit of frustration. Again, I > like the product and I value your work and that's also the reason I am > here :) Thanks, that's always nice to hear. :-) Yeah, so this is a one-time, exceptional thing as *everything* else works, see comment #68 and the ones before it. We tested it on everything we could get our hands on and it was fine. I've been running those changes for a while with the upstream kernel to make sure they're good to go before backporting them to oS. But, as it happens according to Murphy, only those boxes are funny. And I'm working on a solution, it just takes time. But I certainly understand you - a system shouldn't break from an update but it seems we've poked the beast too deep this time :-) > Yes, I think so. Didn't know it also affects other distros though. For Yeah, paint is still wet about the whole issue but once I have concrete info, I'll put it here. > I'm still working on opensuse 13.1, there were no issues. I don't > know what exactly gets updated with the microcode, but after a clean > install 13.2 worked, after the update it crashed. Installing it via > netinst it crashed immediately. Right, so early microcode update wasn't working on AMD at all. I've fixed it upstream and we pulled it into openSUSE because it is a Good Thing(tm) to have. And this issue was unexpected. > No logs, as I wouldn't know which ones you need. I can post whatever > you need if you give me the commands. No need, the other two messages you pasted are enough. It basically shows that 13.1 did late microcode update (which has always worked fine but was happening too late) and 13.2 didn't update at all. The version 0x010000af is the one which your system gets from the BIOS and 0x010000c8 is the latest one which AMD distributes. Thanks for now and stay tuned. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 922529] fails to find eMMC during initial install
by bugzilla_noreply＠novell.com 12 May '15

12 May '15

http://bugzilla.suse.com/show_bug.cgi?id=922529 Gerry Gavigan <gerrysw11(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsrain(a)suse.com Flags| |needinfo?(jsrain(a)suse.com) --- Comment #60 from Gerry Gavigan <gerrysw11(a)gmail.com> --- Just wondering if there was any news? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 918158] error 4 segfault in systemd and systemd-udev
by bugzilla_noreply＠novell.com 12 May '15

12 May '15

http://bugzilla.suse.com/show_bug.cgi?id=918158 --- Comment #47 from Dr. Werner Fink <werner(a)suse.com> --- Sorry but I'm not familiar with your hardware, maybe this is more a trail and error together with using google about driver problems -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 918158] New: error 4 segfault in systemd and systemd-udev
by bugzilla_noreply＠novell.com 12 May '15

12 May '15

http://bugzilla.opensuse.org/show_bug.cgi?id=918158 Bug ID: 918158 Summary: error 4 segfault in systemd and systemd-udev Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: ivan.topolsky(a)isb-sib.ch QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:36.0) Gecko/20100101 Firefox/36.0 Build Identifier: systemd-udevd[772]: segfault at 18 ip 00007fa5e0700a55 sp 00007fffc57d9f70 error 4 in libc-2.19.so[7fa5e0688000+19e000] followed a little bit later by: kernel:[73256.715384] systemd[1]: segfault at 7ce00000 ip 0000000000460384 sp 00007fff16f78d70 error 4 in systemd[400000+114000] broadcast on all terminals. Reproducible: Sometimes Steps to Reproduce: (0. not sure about this step: the first crash in systemd-udev might happen after resume from "Suspend-to-RAM") 1. "zypper update" 2. zypper updates a service (cups in my last occurence) 3. zypper restarts a service Actual Results: segfault broadcast on all terminal. systemd dies. systemctl is unresponsive. SysRq magic key is the only way to (more or less) cleanly restart the system Expected Results: systemd should NOT die. (Or at least, there should be a clean way to reload it) started following a recent upgrade of the system from the official opensuse update repository. might be related to glib2 problems that plague my KDE desktop. Similar to this: https://bugzilla.redhat.com/show_bug.cgi?id=1071128 https://bbs.archlinux.org/viewtopic.php?id=177801 Related to this (similar results, different component of systemd) : https://bugzilla.opensuse.org/show_bug.cgi?id=905369 -- You are receiving this mail because: You are on the CC list for the bug.

1 19

[Bug 930330] missing "xdpyinfo" in the list of dependencies (or recommends) for package "i3lock-xlock-compat"
by bugzilla_noreply＠novell.com 12 May '15

12 May '15

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

1 0

[Bug 926795] boot of opensuse installer as PV DomU, pvgrub2 binary fails to find grub configfile, missing linuxefi/initrdefi commands
by bugzilla_noreply＠novell.com 12 May '15

12 May '15

http://bugzilla.suse.com/show_bug.cgi?id=926795 --- Comment #33 from Olaf Hering <ohering(a)suse.com> --- Comment on attachment 633695 --> http://bugzilla.suse.com/attachment.cgi?id=633695 grub2-xen.cfg >set hdcfg="" >if [ -n "${hddev}" ] ; then > set default="Boot From Hard Disk" > menuentry "${hddev} Boot From Hard Disk" { > set root="${hddev}" > configfile "${hdcfg}" > } >fi This should have been if ${hdcfg} instead of if ${hddev}. Also, regarding finding config files more modules should be loaded. But I'm not sure if lvm for example is already available due to the way grub.xen is built. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 930584] New: typelib compiler writes uninitialised memory to typelib file
by bugzilla_noreply＠novell.com 12 May '15

12 May '15

http://bugzilla.suse.com/show_bug.cgi?id=930584 Bug ID: 930584 Summary: typelib compiler writes uninitialised memory to typelib file Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: ohering(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- in packman the gstreamer related packages get republished very often because there are tiny changes in the binary. /usr/lib64/girepository-1.0/GstBase-1.0.typelib differs (G-IR binary database, v4.0, 82 entries/52 local) --- /tmp/tmp.WrMdAo06Bf/tmp.wKP9itRPJc 2015-05-12 12:18:33.344211454 +0000 +++ /tmp/tmp.WrMdAo06Bf/tmp.EMX37uKiLY 2015-05-12 12:18:33.345211476 +0000 @@ -2582,7 +2582,7 @@ 0000a150 44 00 00 00 30 00 00 00 05 00 00 00 00 00 00 00 |D...0...........| 0000a160 01 00 00 00 17 00 00 00 01 00 00 00 00 00 00 00 |................| 0000a170 07 0e 00 20 09 5a 38 79 f1 59 7c 54 cd bf a1 9b |... .Z8y.Y|T....| -0000a180 17 de ff 45 2b 00 30 00 33 00 15 00 13 00 04 00 |...E+.0.3.......| +0000a180 17 de ff 00 2b 00 30 00 33 00 15 00 13 00 04 00 |....+.0.3.......| 0000a190 24 00 26 00 17 00 1e 00 1c 00 16 00 2d 00 1d 00 |$.&.........-...| 0000a1a0 03 00 10 00 32 00 0a 00 1b 00 2a 00 31 00 25 00 |....2.....*.1.%.| 0000a1b0 19 00 0d 00 2f 00 00 00 1a 00 14 00 0e 00 0c 00 |..../...........| This was fixed in gobject-introspection-1.40.0. https://bugzilla.gnome.org/show_bug.cgi?id=721177 I will submit packages for 13.1 and sles12sp1 to avoid the constant republishing in the future. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 927147] php5-fpm -p option
by bugzilla_noreply＠novell.com 12 May '15

12 May '15

http://bugzilla.novell.com/show_bug.cgi?id=927147 --- Comment #6 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-SU-2015:0855-1: An update that solves three vulnerabilities and has one errata is now available. Category: security (important) Bug References: 927147,928408,928506,928511 CVE References: CVE-2015-2783,CVE-2015-3329,CVE-2015-3330 Sources used: openSUSE 13.2 (src): php5-5.6.1-21.1 openSUSE 13.1 (src): php5-5.4.20-52.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 930564] New: mongodb should use socket under /run not /tmp
by bugzilla_noreply＠novell.com 12 May '15

12 May '15

http://bugzilla.opensuse.org/show_bug.cgi?id=930564 Bug ID: 930564 Summary: mongodb should use socket under /run not /tmp Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: tschaefer(a)t-online.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:37.0) Gecko/20100101 Firefox/37.0 Build Identifier: mongodb should use socket under /run not /tmp tested with packages from: http://download.opensuse.org/repositories/devel:/languages:/python/openSUSE… http://download.opensuse.org/repositories/server:/database/openSUSE_13.2/ omega:~ # LANG=C netstat -anp | grep mongo tcp 0 0 127.0.0.1:27017 0.0.0.0:* LISTEN 9249/mongod tcp 0 0 127.0.0.1:27017 127.0.0.1:53154 ESTABLISHED 9249/mongod tcp 0 0 127.0.0.1:27017 127.0.0.1:53156 ESTABLISHED 9249/mongod tcp 0 0 127.0.0.1:27017 127.0.0.1:53155 ESTABLISHED 9249/mongod tcp 0 0 127.0.0.1:27017 127.0.0.1:53153 ESTABLISHED 9249/mongod tcp 0 0 127.0.0.1:27017 127.0.0.1:53152 ESTABLISHED 9249/mongod tcp 0 0 ::1:27017 :::* LISTEN 9249/mongod unix 2 [ ACC ] STREAM LISTENING 28574056 9249/mongod /tmp/mongodb-27017.sock Reproducible: Always Steps to Reproduce: start mongodb with default from package and look LANG=C netstat -anp | grep mongo Actual Results: /tmp/mongodb-27017.sock Expected Results: /run/mongodb-27017.sock -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 928086] New: Intel's driver for GPU 5500 is defective
by bugzilla_noreply＠novell.com 12 May '15

12 May '15

http://bugzilla.opensuse.org/show_bug.cgi?id=928086 Bug ID: 928086 Summary: Intel's driver for GPU 5500 is defective Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: j9002j(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: Customer Blocker: No Intel's processor Core i5 5200U, and probably several others, come with GPU 5500. Intel has changed the default graphics acceleration method used in GPU's driver from UXA to SNA. But the change was not successful. Under difficult conditions (several windows open, moving windows, video coming from webcam) the graphics on monitor is distorted. Video from webcam is extremely slow, perhaps at 0.2 frames per second. Watching video from webcam can even cause a crash, perhaps related to gfx stack. The solution is found in Ubuntu forums and is to restore the old acceleration method UXA: http://ubuntuforums.org/showthread.php?t=2208072 For this, create a file called 20-intel.conf and put it in directory /etc/X11/xorg.conf.d/ The content of the file is Section "Device" Identifier "Intel Graphics" Driver "intel" Option "AccelMethod" "uxa" EndSection After rebooting, check in Xorg's log file /var/log/Xorg.0.log that the acceleration method indeed has changed to UXA; there shall be a mention about that. -- You are receiving this mail because: You are on the CC list for the bug.

1 6