November 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1062068] New: X server should exit anymore when logind (v234) is restarted
by bugzilla_noreply＠novell.com 26 Feb '20

26 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1062068 Bug ID: 1062068 Summary: X server should exit anymore when logind (v234) is restarted 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: fbui(a)suse.com QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- Previously, logind didn't fully support restarting as the file descriptors of the session devices shared with the X server weren't saved. Due to this limitation a workaround was added in the X server [1] so the server exits as soon as it detects logind was stopped or restarted. However since v234, logind saves/reloads the fds before/after restarting so the revocation logic continue to work properly. Therefore the workaround [1] mentioned above is no more needed. However it's still not clear what should be done if logind is stopped completely. It's being discussed here [2]. This bug was opened so this issue is not lost on our side. [1] https://cgit.freedesktop.org/xorg/xserver/commit/?id=dc48bd653c7e1013e2d69e… [2] https://github.com/systemd/systemd/pull/5600#issuecomment-328023750 -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1051848] New: server:mail/cyrus-imapd: proxy segfault after upgrade to 2.4.19-149.1
by bugzilla_noreply＠novell.com 26 Feb '20

26 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1051848 Bug ID: 1051848 Summary: server:mail/cyrus-imapd: proxy segfault after upgrade to 2.4.19-149.1 Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: SLES 11 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: opensuse-communityscreening(a)forge.provo.novell.com Reporter: wullinger(a)rz.uni-kiel.de QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- We use cyrus imapd 2.4 in a proxy configuration for multiple mailbox storage servers. Since upgrading to 2.4.19-149.1, the frontend proxies (and only those) experience frequent segfaults of pop3d, proxyd, timsieved, and lmptproxyd: Aug 2 06:16:31 frontend3 kernel: [488770.024881] pop3d[XXXX]: segfault at 7f42ef735738 ip 00007f42ef546ca3 sp 00007ffdd7a45970 error 4 in ld-2.11.3.so[7f42ef539000+1f000] The problems disappears after downgrading back to cyrus-imapd-2.4.19-146.1. After such a crash, the BDB environment is often reported as needing recovery (we only use skiplist DBs, but BDB gets initialized nonetheless) As far as we can tell, there's no interruption of service associated with these crashes. For example, for lmtpproxyd, the problem seems to appear after the final QUIT, when the process is about to exit, anyway: write(13, "QUIT\r\n", 6) = 6 rt_sigprocmask(SIG_BLOCK, [INT QUIT ALRM TERM CHLD], [], 8) = 0 pselect6(14, [13], NULL, NULL, {229, 0}, {[], 8}) = 1 (in [13], left {228, 999487532}) rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 read(13, "221 2.0.0 bye\r\n", 4096) = 15 rt_sigprocmask(SIG_BLOCK, [INT QUIT ALRM TERM CHLD], [], 8) = 0 pselect6(14, [13], NULL, NULL, {0, 0}, {[], 8}) = 1 (in [13], left {0, 0}) rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 read(13, "", 4096) = 0 shutdown(13, 0 /* receive */) = 0 close(13) = 0 munmap(0x7f87be793000, 38608896) = 0 close(8) = 0 munmap(0x7f87c693f000, 40960) = 0 munmap(0x7f87c6873000, 98304) = 0 munmap(0x7f87c1aca000, 28131328) = 0 munmap(0x7f87c688b000, 671744) = 0 --- SIGSEGV (Segmentation fault) @ 0 (0) --- A slight hunch seems to suggest that there's a memory corruption issue that gets triggered during the final close of the BDB environment. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 917728] New: Obsolete/deprecated config option still enabled
by bugzilla_noreply＠novell.com 23 Feb '20

