March 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 918705] New: alpine locking failure (against procmail) leads to mail corruption
by bugzilla_noreply＠novell.com 11 Mar '22

11 Mar '22

http://bugzilla.suse.com/show_bug.cgi?id=918705 Bug ID: 918705 Summary: alpine locking failure (against procmail) leads to mail corruption Classification: openSUSE Product: openSUSE Factory Version: 201502* Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: gp(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is something I started to see a bit ago, and since it now happened twice today I figured I'd report it. When I obtain mail via fetchmail, using procmail as the delivery agent, occasionally I get corrupted mails like the following (in mbox format): ==== snip ==== >From gp Thu Feb 19 18:56:54 2015 Mime-Version: 1.0 Date: Thu, 19 Feb 2015 18:56:00 +0100 Subject: AW: Re: Your help needed: Fwd: Comment opportunity: Software Status: RO X-Status: X-Keywords: X-UID: 9310 definedstorage Subject: AW: Re: Your help needed: Fwd: Comment opportunity: Software definedstorage References: <54E302D90200006F00158C8B(a)suse.com> <54E2D72A0200002B000A1B55(a)suse.com> <54E339FA0200006F00158DBD(a)suse.com> <54E2D7DE0200002B000A1B68(a)suse.com> <alpine.LSU.2.11.1502191739290.2252(a)ghan.fvgr> In-Reply-To: <alpine.LSU.2.11.1502191739290.2252(a)ghan.fvgr> Message-ID: <54E623B70200006F001594A6(a)suse.com> From: ... To: "Gerald Pfeifer" <gp(a)suse.com> ==== snap ==== This does not happen daily, and I believe it happens especially when I have been offline for several hours and a few dozen e-mails are delivered at once (though this specific case was not that). The same configuration had been working for years without ever showing this problem, and it looks like looking on the Alpine side (or procmail, though less likely I guess, since it essentially only reads :0 INBOX ) -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 906594] New: Apper showing wrong package description
by bugzilla_noreply＠novell.com 17 Feb '22

