February 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 904210] New: package link not shown in web UI
by bugzilla_noreply＠novell.com 24 Jun '20

24 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=904210 Bug ID: 904210 Summary: package link not shown in web UI Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: nico.kruber(a)gmail.com QA Contact: adrian(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:33.0) Gecko/20100101 Firefox/33.0 Build Identifier: if repo B is based on repo A which contains package C, then linking to B:C (without C being directly available in B) produces no UI elements to show (un)expanded sources in the web UI, neither is the link shown as such ("links to ...") example: https://build.opensuse.org/package/show/KDE:Extra/PackageKit https://build.opensuse.org/package/show/KDE:Extra/PackageKit?expand=0 https://build.opensuse.org/package/show/KDE:Extra/PackageKit?expand=1 Reproducible: Always Steps to Reproduce: 1. create link to a package in openSUSE:13.2:Update which is only available in openSUSE:13.2 2. browse to that link Actual Results: the link exists but is not shown as such Expected Results: same UI as if the package was linked to openSUSE:13.2 directly -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 953287] New: gdb internal-error: value_contents_bits_eq: Assertion `offset2 + length <= TYPE_LENGTH (val2->enclosing_type) * TARGET_CHAR_BIT' failed.
by bugzilla_noreply＠novell.com 12 Jun '20

12 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=953287 Bug ID: 953287 Summary: gdb internal-error: value_contents_bits_eq: Assertion `offset2 + length <= TYPE_LENGTH (val2->enclosing_type) * TARGET_CHAR_BIT' failed. Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: rguenther(a)suse.com Reporter: mpluskal(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 654335 --> http://bugzilla.opensuse.org/attachment.cgi?id=654335&action=edit core file When opening coredump for pinger (part of squid). following occurs: #17 0x000056267a78966c in IcmpPinger::Recv (this=0x56267a99b620 <control>) at IcmpPinger.cc:166 _dbo = warning: can't find linker symbol for virtual table for `std::basic_ostream<char, std::char_traits<char> >' value warning: found `construction vtable for std::__cxx11::basic_ostringstream<char, std::char_traits<char>, std::allocator<char> >-in-Debug::OutStream' instead @0x56267b3f16c0: warning: can't find linker symbol for virtual table for `std::basic_ostream<char, std::char_traits<char> >' value warning: found `construction vtable for std::__cxx11::basic_ostringstream<char, std::char_traits<char>, std::allocator<char> >-in-Debug::OutStream' instead {<std::basic_ios<char, std::char_traits<char> >> = {<std::ios_base> = {_vptr.ios_base = 0x56267a994978 <construction vtable for std::__cxx11::basic_ostringstream<char, std::char_traits<char>, std::allocator<char> >-in-Debug::OutStream+64>, static boolalpha = std::_S_boolalpha, static dec = std::_S_dec, static fixed = std::_S_fixed, static hex = std::_S_hex, static internal = std::_S_internal, static left = std::_S_left, static oct = std::_S_oct, static right = std::_S_right, static scientific = std::_S_scientific, static showbase = std::_S_showbase, static showpoint = std::_S_showpoint, static showpos = std::_S_showpos, static skipws = std::_S_skipws, static unitbuf = std::_S_unitbuf, static uppercase = std::_S_uppercase, static adjustfield = std::_S_adjustfield, static basefield = std::_S_basefield, static floatfield = std::_S_floatfield, static badbit = std::_S_badbit, static eofbit = std::_S_eofbit, static failbit = std::_S_failbit, static goodbit = std::_S_goodbit, static app = std::_S_app, static ate = std::_S_ate, static binary = std::_S_bin, static in = std::_S_in, static out = std::_S_out, static trunc = std::_S_trunc, static beg = std::_S_beg, static cur = std::_S_cur, static end = std::_S_end, _M_precision = 2, _M_width = 0, _M_flags = 4102, _M_exception = std::_S_goodbit, _M_streambuf_state = std::_S_goodbit, _M_callbacks = 0x0, _M_word_zero = {_M_pword = 0x0, _M_iword = 0}, _M_local_word = {../../gdb/value.c:823: internal-error: value_contents_bits_eq: Assertion `offset2 + length <= TYPE_LENGTH (val2->enclosing_type) * TARGET_CHAR_BIT' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 920134] New: windows:mingw:win{32,64}/mingw{32,64}-binutils: windmc memory bug
by bugzilla_noreply＠novell.com 11 Jun '20

