May 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1094772] New: Distributed phpPgAdmin 5.1 does not support distributed PostgreSQL 10.3
by bugzilla_noreply＠novell.com 04 May '20

04 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1094772 Bug ID: 1094772 Summary: Distributed phpPgAdmin 5.1 does not support distributed PostgreSQL 10.3 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: woe.2018(a)wizonet.ch QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The phpPgSql tool shipped with openSuSE Leap15 does not support the shipped PostgreSQL version 10.3. Loggin into a 10.3 server ends up with this message: Ihre PostgreSQL-Version wird nicht unterstützt. Bitte stellen Sie Ihre Datenbank auf Version oder eine neuere Version um. I've tried to deinstal postgresql10-server and then install postgresql96-server, but postgresql10-server is an dependency of postgresql96-server and therefore this ends up in an installed postgres 10.3 server again. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1121298] New: 389-ds from server:Kolab:Extras doesn't
by bugzilla_noreply＠novell.com 03 May '20

03 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1121298 Bug ID: 1121298 Summary: 389-ds from server:Kolab:Extras doesn't Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: openSUSE Factory Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: ecsos(a)schirra.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The 389 Directory Server (389-ds) doesn't start. Directory /var/lib/dirsrv has 0750 dirsrv:dirsrv but kolab need write rights. So /var/lib/dirsrv need: 0770 dirsrv:kolab or need: 0770 dirsrv:dirsrv and kolab must in group dirsrv. Without that Server can not be start. -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1125664] New: Spyder 3.3.2 broken menu and toolbars icons
by bugzilla_noreply＠novell.com 01 May '20

01 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1125664 Bug ID: 1125664 Summary: Spyder 3.3.2 broken menu and toolbars icons Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: cygnix(a)tutanota.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 797005 --> http://bugzilla.opensuse.org/attachment.cgi?id=797005&action=edit broken icons screen caption As of openSUSE Tumbleweed 20190214, all menu and toolbars icons are broken on Spyder 3.3.2. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1134805] New: Graphical artifacts in KDE and SDDM, using radeon driver
by bugzilla_noreply＠novell.com 01 May '20

01 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1134805 Bug ID: 1134805 Summary: Graphical artifacts in KDE and SDDM, using radeon driver Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: opensuse.lietuviu.kalba(a)gmail.com QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- Created attachment 804814 --> http://bugzilla.opensuse.org/attachment.cgi?id=804814&action=edit /var/log/Xorg.0.log I see graphical artifacts during KDE logout and in SDDM. Operating System: openSUSE Tumbleweed 20190509 KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.3 Kernel Version: 5.0.11-1-default OS Type: 32-bit Processors: 1 × Intel® Celeron® D CPU 3.06GHz Memory: 1,8 GiB /etc/X11/xorg.conf does not exist > zypper se --details --installed-only xf86-video- Loading repository data... Reading installed packages... S | Name | Type | Version | Arch ---+-------------------+---------+------------+----- i+ | xf86-video-amdgpu | package | 19.0.1-1.1 | i586 i+ | xf86-video-ati | package | 19.0.1-1.1 | i586 i | xf86-video-dummy | package | 0.3.8-1.6 | i586 i+ | xf86-video-fbdev | package | 0.5.0-1.4 | i586 i+ | xf86-video-mach64 | package | 6.9.6-1.4 | i586 i+ | xf86-video-r128 | package | 6.11.0-1.2 | i586 i+ | xf86-video-vesa | package | 2.4.0-1.4 | i586 > rpm -q sddm | head -n3 sddm-0.18.0-7.1.i586 > rpm --changelog -q sddm | head -n3 * Mon Feb 18 2019 Fabian Vogt <fabian(a)ritter-vogt.de> - Add patch to fix reading garbage from getpwnam (boo#1125624): * 0001-Use-C-scoping-for-handling-buffer-deletion.patch > rpm --changelog -q Mesa | head -n3 * Fri Apr 26 2019 Stefan Dirsch <sndirsch(a)suse.com> - Update to 19.0.3 * quiet release with just 19 patches (excluding release churn) > rpm --changelog -q xorg-x11-server | head -n3 * Wed Apr 24 2019 Martin Li?ka <mliska(a)suse.cz> - Disable LTO (boo#1133294). > rpm --changelog -q xf86-input-evdev | head -n3 * Wed May 30 2018 sndirsch(a)suse.com - upt to version 2.10.6 * Since evdev is in maintenance mode there aren't a lot of > rpm --changelog -q xf86-video-ati | head -n3 * Fri Mar 22 2019 Stefan Dirsch <sndirsch(a)suse.com> - Update to release 19.0.1 * Fixes for two regressions which crept into the 19.0.0 release. > rpm --changelog -q xf86-video-fbdev | head -n3 * Mon Jun 04 2018 sndirsch(a)suse.com - Update to version 0.5.0 * Compatibility updates for xserver 1.20. > rpm --changelog -q xf86-video-modesetting | head -n3 package xf86-video-modesetting is not installed > rpm --changelog -q xf86-video-vesa | head -n3 * Fri Feb 16 2018 sndirsch(a)suse.com - Update to version 2.4.0 * Nothing terribly exciting, but enough bug fixes to justify a > hwinfo --gfx 14: PCI 105.0: 0300 VGA compatible controller (VGA) [Created at pci.386] Unique ID: ul7N.n3FKoMfWx+7 Parent ID: vSkL.4UFp5fHqms6 SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:01:05.0 SysFS BusID: 0000:01:05.0 Hardware Class: graphics card Model: "ATI Radeon XPRESS 200 5A61 (PCIE)" Vendor: pci 0x1002 "ATI Technologies Inc" Device: pci 0x5a61 "Radeon XPRESS 200 5A61 (PCIE)" SubVendor: pci 0x8086 "Intel Corporation" SubDevice: pci 0xd601 Driver: "radeon" Driver Modules: "radeon" Memory Range: 0x80000000-0x8fffffff (ro,non-prefetchable) I/O Ports: 0x2000-0x2fff (rw) Memory Range: 0xa0100000-0xa010ffff (rw,non-prefetchable) Memory Range: 0x000c0000-0x000dffff (rw,non-prefetchable,disabled) IRQ: 17 (3009 events) I/O Ports: 0x3c0-0x3df (rw) Module Alias: "pci:v00001002d00005A61sv00008086sd0000D601bc03sc00i00" Driver Info #0: XFree86 v4 Server Module: radeon Driver Info #1: XFree86 v4 Server Module: fglrx 3D Support: yes Extensions: dri Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #20 (PCI bridge) -- You are receiving this mail because: You are on the CC list for the bug.

1 34

[Bug 1066021] New: Always getting 'Failed unmounting Runtime Directory' (and /var) during shutdown
by bugzilla_noreply＠novell.com 01 May '20

01 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1066021 Bug ID: 1066021 Summary: Always getting 'Failed unmounting Runtime Directory' (and /var) during shutdown Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: x86-64 OS: openSUSE 42.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: studio(a)anchev.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Each time I shutdown/reboot I get these red colored messages: ---- Failed unmounting Runtime Directory. ... Failed unmounting /var. ---- This has been happening since I installed Leap 42.1 (currently I use 42.3). Nothing seems to have been broken so far but once during a recent boot there was some more extensive disk check. I have followed the steps given here: https://lists.opensuse.org/opensuse-factory/2016-05/msg00341.html As the guys in the forums asked to look at the beginning of the log here are the first 20 lines of the latest log file: https://susepaste.org/71c124c1 These are the last 40 lines of the log: https://susepaste.org/29aa84b3 The message "Failed to unmount /var" appears during shutdown right before this message (I don't know why it is not in the log though): [ 31.245825] systemd-shutdown[1]: Unmounting /var. /var is sdb3 Another message which always appears in the log is this one: [ 10.165896] FAT-fs (sdd1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. sdd1 is /boot/efi Looking at SMART tests - all disks are fine, i.e. it is not a hardware issue. I am hesitant to share the full shutdown-log.txt as I am cautious about the security of the system (it seems to expose certain data) but if there is any other way to diagnose this and provide necessary data please let me know. You can see the whole forum discussion: https://forums.opensuse.org/showthread.php/527879-Always-getting-Failed-unm… -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1076039] New: science/slepc: Bug slepc-openmpi-devel not installable
by bugzilla_noreply＠novell.com 30 Apr '20

30 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1076039 Bug ID: 1076039 Summary: science/slepc: Bug slepc-openmpi-devel not installable Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: openSUSE 42.2 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: dmitry(a)roshchin.org Reporter: gass(a)search.ch QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- slepc-openmpi-devel is not installable on openSUSE Tumbleweed or openSUSE Leap 42.2. Commands to reproduce the problem: zypper addrepo 'http://download.opensuse.org/repositories/science/openSUSE_Leap_42.2/' science zypper install slepc-openmpi-devel Relevant output: Problem: nothing provides petsc-openmpi-devel needed by slepc-openmpi-devel-3.7.3-1.19.x86_64 Greetings Nathan Gass -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1123328] New: obs-arm-7 hangs on umount/mount (obs worker kvm builds) with kernel >= 4.19
by bugzilla_noreply＠novell.com 29 Apr '20

29 Apr '20