23 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=917728 Bug ID: 917728 Summary: Obsolete/deprecated config option still enabled Classification: openSUSE Product: openSUSE Factory Version: 201502* Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: zaitor(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi Kernel people. Just installed the spiffy new 3.19 kernel from Kernel:stable, and when going through journald logs to see if there was something new and exciting I came over these warnings that I've seen for ages, but never cared for since it seem to do no harm. linux-ial4:~ # uname -r 3.19.0-1.g8a7d5f9-desktop linux-ial4:~ # journalctl -b | grep CONFIG_ACPI_PROCFS_POWER feb. 13 00:27:50 linux-ial4 kernel: ACPI: Deprecated procfs I/F for battery is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared feb. 13 00:27:50 linux-ial4 kernel: ACPI: Deprecated procfs I/F for battery is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared feb. 13 00:27:50 linux-ial4 kernel: ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared linux-ial4:~ # ---- But today I took the time to google it, and found this bug from Arch https://bugs.archlinux.org/task/25845 Snip from bug ACPI: Deprecated procfs I/F for battery is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared This was scheduled for removal in 2.6.39, but is still there. I suggest trying to disable it for 3.1, if for nothing else than to discover what problems this might cause so the appropriate bug reports can be filed. >From Documentation/feature-removal-schedule.txt: What: CONFIG_ACPI_PROCFS_POWER When: 2.6.39 Why: sysfs I/F for ACPI power devices, including AC and Battery, has been working in upstream kernel since 2.6.24, Sep 2007. In 2.6.37, we make the sysfs I/F always built in and this option disabled by default. Remove this option and the ACPI power procfs interface in 2.6.39. Who: Zhang Rui <rui.zhang(a)intel.com> ---- Short story this was disabled on Arch back in 2011 Could we do this for openSUSE too? -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 966255] New: System does not boot
by bugzilla_noreply＠novell.com 09 Feb '20

09 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=966255 Bug ID: 966255 Summary: System does not boot Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: rjschwei(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- kernel 4.4.0.3 Has encrypted user partition. Hangs at Ignoring BGRT: Invalid version 0 (expected 1) This appears to happen right before the point where I would expect to enter my passphrase. -- You are receiving this mail because: You are on the CC list for the bug.

1 34

[Bug 1068707] New: bcache broken on s390x
by bugzilla_noreply＠novell.com 08 Feb '20

08 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1068707 Bug ID: 1068707 Summary: bcache broken on s390x Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: ro(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- trying to repeat on s390x what worked on aarch64 ... OBS_WORKER_DISK=/dev/mapper/3600a098051764b2d515d436d66416b4f wipefs -f -a $OBS_WORKER_DISK modprobe zram num_devices=1 modprobe bcache echo 8G > /sys/block/zram0/disksize wipefs -f -a /dev/zram0 make-bcache --wipe-bcache --block 4k --bucket 2M -B $OBS_WORKER_DISK -C /dev/zram0 # up to here it seemed to work, but: echo /dev/zram0 > /sys/fs/bcache/register -bash: echo: write error: Invalid argument in dmesg: [1256250.924470] zram: Added device: zram0 [1256258.363017] zram0: detected capacity change from 0 to 8589934592 [1256269.146000] bcache: register_bcache() error opening /dev/dm-2: Not a bcache superblock [1256275.462897] bcache: register_bcache() error opening /dev/zram0: Not a bcache superblock so the written superblock is not recognized ... endianess issue ? -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1052140] New: NetworkManager dispatcher script "nfs" is mounting nfs shares from fstab with option "noauto"
by bugzilla_noreply＠novell.com 01 Feb '20

01 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1052140 Bug ID: 1052140 Summary: NetworkManager dispatcher script "nfs" is mounting nfs shares from fstab with option "noauto" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The NetworkManager dispatcher script "nfs" is mounting nfs shares from fstab, which have set option "noauto". In my environment this is a good thing, but it is not the expected behaviour. Perhaps we could have a new fstab option like "x-nm.mount" for nfs shares to explicitly control this behaviour? The reason for experimenting with fstab options for nfs shares is the really strange "cooperation" of systemd and NetworkManager. Having the "auto" option set and nfs.service is active, systemd tries to mount the shares on boot, before network is available. This gives lots of errors in the log, although NetworkManager succeeds in mounting the share, when running the dispatcher script. With "auto" in fstab and a deactivated nfs.service neither systemd nor NetworkManager are trying to mount nfs shares. With "noauto" in fstab and an activated nfs.service systemd ignores the shares, but NetworkManager's nfs dispatcher is mounting them nevertheless. I tried x-systemd.automount, too. This worked generally, but after a hibernate/resume cycle all nfs shares were inaccessible. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1069396] New: sddm cannot be updated
by bugzilla_noreply＠novell.com 29 Jan '20

29 Jan '20

http://bugzilla.suse.com/show_bug.cgi?id=1069396 Bug ID: 1069396 Summary: sddm cannot be updated Classification: openSUSE Product: openSUSE Backports Version: SLE-12-SP3 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Packages Assignee: packagehub-bugs(a)suse.com Reporter: kukuk(a)suse.com QA Contact: packagehub-bugs(a)suse.com Found By: --- Blocker: --- If you try to update to the latest sddm version: Problem: nothing provides sddm-theme-openSUSE needed by sddm-branding-openSUSE-0.14.0-2.1.x86_64 Solution 1: deinstallation of sddm-branding-SLE-0.13.0-5.1.x86_64 Solution 2: do not install sddm-0.14.0-2.1.x86_64 Solution 3: break sddm-branding-openSUSE-0.14.0-2.1.x86_64 by ignoring some of its dependencies Reproduceable on SLES12 SP2 and SLES12 SP3. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1049825] New: zypper bash completion expands non-existing options
by bugzilla_noreply＠novell.com 09 Jan '20

09 Jan '20

http://bugzilla.suse.com/show_bug.cgi?id=1049825 Bug ID: 1049825 Summary: zypper bash completion expands non-existing options Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)forge.provo.novell.com Reporter: astieger(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- There seems to be a bug in the script that extracts available options in zypper. It expands to "*" and "If" $ zypper search [TAB][TAB] * --file-list --name --repo --suggests --case-sensitive --installed-only --not-installed-only --requires --type --conflicts --match-exact --obsoletes --search-descriptions If --details --match-substrings --provides --sort-by-name --details, --match-words --recommends --sort-by-repo This is actually from last two lines of the zypper help output: # zypper help search > -v, --verbose Like --details, with additional information where the > search has matched (useful for search in dependencies). > > * and ? wildcards can also be used within search strings. > If a search string is enclosed in '/', it's interpreted as a regular expression. -- You are receiving this mail because: You are on the CC list for the bug.

1 31

[Bug 1023732] New: openSUSE:Factory/golang-org-x-net fails to build
by bugzilla_noreply＠novell.com 08 Jan '20

08 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1023732 Bug ID: 1023732 Summary: openSUSE:Factory/golang-org-x-net fails to build 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: --- The package golang-org-x-net fails to build in openSUSE:Factory. Earlier notifications by email to the bugowner and Maintainer have remained without reaction / fix. If the package is not being fixed within 2 weeks, it will be scheduled for removal from Tumbleweed -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1052970] New: suse-xsl-stylesheets depends on aspell
by bugzilla_noreply＠novell.com 07 Jan '20

07 Jan '20

http://bugzilla.suse.com/show_bug.cgi?id=1052970 Bug ID: 1052970 Summary: suse-xsl-stylesheets depends on aspell 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: pgajdos(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Our management would like to remove aspell from the distro (fate#323578). We need to ensure it is not dependency of any package in Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

1 20