February 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 995167] New: WiFi configuration with WPA2-PSK for a hidden network won't be accepted during installation
by bugzilla_noreply＠novell.com 12 Nov '19

12 Nov '19

http://bugzilla.opensuse.org/show_bug.cgi?id=995167 Bug ID: 995167 Summary: WiFi configuration with WPA2-PSK for a hidden network won't be accepted during installation Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: All OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: ada.lovelace(a)gmx.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:48.0) Gecko/20100101 Firefox/48.0 Build Identifier: I use a hidden network with WPA2-PSK at home. After testing the fix for bug 992516 on openSUSE Tumbleweed, the problem with the hidden network exists for a longer time. The network configuration won't be accepted or the network won't be found. It seems it needs something to choose like after the installation in the WiFi configuration for "hidden networks". workaround at the moment: Installation without adding repositories and adding the WiFi after the installation with choosing "hidden network" (verstecktes Netzwerk) The problem will be that "hidden networks" (security) won`t be supported during installations. Reproducible: Always Steps to Reproduce: 1. configure your WiFi with WPA2-PSK and as a hidden network (not public to find) 2. configure the wlan interface for WPA2-PSK with a password during the installation 3. The WiFi can't be found. (no error message) 4. Online repositories can't be used. 5. Looking after the network configuration again (it is configured). 6. installation without repositories 7. configuration of the network interface after the openSUSE installation successfully (openSUSE Tumbleweed was used: reason bug 992516) Actual Results: The WiFi configuration with WPA2-PSK with a hidden network (verstecktes Netzwerk) won't be accepted during the installation of openSUSE Leap/ Tumbleweed. The WiFi works after a configuration after the installation. Expected Results: You can choose every WiFi (unimportant whether public or hidden network) during the installation. You can't reproduce it on Leap at the moment, because another (fixed) network configuration bug exists there at the moment. Use Tumbleweed for that! -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 935864] New: zlib: package minizip?
by bugzilla_noreply＠novell.com 12 Nov '19

12 Nov '19

http://bugzilla.suse.com/show_bug.cgi?id=935864 Bug ID: 935864 Summary: zlib: package minizip? Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: tchvatal(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de CC: security-team(a)suse.de Found By: --- Blocker: --- zlib contains contrib/minizip which at least by judging from the use of unzip.h is contained as copy in 30 other packages. What about building minizip as separate sub package? -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 911355] New: Job for spamd.service failed
by bugzilla_noreply＠novell.com 11 Nov '19

11 Nov '19

http://bugzilla.suse.com/show_bug.cgi?id=911355 Bug ID: 911355 Summary: Job for spamd.service failed Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: stephan.barth(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After the upgrade from 12.3 I found out that spmad was not running anymore. When trying to start it manually I get: # /etc/init.d/spamd restart redirecting to systemctl restart spamd.service Job for spamd.service failed. See "systemctl status spamd.service" and "journalctl -xn" for details. Running the latter command yields: Dec 29 16:40:11 linux-wulv echo[6901]: Starting spamd: Dec 29 16:40:11 linux-wulv spamd[6903]: logger: removing stderr method Dec 29 16:40:11 linux-wulv spamd[6905]: config: no rules were found! Do you need to run 'sa-update'? Dec 29 16:40:12 linux-wulv spamd[6903]: child process [6905] exited or timed out without signaling production of a PID file: exit 255 at /us Dec 29 16:40:12 linux-wulv spamd[6903]: child process [6905] exited or timed out without signaling production of a PID file: exit 255 at /us Dec 29 16:40:12 linux-wulv systemd[1]: Failed to start Daemonized version of spamassassin. -- Subject: Unit spamd.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit spamd.service has failed. -- -- The result is failed. # rpm -q perl-Mail-SpamAssassin perl-Mail-SpamAssassin-3.4.0-44.1.3.x86_64 # rpm -q spamassassin spamassassin-3.4.0-44.1.3.x86_64 Solution: Running sa-update manually makes spamd start with '/etc/init.d/spamd restart'. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1025419] New: Tomcat throws exceptions on specific addresses
by bugzilla_noreply＠novell.com 04 Nov '19