http://bugzilla.suse.com/show_bug.cgi?id=1123328 Bug ID: 1123328 Summary: obs-arm-7 hangs on umount/mount (obs worker kvm builds) with kernel >= 4.19 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: dmueller(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- when obs-arm-7 (Cavium ThunderX CN99xx) builds with kernel >= 4.19, the initial umount/mount of filesystems is hanging: # ps -elf | grep umou 4 D root 60909 1 0 80 0 - 995 blk_mq Jan22 ? 00:00:00 umount /var/cache/obs/worker/root_3/.mount 0 D root 102921 102894 0 80 0 - 998 blkdev 10:11 pts/20 00:00:00 mount -o noatime,loop /var/cache/obs/worker/root_5/root /var/cache/obs/worker/root_5/.mount 0 D root 102949 102922 0 80 0 - 998 blkdev 10:11 pts/23 00:00:00 mount -o noatime,loop /var/cache/obs/worker/root_8/root /var/cache/obs/worker/root_8/.mount 0 D root 102977 102950 0 80 0 - 998 blkdev 10:11 pts/22 00:00:00 mount -o noatime,loop /var/cache/obs/worker/root_7/root /var/cache/obs/worker/root_7/.mount 0 D root 103005 102978 0 80 0 - 998 blkdev 10:11 pts/25 00:00:00 mount -o noatime,loop /var/cache/obs/worker/root_10/root /var/cache/obs/worker/root_10/.mount 0 D root 103063 103036 0 80 0 - 998 blkdev 10:12 pts/24 00:00:00 mount -o noatime,loop /var/cache/obs/worker/root_9/root /var/cache/obs/worker/root_9/.mount 0 D root 103137 103110 0 80 0 - 998 blkdev 10:13 pts/17 00:00:00 mount -o noatime,loop /var/cache/obs/worker/root_2/root /var/cache/obs/worker/root_2/.mount 0 D root 103253 103217 0 80 0 - 998 blkdev 10:14 pts/26 00:00:00 mount -o noatime,loop /var/cache/obs/worker/root_11/root /var/cache/obs/worker/root_11/.mount 0 D root 103273 103226 0 80 0 - 998 blkdev 10:14 pts/27 00:00:00 mount -o noatime,loop /var/cache/obs/worker/root_12/root /var/cache/obs/worker/root_12/.mount 0 D root 103324 103292 0 80 0 - 998 blkdev 10:14 pts/30 00:00:00 mount -o noatime,loop /var/cache/obs/worker/root_15/root /var/cache/obs/worker/root_15/.mount 0 D root 103875 103843 0 80 0 - 998 blkdev 10:21 pts/16 00:00:00 mount -o noatime,loop /var/cache/obs/worker/root_1/root /var/cache/obs/worker/root_1/.mount sysrq-W gives: [1213689.321930] task PC stack pid father [1213689.325022] umount D 0 60909 1 0x00000009 [1213689.325027] Call trace: [1213689.325035] __switch_to+0x9c/0xd8 [1213689.325042] __schedule+0x2a0/0x888 [1213689.325045] schedule+0x30/0x88 [1213689.325050] blk_mq_freeze_queue_wait+0x54/0xa0 [1213689.325053] blk_freeze_queue+0x30/0x58 [1213689.325055] blk_mq_freeze_queue+0x20/0x30 [1213689.325064] loop_clr_fd+0x4c/0x288 [loop] [1213689.325067] lo_release+0xa4/0xc8 [loop] [1213689.325072] __blkdev_put+0x22c/0x260 [1213689.325074] blkdev_put+0xe4/0x118 [1213689.325079] kill_block_super+0x44/0x58 [1213689.325082] deactivate_locked_super+0x50/0x90 [1213689.325084] deactivate_super+0x74/0x80 [1213689.325087] cleanup_mnt+0x44/0x88 [1213689.325089] __cleanup_mnt+0x20/0x30 [1213689.325093] task_work_run+0xb8/0xe8 [1213689.325096] do_notify_resume+0x2f4/0x390 [1213689.325097] work_pending+0x8/0x14 [1213689.325101] mount D 0 61620 1 0x00000001 [1213689.325104] Call trace: [1213689.325106] __switch_to+0x9c/0xd8 [1213689.325109] __schedule+0x2a0/0x888 [1213689.325111] schedule+0x30/0x88 [1213689.325113] schedule_preempt_disabled+0x14/0x20 [1213689.325115] __mutex_lock.isra.1+0x2c0/0x4b8 [1213689.325117] __mutex_lock_slowpath+0x24/0x30 [1213689.325120] mutex_lock+0x48/0x50 [1213689.325122] __blkdev_get+0x70/0x488 [1213689.325124] blkdev_get+0x10c/0x368 [1213689.325125] blkdev_open+0x9c/0xb0 [1213689.325128] do_dentry_open+0x11c/0x340 [1213689.325130] vfs_open+0x38/0x48 [1213689.325133] do_last+0x224/0x830 [1213689.325135] path_openat+0x68/0x238 [1213689.325137] do_filp_open+0x70/0xd0 [1213689.325139] do_sys_open+0x15c/0x1e8 [1213689.325141] __arm64_sys_openat+0x2c/0x38 [1213689.325145] el0_svc_common+0x98/0x100 [1213689.325147] el0_svc_handler+0x38/0x78 [1213689.325149] el0_svc+0x8/0xc [1213689.325153] mount D 0 62347 1 0x00000001 [1213689.325155] Call trace: [1213689.325157] __switch_to+0x9c/0xd8 [1213689.325160] __schedule+0x2a0/0x888 [1213689.325162] schedule+0x30/0x88 [1213689.325164] schedule_preempt_disabled+0x14/0x20 [1213689.325166] __mutex_lock.isra.1+0x2c0/0x4b8 [1213689.325168] __mutex_lock_slowpath+0x24/0x30 [1213689.325170] mutex_lock+0x48/0x50 [1213689.325172] __blkdev_get+0x70/0x488 [1213689.325174] blkdev_get+0x10c/0x368 [1213689.325176] blkdev_open+0x9c/0xb0 [1213689.325178] do_dentry_open+0x11c/0x340 [1213689.325179] vfs_open+0x38/0x48 [1213689.325182] do_last+0x224/0x830 [1213689.325184] path_openat+0x68/0x238 [1213689.325186] do_filp_open+0x70/0xd0 [1213689.325187] do_sys_open+0x15c/0x1e8 [1213689.325189] __arm64_sys_openat+0x2c/0x38 [1213689.325191] el0_svc_common+0x98/0x100 [1213689.325193] el0_svc_handler+0x38/0x78 [1213689.325195] el0_svc+0x8/0xc [1213689.325199] mount D 0 62405 1 0x00000001 [1213689.325201] Call trace: [1213689.325203] __switch_to+0x9c/0xd8 [1213689.325205] __schedule+0x2a0/0x888 [1213689.325207] schedule+0x30/0x88 [1213689.325209] schedule_preempt_disabled+0x14/0x20 [1213689.325211] __mutex_lock.isra.1+0x2c0/0x4b8 [1213689.325214] __mutex_lock_slowpath+0x24/0x30 [1213689.325216] mutex_lock+0x48/0x50 [1213689.325218] __blkdev_get+0x70/0x488 [1213689.325220] blkdev_get+0x10c/0x368 [1213689.325222] blkdev_open+0x9c/0xb0 [1213689.325223] do_dentry_open+0x11c/0x340 [1213689.325225] vfs_open+0x38/0x48 [1213689.325227] do_last+0x224/0x830 [1213689.325229] path_openat+0x68/0x238 [1213689.325231] do_filp_open+0x70/0xd0 [1213689.325233] do_sys_open+0x15c/0x1e8 [1213689.325234] __arm64_sys_openat+0x2c/0x38 [1213689.325237] el0_svc_common+0x98/0x100 [1213689.325239] el0_svc_handler+0x38/0x78 [1213689.325240] el0_svc+0x8/0xc [1213689.325244] mount D 0 62568 1 0x00000001 [1213689.325246] Call trace: [1213689.325248] __switch_to+0x9c/0xd8 [1213689.325250] __schedule+0x2a0/0x888 [1213689.325252] schedule+0x30/0x88 [1213689.325254] schedule_preempt_disabled+0x14/0x20 [1213689.325256] __mutex_lock.isra.1+0x2c0/0x4b8 [1213689.325258] __mutex_lock_slowpath+0x24/0x30 [1213689.325260] mutex_lock+0x48/0x50 [1213689.325262] __blkdev_get+0x70/0x488 [1213689.325264] blkdev_get+0x10c/0x368 [1213689.325266] blkdev_open+0x9c/0xb0 [1213689.325267] do_dentry_open+0x11c/0x340 [1213689.325269] vfs_open+0x38/0x48 [1213689.325271] do_last+0x224/0x830 [1213689.325273] path_openat+0x68/0x238 [1213689.325275] do_filp_open+0x70/0xd0 [1213689.325277] do_sys_open+0x15c/0x1e8 [1213689.325279] __arm64_sys_openat+0x2c/0x38 [1213689.325281] el0_svc_common+0x98/0x100 [1213689.325283] el0_svc_handler+0x38/0x78 [1213689.325284] el0_svc+0x8/0xc [1213689.325288] mount D 0 62723 1 0x00000001 [1213689.325290] Call trace: [1213689.325292] __switch_to+0x9c/0xd8 [1213689.325294] __schedule+0x2a0/0x888 [1213689.325296] schedule+0x30/0x88 [1213689.325298] schedule_preempt_disabled+0x14/0x20 [1213689.325300] __mutex_lock.isra.1+0x2c0/0x4b8 [1213689.325302] __mutex_lock_slowpath+0x24/0x30 [1213689.325304] mutex_lock+0x48/0x50 [1213689.325306] __blkdev_get+0x70/0x488 [1213689.325308] blkdev_get+0x10c/0x368 [1213689.325310] blkdev_open+0x9c/0xb0 [1213689.325312] do_dentry_open+0x11c/0x340 [1213689.325313] vfs_open+0x38/0x48 [1213689.325315] do_last+0x224/0x830 [1213689.325317] path_openat+0x68/0x238 [1213689.325319] do_filp_open+0x70/0xd0 [1213689.325321] do_sys_open+0x15c/0x1e8 [1213689.325323] __arm64_sys_openat+0x2c/0x38 [1213689.325325] el0_svc_common+0x98/0x100 [1213689.325327] el0_svc_handler+0x38/0x78 [1213689.325328] el0_svc+0x8/0xc [1213689.325333] mount D 0 66786 1 0x00000001 [1213689.325335] Call trace: [1213689.325337] __switch_to+0x9c/0xd8 [1213689.325340] __schedule+0x2a0/0x888 [1213689.325342] schedule+0x30/0x88 [1213689.325344] schedule_preempt_disabled+0x14/0x20 [1213689.325346] __mutex_lock.isra.1+0x2c0/0x4b8 [1213689.325348] __mutex_lock_slowpath+0x24/0x30 [1213689.325350] mutex_lock+0x48/0x50 [1213689.325352] __blkdev_get+0x70/0x488 [1213689.325354] blkdev_get+0x10c/0x368 [1213689.325356] blkdev_open+0x9c/0xb0 [1213689.325358] do_dentry_open+0x11c/0x340 [1213689.325360] vfs_open+0x38/0x48 [1213689.325362] do_last+0x224/0x830 [1213689.325364] path_openat+0x68/0x238 [1213689.325366] do_filp_open+0x70/0xd0 [1213689.325368] do_sys_open+0x15c/0x1e8 [1213689.325370] __arm64_sys_openat+0x2c/0x38 [1213689.325372] el0_svc_common+0x98/0x100 [1213689.325374] el0_svc_handler+0x38/0x78 [1213689.325375] el0_svc+0x8/0xc [1213689.325379] mount D 0 72349 1 0x00000001 [1213689.325381] Call trace: [1213689.325383] __switch_to+0x9c/0xd8 [1213689.325386] __schedule+0x2a0/0x888 [1213689.325388] schedule+0x30/0x88 [1213689.325390] schedule_preempt_disabled+0x14/0x20 [1213689.325392] __mutex_lock.isra.1+0x2c0/0x4b8 [1213689.325394] __mutex_lock_slowpath+0x24/0x30 [1213689.325396] mutex_lock+0x48/0x50 [1213689.325399] __blkdev_get+0x70/0x488 [1213689.325400] blkdev_get+0x10c/0x368 [1213689.325402] blkdev_open+0x9c/0xb0 [1213689.325404] do_dentry_open+0x11c/0x340 [1213689.325406] vfs_open+0x38/0x48 [1213689.325408] do_last+0x224/0x830 [1213689.325410] path_openat+0x68/0x238 [1213689.325412] do_filp_open+0x70/0xd0 [1213689.325414] do_sys_open+0x15c/0x1e8 [1213689.325416] __arm64_sys_openat+0x2c/0x38 [1213689.325418] el0_svc_common+0x98/0x100 [1213689.325420] el0_svc_handler+0x38/0x78 [1213689.325422] el0_svc+0x8/0xc [1213689.325425] mount D 0 75917 1 0x00000001 [1213689.325427] Call trace: [1213689.325429] __switch_to+0x9c/0xd8 [1213689.325432] __schedule+0x2a0/0x888 [1213689.325434] schedule+0x30/0x88 [1213689.325436] schedule_preempt_disabled+0x14/0x20 [1213689.325438] __mutex_lock.isra.1+0x2c0/0x4b8 [1213689.325440] __mutex_lock_slowpath+0x24/0x30 [1213689.325442] mutex_lock+0x48/0x50 [1213689.325444] __blkdev_get+0x70/0x488 [1213689.325446] blkdev_get+0x10c/0x368 [1213689.325448] blkdev_open+0x9c/0xb0 [1213689.325449] do_dentry_open+0x11c/0x340 [1213689.325451] vfs_open+0x38/0x48 [1213689.325453] do_last+0x224/0x830 [1213689.325455] path_openat+0x68/0x238 [1213689.325457] do_filp_open+0x70/0xd0 [1213689.325459] do_sys_open+0x15c/0x1e8 [1213689.325461] __arm64_sys_openat+0x2c/0x38 [1213689.325463] el0_svc_common+0x98/0x100 [1213689.325465] el0_svc_handler+0x38/0x78 [1213689.325467] el0_svc+0x8/0xc [1213689.325471] mount D 0 77793 1 0x00000001 [1213689.325472] Call trace: [1213689.325474] __switch_to+0x9c/0xd8 [1213689.325477] __schedule+0x2a0/0x888 [1213689.325479] schedule+0x30/0x88 [1213689.325481] schedule_preempt_disabled+0x14/0x20 [1213689.325483] __mutex_lock.isra.1+0x2c0/0x4b8 [1213689.325485] __mutex_lock_slowpath+0x24/0x30 [1213689.325487] mutex_lock+0x48/0x50 [1213689.325489] __blkdev_get+0x70/0x488 [1213689.325491] blkdev_get+0x10c/0x368 [1213689.325493] blkdev_open+0x9c/0xb0 [1213689.325494] do_dentry_open+0x11c/0x340 [1213689.325496] vfs_open+0x38/0x48 [1213689.325498] do_last+0x224/0x830 [1213689.325500] path_openat+0x68/0x238 [1213689.325502] do_filp_open+0x70/0xd0 [1213689.325504] do_sys_open+0x15c/0x1e8 [1213689.325505] __arm64_sys_openat+0x2c/0x38 [1213689.325507] el0_svc_common+0x98/0x100 [1213689.325509] el0_svc_handler+0x38/0x78 [1213689.325511] el0_svc+0x8/0xc [1213689.325514] mount D 0 79041 1 0x00000001 [1213689.325516] Call trace: [1213689.325518] __switch_to+0x9c/0xd8 [1213689.325521] __schedule+0x2a0/0x888 [1213689.325523] schedule+0x30/0x88 [1213689.325525] schedule_preempt_disabled+0x14/0x20 [1213689.325527] __mutex_lock.isra.1+0x2c0/0x4b8 [1213689.325529] __mutex_lock_slowpath+0x24/0x30 [1213689.325531] mutex_lock+0x48/0x50 [1213689.325533] __blkdev_get+0x70/0x488 [1213689.325535] blkdev_get+0x10c/0x368 [1213689.325536] blkdev_open+0x9c/0xb0 [1213689.325538] do_dentry_open+0x11c/0x340 [1213689.325540] vfs_open+0x38/0x48 [1213689.325542] do_last+0x224/0x830 [1213689.325544] path_openat+0x68/0x238 [1213689.325546] do_filp_open+0x70/0xd0 [1213689.325547] do_sys_open+0x15c/0x1e8 [1213689.325549] __arm64_sys_openat+0x2c/0x38 [1213689.325551] el0_svc_common+0x98/0x100 [1213689.325553] el0_svc_handler+0x38/0x78 [1213689.325555] el0_svc+0x8/0xc [1213689.325559] mount D 0 79830 1 0x00000001 [1213689.325560] Call trace: [1213689.325562] __switch_to+0x9c/0xd8 [1213689.325565] __schedule+0x2a0/0x888 [1213689.325567] schedule+0x30/0x88 [1213689.325569] schedule_preempt_disabled+0x14/0x20 [1213689.325571] __mutex_lock.isra.1+0x2c0/0x4b8 [1213689.325573] __mutex_lock_slowpath+0x24/0x30 [1213689.325575] mutex_lock+0x48/0x50 [1213689.325577] __blkdev_get+0x70/0x488 [1213689.325579] blkdev_get+0x10c/0x368 [1213689.325581] blkdev_open+0x9c/0xb0 [1213689.325583] do_dentry_open+0x11c/0x340 [1213689.325584] vfs_open+0x38/0x48 [1213689.325586] do_last+0x224/0x830 [1213689.325588] path_openat+0x68/0x238 [1213689.325590] do_filp_open+0x70/0xd0 [1213689.325592] do_sys_open+0x15c/0x1e8 [1213689.325594] __arm64_sys_openat+0x2c/0x38 [1213689.325596] el0_svc_common+0x98/0x100 [1213689.325598] el0_svc_handler+0x38/0x78 [1213689.325600] el0_svc+0x8/0xc [1213689.325606] mount D 0 83698 1 0x00000001 [1213689.325607] Call trace: [1213689.325609] __switch_to+0x9c/0xd8 [1213689.325612] __schedule+0x2a0/0x888 [1213689.325614] schedule+0x30/0x88 [1213689.325616] schedule_preempt_disabled+0x14/0x20 [1213689.325619] __mutex_lock.isra.1+0x2c0/0x4b8 [1213689.325621] __mutex_lock_slowpath+0x24/0x30 [1213689.325623] mutex_lock+0x48/0x50 [1213689.325625] __blkdev_get+0x70/0x488 [1213689.325627] blkdev_get+0x10c/0x368 [1213689.325629] blkdev_open+0x9c/0xb0 [1213689.325630] do_dentry_open+0x11c/0x340 [1213689.325632] vfs_open+0x38/0x48 [1213689.325634] do_last+0x224/0x830 [1213689.325636] path_openat+0x68/0x238 [1213689.325638] do_filp_open+0x70/0xd0 [1213689.325640] do_sys_open+0x15c/0x1e8 [1213689.325641] __arm64_sys_openat+0x2c/0x38 [1213689.325643] el0_svc_common+0x98/0x100 [1213689.325645] el0_svc_handler+0x38/0x78 [1213689.325647] el0_svc+0x8/0xc ... -- You are receiving this mail because: You are on the CC list for the bug.