11 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=920134 Bug ID: 920134 Summary: windows:mingw:win{32,64}/mingw{32,64}-binutils: windmc memory bug Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: All OS: Windows Status: NEW Severity: Major Priority: P5 - None Component: 3rd party software Assignee: fstrba(a)suse.com Reporter: gitne(a)gmx.de QA Contact: opensuse-communityscreening(a)forge.provo.novell.com CC: fridrich.strba(a)bluewin.ch, gitne(a)gmx.de, hib(a)hiberis.nl, mkbosmans(a)gmail.com, tlillqvist(a)suse.com Found By: Community User Blocker: No Created attachment 624972 --> http://bugzilla.opensuse.org/attachment.cgi?id=624972&action=edit Sample source message file for windmc without a trailing line feed (U+000A) character If the input file does not end with a line feed character (U+000A) the windmc tool eats up all the memory and then terminates with an out of memory error. To reproduce, try the atteched sample.mc file. Append a line feed character at the end of the file and windmc works (mostly) as intended. Warning: Be careful when reproducing on 64 bit systems with lots of RAM and/or swap space. This operation may cause the system to seemingly block for an extended amount of time. It is probably best to use the mingw32 version of windmc or to specifically limit the available amount of memory to the process to a reasounable amount. -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 948280] New: windows:mingw:win{32,64}/mingw{32,64}-filesystem: Add hardening options?
by bugzilla_noreply＠novell.com 06 Jun '20

06 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=948280 Bug ID: 948280 Summary: windows:mingw:win{32,64}/mingw{32,64}-filesystem: Add hardening options? Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: fstrba(a)suse.com Reporter: gerald(a)wireshark.org QA Contact: opensuse-communityscreening(a)forge.provo.novell.com CC: fridrich.strba(a)bluewin.ch, hib(a)hiberis.nl, idonmez(a)suse.com, mkbosmans(a)gmail.com, tlillqvist(a)suse.com Found By: --- Blocker: --- It doesn't appear that any of the mingw:win32 or mingw:win64 packages are built with hardening options enabled, e.g. --dynamicbase, --nxcompat, and --highentropyva. Would it be possible to do so? -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 911001] New: dnsmasq apparmor profile prevents libvirt default network to start
by bugzilla_noreply＠novell.com 05 Jun '20

05 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=911001 Bug ID: 911001 Summary: dnsmasq apparmor profile prevents libvirt default network to start Classification: openSUSE Product: openSUSE Factory Version: 201412* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: AppArmor Assignee: suse-beta(a)cboltz.de Reporter: cbosdonnat(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This commit in libvirt forces dnsmasq to actually use the leaseshelper program: http://libvirt.org/git/?p=libvirt.git;a=commit;h=421406808abaf7eb66abd27d71… The problem is that the dnsmasq apparmor profile prevents the libvirt default network to start due to: * Not allowing /bin/bash to be run * Not allowing leaseshealper contained in /usr/lib64 folder to be run. Note that this bug may hit 13.2 if an updated libvirt is shipped there. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 966057] New: RPM pacakges won't regenerate initrd on removal
by bugzilla_noreply＠novell.com 29 May '20

29 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=966057 Bug ID: 966057 Summary: RPM pacakges won't regenerate initrd on removal Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: All 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: --- Currently there are two macros in /etc/rpm/macros.initrd: %regenerate_initrd_post, to be called in the %post and %postun sections and %regenerate_initrd_posttrans, to be called in %posttrans. %regenerate_initrd_post simply sets a flag that the initrd has to be rebuilt after the transaction. The posttrans macros takes care of that. Now, that works fine for installation (%post -> %posttrans) and upgrades (%postun -> %post -> %posttrans), but on removal, %posttrans is never run. How could that be implemented properly? -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 954505] New: yast ruby msg extractor (xgettext) does not support format marker
by bugzilla_noreply＠novell.com 06 May '20

06 May '20

http://bugzilla.suse.com/show_bug.cgi?id=954505 Bug ID: 954505 Summary: yast ruby msg extractor (xgettext) does not support format marker Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: ke(a)suse.com QA Contact: jsrain(a)suse.com CC: 5yrnyk(a)myway.com, ancor(a)suse.com, dimstar(a)opensuse.org, ke(a)suse.com Depends on: 954357 Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #954357 +++ When installing Leap 42.1 (or 13.2) with Ukrainian localization the page of user account setup is skipped with error: Details: malformed format string - %*[0-9] Caller: /usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.9.2/lib/fast_gettext/vendor/string.rb:70:in `%' Other tried localizations show user account page correctly. y2logs is attached ============================================================================= Karl Eichwalder 2015-11-10 17:36:40 CET (In reply to Ancor Gonzalez Sosa from comment #5) > Silly me! I was looking at Estonian .po file (et) and checking the effect in > Greek language (el). But turns out el!=et. :-) > > In Estonian it's not broken just because the translation is marked as fuzzy > (so not included in the .mo file)... a missing translation that is not that > obvious when you are staring at a Greek screen and you see no English text. > :-D > > So, in the end, it's a bug in the uk/users.po, as expected from the very > beginning. So reassigning to translations. Ok, thanks for debugging. It would work better, if the ruby xgettext extractor would add formatting markers as it does for other languages such as c or even ycp: #, c-format #, ycp-format I'm not sure whether that's a general issue or whether our yast xgettext extractor just does not know about this. Without such markers we are not (easily) able to validate the translations -- we usually do this with msgfmt. -- You are receiving this mail because: You are on the CC list for the bug.

1 21

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