04 Nov '19

http://bugzilla.suse.com/show_bug.cgi?id=1025419 Bug ID: 1025419 Summary: Tomcat throws exceptions on specific addresses Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: SLES 12 Status: NEW Severity: Major Priority: P5 - None Component: Java Assignee: bnc-team-java(a)forge.provo.novell.com Reporter: jweberhofer(a)weberhofer.at QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- A application which works without any issues on several tomcat versions (8.0.x and 8.5.x) fails on the package provided by SLES 12 and openSUSE 42.2: Feb 14 14:10:03 SPRZVW02 tomcat.service[902]: java.io.IOException: Server returned HTTP response code: 400 for URL: http://localhost:8080/eusoda/eusodaweb/services?{"institution":{"type":"content","absurls":"true",""}} This URL is mapped using a spring service. Software version: Repository : SLES12-SP2-Updates for x86_64 (Testing) Name : tomcat Version : 8.0.36-17.1 Name : java-1_8_0-openjdk Version : 1.8.0.121-20.1 WE have also tried to use older versions of java and tomcat (8.0.32) but this always resulted in the same issue; the server worked with an older version of tomcat (prior to 8.0.32, I don't have an exact version number). Here is the complete stack-trace: Feb 14 14:10:03 SPRZVW02 tomcat.service[902]: java.io.IOException: Server returned HTTP response code: 400 for URL: http://localhost:8080/eusoda/eusodaweb/services?{"institution":{"type":"content","absurls":"true","true",""}} Feb 14 14:10:03 SPRZVW02 tomcat.service[902]: at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1876) Feb 14 14:10:03 SPRZVW02 tomcat.service[902]: at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474) Feb 14 14:10:03 SPRZVW02 tomcat.service[902]: at at.weberhofer.eusoda.server.admin.pages.InstitutionEdit.getPrivateView(InstitutionEdit.java:1258) Feb 14 14:10:03 SPRZVW02 tomcat.service[902]: at sun.reflect.GeneratedMethodAccessor1360.invoke(Unknown Source) Feb 14 14:10:03 SPRZVW02 tomcat.service[902]: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) Feb 14 14:10:03 SPRZVW02 tomcat.service[902]: at java.lang.reflect.Method.invoke(Method.java:498) Feb 14 14:10:03 SPRZVW02 tomcat.service[902]: at ognl.OgnlRuntime.invokeMethod(OgnlRuntime.java:851) Feb 14 14:10:03 SPRZVW02 tomcat.service[902]: at ognl.OgnlRuntime.getMethodValue(OgnlRuntime.java:1414) Feb 14 14:10:03 SPRZVW02 tomcat.service[902]: at ognl.ObjectPropertyAccessor.getPossibleProperty(ObjectPropertyAccessor.java:60) Feb 14 14:10:03 SPRZVW02 tomcat.service[902]: at ognl.ObjectPropertyAccessor.getProperty(ObjectPropertyAccessor.java:147) Feb 14 14:10:03 SPRZVW02 tomcat.service[902]: at ognl.OgnlRuntime.getProperty(OgnlRuntime.java:2210) Feb 14 14:10:03 SPRZVW02 tomcat.service[902]: at ognl.ASTProperty.getValueBody(ASTProperty.java:114) Feb 14 14:10:03 SPRZVW02 tomcat.service[902]: at ognl.SimpleNode.evaluateGetValueBody(SimpleNode.java:212) Feb 14 14:10:03 SPRZVW02 tomcat.service[902]: at ognl.SimpleNode.getValue(SimpleNode.java:258) Feb 14 14:10:03 SPRZVW02 tomcat.service[902]: at ognl.Ognl.getValue(Ognl.java:494) Feb 14 14:10:03 SPRZVW02 tomcat.service[902]: at ognl.Ognl.getValue(Ognl.java:458) Feb 14 14:10:03 SPRZVW02 tomcat.service[902]: at org.apache.tapestry.binding.ExpressionBinding.resolveProperty(ExpressionBinding.java:201) Feb 14 14:10:03 SPRZVW02 tomcat.service[902]: at org.apache.tapestry.binding.ExpressionBinding.getObject(ExpressionBinding.java:194) Feb 14 14:10:03 SPRZVW02 tomcat.service[902]: at org.apache.tapestry.binding.AbstractBinding.getObject(AbstractBinding.java:208) Feb 14 14:10:03 SPRZVW02 tomcat.service[902]: at org.apache.tapestry.param.AbstractParameterConnector.getBindingValue(AbstractParameterConnector.java:105) Feb 14 14:10:03 SPRZVW02 tomcat.service[902]: at org.apache.tapestry.param.ObjectParameterConnector.setParameter(ObjectParameterConnector.java:53) Feb 14 14:10:03 SPRZVW02 tomcat.service[902]: at org.apache.tapestry.param.ParameterManager.setParameters(ParameterManager.java:105) Feb 14 14:10:03 SPRZVW02 tomcat.service[902]: at org.apache.tapestry.AbstractComponent.prepareForRender(AbstractComponent.java:898) Feb 14 14:10:03 SPRZVW02 tomcat.service[902]: at org.apache.tapestry.AbstractComponent.render(AbstractComponent.java:853) Feb 14 14:10:03 SPRZVW02 tomcat.service[902]: at org.apache.tapestry.AbstractComponent.renderBody(AbstractComponent.java:624) Feb 14 14:10:03 SPRZVW02 tomcat.service[902]: at org.apache.tapestry.form.Form.renderComponent(Form.java:362) Feb 14 14:10:03 SPRZVW02 tomcat.service[902]: at org.apache.tapestry.AbstractComponent.render(AbstractComponent.java:857) Feb 14 14:10:04 SPRZVW02 systemd-journal[489]: Forwarding to syslog missed 4 messages. Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.tapestry.AbstractComponent.renderBody(AbstractComponent.java:624) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.tapestry.components.RenderBody.renderComponent(RenderBody.java:45) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.tapestry.AbstractComponent.render(AbstractComponent.java:857) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.tapestry.AbstractComponent.renderBody(AbstractComponent.java:624) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.tapestry.html.Body.renderComponent(Body.java:269) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.tapestry.AbstractComponent.render(AbstractComponent.java:857) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.tapestry.AbstractComponent.renderBody(AbstractComponent.java:624) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.tapestry.html.Shell.renderComponent(Shell.java:124) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.tapestry.AbstractComponent.render(AbstractComponent.java:857) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.tapestry.BaseComponent.renderComponent(BaseComponent.java:118) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.tapestry.AbstractComponent.render(AbstractComponent.java:857) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.tapestry.BaseComponent.renderComponent(BaseComponent.java:118) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.tapestry.AbstractComponent.render(AbstractComponent.java:857) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.tapestry.AbstractPage.renderPage(AbstractPage.java:300) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.tapestry.engine.RequestCycle.renderPage(RequestCycle.java:368) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.tapestry.engine.AbstractEngine.renderResponse(AbstractEngine.java:749) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.tapestry.engine.DirectService.service(DirectService.java:174) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.tapestry.engine.AbstractEngine.service(AbstractEngine.java:889) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.tapestry.ApplicationServlet.doService(ApplicationServlet.java:198) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at javax.servlet.http.HttpServlet.service(HttpServlet.java:648) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:292) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.catalina.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:108) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.tapestry5.TapestryFilter.doFilter(TapestryFilter.java:175) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.tapestry.RedirectFilter.doFilter(RedirectFilter.java:106) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:212) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:141) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:616) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:522) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1095) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:672) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.doRun(AprEndpoint.java:2500) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.run(AprEndpoint.java:2489) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at java.lang.Thread.run(Thread.java:745) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at org.apache.tapestry.ApplicationServlet.doPost(ApplicationServlet.java:327) Feb 14 14:10:04 SPRZVW02 tomcat.service[902]: at javax.servlet.http.HttpServlet.service(HttpServlet.java:648) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 950955] New: Error Messages from rtkit-daemon caused by CONFIG_RT_GROUP_SCHED
by bugzilla_noreply＠novell.com 04 Nov '19

