May 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1029972] New: procps has binaries in /bin
by bugzilla_noreply＠novell.com 01 Mar '21

01 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1029972 Bug ID: 1029972 Summary: procps has binaries in /bin Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: daniel.molkentin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- procps is one of the remaining packages in Tumbleweed to install binaries to /bin. Please make sure all binaries previously in /usr go to %_bindir (aka /usr/bin), and /bin contains a symlink to those. See https://bugzilla.opensuse.org/show_bug.cgi?id=1029961 for an overview. If you need assistance, don't hesitate to ask. General discussions should happen in the meta bug (see previous link). -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1110512] New: Bump appimaged to latest, it is now provided by separate git repo
by bugzilla_noreply＠novell.com 28 Feb '21

28 Feb '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1110512 Bug ID: 1110512 Summary: Bump appimaged to latest, it is now provided by separate git repo Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Enhancement Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: brentonhorne77(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 784935 --> http://bugzilla.opensuse.org/attachment.cgi?id=784935&action=edit Log from my OBS openSUSE Tumbleweed x86-64 build (rev 2) It is admirable that this fine distro is one of very few that has AppImage packages in its official repositories, unfortunately appimaged has become outdated. appimaged is now provided by a separate git repo: https://github.com/AppImages/appimaged. I've tried packaging it myself but as it tries to download several external dependencies during the build it is proving to be quite a pain to package with the Open Build Service. Here's my OBS project where I've been attempting to build appimaged: https://build.opensuse.org/package/show/home:fusion809/appimaged (at the time of writing it is at revision 2, https://build.opensuse.org/package/show/home:fusion809/appimaged?rev=2) The build error log for openSUSE Tumbleweed x86-64 (which was originally at https://build.opensuse.org/package/live_build_log/home:fusion809/appimaged/…) I'm looking at, at the time of writing is attached as _log. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1116277] New: klogconsole: split out of util-linux or upstream
by bugzilla_noreply＠novell.com 26 Feb '21

26 Feb '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1116277 Bug ID: 1116277 Summary: klogconsole: split out of util-linux or upstream Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: sbrabec(a)suse.com Reporter: sbrabec(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- util-linux is intended to package the upstream util-linux project. Over the time, our downstream package integrated several special specific utilities. klogconsole is one of them. It seems that klogconsole has no upstream nowadays. But there is a similar utility setlogcons in the kbd package. Maybe it makes sense to drop klogconsole in favor of setlogcons. If klogconsole still makes sense over setlogcons, then it makes sense to separate the project out ot util-linux, or integrate to the upstream util-linux (less probable, as conunterpart exists). -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1048942] New: qla2xxx: endless rport login loop after update to kernel version 4.11.8-1-default (32bit)
by bugzilla_noreply＠novell.com 23 Feb '21

23 Feb '21

http://bugzilla.suse.com/show_bug.cgi?id=1048942 Bug ID: 1048942 Summary: qla2xxx: endless rport login loop after update to kernel version 4.11.8-1-default (32bit) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: thomas.blume(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After updating my old 32bit server from kernel version 4.10.13-1 to 4.11.8-1 the system boot hangs during load of the qla2xxx driver. Log messages shown are: --> Jul 17 13:17:15 c92 kernel: qla2xxx [0000:00:00.0]-0005: : QLogic Fibre Channel HBA Driver: 9.00.00.00-k. Jul 17 13:17:15 c92 kernel: qla2xxx [0000:06:02.0]-001d: : Found an ISP2312 irq 21 iobase 0xf823d000. Jul 17 13:17:15 c92 kernel: scsi host4: qla2xxx Jul 17 13:17:15 c92 kernel: qla2xxx [0000:06:02.0]-4800:4: DPC handler sleeping. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-580e:4: Asynchronous P2P MODE received. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-500a:4: LOOP UP detected (2 Gbps). Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-5812:4: Port database changed ffff 0006 0000. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-107ff:4: Mark all dev lost Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-5811:4: Asynchronous PORT UPDATE ignored 0000/0006/0000. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-5811:4: Asynchronous PORT UPDATE ignored 0001/0006/0000. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-5810:4: Port logout 0000 0007 0000. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-5810:4: Port logout 0001 0007 0000. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-5811:4: Asynchronous PORT UPDATE ignored 0000/0006/0000. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-5811:4: Asynchronous PORT UPDATE ignored 0001/0006/0000. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-5810:4: Port logout 0000 0007 0000. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-5810:4: Port logout 0001 0007 0000. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-480b:4: Reset marker scheduled. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-480c:4: Reset marker end. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-480f:4: Loop resync scheduled. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-8837:4: F/W Ready - OK. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-883a:4: fw_state=3 (ffff, ffff, ffff, ffff ffff) curr time=9ada0. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-280e:4: HBA in F P2P topology. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-2814:4: Configure loop -- dpc flags = 0x112e0. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-287d:4: NodeName = 200000e08b0807cd. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-28a5:4: Manufacturer = QLogic Corporation. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-28a6:4: Serial no. = F76775. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-28a7:4: Model Name = QLA2340. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-28a8:4: Model Desc = 133MHz PCI-X to 2Gb FC, Single Channel. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-28a9:4: Hardware ver = HW:. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-28aa:4: Driver ver = 9.00.00.00-k. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-28ab:4: Optrom version = 46.49. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-28ac:4: Firmware vers = 3.03.28 IPX. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-28ae:4: OS Name and Version = Linux 4.11.8-1-default #1 SMP Thu Jun 29 14:37:33 UTC 2017 (42bd7a0). Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-28af:4: CT Payload Length = 0x80000. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-28b0:4: Symbolic Name = QLA2340 FW:v3.03.28 DVR:v9.00.00.00-k. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-28b1:4: Vendor Id = 77100000. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-28b2:4: Port Num = 1000000. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-28b3:4: Fabric Name = 0220de0000fbd13b. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-28b4:4: BIOS Name = BIOS 1.45 Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-28b1:4: Vendor Identifier = QLGC. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-28b5:4: RHBA identifier = 210000e08b0807cd. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-2816:4: RHBA FDMI v2 failed, CT Reason code: 0x9, CT Explanation 0x0 Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-2825:4: NodeName = 200000e08b0807cd. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-2826:4: Manufacturer = QLogic Corporation. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-2827:4: Serial no. = F76775. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-2828:4: Model Name = QLA2340. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-2829:4: Model Desc = 133MHz PCI-X to 2Gb FC, Single Channel. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-282a:4: Hardware ver = HW:. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-282b:4: Driver ver = 9.00.00.00-k. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-282c:4: Optrom vers = 1.45. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-282d:4: Firmware vers = 3.03.28 IPX. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-282e:4: RHBA identifier = 210000e08b0807cd size=184. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-2835:4: RHBA exiting normally. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-2839:4: FC4_TYPES=01 00. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-283a:4: Supported_Speed=3000000. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-283b:4: Current_Speed=2000000. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-283c:4: Max_Frame_Size=80000. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-284b:4: OS_Device_Name=qla2xxx:host4. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-283d:4: HostName=c92. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-283e:4: RPA portname 210000e08b0807cd, size = 100. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-2841:4: RPA exiting normally. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-2844:4: RFT_ID exiting normally. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-2848:4: RFF_ID exiting normally. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-284e:4: RNN_ID exiting normally. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-2852:4: RSNN_NN exiting normally. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-2858:4: GID_PT entry - nn 200400a0981116c6 pn 200000a0981116c6 portid=770403. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-2858:4: GID_PT entry - nn 200400a0981116c6 pn 200200a0981116c6 portid=770505. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-2858:4: GID_PT entry - nn 200000e08b0807cd pn 210000e08b0807cd portid=7c0700. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-2858:4: GID_PT entry - nn 50060b0000275a0f pn 50060b0000275a0e portid=7c0800. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-2863:4: GA_NXT entry - nn 200400a0981116c6 pn 200000a0981116c6 port_id=770403. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-2863:4: GA_NXT entry - nn 200400a0981116c6 pn 200200a0981116c6 port_id=770505. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-2863:4: GA_NXT entry - nn 200000e08b0807cd pn 210000e08b0807cd port_id=7c0700. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-2863:4: GA_NXT entry - nn 50060b0000275a0f pn 50060b0000275a0e port_id=7c0800. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-2863:4: GA_NXT entry - nn 200400a0981116c6 pn 200000a0981116c6 port_id=770403. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-2865:4: Device wrap (770403). Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-107ff:4: qla24xx_fcport_handle_login 20:00:00:a0:98:11:16:c6 DS 0 LS 7 P 0 fl 3 confl (null) rscn 0|0 login 0|0 retry 5 lid 4096 Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-107ff:4: qla24xx_fcport_handle_login 859 20:00:00:a0:98:11:16:c6 post gnl Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-107ff:4: Async-gnlist WWPN 20:00:00:a0:98:11:16:c6 Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-107ff:4: Async-gnlist - OUT WWPN 20:00:00:a0:98:11:16:c6 hndl 2 Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-107ff:4: qla24xx_fcport_handle_login 20:02:00:a0:98:11:16:c6 DS 0 LS 7 P 0 fl 3 confl (null) rscn 0|0 login 0|0 retry 5 lid 4096 Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-107ff:4: qla24xx_fcport_handle_login 859 20:02:00:a0:98:11:16:c6 post gnl Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-107ff:4: Async-gnlist WWPN 20:02:00:a0:98:11:16:c6 Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-107ff:4: qla24xx_fcport_handle_login 50:06:0b:00:00:27:5a:0e DS 0 LS 7 P 0 fl 3 confl (null) rscn 0|0 login 0|0 retry 5 lid 4096 Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-107ff:4: qla24xx_fcport_handle_login 859 50:06:0b:00:00:27:5a:0e post gnl Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-5046:4: Async-gnlist failed - hdl=2 portid=770403 status=30 mb0=4006 mb1=4000 mb2=0 mb6=0 mb7=0. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-107ff:4: Async done-gnlist res 0 mb[1]=4005 mb[2]=0 Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-107ff:4: qla24xx_handle_gnl_done_event 363 20:00:00:a0:98:11:16:c6 n 409 770403 lid 4096 Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-2886:4: Assigning new loopid=81, portid=770403. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-107ff:4: qla24xx_fcport_handle_login 20:00:00:a0:98:11:16:c6 DS 2 LS 7 P 0 fl 3 confl (null) rscn 0|0 login 0|0 retry 4 lid 129 Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-107ff:4: qla24xx_fcport_handle_login 890 20:00:00:a0:98:11:16:c6 post login Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-107ff:4: qla24xx_handle_gnl_done_event 363 20:02:00:a0:98:11:16:c6 n 409 770505 lid 4096 Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-2886:4: Assigning new loopid=82, portid=770505. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-107ff:4: qla24xx_fcport_handle_login 20:02:00:a0:98:11:16:c6 DS 2 LS 7 P 0 fl 3 confl (null) rscn 0|0 login 0|0 retry 4 lid 130 Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-107ff:4: qla24xx_fcport_handle_login 890 20:02:00:a0:98:11:16:c6 post login Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-107ff:4: Async-gnlist WWPN 50:06:0b:00:00:27:5a:0e Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-107ff:4: Async-gnlist - OUT WWPN 50:06:0b:00:00:27:5a:0e hndl 3 Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-2869:4: LOOP READY. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-286b:4: qla2x00_configure_loop: exiting normally. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-4810:4: Loop resync end. Jul 17 13:17:16 c92 kernel: qla2xxx [0000:06:02.0]-5046:4: Async-gnlist failed - hdl=3 portid=7c0800 status=30 mb0=4006 mb1=4000 mb2=0 mb6=0 mb7=0. --< Reverting to kernel version 4.10.13-1 make the rport login work and the system booting up correctly. -- You are receiving this mail because: You are on the CC list for the bug.