1 39

[Bug 1063167] New: crash of synergyc
by bugzilla_noreply＠novell.com 28 Apr '20

28 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1063167 Bug ID: 1063167 Summary: crash of synergyc Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: werner(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- noether:~ # coredumpctl list synergyc TIME PID UID GID SIG COREFILE EXE Tue 2017-09-05 14:35:11 CEST 3778 223 50 11 missing /usr/bin/synergyc Tue 2017-09-12 12:49:47 CEST 2474 223 50 11 missing /usr/bin/synergyc Thu 2017-10-05 08:23:57 CEST 2956 223 50 11 none /usr/bin/synergyc Thu 2017-10-05 08:56:20 CEST 32056 223 50 11 none /usr/bin/synergyc Thu 2017-10-05 10:17:47 CEST 2495 223 50 11 none /usr/bin/synergyc Thu 2017-10-05 10:51:14 CEST 4517 223 50 11 none /usr/bin/synergyc Mon 2017-10-09 13:54:01 CEST 2147 223 50 11 none /usr/bin/synergyc Mon 2017-10-09 14:28:03 CEST 12156 223 50 11 none /usr/bin/synergyc Tue 2017-10-10 12:45:05 CEST 13178 223 50 11 none /usr/bin/synergyc Wed 2017-10-11 15:02:24 CEST 20573 223 50 11 present /usr/bin/synergyc -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1127794] New: NetworkManager keeps OpenVPN processes running
by bugzilla_noreply＠novell.com 27 Apr '20

27 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1127794 Bug ID: 1127794 Summary: NetworkManager keeps OpenVPN processes running Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: opensuse(a)pohw.nl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- NetworkManager keeps all OpenVPN processes running, even if no vpn is actually active. Once you activate one, you can't get rid of it in the process list. Closing the vpn doesn't help. Worse: the processes are kept running even after all OpenVPN profiles have been deleted: # ps axu|grep openvpn nm-open+ 6865 0.0 0.0 47384 7564 ? S 18:01 0:02 /usr/sbin/openvpn --remote <IP> 443 udp --nobind (...) nm-open+ 19826 0.0 0.0 47384 7776 ? S 18:13 0:00 /usr/sbin/openvpn --remote <IP> 443 udp --nobind (...) At one time I had 4 profiles with 4 active processes. This causes unstable OpenVPN connections, with lots of TLS errors and invalidated connections (i.e.: no traffic is possible after a number of seconds). # journalctl -f Mon Mar 4 18:23:56 2019 80.155.9.251:51053 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity) Mon Mar 4 18:23:56 2019 80.155.9.251:51053 TLS Error: TLS handshake failed Mon Mar 4 18:23:56 2019 80.155.9.251:51053 SIGUSR1[soft,tls-error] received, client-instance restarting After deleting all OpenVPN profiles and killing all OpenVPN processes, I re-imported one OpenVPN profile and everything worked flawlessly after that. -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 894783] New: CA management: Sign Request: Don't use sequential serial numbers
by bugzilla_noreply＠novell.com 26 Apr '20

26 Apr '20

https://bugzilla.novell.com/show_bug.cgi?id=894783 https://bugzilla.novell.com/show_bug.cgi?id=894783#c0 Summary: CA management: Sign Request: Don't use sequential serial numbers Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Ulrich.Windl(a)rz.uni-regensburg.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Firefox/31.0 (In openssl tradition certificates use sequential serial numbers) YaST's certificate signing function uses sequential serial numbers to issue (sign) certificates (like 01, 02, 03, ... 09, 0A, 0B, ...) Due to some weaknesses in SHA-1, there's a recommendation to use serial numbers with a higher entropy. See https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/ElekSignatur/BSI_SHA1_Z… (German): ---BEGIN quote--- Kollisionsangriffe gegen die Zertifikaterstellung mit SHA-1 können von vornherein verhindert werden, wenn folgendes gilt: 1) Es wird das X.509v3 Format gemäß ISIS-MTT verwendet. 2) Die Seriennummer ("serialNumber") des Zertifikats hat eine genügend hohe Entropie h für den Angreifer. D.h. die Unsicherheit des Angreifers über die Seriennummer eines zu erstellenden Zertifikats ist mindestens h Bits. (...) ---END quote--- Reproducible: Always Steps to Reproduce: 1. Sign a certificate request (CSR) in YaST's CA management Actual Results: The certificate gets a serial number that can easily be guessed Expected Results: The serial number should not be easy to guess See also http://www.heise.de/security/meldung/Fragwuerdige-Hash-Funktion-SHA-1-immer… (German) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 5

[Bug 1095131] New: kubelet service (1.10.2) fails to start: failed to get device for dir "/var/lib/kubelet"
by bugzilla_noreply＠novell.com 26 Apr '20

26 Apr '20

http://bugzilla.suse.com/show_bug.cgi?id=1095131 Bug ID: 1095131 Summary: kubelet service (1.10.2) fails to start: failed to get device for dir "/var/lib/kubelet" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: kubic-bugs(a)opensuse.org Reporter: mmeister(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.170 Safari/537.36 Build Identifier: May 30 04:56:24 admin hyperkube[2766]: F0530 04:56:24.779150 2766 kubelet.go:1354] Failed to start ContainerManager failed to get rootfs info: failed to get device for dir "/var/lib/kubelet": could not find device with major: 0, minor: 46 in cached partitions map kubelet wont start with kubernetes 1.10.2 it might be a regression of https://github.com/google/cadvisor/pull/1668 ? k8s is not yet updated officially, i have used: https://build.opensuse.org/package/show/home:m_meister:branches:devel:CaaSP… tested on the Stack-hardware image, which comes with the additional 9p kernel modules and k8s preinstalled: https://download.opensuse.org/repositories/devel:/CaaSP:/images/images/open… some previous discussion can be found also in https://bugzilla.suse.com/show_bug.cgi?id=1084766 Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 20

[Bug 1131607] New: yast-samba-client join fails with 'Failed to join domain: Invalid configuration ("workgroup" set to '', should be 'FROGGY') and configuration modification was not requested'
by bugzilla_noreply＠novell.com 24 Apr '20

24 Apr '20

http://bugzilla.suse.com/show_bug.cgi?id=1131607 Bug ID: 1131607 Summary: yast-samba-client join fails with 'Failed to join domain: Invalid configuration ("workgroup" set to '', should be 'FROGGY') and configuration modification was not requested' 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: david.mulder(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- If you look at the logs, you see this: 2019-04-04 12:45:40 <3> linux-0bgx.froggy.suse.de(1385) [Y2Python] YPython.cc(callInner):293 Python error: error type: <class 'NameError'>; error value: name 'Net' is not defined; error traceback: This was caused by the fix for bug 1124390. The samba imports are within a if block that doesn't always execute. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1133434] New: yast-samba-client fails to parse new idmap settings
by bugzilla_noreply＠novell.com 24 Apr '20

24 Apr '20

http://bugzilla.suse.com/show_bug.cgi?id=1133434 Bug ID: 1133434 Summary: yast-samba-client fails to parse new idmap settings 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: david.mulder(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- 2019-04-25 09:20:20 <3> linux-0bgx(11420) [agent-ini] IniParser.cc(parse_helper):869 /etc/samba/smb.conf:11: Extra characters: idmap config * : backend = tdb 2019-04-25 09:20:20 <3> linux-0bgx(11420) [agent-ini] IniParser.cc(parse_helper):869 /etc/samba/smb.conf:12: Extra characters: idmap config * : range = 10001-19999 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1021335] New: desktop files randomly miss translations
by bugzilla_noreply＠novell.com 23 Apr '20

23 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1021335 Bug ID: 1021335 Summary: desktop files randomly miss translations Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE 42.2 Status: NEW Severity: Major 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 CC: ke(a)suse.com Found By: Development Blocker: --- While working on making builds reproducible for openSUSE, I found multiple packages randomly missing translations in .desktop files. Affected packages are at least exo gedit gedit-plugins gnome-menus gnome-video-effects lxmenu-data for an example diff see https://www.zq1.de/~bernhard/linux/reproducibleopensuse/compare.factory/exo… when looking at the build.log it had sequences like [ 49s] Generating and caching the translation database [ 49s] Merging translations into debian-sensible-browser.desktop. [ 49s] LC_ALL=C /usr/bin/intltool-merge -d -u -c ../../po/.intltool-merge-cache ../../po epiphany.desktop.in epiphany.desktop [ 49s] Found cached translation database [ 49s] Merging translations into epiphany.desktop. [ 49s] LC_ALL=C /usr/bin/intltool-merge -d -u -c ../../po/.intltool-merge-cache ../../po eterm.desktop.in eterm.desktop [ 49s] Generating and caching the translation database [ 49s] Merging translations into encompass.desktop. [ 49s] LC_ALL=C /usr/bin/intltool-merge -d -u -c ../../po/.intltool-merge-cache ../../po evolution.desktop.in evolution.desktop [ 49s] Generating and caching the translation database [ 49s] Merging translations into debian-x-terminal-emulator.desktop. [ 49s] LC_ALL=C /usr/bin/intltool-merge -d -u -c ../../po/.intltool-merge-cache ../../po firefox.desktop.in firefox.desktop [ 49s] Found cached translation database so my guess is that this is running in parallel with make -j8 and thus there might be races with processes using the cache file before it is fully generated. Assiging to GNOME team as maintainers of intltool-merge tool -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1082655] New: vim: please, provide a /etc/vim.d
by bugzilla_noreply＠novell.com 23 Apr '20

23 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1082655 Bug ID: 1082655 Summary: vim: please, provide a /etc/vim.d Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: luizluca(a)tre-sc.jus.br QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- As many other sw do, vim could use a config directory. It is just a matter of including those lines in /etc/vimrc for rcfile in split(globpath("/etc/vim.d/", "*.vim"), '\n') execute('source '.rcfile) endfor -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1041112] New: KDE packagekit update dialog shows still updates available for a short time after applying updates
by bugzilla_noreply＠novell.com 23 Apr '20