04 Nov '19

http://bugzilla.opensuse.org/show_bug.cgi?id=950955 Bug ID: 950955 Summary: Error Messages from rtkit-daemon caused by CONFIG_RT_GROUP_SCHED Classification: openSUSE Product: openSUSE Factory Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: Jan.Hebler(a)Kabeldeutschland.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- rtkit-daemon produces the following Error-Messages: ... Okt 19 07:06:19 tablette rtkit-daemon[3051]: Failed to make ourselves RT: Operation not permitted ... If i understand Lennart Poettering here https://bugzilla.redhat.com/show_bug.cgi?id=1229700 correct, the Kernel-Option CONFIG_RT_GROUP_SCHED should turned off. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1008898] New: KIWI can't unmount sysfs (is in use by systemd-logind)
by bugzilla_noreply＠novell.com 30 Oct '19

30 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=1008898 Bug ID: 1008898 Summary: KIWI can't unmount sysfs (is in use by systemd-logind) Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: ms(a)suse.com Reporter: svollath(a)suse.com QA Contact: qa-bugs(a)suse.de CC: thardeck(a)suse.com Found By: --- Blocker: --- Created attachment 700932 --> http://bugzilla.suse.com/attachment.cgi?id=700932&action=edit KIWI logs + config When building an appliance with kiwi (in this case using "machinery build"), kiwi finishes SUCCESSFUL, but machinery can't cleanup its temporary files. This is because kiwi leaves a sysfs mount open which requires a reboot to get rid of. ((Reproduced with Leap 42.1, 42.2, kiwi-7.03.97, kiwi-7.04.8, kiwi-7.04.13)) Buildlog snippets: ... Nov-07 14:52:18 <1> : EXEC [mount -n -t sysfs sysfs /tmp/machinery-image20161107-10165-1js1i2p/build/image-root/sys] ... Nov-07 14:56:36 <1> : EXEC [umount "/tmp/machinery-image20161107-10165-1js1i2p/build/image-root/sys" 2>&1] Nov-07 14:56:36 <2> : Umount of /tmp/machinery-image20161107-10165-1js1i2p/build/image-root/sys failed: umount: /tmp/machinery-image20161107-10165-1js1i2p/build/image-root/sys: target is busy (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1).) ... Nov-07 15:02:05 <1> : Closing session with ecode: 0 Nov-07 15:02:06 <1> : KIWI exited successfully ... see full log and config attached. # mount | grep sysfs sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) sysfs on /tmp/machinery-image20161107-10165-1js1i2p/build/image-root/sys type sysfs (rw,relatime) # lsof /tmp/machinery-image20161107-10165-1js1i2p/build/image-root/sys lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/10570/gvfs Output information may be incomplete. COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME systemd-l 2046 root 6r REG 0,17 4096 18025 /sys/devices/virtual/tty/tty0/active ((root 2046 0.0 0.0 20108 2608 ? Ss Nov04 0:01 /usr/lib/systemd/systemd-logind)) -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 941758] New: grub-once isn't called at hibernate
by bugzilla_noreply＠novell.com 22 Oct '19