2 56

[Bug 1121920] New: PCP regression: monitoring agent binaries dropped from package
by bugzilla_noreply＠novell.com 23 Feb '21

23 Feb '21

http://bugzilla.suse.com/show_bug.cgi?id=1121920 Bug ID: 1121920 Summary: PCP regression: monitoring agent binaries dropped from package Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: ddiss(a)suse.com Reporter: ddiss(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kkaempf(a)suse.com Found By: --- Blocker: --- The [open]SUSE PCP source includes a patch atop upstream which drops the execute permission from installed .so libraries. Between Base:System/pcp revisions 61 and 63 we went from installing some monitoring agent binary and library files, with 0755 and 0644 mode flags respectively, to only installing library files: E.g. Base:System/pcp> osc diff -r 61:63 |grep -A7 -e "pmdas/linux/" -e Install-libraries-without-exec-permission ... -- Index: 0001-Install-libraries-without-exec-permission.patch =================================================================== --- 0001-Install-libraries-without-exec-permission.patch (added) +++ 0001-Install-libraries-without-exec-permission.patch (revision 63) @@ -0,0 +1,333 @@ +From 550357486d093e60ddf8102cf3ff474c7fa1721d Mon Sep 17 00:00:00 2001 +From: =?UTF-8?q?Klaus=20K=C3=A4mpf?= <kkaempf(a)suse.de> +Date: Fri, 12 Dec 2014 15:43:00 +0100 +Subject: [PATCH 1/6] Install libraries without exec permission + +--- -- ... -- +diff --git a/src/pmdas/linux/GNUmakefile b/src/pmdas/linux/GNUmakefile +index bd76a5938154..b049d7a398ae 100644 +--- a/src/pmdas/linux/GNUmakefile ++++ b/src/pmdas/linux/GNUmakefile +@@ -88,7 +88,7 @@ install: default + $(INSTALL) -m 755 -d $(PMDADIR) + $(INSTALL) -m 644 domain.h help $(HELPTARGETS) $(PMDADIR) + $(INSTALL) -m 644 bandwidth.conf $(PMDADIR)/samplebandwidth.conf +- $(INSTALL) -m 755 $(LIBTARGET) $(CMDTARGET) $(PMDADIR) ++ $(INSTALL) -m 644 $(LIBTARGET) $(PMDADIR)/$(LIBTARGET) + $(INSTALL) -m 644 root_linux $(PCP_VAR_DIR)/pmns/root_linux -- Index: 0002-Install-libraries-without-exec-permission.patch =================================================================== --- 0002-Install-libraries-without-exec-permission.patch (revision 61) +++ 0002-Install-libraries-without-exec-permission.patch (deleted) @@ -1,440 +0,0 @@ -From 865c920542f1cc499500c97217bfb36b70541765 Mon Sep 17 00:00:00 2001 -From: =?UTF-8?q?Klaus=20K=C3=A4mpf?= <kkaempf(a)suse.de> -Date: Fri, 12 Dec 2014 15:43:00 +0100 -Subject: [PATCH 2/6] Install libraries without exec permission - ---- -- ... -- -Index: pcp-3.11.9/src/pmdas/linux/GNUmakefile -=================================================================== ---- pcp-3.11.9.orig/src/pmdas/linux/GNUmakefile -+++ pcp-3.11.9/src/pmdas/linux/GNUmakefile -@@ -78,7 +78,8 @@ install: default - $(INSTALL) -m 755 -d $(PMDADIR) - $(INSTALL) -m 644 domain.h help $(HELPTARGETS) $(PMDADIR) - $(INSTALL) -m 644 bandwidth.conf $(PMDADIR)/samplebandwidth.conf -- $(INSTALL) -m 755 $(LIBTARGET) $(CMDTARGET) $(PMDADIR) -+ $(INSTALL) -m 644 $(LIBTARGET) $(PMDADIR)/$(LIBTARGET) -+ $(INSTALL) -m 755 $(CMDTARGET) $(PMDADIR)/$(CMDTARGET) -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1121914] New: PCP monitoring agent leaves behind zombie processes
by bugzilla_noreply＠novell.com 23 Feb '21

23 Feb '21

http://bugzilla.suse.com/show_bug.cgi?id=1121914 Bug ID: 1121914 Summary: PCP monitoring agent leaves behind zombie processes Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: ddiss(a)suse.com Reporter: ddiss(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- # pcp -V pcp version 4.1.1 # systemctl status pmcd ● pmcd.service - Performance Metrics Collector Daemon Loaded: loaded (/usr/lib/systemd/system/pmcd.service; disabled; vendor preset: disabled) Active: active (running) since Mon 2019-01-14 23:23:40 CET; 6min ago Docs: man:pmcd(8) Process: 5328 ExecStart=/usr/share/pcp/lib/pmcd start (code=exited, status=0/SUCCESS) Main PID: 5420 (pmcd) Tasks: 7 (limit: 20889) CGroup: /system.slice/pmcd.service ├─5420 /usr/lib64/pcp/bin/pmcd ├─5423 /var/lib/pcp/pmdas/root/pmdaroot ├─5425 /var/lib/pcp/pmdas/xfs/pmdaxfs -d 11 └─5427 /var/lib/pcp/pmdas/kvm/pmdakvm -d 95 Jan 14 23:23:40 kerbus systemd[1]: Starting Performance Metrics Collector Daemon... Jan 14 23:23:40 kerbus pmcd[5328]: Starting pmcd ... ..done Jan 14 23:23:40 kerbus systemd[1]: Started Performance Metrics Collector Daemon. # ps -elf|grep pmda 4 S root 5423 5420 0 80 0 - 16399 core_s 23:23 ? 00:00:00 /var/lib/pcp/pmdas/root/pmdaroot 1 Z root 5424 5423 0 80 0 - 0 - 23:23 ? 00:00:00 [pmdaroot] <defunct> 4 S root 5425 5423 0 80 0 - 15832 - 23:23 ? 00:00:00 /var/lib/pcp/pmdas/xfs/pmdaxfs -d 11 1 Z root 5426 5423 0 80 0 - 0 - 23:23 ? 00:00:00 [pmdaroot] <defunct> 4 S root 5427 5423 0 80 0 - 15827 - 23:23 ? 00:00:00 /var/lib/pcp/pmdas/kvm/pmdakvm -d 95 0 R root 5767 5277 0 80 0 - 1858 - 23:29 pts/4 00:00:00 grep --color=auto pmda It seems that the zombies correspond to the "proc" and "linux" pmdas, which fail to be spawned by the parent pmdaroot process - /var/log/pcp/pmcd/root.log: [Mon Jan 14 23:23:40] pmdaroot(5423) Info: Starting proc agent: /var/lib/pcp/pmdas/proc/pmdaproc -d 3 pmdaroot: error starting /var/lib/pcp/pmdas/proc/pmdaproc: No such file or directory [Mon Jan 14 23:23:40] pmdaroot(5423) Info: Starting xfs agent: /var/lib/pcp/pmdas/xfs/pmdaxfs -d 11 [Mon Jan 14 23:23:40] pmdaroot(5423) Info: Starting linux agent: /var/lib/pcp/pmdas/linux/pmdalinux pmdaroot: error starting /var/lib/pcp/pmdas/linux/pmdalinux: No such file or directory [Mon Jan 14 23:23:40] pmdaroot(5423) Info: Starting kvm agent: /var/lib/pcp/pmdas/kvm/pmdakvm -d 95 -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1025744] New: Shaking rendering on windows resize or some with transparency
by bugzilla_noreply＠novell.com 20 Feb '21

