August 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 905418] New: No audio/no sound when headphone is plugged in -- choosing "Headphones (unplugged)" in pavucontrol then works
by bugzilla_noreply＠novell.com 28 May '21

28 May '21

http://bugzilla.suse.com/show_bug.cgi?id=905418 Bug ID: 905418 Summary: No audio/no sound when headphone is plugged in -- choosing "Headphones (unplugged)" in pavucontrol then works Classification: openSUSE Product: openSUSE Factory Version: 201411* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: gp(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 613619 --> http://bugzilla.suse.com/attachment.cgi?id=613619&action=edit Screenshot showing pavucontrol vs GNOME Sound panel when external jack is unplugged This is an interesting one, current Factory with kernel 3.16.4-1.g7a8842b-default (and before that also with kernel-default-3.17.1-1.2.g5c4d099 I believe). Sounds on this Lenovo T430s notebook works just fine. Except when I plug in speakers or a headset, instead of switching off the internal speakers and activating that external audio -- silence. The GNOME Sound panel provides no way to address this. pavucontrol, however shows "Headphones (unplugged)", and when I select that as Output Device, everything works as it used to (with 13.1, 13.2 and Factory until a few days ago). 14: PCI 1b.0: 0403 Audio device [Created at pci.328] Unique ID: u1Nb.0TDI6CRLz81 SysFS ID: /devices/pci0000:00/0000:00:1b.0 SysFS BusID: 0000:00:1b.0 Hardware Class: sound Model: "Intel 7 Series/C210 Series Chipset Family High Definition Audio Controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x1e20 "7 Series/C210 Series Chipset Family High Definition Audio Controller" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x21fb Revision: 0x04 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xf2530000-0xf2533fff (rw,non-prefetchable) IRQ: 46 (1867 events) Module Alias: "pci:v00008086d00001E20sv000017AAsd000021FBbc04sc03i00" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=yes, avail=yes, need=no, active=unknown -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1094638] New: QEMU doesn't redirect F10 key
by bugzilla_noreply＠novell.com 24 May '21

24 May '21

http://bugzilla.suse.com/show_bug.cgi?id=1094638 Bug ID: 1094638 Summary: QEMU doesn't redirect F10 key Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: dheidler(a)suse.com QA Contact: qa-bugs(a)suse.de CC: agraf(a)suse.com Found By: --- Blocker: --- When I start a VM in QEMU using the command qemu-system-i386 -cdrom suse.iso suse.qcow2 I am not able to send the F10 key to the VM. When I press the F10 key, QEMU will open the "Machine" menu - even in keyboard grabbing mode. At least in keyboard grabbing mode ALL keys should be sent to the VM and not handled as a hotkey within the QEMU window. I'm running qemu version 2.11.1 -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[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 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 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

[Bug 1003362] New: server:monitoring/nagios: Bug
by bugzilla_noreply＠novell.com 11 May '21

11 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1003362 Bug ID: 1003362 Summary: server:monitoring/nagios: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: lars.vogdt(a)suse.com Reporter: ian.mcconnell(a)denbridgemarine.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com CC: nix(a)opensuse.org Found By: --- Blocker: --- Created attachment 696185 --> http://bugzilla.opensuse.org/attachment.cgi?id=696185&action=edit Fix permissions on command files. nagios creates the following files with the wrong permissions: # ls -l /var/spool/nagios/ srw-rw---- 1 nagios nagios 0 Oct 6 13:47 live prw-rw---- 1 nagios nagios 0 Oct 6 13:47 nagios.cmd For nagvis to access them, they need to be in group "nagcmd" srw-rw---- 1 nagios nagcmd 0 Oct 6 13:47 live prw-rw---- 1 nagios nagcmd 0 Oct 6 13:47 nagios.cmd Since "nagios.cmd" is a named pipe, the permission can be changed once to correct it, but "live" needs changing each time "nagios" is run. The following lines in /etc/nagios/nagios.cfg set these files: command_file=/var/spool/nagios/nagios.cmd broker_module=/usr/lib/check_mk/livestatus-nagios4.o /var/spool/nagios/live I noticed that the file "/usr/lib/nagios/nagios-exec-start-pre" tried to set these permissions by setting the variable nagios_cmdgrp. nagios_cmdgrp="$(get_var nagios_cmdgrp)" but nagois_cmdgrp isn't in /etc/nagios/nagios.cfg. It can't be added as nagios complains about an unknown definition and won't start. Also the line : ${nagios_cmdgrp:-nagcmd} doesn't seem to work for me when /bin/sh is linked to bash /bin/sh --version GNU bash, version 4.2.47(1)-release (x86_64-suse-linux-gnu) nagios_cmdgrp="" echo $nagios_cmdgrp : ${nagios_cmdgrp:-nagcmd} echo $nagios_cmdgrp : ${nagios_cmdgrp:=nagcmd} echo $nagios_cmdgrp nagcmd nagios_cmdgrp="xxxx" : ${nagios_cmdgrp:=nagcmd} echo $nagios_cmdgrp xxxx Unfortunately changing : ${nagios_cmdgrp:-nagcmd} to : ${nagios_cmdgrp:=nagcmd} doesn't fix the permissions on the command files # ls -l /var/spool/nagios/ srw-rw---- 1 nagios nagios 0 Oct 6 14:16 live prw-rw---- 1 nagios nagios 0 Oct 6 14:16 nagios.cmd as these are created after the process "nagios" starts. A workaround is to add the line ExecStartPost=/usr/lib/nagios/nagios-exec-start-post to nagios.service. I have attached the nagios-exec-start-post script. This works with # systemctl start nagios.service # systemctl restart nagios.service but for # systemctl reload nagios.service I get the wrong permissions: # ls -l /var/spool/nagios/ srw-rw---- 1 nagios nagios 0 Oct 6 14:23 live prw-rw---- 1 nagios nagcmd 0 Oct 6 14:16 nagios.cmd These are the nagios packages I installed: nagios-4.2.1-1.1.x86_64 nagios-www-4.2.1-1.1.x86_64 nagios-www-dch-4.2.1-1.1.x86_64 pnp4nagios-0.6.25-6.24.x86_64 pnp4nagios-nagios-0.6.25-6.24.x86_64 nagvis-1.8.5-3.1.noarch mk-livestatus-1.2.8p11-3.2.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

2 1