22 Oct '19

http://bugzilla.opensuse.org/show_bug.cgi?id=941758 Bug ID: 941758 Summary: grub-once isn't called at hibernate Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: tiwai(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since the recent change of systemd, grub-once isn't called any longer, thus at thawing, the normal GRUB menu is shown instead of the direct boot to the target kernel. The regression was introduced in openSUSE:Factory/systemd changeset 215: Wed Feb 18 05:01:38 UTC 2015 - crrodriguez(a)opensuse.org .... - systemd-sleep-grub: moved to the grub2 package where it belongs as a suspend/resume hook (SR#286533) (drops prepare-suspend-to-disk.patch) However, SR#286533 was declined and it's lost since then. The fix would be either revert the change in systemd or put the hook properly into grub2 package. The latter method has a potential bug, however. systemd-sleep doesn't call hooks to restore when writing to /sys/power/state fails. That is, if we have a hook to set up grubenv, it'll left when the hibernation fails, and the next boot would go wrong. This didn't happen in the past because it invoked the grubenv setup in a different manner. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 969165] New: parted creates wrong protective mbr
by bugzilla_noreply＠novell.com 22 Oct '19

22 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=969165 Bug ID: 969165 Summary: parted creates wrong protective mbr Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: puzel(a)suse.com Reporter: snwint(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: Development Blocker: --- The protective mbr parted creates has inconsistent data. The CHS value for the partition start is 0/0/1 (pointing to the MBR itself) but should be 0/0/2 (pointing to the partition). The LBA starting value of 1 is correct, however. (CHS values are 1-based.) UEFI spec also explicitly mentions the correct value 0/0/2. gptfdisk works correctly, btw. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1013981] New: Errors from /usr/lib/obs/service/source_validators/20-files-present-and-referenced
by bugzilla_noreply＠novell.com 22 Oct '19