17 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=906594 Bug ID: 906594 Summary: Apper showing wrong package description Classification: openSUSE Product: openSUSE Factory Version: NO 13.2 BUGS!! Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications Assignee: kde-maintainers(a)suse.de Reporter: erwin.vandevelde(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Apper shows the package's description when clicking on it, but only for the first package you click on this is done correctly. Apper shows the same description again and again for each other package you click on. Versions: apper 0.9.1-2.1 -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 942751] New: python3 test / missing __main__ module
by bugzilla_noreply＠novell.com 17 Feb '22

17 Feb '22

http://bugzilla.suse.com/show_bug.cgi?id=942751 Bug ID: 942751 Summary: python3 test / missing __main__ module Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: myemailu(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When running python 3 -m test the output is: Traceback (most recent call last): File "/usr/lib64/python3.4/runpy.py", line 170, in _run_module_as_main "__main__", mod_spec) File "/usr/lib64/python3.4/runpy.py", line 85, in _run_code exec(code, run_globals) File "/usr/lib64/python3.4/_import_failed/test.py", line 21, in <module> Please file a bug on the SUSE Bugzilla.""".format(__name__)) ImportError: Module '__main__' is not installed. It is supposed to be part of python3 distribution, but missing from failed import map. Please file a bug on the SUSE Bugzilla. I'm using python3 on Tumbleweed rpm -qi python3 Name : python3 Version : 3.4.3 Release : 4.1 Architecture: x86_64 Install Date: Mi 29 Jul 2015 22:03:48 CEST Group : Development/Languages/Python Size : 2996719 License : Python-2.0 Signature : RSA/SHA256, Di 28 Jul 2015 11:49:27 CEST, Key ID b88b2fd43dbdc284 Source RPM : python3-3.4.3-4.1.src.rpm Build Date : Di 28 Jul 2015 11:49:14 CEST Build Host : build75 Relocations : (not relocatable) Packager : http://bugs.opensuse.org Vendor : openSUSE URL : http://www.python.org/ Summary : Python3 Interpreter -- You are receiving this mail because: You are on the CC list for the bug.

2 26

[Bug 917759] New: osc fails with a python exception
by bugzilla_noreply＠novell.com 17 Feb '22

17 Feb '22

http://bugzilla.suse.com/show_bug.cgi?id=917759 Bug ID: 917759 Summary: osc fails with a python exception Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: BuildService Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: lmb(a)suse.com QA Contact: adrian(a)suse.com Found By: --- Blocker: --- This is about the latest osc client on Factory (osc-0.150.1-158.1.noarch) used on the internal build service instance: # iosc rdiff Devel:Storage:1.0 _product SUSE:SLE-12:Update:Products:Cloud5 Traceback (most recent call last): File "/usr/bin/osc", line 26, in <module> r = babysitter.run(osccli) File "/usr/lib/python2.7/site-packages/osc/babysitter.py", line 61, in run return prg.main(argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 343, in main return self.cmd(args) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 366, in cmd retval = self.onecmd(argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 500, in onecmd return self._dispatch_cmd(handler, argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 1230, in _dispatch_cmd return handler(argv[0], opts, *args) File "/usr/lib/python2.7/site-packages/osc/commandline.py", line 3593, in do_rdiff expand=not opts.unexpand) File "/usr/lib/python2.7/site-packages/osc/core.py", line 4488, in server_diff_noex unified, missingok, meta, expand) File "/usr/lib/python2.7/site-packages/osc/core.py", line 4477, in server_diff f = http_POST(u) File "/usr/lib/python2.7/site-packages/osc/core.py", line 3201, in http_POST def http_POST(*args, **kwargs): return http_request('POST', *args, **kwargs) File "/usr/lib/python2.7/site-packages/osc/core.py", line 3144, in http_request install_opener(conf._build_opener(url)) File "/usr/lib/python2.7/site-packages/osc/conf.py", line 507, in _build_opener from . import oscssl File "/usr/lib/python2.7/site-packages/osc/oscssl.py", line 8, in <module> import M2Crypto.httpslib File "/usr/lib64/python2.7/site-packages/M2Crypto/__init__.py", line 24, in <module> import ASN1 File "/usr/lib64/python2.7/site-packages/M2Crypto/ASN1.py", line 12, in <module> import BIO File "/usr/lib64/python2.7/site-packages/M2Crypto/BIO.py", line 221, in <module> class CipherStream(BIO): File "/usr/lib64/python2.7/site-packages/M2Crypto/BIO.py", line 227, in CipherStream SALT_LEN = m2.PKCS5_SALT_LEN AttributeError: 'module' object has no attribute 'PKCS5_SALT_LEN' Most invocations fail like that for me, including "osc up", submitreq, etc, making it completely unusable for me. -- You are receiving this mail because: You are on the CC list for the bug.

2 21

[Bug 936416] New: harfbuzz 32bit devel package missing symlinks
by bugzilla_noreply＠novell.com 10 Feb '22

10 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=936416 Bug ID: 936416 Summary: harfbuzz 32bit devel package missing symlinks Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: admin(a)leinir.dk QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The 32bit devel package of harfbuzz (and accompanying harfbuzz-icu) is missing the .so symlinks in /usr/lib. Temporary workaround: ln -s libharfbuzz.so.0 /usr/lib/libharfbuzz.so ln -s libharfbuzz-icu.so.0 /usr/lib/libharfbuzz-icu.so -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 954329] New: Purely virtual bridge breaks networking
by bugzilla_noreply＠novell.com 08 Feb '22

08 Feb '22

