May 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1109367] New: Qt5 documentation packages are incomplete
by bugzilla_noreply＠novell.com 22 May '21

22 May '21

http://bugzilla.suse.com/show_bug.cgi?id=1109367 Bug ID: 1109367 Summary: Qt5 documentation packages are incomplete Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: fvogt(a)suse.com Reporter: lpechacek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Qt class documentation is incomplete. Help function in Creator does not provide information on Qt classes. For some reason these files are missing from the libqt5-qtdoc* packages. For example compare the contents of file:///usr/share/doc/packages/qt5/qtserialport/qtserialport-module.html# and http://doc.qt.io/qt-5/qtserialport-module.html In the on-disk file there is Classes section missing. Installing packages from KDE:Qt:5.11 OBS project fixes the problem. -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 921577] New: doxygen build failure for Power8 because double free or corruption
by bugzilla_noreply＠novell.com 21 May '21

21 May '21

http://bugzilla.suse.com/show_bug.cgi?id=921577 Bug ID: 921577 Summary: doxygen build failure for Power8 because double free or corruption Classification: openSUSE Product: openSUSE Factory Version: 201502* Hardware: PowerPC-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: normand(a)linux.vnet.ibm.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- doxygen build failure for Power8 because double free or corruption === ... [ 241s] Generating docs for compound B/home/abuild/rpmbuild/BUILD/doxygen-1.8.9.1/vhdlparser/TokenManager.h:19: warning: Unsupported xml/html tag <EOF> found [ 248s] *** Error in `./bin/doxygen': double free or corruption (fasttop): 0x000001001077bcf0 *** [ 248s] ======= Backtrace: ========= [ 248s] /lib64/libc.so.6(+0x836c0)[0x3fffa7ec36c0] [ 248s] /lib64/libc.so.6(+0x8ba84)[0x3fffa7ecba84] [ 248s] /lib64/libc.so.6(+0x8cadc)[0x3fffa7eccadc] [ 248s] /lib64/libc.so.6(cfree+0xd0)[0x3fffa7ed0a30] [ 248s] /usr/lib64/libstdc++.so.6(_ZdlPv+0x20)[0x3fffa819ce10] [ 248s] ./bin/doxygen[0x106620e4] [ 248s] ./bin/doxygen[0x1053ba84] [ 248s] ./bin/doxygen[0x1053bb18] [ 248s] ./bin/doxygen[0x106a0a44] [ 248s] /lib64/libpthread.so.0(+0x9454)[0x3fffa8299454] [ 248s] /lib64/libc.so.6(clone+0xe4)[0x3fffa7f4e0c4] ... === detailed log in doxygen_opensuse_ppc64le_failure.log attachment -- You are receiving this mail because: You are on the CC list for the bug.

2 42

[Bug 1107187] New: kpartx -l leaves a loop device behind
by bugzilla_noreply＠novell.com 19 May '21