20 Feb '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1025744 Bug ID: 1025744 Summary: Shaking rendering on windows resize or some with transparency Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: heitorcmj(a)gmail.com QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- I can't describe as a log what is exactly occurring. Please watch the video I uploaded to try to describe it. When I type an URL in the Firefox the search combobox shakes as well. When resizing a window, as shown in the video, the problem occurs too. When transparency is enable in Terminator, the bug blur all the window and when I hold it with the mouse, the blur is gone. Type again and it blurs again. When transparency is disable, it doesn't happens. In Konsole, the blur doesn't occurs, even if transparency is enable. https://youtu.be/drm_lHXTIBM -- You are receiving this mail because: You are on the CC list for the bug.

2 19

[Bug 981271] New: KTTSMgr cannot use festival 2.4 in 13.1 or 13.2 or 42.1
by bugzilla_noreply＠novell.com 19 Feb '21

19 Feb '21

http://bugzilla.opensuse.org/show_bug.cgi?id=981271 Bug ID: 981271 Summary: KTTSMgr cannot use festival 2.4 in 13.1 or 13.2 or 42.1 Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 URL: http://bugs.pearsoncomputing.net/show_bug.cgi?id=2657 OS: Other Status: NEW Keywords: accessibility Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de CC: anixx(a)opensuse.org Found By: --- Blocker: --- To reproduce: 1.ensure sound system works reliably 2.install festival and kdeaccessibility3 or trinity-tdeaccessibility from standard repos 3.enable festival with chkconfig (no systemd service for it exists) 4.open a KDE3 or TDE session 5.open KTTSMgr 6.try to add or edit a talker (talker tab) Actual behavior: 1.voice query fails 2.Enable on General tab cannot be selected 3.TTS cannot produce sound Expected behavior: 1.voice query succeeds 2.enabling on General tab is possible 3.TTS works as expected (e.g. speak clipboard) Notes: 1-KDE3's KTTSMgr on 13.1 on host Easystreet made sound until most recent updating, which replaced festival 2.1 with 2.4. Reverting to festival 2.1 from OSS repo restored sound. 2.KDE3' KTTSMgr on 13.2 had never been made to find voices or make sound on host Easystreet. I was only able to make it find voices and make sound after replacing its installed festival 2.4 from KDE3 repo with 2.1 from OSS repo. 3.TDE's KTTSMgr on 42.1 on hosts Easystreet and gx62b would not find voices or make sound until I replaced their festival 2.4 with the 2.1 version from 13.2's OSS repo. 4.TDE's KTTSMgr on Debian stretch on host Easystreet works as expected with its own festival 2.4. Yet to do is figure out why same OS/KTTSMgr/festival on host big41 does not output sound, though it does claim to find voices and appear fully configured to output sound, and other apps do output sound. 5.mailing list thread: http://trinity-users.pearsoncomputing.net/?0::10248 -- You are receiving this mail because: You are on the CC list for the bug.

2 22

[Bug 1115109] New: empathy does not limit icon size in history
by bugzilla_noreply＠novell.com 19 Feb '21

19 Feb '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1115109 Bug ID: 1115109 Summary: empathy does not limit icon size in history Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: luizluca(a)tre-sc.jus.br QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, I'm using kde configured to use breeze icons for gtk apps. In empathy history dialog, there is an icon at the beginning of each chat. It seems to be format-justify-fill In my system, it is using /usr/share/icons/breeze/actions/16/format-justify-fill.svg from breeze5-icons-5.51.0-1.2.noarch. The problem is that empathy history expands that icon to fill windows width. The first line in icon file has a viewbox property: <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"> Empathy history dialog does not respect viewbox property (should it?). The same does not happen when the icon is an bitmap image (PNG), like oxygen icons. The result is that I need to scroll down a "window width" to read any text at all. This is quite annoying. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1127667] New: GNOME:Factory/webkit2gtk3: high CPU usage resulting in Midori and Gnome Web slow loading pages
by bugzilla_noreply＠novell.com 19 Feb '21

19 Feb '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1127667 Bug ID: 1127667 Summary: GNOME:Factory/webkit2gtk3: high CPU usage resulting in Midori and Gnome Web slow loading pages Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: os.gnome.maintainers(a)gmail.com Reporter: maurizio.galli(a)gmail.com QA Contact: bnc-team-screening(a)forge.provo.novell.com Found By: --- Blocker: --- When using Midori (and Gnome Web) web2gtk process uses high CPU every time a page is loading. One consequence of this is pages loading time being slow. Please let me know additional info to provide to debug this. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1049382] New: geany does not produce consistent output
by bugzilla_noreply＠novell.com 19 Feb '21

19 Feb '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1049382 Bug ID: 1049382 Summary: geany does not produce consistent output Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: Development Blocker: --- When the glfw package is built, it calls geany -v -c geany_config -g glfw.c.tags ...c but this produces varying results probably depending on some ordering in the filesystem. Diffing the build logs gave: - In file included from /tmp/tmp_F5J72Y.cpp:2:0: - ./src/wl_platform.h:30:10: fatal error: wayland-client.h: No such file or directory - #include <wayland-client.h> - ^~~~~~~~~~~~~~~~~~ + In file included from ./src/glx_context.c:28:0, + from /tmp/tmp_PQIPOZ.cpp:1: + ./src/internal.h:175:3: error: #error "No supported window creation API selected" + #error "No supported window creation API selected" + ^~~~~ + In file included from /tmp/tmp_PQIPOZ.cpp:6:0: + ./src/egl_context.h:50:3: error: #error "No supported EGL platform selected" + #error "No supported EGL platform selected" + ^~~~~ + In file included from /tmp/tmp_PQIPOZ.cpp:9:0: + ./src/mir_platform.h:34:10: fatal error: mir_toolkit/mir_client_library.h: No such file or directory + #include <mir_toolkit/mir_client_library.h> + ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. so it seems, the 'compilation terminated' happens in different places. -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1017652] New: tracker-extract process generating core dumps through udev bad system call to socket()
by bugzilla_noreply＠novell.com 19 Feb '21