http://bugzilla.suse.com/show_bug.cgi?id=954329 Bug ID: 954329 Summary: Purely virtual bridge breaks networking Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: lmb(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Take a purely virtual bridge (to be used for VMs) with a static network configuration: # cat /etc/sysconfig/network/ifcfg-br0 STARTMODE='auto' BOOTPROTO='static' BRIDGE='yes' BRIDGE_PORTS='' BRIDGE_FORWARDDELAY='0' BRIDGE_STP='off' IPADDR='172.16.1.1/24' enp0s25 is the local, normal ethernet interface which is working fine: 2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 Now: # ifup br0 # ip link 2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UP mode DEFAULT group default qlen 1000 link/ether 28:d2:44:df:33:18 brd ff:ff:ff:ff:ff:ff 9: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 28:d2:44:df:33:18 brd ff:ff:ff:ff:ff:ff It seems that the scripts use the ethernet interface as the *default* value for BRIDGE_PORTS, which obviously then breaks networking. (If I had wanted a slaved network device, I'd have configured one.) brctl addbr br0 ; ip a add dev br0 172.16.1.1/24 ; ip link set br0 up creates the desired configuration just fine and is what I'd have expected given the configuration file. -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 966599] New: home:j-engel/bacula: Bug
by bugzilla_noreply＠novell.com 15 Jan '22

15 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=966599 Bug ID: 966599 Summary: home:j-engel/bacula: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: jcnengel(a)gmail.com Reporter: marc(a)marcchamberlin.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Tried to download/install Bacula 7.4.0 using the 1 click installer and downloading the RPM package. I get the following error - nothing provides libbaccats-7.4.0.so()(64bit) needed by bacula-7.4.0-6.2.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 940478] New: ASL: rename conflicting-confusing package
by bugzilla_noreply＠novell.com 14 Jan '22

14 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=940478 Bug ID: 940478 Summary: ASL: rename conflicting-confusing package Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: All OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: alinm.elena(a)gmail.com Reporter: jengelh(a)inai.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- openSUSE:Factory already has an "asl" package, and recently gained an "ASL" package. This very same name is, I will argue, confusing for both users and developers, as they only differ in case, and case is not something people pay sufficient attention to when e.g. reporting bugs or discussing. I suggest to rename the ASL package. Considering that "asl library" yields lots of different things on Google already, a package name like "advsimlib" might work better than "asllib". Confer with the asl.org.il team perhaps. [ The current plan is to reject, in the direct future, same-name submissions to Factory which only differ in casing. On a related notem, libzypp even falls over currently (but probably intentionally; see bug #940477). ] -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 937067] New: efi=1 does not seem to work anymore
by bugzilla_noreply＠novell.com 17 Dec '21

17 Dec '21

http://bugzilla.suse.com/show_bug.cgi?id=937067 Bug ID: 937067 Summary: efi=1 does not seem to work anymore Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: kukuk(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- In the past, you could add efi=1 as argument for the installer, and your system was setup for EFI boot, even if the detection fails. This works only partly with Tumbleweed 20150630: the bootloader still installs and configures grub2-x86_64-efi, but the storage proposal does not create a vfat /boot/EFI partition anymore. This works with SLES12, haven't tested openSUSE 13.2. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 972787] New: [gpg-agent] Rework agent startup for DM sessions.
by bugzilla_noreply＠novell.com 01 Dec '21

01 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=972787 Bug ID: 972787 Summary: [gpg-agent] Rework agent startup for DM sessions. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE 42.1 Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: eich(a)suse.com QA Contact: qa-bugs(a)suse.de CC: astieger(a)suse.com, meissner(a)suse.com, premysl.janouch(a)suse.com, werner(a)suse.com, xorg-maintainer-bugs(a)forge.provo.novell.com Found By: Development Blocker: --- The gpg-agent for a user session is started by the script /etc/X11/xdm/sys.xsession. An openSUSE user pointed out to me that the socket handling of the gpg-agent has changed with gpg 2.1 - now neither a env file is written (the option --write-env-file is ignored) nor nor does anything use the env variable GPG_AGENT_INFO. Instead today a standard socket is used in $HOME/.gnupg/S.gpg-agent. Also check: https://gnupg.org/faq/whats-new-in-2.1.html If NFS mounted homes are desired, it can be handled as described in: https://wiki.gnupg.org/NFS This requires reworking of the gpg-agent startup (and possibly also of the ssh-agent) in sys.xsession. Any takers? -- You are receiving this mail because: You are on the CC list for the bug.

2 4