23 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1041112 Bug ID: 1041112 Summary: KDE packagekit update dialog shows still updates available for a short time after applying updates Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other URL: http://lord.arch/tests/6386/modules/updates_packagekit _kde/steps/15 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: okurz(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Observation openQA test in scenario opensuse-42.2-UpdateTest-x86_64-fix_kde_update_tray@64bit-2G fails in [updates_packagekit_kde](http://lord.arch/tests/6386/modules/updates_packagekit_kde/steps/15) showing that there is an update available which has been installed just in before by a click on "Install Updates" button. This is detected by the openQA tests in about 30-50 percent of all cases. Going through the video from http://lord.arch/tests/6386/file/video.ogv is giving the best impression. There it can clearly be seen that after a click on "install updates" these are installed, the dialog shows the 1 update to install again, then it suddenly shows that there are no updates to install. Further logs are available: http://lord.arch/tests/6386#downloads ## Reproducible Fails since (at least) Build [20170526-3](http://lord.arch/tests/6361) ## Expected result Last good: (unknown), probably in there like "forever". Expected behaviour is that after refreshing there are no available updates shown anymore. Is this related to how package kit related events are handled and libzypp and such? ## Further details Always latest result in this scenario: [latest](http://lord.arch/tests/latest?flavor=UpdateTest&version=42.2&distri=opensuse&machine=64bit-2G&arch=x86_64&test=fix_kde_update_tray). Bug 992773 is probably related. If necessary we can try to provide more information in logs. Or should I report upstream? -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1132829] New: UPNP does not work in VLC
by bugzilla_noreply＠novell.com 22 Apr '20