19 Feb '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1017652 Bug ID: 1017652 Summary: tracker-extract process generating core dumps through udev bad system call to socket() Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: bwilson3013(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:50.0) Gecko/20100101 Firefox/50.0 Build Identifier: After updating openSUSE Tumbleweed yesterday (12/29), I discovered that the tracker-extract process was cyclically failing and causing core dumps to be generated through systemd-coredump. The issue does not start until I log into the GNOME desktop (Wayland and/or X.org), and is not present if I log into the IceWM desktop. When I log into the GNOME desktop, I quickly hear my laptop fans kick into high gear, and I can see several (6-8) systemd-coredump processes running to generate the core dump files. I can see the new core-dump files being actively created in /var/lib/systemd/coredump/ When I first noticed this issue, I was using the packman-essentials repo for codes. I disabled the packman-essentials repo and reverted to the official Tumbleweed versions, and the issue is still present. I did a little debugging with the systemd coredumpctl utility, and the error seems to be caused by a bad system call in glibc socket(). Here's the gdb output and backtrace: Core was generated by `/usr/lib/tracker-extract'. Program terminated with signal SIGSYS, Bad system call. #0 0x00007f34356a1587 in socket () at ../sysdeps/unix/syscall-template.S:84 84 ../sysdeps/unix/syscall-template.S: No such file or directory. [Current thread is 1 (Thread 0x7f3413b15700 (LWP 2777))] (gdb) bt #0 0x00007f34356a1587 in socket () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007f342fb0d304 in udev_monitor_new_from_netlink_fd (udev=0x7f340c379be0, name=<optimized out>, fd=-1) at src/libudev/libudev-monitor.c:207 #2 0x00007f343178a3a2 in () at /usr/lib64/libgudev-1.0.so.0 #3 0x00007f3435e9f0d7 in () at /usr/lib64/libgobject-2.0.so.0 #4 0x00007f3435ea0a6e in g_object_new_valist () at /usr/lib64/libgobject-2.0.so.0 #5 0x00007f3435ea0d11 in g_object_new () at /usr/lib64/libgobject-2.0.so.0 #6 0x00007f343178a537 in g_udev_client_new () at /usr/lib64/libgudev-1.0.so.0 #7 0x00007f33fe030d3a in () at /usr/lib64/gstreamer-1.0/libgstvideo4linux2.so #8 0x00007f33fe00ea53 in () at /usr/lib64/gstreamer-1.0/libgstvideo4linux2.so #9 0x00007f34207d10f7 in () at /usr/lib64/libgstreamer-1.0.so.0 #10 0x00007f34207d3068 in () at /usr/lib64/libgstreamer-1.0.so.0 #11 0x00007f34207dfc0e in () at /usr/lib64/libgstreamer-1.0.so.0 #12 0x00007f34207e0d01 in () at /usr/lib64/libgstreamer-1.0.so.0 #13 0x00007f34207e0ed6 in () at /usr/lib64/libgstreamer-1.0.so.0 #14 0x00007f34207e2b24 in gst_update_registry () at /usr/lib64/libgstreamer-1.0.so.0 #15 0x00007f342077d41e in () at /usr/lib64/libgstreamer-1.0.so.0 #16 0x00007f3435bcc988 in g_option_context_parse () at /usr/lib64/libglib-2.0.so.0 #17 0x00007f342077ddef in gst_init_check () at /usr/lib64/libgstreamer-1.0.so.0 #18 0x00007f342077de44 in gst_init () at /usr/lib64/libgstreamer-1.0.so.0 #19 0x00007f342110434b in tracker_extract_gstreamer (uri=uri@entry=0x7f340c007930 "file:///home/bwilson3013/Music/moe_/Sticks%20and%20Stones/02%20Sticks%20and%20Stones.m4a", info=info@entry=0x7f3418003060, type=type@entry=EXTRACT_MIME_AUDIO) at tracker-extract-gstreamer.c:1341 #20 0x00007f3421105b59 in tracker_extract_get_metadata (info=0x7f3418003060) at tracker-extract-gstreamer.c:1470 #21 0x000000000040ba86 in get_file_metadata (task=task@entry=0x17ad590, info_out=info_out@entry=0x7f3413b14d10) at tracker-extract.c:326 #22 0x000000000040bb53 in get_metadata (task=0x17ad590) at tracker-extract.c:510 #23 0x000000000040bbb0 in single_thread_get_metadata (queue=0x1932510) at tracker-extract.c:538 #24 0x00007f3435be81c5 in () at /usr/lib64/libglib-2.0.so.0 #25 0x00007f343595d454 in start_thread (arg=0x7f3413b15700) at pthread_create.c:333 #26 0x00007f34356a037f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Reproducible: Always Steps to Reproduce: 1. Turn on computer 2. Log into GNOME 3. See systemd-coredump processes running Actual Results: New core dump files for /usr/lib/tracker-extract appear in /var/lib/systemd/coredump/ Expected Results: GNOME tracker (or udev) should not be generating core dumps -- You are receiving this mail because: You are on the CC list for the bug.

2 68

[Bug 1132919] New: seccheck systemd timers not started at system boot
by bugzilla_noreply＠novell.com 14 Feb '21

14 Feb '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1132919 Bug ID: 1132919 Summary: seccheck systemd timers not started at system boot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: d_werner(a)gmx.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:60.0) Gecko/20100101 Firefox/60.0 Build Identifier: Recently for Tumbleweed and Leap 15.1 the seccheck package was changed to use systemd timers instead of cron. Leap 15.1: rpm -q seccheck seccheck-3.0-lp151.4.1.noarch After installation the timers are all disabled even when before with cron jobs the checks were activated and although /etc/sysconfig/seccheck contains START_SECCHK="yes" I think this should at least be documented so that users can activate them. Somebody who installs this package probably wants them active. As I want these checks to be executed I enabled and started the timers. After the next boot the timers are still enabled, but they are not started: systemctl status -l seccheck-{dai,week,month}ly.timer ● seccheck-daily.timer - Daily seccheck run Loaded: loaded (/usr/lib/systemd/system/seccheck-daily.timer; enabled; vendor preset: disabled) Active: inactive (dead) Trigger: n/a ● seccheck-weekly.timer - Weekly seccheck run Loaded: loaded (/usr/lib/systemd/system/seccheck-weekly.timer; enabled; vendor preset: disabled) Active: inactive (dead) Trigger: n/a ● seccheck-monthly.timer - Monthly seccheck run Loaded: loaded (/usr/lib/systemd/system/seccheck-monthly.timer; enabled; vendor preset: disabled) Active: inactive (dead) Trigger: n/a Timers which are enabled should be started automatically during system startup I think, e.g. the logrotate.timer is. Reproducible: Always Steps to Reproduce: 1.install the seccheck package (e.g. "zypper in seccheck") 2.activate the systemd timers: (systemctl enable seccheck-{dai,week,month}ly.timer) 3.verify the timers have correctly been enabled: systemctl status seccheck-{dai,week,month}ly.timer and check "enabled" state 4.reboot, check if the timers are Active, e.g. wrong state: ● seccheck-daily.timer - Daily seccheck run Loaded: loaded (/usr/lib/systemd/system/seccheck-daily.timer; enabled; vendor preset: disabled) Active: inactive (dead) Trigger: n/a correct state would be: ● seccheck-daily.timer - Daily seccheck run Loaded: loaded (/usr/lib/systemd/system/seccheck-daily.timer; enabled; vendor preset: disabled) Active: active (waiting) since Fri 2019-04-19 18:55:16 CEST; 8s ago Trigger: Sat 2019-04-20 00:00:00 CEST; 5h 4min left Actual Results: the systemd seccheck related timers are inactive after boot although enabled Expected Results: Timers should be active automatically after boot when enabled -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1084758] New: seccheck fails to cleanup some temporary files created during daily and weekly run
by bugzilla_noreply＠novell.com 14 Feb '21

14 Feb '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1084758 Bug ID: 1084758 Summary: seccheck fails to cleanup some temporary files created during daily and weekly run Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: d_werner(a)gmx.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 Build Identifier: During each run of the daily or weekly cron jobs of seccheck afterwards temporary files are left. Specifically these files are daily: created by the pattern specia_files_owner.XXXX in security_daily_helper.inc e.g. /tmp/specia_files_owner.Jx25 weekly: created by the pattern rpm-md5.XXXX in helper.inc e.g. /tmp/rpm-md5.AYWm This is observed with the rpm seccheck-3.0-lp150.2.3.noarch.rpm from Leap 15.0 Build 153.1 Reproducible: Always Steps to Reproduce: 1.have the seccheck rpm installed (and ensure the START_SECCHK="yes" which is the default) 2.let the time pass when the cron job triggers or tweak it to run "soon" 3.check if the files /tmp/rpm-md5.* or /tmp/specia_files_owner.* exist after the cronjob is finished dependent whether the daily or the weekly cron job was executed. Note: the weekly job can run for several minutes. Actual Results: Temporary files created by the cron job are left after the cron job completes. /tmp/specia_files_owner.???? /tmp/rpm-md5.???? Expected Results: seccheck should not leave temporary files after it finishes successfully. I do not consider this bug is not an actual security problem, it is just in a security related component. As far as I remember it even was already once fixed but crept in again. Note: this is not a new problem, AFAIK it also exists in Leap 42.3 and Tumbleweed, but maybe now is a good time to fix it and the fix is simple. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1094834] New: Unable to install leap 15 on Lenovo T430 along with Windows 10 in dual boot
by bugzilla_noreply＠novell.com 13 Feb '21

13 Feb '21

http://bugzilla.suse.com/show_bug.cgi?id=1094834 Bug ID: 1094834 Summary: Unable to install leap 15 on Lenovo T430 along with Windows 10 in dual boot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: rashmiranjan.mohanty(a)microfocus.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 771520 --> http://bugzilla.suse.com/attachment.cgi?id=771520&action=edit Screenshot of hung install I am unable to install openSUSE Leap 15.0 on my Lenovo T430 laptop. It already has Windows 10 installed. I am trying to install Leap 15 as dual OS. It just gets stuck on the progress bar screen (After loading Kernel and before installer UI comes up). Attaching screenshot. System does not hang though. System responds to Ctrl+Alt+Delete fine and reboots. Additional information : 1. On the same laptop Windows 7 and OpenSUSE leap 42.3 were running fine in dual boot mode before formatting the whole system. 2. I tried DVD and NET media for Leap 15 and it gets stuck at same place. 3. Even tried installing Leap 42.3. That also got stuck in the progress screen. 4. Then I tried installing Fedora 27 and it installed fine. I know since the media is already released there may not be much that can be done to fix the issue in media, but if any workaround can be provided so that I can install Leap 15 on the system, I will be more than happy. -- You are receiving this mail because: You are on the CC list for the bug.

2 43

[Bug 1093098] New: document minimum disk size
by bugzilla_noreply＠novell.com 13 Feb '21

13 Feb '21

http://bugzilla.suse.com/show_bug.cgi?id=1093098 Bug ID: 1093098 Summary: document minimum disk size Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Release Notes Assignee: sknorr(a)suse.com Reporter: lnussel(a)suse.com QA Contact: lnussel(a)suse.com CC: ancor(a)suse.com Found By: --- Blocker: --- The installer will only propose a partitioning scheme if the available hard disk size is larger than 12GB. Administrators wanting to install e.g. very small virtual machines images will have to use the guided setup to tune the parameters for the partitioning manually. -- You are receiving this mail because: You are on the CC list for the bug.

2 11

[Bug 1091103] New: Release notes entry about automatic Qt HiDPI scaling
by bugzilla_noreply＠novell.com 13 Feb '21

13 Feb '21

http://bugzilla.suse.com/show_bug.cgi?id=1091103 Bug ID: 1091103 Summary: Release notes entry about automatic Qt HiDPI scaling Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Release Notes Assignee: sknorr(a)suse.com Reporter: fvogt(a)suse.com QA Contact: lnussel(a)suse.com CC: opensuse-kde-bugs(a)opensuse.org Found By: --- Blocker: --- Release notes entry for bsc#1089932 and related. It's a rather complicated topic unfortunately, with no easy fix or workarounds available. Qt supports automatic per-monitor scaling on X. It uses the DPI value of the virtual X screen to calculate the font size for the primary monitor, which is by default 96. It uses the relative DPI of the primary monitor to derive font DPI for all other monitors. If the primary monitor is HiDPI (>= 144dpi), this means the font has effectively a 0.5x scale on all monitors. Applications which request it (e.g. VLC) have too small text on all monitors. Applications which do not request scaling (e.g. YaST) are not affected and use the same DPI value on all monitors. Applications run on KDE Plasma or GNOME are not affected as Plasma disables automatic scaling by default and GNOME sets Xft.dpi according to the monitor scale. Workarounds: a) Use a non-HiDPI monitor as primary monitor. VLC is then scaled accordingly on the HiDPI monitor. b) Set the font DPI (Xft.dpi) using the DE configuration or "echo Xft.dpi: <value> | xrdb -nocpp -merge" to equal the DPI of the primary monitor c) Disable automatic scaling: export QT_AUTO_SCREEN_SCALE_FACTOR=0 (maybe this part into a separate section?) HiDPI support in sddm: To enable HiDPI support in sddm, edit /etc/sddm.conf and set: [X11] EnableHiDPI=true ServerArguments=-nolisten tcp -dpi <dpi> with <dpi> being 96*scale of the first monitor listed by "xrandr". -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1089315] New: Tracker bug for bugs impacting transactional-netboot
by bugzilla_noreply＠novell.com 11 Feb '21

11 Feb '21

http://bugzilla.suse.com/show_bug.cgi?id=1089315 Bug ID: 1089315 Summary: Tracker bug for bugs impacting transactional-netboot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: fvogt(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is a tracker bug for all issues having an impact on transactional-netboot. -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1089349] New: overlayfs does not work with NFS as lower layer
by bugzilla_noreply＠novell.com 11 Feb '21

11 Feb '21

http://bugzilla.suse.com/show_bug.cgi?id=1089349 Bug ID: 1089349 Summary: overlayfs does not work with NFS as lower layer Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 766955 --> http://bugzilla.suse.com/attachment.cgi?id=766955&action=edit 0001-ovl-Allow-copying-of-files-to-the-upper-layer-from-c.patch When replicating a file/dir from a lower to the upper layer, it tries to copy all xattrs. However, this fails with NFSv4 as it has a special "system.nfs4_acl" xattr" which can't be written if the upper layer isn't NFSv4 (which is not supported anyway). A patch which fixes this issue is attached, but I'm not very familiar with either overlayfs nor xattrs to be able to tell whether it's correct. -- You are receiving this mail because: You are on the CC list for the bug.

2 21

[Bug 912059] New: networkmanager plasmoid shows nearly everybody connected (although it seems that only one wpa2 is correctly connected
by bugzilla_noreply＠novell.com 11 Feb '21

11 Feb '21

http://bugzilla.opensuse.org/show_bug.cgi?id=912059 Bug ID: 912059 Summary: networkmanager plasmoid shows nearly everybody connected (although it seems that only one wpa2 is correctly connected Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Minor Priority: P5 - None Component: KDE4 Applications Assignee: kde-maintainers(a)suse.de Reporter: stakanov(a)freenet.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 618858 --> http://bugzilla.opensuse.org/attachment.cgi?id=618858&action=edit wrong connection info of networkmanager plugin Create several users. Create in user A a connection with wpa2 encryption, choose: only this user can connect. Save and connect. Look at the list of the plasmoid: it shows all available wlan as not connected and the one you created as connected. Now change to user B or C. As you are still up with user A and you are connected, now in user B or C it should show the same as in user A. Only it should not be possible to end simply this connection or to start it. But you will be able to use it. What happens: in B or C respectively, the list of all available stations shows up as "connected". So in theory you are connected to all wireless of the area. All? No, some do show up correctly as "not connected" but the list here is so long that I can show only the beginning of the screen-shot. The output of ifconfig and netstat seem normal. So this seems to be more an apparent than a real bug. I join a screenshot. What should have done the program: show the correct connection information. Screen-shot: the only "real" connection iw the one with the button disconnect. The other ssids are from the neighborhood. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1096072] New: systemd hangs on initrd-switch-root.service for 1.5 minutes when booting
by bugzilla_noreply＠novell.com 10 Feb '21

10 Feb '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1096072 Bug ID: 1096072 Summary: systemd hangs on initrd-switch-root.service for 1.5 minutes when booting Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: alarrosa(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 772558 --> http://bugzilla.opensuse.org/attachment.cgi?id=772558&action=edit journalctl --system --since "1 hour ago" After upgrading my Leap 42.3 system to Leap 15.0 it takes very long to boot up. Of that time, around 1.5 minutes (1:34) is spent on initrd-switch-root.service while it seems the system is doing nothing (at least the hard disk light stops blinking for all that time). The system stops just after: Jun 05 18:32:41 geeko systemd[1]: Switching root. Jun 05 18:32:41 geeko systemd-journald[154]: Journal stopped And then continues with: Jun 05 18:34:16 geeko systemd-journald[154]: Received SIGTERM from PID 1 (systemd). Jun 05 18:34:16 geeko kernel: systemd: 20 output lines suppressed due to ratelimiting Jun 05 18:34:16 geeko kernel: EXT4-fs (sda6): re-mounted. Opts: acl,user_xattr Jun 05 18:34:16 geeko systemd-journald[414]: Journal started Jun 05 18:34:16 geeko systemd-journald[414]: Runtime journal (/run/log/journal/f7cb102c5d6c079fd36e51615215ef87) is 8.0M, max 383.4M, 375.4M free. Jun 05 18:32:43 geeko systemd[1]: systemd 234 running in system mode. (+PAM -AUDIT +SELINUX -IMA +APPARMOR -SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT -GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN2 -IDN default-hierarchy=hybrid) Jun 05 18:32:43 geeko systemd[1]: Detected architecture x86-64. Jun 05 18:32:43 geeko systemd[1]: Set hostname to <geeko>. Jun 05 18:34:13 geeko systemd[1]: system-generators terminated by signal ALRM. Jun 05 18:34:16 geeko apparmor.systemd[420]: Restarting AppArmor Jun 05 18:34:13 geeko systemd[1]: Execution failed: Protocol error Note the systemd log from 18:32:43 being written after other logs from 18:34:16 and the "Execution failed: Protocol error" message which might be related. I tried enabling debug-shell.service, but that is started after systemd unfreezes. I attach the full output of journalctl --system --since "1 hour ago". Btw, for some reason, in this system, journalctl only shows the journal logs from the current boot, never showing logs from previous boots. Also, just in case it rings a bell, I also have this problem on the same system: https://bugzilla.opensuse.org/show_bug.cgi?id=1096050 -- You are receiving this mail because: You are on the CC list for the bug.

2 35

[Bug 980313] New: /usr/lib/zypp/plugins/commit/susemanager should be moved to susemanager related package and not be part of base salt-minion
by bugzilla_noreply＠novell.com 08 Feb '21

08 Feb '21

http://bugzilla.suse.com/show_bug.cgi?id=980313 Bug ID: 980313 Summary: /usr/lib/zypp/plugins/commit/susemanager should be moved to susemanager related package and not be part of base salt-minion Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mrueckert(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- seen with salt-minion-2015.8.8-68.1.x86_64 from systemsmanagement:saltstack the salt setup on the machine was turned off atm and this noticably slows down all zypp operations. if this plugin is mostly for susemanager it shouldnt be part of the normal salt-minion package. if it is meant to be used with normal salt, i would recommend renaming it. -- You are receiving this mail because: You are on the CC list for the bug.

2 25

[Bug 978833] New: systemsmanagement:saltstack/salt broken pkgrepo.managed priority atribute
by bugzilla_noreply＠novell.com 08 Feb '21

08 Feb '21

http://bugzilla.suse.com/show_bug.cgi?id=978833 Bug ID: 978833 Summary: systemsmanagement:saltstack/salt broken pkgrepo.managed priority atribute Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bmaryniuk(a)suse.com Reporter: tchatzimichos(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- pkgrepo.managed priority attribute shows the following error: Failed to configure repo 'NON_Public:Infrastructure': zypper command failed: Invalid priority ''102''. Use a positive integer number. The greater the number, the lower the priority. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1032452] New: salt-cloud package misses deployment scripts
by bugzilla_noreply＠novell.com 08 Feb '21

08 Feb '21

http://bugzilla.suse.com/show_bug.cgi?id=1032452 Bug ID: 1032452 Summary: salt-cloud package misses deployment scripts Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: openSUSE 42.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dkarakasilis(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 Build Identifier: There is a number of scripts that salt-cloud uses in order to "saltify" (aka bootstrap) the minions: https://github.com/saltstack/salt/tree/develop/salt/cloud/deploy One of them (bootstrap-salt.sh) is the default when no specific (or custom) script is specified in configuration. None of our packages (salt, salt-cloud) provide that script. As a result, when a machine is started on some public cloud (only tried ec2 driver), the machine doesn't get salt-master or salt-minion services installed or run. The bootstrap process is completely ignored. After copying the bootstrap-salt.sh script from the github repo in "/usr/lib/python2.7/site-packages/salt/cloud/deploy" directory, the machines gets saltified. One thing to keep in mind though, if we are going to package those files, is that there is a "salt-cloud -u" command that fetches the latest versions from i-dont-know-where. That might mean, our users will use versions of those scripts that weren't packaged (or tested) by us. The 'salt-cloud -u' command doesn't fetch anything in my case, I don't know if this is because of the files missing in the first place or some other problem. Reproducible: Always Steps to Reproduce: 1. In OpenSUSE LEAP 42.2 install the packages salt-cloud and salt 2. Create ec2 provider and profile configuration 3. Try to create a saltified machine. E.g. "salt-cloud -p my_ec2_profile my_machine_name" Actual Results: The machine is created but there is no salt related package installed and no salt service running. We should get at least salt-minion running. Expected Results: Depending on configuration we should get "salt-minion" services installed and running. If we set "make_master: True" in our configuration we should also get salt-master service installed and running. below are an ec2 provider and profile examples. Replace placeholders with something working. > cat /etc/salt/cloud.providers.d/my-ec2.provider.conf my-ec2-provider: id: your_id_here key: 'your_key_here' keyname: your_key_name_as_it_appears_in_aws_console subnetid: comment_out_if_no_subnet_is_used private_key: your_pem_key_path # Make sure it is owned by whatever user salt is run as driver: ec2 ssh_interface: public_ips > cat /etc/salt/cloud.profiles.d/base_ec2.conf base_ec2: provider: my-ec2-provider # Opensuse image image: ami-eada30fc size: t2.micro make_master: True ssh_username: ec2-user -- You are receiving this mail because: You are on the CC list for the bug.

2 28

[Bug 1020831] New: All salt commands hang and cause salt-master to crash soon after
by bugzilla_noreply＠novell.com 08 Feb '21

08 Feb '21

http://bugzilla.suse.com/show_bug.cgi?id=1020831 Bug ID: 1020831 Summary: All salt commands hang and cause salt-master to crash soon after Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: hguo(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 710818 --> http://bugzilla.suse.com/attachment.cgi?id=710818&action=edit master journal I started 3 fresh instances of Leap 42.2 on EC2, then proceed to install all updates and salt. Two minions can successfully join the master, but then all salt commands issued by master hang and cause salt-master to crash soon after a python error is raised. See attached log files. -- You are receiving this mail because: You are on the CC list for the bug.

2 41

[Bug 1104594] New: VoIP programs fail to connect to a SIP account.
by bugzilla_noreply＠novell.com 06 Feb '21

06 Feb '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1104594 Bug ID: 1104594 Summary: VoIP programs fail to connect to a SIP account. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mail(a)marekpasnikowski.name QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have a SIP account registered with SipGate. Both Ekiga and Ring fail to connect to that account. I did not have this problem when I used SUSE Linux Enterprise Desktop on the same computer. -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1117483] New: openvswitch: please consider dropping the use of DISABLE_STOP_ON_REMOVAL/DISABLE_RESTART_ON_UPDATE
by bugzilla_noreply＠novell.com 05 Feb '21

05 Feb '21

http://bugzilla.suse.com/show_bug.cgi?id=1117483 Bug ID: 1117483 Summary: openvswitch: please consider dropping the use of DISABLE_STOP_ON_REMOVAL/DISABLE_RESTART_ON_UPDATE Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: fbui(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi Jaime, After a discussion with Markos, it appears that the use of both DISABLE_STOP_ON_REMOVAL=yes and DISABLE_RESTART_ON_UPDATE=yes in openvswitch.spec is not needed at all. Regarding DISABLE_RESTART_ON_UPDATE=yes and according to Markos, OVS services can now be restarted on package updates because "it's being handled by the upper layers from crowbar or whatever else management tool they use". Even if the package would still need to be restarted on updates, %systemd_postun_with_restart() or %systemd_postun() macros should be used instead of the env variable. Regarding DISABLE_STOP_ON_REMOVAL=yes: this was actually an "addon" on the previous issue but it's not needed at all. It would be nice if it could be dropped especially since a) leaving a daemon running while all its files (binaries, libs, config files, etc...) have been deleted may obviously lead to crashes b) one can expect that the network is going down if a package such as openvswitch is removed. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

2 38

[Bug 1058115] New: ORC tracker
by bugzilla_noreply＠novell.com 05 Feb '21

05 Feb '21

http://bugzilla.suse.com/show_bug.cgi?id=1058115 Bug ID: 1058115 Summary: ORC tracker Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: jslaby(a)suse.com Reporter: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is a tracker for ORC patches. -- You are receiving this mail because: You are on the CC list for the bug.

2 102

[Bug 1046104] New: Monospaced font SourceCodePro is bold by default after update to texlive 2017
by bugzilla_noreply＠novell.com 02 Feb '21

02 Feb '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1046104 Bug ID: 1046104 Summary: Monospaced font SourceCodePro is bold by default after update to texlive 2017 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mail(a)philipp-wagner.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 730330 --> http://bugzilla.opensuse.org/attachment.cgi?id=730330&action=edit Screenshot with texlive-sourcecodepro installed Since the last update including the new texlive 2017 packages, the default monospace font (SourceCodePro) on my system was overwritten with a bold one. Things are better explained in a picture as seen in the attached screenshots. I got things back to normal by deinstalling the texlive versions of the font with > sudo zypper remove texlive-sourcecodepro* Now the following packets are installed: > LANG=C sudo zypper search sourcecodepro Loading repository data... Reading installed packages... S | Name | Summary | Type ---+-----------------------------+----------------------------------------------------------+-------- i+ | adobe-sourcecodepro-fonts | A set of OpenType fonts designed for coding environments | package | texlive-sourcecodepro | Use SourceCodePro with TeX(-alike) systems | package | texlive-sourcecodepro-doc | Documentation for texlive-sourcecodepro | package | texlive-sourcecodepro-fonts | Severed fonts for texlive-sourcecodepro | package I've confirmed with fc-match that if the texlive packages are installed, the texlive version of SourceCodePro is used. Otherwise, it's the version from the adobe-sourcecodepro-fonts package. I've also attached the output of "fc-match -v monospace" before and after deinstalling the texlive package. My system information: > cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20170625" ID=opensuse ID_LIKE="suse" VERSION_ID="20170625" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20170625" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1102143] New: blueman-applet - missing German translations / l10n
by bugzilla_noreply＠novell.com 31 Jan '21

31 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1102143 Bug ID: 1102143 Summary: blueman-applet - missing German translations / l10n Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Minor Priority: P5 - None Component: Translations Assignee: ke(a)suse.com Reporter: linuxandlanguages(a)t-online.de QA Contact: ke(a)suse.com Found By: --- Blocker: --- Hello everyone, I noticed that in blueman-applet the following menu entry is not localized. Desktop environment is LXDE. Steps to reproduce: zypper install blueman blueman-applet (from command line) Menü -> Gerät -> "Rename device" is not localized but in https://github.com/blueman-project/blueman/blob/master/po/de.po the string is already translated. Also: Adapter -> Preferences isn't localized either but I don't know where these strings can be found. Could you sync the latest translations for "Tumbleweed" please? Regards, Maik -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1078162] New: Unable to add Brother HL-2370DW printer via Gnome Settings
by bugzilla_noreply＠novell.com 29 Jan '21

29 Jan '21

http://bugzilla.suse.com/show_bug.cgi?id=1078162 Bug ID: 1078162 Summary: Unable to add Brother HL-2370DW printer via Gnome Settings Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: tonyj(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Same issue as reported here: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1721704 Open settings, select devices/printers. Unlock to root, select "add". Searching for printer yields nothing, so I enter it's IP address. It immediately returns with 2 options, Jet Direct and LPD. I select Jet Direct and it gets stuck at "Loading Drivers Database". I have to eventually abort with cancel. gnome-settings-daemon-3.26.2-1.1.x86_64 cups-2.2.6-2.1.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1062303] New: trackerbug: packages do not build reproducibly from randomness
by bugzilla_noreply＠novell.com 26 Jan '21

26 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1062303 Bug ID: 1062303 Summary: trackerbug: packages do not build reproducibly from randomness Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: Development Blocker: --- See also https://reproducible-builds.org/ When packages write random bytes into files that are packaged it results in binaries that differ on every build. These thus trigger rebuilds of depending packages and are published to mirrors and users when actually nothing really changed. -- You are receiving this mail because: You are on the CC list for the bug.

2 18

[Bug 1131894] New: smbios patch that qemu carries has multiple issues
by bugzilla_noreply＠novell.com 25 Jan '21

25 Jan '21

http://bugzilla.suse.com/show_bug.cgi?id=1131894 Bug ID: 1131894 Summary: smbios patch that qemu carries has multiple issues Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KVM Assignee: kvm-bugs(a)suse.de Reporter: brogers(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm creating a new bug report instead of reopening the original bug report because the patch did basically address the issue reported. But recently an issue with that patch was brought to my attention because the latest upstream code now allows compiling qemu with -Werror, and so a warning for this patch became evident, and points out a code issue that needs to be addressed. But beyond the warning causing build failure and the code issue needing to be fixed, this patch prevents us from being compatible with upstream as far as the -smbios file=xxxx usage is concerned. This needs to be addressed as well. Details: The code statement: table_str_field_count = sizeof(tables_str_field_offset) / sizeof(tables_str_field_offset[0]); is erroneous and doesn't achieve the desire result. One solution is to simply assign it the appropriate TYPE_X_STR_FIELD_COUNT (substituting for X). The existing fix allows for using legacy smbios file data with more recent x86 machine types, whereas upstream expects per-spec smbios data when the machine types is newer than pc-i440fx-2.0. It's unfortunate that the interpretation of the file data is tied to the machine type. This is a backwards compatibility issue, hence the original bug. -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1080592] New: feh needs libjpeg-turbo
by bugzilla_noreply＠novell.com 25 Jan '21

25 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1080592 Bug ID: 1080592 Summary: feh needs libjpeg-turbo Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: All OS: openSUSE 42.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: novell(a)howorth.org.uk QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I sometimes use 'feh' to browse images. I used it today but when I tried to rotate a picture (File/Edit in Place/Rotate 90 CW) the rotate didn't happen and I got a useful error message in the command terminal: $ feh WARNING: lossless rotate: Is 'jpegtran' installed? Failed to exec: No such file or directory feh WARNING: lossless rotate: Got exitcode 1 from jpegtran. Commandline was: jpegtran -copy all -rotate 90 -outfile P1020918.JPG P1020918.JPG This is on 42.3. The last time I used rotate was on 42.2 and I'm fairly sure it worked there. The current version of feh is 2.18.3-7.1-x86_64 from openSUSE-Leap-42.3-Oss. YaST doesn't show me any results when I search for jpegtran. rpmfind OTOH finds libjpeg-turbo-1.5.3-42.1 and says it contains jpegtran. And sure enough after I install libjpeg-turbo, rotation works in feh. But YaST still doesn't return any results for jpegtran. I believe: feh should require libjpeg-turbo since it is required for feh to function properly. -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1131885] New: VUL-1: CVE-2019-10732: kmail: attacker in possession of S/MIME or PGP encrypted emails can wrap them as sub-parts within a crafted multipart email
by bugzilla_noreply＠novell.com 25 Jan '21

25 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1131885 Bug ID: 1131885 Summary: VUL-1: CVE-2019-10732: kmail: attacker in possession of S/MIME or PGP encrypted emails can wrap them as sub-parts within a crafted multipart email Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other URL: https://smash.suse.de/issue/229064/ OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Security Assignee: lbeltrame(a)kde.org Reporter: atoptsoglou(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2019-10732 In KDE KMail 5.2.3, an attacker in possession of S/MIME or PGP encrypted emails can wrap them as sub-parts within a crafted multipart email. The encrypted part(s) can further be hidden using HTML/CSS or ASCII newline characters. This modified multipart email can be re-sent by the attacker to the intended receiver. If the receiver replies to this (benign looking) email, they unknowingly leak the plaintext of the encrypted message part(s) back to the attacker. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-10732 http://www.cvedetails.com/cve/CVE-2019-10732/ http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10732 https://bugs.kde.org/show_bug.cgi?id=404698 -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1098635] New: Application:Geo/grass: Bug DBMI-PostgreSQL not working
by bugzilla_noreply＠novell.com 25 Jan '21

25 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1098635 Bug ID: 1098635 Summary: Application:Geo/grass: Bug DBMI-PostgreSQL not working Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: openSUSE 42.3 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: dassau(a)gbd-consult.de Reporter: nrochard(a)gmail.com QA Contact: bnc-team-screening(a)forge.provo.novell.com CC: tzotsos(a)gmail.com Found By: --- Blocker: --- Hello, I've use db.connect and db.login over pg driver to connect to a PostGIS Server : it works. db.tables can list all tables but not much more. But when I try v.external to display PostGIS table into GRASS : Using DB driver: pg EXECUTE: OK EXECUTE: OK EXECUTE: OK DBMI-PostgreSQL driver error missing Regards Nicolas -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1120960] New: Undefined method "key?" for false:FalseClass while parsing autoinst.xml
by bugzilla_noreply＠novell.com 22 Jan '21

22 Jan '21

http://bugzilla.suse.com/show_bug.cgi?id=1120960 Bug ID: 1120960 Summary: Undefined method "key?" for false:FalseClass while parsing autoinst.xml Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: AutoYaST Assignee: yast2-maintainers(a)suse.de Reporter: pieter(a)hollants.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 793781 --> http://bugzilla.suse.com/attachment.cgi?id=793781&action=edit Screenshot of Yast crash With current (20181225) Tumbleweed NET Install ISO, YaST crashes with "Undefined key 'key?' for false::FalseClass" while parsing the attached minimal control file. This happens even before /tmp/profile/* get created, so I assume it is some early code parsing the control file and expecting something that is not present. -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1128780] New: mysql-workbench 8.x crashes with mySQL 8.0 ...
by bugzilla_noreply＠novell.com 20 Jan '21

20 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1128780 Bug ID: 1128780 Summary: mysql-workbench 8.x crashes with mySQL 8.0 ... Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dutch.glory(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 799648 --> http://bugzilla.opensuse.org/attachment.cgi?id=799648&action=edit wb.log Using OpenSUSE Tumbleweed: Operating System: OpenSUSE Tumbleweed 2019.03.07 KDE Plasma Version: 5.15.2 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.0 Kernel Version: 4.20.13-1-default OS Type: 64-bit Processors: 2 × Intel® Core™2 CPU 6700 @ 2.66GHz Memory: 5,8 GiB downloaded/installed mysql-workbench from: http://download.opensuse.org/repositories/server:/database/openSUSE_Tumblew… when i try to connect to mysql, mysql-workbench crashes (root an non-root) WB.log: 23:50:28 [INF][ WBContext UI]: Initializing workbench context UI with these values: base dir: /usr/share/mysql-workbench plugin path: /usr/lib64/mysql-workbench/plugins struct path: /usr/share/mysql-workbench/grt module path: /usr/lib64/mysql-workbench/modules library path: /usr/share/mysql-workbench/libraries user data dir: /root/.mysql/workbench open at start: open type: run at startup: run type: Force SW rendering: No Force OpenGL: No quit when done: No 23:50:28 [INF][ WBContext]: WbContext::init 23:50:28 [WRN][ grt]: Could not load wb.model.grt.so: Could not open module /usr/lib64/mysql-workbench/modules/wb.model.grt.so (/usr/lib64/mysql-workbench/modules/wb.model.grt.so: undefined symbol: _ZN9Scintilla8WordListD1Ev) 23:50:28 [INF][ WBA]: Looking for extension modules for WBA... 23:50:28 [INF][ WBA]: 0 extension modules found 23:50:28 [WRN][ grt]: Could not load db.mysql.diff.reporting.wbp.so: Could not open module /usr/lib64/mysql-workbench/plugins/db.mysql.diff.reporting.wbp.so (/usr/lib64/mysql-workbench/plugins/db.mysql.diff.reporting.wbp.so: undefined symbol: _Z17build_catalog_mapN3grt3RefI16db_mysql_CatalogEERSt3mapINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEENS0_I14GrtNamedObjectEESt4lessIS9_ESaISt4pairIKS9_SB_EEE) 23:50:28 [WRN][ grt]: /usr/share/mysql-workbench/modules/data/mysql_rdbms_info.xml:1446: link 'om.mysql.rdbms.mysql.driver.native_sshtun' <object > key=owner could not be resolved 23:50:28 [WRN][ grt]: /root/.mysql/workbench/connections.xml:23: link 'aa7b93dc-4386-11e9-a89e-0019d1852a92' <object GrtObject> key=owner could not be resolved 23:50:28 [INF][ WBContext]: System info: MySQL Workbench Community (GPL) for Linux/Unix version 8.0.15 CE build 14271522 (64 bit) Configuration Directory: /root/.mysql/workbench Data Directory: /usr/share/mysql-workbench Cairo Version: 1.16.0 OS: x86_64 CPU: 2x Intel(R) Core(TM)2 CPU 6700 @ 2.66GHz (2072.567MHz) - 5,75GiB RAM No video adapter info available Fips mode enabled: no 23:50:28 [WRN][ WBModule]: OS not found on supported OS list. OS string: ' x86_64' -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1120397] New: I Cannot launch YaST modules from the LXQt programs menu
by bugzilla_noreply＠novell.com 16 Jan '21

16 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1120397 Bug ID: 1120397 Summary: I Cannot launch YaST modules from the LXQt programs menu Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: trcs(a)gmx.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When I click any of the YaST modules menu entries in the programs menu, nothing happens. The only one working is YaST Control Center, and from there the modules can be launch without issues. I think it is something related to quotes because it works fine if I remove the quotes around $cmd in the line $LXQTSU -s "$cmd" of the su_lxqt() function in the /usr/bin/xdg-su script. The LXQt sudo dialog shows a different quotation around the command when I remove the aforementioned quotes. For example: Command: '/sbin/yast2 sound' → xdg-su not modified, it doesn't work Command: '/sbin/yast2' 'sound' → xdg-su modified, it works Following with the example, if I run the command of the Exec key in YaST2/sound.desktop (xdg-su -c "/sbin/yast2 sound") from the terminal, I get the following error: bash: /sbin/yast2 sound: No such file or directory If I use the X11:LXQt:git repository the problem remains, YaST modules menu entries don't work. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1112631] New: Out of date package: openSUSE:Factory/alacritty is out of date
by bugzilla_noreply＠novell.com 16 Jan '21

16 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1112631 Bug ID: 1112631 Summary: Out of date package: openSUSE:Factory/alacritty is out of date Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: sean(a)suspend.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- https://build.opensuse.org/package/show/openSUSE:Factory/alacritty is out of date. New version available upstream at: https://github.com/jwilm/alacritty/archive/v0.2.1.tar.gz. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1113996] New: yast2_hostnames parsing error has unclear error message
by bugzilla_noreply＠novell.com 15 Jan '21

15 Jan '21

http://bugzilla.suse.com/show_bug.cgi?id=1113996 Bug ID: 1113996 Summary: yast2_hostnames parsing error has unclear error message Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: agraul(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 787810 --> http://bugzilla.suse.com/attachment.cgi?id=787810&action=edit Example on fresh TW 20181022 installation A misconfigured /etc/hosts file results in a somewhat misleading error message: ``` Error Internal error. Please report a bug report with logs. Run save_y2logs to get complete logs. Details: Augeas parsing error: Iterated lens matched less than it should at /etc/hosts:23:7, lens /usr/share/augeas/lenses/dist/hosts.aug:13.12-.52: Caller: /usr/lib64/ruby/gems/2.5.0/gems/cfa-0.6.4/lib/cfa/augeas_parser.rb:377:in `report_error' ``` While it is possible to read that the parsing failed, untrained eyes will have a problem with parsing this error message. I would expect a clear message telling me to check the file manually for misconfiguration. -- You are receiving this mail because: You are on the CC list for the bug.

