May 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 930076] New: fontforge reports the wrong version
by bugzilla_noreply＠novell.com 07 May '15

07 May '15

http://bugzilla.opensuse.org/show_bug.cgi?id=930076 Bug ID: 930076 Summary: fontforge reports the wrong version Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: pgajdos(a)suse.com Reporter: davejplater(a)gmail.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com CC: coolo(a)suse.com, pgajdos(a)suse.com Found By: --- Blocker: --- One of the changes to fontforge since it's last update causes it to report the wrong version to the lilypond build. [ 379s] checking for fontforge... fontforge [ 379s] checking for fontforge... /usr/bin/fontforge [ 379s] checking /usr/bin/fontforge version... 4d46e7241d075bf87b923d18742fc706134707 [ 385s] ERROR: Please install required programs: /usr/bin/fontforge >= 20110222 (installed: 4d46e7241d075bf87b923d18742fc706134707) This problem wasn't present 18 days ago when I started trying to fix the issue that the doc build had with texi2html, April 19 so it must be due to either the bugfix for bnc#926061 or the last change in sr#304946. I can't access bnc#926061 and I can't see any changes to version reporting in sr#304946. The version number it reports looks like a git version. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 927719] Tumbleweed Snapshot blocked: no multipath support in 20150416 (likely dracut issue)
by bugzilla_noreply＠novell.com 07 May '15

07 May '15

http://bugzilla.suse.com/show_bug.cgi?id=927719 --- Comment #3 from Thomas Renninger <trenn(a)suse.com> --- *** Bug 930019 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 930019] New: multipath is broken in dracut due to missing /etc/multipath.conf file (systemd multpath.service condition)
by bugzilla_noreply＠novell.com 07 May '15

07 May '15

http://bugzilla.suse.com/show_bug.cgi?id=930019 Bug ID: 930019 Summary: multipath is broken in dracut due to missing /etc/multipath.conf file (systemd multpath.service condition) Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: hare(a)suse.com Reporter: trenn(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Title says everything. multipathd is not started and rootfs and swap are not found: systemctl status multipathd.service * multipathd.service - Device-Mapper Multipath Device Controller Loaded: loaded (/usr/lib/systemd/system/multipathd.service; disabled; vendor preset: enabled) Active: inactive (dead) Condition: start condition failed at Thu 2015-05-07 11:49:11 CEST; 7min ago ConditionPathExists=/etc/multipath.conf was not met creating /etc/multipath.conf, restarting multipath service, exiting emergency shell and the system comes up... -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[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 07 May '15

07 May '15

http://bugzilla.suse.com/show_bug.cgi?id=926795 Olaf Hering <ohering(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(ohering(a)suse.com) | --- Comment #25 from Olaf Hering <ohering(a)suse.com> --- Created attachment 633602 --> http://bugzilla.suse.com/attachment.cgi?id=633602&action=edit grub2-xen.cfg This one works better with just isos attached to the domU. It also checks for /media.1/products http://lists.opensuse.org/zypp-devel/2015-05/msg00001.html -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 928394] Headphone jack not working anymore
by bugzilla_noreply＠novell.com 07 May '15

07 May '15

http://bugzilla.novell.com/show_bug.cgi?id=928394 --- Comment #37 from Leslie Satenstein <leslie.satenstein(a)gmail.com> --- Request Is it possible to add a wrapper around this patch to respond to the following. I use the analogue interface from the motherboard. I apply the patch and set the sound on when I log in. All is fine. If by any chance I look at audio selection by looking at a second device, and upon returning to the original, The amixer settings are lost. I have therefore have to manually reset amixer. Should this comment be presented as a new bug, or should it remain as a request? By the way, amixer -c0 set Headphone unmute 100% on a line on it's own within the .profile does not always work. I made a 2 line script amixer.sh which I placed into /usr/local/bin sleep 1 amixer -c0 set Headphone unmute 100% within .profile the one liner amixer.sh & The .profile terminates before amixer settings is done and this approach has produced 100% headphone sound on reliability. Here is another note: On one of my test distributions, I discovered a new sound device. This was a pleasant surprise. Headphone. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 922235] xen guest - kernel BUG at ../arch/x86/include/mach-xen/asm/maddr.h:37!
by bugzilla_noreply＠novell.com 07 May '15

07 May '15

http://bugzilla.suse.com/show_bug.cgi?id=922235 Jan Beulich <jbeulich(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #633587|0 |1 is obsolete| | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 922235] xen guest - kernel BUG at ../arch/x86/include/mach-xen/asm/maddr.h:37!
by bugzilla_noreply＠novell.com 07 May '15

07 May '15

http://bugzilla.suse.com/show_bug.cgi?id=922235 Jan Beulich <jbeulich(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #633547|0 |1 is obsolete| | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 930048] latest krfb crashes on connect
by bugzilla_noreply＠novell.com 07 May '15

07 May '15

http://bugzilla.novell.com/show_bug.cgi?id=930048 --- Comment #1 from Bernhard Wiedemann <bwiedemann(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (930048) was mentioned in https://build.opensuse.org/request/show/305764 13.2 / LibVNCServer -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 929462] icons are broken on Bigendian
by bugzilla_noreply＠novell.com 07 May '15

07 May '15

1 0

[Bug 881506] mod_access_compat doesn't seem to work anymore
by bugzilla_noreply＠novell.com 07 May '15

07 May '15

http://bugzilla.suse.com/show_bug.cgi?id=881506 --- Comment #24 from Jan Matejek <jmatejek(a)suse.com> --- (In reply to Petr Gajdos from comment #23) > According to that you said in comment 18, it should work if access_compat is > loaded in addition to authz_core. authz_core, as the prefered one, would be > unloadable only with significant change to config. yes, this should work. what i was saying before is, if you make authz_core syntax the default, and config files contain "Require all denied" just like that, then i don't see any advantage from making mod_authz_core unloadable. Because: when you unload the module, apache will completely break because it won't be able to parse the "Require" statements. So if you want to unload it, you need to rewrite the config, and if you're rewriting the config, you can as well remove all "Require" statements and keep the module loaded. (unless there is something i'm missing, or unless we're potentially optimizing for server memory footprint, or something) Also please note that mod_authz_core is just the *core* module for the new access control method, and all mod_authz_* depend on it -- so if authz_core is unloadable, all the authz_* must be unloadable as well. > For other configuration files: > 1. new syntax would work always with our default conf, if you're talking about modules separate from the apache package, then no -- new syntax is accepted but doesn't enable access if mod_access_compat is present. Modules must check for both and use both syntax variants. > 2. old syntax should start to work after access_compat is loaded again, no -- old syntax, without new syntax, is not sufficient to enable access, if new syntax disabled it > 3. mix of new and old syntax would work as long as access_compat is loaded > and there is not contradiction (one permits and second forbids). Both types > of conditionals (comment 7, comment 18) should work. comment 7 never works, because it is if/else. (enabling access for authz_core only when access_compat is unloaded; when both are loaded, this is wrong) to reliably enable both, we need if+if comment 18 always works (it's the if+if variant) -- You are receiving this mail because: You are on the CC list for the bug.

1 0