22 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1132829 Bug ID: 1132829 Summary: UPNP does not work in VLC Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: seb95passionlinux(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- My title may be inappropriate, I apologize. I'm on openSUSE Tumbleweed (updated at this date), I have for several months (27/11/18 - https://bugzilla.opensuse.org/show_bug.cgi?id=1117448) an impossibility to browse from VLC the UPNP network. The output in a console gives this: ~$ vlc VLC media player 3.0.6 Vetinari (revision 3.0.6-0-g5803e85f73) [000055c090630ce0] main libvlc: Lancement de vlc avec l'interface par défaut. Utilisez « cvlc » pour démarrer VLC sans interface. [000055c09062b350] main playlist: playlist is empty [00007f401c656f60] upnp services discovery: Initializing libupnp on 'default' interface [00007f401c656f60] upnp services discovery error: Initialization failed: UPNP_E_SOCKET_BIND [00007f401c656f60] main services discovery error: no suitable services discovery module [00007f401c656f60] upnp services discovery: Initializing libupnp on 'default' interface [00007f401c656f60] upnp services discovery error: Initialization failed: UPNP_E_SOCKET_BIND [00007f401c656f60] main services discovery error: no suitable services discovery module I am with the VLC OSS repositories, but I can also change and put the one of packman and it does not change. I tested on an openSUSE without third-party repositories (without packman) and the problem exists. Thank you for your time. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1135082] New: zypper man page formatting broken
by bugzilla_noreply＠novell.com 21 Apr '20

21 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1135082 Bug ID: 1135082 Summary: zypper man page formatting broken Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Ruby Assignee: ruby-devel(a)suse.de Reporter: iforster(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The zypper man page (`man zypper`) contains several formatting errors: Starting at the description of the "install (in)" command various '+' and occasional '-' signs are spread in the text without any obvious reason. Later on (starting in the "-t, --type" option of "in") the man page contains whole passages incorrectly printed in bold or underlined. Looking at the spec file it seems this only happens when the man page was generated using Ruby's asciidoctor, pages created with asciidoc seem to look correct. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1044250] New: FileSystems.rb - undefined method `split' for nil:NilClass
by bugzilla_noreply＠novell.com 20 Apr '20

20 Apr '20

http://bugzilla.suse.com/show_bug.cgi?id=1044250 Bug ID: 1044250 Summary: FileSystems.rb - undefined method `split' for nil:NilClass Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: joyce.na(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 728882 --> http://bugzilla.suse.com/attachment.cgi?id=728882&action=edit y2logs issue: There is an error message when try to open "yast disk" Error Internal error. Please report a bug report with logs. Run save_y2logs to get complete logs. Details: undefined method `split' for nil:NilClass Caller: /usr/share/YaST2/modules/FileSystems.rb:2114:in `btrfs_subvol_name_for' reproduce steps: 1.create 2 new partitions /dev/sda7 and /dev/sda8 2.mkfs.btrfs /dev/sda7 /dev/sda8 3.mount /dev/sda7 /mnt/backup 4.mount /dev/sda8 /mnt 5.yast disk Note:Ext4 and XFS do not have this issue,only btrfs failed. -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1013047] New: Autoyast profile does not validate
by bugzilla_noreply＠novell.com 20 Apr '20

20 Apr '20

http://bugzilla.suse.com/show_bug.cgi?id=1013047 Bug ID: 1013047 Summary: Autoyast profile does not validate Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: AutoYaST Assignee: autoyast-maintainers(a)suse.de Reporter: mkravec(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 704429 --> http://bugzilla.suse.com/attachment.cgi?id=704429&action=edit autoinst.xml Generated profile fails to validate with: xmllint: - Element profile has extra content: add-on jing: - element "copy_on_write" not allowed here; expected the element end-tag or text - element "path" not allowed here; expected the element end-tag or text OpenQA link: http://dhcp91.suse.cz/tests/3181#step/yast2_clone_system/7 -- You are receiving this mail because: You are on the CC list for the bug.

1 40

[Bug 1079400] New: 389-ds upgrade to 1.3.4 breaks existing LDAP setups
by bugzilla_noreply＠novell.com 17 Apr '20

17 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1079400 Bug ID: 1079400 Summary: 389-ds upgrade to 1.3.4 breaks existing LDAP setups Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: lbeltrame(a)kde.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I used to have a working LDAP setup with 389-ds and Tumbleweed, but once 1.3.4 hit the distribution the server refuses to start: - /etc/dirsrv/slapd-palver/dse.ldif[04/Feb/2018:20:41:46.884975571 +0100] - ERR - slapd_bootstrap_config - The default password storage scheme could not be read or was not found in the file /etc/dirsrv/slapd-palver/dse.ldif. It is mandatory. There were no changes in dse.ldif across version upgrades. Did anything change with regards to configuration (note: I wasn't able to find anything relevant in the 389-ds documentation)? -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1116552] New: Packaggin Issues related to openSUSE:Factory/-ds
by bugzilla_noreply＠novell.com 17 Apr '20

17 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1116552 Bug ID: 1116552 Summary: Packaggin Issues related to openSUSE:Factory/-ds 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: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- A couple issues occured in the packaging for 389-ds: * The build fails since the permissions have been added to the permissions package: >[ 311s] package: 389-ds >[ 311s] /usr/bin/chkstat modified files that are not properly handled! >[ 311s] this will break rpm -V, ask ro for details. >[ 311s] diff for both runs of rpm -V: >[ 311s] +.M....G.P /usr/sbin/ns-slapd * The package 389-ds produces a binary called libsvrcore0 - which is also produced by the source package svrcore: where it, judged by the name, belongs to. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1125775] New: firewalld missing python firewall
by bugzilla_noreply＠novell.com 16 Apr '20

16 Apr '20

http://bugzilla.suse.com/show_bug.cgi?id=1125775 Bug ID: 1125775 Summary: firewalld missing python firewall Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: pgajdos(a)suse.com Reporter: ohering(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Tumbleweed 20181130-0 -> 20190214-0 firewalld 0.6.3-1.1 -> 0.6.3-2.2 apache2 2.4.37-2.1 -> 2.4.38-1.1 (3856/5676) Installing: apache2-2.4.38-1.1.x86_64 .[done] Additional rpm output: Updating /etc/sysconfig/apache2 ... Running in chroot, ignoring request: daemon-reload Traceback (most recent call last): File "/usr/bin/firewall-cmd", line 31, in <module> from firewall.client import FirewallClient, FirewallClientIPSetSettings, \ ModuleNotFoundError: No module named 'firewall' Running in chroot, ignoring request: daemon-reload Requesting apache restart (all instances) Might be just a missing or incomplete Requires(pre) in apache2 or firewalld. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 976102] New: JavaFX/OpenJFX is not yet packaged
by bugzilla_noreply＠novell.com 16 Apr '20

16 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=976102 Bug ID: 976102 Summary: JavaFX/OpenJFX is not yet packaged Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Java Assignee: bnc-team-java(a)forge.provo.novell.com Reporter: matthias(a)mailaender.name QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I was trying to compile OpenChrom according to https://wiki.openchrom.net/index.php/Development using the Eclipse IDE. A major pain was the JavaFX dependency, which just doesn't exist in openSUSE at all. Purging SUSE's OpenJDK and installing Oracle Java was ultimately the only solution. For Fedora/Mageia and Debian/Ubuntu you can simply install openjfx packages from the repositories. I tried packaging it myself: https://build.opensuse.org/package/show/home:Mailaender:branches:Java:packa… but pretty much failed early as openSUSE is missing the gradle and the whole xmvn infrastructure so dependencies can't get packaged and resolved. I would like to fill this gap for SUSE to scratch my own itch, but I need some help here. -- You are receiving this mail because: You are on the CC list for the bug.

1 22

[Bug 963323] New: Making Maven officially available in openSUSE
by bugzilla_noreply＠novell.com 16 Apr '20

16 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=963323 Bug ID: 963323 Summary: Making Maven officially available in openSUSE Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Java Assignee: bnc-team-java(a)forge.provo.novell.com Reporter: p.drouand(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is a kind of metabug to track progress made by people actually involved in Maven packaging. We will update this bug progressively according to progresses done themselves. -- You are receiving this mail because: You are on the CC list for the bug.

1 24

[Bug 1120178] New: gnome-shell(gdm?) crashes with gnome-shell.9669 maintenance update
by bugzilla_noreply＠novell.com 15 Apr '20

15 Apr '20

http://bugzilla.suse.com/show_bug.cgi?id=1120178 Bug ID: 1120178 Summary: gnome-shell(gdm?) crashes with gnome-shell.9669 maintenance update Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: mlin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- With gnome-shell maintenance update(gnome-shell.9669)[1], fails booting to gnome, looks like gnome-shell or gdm crashed[2]. [1] https://build.opensuse.org/request/show/659421 [2] https://openqa.opensuse.org/tests/818553#step/first_boot/21 -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1131752] New: X server dies after resuming from hibernation
by bugzilla_noreply＠novell.com 15 Apr '20

15 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 Bug ID: 1131752 Summary: X server dies after resuming from hibernation Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: opensuse(a)mike.franken.de QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- Sometimes, but not always my X server dies after the system has successfully resumed from hibernation. It is restarted then, so I can login, but of course my previous session is lost. It *seems* to happen only, when the notebook is connected to the Thunderbolt dock (see below) and the external monitor is used. Xorg.log.old contains: ------------------------< snip snip snip >----------------------------- ... [ 65043.707] (II) AIGLX: Suspending AIGLX clients for VT switch [ 65050.192] (II) AIGLX: Resuming AIGLX clients after VT switch [ 65050.212] (EE) modeset(0): failed to set mode: Invalid argument [ 65050.212] (EE) Fatal server error: [ 65050.212] (EE) EnterVT failed for screen 0 [ 65050.212] (EE) [ 65050.212] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 65050.212] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 65050.212] (EE) [ 65050.216] (II) AIGLX: Suspending AIGLX clients for VT switch [ 65050.266] (EE) Server terminated with error (1). Closing log file. ------------------------< snip snip snip >----------------------------- journal says: ------------------------< snip snip snip >----------------------------- org.a11y.Bus[2632]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" org.a11y.Bus[2632]: after 23769 requests (23769 known processed) with 0 events remaining. ------------------------< snip snip snip >----------------------------- - openSUSE Tumbleweed with latest snapshot - Linux thunder 5.0.3-1-default #1 SMP Fri Mar 22 17:30:35 UTC 2019 (2a31831) x86_64 x86_64 x86_64 GNU/Linux - notebook Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.8.1 02/14/2019 - Thunderbolt docking station CalDigit TS3 Plus - my monitor is connected to the display port connector of this docking station -- You are receiving this mail because: You are on the CC list for the bug.

1 41

[Bug 1075879] New: Anki desktop application doesn't work
by bugzilla_noreply＠novell.com 12 Apr '20