2 11

[Bug 980577] New: "cobbler get-loaders" doesn't resolve www.clobberd.org
by bugzilla_noreply＠novell.com 14 Jan '21

14 Jan '21

http://bugzilla.suse.com/show_bug.cgi?id=980577 Bug ID: 980577 Summary: "cobbler get-loaders" doesn't resolve www.clobberd.org Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: pablo.suarezhernandez(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ferruja:~ # cobbler get-loaders task started: 2016-05-18_154111_get_loaders task started (id=Download Bootloader Content, time=Wed May 18 15:41:11 2016) downloading http://www.cobblerd.org/loaders/README to /var/lib/cobbler/loaders/README Exception occured: <class 'urlgrabber.grabber.URLGrabError'> Exception value: [Errno 14] PYCURL ERROR 6 - "Could not resolve host: www.cobblerd.org" Exception Info: File "/usr/lib/python2.7/site-packages/cobbler/remote.py", line 87, in run rc = self._run(self) File "/usr/lib/python2.7/site-packages/cobbler/remote.py", line 181, in runner return self.remote.api.dlcontent(self.options.get("force",False), self.logger) File "/usr/lib/python2.7/site-packages/cobbler/api.py", line 751, in dlcontent return grabber.run(force) File "/usr/lib/python2.7/site-packages/cobbler/action_dlcontent.py", line 72, in run urlgrabber.grabber.urlgrab(src, filename=dst, proxies=proxies) File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 618, in urlgrab return default_grabber.urlgrab(url, filename, **kwargs) File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 982, in urlgrab return self._retry(opts, retryfunc, url, filename) File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 886, in _retry r = apply(func, (opts,) + args, {}) File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 968, in retryfunc fo = PyCurlFileObject(url, filename, opts) File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 1063, in __init__ self._do_open() File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 1352, in _do_open self._do_grab() File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 1482, in _do_grab self._do_perform() File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 1339, in _do_perform raise err !!! TASK FAILED !!! -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 956264] New: cobbler_web apache config uses old syntax
by bugzilla_noreply＠novell.com 14 Jan '21