19 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1107187 Bug ID: 1107187 Summary: kpartx -l leaves a loop device behind Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: seroton10(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Steps to reproduce: print:~ # truncate -s 10M disk.image print:~ # fdisk disk.image Welcome to fdisk (util-linux 2.31.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Device does not contain a recognized partition table. Created a new DOS disklabel with disk identifier 0x1245ac3a. Command (m for help): w The partition table has been altered. Syncing disks. print:~ # fdisk -l disk.image Disk disk.image: 10 MiB, 10485760 bytes, 20480 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x1245ac3a print:~ # losetup --list print:~ # kpartx -l disk.image print:~ # losetup --list NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE DIO LOG-SEC /dev/loop0 0 0 0 0 /root/disk.image 0 512 ??? Why does kpartx -l leave behind a loop device on the inspected image? ??? print:~ # cat /etc/os-release NAME="openSUSE Leap" VERSION="15.0" ID="opensuse-leap" ID_LIKE="suse opensuse" VERSION_ID="15.0" PRETTY_NAME="openSUSE Leap 15.0" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:leap:15.0" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" print:~ # uname -a Linux print 4.12.14-lp150.12.16-default #1 SMP Tue Aug 14 17:51:27 UTC 2018 (28574e6) x86_64 x86_64 x86_64 GNU/Linux print:~ # rpm -q kpartx kpartx-0.7.3+67+suse.8f0c27b-lp150.1.1.x86_64 The same behaviour occurs with Tumbleweed 20180831. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1095723] New: pin not working: no ARCHIVES.gz on medium or FTP
by bugzilla_noreply＠novell.com 19 May '21

19 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1095723 Bug ID: 1095723 Summary: pin not working: no ARCHIVES.gz on medium or FTP Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: Mathias.Homann(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- openSUSE has provided the "pin" command to locate files within uninstalled packages for many years. pin relies on being able to access a file /etc/SuSE-release to figure out the installed version, and a file /var/lib/pin/ARCHIVES.gz which on first use is copied from the installation media. ...there is no /etc/SuSE-release and there is no ARCHIVES.gz on installation medium or ftp. This majorly breaks all kind of administration routines. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1092425] New: Assertion failure in libclang on i586 (when building qtdoc)
by bugzilla_noreply＠novell.com 17 May '21

17 May '21

http://bugzilla.suse.com/show_bug.cgi?id=1092425 Bug ID: 1092425 Summary: Assertion failure in libclang on i586 (when building qtdoc) 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: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This appears when building KDE:Qt:5.11/libqt5-qtdoc. 100% reproducible on i586, never fails on x86_64. /home/abuild/rpmbuild/BUILD/qt-everywhere-src-5.11.0-rc/qtbase/src/corelib/qdoc_wrapper.sh -outputdir /home/abuild/rpmbuild/BUILD/qt-everywhere-src-5.11.0-rc/qtbase/doc/qtcore -installdir /usr/share/doc/packages/qt5 /home/abuild/rpmbuild/BUILD/qt-everywhere-src-5.11.0-rc/qtbase/src/corelib/doc/qtcore.qdocconf -prepare -no-link-errors -I. -Iglobal -I../3rdparty/harfbuzz/src -I../3rdparty/md5 -I../3rdparty/md4 -I../3rdparty/sha3 -I../3rdparty/forkfd -I../../include -I../../include/QtCore -I../../include/QtCore/5.11.0 -I../../include/QtCore/5.11.0/QtCore -I.moc -I.tracegen -isystem /usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I../../mkspecs/linux-g++ [ 348s] QT_HASH_SEED: forced seed value is not 0, cannot guarantee that the hashing functions will produce a stable value.qdoc: ../tools/clang/lib/Serialization/ASTWriter.cpp:4046: void clang::ASTWriter::GenerateNameLookupTable(const clang::DeclContext *, llvm::SmallVectorImpl<char> &): Assertion `ConversionNameSet.empty() && "Failed to find all of the visible " "conversion functions by walking all " "the lexical members of the context."' failed. [ 348s] libclang: crash detected during AST saving: { [ 348s] 'filename' : '/tmp/qdoc_pch.PWbpkA/QtCore.pch' [ 348s] 'options' : 0, [ 348s] } [ 348s] qdoc: ../include/llvm/Bitcode/BitstreamWriter.h:90: llvm::BitstreamWriter::~BitstreamWriter(): Assertion `BlockScope.empty() && CurAbbrevs.empty() && "Block imbalance"' failed. -- You are receiving this mail because: You are on the CC list for the bug.

2 15

[Bug 1124865] New: openssh-askpass-gnome recommended in non-gnome installation
by bugzilla_noreply＠novell.com 17 May '21

17 May '21

http://bugzilla.suse.com/show_bug.cgi?id=1124865 Bug ID: 1124865 Summary: openssh-askpass-gnome recommended in non-gnome installation Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Patterns Assignee: simonf.lees(a)suse.com Reporter: fabian(a)ritter-vogt.de QA Contact: qa-bugs(a)suse.de CC: lnussel(a)suse.com Found By: --- Blocker: --- patterns-base-x11 recommends openssh-askpass-gnome, which is thus installed even on LXQt and KDE desktops. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1090641] New: kronosnet-1.3 is available now
by bugzilla_noreply＠novell.com 12 May '21

12 May '21

http://bugzilla.suse.com/show_bug.cgi?id=1090641 Bug ID: 1090641 Summary: kronosnet-1.3 is available now Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: High Availability Assignee: ha-bugs(a)suse.de Reporter: bliu(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- kronosnet-1.3 is available now -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1057349] New: postfix/smtpd[3493]: fatal: bad string length 0 < 1: smtpd_sasl_path =
by bugzilla_noreply＠novell.com 12 May '21

12 May '21

http://bugzilla.suse.com/show_bug.cgi?id=1057349 Bug ID: 1057349 Summary: postfix/smtpd[3493]: fatal: bad string length 0 < 1: smtpd_sasl_path = 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: qingming.su(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The problem is found by fetchmail, which fails to fetch mail from a remote mailserver (runing postfix+dovecot) The console output looks like: admin@localhost:~> fetchmail -v --ssl mail.openqa.suse fetchmail: 6.3.26 querying mail.openqa.suse (protocol POP3) at Wed 06 Sep 2017 03:12:03 PM CST: poll started Trying to connect to 10.67.18.229/995...connected. fetchmail: Server certificate: fetchmail: Issuer Organization: SUSE fetchmail: Issuer CommonName: openQA CA fetchmail: Subject CommonName: mail.openqa.suse fetchmail: mail.openqa.suse key fingerprint: 4E:FD:84:BE:B5:6C:BF:B0:75:F2:F4:EF:E8:7F:50:9E fetchmail: POP3< +OK Dovecot ready. fetchmail: POP3> CAPA fetchmail: POP3< +OK fetchmail: POP3< CAPA fetchmail: POP3< TOP fetchmail: POP3< UIDL fetchmail: POP3< RESP-CODES fetchmail: POP3< PIPELINING fetchmail: POP3< AUTH-RESP-CODE fetchmail: POP3< USER fetchmail: POP3< SASL PLAIN fetchmail: POP3< . fetchmail: POP3> USER admin fetchmail: POP3< +OK fetchmail: POP3> PASS * fetchmail: POP3< +OK Logged in. fetchmail: POP3> STAT fetchmail: POP3< +OK 2 1446 fetchmail: POP3> LAST fetchmail: POP3< -ERR Unknown command: LAST fetchmail: Unknown command: LAST fetchmail: POP3> UIDL fetchmail: POP3< +OK fetchmail: POP3< 1 00000016599145ec fetchmail: POP3< 2 00000017599145ec fetchmail: POP3< . 2 messages for admin at mail.openqa.suse (1446 octets). fetchmail: POP3> LIST 1 fetchmail: POP3< +OK 1 741 fetchmail: POP3> TOP 1 99999999 fetchmail: POP3< +OK reading message admin@mail.openqa.suse:1 of 2 (741 octets) Trying to connect to ::1/25...connected. <fetchmail hangs here> The system journal disclosures the real issue: Sep 06 15:03:49 localhost postfix/smtpd[3442]: fatal: bad string length 0 < 1: smtpd_sasl_path = Sep 06 15:03:50 localhost postfix/master[2712]: warning: process /usr/lib/postfix/smtpd pid 3442 exit status 1 Sep 06 15:03:50 localhost postfix/master[2712]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling The error can be fixed by editing the configuration file /etc/postfix/main.cf, comment out the following lines: smtpd_sasl_path = smtpd_sasl_type = Note: the new lines look like: #smtpd_sasl_path = #smtpd_sasl_type = -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1037846] New: rpm -qf shows files as part of postfix, despite "files or directories still exist but are no longer part of Postfix"
by bugzilla_noreply＠novell.com 12 May '21

12 May '21

http://bugzilla.suse.com/show_bug.cgi?id=1037846 Bug ID: 1037846 Summary: rpm -qf shows files as part of postfix, despite "files or directories still exist but are no longer part of Postfix" 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: gp(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I saw the following when updating postfix the last few times: (18/50) Installing: postfix-3.2.0-4.1.x86_64 .............................[done] Additional rpm output: warning: /etc/postfix/main.cf created as /etc/postfix/main.cf.rpmnew Executing upgrade-configuration. Note: the following files or directories still exist but are no longer part of Postfix: /etc/postfix/postfix-files /etc/postfix/postfix-script /etc/postfix/post-install Updating /etc/sysconfig/postfix ... Updating /etc/sysconfig/mail ... Alas: > rpm -qf /etc/postfix/postfix-files postfix-3.2.0-4.1.x86_64 > rpm -qf /etc/postfix/postfix-script postfix-3.2.0-4.1.x86_64 > rpm -qf /etc/postfix/post-install postfix-3.2.0-4.1.x86_64 Isn't that inconsistent? -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1042529] New: YaST submodule windows don't remember their size and position when opened as standalone programs
by bugzilla_noreply＠novell.com 11 May '21

11 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1042529 Bug ID: 1042529 Summary: YaST submodule windows don't remember their size and position when opened as standalone programs Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: pointedstick(a)zoho.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Steps to reproduce: 1. Open any YaST submodule directly (e.g. search for "Software Management" from KRunner) 2. Adjust the window size and position 3. Close the window 4. Open it again the same way as in 1 Expected results: - The window spawns with the same size and position as it had when you last closed it Actual results: - The window opens at position 0,0 with a size of 1344x771. Additional information: - YaST's main window behaves properly and remembers its position; it's only submodule windows when opened directly that exhibit this issue. -- You are receiving this mail because: You are on the CC list for the bug.

2 3