12 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1075879 Bug ID: 1075879 Summary: Anki desktop application doesn't work Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: andranik(a)openmailbox.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is the issue after anki command: user@linux:~> anki Traceback (most recent call last): File "/usr/bin/anki", line 5, in <module> import aqt File "/usr/share/anki/aqt/__init__.py", line 12, in <module> from aqt.qt import * File "/usr/share/anki/aqt/qt.py", line 22, in <module> from PyQt4.QtWebKit import QWebPage, QWebView, QWebSettings ImportError: No module named QtWebKit Here are the depends on my system (I use Education repo to install anki): Installed Version Version: 2.0.47-1.4 Provides: application() appdata() appdata(anki.appdata.xml) application(anki.desktop) mimehandler(application/x-anki) mimehandler(application/x-apkg) anki = 2.0.47-1.4 Prerequires: /bin/sh /bin/sh Requires: /usr/bin/env python-qt4 python-sip python-httplib2 python-beautifulsoup python-send2trash rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(PayloadIsXz) <= 5.2-1 /bin/sh /bin/sh Suggests: sox MPlayer lame These packages and libs are not found in my repos: python-httplib2 python-send2trash rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(PayloadIsXz) <= 5.2-1 libqt4-x11,libQtWebKit4, python2-qt4 are installed on my system. Also there was upgrade info on Anki website that possibly can explain this issue https://apps.ankiweb.net/docs/beta.html -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1082814] New: VUL-0: CVE-2012-6709 elinks: Does not properly verify SSL certificates
by bugzilla_noreply＠novell.com 12 Apr '20

12 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1082814 Bug ID: 1082814 Summary: VUL-0: CVE-2012-6709 elinks: Does not properly verify SSL certificates Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other URL: https://smash.suse.de/issue/200756/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: puzel(a)suse.com Reporter: jsegitz(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- >From Vincent Danen A Debian bug report [1] indicated that Links does not properly verify SSL certificates. If you visit a web site with an expired SSL certificate, Links will only display "SSL error" without any indication as to what the error was. This, in and of itself, is not a flaw however when testing, I found that when you go to a site with a valid SSL certificate, but for a different hostname (for example, if you go to https://alias.foo.com which might be a CNAME or a proxy for https://foo.com) Links will connect without any errors or warnings. Doing the same in a browser like Google Chrome, however, reports "You attempted to reach alias.foo.com, but instead you actually reached a server identifying itself as foo.com." and allows you to either proceed or not, before loading the site. elinks https://wrong.host.badssl.com/ opens without warning References: [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694658 https://bugzilla.redhat.com/show_bug.cgi?id=881399 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2012-6709 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694658 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1101237] New: ImageWriter not displayed in German language
by bugzilla_noreply＠novell.com 12 Apr '20