14 Jan '21

http://bugzilla.suse.com/show_bug.cgi?id=956264 Bug ID: 956264 Summary: cobbler_web apache config uses old syntax Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: osynge(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Please set up cobbler and cobbler_web to use new syntax. Require all granted instead of Order allow,deny Allow from all See http://httpd.apache.org/docs/2.4/upgrading.html. -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1124922] New: Service systemd-remount-fs.service failing often on transactional-update system
by bugzilla_noreply＠novell.com 14 Jan '21

14 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1124922 Bug ID: 1124922 Summary: Service systemd-remount-fs.service failing often on transactional-update system Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: okurz(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Osservation ``` # systemctl --failed UNIT LOAD ACTIVE SUB DESCRIPTION ● systemd-remount-fs.service loaded failed failed Remount Root and Kernel File Systems LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 1 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. # systemctl status systemd-remount-fs.service ● systemd-remount-fs.service - Remount Root and Kernel File Systems Loaded: loaded (/usr/lib/systemd/system/systemd-remount-fs.service; static; vendor preset: disabled) Active: failed (Result: exit-code) since Mon 2019-02-11 03:34:13 CET; 3h 49min ago Docs: man:systemd-remount-fs.service(8) https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems Main PID: 761 (code=exited, status=1/FAILURE) Feb 11 03:34:13 openqaworker4 systemd-remount-fs[761]: mount: /: mount point is busy. Feb 11 03:34:13 openqaworker4 systemd-remount-fs[761]: /usr/bin/mount for / exited with exit status 32. Feb 11 03:34:13 openqaworker4 systemd[1]: systemd-remount-fs.service: Main process exited, code=exited, status=1/FAILURE Feb 11 03:34:13 openqaworker4 systemd[1]: Failed to start Remount Root and Kernel File Systems. Feb 11 03:34:13 openqaworker4 systemd[1]: systemd-remount-fs.service: Unit entered failed state. Feb 11 03:34:13 openqaworker4 systemd[1]: systemd-remount-fs.service: Failed with result 'exit-code'. ``` -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1032027] New: btrfs cleaner => freeze
by bugzilla_noreply＠novell.com 11 Jan '21