22 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=1013981 Bug ID: 1013981 Summary: Errors from /usr/lib/obs/service/source_validators/20-files-presen t-and-referenced Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: ro(a)suse.de Reporter: lpechacek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- While submitting an update for sle-module-toolchain-release package, errors were detected by the maintenance checker script. It turned out to be a result of /usr/lib/obs/service/source_validators/20-files-present-and-referenced failing to process the special .spec file. How to reproduce: # osc -A https://api.suse.de/ co Devel:Toolchain:SLE12 _product:sle-module-toolchain-release # cd Devel\:Toolchain\:SLE12/_product\:sle-module-toolchain-release/ # /usr/lib/obs/service/source_validators/20-files-present-and-referenced Actual output: # /usr/lib/obs/service/source_validators/20-files-present-and-referenced (E) warning: mentioned in spec file does not exist. (E) line mentioned in spec file does not exist. (E) 20: mentioned in spec file does not exist. (E) Invalid mentioned in spec file does not exist. (E) version mentioned in spec file does not exist. (E) (double mentioned in spec file does not exist. (E) separator mentioned in spec file does not exist. (E) '-'): mentioned in spec file does not exist. (E) sle-module-toolchain: mentioned in spec file does not exist. (E) Provides: mentioned in spec file does not exist. (E) product() mentioned in spec file does not exist. (E) = mentioned in spec file does not exist. (E) sle-module-toolchain mentioned in spec file does not exist. Expected output: Exit status 0, nothing reported. Interestingly enough, the script works fine on SLE 11 SP4, which has bash 3.2.57. It is failing on distros with bash 4.3.x and higher (SLE 12, Leap 42, Tumbleweed). -- You are receiving this mail because: You are on the CC list for the bug.

1 17

[Bug 939248] New: gnome-shell not having correct SSH_AUTH_SOCK variable
by bugzilla_noreply＠novell.com 20 Oct '19

20 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=939248 Bug ID: 939248 Summary: gnome-shell not having correct SSH_AUTH_SOCK variable Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: vuntz(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Any process that I start through gnome-shell seems to have a SSH_AUTH_SOCK matching a ssh-agent process (probably started through the X11 session scripts). However, if I start a process through gnome-settings-daemon (like a terminal, through the shortcurt for that), it has SSH_AUTH_SOCK set to the path for gnome-keyring. The result is that any app I start through gnome-shell actually has, by default, not access to my ssh keys :/ (also, I thought I had fixed a long time ago the bit starting ssh-agent on gnome sessions -- this shouldn't happen because of the keyring) -- You are receiving this mail because: You are on the CC list for the bug.

1 1