12 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1101237 Bug ID: 1101237 Summary: ImageWriter not displayed in German language Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Enhancement Priority: P5 - None Component: Translations Assignee: ke(a)suse.com Reporter: mail(a)maikwagner.de QA Contact: ke(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0 Build Identifier: Hello everyone, for a fresh installation of Tumbleweed I installed ImageWriter but it's not displayed in German language. Version number is 1.10 Reproducible: Always Steps to Reproduce: 1. zypper install imagewriter 2. starting SUSE Studio ImageWriter from Systemwerkzeuge - SUSE Studio ImageWriter 3. also happens when launching from the command line Actual Results: User interface is shown in English language Expected Results: Display everything in German -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1046277] New: TUMBLEWEED texlive is broken in tumbleweed 20170626
by bugzilla_noreply＠novell.com 11 Apr '20

11 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1046277 Bug ID: 1046277 Summary: TUMBLEWEED texlive is broken in tumbleweed 20170626 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: g.hughsong(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since Tumbleweed snapshot 20172025, texlive appears to be broken. When pdflatex is run, I get ==================== This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/TeX Live for SUSE Linux) (preloaded format=pdflatex) restricted \write18 enabled. ---! /var/lib/texmf/web2c/pdftex/pdflatex.fmt made by different executable version (Fatal format file error; I'm stymied) ==================== On "latex" command, I get almost exactly the same error message. Thanks for your attention. -- You are receiving this mail because: You are on the CC list for the bug.

1 32

[Bug 1123741] New: GIMP does not start
by bugzilla_noreply＠novell.com 11 Apr '20

11 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1123741 Bug ID: 1123741 Summary: GIMP does not start Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Minor Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: saubernix(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After the upgrade from Leap 42.3 to Leap 15.0, the GIMP does not work anymore. Started from the menu (or the Alt+F2 commandline) almost nothing happens. A symbol appears in the taskbar for some seconds and thatŽs it. Trying the same from the command line shows the following (sorry for it is in German!): GEGL-Message: Fehler beim Laden von Modul »/usr/lib64/gegl-0.3/exr-load.so«: /usr/lib64/libIlmImf-2_2.so.23: undefined symbol: _ZN7Iex_2_27BaseExc6assignERNSt7__cxx1118basic_stringstreamIcSt11char_traitsIcESaIcEEE Speicherzugriffsfehler (Speicherabzug geschrieben) Must give in IŽm not an expert, but can supply any helpful information. Thanks for your help! Ralf -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1131952] New: VUL-1: CVE-2019-11025: cacti: an XSS vulnerability exists due to missing escape before printing the SNMP community string
by bugzilla_noreply＠novell.com 11 Apr '20

11 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1131952 Bug ID: 1131952 Summary: VUL-1: CVE-2019-11025: cacti: an XSS vulnerability exists due to missing escape before printing the SNMP community string Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other URL: https://smash.suse.de/issue/229228/ OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Security Assignee: liedke(a)rz.uni-mannheim.de Reporter: atoptsoglou(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2019-11025 In clearFilter() in utilities.php in Cacti before 1.2.3, no escaping occurs before printing out the value of the SNMP community string (SNMP Options) in the View poller cache, leading to XSS. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-11025 http://www.cvedetails.com/cve/CVE-2019-11025/ http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11025 https://github.com/Cacti/cacti/issues/2581 https://github.com/Cacti/cacti/compare/6ea486a...99995bb -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1122535] New: VUL-1: CVE-2009-4112: cacti: Privilege escalation under certain conditions
by bugzilla_noreply＠novell.com 11 Apr '20

11 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1122535 Bug ID: 1122535 Summary: VUL-1: CVE-2009-4112: cacti: Privilege escalation under certain conditions Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other URL: https://smash.suse.de/issue/41118/ OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Security Assignee: liedke(a)rz.uni-mannheim.de Reporter: astieger(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- >From https://github.com/Cacti/cacti/issues/1072 " CVE-2009-4112 still exists (after 8 years) #1072 " This re-occurrence is now about creating new data input methods rather than modifying existing ones. Mitigation in upstream 1.2.0. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1123699] New: libvirt does not start default network automatically
by bugzilla_noreply＠novell.com 11 Apr '20

11 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1123699 Bug ID: 1123699 Summary: libvirt does not start default network automatically Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: agraul(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 795623 --> http://bugzilla.opensuse.org/attachment.cgi?id=795623&action=edit libvirt network default not enabled On a recent TW installation (Snapshot 20190125) that uses wicked (server role), the default network was not started automatically. Reproduction: 1. Install yast2-vm 2. Using yast2 virtualization: Install virtualization stack (xen server + tools, kvm server + tools, libvirt-lxc) and enable the virtualization bridge as the yast popup proposes 3. Start the libvirtd systemd service via `systemctl start libvirtd.service` 4. `virsh net-info default` shows that the 'default' network is not active. Expected result: The default network is started when libvirtd is started via systemctl, which allows commands like `virt-install` to succeed. See additional discussion: https://progress.opensuse.org/issues/41093 -- You are receiving this mail because: You are on the CC list for the bug.

1 31

[Bug 1123118] New: rubygem-activesupport-5.2 couldn't be installed due to lack of tzinfo:1 dependency
by bugzilla_noreply＠novell.com 11 Apr '20

11 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1123118 Bug ID: 1123118 Summary: rubygem-activesupport-5.2 couldn't be installed due to lack of tzinfo:1 dependency Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Ruby Assignee: ruby-devel(a)suse.de Reporter: w01dnick(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Snapshot 20190121 introduced update rubygem-tzinfo (1.2.5 -> 2.0.0) which lead to uninstallable rubygem-activesupport-5.2 and as dependency rubygem-rails-5.2: ``` Problem: nothing provides rubygem(ruby:2.5.0:tzinfo:1) >= 1.1 needed by ruby2.5-rubygem-activesupport-5.2-5.2.2-1.1.x86_64 ``` rubygem-activesupport-5.2 still needs tzinfo:1 but tzinfo now provides tzinfo:2, is it possible to return tzinfo 1.2.5 as rubygem-tzinfo-1 (like currently present rubygem-tzinfo-0)? -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 911286] New: mc/midnight commander lost shell/fish support
by bugzilla_noreply＠novell.com 10 Apr '20

10 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=911286 Bug ID: 911286 Summary: mc/midnight commander lost shell/fish support Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: richlv(a)nakts.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- this is a recent regression. midnight commander/mc after a recent upgrade has lost fish/"shell link" support. upstream report suggests that it should be built with fish support : https://www.midnight-commander.org/ticket/3294 sftp support in mc does not use ssh keys, thus it is not a proper replacement for fish/shell link support. -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1124066] New: KDE LiveCD provides a lot of Joe's Own Editor entries in application menu
by bugzilla_noreply＠novell.com 09 Apr '20

09 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1124066 Bug ID: 1124066 Summary: KDE LiveCD provides a lot of Joe's Own Editor entries in application menu Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Live Medium Assignee: dimstar(a)opensuse.org Reporter: opensuse.lietuviu.kalba(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 795860 --> http://bugzilla.opensuse.org/attachment.cgi?id=795860&action=edit menu Do we really need so much (4) Joe's Own Editor entries in application menu? See attached image from openSUSE-Tumbleweed-KDE-Live-i686-Snapshot20190126-Media.iso -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1104331] New: OSD Segmentation fault in thread_name:safe_timer
by bugzilla_noreply＠novell.com 08 Apr '20

08 Apr '20

http://bugzilla.suse.com/show_bug.cgi?id=1104331 Bug ID: 1104331 Summary: OSD Segmentation fault in thread_name:safe_timer Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: eugen.block(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- We're running a Ceph Luminous Cluster on Leap 42.3: ceph1:~ # rpm -qi ceph-common Name : ceph-common Version : 12.2.5+git.1524775272.5e7ea8cf03 Release : 2.1 Architecture: x86_64 Install Date: Thu May 24 15:14:56 2018 Group : System/Filesystems Size : 18064537 License : LGPL-2.1 and CC-BY-SA-3.0 and GPL-2.0 and BSL-1.0 and BSD-3-Clause and MIT Signature : RSA/SHA256, Fri Apr 27 01:48:28 2018, Key ID 98c97fe7324e6311 Source RPM : ceph-12.2.5+git.1524775272.5e7ea8cf03-2.1.src.rpm Build Date : Fri Apr 27 01:10:29 2018 Build Host : lamb72 Relocations : (not relocatable) Vendor : obs://build.opensuse.org/filesystems Since a couple of days we're suddenly experiencing random segfaults leading to failing OSDs. We didn't update any packages on our ceph servers, they ran stable until these segfaults. Sometimes the OSDs recover by themselves, sometimes a whole host goes down and leaves a degraded cluster. The description in [2] sounds exactly like our issue ([1] is a duplicate of [2]). I'll spare you the details since the upstream bug has lots of information. There seems to be a backport [3] for Luminous, but it's still in progress although the change has been reviewed. I just wanted to raise awareness for this issue since it impacts our production cluster that ran stable for months and we'd appreciate it if the updated packages would be available soon to fix this issue. Please let me know if any further information is needed. [1] https://tracker.ceph.com/issues/23431 [2] https://tracker.ceph.com/issues/23352 [3] https://tracker.ceph.com/issues/26871 -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1120941] New: [Build 20190103] openQA test fails in salt: Ping does not work on 32-bit rescue cd
by bugzilla_noreply＠novell.com 08 Apr '20

08 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1120941 Bug ID: 1120941 Summary: [Build 20190103] openQA test fails in salt: Ping does not work on 32-bit rescue cd Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/824549/modules/salt/ steps/22 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Salt Assignee: salt-maintainers(a)suse.de Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- openQA test in scenario opensuse-Tumbleweed-Rescue-CD-i686-rescue@32bit fails in [salt](https://openqa.opensuse.org/tests/824549/modules/salt/steps/22) Unfortunately there aren't any further logs available. Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?version=Tumbleweed&distri=… -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1136788] New: Sqlite oserror test fails on ppc64le
by bugzilla_noreply＠novell.com 06 Apr '20

06 Apr '20

http://bugzilla.suse.com/show_bug.cgi?id=1136788 Bug ID: 1136788 Summary: Sqlite oserror test fails on ppc64le Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: PowerPC OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: max(a)suse.com Reporter: jbrielmaier(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The oserror.test (https://repo.or.cz/sqlite.git/blob_plain/HEAD:/test/oserror.test) fails sometimes on ppc64le with the following error log: ! oserror-2.1.1 expected: [1 {disk I/O error}] ! oserror-2.1.1 got: [0 {}] ! oserror-2.1.2 expected: [^os_unix.c:\d+: $\d+$ unlink$.*test.db-wal$ - ] ! oserror-2.1.2 got: [] Time: oserror.test 194 ms The strange point here is, that it doesn't seem to fail always. So the build in server:database for openSUSE_Factory_PowerPC succeeds without this error. But when I built sqlite from server:database on a local ppc64le machine, it fails with exactly this test. I checked it on another Power machine and there the test also fails (one is POWER8, the other POWER9). In openSUSE:Factory:PowerPC/sqlite3 it fails in a different test (swarmvtab2.test). So I assume these failures are not connected. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 959025] New: mate-tweak completely broken
by bugzilla_noreply＠novell.com 05 Apr '20

05 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=959025 Bug ID: 959025 Summary: mate-tweak completely broken Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: sb56637(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- "/usr/lib/python2.7/site-packages/gi/overrides/Gtk.py:50: RuntimeWarning: You have imported the Gtk 2.0 module. Because Gtk 2.0 was not designed for use with introspection some of the interfaces and API will fail. As such this is not supported by the pygobject development team and we encourage you to port your app to Gtk 3 or greater. PyGTK is the recomended python module to use with Gtk 2.0" Possibly related reports: https://forum.antergos.com/topic/1898/mintmenu-is-broken-again/6 https://github.com/linuxmint/mintmenu/issues/130 https://bugs.launchpad.net/linuxmint/+bug/1261862 -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1089701] New: With kernel 4.16 webcam video is not working with Skype and Google Hangouts
by bugzilla_noreply＠novell.com 03 Apr '20

03 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1089701 Bug ID: 1089701 Summary: With kernel 4.16 webcam video is not working with Skype and Google Hangouts Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: tneo(a)gmx.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When I boot TW with kernel 4.16 the webcam video in both Skype and Google Hangouts don't have video support. Microphone works. The webcam is not broken as with eg. Ekiga I do have video. Booting kernel 4.15 gives the video output again, though other not relevant issues arise. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 597673] New: fetchmail: DoS in -v -v mode in multibyte
by bugzilla_noreply＠novell.com 02 Apr '20

02 Apr '20

http://bugzilla.novell.com/show_bug.cgi?id=597673 http://bugzilla.novell.com/show_bug.cgi?id=597673#c0 Summary: fetchmail: DoS in -v -v mode in multibyte Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security AssignedTo: puzel(a)novell.com ReportedBy: lnussel(a)novell.com QAContact: qa(a)suse.de CC: security-team(a)suse.de Found By: Other Blocker: --- Your friendly security team received the following report via oss-security. Please respond ASAP. The issue is public. Factory only sufficient ------------------------------------------------------------------------------ Date: Sun, 18 Apr 2010 18:58:30 +0200 From: "Matthias Andree" <matthias.andree(a)gmx.de> Subject: [oss-security] CVE request: fetchmail 4.6.3...6.3.16 DoS in -v -v mode in multibyte locales on invalid input Please assign a CVE id for the issue described below. (Best viewed in non-proportional font with 8 space tabs): Draft announcement: - DRAFT - XXX - DRAFT - fetchmail-SA-2010-02: Denial of service in debug mode w/ multichar locales Topics: Denial of service in debug output. Author: Matthias Andree Version: 0.1 XXX Announced: XXX Type: malloc() Buffer overrun with printable characters Impact: Denial of service. Danger: low CVE Name: CVE-2010-XXXX CVSSv2: XXX URL: http://www.fetchmail.info/fetchmail-SA-2010-02.txt Project URL: http://www.fetchmail.info/ Affects: fetchmail releases 4.6.3 up to and including 6.3.16 Not affected: fetchmail release 6.3.17 and newer Corrected: 2010-04-18 Git (XXX) 0. Release history ================== 2010-04-18 0.1 first draft (visible in SVN and through oss-security) XXX 1. Background ============= fetchmail is a software package to retrieve mail from remote POP2, POP3, IMAP, ETRN or ODMR servers and forward it to local SMTP, LMTP servers or message delivery agents. It supports SSL and TLS security layers through the OpenSSL library, if enabled at compile time and if also enabled at run time. 2. Problem description and Impact ================================= In debug mode (-v -v), fetchmail prints information that was obtained from the upstream server (POP3 UIDL lists) or from message headers retrieved from it. If printing such information fails, for instance because there are invalid multibyte character sequences in this information (message headers), fetchmail will misinterpret this condition, and believe that the buffer was too small, and reallocate a bigger one (with linearly increasing buffer size), and repeat, until the allocation fails. At that point, fetchmail will abort. Note that the "Affects:" line above may be inaccurate, and it may be that versions before 5.6.6 are actually unaffected. The author was unable to compile such old fetchmail versions to verify the existence of the bug. Given that other security issues are present in such versions, those should not be used, and the wider version range was listed as vulnerable to err towards the safe. 3. Solution =========== There are two alternatives, either of them by itself is sufficient: a. Apply the patch found in section B of this announcement to fetchmail 6.3.14 or newer, recompile and reinstall it. b. Install fetchmail 6.3.17 or newer after it will have become available. The fetchmail source code is always available from <http://developer.berlios.de/project/showfiles.php?group_id=1824>. 4. Workaround ============= Run fetchmail with at most one -v (--verbose) option. A. Copyright, License and Warranty ================================== (C) Copyright 2010 by Matthias Andree, <matthias.andree(a)gmx.de>. Some rights reserved. This work is licensed under the Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 Germany License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-nd/3.0/de/ or send a letter to Creative Commons 171 Second Street Suite 300 SAN FRANCISCO, CALIFORNIA 94105 USA THIS WORK IS PROVIDED FREE OF CHARGE AND WITHOUT ANY WARRANTIES. Use the information herein at your own risk. B. Patch to remedy the problem ============================== Note that when taking this from a GnuPG clearsigned file, the lines starting with a "-" character are prefixed by another "- " (dash + blank) combination. Either feed this file through GnuPG to strip them, or strip them manually. You may want to use the "-p1" flag to patch. Whitespace differences can usually be ignored by invoking "patch -l", so try this if the patch does not apply. diff --git a/rfc822.c b/rfc822.c index 6f2dbf3..dbcda32 100644 --- a/rfc822.c +++ b/rfc822.c @@ -25,6 +25,7 @@ MIT license. Compile with -DMAIN to build the demonstrator. #include <stdlib.h> #include "fetchmail.h" +#include "sdump.h" #ifndef MAIN #include "i18n.h" @@ -74,9 +75,10 @@ char *reply_hack( } #ifndef MAIN - if (outlevel >= O_DEBUG) - report_build(stdout, GT_("About to rewrite %.*s...\n"), - (int)BEFORE_EOL(buf), buf); + if (outlevel >= O_DEBUG) { + report_build(stdout, GT_("About to rewrite %s...\n"), (cp = sdump(buf, BEFORE_EOL(buf)))); + xfree(cp); + } /* make room to hack the address; buf must be malloced */ for (cp = buf; *cp; cp++) @@ -211,9 +213,12 @@ char *reply_hack( } #ifndef MAIN - if (outlevel >= O_DEBUG) - report_complete(stdout, GT_("...rewritten version is %.*s.\n"), - (int)BEFORE_EOL(buf), buf); + if (outlevel >= O_DEBUG) { + report_complete(stdout, GT_("...rewritten version is %s.\n"), + (cp = sdump(buf, BEFORE_EOL(buf)))); + xfree(cp) + } + #endif /* MAIN */ *length = strlen(buf); return(buf); diff --git a/uid.c b/uid.c index fdc6f5d..d813bee 100644 --- a/uid.c +++ b/uid.c @@ -20,6 +20,7 @@ #include "fetchmail.h" #include "i18n.h" +#include "sdump.h" /* * Machinery for handling UID lists live here. This is mainly to support @@ -260,8 +261,11 @@ void initialize_saved_lists(struct query *hostlist, const char *idfile) if (uidlcount) { report_build(stdout, GT_("Scratch list of UIDs:")); - for (idp = scratchlist; idp; idp = idp->next) - report_build(stdout, " %s", idp->id); + for (idp = scratchlist; idp; idp = idp->next) { + char *t = sdump(idp->id, strlen(idp->id)); + report_build(stdout, " %s", t); + free(t); + } if (!idp) report_build(stdout, GT_(" <empty>")); report_complete(stdout, "\n"); @@ -517,8 +521,11 @@ void uid_swap_lists(struct query *ctl) report_build(stdout, GT_("Merged UID list from %s:"), ctl->server.pollname); else report_build(stdout, GT_("New UID list from %s:"), ctl->server.pollname); - for (idp = dofastuidl ? ctl->oldsaved : ctl->newsaved; idp; idp = idp->next) - report_build(stdout, " %s = %d", idp->id, idp->val.status.mark); + for (idp = dofastuidl ? ctl->oldsaved : ctl->newsaved; idp; idp = idp->next) { + char *t = sdump(idp->id, strlen(idp->id)); + report_build(stdout, " %s = %d", t, idp->val.status.mark); + free(t); + } if (!idp) report_build(stdout, GT_(" <empty>")); report_complete(stdout, "\n"); @@ -567,8 +574,11 @@ void uid_discard_new_list(struct query *ctl) /* this is now a merged list! the mails which were seen in this * poll are marked here. */ report_build(stdout, GT_("Merged UID list from %s:"), ctl->server.pollname); - for (idp = ctl->oldsaved; idp; idp = idp->next) - report_build(stdout, " %s = %d", idp->id, idp->val.status.mark); + for (idp = ctl->oldsaved; idp; idp = idp->next) { + char *t = sdump(idp->id, strlen(idp->id)); + report_build(stdout, " %s = %d", t, idp->val.status.mark); + free(t); + } if (!idp) report_build(stdout, GT_(" <empty>")); report_complete(stdout, "\n"); -- Matthias Andree -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 4

[Bug 1136281] New: Cannot create user directory because /home is not a btrfs sub volume
by bugzilla_noreply＠novell.com 01 Apr '20

01 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1136281 Bug ID: 1136281 Summary: Cannot create user directory because /home is not a btrfs sub volume Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: j.r.hudson(a)virginmedia.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- When adding a new user, YaST says it cannot create a user directory because /home is not a btrfs sub volume. I still have /home on an XFS partition having done online upgrades from earlier versions. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 921570] New: after dist upgrade system boots to emergency mode
by bugzilla_noreply＠novell.com 01 Apr '20

01 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=921570 Bug ID: 921570 Summary: after dist upgrade system boots to emergency mode Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: steffen.hau(a)rz.uni-mannheim.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I've started upgrading systems from openSUSE 13.1 to 13.2. Virtual machines without special stuff like mdadm raid devices oder multipathed FC LUN's went fine. But systems (IBM HS22 Blades) with mdadm raid devices are booting to emergency mode. The systems have three raid 1 devices (swap, / and /srv or /home), swap and / are correctly assembled but the third md device is missing and it also does not appear in /proc/mdstat. Manually running "mdadm -A --scan" brings it up and "systemctl default" continues booting. To dig deeper into this issue, I've installed openSUSE 13.2 from scratch on a spare blade and here md2 is correctly assembled. This is the content of /etc/systemd/system/ of the upgraded system: /etc/systemd/system/dbus-org.opensuse.Network.AUTO4.service /etc/systemd/system/dbus-org.opensuse.Network.DHCP4.service /etc/systemd/system/dbus-org.opensuse.Network.DHCP6.service /etc/systemd/system/dbus-org.opensuse.Network.Nanny.service /etc/systemd/system/default.target /etc/systemd/system/default.target.wants/sysstat.service /etc/systemd/system/default.target.wants/systemd-readahead-collect.service /etc/systemd/system/default.target.wants/systemd-readahead-replay.service /etc/systemd/system/getty.target.wants/getty(a)tty1.service /etc/systemd/system/multi-user.target.wants/acpid.service /etc/systemd/system/multi-user.target.wants/apache2.service /etc/systemd/system/multi-user.target.wants/auditd.service /etc/systemd/system/multi-user.target.wants/cron.service /etc/systemd/system/multi-user.target.wants/dsmc.service /etc/systemd/system/multi-user.target.wants/irqbalance.service /etc/systemd/system/multi-user.target.wants/mcelog.service /etc/systemd/system/multi-user.target.wants/ntpd.service /etc/systemd/system/multi-user.target.wants/postfix.service /etc/systemd/system/multi-user.target.wants/remote-fs.target /etc/systemd/system/multi-user.target.wants/smartd.service /etc/systemd/system/multi-user.target.wants/sshd.service /etc/systemd/system/multi-user.target.wants/syslog-ng.service /etc/systemd/system/multi-user.target.wants/wicked.service /etc/systemd/system/network-online.target.wants/wicked.service /etc/systemd/system/network.service /etc/systemd/system/sysinit.target.wants/multipathd.service /etc/systemd/system/syslog.service /etc/systemd/system/system-update.target.wants/systemd-readahead-drop.service /etc/systemd/system/timers.target.wants/logrotate.timer /etc/systemd/system/wickedd.service.wants/wickedd-auto4.service /etc/systemd/system/wickedd.service.wants/wickedd-dhcp4.service /etc/systemd/system/wickedd.service.wants/wickedd-dhcp6.service /etc/systemd/system/wickedd.service.wants/wickedd-nanny.service /etc/systemd/system/wicked.service.wants/wickedd.service I've made the scratch system identical to the problematic system (identical installed packages, conf files in /etc, active systemd services, and so on) and it still assembles md2. I've no more ideas where to search for possible causes. Please let me know what kind of information I should provide in order to help you to find the cause. -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 911512] New: opensuse boots to terminal
by bugzilla_noreply＠novell.com 01 Apr '20

01 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=911512 Bug ID: 911512 Summary: opensuse boots to terminal Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: illumilore(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:34.0) Gecko/20100101 Firefox/34.0 Build Identifier: after an update, opensuse now boots to a terminal. trying to use the command startx gives the output that it cannot open /dev/tty0 no such file or directory. Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1136099] New: python-nbconvert fails test on 1-core VM
by bugzilla_noreply＠novell.com 30 Mar '20

30 Mar '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1136099 Bug ID: 1136099 Summary: python-nbconvert fails test on 1-core VM Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: toddrme2178(a)gmail.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: Development Blocker: --- While working on reproducible builds for openSUSE, I found that osc build --vm-type=kvm -j1 --noservice for python-nbconvert fails 1 test on a 1-core VM 1 failed, 251 passed, 32 skipped, 2 deselected, 59 warnings in 241.06 =================================== FAILURES ========================== ________________________ TestExecute.test_disable_stdin ______________ self = <nbconvert.preprocessors.tests.test_execute.TestExecute testMethod=test_ disable_stdin> def test_disable_stdin(self): """Test disabling standard input""" filename = os.path.join(current_dir, 'files', 'Disable Stdin.ipynb') res = self.build_resources() res['metadata']['path'] = os.path.dirname(filename) > input_nb, output_nb = self.run_notebook(filename, dict(allow_errors=True), res) If you cannot debug this yourself, please work with upstream. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 690867] New: Consider to DNSSEC sign the opensuse.org domain
by bugzilla_noreply＠novell.com 28 Mar '20

28 Mar '20

https://bugzilla.novell.com/show_bug.cgi?id=690867 https://bugzilla.novell.com/show_bug.cgi?id=690867#c0 Summary: Consider to DNSSEC sign the opensuse.org domain Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Infrastructure AssignedTo: mrueckert(a)novell.com ReportedBy: burnus(a)gmx.de QAContact: lrupp(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:2.0) Gecko/20100101 Firefox/4.0 Currently, the opensuse.org domain is not secured using DNSSEC: http://dnsviz.net/d/opensuse.org/dnssec/ It would be useful, if it could be signed. Other domains are already signed such as: - Fedora: http://dnsviz.net/d/fedoraproject.org/dnssec/ - Mozilla: http://dnsviz.net/d/wiki.mozilla.org/dnssec/ (Side remark: In Firefox, the plugin http://www.dnssec-validator.cz/ can be used to see the DNSSEC status.) Reproducible: Always -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 11

[Bug 1093163] New: mdadm: using service templates in preun is wrong:
by bugzilla_noreply＠novell.com 27 Mar '20

27 Mar '20

http://bugzilla.suse.com/show_bug.cgi?id=1093163 Bug ID: 1093163 Summary: mdadm: using service templates in preun is wrong: 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: ro(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- in mdadm.spec: %preun %service_del_preun %services mdmon@.service mdadm-last-resort@.service mdadm-grow-continue@.service leads to: # rpm -e mdadm --nodeps Failed to stop mdmon@.service: Unit name mdmon@.service is missing the instance name. See system logs and 'systemctl status mdmon@.service' for details. Failed to stop mdadm-last-resort@.service: Unit name mdadm-last-resort@.service is missing the instance name. See system logs and 'systemctl status mdadm-last-resort@.service' for details. Failed to stop mdadm-grow-continue@.service: Unit name mdadm-grow-continue@.service is missing the instance name. See system logs and 'systemctl status mdadm-grow-continue@.service' for details. Failed to get load state of mdmon@.service: Unit name mdmon@.service is neither a valid invocation ID nor unit name. Failed to get load state of mdadm-last-resort@.service: Unit name mdadm-last-resort@.service is neither a valid invocation ID nor unit name. Failed to get load state of mdadm-grow-continue@.service: Unit name mdadm-grow-continue@.service is neither a valid invocation ID nor unit name. a service template file (foo@.service) can not be used with the %service_add/del macros. -- You are receiving this mail because: You are on the CC list for the bug.

1 3