11 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1032027 Bug ID: 1032027 Summary: btrfs cleaner => freeze Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: epistemepromeneur(a)free.fr QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- each time btrfs cleaner is active then all dialogs are freezed. we must wait for the end to use our pc. on a slow laptop we must wait several minutes! -- You are receiving this mail because: You are on the CC list for the bug.

2 27

[Bug 956153] New: Software Update Error "License Agreement Failed" But A License Agreement Is Never Presented
by bugzilla_noreply＠novell.com 08 Jan '21

08 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=956153 Bug ID: 956153 Summary: Software Update Error "License Agreement Failed" But A License Agreement Is Never Presented Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: bill_wayson(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 656868 --> http://bugzilla.opensuse.org/attachment.cgi?id=656868&action=edit Zip file with error message screenshot, zypper.log, and pk_backend_zypp files On Saturday morning (11/21/2015 PST) I am presented with 246 updates by the software updater. I press the "Install Updates" button, and the update begins. But it quickly stops with a message dialog "Update Error The license agreement failed. The license agreement was not agreed to. To use this software you have to accept the license." The problems are that a license agreement dialog is never presented, and there is no indication of which of the 246 updates require the license agreement (so that I can, say, deselect it). I have attached a zip file that contains a screenshot of the message along with the zypper.log and pk_backend_zypp files. The latter file appears to be the log updated by the software updater. My tumbleweed is currently at 20151113. I hope I chose the correct component. -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 1133764] New: [TRACKER] port packages to use file triggers
by bugzilla_noreply＠novell.com 08 Jan '21

08 Jan '21

http://bugzilla.suse.com/show_bug.cgi?id=1133764 Bug ID: 1133764 Summary: [TRACKER] port packages to use file triggers Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- several packages would benefit from the usage of file triggers to replace eg %post scripts that packagers have to remember to use in a correct way in %post: https://rpm.org/user_doc/file_triggers.html The tracker to collect information. -- You are receiving this mail because: You are on the CC list for the bug.

2 14

[Bug 1133272] New: LTO: papi build fails
by bugzilla_noreply＠novell.com 08 Jan '21

08 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1133272 Bug ID: 1133272 Summary: LTO: papi build fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: martin.liska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Fails due to: [ 27s] make[1]: Leaving directory '/home/abuild/rpmbuild/BUILD/papi-5.7.0/src/ftests' [ 31s] instructions_testcode.c: Assembler messages: [ 31s] instructions_testcode.c:13: Error: symbol `test_loop' is already defined [ 31s] lto-wrapper: fatal error: gcc returned 1 exit status [ 31s] compilation terminated. [ 31s] /usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld: error: lto-wrapper failed [ 31s] collect2: error: ld returned 1 exit status -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1004049] New: /usr/bin/socat ... openpty() is not allowd to do chown of resulting /dev/pts/ device
by bugzilla_noreply＠novell.com 08 Jan '21

08 Jan '21

http://bugzilla.suse.com/show_bug.cgi?id=1004049 Bug ID: 1004049 Summary: /usr/bin/socat ... openpty() is not allowd to do chown of resulting /dev/pts/ device Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: All OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: werner(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Even with apparmor disabled I see in the strace close(8) = 0 close(7) = 0 chown("/dev/pts/8", 223, 5) = -1 EPERM (Operation not permitted) close(6) = 0 which makes this tool useless for normal users. Beside this: why we do have setcap/getcap installed by default? With this we would be able to set permissions based on capabilities for tools like setcap and ping, ping6, ... in the %post install section of the rpm of the affected tools -- You are receiving this mail because: You are on the CC list for the bug.

2 16

[Bug 954603] New: Leap lacks tomcat
by bugzilla_noreply＠novell.com 07 Jan '21

07 Jan '21

http://bugzilla.suse.com/show_bug.cgi?id=954603 Bug ID: 954603 Summary: Leap lacks tomcat Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Java Assignee: bnc-team-java(a)forge.provo.novell.com Reporter: tchvatal(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Leap lacks tomcat as it didn't build. I will submit fixed dbcp that should go later as maint-update to SLE12 directly and for tomcat we can grab 1:1 the SLE-12:SP1 counterpart. -- You are receiving this mail because: You are on the CC list for the bug.

2 11